[ROOT+BB+CWM] ICS and non rootable GB build

Search This thread

puppet13th

Senior Member
I have create rooting method based on DooMLoRD method [ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS} but have different approach.

special thanks to DooMLoRD

REQUIRED ROOTED DEVICE prior to update

How this method work?
1. create file /data/local.prop contain "ro.kernel.qemu=1" to enable root shell (this step must be done on ROOTED DEVICE)
2. update using Update Service/PC Companion/Flashtool without Factory Reset
3. after device updated,we should gained root shell that we use to push su binary and superuser.apk

Download : Xperia-ROOT.rev3.zip

Download : Xperia-ROOT.rev4.zip
Including autoinstall Stericson Busybox 1.20.1 and nAa CWM Recovery 5.0.2.7

extract Xperia-ROOT.rev3.zip to any folder,so you got something like this
attachment.php


Another great tutorial made by DragonClawsAreSharp can be found at
[Tutorial]Root.Xperia 4.0.4 ROM | 4.1.B.0.431


STEP :
1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
2. power off device and update your device WITHOUT FACTORY RESET

Update Service
select Update (recommended)
attachment.php


Flashtool
UNMARK WIPE DATA
attachment.php


after your device updated
on 1st boot your device will reboot once
on 2nd boot it will boot normally
if you got bootloop run 02-push-root-files.cmd right away
until it finished wait for 1 or 2 reboot
if you still got bootloop you need to reflash rootable firmware(zergrush method) then try again


3. run 02-push-root-files.cmd to push su binary and superuser.apk
4. your device will automatically reboot
5. enjoy your new rooted firmware :)

this method tested on :
1. Arc S ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4
2. Ray ROOTED ICS 4.0.3 updated to ICS 4.0.4
3. Active ROOTED GB 4.0.2.A.0.42 updated to GB 4.0.2.A.0.62

tested by user:
1. SK17i ROOTED GB 4.0.2.A.0.58 updated to GB 4.0.2.A.0.62 by Bolussimo
2. Rooted SK17i FW 4.1.B.0.431 by draco_ag
3. LWW WT19i Rooted GB 4.0.2.A.0.58 updated to ICS 4.0.4 by alness1213
4. SK17i ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4 by DragonClawsAreSharp
 

Attachments

  • 2012-06-06_21-16-42_000096_Xperia-ROOT.jpg
    2012-06-06_21-16-42_000096_Xperia-ROOT.jpg
    36.6 KB · Views: 139,941
Last edited:

puppet13th

Senior Member
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!

Nice piece of work brov...

Yup,that's it bro.

As we know zergrush exploit doesn't works on FW starting .62 and above.

we just need any firmware that can be rooted using zergrush method then use this tool before and after upgrade to gain updated and rooted firmware.

I have tested this method on my Xperia Active running on ROOTED FW .42(rooted using zergrush method) use this tool before and after update to gain rooted FW .62
When doing update you MUST NOT do factory reset.
 

puppet13th

Senior Member
A little question...

Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???

Or make another /data/local.prop???

when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"

you need to run 01-local-prop.cmd just before you update your device.
 
  • Like
Reactions: gaga0101

puppet13th

Senior Member
yes...I have done all the step...but got bootloop...

can you tell me what have you done step by step?

edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop

from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop

builtin rm command syntax on GB build :
Code:
rm [-rR] <target>

workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
 
Last edited:

Till-Kruspe

Senior Member
Mar 19, 2012
2,821
3,454
Redmi K20 / Xiaomi Mi 9T
can you tell me what have you done step by step?

edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop

from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop

builtin rm command syntax on GB build :
Code:
rm [-rR] <target>

workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop

my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...

First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"

Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...

what to do now...this is my only phone...please help me... :(
 

puppet13th

Senior Member
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...

First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"

Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...

what to do now...this is my only phone...please help me... :(

if you have FW. 58 or erlier ftf flash it with flashtool DO NOT UNMARK wipe data.
then root it using zergrush method.

try again from step 1

edit :
it's look like you got bootloop because your data partition was full.


now i got bootloop downgraded to fw. 42 without factory reset.i only got 50mb free before flashing.
my rom was odexed before,so 50mb was not enought to hold dalvik-cache from framework and system app
 
Last edited:

puppet13th

Senior Member
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...

First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"

Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...

what to do now...this is my only phone...please help me... :(

now i hit the bull eye

/data/local.prop : ro.kernel.qemu=1 --> cause system instability that cause bootloop if data partition was full
download Xperia-ROOT.rev3.zip from 1st post and run 02-push-root-files.cmd it will wait for device before reboot(bootloop).after /data/local.prop(ro.kernel.qemu=1) gone,it will boot normally

when it reach home screen you need to make more free space on /data partition
 
Last edited:

puppet13th

Senior Member
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).

Or there can be some other reasons?

Thanks,
Rick

Sent from my SK17i using XDA

it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.

if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
 

DragonClawsAreSharp

Senior Member
Nov 1, 2011
587
1,129
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.

if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown

Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?

Sent from my SK17i using XDA
 

puppet13th

Senior Member
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?

Sent from my SK17i using XDA

02-push-root-files.cmd doesn't run on su access because of /data/local.prop (ro.kernel.qemu=1)
when ro.kernel.qemu=1 in effect we automatically got root shell

so when we start adb shell we got # instead of $
# = root user
$ = normal user
 

Top Liked Posts

  • There are no posts matching your filters.
  • 151
    I have create rooting method based on DooMLoRD method [ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS} but have different approach.

    special thanks to DooMLoRD

    REQUIRED ROOTED DEVICE prior to update

    How this method work?
    1. create file /data/local.prop contain "ro.kernel.qemu=1" to enable root shell (this step must be done on ROOTED DEVICE)
    2. update using Update Service/PC Companion/Flashtool without Factory Reset
    3. after device updated,we should gained root shell that we use to push su binary and superuser.apk

    Download : Xperia-ROOT.rev3.zip

    Download : Xperia-ROOT.rev4.zip
    Including autoinstall Stericson Busybox 1.20.1 and nAa CWM Recovery 5.0.2.7

    extract Xperia-ROOT.rev3.zip to any folder,so you got something like this
    attachment.php


    Another great tutorial made by DragonClawsAreSharp can be found at
    [Tutorial]Root.Xperia 4.0.4 ROM | 4.1.B.0.431


    STEP :
    1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
    2. power off device and update your device WITHOUT FACTORY RESET

    Update Service
    select Update (recommended)
    attachment.php


    Flashtool
    UNMARK WIPE DATA
    attachment.php


    after your device updated
    on 1st boot your device will reboot once
    on 2nd boot it will boot normally
    if you got bootloop run 02-push-root-files.cmd right away
    until it finished wait for 1 or 2 reboot
    if you still got bootloop you need to reflash rootable firmware(zergrush method) then try again


    3. run 02-push-root-files.cmd to push su binary and superuser.apk
    4. your device will automatically reboot
    5. enjoy your new rooted firmware :)

    this method tested on :
    1. Arc S ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4
    2. Ray ROOTED ICS 4.0.3 updated to ICS 4.0.4
    3. Active ROOTED GB 4.0.2.A.0.42 updated to GB 4.0.2.A.0.62

    tested by user:
    1. SK17i ROOTED GB 4.0.2.A.0.58 updated to GB 4.0.2.A.0.62 by Bolussimo
    2. Rooted SK17i FW 4.1.B.0.431 by draco_ag
    3. LWW WT19i Rooted GB 4.0.2.A.0.58 updated to ICS 4.0.4 by alness1213
    4. SK17i ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4 by DragonClawsAreSharp
    3
    Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!

    Nice piece of work brov...

    Yup,that's it bro.

    As we know zergrush exploit doesn't works on FW starting .62 and above.

    we just need any firmware that can be rooted using zergrush method then use this tool before and after upgrade to gain updated and rooted firmware.

    I have tested this method on my Xperia Active running on ROOTED FW .42(rooted using zergrush method) use this tool before and after update to gain rooted FW .62
    When doing update you MUST NOT do factory reset.
    3
    Uploaded Xperia-ROOT.rev4.zip --> check 1st post :D
    2
    Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!

    Nice piece of work brov...
    2
    :D:D:D:D:D:D:D

    WWWOOOOOOOOOOOO!!!!!...I have done it....rooted FW .62....

    Thank you so much!!!...how may I repay for your kindness... :)