Skip to content

Android User Patterns

Jump to bottom
raisercostin edited this page Jul 28, 2017 · 32 revisions

Patterns

Backup Current Device

  • RootAndroidDevice
  • Install Titanium Backup Tool (needs root).
  • Configure it with:
    • backup external SD Data as well (some apps save their data there) - Preferences > Backup app external data > Enabled (Always).
  • Backup to SDCard(internal,external)/Dropbox/GoogleDrive all your phone with Titanium Backup Tool (see http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-user-guide.html)
    • applications (apks: user and system apps)
    • app data
      • internal (usually not available if the devices is not rooted)
      • external
        • internal sd card (emulated)
        • external sd card (might be encrypted)

Root Android Device

Procedure

  1. With a new phone (samsung gio in my case)
  2. Download and/or Copy from sdcard the kingroot.apk.
  3. Settings:
    • Unknown sources: checked. Allow installation of non-Market applications.
    • USB debugging: checked. Debug mode when USB is connected (if root from external OS: windows/osx/linux).
  4. Add WiFi (kingroot require network connectivity)
  5. Run kingroot app.
  6. Rooted!!!!

Notes

KingoRoot

KingRoot

  • it works with SuperSu Me?

Super User Manager

After you root you might want to replace the default super user manager that grants root rights to different applications. The options are:

Restore on Current Device

Fix Permissions

On some Samsungs the CWM-based Recovery has the option to fix permissions. See https://forum.xda-developers.com/galaxy-s2/help/fix-permissions-t1251296 . My Samsung-GT-S5660--Gio haas the CWM-based Recovery v5.0.2.6

Recovery Tools

Enable them by power off > home+power on (Samsung-GT-S5660--Gio). Among options:

  • apply update from sdcard
  • wipe data/factory reset
  • wipe cache partition
  • install zip from sdcard
  • backup and restore
  • mounts and storage
  • advanced
    • reboot recovery
    • wipe Dalvik cache
    • wipe battery status
    • report error
    • key test
    • show log
    • partition SD Card
    • fix permissions

Recover Bootloader

If you managed to Soft Brick your android device you still might have some options:

  • Odin
  • Heimdall-1.4.0
  • Heimdall-Gui-1.4.0 (harder to describe what to put where)

Deprecated options:

  • heimdall-one-click

The process go as the following:

  1. You need some drivers that will now to connect to your device
  2. Heimdall should detect the serial port when you plug your android
    heimdall detect
  3. Find out the name of the partitions: heimdall print-pit > <myPartitions>.txt
  4. You run a command to transfer various files to your device like this:
    heimdall flash --IBL+PBL boot.bin --SBL sbl.bin --SBL2 Sbl.bin --PARAM param.lfs --KERNEL zImage --FACTORYFS factoryfs.rfs --CACHE cache.rfs --MODEM modem.bin --verbose
    The parameters are the name of the partitions and various files that you found online for your phone.

Other useful things:

  • Check partitions from .pit files: heimdall print-pit --file s1_odin_20100512.pit

Choose OS

You have several options:

Android Alternative Marketplaces

Low Level Shell To Android

adb shell
su
#list full details
ls -l /
#change owner: root, system, ...
chown groupId.userId /system/*

# !!! If you do this at reboot the device is blocked in a [[Boot Loop]]
#allow to change rights on a read only filesystem: After error: Unable to chmod /system/app/AccountAndSyncSettings.apk: Read-only file system
mount -o rw,remount -t rootfs rootfs /system
#change rights
chmod 777 /system/*

Problems

  1. Cannot use external SdCard on android-4.1.x from Titanium Backup Tool.
    See Android-Storage-Permissions
  2. Cannot run su through adb shell 
    d:\personal\work\galaxyS-GT-I9000-xwjw1>adb shell
$ su
su: not found
    A: The device is not rooted.
  3. I get the message "Applicattion stopped unexpectedly. Please try again. Force close" for a lot of applications. A: The permissions on your /data partition are not ok. Or maybe something else.
  4. When I run heimdall print-pit I get the error "ERROR: Failed to access device. libusb error: -12" A: Use zdiag to replace the samsung/GadgetSerial drivers with libusb0 (v1.2.5.0 in my case) Cause: You have some drivers installed that conflicts with heimdel. Probably you installed them for Odin or where installed by Samsung Kies ... etc.

Device Specific

Samsung Galaxy S I9000

In this device the recovery image is the same as the kernel one. If you want to replace the Recovery console you need to:
heimdall flash --KERNEL philz_touch_6.07.9-galaxysmtd\boot.img

Clone this wiki locally