Database Develop

[Q] Revert to stock

Not sure if I am in the right place to ask this question, well, i'll ask anyway.
I unlocked my bootloader using Revolutionary. I now need to revert to stock for warranty. I downloaded the INDIA RUU from goo manager.
I managed to replace the Revolutionary HBOOT by changing mainver. However, my radio is not getting replaced, no matter what I try. As a result, my phone bootloops though the RUU install was successful. So I had to revert to Revolutionary by installing WWE ASIA RUU. This was successful because the Radios are the same ie 3805.04.03.27_M.
I am currently on
HBOOT - 6.13.1002
Radio-3805.04.03.27_M
How can I go back to HBOOT 1.13 and Radio 38.02.01.11_M?

HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.

Inferi0r said:
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Click to expand...
Click to collapse
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.

craynet said:
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
Click to expand...
Click to collapse
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.

fastboot....

tpbklake said:
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
Click to expand...
Click to collapse
yeah, you are right...i now remember that this will brick my phone, a risk not worth taking.

just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?

skinniezinho said:
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
Click to expand...
Click to collapse
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.

tpbklake said:
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
Click to expand...
Click to collapse
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
exnerjan said:
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Click to expand...
Click to collapse

skinniezinho said:
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
Click to expand...
Click to collapse
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.

tpbklake said:
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
Click to expand...
Click to collapse
So I do I do?
edit:
Just found it:
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1705913

Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"

skinniezinho said:
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
Click to expand...
Click to collapse
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.

tpbklake said:
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
Click to expand...
Click to collapse
do you know wich one is it?for wwe phone.

skinniezinho said:
do you know wich one is it?for wwe phone.
Click to expand...
Click to collapse
wwe -> 2.30.405.1

[Q] Fastboot freezez...Help required

I am S OFF, UNLOCKED.
When I boot into bootloader and into fastbootmode, as soon as i connect the cable to my phone, the fastboot USB mode freezez... No keys work that time...I have to press and hold power button for a few seconds in order to reboot the phone. This happen always with me.
I wanted to backup my Stock recovery by booting into custom recovery using this command fastboot boot name_of_your_custom_recovery.img . It sends the recovery and everything is okay on the PC, but nothing happens on the phone.
But I did flash the unlock.bin via fastboot, that way it works....I am not getting what the problem is.
I need to backup my STOCK RECOVERY (HTC CID_J15) before flashing CWM.
ANy help would be appreciated.

mathrania said:
I am S OFF, UNLOCKED.
When I boot into bootloader and into fastbootmode, as soon as i connect the cable to my phone, the fastboot USB mode freezez... No keys work that time...I have to press and hold power button for a few seconds in order to reboot the phone. This happen always with me.
I wanted to backup my Stock recovery by booting into custom recovery using this command fastboot boot name_of_your_custom_recovery.img . It sends the recovery and everything is okay on the PC, but nothing happens on the phone.
But I did flash the unlock.bin via fastboot, that way it works....I am not getting what the problem is.
I need to backup my STOCK RECOVERY (HTC CID_J15) before flashing CWM.
ANy help would be appreciated.
Click to expand...
Click to collapse
Not sure about your fastboot issue, but just an FYI if you have upgraded your firmware and now have hboot 1.54 you can no longer use the command
Code:
fastboot boot name_of_your_custom_recovery.img
to boot to a non installed recovery. That can only be done with the older 1.44 hboot.
Since you have s-off, if you can get fastboot working, you should be able to flash hboot 1.44 if you the need the ability to boot a non installed recovery.

crushalot said:
Not sure about your fastboot issue, but just an FYI if you have upgraded your firmware and now have hboot 1.54 you can no longer use the command
Code:
fastboot boot name_of_your_custom_recovery.img
to boot to a non installed recovery. That can only be done with the older 1.44 hboot.
Since you have s-off, if you can get fastboot working, you should be able to flash hboot 1.44 if you the need the ability to boot a non installed recovery.
Click to expand...
Click to collapse
Yes, hboot 1.54....so how do i ensure i have stock recovery backup before flashing CWM?
Sent from my HTC One using xda premium

mathrania said:
Yes, hboot 1.54....so how do i ensure i have stock recovery backup before flashing CWM?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Could go a few different routes. First there are tons of users who posted the stock recovery on XDA and other sites. Also it could be pulled from the RUU if you device has one or one of the posted nandroid backups. (http://forum.xda-developers.com/showthread.php?p=39588860)
This site has the original retail dump which has the stock recovery:
http://www.modaco.com/topic/361407-htc-one-retail-release-dump/
You have s-off, so you can downgrade back to hboot 1.44 and boot a custom recovery. Just flash the stock 1.44 hboot from here:
http://forum.xda-developers.com/showthread.php?t=2316726
When finished you can leave hboot 1.44 or flash back up to 1.54.
Lastly if you have root you can look around (Will have to search) for how to pull the recovery.img like a system dump.
Best of luck.

crushalot said:
Could go a few different routes. First there are tons of users who posted the stock recovery on XDA and other sites. Also it could be pulled from the RUU if you device has one or one of the posted nandroid backups. (http://forum.xda-developers.com/showthread.php?p=39588860)
This site has the original retail dump which has the stock recovery:
http://www.modaco.com/topic/361407-htc-one-retail-release-dump/
You have s-off, so you can downgrade back to hboot 1.44 and boot a custom recovery. Just flash the stock 1.44 hboot from here:
http://forum.xda-developers.com/showthread.php?t=2316726
When finished you can leave hboot 1.44 or flash back up to 1.54.
Lastly if you have root you can look around (Will have to search) for how to pull the recovery.img like a system dump.
Best of luck.
Click to expand...
Click to collapse
Is the stock recovery same for all HtC One?? I mean also the 1.29.x.x and 2.24.x.x are same too?
Sent from my HTC One using xda premium

mathrania said:
Is the stock recovery same for all HtC One?? I mean also the 1.29.x.x and 2.24.x.x are same too?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
No there are differences for some of the different models and carriers. You will have to match your CID to one of the nandroids or find the proper RUU.
The stock recovery was updated in 2.24 I think, but I am not positive since I didn't ever use it.
It will only take a few minutes to flash the hboot to 1.44 so that you can boot a recovery and take a backup for yourself. I would recommend that method.

crushalot said:
No there are differences for some of the different models and carriers. You will have to match your CID to one of the nandroids or find the proper RUU.
The stock recovery was updated in 2.24 I think, but I am not positive since I didn't ever use it.
It will only take a few minutes to flash the hboot to 1.44 so that you can boot a recovery and take a backup for yourself. I would recommend that method.
Click to expand...
Click to collapse
Yes, but i am afraid to do it.... Might brick my phone....
Sent from my HTC One using xda premium

mathrania said:
Yes, but i am afraid to do it.... Might brick my phone....
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Um, not sure where your getting that but just flashing stock hboots will not brick your phone. I have switched my hboot around between like 4 different versions 10+ times to test some things after the firmware upgrades.
Even the modified one are no problem.
Oh well. Good luck.

Please help, possible brick after following guide to flash firmware

I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.

And what the HBOOT version you wanted to downgrade to?

Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?

Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk

Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?

vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.

Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......

Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One

[Q] s-off from recovery (TWRP, CWM)

My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?

ergosteur said:
My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?
Click to expand...
Click to collapse
Why your phone is stuck in ruu mode if there is no ruu for your phone?

alray said:
Why your phone is stuck in ruu mode if there is no ruu for your phone?
Click to expand...
Click to collapse
I restored it back to stock (or so I thought), but when I tried installing the 4.3 OTA the phone got stuck in bootloop and eventually just stuck in ruu.

ergosteur said:
My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?
Click to expand...
Click to collapse
I come from China, I can solve your problem, you can contact QQ990128461, or email [email protected]

wudan120 said:
I come from China, I can solve your problem, you can contact QQ990128461, or email [email protected]
Click to expand...
Click to collapse
What's your problem? Just trolling around, or do you actually have something to contribute??
http://forum.xda-developers.com/showpost.php?p=51284986&postcount=3
http://forum.xda-developers.com/showpost.php?p=51285277&postcount=2
http://forum.xda-developers.com/showpost.php?p=51466900&postcount=7

OK, total stupid moment.
All I had to do was restore a stock nandroid for my CID (found on http://www.htc1guru.com/) using recovery booted via fastboot boot [cwm filename].img.
Then, run fastboot oem boot.
Found last command on: http://forum.xda-developers.com/showthread.php?t=1612969
Guess i got scared by the warning triangles. :victory:
Looks like the "modem" partition is still corrupted, so I have to run fastboot oem boot every time I boot the phone. But, now I should be able to boot a rom, get root, and s-off the regular way.
Also I actually was S-ON with a locked bootloader - managed to do the HTCdev unlock "blind" while in the ruu mode.

[Q] going back to stock - cannot fastboot boot recovery

Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.

xerockz said:
Trying to return my one back to stock (unlocked, s-off) to send in for purple tint repair.
I tried a few different methods involving the RUUs but never had any luck:
1. The RUU.exe for my specific phone (telus), always crashed when htc_fastboot.exe stopped responding.
2. Since there was no RUU.zip for the Telus version I extracted it out of the exe and tried flashing manually, but again fastboot stops responding.
3. Tried changing the CID to CWS__001 and using the matching RUU.exe, and while fastboot didn't crash it wasn't able to complete either (can't remember the exact error).
So I decided to use the Telus Guru Reset from htc1guru, which worked fine.
Now I need to get rid of the tampered flag and lock bootloader/s-on, but I can't boot a custom recovery with fastboot boot recovery.img.
I need to boot into recovery to either use the guru bootloader reset tool or to temporarily install superuser, so that I can manually remove the tampered flag.
Tried the latest version of both TWRP and CWM Touch, and also tried fastboot erase cache before each.
Every time fastboot succesfully pushes the img to the phone and outputs booting..., OKAY, and finished, but the phone gets stuck at the bootloader and never actually boots to the recovery (have to force power off).
Any ideas/help would be greatly appreciated.
Click to expand...
Click to collapse
boot recover has not worked sense hboot 1.44

clsA said:
boot recover has not worked sense hboot 1.44
Click to expand...
Click to collapse
I guess that explains the problem as I am on 1.57. Just re-flashed that guru reset, and checked the option to install superuser and busybox this time so now I should be able to fix the tampered flag and lock, without having to worry about booting to a custom recovery.

Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.

xerockz said:
Okay so I got it locked and tampered removed, however I cannot remove Superuser.apk, the su binary, or busybox now that my bootloader is locked (using adb shell, su, rm -r /system/app/Superuser.apk). Tried factory reseting and the files are still there, not sure how I can get rid of them!
edit: I've found this old post, not sure if it's still relevant, or exactly what it's doing.
Click to expand...
Click to collapse
Why not just run the Guru Reset again and select stock recovery and no root.

@xerockz try to install SuperSU app from Play Store. Open it and let update the binaries (normal!) and if successfull, you will after reboot get able to unroot for good in the app.
tetakpatalked from N7100

Hey guys, thanks for the suggestions. I ended up getting it all back to stock.
I believe the reason the RUUs weren't working was because I was on hboot 1.57.
I flashed 1.44 and then was unable to get fastboot to recognize the device under windows 8.1 (common driver issue apparently). I couldn't be bothered to try to fix the driver issue so I booted into a live Fedora usb which then let me use fastboot and flash the appropriate ruu.zip.
Now the ruu had hboot 1.55 so I was once again unable to fastboot boot recovery.img.
I ended up flashing TWRP again, trying the guru bootloader reset over and over, (for tampered and lock) wiped cache/dalvik, still wouldn't work.
Finally got it to work after fastboot format cache.
Now I was locked and no tampered flag, but still had TWRP flashed.
Tried pulling the signed_recovery.img out of the RUU zip and flashing it but obviously that doesn't work since I was locked at this point.
So I just flashed the entire RUU again, which fortunately worked even though I was locked.
Now I just had to S-ON, update OTA, and factory reset (through sense settings) and I'm completely back to stock.
14 hours of headache later and I finally got this thing reset.
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.

xerockz said:
It's unfortunate the return to stock guides fail to mention the RUUs don't work if you are on a newer hboot, and also that you need/can flash the RUU AFTER fixing tampered/locking.
Click to expand...
Click to collapse
beg to differ [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
but glad you got everything sorted out :good: :good: