• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How To] Root 2.3.4/downgrade and Get S-off

Status
Not open for further replies.
come to find out I had a slcd incredible. I formatted an extra sd card and placed the gingerbread Rom on it and manually loaded it through bootloader (getting me back to ota gb). Followed the new clockworkmod instructions and it worked like a champ after running unrevoked twice. Now I'm running cm 7.1 thanks to everyone's help. Thanks for all this Scotty!
 
I'm also still amazed that this method works, VERY curious as to how and why it does. Has anyone tweeted the unrevoked team to take a look at it? (I don't have a twitter account but half tempted to sign up for one just to ask)
 
I must say that this thread has become quite epic in short order.

GOOD WORK
Indeed! I have been a bit afraid to go full monty with this root thing, but followed the instructions to downgrade and root 2.3.4, and i am back to running 2.2 with better battery life, trackball will unlock again, and i am planning on running the latest unrevoked tonight to root 2.2, and start having some fun. The 2.3.4 OTA was not worth it! It was more of a downgrade, than an upgrade! Too many things not working right!


Thanks go to all y'all!
 
I'm also still amazed that this method works, VERY curious as to how and why it does. Has anyone tweeted the unrevoked team to take a look at it? (I don't have a twitter account but half tempted to sign up for one just to ask)

I tweeted koush, haven't heard back.
 
Well here we go, new root method that supposedly works on ALL 2.2 and 2.3 devices (from the unrevoked/alpharev team):

Revolutionary - zergRush local root 2.2/2.3 - xda-developers

thanks for the link! i actually knew this was coming,they tweeted the source code the other day,but without much info along with it. like iowa said,it looks like its a temp root. good for rewriting misc images,but not so much for using root apps,or adding a recovery. i should be able to use it roll my spare inc back to froyo and see if its still junk :D

since the "experimental method" seems to be working,ill go ahead and make that part of the directions :cool:
 
come to find out I had a slcd incredible. I formatted an extra sd card and placed the gingerbread Rom on it and manually loaded it through bootloader (getting me back to ota gb). Followed the new clockworkmod instructions and it worked like a champ after running unrevoked twice. Now I'm running cm 7.1 thanks to everyone's help. Thanks for all this Scotty!

thanks for reporting back,i was wondering how it went for you.im glad the PB31IMG you ran didnt turn your phone into junk like mine :eek: happen to have a link where you downloaded it from? :)
 
thanks for the link! i actually knew this was coming,they tweeted the source code the other day,but without much info along with it. like iowa said,it looks like its a temp root. good for rewriting misc images,but not so much for using root apps,or adding a recovery. i should be able to use it roll my spare inc back to froyo and see if its still junk :D

since the "experimental method" seems to be working,ill go ahead and make that part of the directions :cool:


Yeah, I saw that the other day too, wish I had more time to learn how to read the source code and figure out what it is doing when it runs... Judging by the output it seems like some type of overload, similar to a DoS attack maybe...

Seems some users only are reporting root in the adb shell which you can still push superuser, busybox etc through (or rewrite the misc.img like you mentioned).
 
well,it works :D

used it to get the # so i could rewrite the misc image,and roll the junk inc back to froyo. its flashing now ill know if it truly is junk or just a bad flash of some sort :eek:

its nice that the older unrevoked works. it gives users the options to download titanium,and make nandroids,not to mention just stay on rooted GB if thats all they really want.

but as ive just discovered,zergRush works and wed have had our downgrade anyway.

heres what the front page guide would look like if 3.22 didnt work,those guys have a sense of humor for sure :D
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT117HJ00242    device


C:\Users\Scott>cd c:\mini-adb_inc

c:\mini-adb_inc>adb push zergRush /data/local/
1035 KB/s (21215 bytes in 0.020s)

c:\mini-adb_inc>adb shell
$  chmod 755 /data/local/zergRush
 chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25749 0xafd395f7
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...

[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!

c:\mini-adb_inc>adb push flash_image /data/local/
1280 KB/s (76044 bytes in 0.058s)

c:\mini-adb_inc>adb push mtd0.img /sdcard/
1545 KB/s (655360 bytes in 0.414s)

c:\mini-adb_inc>adb shell
# cd /data/local
cd /data/local
# chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
# cd /data/local
cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
# exit
exit

c:\mini-adb_inc>adb reboot bootloader

c:\mini-adb_inc>
 
Used Unrevoked 3.22 with clockwork 5.0.2.0 on an SLCD. Worked perfectly. Thanks for the guide.

EDIT: Oh, also, once Unrevoked reached "done," it left me in ClockworkMod, and there was some text complaining about some ROM Manager thing, which I figure is because the phone didn't have ROM Manager at the time? I just rebooted, checked for root, then went back to recovery and made a backup.

(My personal device is a G2x where this stuff is much simpler; I'm doing this for a friend and so I'm new to all this Unrevoked stuff.)
 
awsome! makes me happy its working for everybody without much issue. :cool:

i think later today,ill add to the second post a method that uses the new zergRush tool linked above,for the folks that dont care about a backup,or for some reason(like me) the old unrevoked wouldnt worked. i think the zergRush should work for everyone.
 
I rooted my 2.3.4 incredible a couple of days ago and I am now enjoying CM7 on it, thanks to the people who took the time to get it all to work.

I followed the instructions and they worked to a tee, had some issues with flashing google apps which was cleared up with a wipe of the cache on the phone. There was another issue with flashing the ROM using the ROM manager, it kept getting permissions errors; I was able to do it manually through the recovery, and later fixed the issue by running the fix permissions button on the ROM manager, I was then able to flash directly from the program.

Thanks for your help
 
So I was sitting here this morning sipping my coffee and I had a major head slap. Now that we know both screen types work (if using the alternate recovery.img method), I think we can avoid all the downgrade stuff. Once you are rooted and have a working recovery, just download the "s-off" file and apply it like a rom in recovery:

http://unrevoked.com/rootwiki/doku.php/public/forever

The file is located under the "Installation Instructions" section in that link.

It says to rename it update.zip but you do not have to do this. Leave it named as is, place the zip on the SD card and load it via Clockwork:

-install zip from sd card option
-choose zip from sd card option

navigate to the unrevoked forever s-off zip and load it. If this works, it should simplify the process a great deal.
 
So I was sitting here this morning sipping my coffee and I had a major head slap. Now that we know both screen types work (if using the alternate recovery.img method), I think we can avoid all the downgrade stuff. Once you are rooted and have a working recovery, just download the "s-off" file and apply it like a rom in recovery:

http://unrevoked.com/rootwiki/doku.php/public/forever

The file is located under the "Installation Instructions" section in that link.

It says to rename it update.zip but you do not have to do this. Leave it named as is, place the zip on the SD card and load it via Clockwork:

-install zip from sd card option
-choose zip from sd card option

navigate to the unrevoked forever s-off zip and load it. If this works, it should simplify the process a great deal.


Great idea! One question, isn't it radio specific and still require the user to swap to the froyo radio 7.28 I think, then the radio of their choice?
 
But has anyone tried it yet? To my knowledge this is the first time anybody's had SU on Gingerbread for the Inc. Although on second thought, maybe it would be dangerous to try idk.

Edit:
Ok, bad idea. You guys are right. Back to drinking coffee for me lol.
 
Status
Not open for further replies.
Back
Top Bottom