Good Morning,
I got myself in a situation and I'm not sure how to get out of. My phone is rooted and before had s-off with hboot .93 and baseband 2.15.00.0808. I wanted to try a rom that only worked with certain versions of hboot. So I updated my hboot to 0.97 and I lost my s-off. Currently I can't use unrevoked because my baseband is not supported. I also can't use revolutionary because my hboot is not supported. Is there anything I can do to get my s-off again thank you.
kronik420 said:
Good Morning,
I got myself in a situation and I'm not sure how to get out of. My phone is rooted and before had s-off with hboot .93 and baseband 2.15.00.0808. I wanted to try a rom that only worked with certain versions of hboot. So I updated my hboot to 0.97 and I lost my s-off. Currently I can't use unrevoked because my baseband is not supported. I also can't use revolutionary because my hboot is not supported. Is there anything I can do to get my s-off again thank you.
Click to expand...
Click to collapse
Have you tried running an RUU.exe from fastboot? Maybe the 4.53 update, so you can be able to root with Revolutionary.
Here is Football's RUU folder.
http://www.filefactory.com/f/acf0b850b0f70d7b/
Good Luck and good morning to you too.
atapia984 - So your saying download and install 4.53 update. I need to place that on my sd card on the setup to flash the phone. Also will that update my hboot
kronik420 said:
atapia984 - So your saying download and install 4.53 update. I need to place that on my sd card on the setup to flash the phone. Also will that update my hboot
Click to expand...
Click to collapse
No these are RUU.exe you run from your Windows machine. You could also try Captain_Throwback's PC36IMG.zip's you can flash from the HBOOT from the post here.
http://forum.xda-developers.com/showpost.php?p=16949711&postcount=15
either the 4.54 or the 3.70 so you will be able to root with either Unrevoked or Revolutionary.
Ok its downloaded just curious do you think this will brick my device before I go through and install it just want to be sure Its not going to brick it
http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html
I tried this and I got error failed to get root is your firmware to new.
If succesful an RUU restores your device back to stock firmware. There should not be a brick.
Sent from my PC36100
I tried it and it says ERROR [155] UNKNOWN ERROR
the rom update utility cannot update your android phone.
kronik420 said:
I tried it and it says ERROR [155] UNKNOWN ERROR
the rom update utility cannot update your android phone.
Click to expand...
Click to collapse
Make sure you have the necessary drivers for Windows.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Have you tried the PC36IMG.zip?
According to G&E all HBoots are now downgradeable as of 3/15/12 so try downgrading back to your old HBOOT that worked. There's also a thread on here, I think it (Radios) by Caulkin it where I get all the latest radios, combo zips, hboot versions and more, great resource, good luck.
http://www.goodandevo.net/2012/03/state-of-the-htc-evo-4g-and-evo-3d-root-world-march-2012.html#more
BeInGarvey
kronik420 said:
I tried it and it says ERROR [155] UNKNOWN ERROR
the rom update utility cannot update your android phone.
Click to expand...
Click to collapse
Just use the 4.54 PC36IMG.zip file from my post that someone linked earlier, and flash it through Bootloader. Then you can re-root/unlock using Revolutionary.
Related
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.
So I was trying to unroot my phone to take it back to Sprint. I flashed PCimg to put S-on and was going RUU back to stock ROM. However, for some reason the RUU says it cant find my device. So I decided to just go back and switch back to S-off. But when I try to run Revolutionary it says that I am already S-off. But the bootloader says I have S-on. Halp!
download unrevoked forever son patch and put on sd card. Go into your recovery and flash it. Go back to hboot and see if its on. Lemme know if that works thanks.. if you need the file i can upload it for ya.
thlinx said:
download unrevoked forever son patch and put on sd card. Go into your recovery and flash it. Go back to hboot and see if its on. Lemme know if that works thanks.. if you need the file i can upload it for ya.
Click to expand...
Click to collapse
Ok well I attempted to do that....but I cant flash unrevoked forever because I have the latest radio version and they are not compatible. So the flash aborts midway through. And unfortunately I cannot downgrade my radio, at least not that I've seen. So now what?
What hboot version do you have?
If it is 6.17 because that's how you s-on'ed revolutionary, you need to run an RUU to get you back to 2.16 so you can reroot. If the computer won't find your device, try running it with the phone in fastboot.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
What hboot version do you have?
If it is 6.17 because that's how you s-on'ed revolutionary, you need to run an RUU to get you back to 2.16 so you can reroot. If the computer won't find your device, try running it with the phone in fastboot.
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
I ended up flashing a PC36IMG that wiped everything and set my OTA, hboot, recovery, splash, boot animation, and got the S-on worked out. One file.....one flash....one happy Evo owner.
Thanks for the suggestions.
I have that exact same problem. Any way you can share the link to that PCIMG file you used to fix your problem. I am in the same boat.
johng294 said:
I have that exact same problem. Any way you can share the link to that PCIMG file you used to fix your problem. I am in the same boat.
Click to expand...
Click to collapse
nevermind i just had to run the RUU again. my mistake.
johng294 said:
nevermind i just had to run the RUU again. my mistake.
Click to expand...
Click to collapse
Hey man, sorry for not responding. I didn't see that this thread had been bumped. Glad you got it working properly.
help
well im on hboot 6.17 but i have s-on as well an i cant flash pc36img it wont take it for some reason an were i took that ota 4.54 i cant find an ruu for it..can anyone help??
tylo23 said:
well im on hboot 6.17 but i have s-on as well an i cant flash pc36img it wont take it for some reason an were i took that ota 4.54 i cant find an ruu for it..can anyone help??
Click to expand...
Click to collapse
Wouldn't you be able to run the RUU for the 4.53 then just update to the new 4.54??
I'm trying to root my brothers Evo again and running into some problems.
Back story: I had rooted his device with Revolutionary and he was running CM7 just fine. He started to have troubles with his screen so we unrooted it and got S-ON back. He took his phone to Sprint and instead of replacing the device, they decided to just replace the screen on it.
Current story: Downloaded Revolutionary and ran it and got this;
Code:
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PC36100 (supersonic-6.17.0001, Android: 2.3.3, ROM version: 4.53.651.1)
Your device is already S-OFF, what exactly do you think you're doing? Not setting S-OFF.
Do you want to download (Internet connection required) and flash ClockworkMod Recovery? [Y/ny
Downloading recovery for your phone (supersonic)...Done.
Rebooting to fastboot...
Flashing recovery over fastboot...INFOsignature checking...
FAILED. Unable to flash recovery. Please download custom recovery yourself and flash it over fastboot.
So here I am with the HBOOT saying that S-ON and Revolutionary telling me it's off and won't turn it off.
Not sure where to go from here!?
Thanks!
When it tells you that your Device is already S-OFF, you should have an option to turn it off regardless.
If that doesn't work, I guess you could try and use another method to do it.
and if THOSE don't work, I guess you could just sbf flash it it
I don't have an option to turn it off regardless.. it finds the device and logs the fact it thinks S-OFF is present and asks to download the recovery.
I thought revolutionary was the only option for HBOOT 1.6 at this point. Is this incorrect?
Also what do you mean by sbf flash it?
DruKe said:
I don't have an option to turn it off regardless.. it finds the device and logs the fact it thinks S-OFF is present and asks to download the recovery.
I thought revolutionary was the only option for HBOOT 1.6 at this point. Is this incorrect?
Also what do you mean by sbf flash it?
Click to expand...
Click to collapse
You didn't do the last step after getting S-ON, which is flashing a stock ROM. Because of your HBOOT version, Revolutionary thinks you're already S-OFF. You need to flash a stock ROM to normalize your HBOOT version, and then Revolutionary will work.
He cannot flash a stock ROM if he is S-ON. Sbf basically resets everything on your phone back to its "out of the box" state
@Druke, can you get to recovery? If there is no recovery you may want to RUU back to 4.54 then try revolutionary again. Or just go through the un-rooting steps again.
imheroldman said:
@Druke, can you get to recovery? If there is no recovery you may want to RUU back to 4.54 then try revolutionary again. Or just go through the un-rooting steps again.
Click to expand...
Click to collapse
Just remember to not do any updates after RUU'ing back to 4.54! Then you'll have to use other methods to unlock and revert. Good luck.
Flowsick said:
He cannot flash a stock ROM if he is S-ON.
Click to expand...
Click to collapse
This is incorrect. You can flash a signed HTC stock ROM in PC36IMG format (or RUU on a PC for that matter) just fine. As I said, that's the last necessary step to returning the device to stock conditions. Trust me, I've done it probably almost 100 times.
P.S. Since I'm the one that came up with the unrooting method that was used, I would know .
I did try an RUU yes. I will need to try an RUU again. The one I used must have been unsigned or unofficial somehow. Anyone help me out? With the megaupload thing it seems all the links around here have dried up. Thanks!
Sent from my PC36100 using XDA App
DruKe said:
I did try an RUU yes. I will need to try an RUU again. The one I used must have been unsigned or unofficial somehow. Anyone help me out? With the megaupload thing it seems all the links around here have dried up. Thanks!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The unrooting Revolutionary root link in my sig has links to some PC36IMG zips that can be flashed in bootloader.
I recommend the 4.54 version. Sometimes it won't work if you're using a version that's too old, or if your SD card isn't a high capacity card or got corrupted somehow.
Captain_Throwback said:
The unrooting Revolutionary root link in my sig has links to some PC36IMG zips that can be flashed in bootloader.
I recommend the 4.54 version. Sometimes it won't work if you're using a version that's too old, or if your SD card isn't a high capacity card or got corrupted somehow.
Click to expand...
Click to collapse
4.54 RUU or PC36IMG is the most likely to work, however, 4.24 and 4.53 contain the same HBOOT needed for Revolutionary to work again as well.
Sent from my PC36100 using XDA Premium App
shortydoggg said:
4.54 RUU or PC36IMG is the most likely to work, however, 4.24 and 4.53 contain the same HBOOT needed for Revolutionary to work again as well.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Of course, but my recommendation was referring to the ones posted in the link .
I tried grabbing the 4.54 version from you post however the link to it is dead.
Got dropbox?
DruKe said:
I tried grabbing the 4.54 version from you post however the link to it is dead.
Got dropbox?
Click to expand...
Click to collapse
It shouldn't be - I refreshed those links earlier today and changed them to 4shared. When did you last try?
So weird.. works now! Thanks a ton! I'll give it a shot this weekend. Hopefully everything goes aces!
Thanks again.
This is an error i'm geting after doing a ruu, when I try to install unrevoked this is the error it comes up with, any ideas? The radio it shows now is one I installed because it said radio unsupported....
unrEVOked forever S-OFF patch v1.3
Verifying system type...
.
.
Got device:
@PID: 69,"INCREDIBLE_C"
Got radio version:
2.15.10.05.06
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
normanx said:
This is an error i'm geting after doing a ruu, when I try to install unrevoked this is the error it comes up with, any ideas? The radio it shows now is one I installed because it said radio unsupported....
unrEVOked forever S-OFF patch v1.3
Verifying system type...
.
.
Got device:
@PID: 69,"INCREDIBLE_C"
Got radio version:
2.15.10.05.06
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
Click to expand...
Click to collapse
Which version of ruu did you do? Are you s-off? If you are s-off flash radio 2.15.00.07.28 from here http://pvillecomp.com/?page_id=18, then try unrevoked again.
If you are on gingerbread rom and s-on, you will need to use scottys guide http://forum.xda-developers.com/showthread.php?t=1306400 to downgrade and get s-off.
I used the stock PB31IMG image from Pvilles website, I thought it was the 4.08.605.2 but it was one prior to it, its a downgrade by version numbers, Yes I have S-off, I had it before from when I first got the phone and downgraded it to get root, and did the unrevoked forever and all was fine...then I installed a ROM that I was sure messed up my dbm signal, So I ruu'd back to start over.
That was all it took.....Thank you very much I knew I was forgetting something.....just could not remember what....
normanx said:
I used the stock PB31IMG image from Pvilles website, I thought it was the 4.08.605.2 but it was one prior to it, its a downgrade by version numbers, Yes I have S-off, I had it before from when I first got the phone and downgraded it to get root, and did the unrevoked forever and all was fine...then I installed a ROM that I was sure messed up my dbm signal, So I ruu'd back to start over.
That was all it took.....Thank you very much I knew I was forgetting something.....just could not remember what....
Click to expand...
Click to collapse
Fyi if your s-off you dont need to use unrevoked to regain root. Just flash cwm recovery thru hboot as a PB31IMG.zip (http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip), and then flash the su binary thru cwm recovery (http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip). Then boot up and install busy box and your rooted and good to go.
Thanks very much. I owe ya
Sent from my unrEVOked forever Dinc, CM7.1.0
Hi all. I rooted (and s-off'ed) my CLNR Inc2 using the TacoRoot and Revolutionary method and flashed a few custom Roms to try them out. Now, I wanted to get back to unrooted, and s-on. I tried the method of first flashing the Froyo RUU which doesn't work. It tells me something about the versions. So I flashed the 5.10.605.9 RUU which flashed everything except the bootloader. Can someone tell me how to get rid of Revolutionary's hboot and get back to s-on please? I assume that since I'm not running Froyo, if I did "adb push hboot_0.97.0000_336906.nb0 /data/local/" as referenced in the thread http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/ I would brick my phone. Help? Thank you!!
Camaro305 said:
Hi all. I rooted (and s-off'ed) my CLNR Inc2 using the TacoRoot and Revolutionary method and flashed a few custom Roms to try them out. Now, I wanted to get back to unrooted, and s-on. I tried the method of first flashing the Froyo RUU which doesn't work. It tells me something about the versions. So I flashed the 5.10.605.9 RUU which flashed everything except the bootloader. Can someone tell me how to get rid of Revolutionary's hboot and get back to s-on please? I assume that since I'm not running Froyo, if I did "adb push hboot_0.97.0000_336906.nb0 /data/local/" as referenced in the thread http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/ I would brick my phone. Help? Thank you!!
Click to expand...
Click to collapse
What message are you getting when trying to flash the Froyo RUU? Please be more specific.
tincbtrar said:
What message are you getting when trying to flash the Froyo RUU? Please be more specific.
Click to expand...
Click to collapse
It scans the zip, then says "Wrong zipped image" - "No image or wrong image". Like I said, if I flash the 5.10.605.9 ruu, it flashes everything except the bootloader, which is understandable since I realize the Revolutionary hboot is protected. Previously, when I rooted and unrooted, I would downgrade to Froyo, replace hboot with 0.97, and then flash the latest ruu via bootloader.
Thanks in advance to you or anyone else who can help me out!
Actually, I'm sitting here thinking... why would I want to put s-on again? I flashed CWM recovery via fastboot, then flashed CM7.2 and all is well. I'll just keep s-off. Thanks anyway!
Camaro305 said:
Actually, I'm sitting here thinking... why would I want to put s-on again? I flashed CWM recovery via fastboot, then flashed CM7.2 and all is well. I'll just keep s-off. Thanks anyway!
Click to expand...
Click to collapse
Good call! lol.
You were probably getting that error because the RUU wasnt located in the directory that you have adb/fastboot (tools) enabled.
Give that a shot next time and you will be fine.
tincbtrar said:
Good call! lol.
You were probably getting that error because the RUU wasnt located in the directory that you have adb/fastboot (tools) enabled.
Give that a shot next time and you will be fine.
Click to expand...
Click to collapse
I don't think it matters where adb/fastboot is on the PC. The RUU was on the phone, renamed as PG32IMG.zip.
Followup:
It turns out I was getting the error as a result of a bad download. That's why the bootloader scanned the zip and took a ****. I re-downloaded the Froyo ruu, flashed, pushed the .97 hboot, and ta-da, have s-on.