[Q] Problem restoring to stock - AT&T HTC One (M7)

** UPDATE **
Got past the stuck screen by doing this:
http://forum.xda-developers.com/showthread.php?t=2386084 Jeez.
Tried to install the .12 RUU but this failed repeatedly with an error 155. Wasn't sure if this was caused by a newer HBOOT or a different firmware. Downloaded a KK RUU from here:
http://forum.xda-developers.com/showthread.php?t=2428276
Almost back to stock. Now need to get rid of the RELOCKED message in the bootloader. Will attack that later.
I'm trying to get my phone back to stock so I can return it to AT&T due to the purple camera problem. What I was attempting to do was to restore a 4.1.2 JB nandroid backup, then install an RUU as described in post #55 here:
http://forum.xda-developers.com/showthread.php?t=2394155&page=6
I had changed the cid number back to CWS__001 and restored the nandroid backup. When I went to reboot the phone I got the AT&T animation, then the HTC One screen. This is where I'm stuck. I can't reboot into recovery or anything. Is this phone recoverable or am I SOL? Thanks for any help.
These were my settings before I started this.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s

---

Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe

---

I'm also trying to revert to stock in order to return to HTC for purple tint issue. I am running an AT&T HTC One.
Originally, I followed the instructions on this thread and basically converted my phone to GPE (http://forum.xda-developers.com/showthread.php?t=2358781).
To revert to stock I followed these instructions (http://www.htc1guru.com/guides/return-stock-guide/) multiple times and kept failing getting the error 155 message. I was using the RUU.exe file. Eventually I got stuck and decided to follow another post on a different site. That post had me re-lock the bootloader and rever to S-ON. Then all went to hell. Bootloop city.
I was able to load TWRP recovery and I side-loaded a different ROM that I had from when I was first tinkering around with custom ROMs (the one described here http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/). It booted but threw tons of errors and was unusable. So, I re-unlocked my bootloader (still S-ON) and this time ran the RUU.exe (named RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe). Only instead of run through the GUI I tried to use fastboot to load the rom.zip that was extracted to a temp folder. It ran but ended up failing with the error "FAILED (status read failed (Too many links))."
I believe I then reinstalled the rom from (http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/) and now it it boots and is "working."
Here is where I am at:
TAMPERED
UNLOCKED
S-ON
hboot 1.54
TWRP 2.6.3.3 recovery (note: when I boot into recovery i see a Google logo with an unlocked padlock)
this ROM, rooted: http://downloadandroidrom.com/file/HTCOne/M7/roms/Sense4.4/One_4.06.1540.2_odexed.zip
When I boot the system from power off I get the htc animation with no other warning text
If I boot the system from TWRP recovery I first get the Google logo with an unlocked padlock, followed by the htc animation with no other warning text.
I assume I need to go back to S-OFF, lock the bootloader and run an RUU, but I'm concerned about the error 155, as well as the "too many links" error.
Here is the log from the RUU.exe that fails:
Code:
<T135636><DEBUG><CMD>htc_fastboot -s H******* -d flash zip C:\Users\o****\AppData\Local\Temp\{A08E6688-8B3D-493C-BEF3-013152BF8F99}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T135636>
<T135844><DEBUG><OUT>sending 'zip'... (1029872 KB) OKAY</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) signature checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing start ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing finish ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip header checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip info parsing...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>FAILED (status read failed (Too many links))</OUT>
</DEBUG></T135844>
<T135927><DEBUG><CMD>adb kill-server</CMD>
Code:
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Any help would be greatly appreciated.

---

cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
Click to expand...
Click to collapse
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.

---

ZBell said:
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.
Click to expand...
Click to collapse
If you don't mind, which RUU specifically?

---

ocieb said:
If you don't mind, which RUU specifically?
Click to expand...
Click to collapse
this is the only kitkat RUU for AT&T
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe

---

clsA said:
this is the only kitkat RUU for AT&T
Click to expand...
Click to collapse
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.

---

ocieb said:
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.
Click to expand...
Click to collapse
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me

---

clsA said:
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me
Click to expand...
Click to collapse
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!

---

ocieb said:
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35GW916488
(bootloader) imei: 354439055183836
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!
Click to expand...
Click to collapse
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe

---

clsA said:
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Thanks, I'll try this. Should it matter that I'm relocked and S-ON?
Also, I want to run this exe while my phone is connected to my computer and un fastboot usb, correct?
---------- Post added at 07:14 PM ---------- Previous post was at 06:51 PM ----------
Hi again,
Just failed both using the exe and extracting the rom.zip file. Any advice?
I was thinking of trying to go back to full GPE and either starting over, or just sending the device in like that and keeping my fingers crossed

---

cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.

---

sharksfan7 said:
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.
Click to expand...
Click to collapse
Locked bootloader is not require to RUU when s-off. OP just wanted to remove relocked.