on sony we can get .2.55 rooted if we pre-root (sys) and flash zip with CWM
then i just needed 2 flash kernel and baseband from .2.55
should be possible with T also
mine is bootlocked and rooted xperia s .2.55
im finishing some testing still but soon will post the zip
Also it would be nice to see a new exploit from another talented dev?!
Regards
This will work if you install a kind of recovery with a old rom then do your steps, its what i am telling for longer now. But as i said, you would need to root a "eariler" vulnerable rom before, because without this you cannot flash any clockworkmod and so no cwm-zip Ofc it is easy to root 2.55 this way, and also some people already doing it.
BTW: you dont need any modded sys for it. my assumption is that it may be more easy, try this:
Flash a "older" Rom which can be rooted, then when you have root copy the su binary to : /data/local/tmp/su
chmod 06755 /data/local/tmp/su
After that flash your "new" rom without wiping any data.
After that open adb shell and execute
./data/local/tmp/su
-> you will have root shell, now copy su and Superuser to correct place and done, this can also be automated, even with flashing and all, since flashtool has cmdline interface which enables you to flash automatic.
Regards
Can someone pls reupload the Root_with_Restore_by_Bin4ry_v17 to a different site?
I can't download from ul.to because of exceeded download.
I've waited now for 3 hours but I still can't download .
Thnx in advance
This will work if you install a kind of recovery with a old rom then do your steps, its what i am telling for longer now. But as i said, you would need to root a "eariler" vulnerable rom before, because without this you cannot flash any clockworkmod and so no cwm-zip Ofc it is easy to root 2.55 this way, and also some people already doing it.
BTW: you dont need any modded sys for it. my assumption is that it may be more easy, try this:
Flash a "older" Rom which can be rooted, then when you have root copy the su binary to : /data/local/tmp/su
chmod 06755 /data/local/tmp/su
After that flash your "new" rom without wiping any data.
After that open adb shell and execute
./data/local/tmp/su
-> you will have root shell, now copy su and Superuser to correct place and done, this can also be automated, even with flashing and all, since flashtool has cmdline interface which enables you to flash automatic.
Regards
yes master... now made it all into a CWM flashble zip...
anyway without ur inicial exploit nothing would be possible...
so my great thanks 2 u
cheers
Great! Another dev to help people with Locked bootloader
When you post your method more clearly, I do it immediatly
Thanks for your help
Regards
trying to root a boost hydro. it appears to work. the runme.bat goes through its stuff and says success but I don't think its rooted.
SuperSu is installed but busybox won't install for lack of root and root checker hangs saying system appears to be running very slow and won't get past that.
suggestions?
Confirmed working on a Canadian LG Optimus G (LG-E973) [Bell] using v15 of the toolkit.
Android: v4.0.4
Baseband: APQ8064/MDM9x15M
Kernel: 3.0.21
Build: IMM76L
Software: E97310f
FCC ID: ZNFE973
Industry Canada #: 2703C-E973
Video showing the toolkit on:
- Xperia S
- Xperia Tablet S
- LG Optimus G (E973)
First, thanks for developing this script!
Several users reported back in Sept/Oct) in this thread that v.3 of this script will root the kyocera rise. Question: Should I stick to v.3 or should I use the most recent version? -- I assume the most recent script will install a more up-to-date superuser script, for example.
THANKS!
Not working on a Stock Xperia S... doesnt ask to restore... just reboots... and fails to chmod
$ dd if=fakebackup.ab bs=1 skip=24 | openssl zlib -d >fakebackup.tar
$ tar tvf fakebackup.tar
-rw-rw-rw- user/user 2093 2012-08-02 03:21 apps/com.android.settings/_manifest
drwxr-xr-x user/user 0 2012-07-12 16:55 apps/com.android.settings/r/
drwxrwxrwx user/user 0 2012-08-02 22:23 apps/com.android.settings/r/a/
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/[B][COLOR="Red"]file44[/COLOR][/B]
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file50
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file71
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file72
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file25
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file49
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file61
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file34
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file05
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file78
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file33
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file39
-rw-r--r-- user/user 524288 2012-08-02 22:22 apps/com.android.settings/r/a/file70
...