Android phones

From YobiWiki
Revision as of 13:43, 22 April 2016 by <bdi>PhilippeTeuwen</bdi> (talk | contribs) (→‎From fastboot)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

OnePlus 2

ADB

To use adb, you need to get the USB ID to be recognized:
From pseudo CD-ROM getting mounted when phone is plugged: 

sudo "/media/<user>/OnePlus Drivers/adb_config_Linux_OSX.sh"

It's doing 

echo 0x2a70 >> ~/.android/adb_usb.ini
adb kill-server

Settings:

  • tap 7x on Settings / About / Build to activate the developer menu
  • enter developer menu
  • activate usb debug
  • authorize auth OEM unlock

Unlock

!!!THIS ERASES ALL DATA!!! 

adb reboot bootloader
fastboot oem unlock
fastboot oem device-info

Recovery

adb reboot bootloader
fastboot boot twrp-2.8.7.0-oneplus2.img

To enter stock recovery: 

adb reboot recovery

In case of trouble one may also do: 

adb reboot bootloader
fastboot boot twrp-2.8.7.0-oneplus2.img
adb reboot recovery

One can also activate a special menu on power down action, allowing to reboot in fastboot or recovery:

Developer options -> advanced reboot

There is also a hardware key to boot in recovery:

  • Switch off the phone
  • Hold Volume up button, and then press the power button once

SuperSU

OTA

OTA updates are stored on /sdcard/.OnePlusOta/ but as explained in Android, I prefer flashing full factory images.

Flashing images

OnePlus doesn't distribute factory images, but there are two types of images available on XDA forum:

From sideload

Images from http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863

Enter stock recovery, then: 

-> Install from USB / ok
adb sideload OnePlus2Oxygen_14_OTA_009_all_1510112055.zip
-> reboot, let it optimizing its apps

To root: 

adb reboot bootloader
fastboot boot twrp-2.8.7.0-oneplus2.img
-> sideload
adb sideload BETA-SuperSU-v2.xx.zip

launch supersu

  • add a PIN

launch again all apps requesting root:

  • adb shell su
  • adbd insecure (enable/enable)
  • titanium
  • busybox pro (smart install)
  • helium
  • root explorer (monter r/w .. r/o)
  • es explorateur
  • shark
  • sshdroid pro
    • ssh-copy-id root@192.168.1.142
    • params: launch at boot, remove pwd auth!!, manage keys:ON

Before installing ROM:

  • Boot your phone in TWRP recovery
  • Select Wipe option > Advanced Wipe > Select Dalvik Cache, System and Cache & Swipe to Wipe

From fastboot

There are some images from http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 flashable from fastboot: ..._fastboot. zip

Therer are only *.bat but it's basically the same commands on linux.
To preserver data partition, remove the line 

fastboot flash userdata userdata.img

or 

fastboot flash userdata userdata_64G.img

Troubleshooting

TitaniumBackup

If TitaniumBackup fails claiming there is not enough storage (and that obviously you have enough of it), untick the 'Mount namespace separation' setting in SuperSU and reboot.

Nexus 4

https://en.wikipedia.org/wiki/Nexus_4

Hardware

  • Chipset: Qualcomm Snapdragon™ S4 Pro processor with 1.5GHz Quad-Core Krait CPUs
  • Operating System: Android 4.2, Jelly Bean
  • Network: 3G (WCDMA), HSPA+
  • Display: 4.7-inch WXGA True HD IPS Plus (1280 x 768 pixels)
  • Memory: 8GB / 16GB
  • RAM: 2GB
  • Camera: 8.0MP rear / 1.3MP HD front
  • Battery: 2,100mAh Li-Polymer (embedded) / Talk time: 15.3 hours / Standby: 390 hours
  • Size: 133.9 x 68.7 x 9.1mm
  • Weight: 139g
  • Other:
    • NFC: Broadcom BCM2079x family: BCM20793 over I2C, cf /dev/bcm2079x-i2c
    • SE: ST33 from STMicroelectronics
    • Wireless charging
    • Miracast
    • BT 4.0
    • SlimPort for HDMI

Versions

physical mark

  • FCC ID: ZNFE960 IC:2703C-E960
  • MODEL LG-960 MADE IN KOREA

under fastboot, stock

  • PRODUCT_NAME - mako
  • VARIANT - mako 16GB
  • HW VERSION - rev_11
  • BOOTLOADER VERSION - MAKOZ10o
  • BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.48
  • CARRIER INFO - None
  • SERIAL NUMBER - xxxxxx
  • SIGNING - production
  • SECURE BOOT - enabled
  • LOCK STATE - lock

under 'About phone' from the settings, stock 4.2.2

  • Android 4.2.2
  • Baseband M9615A-CEFWMAZM-2.0.1700.48
  • Kernel 3.4.0-perf-g7ce11cd
  • Build JDQ39

under 'About phone' from the settings, 4.3

  • Android 4.3
  • Baseband M9615A-CEFWMAZM-2.0.1700.84
  • Kernel 3.4.0-perf-gf43c3d9
  • Build JWR66V then JWR66Y

My tunings

  • Original recovery
  • Rooted with "SuperSU"
    • "SuperSU" protected by PIN
    • Rooting maintained over OTA updates (using chattr +i and "SuperSU" survival mode)
  • OEM locked again
    • "Bootunlocker" app to unlock without wiping
  • Avast Mobile Security
    • anti theft with anchor in system (so even factory reset doesn't help)
    • application firewall (wifi/3g/roaming per app)
  • USB debugging activated and paired with my PC
    • "adbd insecure" installed
  • "BusyBox Pro"
  • "OpenVPN Install" & "OpenVPN Settings"
  • "SSHDroidPro"
  • Encrypted
    • with better pwd at boot time, using "Cryptfs password" app
  • Bluetooth & Belkin A2DP for car: no need to unlock my screen
    • "Bluetooth Auto Connect" -> pairs when screen is turned on
    • "Bluetooth connect and play" -> starts playing when paired
  • "AdAway" installed via "F-Droid"
  • "Nexus 4 Dot" as live wallpaper
  • "Helium" to backup & sync apps via Google Drive
  • With Android 4.4 install launcher of Nexus 5:

Nexus S

Old notes here

Versions

physical sticker behind battery

  • Model: GT-I9023
  • FCC ID: A3LGTI9023
  • SSN: -I9023GSMH
  • IMEI: xxxxxxx
  • S/N: xxxxxxx

under fastboot, after upgrade to 4.1.2

  • Bootloader version - I9020XXLC2
  • Baseband version - I9020XXKI1
  • Carrier info - EUR

under 'About phone' from the settings, after upgrade to 4.1.2

  • Android 4.1.2
  • Baseband I9023XXKI1
  • Kernel 3.0.31-g5894150 android-build@vpbs1 #1
  • Build JZO54K

Upgrading to 4.1.2

OTA update is available and the phone proposed me to start upgrade process
update zip is located in /cache 

android# ls -l /cache
pc$ adb pull /cache/9U4MCfNt.zip .

Preparation

  • Go to fastboot (vol-up + power)
  • Go to recovery
  • Backup & restore / Backup
  • Mount USB
  • Copy all /sdcard content to PC
  • Reboot -> enter fastboot again

Preparation bis

  • edit 9U4MCfNt.zip to remove recovery/ and edit META-INF/com/google/android/updater-script
    • remove all commands about recovery
    • add following line to keep rooted: set_perm(0, 0, 6755, "/system/bin/su");
    • radio image don't seem to be affected by update, nothing to do here

This time I tried differently:

  • pc$ adb push 9U4MCfNt.zip /cache
  • dd if=boot.img of=boot-fit.img bs=262144 count=28 #(with original boot.img from 4.1.1)
  • fastboot flash boot boot-fit.img

Upgrade

This time I tried differently:

  • Reboot and accept upgrade, it will reboot the phone and let Clockwork recovery applying the patch
  • Despite the set_perm, recovery told me "Root access possibly lost. Fix? /system/bin/su" and I accepted, just in case...
  • Backup & restore / Backup
  • Mount USB
  • Copy new backup to PC
  • Reboot

Rooting again

  • Extract new 4.1.2 boot.img (e.g. using clockworkmod backup or:)
  • modify it & flash it back, see below
android$ su
android# cat /dev/mtd/mtd2 > /sdcard/boot.img
adb pull /sdcard/boot.img .
abootimg -x boot.img
mkdir ramdisk
cd ramdisk
gzip -dc ../initrd.img | cpio -i
sed -i 's/ro.secure=1/ro.secure=0/' default.prop
find . -print|cpio -o -Hnewc|gzip > ../initrd.img2
cd ..
abootimg -u boot.img -r initrd.img2
dd if=boot.img of=boot-fit.img bs=262144 count=28
fastboot flash boot boot-fit.img

Installing Cyanogenmod

See http://wiki.cyanogenmod.org/w/Install_CM_for_crespo and repository for Crespo
Boot into cyanogenmod recovery

  • Wipe data/factory reset
adb shell mount /data
adb push YOURROMZIP.zip /sdcard/
  • Install zip from sdcard
  • Choose zip from sdcard...
  • Reboot

To install Google apps, see http://wiki.cyanogenmod.org/w/Gapps

Rooting Samsung Galaxy Tab 10.1

cf http://forum.xda-developers.com/showthread.php?t=1239185
I used a WinXP within a virtualbox under Debian
When flashing with Odin3 I had problems process being stuck at SetupConnection
Trick was to unplug physically the USB cable, start Odin3, plug the cable, connect the USB device through virtualbox to WinXP

Once rooted, upgrade the Superuser application
Once started, the app should detect su binary needs also to be updated. Follow instructions.

To enter clockwork recovery: power off / press vol down + power till 2 icons appear / press vol down to select left icon / press vol up / you should see recovery menu now

Installing new Market application:
Some apk are lying around, here is how I use them
First test their certificate as I don't want to get a malicious app: 

$ adb install Vending_3.1.5.apk 
Failure [INSTALL_FAILED_ALREADY_EXISTS]


This is ok, but e.g. this one seems more worrisome, I wouldn't try it: 

$ adb install Vending_3.1.6.apk 
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]

Make your backups!
Replace manually /system/app/Vending.apk by the new version and reboot.
If trouble you may try to clean the Dalvik cache from Clockwork recovery advanced menu 

busybox  mount -o remount,rw /system
mv /system/app/Vending.apk /sdcard/Vending_1.0.apk
mv /sdcard/Vending_3.1.5.apk /system/app/Vending.apk
chown 0.0 /system/app/Vending.apk
busybox  mount -o remount,ro /system

Rooting Samsung Galaxy Tab 3 7.0 3G/WiFi

cf http://honai-android.blogspot.be/2013/11/how-to-root-galaxy-tab-3-70-sm-t211-on.html
For model number SM-T211!
Other methods reflash completely the device, I prefer the less intrusive method consisting in just installing CyanoGenMod Recovery and SuperSU
I used a Win7 within a virtualbox under Debian
I used

Steps:

  • Enable USB Debugging Mode on the device by navigating to Settings >> Developer Options.
  • Extract CWM and Odin 3.07 files
  • Switch off the Galaxy Tab 3 7.0. Then boot the device into Download Mode by pressing and holding Volume Down, Home and Power buttons together until a construction Android robot icon with a warning triangle appears on screen. Now press the Volume Up button to enter Download Mode.
  • Plug the tablet to let Windows discovering and configuring the device USB drivers
  • Unplug the tablet
  • Run Odin on the computer as an Administrator.
  • Plug the tablet. Wait until Odin detects the device. When the device is connected successfully, the ID: COM box will turn to light blue with the COM port number. Additionally, the successful connected will be indicated by a message saying Added.
  • In Odin, click the PDA button and select the recovery.tar.md5 file. Verify that F. Reset Time checkbox is selected. Also, ensure the Auto Reboot and Re-Partition options are NOT selected.
  • Double-check and click Start button in Odin. The installation process will now begin.
  • Once the installation process completes, you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect the device from the computer.
  • Reboot the device into CWM Recovery mode by pressing and holding Volume Up, Home and Power buttons together.
  • In CWM Recovery, select "install zip / install zip from sideload"
  • Back on Debian:
adb sideload android-armeabi-universal-root-signed.zip
  • Once the installation process completes, return to main recovery menu and select "reboot system now".
Retrieved from "https://wiki.yobi.be/index.php?title=Android_phones&oldid=10034"