Develop Bugs

[Guide] EVO Revert to stock + S-ON after Gingerbread

This took me all day to figure out so I'm making a guide. The 2 Big problems I had were getting the S-on patch to work and the newer Hboot that came with gingerbread refusing to downgrade to an older PC36IMG.zip.
The main reason I wanted to return to stock was for a repair, last time i did everything except s-on and the guy noticed it and black listed my esn.
Make sure you are prepared before you continue! Once you flash your radio your phone wont boot into the OS.
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Download this file I got this off a youtube video for the incredible and replaced the files with their EVO specific counterparts
Open the zip and move flash_image and mtd0.img to your sdk/tools/ folder
boot into your custom recovery and mount /system/
open up a command prompt in your tools folder
(in windows7 hold shift and right click on /tools/ there will be an option to "open command window")
Run the commands in the commands.txt file. FYI you can paste into command prompt with right click.
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Click to expand...
Click to collapse
After this you can move your stock PC36IMG.zip to the root of your SD card and reboot into your Hboot Bootloader. If everything was done correctly it should now accept PC36IMG and downgrade to stock.

Great job! Do you think there will be an easier way in the future? I don't think I would be able to do this.
Sent from my PC36100 using Tapatalk

If you run the 3.70 RUU while still s-off, will it replace the hboot with an older version? It seems like it should, but I'm confused by the 6.16 hboot.
I haven't actually ran revolutionary, so this is all theory, but I thought unrooting/s-on would work like this:
Run the RUU for 3.70. I don't have much experience with RUUs, but if they don't include radios, you would then need to reflash recovery and downgrade the radio. After reflashing etc, then flash the s-on zip. Then rerun the RUU for 3.70 to get rid of your custom recovery, or run the RUU for 4.24, since once you're s-on you can't downgrade & every RUU will be a downgrade from 6.16 hboot.
Now this may be entirely wrong, but I was just curious if it would work. I've been rooted for a while, and unrooting and s-on would be much easier for me. Even though it sounds like a pain, it still sounds more noob friendly than the version in the OP.
Either way, great job on putting this together. I know that a lot of people are curious about unrooting from revolutionary, so hopefully you've cleared some confusion.
Sent from my PC36100 using Tapatalk

Sfork said:
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Click to expand...
Click to collapse
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.

Captain_Throwback said:
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.
Click to expand...
Click to collapse
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk

plainjane said:
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?

Captain_Throwback said:
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?
Click to expand...
Click to collapse
Hboot 6.16 will not downgrade or flash S-ON currently.

[Q] SU Binary Update dont Sucess

Hello Folks,
i have a problem with my Wildfire (was Branded with T-Mobile DE)
I have downloaded the Update for Superuser and now it always say that my SU Binary is too old. But if i want to update it, it get an error at the point to get the /System write rights.
How do i get it work?
Here are some informations from the Bootloader of my Phone:
BUZZ PVT SHIP S-ON
HBOOT-0.80.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO.3.35.20.10
May 13 2010,22:09:43
The currently installed ROM is CM7 Nightly 199
and the CWM Version is 2.5.0.1
And sorry for my bad English, i prefer German

From what I could tell, the S-ON seems to be the problem.

and how do i make it s-off?
cause my h-boot is 0.80.0002 and Alpharev X only works with 1.00.0001

From i know you need to update to official 2.2 with a RUU and then s-off.
Check one of stickies in development for more details.

Alex_GP said:
From i know you need to update to official 2.2 with a RUU and then s-off.
Check one of stickies in development for more details.
Click to expand...
Click to collapse
I tryed it, to install the RUU with the Hboot 1.00.0001 but it always give me an error that its not the right UserID. With no chance -.- ... is there any possibility to Update the Hboot over CWM? Maybe installable from a Zip file?
Need help

Metalschnulli said:
I tryed it, to install the RUU with the Hboot 1.00.0001 but it always give me an error that its not the right UserID. With no chance -.- ... is there any possibility to Update the Hboot over CWM? Maybe installable from a Zip file?
Need help
Click to expand...
Click to collapse
Hi, can't remember exactly my method but try to explain best I can.
I flashed safe not rooted rom from 3xeno's sticky page. Then I downloaded on PC the ruu. Exe and this is the part o can't remember but I got the rom image from the exe and turned it into a pc49 img then placed on SD root and rebooted into hboot? ( Power + vol down ). It did its magic then I just used revolutionary to s-off and did clean install of cm7 to replace revs su. Hope this makes sense!!! And is of help.
Sent from my HTC Wildfire using XDA App

To update the su, just flash the signed zip from here: http://androidsu.com/superuser/

With a RUU, you must be in Android. (so not fastboot or anything else).
Then, if it works.
You open Revolutionary (you found it on revolutionary.io) in admin mode. And then it's okay

[Q] G2- Superuser & Visonary disapear when I switch to desire z hboot

Rooted my brand new replacement G2 with the visonary method today. Just saw the OTA update for gingerbread and ignored it. Successfully perm rooted. Then I went about to obtain the desire z hboot so I could flash Virtuous Unity 2.39.0. I used zedomax's method on youtube where you dont use adb at all.
After successfully installing the desire z hboot I restored my phone from my backup to find that superuser and visionary were gone. I went to my terminal and typed su and it said permission denied. I still have S-OFF so what is going on? I decided to try to root again through visonary and once I permrooted again and rebooted, I could only reboot into clockwork recovery. Ive tried restoring my backups and I cant seem to boot up. Keep getting MD5 is a mismatch! error message. Any help is greatly appreciated

chickawaffles26 said:
Rooted my brand new replacement G2 with the visonary method today. Just saw the OTA update for gingerbread and ignored it. Successfully perm rooted. Then I went about to obtain the desire z hboot so I could flash Virtuous Unity 2.39.0. I used zedomax's method on youtube where you dont use adb at all.
After successfully installing the desire z hboot I restored my phone from my backup to find that superuser and visionary were gone. I went to my terminal and typed su and it said permission denied. I still have S-OFF so what is going on? I decided to try to root again through visonary and once I permrooted again and rebooted, I could only reboot into clockwork recovery. Ive tried restoring my backups and I cant seem to boot up. Keep getting MD5 is a mismatch! error message. Any help is greatly appreciated
Click to expand...
Click to collapse
Visionary is not a safe method to use to permanently root the Vision. There are warnings and stickies all over about this... you might want to check them out. Perhaps there are some solutions in these threads... discovered by users in your same situation... Have you tried the unroot option in Visionary?
Ideally, you can start over completely and use a clean method. If you're still on 2.2 the best bet is here: http://forum.xda-developers.com/showthread.php?t=928160

chickawaffles26 said:
Rooted my brand new replacement G2 with the visonary method today. Just saw the OTA update for gingerbread and ignored it. Successfully perm rooted. Then I went about to obtain the desire z hboot so I could flash Virtuous Unity 2.39.0. I used zedomax's method on youtube where you dont use adb at all.
After successfully installing the desire z hboot I restored my phone from my backup to find that superuser and visionary were gone. I went to my terminal and typed su and it said permission denied. I still have S-OFF so what is going on? I decided to try to root again through visonary and once I permrooted again and rebooted, I could only reboot into clockwork recovery. Ive tried restoring my backups and I cant seem to boot up. Keep getting MD5 is a mismatch! error message. Any help is greatly appreciated
Click to expand...
Click to collapse
Read this guide. Use it. Love it.

[Q] Is it me or did HTC once again lock root?

I was more than content with the "Revolutionary" root and it was great being able to swap ROMs to my hearts content. I was not to smart to accept the OTA update while in the stock HTC Gingerbread. I still show S-OFF and I am unable to flash CWM recovery or Amun Ra. I guess I am stuck with stock HTC sense until there is a way to unlock HBOOT 6.16.1002 or even better flash it back to HBOOT 2.15 or 2.06.
I apologize if this has already been covered on changing HBOOT back to 2.15 or 2.15.

Eltaco71 said:
I was more than content with the "Revolutionary" root and it was great being able to swap ROMs to my hearts content. I was not to smart to accept the OTA update while in the stock HTC Gingerbread. I still show S-OFF and I am unable to flash CWM recovery or Amun Ra. I guess I am stuck with stock HTC sense until there is a way to unlock HBOOT 6.16.1002 or even better flash it back to HBOOT 2.15 or 2.06.
I apologize if this has already been covered on changing HBOOT back to 2.15 or 2.15.
Click to expand...
Click to collapse
If you're still S-OFF you can download Amon-RA from here,
http://www.mediafire.com/?hiaavcq1tiwass1
or clockworkmod from here,
http://www.mediafire.com/?5otzpnt2ld1lmdo
and then if necessary, superuser app to reroot from here,
http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip
Change the recovery files to PC36IMG files and place on the root of your SD card, and also place the su-2.3.6.3-efgh-signed.zip file on the SD card as well. First run the PC36IMG file through your bootloader, and then accept the update. Then flash the su file from whichever recovery you used.

[Q] no root anymore after re-run unrevoked

Hi all I've rooted my wildfire last year using unrevoked and all went ok... now I've used unrevoked another time to flash an updated clockworkmod 2.5.0.7 instead of my actual 2.5.0.1 almost because I can't charge my phone when it's off because of an old bug in cwm.
After running unrevoked the phone boots but I've lost superuser app and unrevoked itself fails with something like "cannot get root, firmware too new?" and if I run "su" from terminal emulator I got a "permission denied". The cwm is still version 2.5.0.1
Any idea?

I've just installed superuser app from the market and now I've restore the su command functionality...
What happened? and why unrevoked doesn't upgrade recovery image with the one I've specified?

mrfree2ita said:
I've just installed superuser app from the market and now I've restore the su command functionality...
What happened? and why unrevoked doesn't upgrade recovery image with the one I've specified?
Click to expand...
Click to collapse
I never would have the idea to re-run unrevoked for flashing a different recovery. Although it's also suggested in The Complete Wildfire Index thread I always would choose one of the three other methods (always done it by the PC49IMG.zip method).
Flashing a recovery isn't just a minor tweak if I'm correct. So I'm not surprised that you lost superuser temporarily. I personally would get a bit nervous to do this by revolutionary - but that's perhaps I'm already an old wise guy

Because I've used unrevoked (when I've rooted my wildfire it was the only way) I'm actually S-ON so the other 3 methods shouldn't work in my case.

mrfree2ita said:
Because I've used unrevoked (when I've rooted my wildfire it was the only way) I'm actually S-ON so the other 3 methods shouldn't work in my case.
Click to expand...
Click to collapse
oh well, I've been mistaken, then - yes that's the only method if you're s-on.