Database Develop

[Q] HTC One Three

Hi Guys, I'm not really a advanced user but i require help in an easy to understand guide. I have a htc one which was on three uk, i changed to a google edition and then backed up back to sense through recovery. However, i now cannot install updates when i do try installing them it takes me to the recovery screen. how do i go back to actual stock rom? would be great help. this is the image that i have took in terminal on my mac of the device as it has all the information there. thanks guys would appreciate it.

John90uk said:
Hi Guys, I'm not really a advanced user but i require help in an easy to understand guide. I have a htc one which was on three uk, i changed to a google edition and then backed up back to sense through recovery. However, i now cannot install updates when i do try installing them it takes me to the recovery screen. how do i go back to actual stock rom? would be great help. this is the image that i have took in terminal on my mac of the device as it has all the information there. thanks guys would appreciate it.
Click to expand...
Click to collapse
Just flash a HTC stock rom in recovery.
Here is a link to the stock rom:
http://forum.xda-developers.com/showthread.php?t=2224752

Thanks for the reply, how do i actually flash it? What software do i need?

There is an app in play store callad .. flashify .. just download it and also download the recovery.img file from the link given in above reply and just flash that recovery image with that app... and done ... you have stock recovery now....
Sent from my GT-S5302 using xda premium

Thanks mate, will I need to put recovery files onto the phone storage first? Currently my phone is rooted by following your method will it become unrooted? I assumed I had to go through boot loader and command prompts in order to put stock ROM. Thanks for the help

John90uk said:
Thanks mate, will I need to put recovery files onto the phone storage first? Currently my phone is rooted by following your method will it become unrooted? I assumed I had to go through boot loader and command prompts in order to put stock ROM. Thanks for the help
Click to expand...
Click to collapse
If you flash the revolution stock it will become unrooted, but you can re-root afterwards. To flash it you can put the zip on your internal storage (/sdcard) and then boot to recovery. I assume you have either TWRP or CWM installed? From there you can install the stock ROM.
I have a Three HTC One too and am running the GPE Revolution ROM without any issues. Are the updates you are trying to install for the ROM or for apps?

I cant remember which one it was i think it was TWP? How do i find out? I was getting a software update, thats why i want to go back to unrooted. So if i use flashify and the ROM it should work?
Do i only put the odexed zip file onto the storage? What about the recovery img file?
svenito said:
If you flash the revolution stock it will become unrooted, but you can re-root afterwards. To flash it you can put the zip on your internal storage (/sdcard) and then boot to recovery. I assume you have either TWRP or CWM installed? From there you can install the stock ROM.
I have a Three HTC One too and am running the GPE Revolution ROM without any issues. Are the updates you are trying to install for the ROM or for apps?
Click to expand...
Click to collapse

John90uk said:
I cant remember which one it was i think it was TWP? How do i find out? I was getting a software update, thats why i want to go back to unrooted. So if i use flashify and the ROM it should work?
Do i only put the odexed zip file onto the storage? What about the recovery img file?
Click to expand...
Click to collapse
From the top of the ARHD post:
With odexed version you can download and flash OTA from HTC (you need stock boot.img and recovery.img as well)
Click to expand...
Click to collapse
So if you want to receive over the air updates (OTA) you need the recovery and boot. I don't know where you get the boot from, but I am sure you can find it if you look for it.
Here's some info on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showpost.php?p=45432325&postcount=2
It's probably just a software update for the ROM that's failing. Go back to stock if you want, but you might want to try ARHD which works really well, and is a very popular, near stock ROM.

John90uk said:
Hi Guys, I'm not really a advanced user but i require help in an easy to understand guide. I have a htc one which was on three uk, i changed to a google edition and then backed up back to sense through recovery. However, i now cannot install updates when i do try installing them it takes me to the recovery screen. how do i go back to actual stock rom? would be great help. this is the image that i have took in terminal on my mac of the device as it has all the information there. thanks guys would appreciate it.
Click to expand...
Click to collapse
All that stuff won't work for you, you are on H3G__001 (2.24.771.3), the .401. roms wont get you any OTAs.
Just flash this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
Here's a small walkthrough: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44 EXCEPT in your case select "stock recovery" and "stock radio", to get OTAs
My humble opinion.
Hit the thanks button if I've helped

nkk71 said:
All that stuff won't work for you, you are on H3G__001 (2.24.771.3), the .401. roms wont get you any OTAs.
Just flash this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
Here's a small walkthrough: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44 EXCEPT in your case select "stock recovery" and "stock radio", to get OTAs
My humble opinion.
Hit the thanks button if I've helped
Click to expand...
Click to collapse
Sounds like the most sensible solution... Useful for me to, just in case.
Thanks!

svenito said:
Sounds like the most sensible solution... Useful for me to, just in case.
Thanks!
Click to expand...
Click to collapse
Yeah, but I really don't understand why so many want to return to stock, with those amazing custom ROMs around. Then again, not my call.

nkk71 said:
Yeah, but I really don't understand why so many want to return to stock, with those amazing custom ROMs around. Then again, not my call.
Click to expand...
Click to collapse
Me neither, but if that's what they want to do....

I am currently also running Google Edition OS and obviously changed the CID(GOOGLE001 I believe)
http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
Basically I need to swap my phone with Three, so could you please confirm the above method will work for me to?
Thanks in advance guys.

Jimzoaar said:
I am currently also running Google Edition OS and obviously changed the CID(GOOGLE001 I believe)
http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
Basically I need to swap my phone with Three, so could you please confirm the above method will work for me to?
Thanks in advance guys.
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), just to see your details

nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n), just to see your details
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *****************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you, hope this is what you were after.

Jimzoaar said:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
Click to expand...
Click to collapse
To answer you quickly: no, same procedure won't work, yours is going to be a bit longer and slightly tougher, but you have S-Off, so it's doable.
Just to confirm, you want to go back to original Three UK (CID H3G__001) Sense 5 based ROM? If so you'll have to give me a bit of time to write things up for you.
Out of curiosity: why would you want to go back to stock

nkk71 said:
To answer you quickly: no, same procedure won't work, yours is going to be a bit longer and slightly tougher, but you have S-Off, so it's doable.
Just to confirm, you want to go back to original Three UK (CID H3G__001) Sense 5 based ROM? If so you'll have to give me a bit of time to write things up for you.
Out of curiosity: why would you want to go back to stock
Click to expand...
Click to collapse
I would really appreciate that if you can find the time.
Yes I literally want it as I opened it out of the box. This is only because I need to return to store due to dead pixels. I literally do not want Three or HTC to be able to tell I modified a thing?

Jimzoaar said:
I would really appreciate that if you can find the time.
Yes I literally want it as I opened it out of the box. This is only because I need to return to store due to dead pixels. I literally do not want Three or HTC to be able to tell I modified a thing?
Click to expand...
Click to collapse
OK, gimme a bit of time, while I write things up for you....
---------- Post added at 06:45 PM ---------- Previous post was at 05:52 PM ----------
Jimzoaar said:
I would really appreciate that if you can find the time.
Yes I literally want it as I opened it out of the box. This is only because I need to return to store due to dead pixels. I literally do not want Three or HTC to be able to tell I modified a thing?
Click to expand...
Click to collapse
It's gonna take me a while to write things up, sort of busy with someone else right now (sorry), but in the meantime can you download the following files
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/

nkk71 said:
OK, gimme a bit of time, while I write things up for you....
---------- Post added at 06:45 PM ---------- Previous post was at 05:52 PM ----------
It's gonna take me a while to write things up, sort of busy with someone else right now (sorry), but in the meantime can you download the following files
That is not a problem please do not rush yourself. I am in the process of speaking with Three about a solution to this (so I am not without a phone for a few weeks) and so expect that to take at least this week to get solved anyway.
Thanks again.
Click to expand...
Click to collapse

Jimzoaar said:
That is not a problem please do not rush yourself. I am in the process of speaking with Three about a solution to this (so I am not without a phone for a few weeks) and so expect that to take at least this week to get solved anyway.
Thanks again.
Click to expand...
Click to collapse
First off: the below procedure is going to wipe everything off your phone, so backup anything you need to your PC!!
Step 1: go back to Sense 5 Stock
fastboot oem writecid HTC__001 (two underscores)
fastboot reboot-bootloader
-> and confirm CID is HTC__001
Run the following RUU, to downgrade to stock Sense 5: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
This will completely return you to 100% stock Sense 5, but European unbranded version.
Step 2: go back to H3G__001
fastboot oem writecid H3G__001
fastboot reboot-bootloader
-> and confirm CID is back to H3G__001
Step 3: restore H3G nandroid
download CWM from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
you should now be in CWM recovery.
download this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/
extract the zip on your PC, it will give you a folder called "2013-04-20.21.00.00" place it in your adb folder then push it:
adb push 2013-04-20.21.00.00 /data/media/clockworkmod/backup/2013-04-20.21.00.00
in recovery select RESTORE, it should show you the above backup, so select "2013-04-20.21.00.00" and restore it.
You still need to get the preloaded stock apps (which get deleted when unlocking using HTCdec), so download this:
http://loadbalancing.modaco.com/download.php?file=one-1.28.401.7-preloaded-modaco-withoutmovie.zip
adb push one-1.28.401.7-preloaded-modaco-withoutmovie.zip /data/media/
in recovery, select "install zip" -> "choose zip" -> and install the above file
Step 4: get back stock recovery
the above nandroid may or may not contain stock recovery, but I doubt it does, so get this: http://d-h.st/uGM
now let's reboot to bootloader/FASTBOOT USB:
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery 1.28.401.7.img (closest one to your version)
fastboot erase cache
Step 5: let's get rid of TAMPERED (if it's there) and set you back to LOCKED (not relocked)
fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
download this: http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
adb push Guru_Bootloader_Reset_1.0 /data/media/
in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"
go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished, and since you're still in CWM, go ahead and:
-> "wipe cache"
-> "advanced" -> "wipe dalvik"
then
adb reboot bootloader
and confirm no TAMPERED and LOCKED status
Step 6: get your 1st OTA
finally (almost) to confirm everything is back to 100% stock, reboot your phone, and set up only basic stuff such as WiFi, check for software update and download & install the 1st one only!
Since recovery is not exactly your version, you may need to reboot your phone manually if it doesnt by itself: the progress bar stopped somewhere in the middle -> press and hold POWER + VOLDOWN, when it reboots keep holding VOLDOWN to get back to stock recovery and let it finish it's business; repeat if it gets stuck again
After finishing the OTA, boot up your ROM, and check you Settings->About to confirm you new version, then reboot to bootloader and do a fastboot getvar all, and confirm firmware and hboot are also updated
Step 7: if YOU decide to go S-On
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55
I really think I should start a universal guide, hmmm
EDIT: I'm sleepy so I hope I didnt forget anything!!
EDIT2: I'll post credits to all those links when I get a chance, sorry guys
Hit the thanks button if I've helped

[Q] Return HTC One to stock EE carrier UK

Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.

VincSingh said:
Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.
Click to expand...
Click to collapse
You can use the volume buttons to move and the power button to select on TWRP (assuming it is not the touch version). Then to fix the problem with CM you should just do a wipe and flash the rom again. To return to stock you have to find your carriers RUU and send that through fastboot/adb, after follow Gizmoe's instructions on this thread to get everything back to stock (http://forum.xda-developers.com/showthread.php?)t=2592068

VincSingh said:
Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), you may wanna take a look at my guide if you want to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
once s-off, going S-ON is NOT recommended.

O-rangePeels said:
You can use the volume buttons to move and the power button to select on TWRP (assuming it is not the touch version). Then to fix the problem with CM you should just do a wipe and flash the rom again. To return to stock you have to find your carriers RUU and send that through fastboot/adb, after follow Gizmoe's instructions on this thread to get everything back to stock (http://forum.xda-developers.com/showthread.php?)t=2592068
Click to expand...
Click to collapse
Thanks O-rangeReels for the advice however for some reason now when I try to go into recovery the htc quietly brilliant screen says entering recovery and does not do anything?

VincSingh said:
Thanks O-rangeReels for the advice however for some reason now when I try to go into recovery the htc quietly brilliant screen says entering recovery and does not do anything?
Click to expand...
Click to collapse
I would be VERY careful using things meant for a Verizon device on a GSM one!

nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n), you may wanna take a look at my guide if you want to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
once s-off, going S-ON is NOT recommended.
Click to expand...
Click to collapse
Thanks for the advice, I do not know what you are asking me"post a getvar? please explain

VincSingh said:
Thanks for the advice, I do not know what you are asking me"post a getvar? please explain
Click to expand...
Click to collapse
are you (at least somewhat) familiar with "adb" and "fastboot"??
you need to boot your phone to bootloader/FASTBOOT USB, and then on your PC :
fastboot getvar all

nkk71 said:
are you (at least somewhat) familiar with "adb" and "fastboot"??
you need to boot your phone to bootloader/FASTBOOT USB, and then on your PC :
fastboot getvar all
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s

VincSingh said:
fastboot getvar all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
finished. total time: 0.067s
Click to expand...
Click to collapse
There's no "two-minute" fix, so a couple of more questions, if you don't mind:
1- does it matter to you if bootloader says UNLOCKED?
2- does it matter to you if bootloader says TAMPERED?
3- you want to go back to stock, in order to receive OTA updates?
4- do you intend on selling the phone or returning for warranty? (and so you need the phone to look "out of the box")

nkk71 said:
There's no "two-minute" fix, so a couple of more questions, if you don't mind:
1- does it matter to you if bootloader says UNLOCKED?
2- does it matter to you if bootloader says TAMPERED?
3- you want to go back to stock, in order to receive OTA updates?
4- do you intend on selling the phone or returning for warranty? (and so you need the phone to look "out of the box")
Click to expand...
Click to collapse
1 and 2 - does not matter at this point I would just like to get the phone back to working in any format stock or rooted.
3 - OTA not necessary in view of 1 and 2
4 - don't intend to sell or return the phone
appreciate your help, thanks

VincSingh said:
1 and 2 - does not matter at this point I would just like to get the phone back to working in any format stock or rooted.
3 - OTA not necessary in view of 1 and 2
4 - don't intend to sell or return the phone
appreciate your help, thanks
Click to expand...
Click to collapse
fair enough, here's a quick fix: just download and install this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
using CWM: http://forum.xda-developers.com/showthread.php?t=2173863
or TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
the above ROM is for a Europan unbranded version; it's stock, can be rooted or not (selectable in the installer), unselect "stock recovery" in installer as it won't allow OTA's with your current configuration.
I'm gonna check something, and will get back to you when I can, in the meantime the above ROM will get you up and running. (or you can choose any one of the custom ROMs around)
I'll get back to you later
cheers
PS: maybe you could give me a little background info on why you ended up in this situation, eg do you want to be on stock rom (or custom), do you want to be rooted, etc etc. and if not, how come you unlocked your bootloader
If I understand your intentions, I could help better

nkk71 said:
fair enough, here's a quick fix: just download and install this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
using CWM: http://forum.xda-developers.com/showthread.php?t=2173863
or TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
the above ROM is for a Europan unbranded version; it's stock, can be rooted or not (selectable in the installer), unselect "stock recovery" in installer as it won't allow OTA's with your current configuration.
I'm gonna check something, and will get back to you when I can, in the meantime the above ROM will get you up and running. (or you can choose any one of the custom ROMs around)
I'll get back to you later
cheers
PS: maybe you could give me a little background info on why you ended up in this situation, eg do you want to be on stock rom (or custom), do you want to be rooted, etc etc. and if not, how come you unlocked your bootloader
If I understand your intentions, I could help better
Click to expand...
Click to collapse
once I have downloaded the ROM how do I install it?
what are the links for CWM and TWRP for, do I need to download anything from them?
As you can tell I dont fully understand the tech side of this much. I thought to root the phone I could get more custom features however after doing this I did not like it and wanted to return to stock but could not find the correct ROM and so the issues began.

VincSingh said:
once I have downloaded the ROM how do I install it?
what are the links for CWM and TWRP for, do I need to download anything from them?
As you can tell I dont fully understand the tech side of this much. I thought to root the phone I could get more custom features however after doing this I did not like it and wanted to return to stock but could not find the correct ROM and so the issues began.
Click to expand...
Click to collapse
@nkk71 full guide for returning to stock is here
http://forum.xda-developers.com/showthread.php?t=2541082
you would do well to read and try and understand all that's going on

clsA said:
@nkk71 full guide for returning to stock is here
http://forum.xda-developers.com/showthread.php?t=2541082
you would do well to read and try and understand all that's going on
Click to expand...
Click to collapse
There are many more downloads required when following the superguide of which I have tried the RUU M7 before and failed at the final stage due to it not being compatible with UK HTC.
the last message from nk77 suggested that all I needed is the Guru reset , which I have downloaded but do not know how to install and cannot see how to do this on the superguide either. Do you know how to install the guru reset?

VincSingh said:
There are many more downloads required when following the superguide of which I have tried the RUU M7 before and failed at the final stage due to it not being compatible with UK HTC.
the last message from nk77 suggested that all I needed is the Guru reset , which I have downloaded but do not know how to install and cannot see how to do this on the superguide either. Do you know how to install the guru reset?
Click to expand...
Click to collapse
1- the guide is made to return to 100% stock; mostly for people going for warranty or want to sell the phone, and put it "out of the box"
2- the Guru Reset i mentioned will only get your phone working (or any other custom ROM), it will not get any OTA updates etc.
3- in order to restore to stock (in your case), you need S-Off
4- if you do have S-Off, you can even turn your phone into an unbranded European version
5- to get the ROM (Guru Reset or any other custom ROM), you can use one of three methods (using custom recovery CWM or TWRP):
i- OTG cable
ii- adb push <name of rom>.zip /data/media/0/
iii- adb sideload <name of rom>.zip

nkk71 said:
1- the guide is made to return to 100% stock; mostly for people going for warranty or want to sell the phone, and put it "out of the box"
2- the Guru Reset i mentioned will only get your phone working (or any other custom ROM), it will not get any OTA updates etc.
3- in order to restore to stock (in your case), you need S-Off
4- if you do have S-Off, you can even turn your phone into an unbranded European version
5- to get the ROM (Guru Reset or any other custom ROM), you can use one of three methods (using custom recovery CWM or TWRP):
i- OTG cable
ii- adb push <name of rom>.zip /data/media/0/
iii- adb sideload <name of rom>.zip
Click to expand...
Click to collapse
I tried S-Off using Rumrunner but could not do it, the error said debugging is on.

sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)

VincSingh said:
sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Click to expand...
Click to collapse
have you attempted the Guru reset yet ?

sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)

No. was trying to S-Off but am getting error message which I last posted!
Any suggestions?

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

[Q] 100% stock ROM reset: how do I get LOCKED instead of RELOCKED?

Hello everybody!
I want to get back to 100% stock ROM (after having used Cyanogenmod previously) - with LOCKED, not RELOCKED.
Current phone: fastboot getvar all yields:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: MYSN
(bootloader) imei: MYIMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have already restored a Nandroid backup with the original software: that backup was taken from my own phone some months ago right after purchase. I only unlocked the phone for the very first time, flashed the CWMR and directly made the backup with that recovery. Then I pulled the backup to my PC my adb.
So far, I successfully got the phone to S-Off, using RumRunner and removed the TAMPERED flag using the following method with adb as described within this post: http://forum.xda-developers.com/showthread.php?t=2477792
However, now I seem to have run into a deadlock:
a) To gain LOCKED using the following method with adb as described within this post(http://forum.xda-developers.com/showthread.php?t=2475914) I need adb access to the phone.
As long the CWMR is on the phone, the device is listed as “Android ADB Interface” in the category “Android Device” in the Windows Device Manager. Fine, so I can access the phone through adb and can set the bootloader back to LOCKED successfully. But after locking I am not able flash the stock recovery any more.
b) If I flash the stock recovery and boot into it, then
- the stock recovery does not provide adb access. The phone is not listed in the Windows Device Manager.
- booted up into HTC Sense OS, it does not provide adb access, either .The phone is listed as “CD Serial” with a question mark in the category “Other Devices” and “HTC One” with a question mark in the category “Portable Devices”; Also it automatically mounts a drive that includes the HTC Sync Manager, Drivers, etc. [EDIT] Got rid of the question marks by re-assigning the correct MTP and CDC drivers; now I can see the emulated sdcard folder[EDIT OFF],
So, without adb access I cannot use the above method to get LOCKED (and fastboot oem relock lead to RELOCKED, which voids my warranty )-: ).
c) Having the matching stock recovery (3.63.161.6 - Vodafone.img downloaded from the internet somwhere, checksum OK) installed and trying to boot into a temporary CWMR by using fastboot boot myM7_UL_CWMR.img (I tried recovery-clockwork-touch-6.0.4.3-m7ul) does not work, the phone is stuck, if I sent that command. -Is it because, I have HBOOT 1.55, and fastboot boot recovery.img is only supported by HBOOT 1.44?
Question: Do I really have to go through the complete procedure described here, to get LOCKED ? :
http://www.htc1guru.com/guides/return-stock-guide/
That procedure seems to be a pain for me as my CID is VODAP102, and there seems no RUU to be listed for my phone, so I will have to change the CID during the process and execute some extra process steps - or I am just too dumb to identify the correct one for my phone:
http://forum.xda-developers.com/showthread.php?t=2428276
Or is there any alternative quicker way than that HTC Guru Guide?
As said, I have a CWR backup .zip from my original factory installation and I already have already downloaded the matching stock recovery image, so I can flash it on the phone. Does this help?
Regards
Steven

that's one hell of a long post and a lot of questions, well first of all i'll see if I can help you with this, link below is Vodafone backup which I created from my phone, unzip it, you will find a folder called backup, that contains the backup files, and another called recovery, that contains twrp that I used to create the backup, so flash that first.
STAY S_OFF, DO NOT SET BACK TO S_ON.
enter recovery, create a backup in order to create the required folders, then boot your phone back to android, once booted, plug into your computer, copy the backup folder from my zip to your internal SDcard/TWRP/BACKUPS/"device serial number"/
Reboot the phone back into recovery and restore that backup, you will now have Vodafone kitkat 4.4.2 on your phone, however one problem you may have is 4.4.2 comes with HBOOT 1.56 not 1.55, they may pick up on that.
https://drive.google.com/file/d/0B_nEcSZr5peRZnpMSHRPRjlzX2c/edit?usp=sharing

Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven

ManyPhones said:
Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven
Click to expand...
Click to collapse
check my guide, see if that makes sense to you: http://forum.xda-developers.com/showthread.php?t=2541082
reason why the CWM restore method is so long: http://forum.xda-developers.com/showpost.php?p=52430301&postcount=834
I recommend you stay S-Off, but that's a decision only you can make
---------- Post added at 04:03 PM ---------- Previous post was at 03:38 PM ----------
@ManyPhones
if you're going to follow my guide, these are the files you need (in case htc1guru.com is giving slow/corrupt downloads):
ruu.zip: http://www.androidfilehost.com/?fid=23329332407584993
nandroid: http://www.androidfilehost.com/?fid=23501681358543658
preloaded apps: http://www.androidfilehost.com/?fid=23329332407580574
and probably this stock recovery: http://d-h.st/XMA should work without hanging.

Dear nkk71,
thank you! I carefully read through your posting and the linked instructions. - your guide is excellent and foolproof!
I understood I had to use the Nandroid backup method, as there was neither an RUU.exe nor an RUU.zip file available for CID VODAP102.
Thank you for providing the explicit versions/links for my individual phone in the posting!
So the key is indeed downgrading to HBOOT 1.44 in order to be able to load a temporary custom recovery with fastboot boot temp_ recovery_name.img.
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Why do you recommend to stay S-Off? - Isn't it possible to go S-On, OTA update to 3.63.161.6, let the phone repair and then later use RumRunner again (after unlocking and rooting again)?
Regards
Steven
P.S.: Someone provided another, shorter method (without downgrade) per PN:
1st download recovery flasher zip (LINK)
Open this zip with 7zip*
Put stock recovery in it simply but renamed recovery.img*
Close zip if it ask save it press yes*
Copy this new zip to phone storage*
Now download guru boot loader reset tool zip from this link & copy to your phone storage
Now reboot to TWRP recovery
*1 st flash recovery flasher zip*
2 nd flash guru boot loader reset tool zip with Locked & remove tempered options ( it tempered is there ) complete flash*
I have not tried it, as I was half through your method. But I can imagine, it maywork - as I do not need to use external adb to access the internal phone memory for the flags, and since I had my own factory-fresh HTC backup re-installed already before.

ManyPhones said:
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Click to expand...
Click to collapse
Hi,
There are always different ways of doing things, some shorter, some longer. My guide was written after many many different one-on-one threads, and the conclusion of every possible outcome I have encountered.
(including IRC chats and teamviewer sessions, and even some shortcut methods were used in my thread, but on a one-to-one basis, not as a general rule)
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
For example: I've seen threads with people sending in their phone with a custom ROM, tampered, unlocked -> no problem
but i've also seen a post, 100% stock including S-On, but the repair guy said the power button was pressed with "too much force" and refused warranty (oh and it wasn't sent to repair for the power button!!)
cheers

I see, your's is a general approach that will work under any circumstances. I can imagine it is almost impossible to provide tailored solutions for each and every individual starting point of the restore. So, the long way is always the safe way (-:
It must have been a lot of work to assemble the guide and the case example.
Great work! You'll be thanked!

Final words
nkk71 said:
Hi,
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
cheers
Click to expand...
Click to collapse
Final words:
I decided to go S-On - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.

ManyPhones said:
Final words:
I decided to go S-Off - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.
Click to expand...
Click to collapse
you mean "go S-On", right?
and yes, for hboot 1.57 firewater is the only method at the moment that may work to get S-Off, hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)

nkk71 said:
you mean "go S-On", right?
Click to expand...
Click to collapse
Yeah, that was a typo - I meant S-On (corrected in post #9, sorry for the confusion!
nkk71 said:
Hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)
Click to expand...
Click to collapse
Those concepts are still inknown to me. Never mind, I'll check it out later as needed.
Thanks again, nkk71 for the excellent support - and the others, who wrote me PMs!

HTC One M7 - can not update to android 5.

Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign.
So I started to read. First I've read that I need to unlock bootloader, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help

See comment in red below
qwe1234 said:
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign. Indicating that your software partition isn't 100% stock. The ota update will only replace the required files to be updated, not the whole system. Before updating, the updater-script check integrity of all files to be updated. If only one of these file isn't as expected, the updater-script will abort and the update will not install ----> red triangle
So I started to read. First I've read that I need to unlock bootloader bootloader lock/unlock status isn't related to ota update, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device You don't need root to install firmware. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found indicating that you are not using the correct file. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference The sprint variant is a CDMA phone). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000 old bootloader version not matching your software version
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls twrp 2.5.0.0 is really outdated and won't work with recent files. Not a problem for now since you will not need to use twrp to fix it, just fyi
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
Click to expand...
Click to collapse
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.

My friend Thank You very much for all the instructions... but...
Last step:
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Click to expand...
Click to collapse
ended with error ;(
fastboot gave following:
processing file 2/5...
error: cannot load 'C:\Users\x101ch\AppData\Local\Temp\tmpp6r0paxd'
htc_fastboot finished. total time: 297.909s
Phone restarted once in the middle like you said.
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
One more thing. I haven't noticed that you changed command from fastboot to htc_fastboot so I changed htc_fastboot file name to just fastboot and used command fastboot. Don't know if it matters...

qwe1234 said:
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
Click to expand...
Click to collapse
Now you probably understand why I said
if something goes wrong post here and wait (do not skip any steps).
Click to expand...
Click to collapse
Rebooting after a failed/incomplete flash can hard brick your phone. If you can't get fastboot connectivity again, there is not much you can do. Sorry

Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?

qwe1234 said:
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
Click to expand...
Click to collapse
maybe or let the battery drain then plug the phone again and try to boot in bootloader with vol down and power.

Ok. I will try to do that tomorrow and will post the result. Thanks again

Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult

qwe1234 said:
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
Click to expand...
Click to collapse
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)

alray said:
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s

qwe1234 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
Click to expand...
Click to collapse
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work

alray said:
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
Click to expand...
Click to collapse
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again

qwe1234 said:
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
Click to expand...
Click to collapse
:good:
you're welcome!

So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?

qwe1234 said:
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
Click to expand...
Click to collapse
So it looks like I'm stupid.
I tried to unlock the phone. Again bootloader unlocked, phone rooted. I wanted to unlock it with terminal commands using HtcOMADM_SPCS but I cannot install it. I've installed twrp (this time version 3.1.1.0) but it keeps saying that footer is wrong and signature verification failed...
Any more help, please? ;(

Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
I'm getting crickets on my thread, and just needed a general confirmation on the process again since it's been awhile.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Just confirming the process you described would still work the same way.
Thanks!
alray said:
See comment in red below
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
Click to expand...
Click to collapse

cloud66 said:
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
Click to expand...
Click to collapse
Since yours is also a Sprint HTC One, yes the same procedure should work.
I'm getting crickets on my thread
Click to expand...
Click to collapse
quote me next time and I'll be notified, just like you did in this thread.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Click to expand...
Click to collapse
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img

alray said:
quote me next time and I'll be notified, just like you did in this thread.
Click to expand...
Click to collapse
Hey again. Alray can I ask you for a little bit more help? I've tried every way to sim unlock i found but without any success. Last method I used was from this video: https://www.youtube.com/watch?v=e6hHUae1TMs but when I want to run Unlock helper it crashes. Have no idea what am I doing wrong...;(

alray said:
Since yours is also a Sprint HTC One, yes the same procedure should work.
quote me next time and I'll be notified, just like you did in this thread.
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
Click to expand...
Click to collapse
Hey so looks like I'm running into an issue when updating my firmware.
I'm getting this:
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware and no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues.
Also flashed twrp recovery without any issues.
Rom is still working, everything is still normal....
Thoughts?

Also wanted to add that I was able to update TWRP to 3.1 and flash ICE ROM 7.1.1 and gapps without any issues. So far running semi-stable.
Tried updating firmware with s-on after i re-locked my bootloader, but that did not work either. I was still getting some weird error so I unlocked my bootloader again and then was able to flash the nougat rom just fine. It's strange that it's working with such an older version of the firmware... oh well.
Will still hold out for any suggestions. I'm sure I will run into some issues soon with the firmware being that out-of-date. Signal issues, battery issues, etc.