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

Root [how to]downgrade and root ICS

Well things are not exactly going to plan... I can't get into the phone to turn on usb-debugging. When I go into hboot, and then into restore, clockworkmod is gone but a very small 4 or 5 item menu has a title like android recover. On that menu, there is a line item to "apply update from sdcard". On the sdcard I have the RUU above as a zip, and the SetMainVer zip. And a few other zips I've tried re: SU etc. I'm trying to run the RUU and I get the message below. So I back up and try to run the SetMainVer, and I get the same message for it. Since I cannnot get into usb-debugging, I'm stymied. Any suggestions? By the way, I'm not opposed to starting all over from the beginning, cut without being able to get into the phone to put it in usb-debugging, I don't know how to get back to the beginning.

finding update package
opening update package
verifying update package
e: signature verification failed
installation aborted
 
OK,I'm a lil confused... The prior post said you were reloading 2.11.605.5... Was that unsuccessful?

From the above,sounds like you have overwritten cw with the stock recovery,which indicates the ruu flash was successful...

At any rate,you cannot use the stock recovery to install ruus or custom roms,only official,signed by HTC files.

If you still need to run an ruu,you'll have to run it from fastboot and the cmd window as above,or allow hboot to install it by renaming to PG05IMG,place on sd card,then boot to hboot.

USB debug is unnecessary at this point. Its only needed to use adb in the booted os. Not for using fastboot :)
 
Thanks for your input. I've been at work until now (1pm PST). The earlier attempt to install the RUU was unsuccessful in that the phone hung at booting up. I didn't know usb-debugging wasn't necessary for fastboot. When fastboot didn't report seeing the device, I thought it was like adb and needed the usb-debugging on. I'll recheck my RUU download with MD5, it was right before but maybe its gotten bad somehow transferring it around my computer folders and the sdcard. I'll get a good read on the RUU, then try either the rename or fastboot, if I can get fastboot to see the phone. Thanks for you help on this. It is interesting and fun, though too much fun starts to border on frustration. I'm not quitting until its rolled back, or dead. :):):)
 
I've tried two different RUUs (slightly different versions, the last decimal places are different); both had good MD5 sums. I'm downloading a third to try now.

My question is this though. I name them PG05IMG.ZIP and place them in the root of the sdcard. Then I start the phone into hboot mode. When they unpacked, both "bypassed" the same two items; 1. Bootloader, and 8. TP

Since my problem is that the phone won't complete booting up (after the install), do you think it may be because my phone "bypassed bootloader" in both these MUUs?

The PG file unzips, all is good, I say yes install, the install has no error messages, install ends with success and says press power to reboot. I do, the phone screen goes black, then the white screen with htc in green in the middle comes on... and that's where it hangs. Is it normal for MUUs to "bypass bootloader" ?

As always, your thoughts and ideas are appreciated.
 
yes,it is normal for the phone to bypass revolutionary's hboot(youd be back to s on if it didnt :eek:) and tz. if all partitions are successful,im not sure why the phone wont boot. how long are you giving it? hopefully 15-20 minutes,the first bootcan be pretty time consuming.

since you now have the stock recovery,try doing a "factory reset" from the hboot screen. :)
 
Scotty85

OH CRAP. 15-20 minutes?!? I've never given it that long. I've never read where it would take that long. I've usually only given it 3-4 minutes for the screen to change to the next screen or whatever...

I'll give it 20-30 mins on this try. I was able to flash the regular CWM back onto the phone, so there is progress. I'll do another wipe of the caches and give 2.11.605.5 another try. I had no idea you had to wait 15-20 mins...

Thanks
Mike
 
In all fairness it doesnt usually take 20+ minutes,but it's not uncommon for it to take 5-10,so giving it 20+ is pretty safe to say it's really hung :)
 
Well, just to give it all the time it wanted, I left it sitting at the white HTC screen while I read about the latest verizon phones. Its been an hour,twelve now. I'm going to pull the battery and try some rebooting and hboot snooping around.
 
Many, Many thanks, to the people who worked on the ics rom and took the time to post the information, I just updated based on the posts and advice from scotty85.

Went smoothly
 
Post deleted.

I had a problem and needed help, but I was referencing other guides and made a big mistake accidentally reading the wrong source. I am starting over now that I have the right info in from of me. Hopefully all will go as planned!
 
Ok, I had to come back and post again, because I am indeed in trouble. I had forgotten to flash superuser and used clockworkmod as recovery instead of what the guide said. I flashed the main version low zip and it rebooted to a black screen. I proceeded anyway and got to relocking the boot loader, but it still goes to the htc logo then a black screen. I went back and found I followed the wrong directions, so I did everything up to the same point correctly, but I'm afraid I might have really messed something up because I still just get a black screen. Right now, it says "relocked" and S-on. Every time I reboot, it shows htc logo, then goes black. I can access recovery and bootloader just fine, but I don't know what I should be doing to save this phone. Any help would be greatly appreciated.

Edit to add: I was advised to proceed even though i had that black screen issue. I proceeded and it worked just fine. Downgrade completed and I have a phone again!
 
What is the info in your hboot screen? You might try changing your recovery to amon,then flash the main version low zip again,then boot to bootloader and flash the downgrade RUU as described. You phone should boot and work,then.

At this point,im unsure if your phone is failing to boot,or is simply still in RUU mode.

Does your black screen have a silverish "htc" in the middle of it?
 
Scotty, thanks for getting back to me. I see you missed my edit on the post, though. I just proceeded with the process and it ended up working fine! I also have no clue what exactly the problem was, but I'm good now. I tried to use trter's all in one tool and it didn't work for me. I went back to revolutionary and I got s-off just fine.

Thanks for getting back to me and thanks for all your help in this thread and all over the forum!
 
Hi. I've tried downloading the downgrade RUU about 6 times and can never seem to get the MD5 to match. I tried flashing it anyway after the 6th try and got an remote: 12 signature verify fail. Looking up this error, it seems to be a bad download problem.
I'm downloading file: RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.5_Radio_0.01.78.0906w_2__NV_8K_1.41_9K_1.64_release_219938_signed.zip
from:
Shipped ROMs
Strangely, I could not get the download to auto trigger with IE or Firefox, but could with Opera. Unknown if this has anything to do with anything.

Also when checking fastboot getvar mainver, I'm getting back 1.00.000.06.
Cleared the cashes & flashed the "set main version low" zip file three times, and still getting 1.00.000.06.

Any help would be greatly appreciated! Thanks!
 
Does sound like a bad download,if you can't get the md5 to match. That would indeed break the signiture and cause that error. Maybe turn off your firewall/antivirus while downloading? Try a different browser?

Your main version response is fine... It's the 1.00.000.x part that matters :)
 
Everything worked great up until i try recovery mode with the main version low zip on my SD card... it shows an icon with my phone with a red triangle and ! on it and just sits there, am i doing something wrong?
 
BigGreenBudz said:
Everything worked great up until i try recovery mode with the main version low zip on my SD card... it shows an icon with my phone with a red triangle and ! on it and just sits there, am i doing something wrong?
Click to expand...

what youre seeing is the stock recovery. sounds like you did the temp recovery when you htcdev unlocked and rooted,wich does not permantly install the recovery.

youll need to repeat the steps to launch temp recovery,then flash the main version low zip,or you will need to go ahead and permantly install recovery so it will be there when you boot to it.

it doesnt matter much wich option you do,as when you flash the downgrade ruu,it will overwrite the recovery with a stock one.
 
Are these steps necessary even if you've already got root? Or can I just download the old radios and a ROM and flash in CWM?
 
Mayhem said:
Are these steps necessary even if you've already got root? Or can I just download the old radios and a ROM and flash in CWM?
Click to expand...

If you're s off,sure. Just flash radios and rom.

All these steps are only necessary if you're s-on and need to downgrade to get s-off. :)
 
Cool beans. I'm bored of ICS and no one made anything out of the official release, so I'm thinking of reverting back. I found a CM ROM I hadn't tried before, so..
 
Mayhem said:
Cool beans. I'm bored of ICS and no one made anything out of the official release, so I'm thinking of reverting back. I found a CM ROM I hadn't tried before, so..
Click to expand...

that being the case,you can prolly just flash the rom. i dont believe the ICS radio will hurt you.
 
Iiiiiiiiii DID it! Gawd it was kind of convoluted compared to what I've done before. A couple of things I ran into, just in case anyone else is coming to the TB newish:

HTC drivers could not be installed on my Windows 8 computer. I solved this by downloading and installing HTC Sync. I then had to uninstall it when I came to the Revolutionary step but that did not remove the drivers so I was good.

The lowest "main version" number that resulted from flashing the latest main version LOW was 1.00.000.6 NOT 1.00.000.0...but I went forward and it worked anyway.

Thanks for the guide!
 
You must log in or register to reply here.
Back
Top Bottom