Database Develop

[q] need help want to go back to stock rom

Hey all Ive opened a few threads and looked at a few threads regarding wanting to go back to stock but im a noob and find somethings confusing in the guides people put up. My phone is a HTC ONE UL from rogers fully unlocked with revone soff and running ARHD 30. i would liek to go back to stock. been noticing some things lagging on my phone and i dont have a recovery as my pc which had the recovery crapped out on me.. cant find a RUU for my phone with the .exe i can only find it with .tar
can anyone help me?
thanks

crisgq27 said:
Hey all Ive opened a few threads and looked at a few threads regarding wanting to go back to stock but im a noob and find somethings confusing in the guides people put up. My phone is a HTC ONE UL from rogers fully unlocked with revone soff and running ARHD 30. i would liek to go back to stock. been noticing some things lagging on my phone and i dont have a recovery as my pc which had the recovery crapped out on me.. cant find a RUU for my phone with the .exe i can only find it with .tar
can anyone help me?
thanks
Click to expand...
Click to collapse
Well honestly I have to say I find it very strange people wanting to go back to stock, I run ARHD 13.3 and LOVE it much better than stock.
But anyway, can you also post a "fastboot getvar all" (remove IMEI and s/n)

i want to go back so i can update my firmware... was trying to do it with fastboot but was having issues... i dont know if its because im on arhd 30 but it kept on failing on loading the firmware zip saying something about my cid

crisgq27 said:
i want to go back so i can update my firmware... was trying to do it with fastboot but was having issues... i dont know if its because im on arhd 30 but it kept on failing on loading the firmware zip saying something about my cid
Click to expand...
Click to collapse
You mentioned you are S-Off, KEEP THAT!!, firmware flashing is VERY easy with S-Off check @vomer's thread: http://forum.xda-developers.com/showthread.php?t=2365506

yea i followed his steps and was getting the fail in loading the firmware

crisgq27 said:
yea i followed his steps and was getting the fail in loading the firmware
Click to expand...
Click to collapse
can it wait till tomorrow? I'm really getting :cyclops: running two threads at the same time. sorry.
I'm sure someone will come along shortly and help out, if not, I'll be back for you tomorrow.
Hit the thanks button, if you feel I've helped out

yea man no prob

crisgq27 said:
yea man no prob
Click to expand...
Click to collapse
Thanks for the Thanks, I'll be back tomorrow. In the meantime, can you post the actual error(s) you were getting. a copy/paste of your command prompt (from beginning to end) would be very helpful

crisgq27 said:
yea man no prob
Click to expand...
Click to collapse
hey man, did you get it solved, or still stuck?

yea still stuck but i had a busy weekend and work has been busy soo i havent bothered to try yet... i was reading that i should go back to ARHD 4.2.2 Rom some people say if you're in a 4.3 rom it wont work on adb command prompt

crisgq27 said:
yea still stuck but i had a busy weekend and work has been busy soo i havent bothered to try yet... i was reading that i should go back to ARHD 4.2.2 Rom some people say if you're in a 4.3 rom it wont work on adb command prompt
Click to expand...
Click to collapse
yeah adb has some issues with 4.3, but I think the updated HTC drivers v4.8.xxxx seem to work, I don't have the link, but sure a search should get you there.
but anyway, you were having firmware problems, right? those are flashed using fastboot, which works fine.
whenever you have time, explain what you want to achieve and where you're getting stuck. copy/paste of the command prompt would help

sorry meant the fastboot from command prompts that some phones with 4.2.2 firmware and on 4.3 rom the fastboot doesnt like that

crisgq27 said:
sorry meant the fastboot from command prompts that some phones with 4.2.2 firmware and on 4.3 rom the fastboot doesnt like that
Click to expand...
Click to collapse
i'm pretty sure fastboot (in command prompt) is fine irrelevant of firmware and rom version.

you would think lol i was doing some google searches on my issues and thats what some people were saying

crisgq27 said:
you would think lol i was doing some google searches on my issues and thats what some people were saying
Click to expand...
Click to collapse
can you copy/paste your command prompt? also have you confirmed the firmware you downloaded is not corrupt.

i downloaded it straight from vomer. i may try the latest 4.2.2 driver first and when i get a chance ill post up my command prompt

C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.17.3250.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.631.4
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: ROGER001
INFObattery-status: good
INFObattery-voltage: 4236mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.150s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Unknown error))
finished. total time: 5.550s
C:\adb>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (1045 KB)... OKAY [ 0.419s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.906s
C:\adb>

crisgq27 said:
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (1045 KB)... OKAY [ 0.419s]
Click to expand...
Click to collapse
That doesn't sound right, 1MB. firmware packages are usually around between 20MB to 40MB. probably a bad download. download again, and check MD5 sum preferably.

after getting my cid to 111111111 it worked lol

crisgq27 said:
after getting my cid to 111111111 it worked lol
Click to expand...
Click to collapse
did fastboot getvar all confirm the updated firmware version? sounds really strange for a firmware package to be 1MB, IMHO

Converting Play Edition to Sense Developer Edition?

Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?

hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.

fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.

hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.

fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?

Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.

hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app

Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.

hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One

I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse

Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One

The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?

hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick

gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.

hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.

gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.

hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).

Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.

hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app

gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?

HTC One cannot use stock RUU

I have an HTC One that feels kinda bricked as it won't run a stock RUU (keeps giving me bootloader version error)
Here's what I have on the bootloader screen:
Tampered
Relocked
M7 WLS PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 1.00.20.0315
OPENDSP V32.120.274.0909
OS 3.05.651.6
I've tried with several stock RUU files, but I imagine they don't work because it's not S-OFF so I can't downgrade as I please.
Then I try with this file: RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2
which seems to be the current OS installed and the file doesn't work, it just quits on its own. Running Windows 7 64x.
I've downloaded the same file a few times (from an XDA thread, no less) and it won't budge.
Any ideas?

Try a different cable
Different USB port
USB 2 works the best

The installer quits (crashes?) right after I accept the terms of user blah blah agreement. Way before I have anything plugged in.

Pigbenis12 said:
The installer quits (crashes?) right after I accept the terms of user blah blah agreement. Way before I have anything plugged in.
Click to expand...
Click to collapse
Have you tried it with the device plugged in?
Also right click and run as admin

Yep, it will just crash and I need to run again. Maybe I'll look from a different download source.

Pigbenis12 said:
I have an HTC One that feels kinda bricked as it won't run a stock RUU (keeps giving me bootloader version error)
Here's what I have on the bootloader screen:
Tampered
Relocked
M7 WLS PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 1.00.20.0315
OPENDSP V32.120.274.0909
OS 3.05.651.6
I've tried with several stock RUU files, but I imagine they don't work because it's not S-OFF so I can't downgrade as I please.
Then I try with this file: RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2
which seems to be the current OS installed and the file doesn't work, it just quits on its own. Running Windows 7 64x.
I've downloaded the same file a few times (from an XDA thread, no less) and it won't budge.
Any ideas?
Click to expand...
Click to collapse
You are going to have to wait for the new RUU to come out, from what TommyJones has said soon. If you had S-off you could run the KK to JB downgrade, then run the RUU found here: http://forum.xda-developers.com/showthread.php?t=2634256
Why do you need to run the RUU? If you are having errors, can you do a hard reset?

weidnerj said:
You are going to have to wait for the new RUU to come out, from what TommyJones has said soon. If you had S-off you could run the KK to JB downgrade, then run the RUU found here: http://forum.xda-developers.com/showthread.php?t=2634256
Why do you need to run the RUU? If you are having errors, can you do a hard reset?
Click to expand...
Click to collapse
I need to run the RUU because there's no functional OS installed. It was given to me like this, unfortunately.
It's a project, so to speak.

Sure the drivers are installed correctly?

I have the latest HTC Sync installed.
C:\Android>fastboot flash zip firmware6516.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1174208 KB)...
OKAY [ 56.854s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.952s
This is the zip method.

Pigbenis12 said:
I have the latest HTC Sync installed.
C:\Android>fastboot flash zip firmware6516.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1174208 KB)...
OKAY [ 56.854s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.952s
This is the zip method.
Click to expand...
Click to collapse
Check PM

Seen, read, replied.

Having the same issue
Pigbenis12 said:
Seen, read, replied.
Click to expand...
Click to collapse
Could you please post it here if you ever have got it to work ?

[HELP] Unable to return 100% stock

Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.

slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's

slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
list of ruu for your phone:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
dont use the 1.20.401.1 ruu, its a pre-release version with no ota updates.

Seanie280672 said:
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's
Click to expand...
Click to collapse
I didn't realise that it was just the firmware.
alray said:
[...] omissis [...]
Click to expand...
Click to collapse
I will try to flash the exe you have linked as soon as I get back from my holidays.
Thank you guys! I've really appreciated your help.

I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:

Mickey Meyers said:
I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:
Click to expand...
Click to collapse
and that's the easy way ?........lol, took him 10 mins to lock his bootloader, the easy way is to reboot to your bootloader and type fastboot oem lock, 2 seconds its done, that applies to firmware flashes, ruu flash commands and then to s-on too.

alray said:
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
Click to expand...
Click to collapse
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.

slvrbllt said:
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.
Click to expand...
Click to collapse
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer

alray said:
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer
Click to expand...
Click to collapse
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?

slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?
Click to expand...
Click to collapse
How about trying a Guru Reset 5.11.401.10 you will have to unlock your bootloader and put TWRP back on your phone to flash it. It should take you back to stock and at the end it will ask you if you want to root. If you want to go complete stock just select the no option.

majmoz said:
How about trying a Guru Reset 5.11.401.10
Click to expand...
Click to collapse
I will.
But wasn't I supposed to flash any RUU I like given I'm S-OFF ?!?!
I would like to figure out why my device isn't flashing the stock ruu at all...

slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
[B][COLOR="Red"]sending 'zip' (1009784 KB)...[/COLOR][/B]
Any other hints ?[/QUOTE]
you should have checked MD5, the actual filesize is 1009792KB
here's an AFH mirror: [URL="https://www.androidfilehost.com/?fid=23329332407584993"]RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7[/URL]
Click to expand...
Click to collapse

nkk71 said:
you should have checked MD5, the actual filesize is 1009792KB]
Click to expand...
Click to collapse
You're right! I extracted the rom.zip from the ruu but did not decrypted it.
The one you have suggested worked fine.
I'm back stock now.
Thank you everybody for your help.
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers

slvrbllt said:
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers
Click to expand...
Click to collapse
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
I'm glad it worked for you, but I would highly recommend against that, because the firmware upgrades (within the OTAs) are incremental, so skipping versions could potentially miss important upgrades within the firmwares, or even worse send you into QHSUSB_DLOAD mode
eg, assuming you installed a 4.xx Guru Reset ROM, and took OTA update to 5.xx, then there's a high chance you would have ended in QHSUSB_DLOAD mode, because the 5.xx firmware (inside the OTA) is missing SBL3

nkk71 said:
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
Click to expand...
Click to collapse
Well, after having flashed 1.28.401.7 (I was on latest GPE before), it started downloading a few OTAs (if I recall well, I applied all otas up to version 2.x).
It took me 1.5hrs to get to this point, so I gave up and installed the Guru Reset 5.11.401.10 instead.
Upon reboot it downloaded the latest OTA and jumped straight to 6.09.401.5.
The smartphone seems to be working fine. How can I be sure that all the required pieces are in place?

[Q] Need help desperately - Back to stock

I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?

I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.

Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!

raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.

Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?

Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer

So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.

raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).

BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?

Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU

So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.

Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)

BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".

Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!