Help needed to get back to stock - HTC Rezound

so i have a Htc rezound i have TWRP installed as the recovery and it is S-ON
i had done a twrp back before i had done any modding to the firmware, and it was and is an entire backup of the phone
i have gotten the backup to restore via TWRP but once it gets to the verizon 4G LTE splash screen it just hangs there everytime
i've downloaded a bunch of RUU's to try and get them to work with the phone but they either don't show up or it tells me the Hboot version im using is too new for the RUU im using.
i have the newest hboot version 2.28
i have used many threads but this was the most promising , i just can't get it to work
http://forum.xda-developers.com/showthread.php?t=2453701
can anyone help as i didn't do the S-off , so it is still S-on
i do have a entire backup of the phone via TWRP i just don't know how to get it to work..... couldn't find a boot.img to flash either , i figured to try that but couldn't find it

---

dust906 said:
so i have a Htc rezound i have TWRP installed as the recovery and it is S-ON
i had done a twrp back before i had done any modding to the firmware, and it was and is an entire backup of the phone
i have gotten the backup to restore via TWRP but once it gets to the verizon 4G LTE splash screen it just hangs there everytime
i've downloaded a bunch of RUU's to try and get them to work with the phone but they either don't show up or it tells me the Hboot version im using is too new for the RUU im using.
i have the newest hboot version 2.28
i have used many threads but this was the most promising , i just can't get it to work
http://forum.xda-developers.com/showthread.php?t=2453701
can anyone help as i didn't do the S-off , so it is still S-on
i do have a entire backup of the phone via TWRP i just don't know how to get it to work..... couldn't find a boot.img to flash either , i figured to try that but couldn't find it
Click to expand...
Click to collapse
I was in a similar predicament only worse because I had accidentally wiped the system and I didn't have any backup as it was a refurbished replacement phone. At the time, I was also S-on and Hboot 2.28. Even though I used AmonRa, I'm sure it would work with TWRP as well. Take a look at THIS POST on how I was able to get my phone back up and running. Maybe it will help.

---

The only way to go back to stock is s-off then downgrade to the stock ruu.exe and then go back to s-on and relock...let me find it but someone already posted a thread about this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app

---

http://forum.xda-developers.com/showthread.php?t=2453701
Instructions and links, step by step to s-off, get ruu stock.

---

Thanks flamewalker....this was exactly what I was referring to
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app

---

REV3NT3CH said:
The only way to go back to stock is s-off then downgrade to the stock ruu.exe and then go back to s-on and relock...let me find it but someone already posted a thread about this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
Not true. I was able to accomplish getting back to fully stock while still S-on with Hboot 2.28.0000 and can see how I did it if you click the link I posted. In order to use the most current ControlBear through the Ubuntu method, you have to be completely stock. Since I had accidentally wiped the entire system along with the cache and dalvik cache, and without a nandroid backup, my phone was soft bricked but I was able to get a working stock phone without having to S-off so it can be done. It was only then that I proceeded to S-off.

---

Not true read flamewalkers post...quite a few have gone s-off while on a custom ROM....and doing downgrading while s-on has a very high chance of bricking your device
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app

---

REV3NT3CH said:
Not true read flamewalkers post...quite a few have gone s-off while on a custom ROM....and doing downgrading while s-on has a very high chance of bricking your device
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
I didn't downgrade, I went from a new replacement phone that unfortunately ended up completely wiped of any of the system files and folders and was able to reinstall the current 4.05.605 using that stock rooted rom and flashing that in a custom recovery. I also did the boot.img thing as well but I am almost certain that I had to flash that boot.img first before flashing the stock rooted rom zip. I never used any earlier versions, only that stock rooted rom file. It didn't require any downgrading or S-off. I had extracted the stock recovery from the firmware link I posted in the other thread and placed it in a custom ph98img.zip. I put that on the ext-sd card after my phone was up and running. Then I went back into the unlocked bootloader and let it install the stock recovery. For whatever reason I was unable to get earlier versions of ControlBear to work for me and that was why I chose to use the most current version. I don't know if it was a problem with my computer or what. And I actually have just about every ControlBear version that had been released. This most current version though, requires that the phone be completely bone stock but unlocked. I know that the earlier versions actually required a rooted rom but this one is different. Take a look at the unlimited.io site for confirmation.
But my point is that you can get a phone back to stock without S-off or having to downgrade either. I know because I suffered through it. The only reason I only downgraded later after doing S-off was to get rid of the relocked and tampered message in the bootloader and then I just let the OTA do it's updates.

---

In order to get fully untampered stock you have to downgrade
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app

---

REV3NT3CH said:
In order to get fully untampered stock you have to downgrade
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I know. I'm fully aware of that.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
But to get a stock phone, you do not need to downgrade, just use that stock rooted rom and then use remove root by using the option in SuperSu that gets installed with that rom. And if you want to take it further then reinstall the stock recovery and you now have a fully stocked phone.

---

Here's a potential facepalm moment...
Did the op try 'fastboot flash boot boot.img' (after extracting the boot.img from the mod zip using winzip or winrar)? Cause with S-ON you have to flash the boot.img after loading a custom rom.

---

mikeyk101 said:
Yeah, I know. I'm fully aware of that.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
But to get a stock phone, you do not need to downgrade, just use that stock rooted rom and then use remove root by using the option in SuperSu that gets installed with that rom. And if you want to take it further then reinstall the stock recovery and you now have a fully stocked phone.
Click to expand...
Click to collapse
You do understand to be "stock" means no "tampered" or "relocked" or "unlocked" tags in hboot right? Stock phone will say "locked" S-On. Only way for our phone is to s-off for "locked" tag after unlocking and to remove "tampered" requires an official RUU, which is only downgrading as we do not have an official RUU for current OTA.
Sent fromy Liquid Smooth Rezound running 4.3

---

Uzephi said:
You do understand to be "stock" means no "tampered" or "relocked" or "unlocked" tags in hboot right? Stock phone will say "locked" S-On. Only way for our phone is to s-off for "locked" tag after unlocking and to remove "tampered" requires an official RUU, which is only downgrading as we do not have an official RUU for current OTA.
Sent fromy Liquid Smooth Rezound running 4.3
Click to expand...
Click to collapse
also i figured out why adb has been an issue for some people trying to fastboot and it slipped my mind...If your bootloader is locked it will not allow all fastboot commands including fastboot flashes...if anyone needs help unlocking their bootloader i can help and all you need to do is pm me

---

I think you guys are way overthinking this. I think we are splitting hairs over what the OP is talking about when he says he wants the phone returned to stock. The way I read it, the OP is just looking at getting his phone up and running and wants it to be "stock" as in not modded. He mentions that he has twrp recovery but makes no mention about wanting to have the stock recovery or locking his bootloader. Sure if you want a pure, able to return to Verizon for warranty phone with an unmolested truly stock ***Locked*** bootloader, then yes, the only way is to downgrade to S-off and use the full 3.14.605.12 RUU and then update OTA back to "fully stock" 4.05.605.14. But I don't think that is what the OP is asking for so to have a working "stock" phone that is fully functional, you do not have to downgrade.
I think we are all making assumptions. Maybe waiting for the OP to respond back would be helpful...

---

Hey guys,
Sorry for the slight threadjack but I didn't want to post a new thread while this one was out there.
I'm having trouble getting my Rezound back to stock as well. I was S-OFF and tried RUUing but it goes to ***RELOCKED*** instead of ***LOCKED***, so I can't get to completely stock. I've tried several different ways and I am having no success.
I need to send the phone back as a warranty replacement, so at this point I'm just looking to make the phone appear as ***LOCKED*** and S-ON. Despite a Verizon customer service lady telling me I had 150 days, just one month and they've charged me $450 for the device, so I need to get it sorted out.
I'm thinking I can RUU while S-OFF, then install custom HBOOT, then S-ON with that custom HBOOT and that might do the trick. However, the custom HBOOT needs to not be an engineering HBOOT because then S-ON will brick it.
Is there a custom HBOOT that will say ***LOCKED*** consistently that I can then S-ON without bricking the phone?
Thanks for any help you can give.

---

tigerxchaos said:
Hey guys,
Sorry for the slight threadjack but I didn't want to post a new thread while this one was out there.
I'm having trouble getting my Rezound back to stock as well. I was S-OFF and tried RUUing but it goes to ***RELOCKED*** instead of ***LOCKED***, so I can't get to completely stock. I've tried several different ways and I am having no success.
I need to send the phone back as a warranty replacement, so at this point I'm just looking to make the phone appear as ***LOCKED*** and S-ON. Despite a Verizon customer service lady telling me I had 150 days, just one month and they've charged me $450 for the device, so I need to get it sorted out.
I'm thinking I can RUU while S-OFF, then install custom HBOOT, then S-ON with that custom HBOOT and that might do the trick. However, the custom HBOOT needs to not be an engineering HBOOT because then S-ON will brick it.
Is there a custom HBOOT that will say ***LOCKED*** consistently that I can then S-ON without bricking the phone?
Thanks for any help you can give.
Click to expand...
Click to collapse
Just S-off again, it will make the locked tag.
Sent fromy Liquid Smooth Rezound running 4.3

---

Uzephi said:
Just S-off again, it will make the locked tag.
Sent fromy Liquid Smooth Rezound running 4.3
Click to expand...
Click to collapse
Yeah if you unlocked and relocked while s-off (which I did once /facepalm), then do the s-off procedure again, then run the ruu to return it completely to stock (if it isn't already on the ruu).
http://forum.xda-developers.com/showthread.php?t=2453701 <- Just start from wherever you are currently at. Be careful not to s-on unless you are fully 100% stock ruu.

---

flamewalker said:
Yeah if you unlocked and relocked while s-off (which I did once /facepalm), then do the s-off procedure again, then run the ruu to return it completely to stock (if it isn't already on the ruu).
http://forum.xda-developers.com/showthread.php?t=2453701 <- Just start from wherever you are currently at. Be careful not to s-on unless you are fully 100% stock ruu.
Click to expand...
Click to collapse
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?

---

I just replied to your post in the other fourm with the same information as above.
When you ruu it will replace the bootloader with the one in the ruu. It should not matter if you are locked or unlocked. You have to be unlocked to s-off any way. I don't quite remember if it auto locks when you run the ruu. If it does just unlock.
Sent from my Infected Rezound using xda app-developers app

---

tigerxchaos said:
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?
Click to expand...
Click to collapse
So my understanding is that you are currently S-Off? Are you on stock rom now or?
Yes. Hboot and recovery all get replaced with RUU. RUU will also relock. Then do the part to s-on after, ONLY after you are successfully booting a full RUU.
Good luck
---------- Post added at 08:58 AM ---------- Previous post was at 08:07 AM ----------
tigerxchaos said:
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?
Click to expand...
Click to collapse
Just to reiterate... Per the s-on instructions, DO NOT S-ON ON ANYTHING OTHER THAN A FULL RUU! You will hard brick your device if you s-on on anything other than a full RUU.