Hi everyone,
I used RegawMod to unlock the bootloader, get root, and installed TWRP flash recovery. Phone is "S-ON". The phone was having issues with repeated SMS and I couldn't take the OTA. So I was told to relock the bootloader and install stock RUU file.
Ok so I did just that, relocked bootloader and then went to reinstall the RUU. When I went to download the RUU's I saw that the latest version was:
"RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
I figured it would be ok to flash this and this would give me Jelly Bean all in one shot. My phone was running the stock rom which was software version "1.13.651.1"
So I installed the RUU and everything seemed to work properly until the phone rebooted. I noticed that none of the settings had been reset and the email account was still there etc. Typically when you flash an RUU everything goes back to configure mode on reboot. So I went into the settings software version etc and sure enough the software was the old software.
Looks like the RUU only changed my boot loader! When I checked originally I had bootloader 1.12.0000 after flashing the latest RUU file my bootloader was now 2.09.0000.
I then downloaded the "1.13.651.1" RUU to try and install it but it said not compatible with the bootloader.
Any advice on why the rom didn't update? What can I do now?
http://forum.xda-developers.com/showthread.php?p=36308826#post36308826
Welcome to the machine, where have you been? It's alright, we know where you've been.
Got a pretty lengthy thread, it seems the more people that run the new RUU are having the same exact issue. My radio is stuck on 1.05 and hboot 2.09 after running that thing. Should have known not to trust anything stock. Always thought those RUUs were safe.
Anyways, a bunch of us are subscribed to the thread I posted at the top of this post, I recommend you subscribe to it to keep things clean.
Alright, I hate having to post a new thread on this topic, but I cannot find any solution, or anything close to a solution for this. my problem is that i cant get back to stock from the newest firmware. I had unlocked, rooted, and gotten s-off all before the update. After that, i flashed a few things, and ended up updating to the newest radio and firmware number (2.04.605.2, and 1.01.01.0110). now i want to go back to stock and start fresh, but nothing seems to work. Trying the RUU method only gets me to a 158 Image error about 3 minute into the process, and i cant seem to get back to 1.15. any help is much appreciated. I've been at it, searching for 5 days. if i missed something, or missed a thread, please let me know, thank you in advance
Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.
Yeap zone is correct, flash the Eng RUU or relock your bootloader either way and then run the RUU. It won't run on a stock hboot that's unlocked.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
zone23 said:
Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.
Click to expand...
Click to collapse
Thank you! worked like a charm, i appreciate your quick response I've been running in circles for days now, i can finally get back on track!
Glad I could help.
ENG Hboot & unroot
I'm having the same problem as the op. I downloaded the updates, and i'm trying to unroot my device and put it back to stock (I broke my screen and I want Verizon to fix it, without giving me grief about my software). I have the RUU and Its giving me an 158 Image Error. Sounds like I need to flash eng Hboot and then run the ruu.
Two Questions:
1. Where can I get / download eng Hboot for my DNA?
2. Which version of Hboot do I need? I currently have hboot 1.33.0001.
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
flybub said:
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
Click to expand...
Click to collapse
Hem... that's the current bootloader. Are you s-on or off ?
dottat said:
Hem... that's the current bootloader. Are you s-on or off ?
Click to expand...
Click to collapse
I'm S-On. I downloaded the PH98 file again thinking maybe it was bad, but no dice. I get the same error message. I can't get anything to boot. I was able to flash a recovery so I flashed Infection 2.5 but I keep getting stuck at the Android looking screen (yes boot.img was flashed in fastboot). I flashed a couple different ICS roms but none of them boot up. I figured if I could get back to stock I would just go s-off and be done with it but I think this phone is done.
Edit: Gave the phone to a friend of mine who is much better at this stuff than I am. Maybe he can figure it out. Thanks for the help
Hm, if you flashed the kernel you should be able to boot up.
If you're s-on and on hboot 2.28 there's no RUU as of yet you can run. There's a stock OTA ROM of the lates OTA in the dev section you can run that and see if that helps. You probably can s-off on that but don't take my word for it, especially since you're on 2.28 hboot.
I would make a nandroid before so you can always get back to that if needed.
If you really want to run an RUU you need to s-off, but confirm that it's still going to work on the latest OTA before trying it.
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !
So, my HTC One M8 is still on CM11, with S-On and rooted with TWRP installed. I have tried to update CM and it fails every time. I tried to revert back to stock by using HTC's RUU, but it fails every time and when it does I lose cell service and WiFi capability. I have Factory reset, which has restored my Cell service and WiFi, but I am still runing CM11. I have watched countless videos and tried to follow guides on how to revert but I simply cannot find one that's up to date, and on XDA I can't find the one pertanent to my CID Num, CWS__001. I am desperate and I really would just like to be on stock Rom again, is there anything that I can do? Does anyone have an idea of what can be done to revert?
You can't just run any RUU. The RUU has to match your CID and MID. In your case, it needs to be the AT&T RUU. If s-on, you also have to relock the bootloader to run the RUU. Also, the RUU needs to be greater or equal firmware version than what is currently on the phone (no "downgrading" allowed with s-on).
Find the AT&T RUUs in my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432&page=6
Also, CM12 requires a certain hboot (I believe 3.19) in order to install. So if your hboot is older, that is probably why CM12 is not installing. The RUU will fix that. But you will then need to unlock the bootloader again, and re-install custom recovery, in order to be able to flash CM12.