[Android Q&A, Help & Troubleshooting] tum.osx:
!!!!!!!!!! Caution rooting can be risk your devices. !!!!!!!!!!!

!!!!!!!!!! CAUTION ROOTING CAN BE RISK YOUR DEVICES. !!!!!!!!!!!

YOU MUST HAVE TO KNOW WHAT YOU DO. BEFORE YOU MAKE A THING.

obtain root privileges on the f-10d

Things Require

1. Root Kit

2. ADB Driver For F-10D

3. PC With android SDK

4. Little Knowledge with linux command line

Things to do

Right click on folded you save extract of root kit. that you download

(1) On command prompt put command "adb restore f-10d_2.ab" without "…"

Press OK certification will appear on the screen

(2) You must verify that

(3) after restore is finished. Put command

> adb shell

$ cd / data / data / com.android.settings / a /

$ ls -l-d

drwxrwxrwx system system a

⇒ a directory that exists and is world readable, writable to

$ ls -l

⇒ up to file00 ~ file99 directory exists

(4) Once removed file00 ~ file99

> adb shell

$ cd /data/data/com.android.settings/

$ rm -r a

(Please go but out ※ error)

(5) Make /data permissions to 777. Input command.

$ while:; do ln -s /data a/file99; done

On your screen should infinite run.While doing this, open new command line. Don't closed running windows.

Now input command in new windows

>adb restore f-10d_2.ab

Confirm on your f-10d to complete the restore

After you have finished, exit the old infinite running windows

(6) Check the permissions on the /data

> adb shell

$ ls -l-d /data

drwxrwxrwx system system data

(7) Execute the following command

> adb push mkdevsh /data/local.org/tmp/mkdevsh

> adb shell chmod 777 /data/local.org/tmp/mkdevsh

(8) On or Off Wifi, and then execute

> echo /data/local.org/tmp/mkdevsh>/sys/kernel/uevent_helper

> adb shell

$ ls -l /dev/sh

-rwsr-sr-x root root 151964 2012-08-06 19:34 sh

$ /Dev/sh

# ************ Tempolary insecure root shell ************

(9) Copy lsm_disabler.ko and f10dunlock to /data/local

>adb push f10dunlock /sdcard

>adb push lsm_disabler.ko /sdcard

>dab shell

# dd if=/mnt/sdcard/f10dunlock of=/data/local/f10dunlock

# dd if=/mnt/sdcard/lsm_disabler.ko of=/data/local/lsm_disabler.ko

(10) release LSM lock

********* "x" and "y" is option for f10dunlock

For x=0 if you're on F-10D Build number V16R45C

x=1 if you're ISW13D Device

x=2 if you're on F-10D Build number V18R46F

IF you can't insert module lsm_disabler.ko after execute f10dunlock "x" you can add option "y" at last one example f10dunlock 0 2 or f10dunlock 0 1 and then try to insert module lsm_disabler.ko **********

# cd /data/local

# chmod 777 f10dunlock

# chown root.root / data/local/f10dunlock

# /data/local/f10dunlock x y

/data/local/f10dunlock

fdaes = -1

open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext

fdaes2 = 3

use new F-10D address

# /data/local/f10dunlock 2

/data/local/f10dunlock 2

fdaes = -1

open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext

fdaes2 = 3

# ./f10dunlock

./f10dunlock

fdaes = -1

open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext

fdaes2 = 3

# lsmod

# mount-o rw, remount / system

mount-o rw, remount / system

# cd /system

cd /system

# chmod 777 / system

chmod 777 / system

# mkdir test

mkdir test

# ls-al

(11) Set su busybox

# sync; sync; sync

sync; sync; sync

# dd if=/mnt/sdcard/su of=/system/bin/su

dd if=/mnt/sdcard/su of=/system/bin/su

743 +1 records in

743 +1 records out

380532 bytes transferred in 0.079 secs (4816860 bytes / sec)

# chown root.shell /system/bin/su

chown root.shell /system/bin/su

# chmod 06755 /system/bin/su

chmod 06755 /system/bin/su

# sync; sync; sync

sync; sync; sync

# dd if=/mnt/sdcard/su of=/system/xbin/su

dd if=/mnt/sdcard/su of=/system/xbin/su

743 +1 records in

743 +1 records out

380532 bytes transferred in 0.034 secs (11192117 bytes / sec)

# chown root.shell /system/xbin/su

chown root.shell /system/xbin/su

# chmod 06755 /system/xbin/su

chmod 06755 /system/xbin/su

# sync; sync; sync

sync; sync; sync

# dd if = /data/local.org/tmp/busybox of=/system/xbin/busybox

dd if=/data/local.org/tmp/busybox of=/system/xbin/busybox

2099 +1 records in

2099 +1 records out

1075144 bytes transferred in 0.085 secs (12648752 bytes / sec)

# chown root.shell /system/xbin/busybox

chown root.shell /system/xbin/busybox

# chmod 04755 /system/xbin/busybox

chmod 04755 /system/xbin/busybox

# ls-al

ls-al

drwxr-xr-x root root 2012-09-01 03:31 app

drwxrwxrwx root shell 2012-09-01 23:59 bin

-rw-r - r - root root 4093 2012-09-01 03:31 build.prop

drwxr-xr-x root shell 2012-09-02 01:05 xbin

# cd /system/xbin

cd /system/xbin

# ls -al

ls -al

-rwxr-xr-x root shell 10028 2012-07-07 21:17 agent

-rwsr-xr-x root shell 1075144 2012-09-02 01:05 busybox

-rwxr-xr-x root shell 9780 2012-07-07 21:17 dbus-monitor

-rwxr-xr-x root shell 5708 2012-07-07 21:17 sdptest

-rwsr-sr-x root shell 380532 2012-09-02 01:03 su

#

(12) Set up SuperUser

Install from the market SuperSU etc..

k you must have permission to launch the app root, root authorization confirmation screen will appear if

Remark form me(yes, me not goroh_kun) : if you reboot your device. It's has re-lock /system. Even you have root access you can't remount /system to r/o until you re-execute f10dunlock. So you should think and plan by carefully that you want to move SuperSU.apk form /data/app to/system/app for more safer factory reset in future or not.

Thank you for the dear goroh_kun.