Develop Bugs

HTC 10 non-standard behavior

Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
Code:
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxx
(bootloader) current-slot:
(bootloader) imei: xxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
all:
finished. total time: 0.064s
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
Code:
target reported max download size of 1579200000 bytes
sending 'recovery' (20852 KB)...
OKAY [ 1.711s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.810s]
finished. total time: 3.528s
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message
Code:
33 RU_UPDATE_FIRMWARE_FAIL
33 RU_UPDATE_FIRMWARE_FAIL
FAIL33 RU_UPDATE_FIRMWARE_FAIL
as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.

madzur said:
Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.
Click to expand...
Click to collapse
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.

Captain_Throwback said:
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.
Click to expand...
Click to collapse
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?

madzur said:
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?
Click to expand...
Click to collapse
You sure you don't have a hardware problem? That's what it sounds like.

Captain_Throwback said:
You sure you don't have a hardware problem? That's what it sounds like.
Click to expand...
Click to collapse
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.

madzur said:
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.
Click to expand...
Click to collapse
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.

Captain_Throwback said:
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.
Click to expand...
Click to collapse
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks

madzur said:
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks
Click to expand...
Click to collapse
Nope, that only happens well, when you've modified the software by installing an unsigned image like a custom recovery or kernel or made modifications to system. So getting an RUU to flash is really the only way to restore it back to official status.

Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?

Same thing
madzur said:
Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?
Click to expand...
Click to collapse
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.

djgreyghost said:
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.
Click to expand...
Click to collapse
Pretty sure you saved my phone from extinction :good: I'm not sure I would of tried the S-On version.

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.

Dukenukemx said:
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.
Click to expand...
Click to collapse
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.

djgreyghost said:
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.
Click to expand...
Click to collapse
Guess I'll be installing LineageOS then. The phone works fine like this, but it bothers me that I can't flash it completely.

Ok the problem with [email protected] is that you installed an aftermarket screen and that causes the failure. The solution is to remove the tp_SYN3708.img file from the rom and then flash it, but I'm still working on how to do that. The tp_SYN3708.img file is specifically for flashing the screen and the screen I have is Chinese replica, so of course it doesn't work. So my options are to remove the file and flash that way or to get another LCD screen. I'd rather find a software solution as looking for an original HTC 10 screen is probably harder than it sounds.

Tmobile: Relocked: S-ON: Stuck in bootloaded

Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!

jdub1983 said:
Hello,
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
I any attempts using flashboot do not work.
Can anyone please help me bring my phone back to life in anyway possible.
Ive been trying to find a RUU.zip file to try on my sd card, although i cant seem to find a download link to a zip file and i am on a MAC so the .exe wont work for me.
can someone please help!!!
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader?

xunholyx said:
What does it say next to "OS" in your bootloader?
Click to expand...
Click to collapse
Nothing is listed next to os in the bootloader mene
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jdub1983 said:
my tmobile m8 is stuck in bootloader after trying to flash signed firmware.
Click to expand...
Click to collapse
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
jdub1983 said:
I any attempts using flashboot do not work.
Click to expand...
Click to collapse
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.

redpoint73 said:
Was the firmware install successful, or not?
Even with a successful firmware flash, the intended and expected result is no boot to OS. Or alternately, you will need to unlock bootloader, flash TWRP, and restore a stock TWRP backup.
Do you mean fastboot?
What exactly did you try, what were the results, specific error messages, etc.
Just say "any attempts . . do not work" doesn't give us enough info to be helpful.
Click to expand...
Click to collapse
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
If you give me a few things to do when I'm in front of the computer I'll execute them later on and report back the results.

jdub1983 said:
My apologies, fastboot is what I meant.
I'm not at my MAC to copy and paste, I can when I get home after work.
None of the firmware attempts were successful. None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
jdub1983 said:
None of the attempts to flash a recovery were successful either.
Click to expand...
Click to collapse
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
jdub1983 said:
Originally I attempted a signed firmware flash from the SD card, renaming the zip, and letting hboot do it's thing. No errors from that method, just rebooted back to the OS.
Click to expand...
Click to collapse
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?

redpoint73 said:
You need to tell us what the error messages were, in order for us to troubleshoot the fastboot problem.
Otherwise, we don't know if the firmware flash was unsuccessful due to wrong firmware, etc.; or if you simply have an issue with USB connectivity.
Try fastboot devices, and see is the output is the phone's serial number. This would mean fastboot is working properly. No need to tell us the serial number (as it's personal info, should not be posted online) - just tell us yes/no.
If the result is "waiting" or no devices connected, or some other error, tell us.
You also need to tell use the firmware numer(s) you tried to flash, and would be nice to see the exact commands, outputs, etc.
Do you mean custom recovery? If so, is it TWRP? What version number?
You can't flash custom recovery (TWRP) with a locked (relocked) bootloader. You need to unlock it again, to flash TWRP.
When asking for help, you should really try to give as many specifics and details as possible. So far, you really haven't provided much specific detail, at all.
It appears that firmware flash was not successful. Otherwise, the version number of the firmware would be listed on the bootloader screen for OS number.
What number firmware did you try to flash?
Click to expand...
Click to collapse
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!

jdub1983 said:
I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
Click to expand...
Click to collapse
I didn't specify that it had to be an error code number. If the response is all text, tell us what it is. Cut and paste, or do a screenshot, if that is easier. Either way, it will probably tell me what is going wrong.

jdub1983 said:
When I get home I'll re-try some of the flashes and let you know what the errors say. I originally tried to flash tmobiles latest firmware, full wipe 6.20.531.5 if memory is serving me right now. Downloaded from sneaky ghosts thread. Attempted via sdcard and fastboot. I'll re run the fastboot flash and report the error again, however there wasn't an error code number reported, was all text.
As for TWRP, I'll unlock bootloader again and try and flash again and report the error it gave me.
Thanks for the help, and apologize for not having complete info for you to work off at the moment.
Greatly appreciated!
Click to expand...
Click to collapse
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off

xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?

xunholyx said:
Sneakyghost doesn't supply signed firmware. Everything he does is modified, and can only be flashed if you are S-Off
Click to expand...
Click to collapse
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.

jdub1983 said:
Doesn't he have 2 options he offers, the no wipe, which he modifies, and the fullwipe, which I thought were signed?
Click to expand...
Click to collapse
No, they aren't.
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
EDIT: I see now that Redpoint has already linked you up. :good: Easier for me

xunholyx said:
Since you are S-On and wiping anyway, the best thing for you to do would just to run an RUU. I'll extract the ROM.zip (RUU.zip) from the T-Mo RUU.exe when I get home in a bit (an hour or two) and link you here to it. You'll be able to flash that via your SD card.
Click to expand...
Click to collapse
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.

redpoint73 said:
As I suspected, but I could never remember.
OP can find signed firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Can't find a zip version of the T-Mobile RUU. So you may need to resort to restoring the stock TWRP backup from the same thread as the signed firmware: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But that depends on what exactly your end goal is. Are you trying to return to full Marshmallow stock, or something else?
---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------
He offers No Wipe (which is modified firmware) and Full Stock (which does wipe). But full stock does not mean it's signed. I remember these not being signed also (like xunholyx said). And you can't flash unsigned firmware, unless you have s-off.
Click to expand...
Click to collapse
Gotcha! If I'm s-on though, how did everything get screwed up? Guess it's not important now.
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom. Something simple really, my m8 is my backup phone.

redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!

jdub1983 said:
If I'm s-on though, how did everything get screwed up?
Click to expand...
Click to collapse
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
jdub1983 said:
I'd like to get the m8 upgraded to latest firmware, radio, etc for T-Mobile network. Was planning on installing a custom ROM once it was upgraded, such as lineageOS or leedroid Rom.
Click to expand...
Click to collapse
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.

redpoint73 said:
I agree the RUU is easier for him, since he is already relocked and (as you mentioned) wiping anyway. Restoring a TWRP backup (by method I linked) is a lot more steps.
Click to expand...
Click to collapse
redpoint73 said:
Once you relock the bootloader with s-on, the phone is rendered unable to boot to OS, as it expects RUU to be run.
OS number is blank in bootloader, usually due to an old version of TWRP being used it the past (known bug).
Other than that, your fastboot issues are often a problem on the PC side. But would need to know the exact error messages to troubleshoot further.
If the intent to flash a custom ROM right away, I would suggest just flashing the signed firmware 6.20.531.5 from the link I provided. Then unlock bootloader again, flash TWRP 3.1.0 (current version) and flash the ROM of your choice.
No point in restoring a stock TWRP backup, if you are just going to then flash a custom ROM.
Click to expand...
Click to collapse
I'll give it a whirl when I get home and let you know of any errors, if any, hopefully not.
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Thanks again!

jdub1983 said:
Question ahead of time: I noticed after re-locking the bootloader, the command "fastboot oem rebootruu" wasn't recognized, does this play into the fact that the phone is expecting a ruu, and therefore already in ruu mode?
Click to expand...
Click to collapse
I doubt it. Rather, I think your syntax was incorrect (if you typed it exactly as you did before) as the part "RUU" (no quotes) should be in caps:
fastboot oem rebootRUU
If the phone is in RUU mode, it will show a black screen, with HTC logo.

jdub1983 said:
Would be great to have the ruu zip, been looking for a one for a few days. However if you want to hold off, I'm happy to go through the long get process as it will be good practice and refresher for me, if I run into any issues I can then hit you up for the zip ruu. Whatever is good for you kind souls helping me out!
Thank you!
Click to expand...
Click to collapse
Here's the RUU.zip for you.

you both are amazing, thank you!
I feel so silly, considering I was using sneaky ghosts unsigned fullwipe firmware... Blah!
Again, you both are awesome, kind to a moron! The universe will provide for you both!
Thanks again!!!
Everything is working wonderful!!!!!

[HTC M8] Unable to update firmware :(

Hello, guys!
I write here for help as HTC's customer support can't help me!
As title tell you I am unable to update firmware.
Everytime I receive notification that an update is available and that I should update my firmware.
Unfortunely, I get error
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
In order to solve this problem I tried to factory reset, but without any success
Would be very glad if someone could help me!
Thank you!
EDIT: I am sorry for my worst English! I hope you understand what I wrote here. Thanks!

Winserity said:
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
Click to expand...
Click to collapse
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Winserity said:
In order to solve this problem I tried to factory reset, but without any success
Click to expand...
Click to collapse
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Winserity said:
I am sorry for my worst English! I hope you understand what I wrote here. Thanks!
Click to expand...
Click to collapse
Your English is fine so far! :good:

redpoint73 said:
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Your English is fine so far! :good:
Click to expand...
Click to collapse
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015,22:51:08.1

Winserity said:
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OS-4.16.401.10
Click to expand...
Click to collapse
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
EDIT:
Look there

Winserity said:
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
Click to expand...
Click to collapse
It's not a dumb question. Others have been confused by the wording in the guide regarding relocking the bootloader.
You do not need to relock the bootloader. S-off bypasses the requirement for bootloader to be locked/relocked when running RUU. In other words, with s-off the RUU will run fine regardless of whether the bootloader is unlocked or locked.
I recommend you leave the bootloader unlocked, as it gives you more options if anything goes wrong.
Thanks for posting the getvar data. Either you knew how to do that already, or you are learning quickly! The info confirms that you should be able to use the RUU. It also appears to have been the US T-Mobile version (model ID 0P6B13000) that was modified to remove the carrier branding, and "convert" it to Euro version.

Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
If there will be new information regarding my issue I will post there
EDIT 2:
After "FAILED" it automatically restart the same procedure
Still waiting for about 25-30 minutes
Is this ok?
EDIT 3:
To be honest, I am feeling scared x(
Can someone confirm that my phone isn't broke?
It's still showing "send `zip` ... (1687274KB)" more than a hour
Why is it taking too long?

Update:
Used OS Windows 7 and I flushed this RUU, but after fastboot reboot my HTC doesn't seems to switch on Android
Screenshot:
Right now, my HTC stucks at a white screen where is shown HTC One logo
Maybe it sounds dumb, but I can't even switch off phone.
I am able only to restart phone using Power + Volume UP
No any setup started after fastboot reboot

Winserity said:
Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
Click to expand...
Click to collapse
It doesn't say anywhere in the instructions to extract anything! Follow the instructions exactly, and don't make up steps!
The zip is an encrypted archive. It's encrypted with HTC's encryptions keys, and there is no way for you to decrypt it (and there isn't any reason to!). That is why Windows thinks it is "corrupt" - but don't worry it isn't. You just flash the RUU, as is, and it will do the rest. Extracting anything will break the signature, and cause it to fail signature check (will not install).
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Error 90 is normal. It needs to be run twice as indicated. The message "flush again immediately" is a strange typo which HTC has maintained over numerous RUUs on different devices - it should say "flash again immediately. You need to run the command again to flash the RUU zip.
It's not completely clear for your description, if you extracted anything from the RUU zip and tried to flash it. Hopefully you didn't. Please describe in full detail, all the steps you performed, with the exact file names, commands, etc.

In the final I didn't extracted archive ZIP. But as you said I tried to repair archive cause I saw "The file is corrupt."
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Until that time I have to tell you thank you very much!
I really appreciate your attention to my issue

Winserity said:
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Click to expand...
Click to collapse
Do you have reason to believe your friend has more knowledge of this specific device than we do (or you doing the steps, with our guidance)?
Because HTC devices can be very nuanced (lots of differences from other Android devices). If he doesn't have specific experience with HTC devices (and even better, the M8 specifically) he might not be able to help, or even make the problem worse.

My friend solved problem by installing firmware version 6.12.1540.4
He used a ROM utility to solve this problem.
Wasn't easy for him at all, but in final I am glad
Now, I have last version installed for my HTC M8
Thanks for your help, redpoint73!
Wish everyone to avoid HTC phone problems =)

Hi all please I do need help on this same issue. I cannot install updates. I get the msg I am using a modified version of the software. Even though I never modified it myself but bought it that way, I tried to unroot it with an app I installed, but it says it's not even rooted. My phone is HTC Desire Eye and it's presently running on 4.4.4 Kitkat. Your assistance will be appreciated. Also I am less of a technical guy, so pls guide me on every step I may need to solve this like a newbie.
Thanks guys!

HELP!: HTC ONE M8 is boot looping after attempted update to android 6.0 Marshmallow

So as some backstory, I recently bought a second-hand HTC ONE M8 and it was working in perfect condition. All the trouble started when I attempted to update the phone to android version 6.0 and the update failed at around 80%. This lead me to a constant reboot state from the HTC logo to the screen with the triangle with an exclamation mark in the middle.
As of right now I have tried every single option on the bootloader to try to fix the issue with no success. I have also attempted to install multiple RUU's to reset the phone but I have no found one RUU that matches my phone's software status (Phone bootloader information below). It is also worth to mention that the phone is an optus (Australia Version). Here are my phone's specifications:
*** Software status: Official ***
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.980.5
eMMC-boot 2048MB
Dec 1 2015,18:43:39.0
Some side notes:
When trying to install an RUU, the log, when failing, suggests that my device has htc/optus_au/htc_m8: 6.0/MRA58K/663331.5:user/release-keys
This device has not been modified by myself nor the previous owners
A user over at android forums had a similar problem (post name was: 'Help! HTC One M8 stuck on Fastboot screen'), but that post is dead with one very informative reply that doesn't help solve the issue .

Th3CobaltLlama said:
I have also attempted to install multiple RUU's to reset the phone but I have no found one RUU that matches my phone's software status
When trying to install an RUU, the log, when failing, suggests that my device has htc/optus_au/htc_m8: 6.0/MRA58K/663331.5:user/release-keys[/LIST]
Click to expand...
Click to collapse
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

redpoint73 said:
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Thanks for the help! I'm trying it out now, just learning how to do all the jazz with TWRP (Kind of confusing to me, if you know a reliable video tutorial could you link me?). I'll repost once I have made some proper progress.

It's Fixed, Many Thanks!
redpoint73 said:
The RUU has to be exactly for your version, Optus and version number 6.12.980.5. I don't know if your version has RUU. So if you don't have that exact RUU, you can run a million different RUUs, and million times, and it will fail every single time, guaranteed.
If no RUU, your best bet is to unlock the bootloader, flash TWRP custom recovery, and either flash a custom ROM, or restore the stock TWRP backup (6.12.980.5) from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
You're an actual legend! It's fixed now! I've never met anyone as helpful as you online redpoint73. Good luck to you in future mate, you deserve whatever good comes your way! :good:

Th3CobaltLlama said:
You're an actual legend! It's fixed now! I've never met anyone as helpful as you online redpoint73. Good luck to you in future mate, you deserve whatever good comes your way! :good:
Click to expand...
Click to collapse
You're quite welcome. Glad you worked it out. The instructions on how to restore a stock TWRP are not trivial; but it's all there, if you are patient and careful enough to work through it (as it appears you've done)!

Updating HTC One M8

i have HTC ONE M8 with following boot properties
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Software Status: Official***
*** LOCKED ***
M8.WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.000
RADIO-1.09.20.0119
OpenDSP-v38.2.2-00542-M8974.0311
OS-3.30.651.2
eMMC-boot 2048MB
OCT 9 2014,21:03:31.33162
HBOOT
when i perform OTA i says my device is already updated but my Android Version is 4.4.4
i want to update it to latest possible android version.

You have the US Sprint version. Which won't get OTA unless you are connected to that actual carrier (Sprint).
To update with official RUU, you can get it here: https://forum.xda-developers.com/showthread.php?t=2729173
If updating to the latest (last) which is Marshmallow 6.20.651.3, then you will need to flash the 6.20.651.3 firmware, before flashing the RUU (peculiar requirement for flashing US Marshmallow RUUs). The firmware is also included on the link above.
Also note that your device may have an unbranded (not Sprint based) ROM installed by a 3rd party seller, in order for it to appear like an "unlocked" device. If you don't see any Sprint branding, such as Sprint logo on boot, Sprint apps, etc.; then it is likely that it has an unbranded ROM installed.
The RUU I linked will install official Sprint-branded ROM, so you may or may not like that. If you don't like the Sprint branding, after flashing firmware/RUU, you can go down the path of flashing a custom ROM (which support the Sprint version M8). But that is another process, and the firmware/RUU needs to be run even in that case, as your firmware (radio, WiFi, etc.) need to be updated to run the current custom ROMs, anyway.

redpoint73 said:
You have the US Sprint version. Which won't get OTA unless you are connected to that actual carrier (Sprint).
To update with official RUU, you can get it here: https://forum.xda-developers.com/showthread.php?t=2729173
If updating to the latest (last) which is Marshmallow 6.20.651.3, then you will need to flash the 6.20.651.3 firmware, before flashing the RUU (peculiar requirement for flashing US Marshmallow RUUs). The firmware is also included on the link above.
Also note that your device may have an unbranded (not Sprint based) ROM installed by a 3rd party seller, in order for it to appear like an "unlocked" device. If you don't see any Sprint branding, such as Sprint logo on boot, Sprint apps, etc.; then it is likely that it has an unbranded ROM installed.
The RUU I linked will install official Sprint-branded ROM, so you may or may not like that. If you don't like the Sprint branding, after flashing firmware/RUU, you can go down the path of flashing a custom ROM (which support the Sprint version M8). But that is another process, and the firmware/RUU needs to be run even in that case, as your firmware (radio, WiFi, etc.) need to be updated to run the current custom ROMs, anyway.
Click to expand...
Click to collapse
in the mentioned website there are alot of RUUs
which one should i use. i have downloaded the first one under 0P6BIMG RUUs heading (i.e 0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zi p) is it right for me or should i download another RUU?
Also there are alot of Firmwares FUU
1. Modified
2. Modified removed boot and recovery
3. Full
4. Signed Full
which one is better for me please tell me.
also which one should i install first RUU or FUU?
Another thing will i be able to run the Radio in new android 6 because currently radio app is installed but it does not work at all
Can i install Android Nougat?

alinazir said:
in the mentioned website there are alot of RUUs
which one should i use. i have downloaded the first one under 0P6BIMG RUUs heading (i.e 0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zi p)
Click to expand...
Click to collapse
I already suggested 6.20.651.3, so I don't know why you are wasting time confusing yourself. If asking for help, please try to read/understand more carefully; instead of asking questions that have already been answere, and making me repeat myself.
6.20.651.3 is the RUU for the "regular" (non-Harmon Kardon) Sprint version. 6.20.654.3 is the Harmon Kardon edition RUU. The only difference is the HK (software) mods. In actuality you can flash either one, since you have SuperCID (11111111). But seeing as your current version is non-HK (3.30.651.2), that is why I picked that one.
4.xx RUUs are Lollipop. Since the goal is to be updated, I would assume you want the latest possible, which is Marshmallow.
zip or exe format RUU is up to you. But for the zip format, you either need an SD card, or know how to use fastboot (and you will need the htc_fastboot instead of the "generic" Google fastboot, which cannot handle the large file size of the RUU).
For exe format, PC is required.
alinazir said:
Also there are alot of Firmwares FUU
1. Modified
2. Modified removed boot and recovery
3. Full
4. Signed Full
which one is better for me please tell me.
Click to expand...
Click to collapse
"Modified" firmware remove either recovery and/or boot.img. The main reason for using a "modified" firmware, is if you want to keep a custom recovery, or the current boot.img (kernel). Neither of those apply in your case.
My recommendation would be to flash the signed full firmware.
alinazir said:
also which one should i install first RUU or FUU?
Click to expand...
Click to collapse
Again, this is a question whose answer I already stated in my previous reply. You need to flash the firmware before flashing the RUU. Otherwise the RUU will fail.
There are 3 different methods for flashing firmware: FUU, SD card method, or fastboot method. Which you use if up to you. But SD card method (obviously) requires an SD card. And fastboot method required you knowing how to use fastboot.
alinazir said:
Another thing will i be able to run the Radio in new android 6 because currently radio app is installed but it does not work at all
Click to expand...
Click to collapse
I don't know. Flash the firmware and RUU and see if the FM radio works.
alinazir said:
Can i install Android Nougat?
Click to expand...
Click to collapse
There is no official HTC Nougat (RUU) for this phone, if that is what you mean.
If you like, you can try a Nougat (or Oreo) based custom ROM after updating the firmware/RUU. But as I previously said, flashing a custom ROM is another process altogether. After flashing the firmware/RUU, you would then need to unlock the bootloader, flash custom recovery TWRP, then flash a Sprint M8 compatible custom ROM of your choice.
Better to take things one step at a time. Update firmware/RUU first. Then go from there, if you like.

redpoint73 said:
I already suggested 6.20.651.3, so I don't know why you are wasting time confusing yourself. If asking for help, please try to read/understand more carefully; instead of asking questions that have already been answere, and making me repeat myself.....
Click to expand...
Click to collapse
Dear i have installed the marshmallow firmware (0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip) from firmware Update Utility FUU. My computer Screen says that the firmware has been installed successfully. My M8 is stuck on the start HTC Logo and on bottom of it powered by android is written . Please help me what should i do now.

alinazir said:
Dear i have installed the marshmallow firmware (0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip) from firmware Update Utility FUU. My computer Screen says that the firmware has been installed successfully. My M8 is stuck on the start HTC Logo and on bottom of it powered by android is written .
Click to expand...
Click to collapse
You are not following instruction properly. You do not flash the RUU using the FUU!
RUU and firmware are two different things!
Flash the firmware (53 MB) first (using FUU, as it seems that is the method you've chosen to flash firmware).
If firmware flash is successful (you may need to flash it twice if you see an error "flush again immediately), then flash the RUU (1.5 GB). Do not use FUU to flash RUU! Since you've chosen the zip format RUU, you need to flash RUU either using htc_fastboot, or SD card method. Otherwise, download and flash RUU in exe format.

redpoint73 said:
You are not following instruction properly. You do not flash the RUU using the FUU!
RUU and firmware are two different things!
Flash the firmware (53 MB) first (using FUU, as it seems that is the method you've chosen to flash firmware).
If firmware flash is successful (you may need to flash it twice if you see an error "flush again immediately), then flash the RUU (1.5 GB). Do not use FUU to flash RUU! Since you've chosen the zip format RUU, you need to flash RUU either using htc_fastboot, or SD card method. Otherwise, download and flash RUU in exe format.
Click to expand...
Click to collapse
Ok my mistake i wrote wrong, i have installed the FUU only the 53mb file and now it is stuck on the logo what should i do? i havn't installed the RUU. Only Firmware is installed. and also when i goto the bootloader it says OS-2.16.254.4 i dont know how did this came from. i copied the Firmware File renamed it to rom.zip and install as stated in the tutorial (6.20.651.3 Signed Full Firmware...(fastboot flashable))

alinazir said:
Ok my mistake i wrote wrong, i have installed the FUU only the 53mb file and now it is stuck on the logo what should i do? i havn't installed the RUU. Only Firmware is installed. and also when i goto the bootloader it says OS-2.16.254.4 i dont know how did this came from. i copied the Firmware File renamed it to rom.zip and install as stated in the tutorial (6.20.651.3 Signed Full Firmware...(fastboot flashable))
Click to expand...
Click to collapse
Stuck on HTC logo after flashing signed firmware is normal and expected, as it expects RUU to be flashed immediately after.
However, the OS number is not normal or expected. It should have changed to 6.20.651.3. I think you mean OS number 2.16.654.4 as there is no version 2.16.254.4 that I know of. Please make sure you type these kinds of number correctly, as they are very important, and telling me the wrong number is extremely confusing!
Check you downloaded the right firmware (6.20.651.3) and flash it again. If you are still getting 2.16.654.4, then the file must be the wrong one. Try the "unsigned Full" firmware 6.20.651.3

redpoint73 said:
Check you downloaded the right firmware (6.20.651.3) and flash it again. If you are still getting 2.16.654.4, then the file must be the wrong one. Try the "unsigned Full" firmware 6.20.651.3
Click to expand...
Click to collapse
how to install the firmware without usb debugging enabled. as i have said that i cannot go to the settings, it is stuck on the logo screen.
yeah thats my bad. its os-2.16.654.4

alinazir said:
how to install the firmware without usb debugging enabled. as i have said that i cannot go to the settings, it is stuck on the logo screen.
Click to expand...
Click to collapse
You flashed the firmware before already, you said (even if it was the wrong one 2.16.654.4). Why would debugging make a difference now, if it didn't before?
Flashing firmware doesn't require debugging. Everything is done by fastboot, not adb. adb needs debugging, fastboot does not.

redpoint73 said:
You flashed the firmware before already, you said (even if it was the wrong one 2.16.654.4). Why would debugging make a difference now, if it didn't before?
Click to expand...
Click to collapse
I have done the firmware with firmware update utility tool. not by fastboot. Can you please guide me how to do it with fastboot?

alinazir said:
I have done the firmware with firmware update utility tool. not by fastboot. Can you please guide me how to do it with fastboot?
Click to expand...
Click to collapse
Doing it with the FUU is fine. The FUU still connects via fastboot, and doesn't need adb, as far as I know.

redpoint73 said:
Doing it with the FUU is fine. The FUU still connects via fastboot, and doesn't need adb, as far as I know.
Click to expand...
Click to collapse
When the program ARUWizard.exe runs it says no device is connected. i used HTC Android Phone Firmware Update Utility 2.0.12.2014

alinazir said:
When the program ARUWizard.exe runs it says no device is connected. i used HTC Android Phone Firmware Update Utility 2.0.12.2014
Click to expand...
Click to collapse
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.

redpoint73 said:
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.
Click to expand...
Click to collapse
The first time i did it wasn't in bootloader. only usb debugging was on and nothing else. phone was on. it is again on the logo screen.

redpoint73 said:
It worked before, so it makes no sense that it doesn't work now. Try another cable, or another USB port. Make sure the phone is in bootloader-fastboot mode.
Click to expand...
Click to collapse
OK firmware installed now how would you suggest me to install the RUU?

alinazir said:
The first time i did it wasn't in bootloader. only usb debugging was on and nothing else. phone was on.
Click to expand...
Click to collapse
Honestly, I haven't used the FUU. But if it's the same as RUU, it works in fastboot mode.
Or just try fastboot or SD card methods. The instructions are on the thread you got the firmware from.
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
alinazir said:
OK firmware installed now how would you suggest me to install the RUU?
Click to expand...
Click to collapse
I gave you the options, and the differences between them. Make the decision yourself. I don't even understand why you are asking me this question.
The RUU is similar to the FUU, but even easier. Just download and run it. So that is probably your best bet.
---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------
alinazir said:
OK firmware installed now how would you suggest me to install the RUU?
Click to expand...
Click to collapse
How about explaining what you did different to make it work?

redpoint73 said:
How about explaining what you did different to make it work?
Click to expand...
Click to collapse
Actually i am a newbee i didn't knew that firmware can be updated in fastboot mode. i just did as you told me to do. Now i am installing the RUU from the .exe file. lets see what happens now. Thanks for ur help.

redpoint73 said:
How about explaining what you did different to make it work?
Click to expand...
Click to collapse
Rom Updated Successfully, Now Sprint Logo came and then htc logo, after that the phone turns on, then it got stuck on Hands Free Activation, and keeps on rotating the Activation. and its been half an hour its doing that.

alinazir said:
Rom Updated Successfully, Now Sprint Logo came and then htc logo, after that the phone turns on, then it got stuck on Hands Free Activation, and keeps on rotating the Activation. and its been half an hour its doing that.
Click to expand...
Click to collapse
Forgot about that Sprint Hands Free Activation crap. So you can't get past that, by pressing home, back, or anything like that?