Hi- I had my phone rooted with s-off and stock 2.1 ROM with a few mods. I have managed to flash a stock 2.1 ROM that also put back stock recovery but it would not run unless I was s-off. Now how do I get s-on? The stock recovery would not accept it.
UnrEVOked Forever now supports going back to S-ON
http://unrevoked.com/rootwiki/doku.php/public/forever
Here is the link to the tool, just read up on that link if you are unsure of anything.
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
Yes I used the s-on tool. Now I am stuck at s-on with clock mod recovery. I need to get back to stock recovery but I can't get run a stock recovery update with s-on.
Just run the 2.1 RUU stock zip again.
I tried the 2.1 RUU It is an .exe and I was told I needed HTC sync to run it. I installed HTC sync and it would not run.
How do I run the "RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe?
I installed htc sync, got it running, plugged in my phone, chose htc sync option, then tried to run the .exe
I'll try again now on another machine.
I can extract the stock recovery and other files out of the ruu.exe file but what do I do with it. In only need the boot loader. As I said I have stock ROM and s-on.
Damn. I titles this thread wrong. I have s-on and stock rom, I need stock recovery. I also need to get this done before I leave town. I'm going to post the question with a proper title for the thread. My apology and moderater please remove this thread.
Resolved
Problem solved with the PB13img file provided with Diego Mejia's 2nd video. Worked perfectly. Did not even have to do all the adb pushing of sys files since I never put in the leaked OTA. His file version was just accepted by hboot. Awesome!
Hey folks.Im trying to root my buddys evo and want to make sure i have everything in order before i go forward..
hboot is version 0.97
software 3.29.651.5
so im hoping i can just use the unrevoked forever to root his phone.Is this correct?It says i need a custom recovery how do i make a custom recovery so i can use the unrevoked forever?
Unrevoked Forever does not root, unrevoked3 does.
Since his HBOOT is 0.97, then yes you can use unrevoked3 to root.
[ROOT] unrEVOked 3.21: one-click root for Froyo, no downgrading
[GUIDE] One Click How to Root EVO with Unrevoked 3.21 *NEW EVO'S WONT WORK 11.16.10*
Ok..thanks for the help.I installed unrevoked3 and it finished.I have the superuser icon also.BUT if i open hboot it still says s-on? Im confused about that.It looks like i got root but why is it saying S-on in hboot?
If anyone else has this same problem,here is what i did to get s-off.
After you use the unrevoked3 you now have ClockworkMod Recovery.Go download the Unrevoked Forever and put it on the root of you sd card.Now restart your phone in Hboot and go to recovery.When your in ClockworkMod Recovery you will see install zip from sd card,click.Find the Unrevoked Forever you just put on your sd card and run it.After it is finished you should now have S-Off .
Wooot!!
I was having issues with my phone about a month ago. I had rooted it using Unrevoked 3. I decided to go back to stock so I downloaded a PB31IMG.ZIP file a reloaded it, loaded the 2.2 updates and loaded the last update from Verizon. It was the third time I've had to do this so I decided to keep it stock. I noticed when I would go into recovery mode that it said "INCREDIBLE XC SHIP S-OFF" on the first line. Does this mean my phone's security level is set to S-OFF? If so, is there a way to change it on my unrooted phone? I downloaded the S-ON zip file from the Unrevoked site, renamed it update.zip and tried to install it but it would give me the E:failed to verify whole-file signature error each time. I want to get my phone back to S-ON just in case I have problems with it and I need to return it under warranty. Any help would be much appreciated. Thanks.
The security is independent of rooting, as you have discovered. Rooting is at the level of the ROM itself whereas the security is at the bootloader level.
The only way to turn security back ON is with S-ON tool. In order to do that you need a custom recovery (clockwork)..in order to install clockwork you need to root. So you did everything backwards.
You'll have to root, install clockwork (if you have stock recovery right now). Then run s-on, then LASTLY run an RUU.
The RUU will replace the bootloader, recovery AND ROM all back to stock. You can flash RUUs with S-ON because they are signed/official.
I need to return my evo for repair, but I have problems unrooting my phone. For some reason i cant run ruu, because it cant recognize my phone. I tried to run PC36IMG.zip , and I have S-OFF. But once I flash S-ON zip and then run PC36IMG.zip from bootloader, it scans the zip file but doesn't let me update. I noticed that when I go back to S-OFF I can flash the zip, but since I don't have access to recovery I can't flash back to S-ON. Any idea anyone?
Try re-rooting your phone, flashing S-OFF and then loading the image.
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.