• 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.
Dammit!!!!!! I am so annoyed at this. I cant get this damn thing rooted. Ihave been at this for days and days and days and hours and hours and hours. I keep getting
Error: failed to get root. Is your firmware too new?

i have searched forum after forum and tried so many damn things. Nothing is working. I cant be the only one to have this happen. I know people are like - its so easy you cant screw it up - but when the software crashes that is not me screwing up a step. I found the site to change your radio baseband version but that site says you need to get root with unrevoked3 first. mother! if i could do that i wouldnt be there.

i wouldnt be so pissed if it were my phone, but this is my wife's phone. so if it goes belly up and keeps flashing all these damn UDI mismatch messages and starts having problems i will have to inherit a inc1 that is f'd up instead of my inc2 that is freshly rooted.

what can i do?

im sorry youre having trouble,and i wish i had an idea why it wasnt working for you. i assume your baseband is actually 2.15.10.07.07,wich is the official GB radio that lots of folks have rooted with unrevoked 3.22.

did you try redownloading 3.22? did its md5 sum match the one listed? a bad download could be giving you problems.

failing every thing else,you arent at a loss. you can give the directions in the 2nd post a shot,they will get you to the same end result, you just will not be able to make a backup prior to downgrading.

edit:
heres one other option for you. you can use the htc supertool,found here: http://forum.xda-developers.com/showthread.php?t=1343114

try option 1,if it fails,try option 2. as long as either 1 or 2 work,do 3. this will push the superuser app and binary into system/app/xbin and will give you root priveledges. you can try using rom manager to install clockwork,but it will prolly fail with an s-on phone.

what you can do,is download titanium and at least make a backup of all her user apps. you can then continue on with the downgrade at step 3 in the first post :)
 
Needless to say, I was a little despondent about the melt down, but then, in the midst of my preparations for hari kiri, it came to me. It is possible to synthesize excited bromide in an argon matrix. Yes, it's an excimer frozen in its excited state.


I will stand up and try again!
 
help needed. im trying to root my friends phone for him and cant seem to get it to work. it wont take downgrade im trying to install. ive went into hboot and put all the needed files in the proper places and it still wont take. i went into the command prompts and tried to do that route and it still wont work. i get so far with the command prompt for it to tell me "su permission denied" after the prompt changes to $. any and all help is much needed and appreciated.
 
help needed. im trying to root my friends phone for him and cant seem to get it to work. it wont take downgrade im trying to install. ive went into hboot and put all the needed files in the proper places and it still wont take. i went into the command prompts and tried to do that route and it still wont work. i get so far with the command prompt for it to tell me "su permission denied" after the prompt changes to $. any and all help is much needed and appreciated.
Are you rooted? In order for the commands to work,you need to be rooted via unrevoked 3.22(if following 1st post directions) or zergrush(2nd post directions)

Optionally,you can possibly use the HTC super tool in place of unrevoked 3.22.
 
yeah, it seems i am still in 2.3.4

i ran 3.22 on another computer. i cant tell you what i really did differently but i got it to run to the end. however the 1st time it made it all the way through i got a booloader error in windows - i didnt get the exact message before i clicked away (stupid me). I then had the superuser app on the phone, but it still said S-ON in the boot menu. i ran it again (still says S-ON) and i didnt get the bootloader message, but i did get this in the clockwork recovery menu:
error verifying extendedcommand
error processing ROM manager script

then i am stuck in ROm manager/or clockworkMod recovery - i cant tell which it is. if i click on any of the options in the menu (blue font with reboot system now, apply update from sd card, etc) it wont select anything and just goes to the screen that looks like the ROM manager icon. if i hit another button it goes back to the options menu in the blue font. so i have to pull the battery.

also when i loaded the windows hboot drivers i originally got it to use the driver "android bootloader interface" but then when the phone is reconeected it looks for another driver and loads the "android ADB interface" driver. and i cant stop it from choosing that. even if i uninstall the driver and try and reload it. I think this is part of the problem, but cant seem to get around it.
(again using windows xp)

oh and the phone has had the update 4.08.65.2 that it has been trying to install for weeks - and i have avoided it cause i dont know if i want to do that while i am rooting. do i? or do i want to do it after, or never?

getting closer, i guess

thanks for the help

going back and forth between this and two sick babies - dont know which is sicker, me and this phone root process or my two kids!
 
You won't have s-off until you complete the downgrade steps. everything else you are seeing is normal. Its supposed to use different drivers in hboot than it does when booted.

You press the trackball in clockwork to choose options not the power button.

Ignore the update message as it will just take you back to square one with this process. You are now successfully rooted but need to downgrade to get s-off and permanent root
 
just to add a lil more to what sdraw said,you may need to try and run a couple root-requiring apps(examples:root explorer,rom manager,titanium backup) and then go to settings/applications/manage apps/superuser and clear data before it will grant permissions to things and work properly. yes you are getting closer,indeed :)
 
oh and the phone has had the update 4.08.65.2 that it has been trying to install for weeks - and i have avoided it cause i dont know if i want to do that while i am rooting. do i? or do i want to do it after, or never?

oops,just noticed this... you will not be able to accept it now while running clockwork recovery. id suggest finishing the downgrade when youre able,become s-off,and then you can simply load a rom based on the newest OTA :)
 
no i am not rooted. your directions said i had to downgrade first before i could root i tried running the program from unrevoked and it said the firmware was too new
 
no i am not rooted. your directions said i had to downgrade first before i could root

pssst! step 2 is "root with unrevoked 3.22" ;)

i tried running the program from unrevoked and it said the firmware was too new

wich unrevoked did you run? 3.22 or 3.32?

i suggest you carefully re-read post 1. if you have trouble at any certain step,be as specific as you can about the trouble youre having at that step. watch carefully that the outputs to the adb commands match mine in the codebox at the bottom of post 1. if you have trouble,provide a copy of your command window as described at the top of box 1.

again,you can try gaining root with "htc supertool" i linked a couple posts up if unrevoked 3.22 wont work for you,and you dont want to try the zergrush method of post 2.

unfortunately,you need at least a temp root to do the adb commands neccessary to downgrade to s-offable froyo.
 
the weird thing for me is that I get into the clockwork boot menu, but i cant do anything there. i cant select any of the options. I just have to pull the battery and reboot. When the phone is connected to the pc, what am i supposed to see in the clockworkmod folder? i only see recovery.log

I also cant re-format my card as fat32. Going to go through this some more.

EDIT: did get the card reformatted, had to have the card in the phone and the phone connected as disk drive and then right click and reformat. now that i think i did read that somewhere. sorry, been working this for a week and a half and i have read so much i forget what is up and what is down.

OK - After running 3.22 on another machine i think it was 3 times I finally got unrevoked to complete without giving me an error. I did get the bootloader error one time through but i had the superuser app after that. At some point after following the instructions correctly I did get things jacked up - I had the clockwork image on the internal storage, and the external storage, and i had the PB31IMG zip file unzipped on the internal storage. So at this point when i got the super user app I formatted the SD card put the correct PB31IMG zip file on there (zipped) and removed everything fro the internal card except the clockwork mod folder (and inside that was the clockwork image) then i ran unrevoked 3.22 that 3rd time and everything finished without errors. Then i was able to run the next step with the PB31IMG zip file, and after that run the shell commands and downgrade with adb. Then i was able to run unrevoked forever 3.32 and that went smooth. I am now S-OFF, Rooted and have a backup of my current ROM.
I have to admit I still dont fully know what I was doing wrong (or really what I am doing for that matter). I think the key for me was kinda wiping all the info off and starting over on another computer. I really feel I followed the process correctly the first bunch of failed attempts but I must have done something wrong. I would say to anybody having problems STICK WITH IT. Go back re-read (and re-read), wipe the device, start again.
Super thanks to Scotty and the other folks on here who are unbelievably super helpful. I am so thankful.
 
Hi there,

I have a Droid Incredible, and I was following the procedure in the OP until I used the unrEVOked program. At first, it seemed to hang on "Waiting for device" so I unplugged the phone and reconnected it.. then it proceeded to use the default ClockworkMod img before I could tell it to use the custom img... after this, my DInc rebooted and sat at the boot screen (not HBOOT, but the one that says Droid Incredible).

I have tried a number of things since then, turning the phone on and off several times, waiting it out, popping out the battery etc. I tried to HBOOT into recovery, but I just get a black screen with white bars on either side.

Here's the thing: All of the troubleshooting I have seen here talks about flashing RUU's onto the phone through HBOOT Recovery.. but that doesn't seem to do anything. I managed to push the PB31IMG.zip into my /sdcard/ through mini-adb but that continues to be unrecognized by HBOOT. (I have rebooted at least a dozen times this way)

Other suggestions I have seen here involve being able to access settings that I can't find through HBOOT. They seem to be available only IF your phone will actually boot up. Is there anything more I can do??

Is there some step in all of this that I am missing?

Also, my HBOOT says 0.92.0000 while all I see here is .97 & .98 - is this going to be a problem?

Thanks.

p.s. I'm really sorry if this question has been sufficiently answered here already.. I got through 5 pages of this topic, along with several other Google searches and other forums, with no results and my patience is wearing out.

EDIT: I also wanted to add, that before this started I had USB Debugging checked, and my USB connection was Charge Only. I can't seem to change anything about this, and I can't access my sdcard contents as far as I can tell.
 
Same reply as on XDA:
Hi, happy NY. As a somewhat of a present - first POST in 2012 :)

Thanks for the topic, this is usefull as i had lost all hope when I found out with s-on i will not be able to install any custom roms :(

Still im not all that sucessfull, faced one general issue and didnt see them referenced in replys to your topic:
my bootloader was searching for PB99IMG.zip instead of PB31IMG.zip, but simply renaming it didnt do. When it was checking the RUU, it said "model ID incorrect update failed!" there are a couple of topic on this, but they weretn helpful.
Would you know what's this about?

My HTC Desire has hboot ver prior to 1.06, something like 0.93-0.92 i think. If this is relevant...

zergRoot wouldnt help as it still relies on using the same RUU, right? :(

*Update

Actually as the thread is for Incredible... I think I should use some other RUU for Desire. Would you be able to point ot it? Make sense MODEL ID of Desire doesnt match the Incredible one :)
 
the weird thing for me is that I get into the clockwork boot menu, but i cant do anything there. i cant select any of the options. I just have to pull the battery and reboot. When the phone is connected to the pc, what am i supposed to see in the clockworkmod folder? i only see recovery.log

I also cant re-format my card as fat32. Going to go through this some more.

edit: did get the card reformatted, had to have the card in the phone and the phone connected as disk drive and then right click and reformat. now that i think i did read that somewhere. sorry, been working this for a week and a half and i have read so much i forget what is up and what is down.
You press the trackball, NOT the power button to select the options in clockwork:cool:
Hi there,

I have a Droid Incredible, and I was following the procedure in the OP until I used the unrEVOked program. At first, it seemed to hang on "Waiting for device" so I unplugged the phone and reconnected it.. then it proceeded to use the default ClockworkMod img before I could tell it to use the custom img... after this, my DInc rebooted and sat at the boot screen (not HBOOT, but the one that says Droid Incredible).

I have tried a number of things since then, turning the phone on and off several times, waiting it out, popping out the battery etc. I tried to HBOOT into recovery, but I just get a black screen with white bars on either side.

Here's the thing: All of the troubleshooting I have seen here talks about flashing RUU's onto the phone through HBOOT Recovery.. but that doesn't seem to do anything. I managed to push the PB31IMG.zip into my /sdcard/ through mini-adb but that continues to be unrecognized by HBOOT. (I have rebooted at least a dozen times this way)

Other suggestions I have seen here involve being able to access settings that I can't find through HBOOT. They seem to be available only IF your phone will actually boot up. Is there anything more I can do??

Is there some step in all of this that I am missing?

Also, my HBOOT says 0.92.0000 while all I see here is .97 & .98 - is this going to be a problem?

Thanks.

p.s. I'm really sorry if this question has been sufficiently answered here already.. I got through 5 pages of this topic, along with several other Google searches and other forums, with no results and my patience is wearing out.

EDIT: I also wanted to add, that before this started I had USB Debugging checked, and my USB connection was Charge Only. I can't seem to change anything about this, and I can't access my sdcard contents as far as I can tell.
Yes, you missed the first and second step, it tells you how to replace the recovery with a functional one. You will have to start over. Read EVERY SINGLE step very carefully. You choose the option to replace the recovery before you plug the phone in.:) And your sd card has to be formatted to FAT32 or this guide will not work.

Edit: you don't really have to start over unless you would like a make a backup before proceeding with the downgrade, but again, that is also covered in the first post. :cool:
Same reply as on XDA:
Hi, happy NY. As a somewhat of a present - first POST in 2012 :)

Thanks for the topic, this is usefull as i had lost all hope when I found out with s-on i will not be able to install any custom roms :(

Still im not all that sucessfull, faced one general issue and didnt see them referenced in replys to your topic:
my bootloader was searching for PB99IMG.zip instead of PB31IMG.zip, but simply renaming it didnt do. When it was checking the RUU, it said "model ID incorrect update failed!" there are a couple of topic on this, but they weretn helpful.
Would you know what's this about?

My HTC Desire has hboot ver prior to 1.06, something like 0.93-0.92 i think. If this is relevant...

zergRoot wouldnt help as it still relies on using the same RUU, right? :(

*Update

Actually as the thread is for Incredible... I think I should use some other RUU for Desire. Would you be able to point ot it? Make sense MODEL ID of Desire doesnt match the Incredible one :)

This guide is only for the original HTC droid incredible, trying to put any of these files onto your phone could brick it.:eek:

http://androidforums.com/desire-all...-all-about-rooting-updated-11-nov-2011-a.html
 
Hi there,

I have a Droid Incredible, and I was following the procedure in the OP until I used the unrEVOked program. At first, it seemed to hang on "Waiting for device" so I unplugged the phone and reconnected it.. then it proceeded to use the default ClockworkMod img before I could tell it to use the custom img... after this, my DInc rebooted and sat at the boot screen (not HBOOT, but the one that says Droid Incredible).

I have tried a number of things since then, turning the phone on and off several times, waiting it out, popping out the battery etc. I tried to HBOOT into recovery, but I just get a black screen with white bars on either side.

Here's the thing: All of the troubleshooting I have seen here talks about flashing RUU's onto the phone through HBOOT Recovery.. but that doesn't seem to do anything. I managed to push the PB31IMG.zip into my /sdcard/ through mini-adb but that continues to be unrecognized by HBOOT. (I have rebooted at least a dozen times this way)

Other suggestions I have seen here involve being able to access settings that I can't find through HBOOT. They seem to be available only IF your phone will actually boot up. Is there anything more I can do??

Is there some step in all of this that I am missing?

Also, my HBOOT says 0.92.0000 while all I see here is .97 & .98 - is this going to be a problem?

Thanks.

p.s. I'm really sorry if this question has been sufficiently answered here already.. I got through 5 pages of this topic, along with several other Google searches and other forums, with no results and my patience is wearing out.

EDIT: I also wanted to add, that before this started I had USB Debugging checked, and my USB connection was Charge Only. I can't seem to change anything about this, and I can't access my sdcard contents as far as I can tell.
.92 is the correct hboot for the droid incredible. .97 and .98 were referencing the inc2.

*since you have a recovery(sort of) and your phone wont boot,you have a couple options:

1)enter recovery thru hboot. plug in your phone and try "adb devices" if you get "<serial number> recovery" than you can prolly simply enter the adb commands in recovery then flash the downgrade 2.2 PB31IMG. you will need to obtain a sd card reader to move files to and from your sd card since you cant boot to the OS,and you cant select "usb mount" in recovery. ill run thru it in a sec and make sure it works.

edit: pushing the commands will work fine in recovery. you will just need to adb shell mount /data after checking the md5s,and before the rest of the commands. heres what it will look like(red are my inputs):

Code:
c:\mini-adb_inc>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    recovery


c:\mini-adb_inc>[COLOR="red"]md5sums mtd0.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
mtd0.img                                       34307be744275f1db1dd16af04c37839

c:\mini-adb_inc>[COLOR="red"]md5sums flash_image[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
flash_image                                    0098a7dd6600b55fac34fc6645be5d7a
c:\mini-adb_inc>[COLOR="red"]adb shell mount /data[/COLOR]

c:\mini-adb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1485 KB/s (76044 bytes in 0.050s)

c:\mini-adb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1939 KB/s (655360 bytes in 0.330s)

c:\mini-adb_inc>[COLOR="red"]adb shell[/COLOR]
/ # [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
/data/local # [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
/data/local # [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
/data/local #[COLOR="red"] ./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
/data/local # [COLOR="red"]exit[/COLOR]
exit

at this point,just pull the battery. put the downgrade PB31IMG on your sd card via a card reader,pop it back in,and power on into hboot. assuming properly named file,properly formatted FAT32 sd card,and correct steps above,it should flash the downgrade. if it doesnt boot after flashing the donwgrade,flash it(the downgrade) again. a second flash has been neccessary for some folks. you wont need to redo any adb commands,simply flash the downgrade a 2nd time.


2)start over as sdraw suggested. to get back to a working phone,youll need to reflash a stock GB image. you can find it here: Stock Images | PvilleComp's

you can flash the PB31IMG by putting it on your sd card via a card reader and powering on into hboot.

you can run the RUU .exe utility by simply starting the utility with the phone in fastboot. get to fastboot by powering on into hboot,then use power to select "fastboot" in the hboot menu.

at this point,im afraid to say,you are hosed on making a backup. either option 1 or 2 will wipe your data. unfortunately,you arent the first to have ended up with a non booting phone after running 3.22,but rest assured its not permanently bricked. :) one of the 2 options will get you up and running :)


My HTC Desire has hboot ver prior to 1.06, something like 0.93-0.92 i think. If this is relevant...
in addition to the link that sdraw provided,you can use revolutionary: public:revolutionary [RootWiki] it supports both the 1.06 hboot of the cdma desire(bravoc) and the hboot .93 and 1.02 of the gsm desire(bravo). you can verify your hboot by powering off,then hold the power and volume down buttons until the hboot screen(white with colored letters) pops up.
 
Fantastic guide Scotty (and all those involved). I have been contemplating rooting my phone for a year and final did last week (I wanted to confirm that everything worked okay and that I didn't have any issues prior to posting). This guide is well written and thorough. It took me a few hours, mainly because I'm new to this and was very methodical...i.e. backing up all my files and rereading steps multiple times. Also, I had to do some minor troubleshooting but I achieved root and have S-Off. I thank you and all those that have contributed to this thread. I feel like I have a new phone now and also feel like I have complete control of my phone.

Cheers
 
Sorry for this delayed response, but I got it working! Root access AND S-OFF!

thank you scotty, and sdrawkcab, for your help!

I must say, this forum.. this topic in particular, and the helpful users maintaining it, are a testament to the power of the open internet ;D it's not just the free sharing of information, but the positive attitudes and encouragement of those providing it, that really make life easier for others

PIPA/SOPA can suck it! lol thanks again guys!
 
is Unrevoked 3.22 necessary? beacause 3.32 is the latest now.

.....I simply can't find 3.22 for linux.....
---------------------------- 5 minutes later--------------------------------

Ohhh.... wait... here it is - 3.22 one for linux:
http://downloads.unrevoked.com/recovery/3.22/Reflash.tar.gz

yes. 3.32 will not work on GB. you need 3.22,htc supertool,or manually run zergrush. then you need to downgrade in order to run 3.32 and achieve s-off.
 
Sorry for this delayed response, but I got it working! Root access AND S-OFF!

thank you scotty, and sdrawkcab, for your help!

I must say, this forum.. this topic in particular, and the helpful users maintaining it, are a testament to the power of the open internet ;D it's not just the free sharing of information, but the positive attitudes and encouragement of those providing it, that really make life easier for others

PIPA/SOPA can suck it! lol thanks again guys!

awsome. glad you got it :cool:
 
Just wanted to report on successfull root / s-off / Cyanogen install of 2.3.34 droid Incredible.

I did everything from Fedora 16 and used regular google-provided android-sdk tools instead of mini-adb.zip binaries. Also - in my droid UP button doesn't work - so that was kind of a b*tch since I couldn't select YES - install PB31IMG.zip, so I had to use fastboot commands from official SDK to initiate downgrade:

fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PB31IMG.zip
fastboot flash zip PB31IMG.zip
fastboot reboot


but there - everything worked wery well. Thanks guys.
 
that is actually how i always flash PxxxIMG files now. its much faster and easier,i think,as you dont actually transfer it to your sd card. for others interested in doing it this way,just put the file into the mini-adb folder(or the file containing adb and fastboot if using the sdk). also,the file can be named anything. you just have to "fastboot flash zip <exact filename>.zip" for example you could "fastboot flash zip PB31IMG-2.2-downgrade.zip" and it would flash just fine.

i thot about converting all my guides to this as it elimates alot of factors from the equation that seem to trip people up a lil. initially i thot fewer adb commands would be easier,but after all the feedback,flashing the RUU from fastboot may have been a better idea.

doing it this way also offers the benefit of seing exactly where it fails,if it does :eek:

for those seeing this post,the fastboot flash zip command is entered twice,as the way some RUUs are flashed,it will do the hboot and radio first,then give you a "please reflush immediately" error,and flash the rest. flashing in hboot,this happens twice without interection from the user.
 
I've read through all 18 pages and don't see my problem. I was able to downgrade to 2.2, root and have s-off. Now I cannot enable wi-fi. It just says wi-fi error. I don't have service yet so I can't get apps. Any ideas?

Wi-fi worked fine prior to the rooting process.
 
Status
Not open for further replies.
Back
Top Bottom