Develop Bugs

[Q] How do i get the latest OTA update on my HTC One M8

Hey, im trying to install the latest OTA update on my htc one m8 (software update: 4.20.710.5)
right now i have stock htc sense 6 - android 4.4.4, with the latest twrp recovery install along with s=on.
Information for my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
software number: 3.32.710.9
so far i have downloaded the ota update within stock sense, however as soon as i go to update it, it takes me straight to the twrp recovery. making it unable to install the update. and i know that i must revert to the stock recovery to do so.
To fully revert my HTC m8 i have 2 options
1. find a RUU compatible with my device.
2. find a stock recovery image.
So far i have had no luck with finding a working RUU, and the closest i have gotten was flashing a ruu.zip that matched my software number and kernal with the hasoon 2000 v2 toolkit, however i received: signature verify failed
is anyone able to find me a RUU that is compatible with my device and tell me the steps to running/installing this RUU, or are you able to find me a stock recovery image that is compatible with my device.
p.s. if i am to install the wrong stock recovery is there anyway to fix it? as i do not want to run into a brick.
(extra information: I am living in New Zealand, Using Vodafone as my carrier)
Thanks.
Tom.

Tom Hyde said:
Hey, im trying to install the latest OTA update on my htc one m8 (software update: 4.20.710.5)
right now i have stock htc sense 6 - android 4.4.4, with the latest twrp recovery install along with s=on.
Information for my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
software number: 3.32.710.9
so far i have downloaded the ota update within stock sense, however as soon as i go to update it, it takes me straight to the twrp recovery. making it unable to install the update. and i know that i must revert to the stock recovery to do so.
To fully revert my HTC m8 i have 2 options
1. find a RUU compatible with my device.
2. find a stock recovery image.
So far i have had no luck with finding a working RUU, and the closest i have gotten was flashing a ruu.zip that matched my software number and kernal with the hasoon 2000 v2 toolkit, however i received: signature verify failed
is anyone able to find me a RUU that is compatible with my device and tell me the steps to running/installing this RUU, or are you able to find me a stock recovery image that is compatible with my device.
p.s. if i am to install the wrong stock recovery is there anyway to fix it? as i do not want to run into a brick.
(extra information: I am living in New Zealand, Using Vodafone as my carrier)
Thanks.
Tom.
Click to expand...
Click to collapse
Restore the 1.12.710.17 - CWM Philz touch from the below link:
https://docs.google.com/uc?id=0B9YiQrvWNwpRa25zZFUyTzIwbUk&export=download
Flash stock recovery 1.12.710.17 recovery.img from the below link:
https://www.androidfilehost.com/?w=files&flid=24386
Then install the latest OTA update and you are good to go.

shafez said:
Restore the 1.12.710.17 - CWM Philz touch from the below link:
Then install the latest OTA update and you are good to go.
Click to expand...
Click to collapse
Thanks you for you quick response, I am pretty sure I understand but just to clarify a little. Am I meant to restore to that 1.12.710.17 VIA TWRP restore.
Also even though this stock recovery should be correct, would flashing the wrong stock recovery lead to problems ?
Thanks.
Tom.

Tom Hyde said:
Thanks you for you quick response, I am pretty sure I understand but just to clarify a little. Am I meant to restore to that 1.12.710.17 VIA TWRP restore.
Also even though this stock recovery should be correct, would flashing the wrong stock recovery lead to problems ?
Thanks.
Tom.
Click to expand...
Click to collapse
Use Philz touch recovery to restore the backup and the flash the stock recovery.

Those files won't work for your device that has a higher version hboot 3.19.0000 and S-On.
You'll get stuck when applying OTA.
You said that you have stock ROM running. What you need is stock recovery image.
Get your stock recovery image 3.32.710.9 here :
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

ckpv5 said:
Those files won't work for your device that has a higher version hboot 3.19.0000 and S-On.
You'll get stuck when applying OTA.
You said that you have stock ROM running. What you need is stock recovery image.
Get your stock recovery image 3.32.710.9 here :
Click to expand...
Click to collapse
Ok Thanks. But are you able to provide me with the direct link to the download I need as I am abit confused by that post.
Also to answer my other question. What is to happen if you install the wrong stock recovery or something goes wrong in the installation process of the stock recovery?
Thanks.
Tom.

Click on the numbers, for your case click on 3.32.710.9 then you get the link.
If you install a wrong stock recovery, your OTA installation will fail. That's all.
If your installation fails due to ROM not stock enough, make a request for the stock backup in that thread then I'll update with link to download stock ROM backup.

ckpv5 said:
Click on the numbers, for your case click on 3.32.710.9 then you get the link.
If you install a wrong stock recovery, your OTA installation will fail. That's all.
If your installation fails due to ROM not stock enough, make a request for the stock backup in that thread then I'll update with link to download stock ROM backup.
Click to expand...
Click to collapse
Ok , Thank you so much.
I'm going to be doing this all very soon , and will let you now how it goes.
Thanks.
Tom.
UPDATE:
The Stock recovery worked perfectly. I manged to flash the recovery, update my phone and put twrp back onto my phone.
Thanks for the great help.
Tom.

Hi Tom Hyde,
I am glad to see you solved a problem I am experiencing...
I want to update from 4.4.4 to lollipop, I need the VODAP021, 3.32.710.9 stock recovery
Can you please tell me how your extracted the stock recovery from that link (http://forum.xda-developers.com/htc-...-twrp-t3086860)? I downloaded the whole file (1.4GB) as a zip file, but once open I cant find the stock recovery.img file that I need. How did you do it?
Many Thanks

sandemask said:
Hi Tom Hyde,
I am glad to see you solved a problem I am experiencing...
I want to update from 4.4.4 to lollipop, I need the VODAP021, 3.32.710.9 stock recovery
Can you please tell me how your extracted the stock recovery from that link (http://forum.xda-developers.com/htc-...-twrp-t3086860)? I downloaded the whole file (1.4GB) as a zip file, but once open I cant find the stock recovery.img file that I need. How did you do it?
Many Thanks
Click to expand...
Click to collapse
The 1.4GB is nandroid backup not stock recovery.
Stock recovery 3.32.710.9 you can find it in post #4 in the same thread (also linked in my signature)

ckpv5 said:
The 1.4GB is nandroid backup not stock recovery.
Stock recovery 3.32.710.9 you can find it in post #4 in the same thread (also linked in my signature)
Click to expand...
Click to collapse
Thank you ckpv5,
I didn't register the link the first time. I will let you know how I go
Cheers

ckpv5 said:
The 1.4GB is nandroid backup not stock recovery.
Stock recovery 3.32.710.9 you can find it in post #4 in the same thread (also linked in my signature)
Click to expand...
Click to collapse
Hi ckpv5,
I dowloaded the stock recovery I needed and it worked. I update from 4.4.4 kitkat to 5.0.1 Lollipop. Now my phone software number is 4.20.710.5
But after the update I run through some problems:
1. Right after the update, I got a notification for another system update 4.20.710.7. So I hit the download and install. But the install didn't complete, it stopped with that red triangle. So I rebooted back to 4.20.710.5
2. My phone shows that I have coverage and data connections, but I cant use internet for some reason. It works fine on Wi-fi though
3. Using ES file explorer, I cant detect my external sdcard. Can't play music on my external sdcard
Would you know how to solve the above issues?
Many Thanks

1. When you have that red triangle, you hold and press volume up button and tap power button once. This will take you to the recovery page where you can read what error tha you have. Usually unexpected content of some system files
2. Check what OS is written on bootloader - is it 4.20.710.5 or 4.20.710.7
I believe the update failed and you still have 4.20.710.5 written on bootloader
3. No idea about that. What you can do is restore a non-rooted stock 4.20.710.5 backup (system part is enough). You can get the backup in my thread. Then redo OTA.

ckpv5 said:
1. When you have that red triangle, you hold and press volume up button and tap power button once. This will take you to the recovery page where you can read what error tha you have. Usually unexpected content of some system files
2. Check what OS is written on bootloader - is it 4.20.710.5 or 4.20.710.7
I believe the update failed and you still have 4.20.710.5 written on bootloader
3. No idea about that. What you can do is restore a non-rooted stock 4.20.710.5 backup (system part is enough). You can get the backup in my thread. Then redo OTA.
Click to expand...
Click to collapse
Thanks again for your reply.
1.I pressed the volume up and power buttons, and I got this message:
Fiinding update package...
OPening update package...
Verifying update package...
Installing update...
L50QCT.01.101.009
Package expects build fingerprint of Htc/htc_asia_aus/htc_m8:5.0.1/LRX22C/463267.5:user/release-keys or htc/htc_asia_aus/htc_m8:5.0.1/LRX22C/463267.7:user/release-keys; this device has htc/htc_asia_aus/htc_m8:4.4.4/KTU84P/397296.9:user/release-keys
Installation aborted
Write host_mode: 0 done
2. Yes bootloader is still 4.20.710.5
3.When I used the non-rooted 3.32.710.9 stock to update to 4.20.710.5. Does it mean my stock recovery is also updated or it remains the 4.4.4 one?
Hopefully I am making sense

1. The error shows that wrong recovery is used for OTA.
It expects 4.20.710.5 or 4.20.710.7 recovery but your device has 3.32.710.9 recovery installed.
2. As expected
3. The recovery should get updated with OTA and it's weird that you have the old recovery intact.
Like it's weird that the latest AUS OTA has funny file in it - a z01 file or something that some people say it's some video file.
You can try again the OTA. Install 4.20.710.5 recovery and see how it goes.

Issue!! (SOLVED)
ckpv5 said:
1. The error shows that wrong recovery is used for OTA.
It expects 4.20.710.5 or 4.20.710.7 recovery but your device has 3.32.710.9 recovery installed.
2. As expected
3. The recovery should get updated with OTA and it's weird that you have the old recovery intact.
Like it's weird that the latest AUS OTA has funny file in it - a z01 file or something that some people say it's some video file.
You can try again the OTA. Install 4.20.710.5 recovery and see how it goes.
Click to expand...
Click to collapse
I was having this same issue when trying to process the OTA update.
i was on stock recovery 3.32.710.9 (device had stock rom yet was rooted). each time i tried to process the OTA update it got halfway and then displayed the red triangle.
i followed your idea and flashed the other stock recovery (4.20.710.5) i then proceeded to install the OTA update. The update seemed to work, however now the phone boots and gets stuck at the HTC one screen (second htc one screen) i am now lost for what to do, any idea?
EDIT: i managed to get to the bootloader by holding power and volume up and then switching to volume down after the screen turns black. what procedure should i undertake once i am at the bootloader (remember: i have recovery 4.20.710.5 and i had just done the update)
extra info: i can use fastboot commands from pc and i receive the following information
C:\Users\Tom\Desktop\Toms Backup\ssd items\Stuff_for_Android_Phone\returning to stock recovery and sense\fastboot\android-sdk-windows\platform-tools>fastboot oem readcid
...
(bootloader) cid: VODAP021
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Tom\Desktop\Toms Backup\ssd items\Stuff_for_Android_Phone\returning to stock recovery and sense\fastboot\android-sdk-windows\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.710.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(bootloader) security: on
all: Done!
finished. total time: 0.038s
SECOND EDIT: sorry for another edit but i have fixed the problem
i tried all three recoveries or 3.32.710.9, 4.20.710.5 and 4.20.710.7 however they all resorted in a bootloop. i finally decided to flash the twrp recovery and luckily i had a stock 4.4.4 android backup on my sd card. i restored to this backup via twrp and the phone boots up normally.
i will now go bout flashing the stock recovery and trying to update from there, without rooting.
sorry for wasting your time reading this.
Tom.

Tom Hyde said:
I was having this same issue when trying to process the OTA update.
i was on stock recovery 3.32.710.9 (device had stock rom yet was rooted). each time i tried to process the OTA update it got halfway and then displayed the red triangle.
i followed your idea and flashed the other stock recovery (4.20.710.5) i then proceeded to install the OTA update. The update seemed to work, however now the phone boots and gets stuck at the HTC one screen (second htc one screen) i am now lost for what to do, any idea?
EDIT: i managed to get to the bootloader by holding power and volume up and then switching to volume down after the screen turns black. what procedure should i undertake once i am at the bootloader (remember: i have recovery 4.20.710.5 and i had just done the update)
extra info: i can use fastboot commands from pc and i receive the following information
C:\Users\Tom\Desktop\Toms Backup\ssd items\Stuff_for_Android_Phone\returning to stock recovery and sense\fastboot\android-sdk-windows\platform-tools>fastboot oem readcid
...
(bootloader) cid: VODAP021
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Tom\Desktop\Toms Backup\ssd items\Stuff_for_Android_Phone\returning to stock recovery and sense\fastboot\android-sdk-windows\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.710.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: deleted
(bootloader) imei: deleted
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(bootloader) security: on
all: Done!
finished. total time: 0.038s
SECOND EDIT: sorry for another edit but i have fixed the problem
i tried all three recoveries or 3.32.710.9, 4.20.710.5 and 4.20.710.7 however they all resorted in a bootloop. i finally decided to flash the twrp recovery and luckily i had a stock 4.4.4 android backup on my sd card. i restored to this backup via twrp and the phone boots up normally.
i will now go bout flashing the stock recovery and trying to update from there, without rooting.
sorry for wasting your time reading this.
Tom.
Click to expand...
Click to collapse
DUDE!!
Delete the ser# and IMEI from your post. That is private info that you shouldn't share on a public forum.

Tom Hyde said:
SECOND EDIT: sorry for another edit but i have fixed the problem
i tried all three recoveries or 3.32.710.9, 4.20.710.5 and 4.20.710.7 however they all resorted in a bootloop. i finally decided to flash the twrp recovery and luckily i had a stock 4.4.4 android backup on my sd card. i restored to this backup via twrp and the phone boots up normally.
i will now go bout flashing the stock recovery and trying to update from there, without rooting.
Tom.
Click to expand...
Click to collapse
It was mentioned before, you can't do OTA with a rooted ROM.
Actually you can use 4.20.710.5 backup that I have in my thread, then you need to do 2 OTAs only 4.20.710.7 and 4.20.710.9
If the 4.4.4 backup is good then it's good.
If it fails or you get stuck you can try 4.20.710.5 or just wait I update the link for 4.20.710.7 when I'm home on Sunday.

[Q] Phone not quite right after 'back to stock'.

I used a nandroid backup I did when I first got my phone - trying to go back to stock, which is unfortunately 'carrier branded' (O2 - UK) quick bullet points then. I then installed a stock recovery I found which I THINK is the correct one... :S
1: The O2 splash screen at startup isnt there, which I thought it would be?
2: When I did a factory reset one one of the startup screens it told me my device was a test device (I can elaborate if needs be).
3: When I tried to do an OTA update to 2.22.206.6 (Android 4.3) it failed. The recovery screen log said
Code:
E: missing bitmap oem_unlock_bg
(code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code - 1)
Finding update package...
Opening Update Package...
Verifying Update Package...
Installing Update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error in /data/media/0/Download/OTA_M8_UL_K44_SENSE60_MR_2_UK_2.22.206.6-1.54.206.10_release_387646.zip
(Status 7)
Installation Aborted
Here is a getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA45DWM02823
(bootloader) imei: 3**************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

tmorterlaing said:
I then installed a stock recovery I found which I THINK is the correct one... :S
Click to expand...
Click to collapse
Which stock recovery did you flash?
Did you do any other modifications before making the nandroid (aside from custom recovery and root) such as deleting any bloat apps?

redpoint73 said:
Which stock recovery did you flash?
Did you do any other modifications before making the nandroid (aside from custom recovery and root) such as deleting any bloat apps?
Click to expand...
Click to collapse
Thanks so much for the quick reply
I did no other mods before the nandroid other than installing TWRP recovery - it was the first thing I did after installing TWRP. I don't know if you have to S-OFF before installing recovery - I would've done that if so.
Installed this recovery: https://www.androidfilehost.com/?w=files&flid=24260
The bottom one on the list.

tmorterlaing said:
Installed this recovery: https://www.androidfilehost.com/?w=files&flid=24260
The bottom one on the list.
Click to expand...
Click to collapse
There are a few things going wrong here:
1) You apparently reverted to stock software build 1.x (either 1.12 or 1.54) based on the fact that OTA 2.22 is trying to install.
2) Normally, you want the stock recovery that corresponds with your software build, so 1.12 or 1.54.
3) However, it seems you have already "manually" updated the firmware (by s-off) to the WWE Euro Lollipop firmware (not O2), as indicated by your main version number (4.16.401), as well as hboot and radio numbers. Its the "401" that marks this as the WWE "international" version. "206" would appear in that location in the build numbers for O2 branded software.
Point 3 above raises the question, why even return to stock at all if you already have updated (Lollipop) firmware?
You can revert to the 1.x firmware (which should allow you to install the 2.22.206 OTA); or alternately you should be able to install the stock ROM 4.16.401 to match the present firmware (which will effectively make the phone the "international" WWE version , not O2). No OTA will presently install after this (since it would already be updated to Lollipop) but you should get future OTA.
But again, I'm guessing a bit here, since its not clear what you end goal is.

redpoint73 said:
There are a few things going wrong here:
But again, I'm guessing a bit here, since its not clear what you end goal is.
Click to expand...
Click to collapse
Thanks so much! My goal was to take it to full 'o2' stock,so I could take it into a store if I needed to. I assumed the nandroid wouldn't have lost the o2 thing though is there a way of returning it to exactly as I got it ?

tmorterlaing said:
Thanks so much! My goal was to take it to full 'o2' stock,so I could take it into a store if I needed to. I assumed the nandroid wouldn't have lost the o2 thing though is there a way of returning it to exactly as I got it ?
Click to expand...
Click to collapse
I too would think the carrier boot splash would return with the nandroid (usually part of the ROM or system partition, as far as I am aware).
You can try to flash the firmware that corresponds with your nandroid, and see if that helps. This should also put the phone in the proper configuration for OTA updates for O2.
While still on the original stock nandroid, what does it say for OS in Settings or on bootloader screen? I'm guessing its 1.54.206 (but 1.12.206 is also possible).

redpoint73 said:
I too would think the carrier boot splash would return with the nandroid (usually part of the ROM or system partition, as far as I am aware).
You can try to flash the firmware that corresponds with your nandroid, and see if that helps. This should also put the phone in the proper configuration for OTA updates for O2.
While still on the original stock nandroid, what does it say for OS in Settings or on bootloader screen? I'm guessing its 1.54.206 (but 1.12.206 is also possible).
Click to expand...
Click to collapse
It didn't - I followed the above instructions, the firmware was all sorted (someone had kindly provided it around XDA), which all worked fine. I was then able to do OTA updates right through to Lollipop - but no splash screen came back. Either I did the nandroid wrong, or its hidden somewhere else... or something.... confused!
Perhaps the only way is to get some sort of O2 RUU, but I guess someone would have to provide that right?

M8 frozen system

Hello all,
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
"fastboot getvar all" returns this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
Now the interesting part. Every time the phone reboots, it is always in the same state as if the partitions were frozen. That is to say for instance if I uninstall an app and then reboot, the app is there again. If I connect to a Wifi network and reboot, it disappears. Every single modification is erased and returns back to the same state. The most annoying thing is that when I connect to a Wifi the apps start synchronizing, crash and the phone reboots.
I tried the following:
- Factory reset from the interface to no avail as it returns to the state it was as well
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
- Tried "fastboot oem rebootRUU", which simply reboots the phone into android
- Tried to unlock the bootloader, which again reboots the phone into android
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
- Tried to flash only the zip from the RUU and ends up with the same signature error
I simply can't think of anything else to do, and I hope one of the gurus can help me in my quest
Thank you for the time you spent reading my post.

My responses/comment below in red font:
tyraek said:
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
(bootloader) version-main: 1.58.502.1
It doesn't appear to have had any OTA updates. Or at most a minor update from 1.54>1.58.
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
Try pressing vol up and power to show the stock recovery menu options. I believe factory reset is one of those options, although if wiping in OS didn't work; I doubt doing so from stock recovery will be any different.
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
Which RUU (exact filename)? There are many, and the RUU has to be intended for your CID version.
What error number, and what error message? This is very important, otherwise we have no idea why it failed.
You're on the right track, by trying to run an RUU. I think its your best bet to fix the issue. But we need to make sure you run the right RUU.
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
You can't flash recovery with a locked bootloader.
- Tried to flash only the zip from the RUU and ends up with the same signature error
Again, which RUU specifically is very important. Can't tell if the RUU is the right one based on the info given.
Also, please verify on the hboot screen, near the top, if it says LOCKED (other possibilities being UNLOCKED and RELOCKED)
Click to expand...
Click to collapse

Thank you so much for your reply.
I have tried the factory reset from the recovery and the result is the same.
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
The update states it will upgrade from 1.58.502.1 to 4.28.502.2. Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.

bump

tyraek said:
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Click to expand...
Click to collapse
Yes, this is for your model (AT&T) and the version number will work.
tyraek said:
Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
.
Click to expand...
Click to collapse
This is means there is a USB communication issue, usually on the PC side, and there is nothing wrong with the RUU or the phone.
RUU is very finicky, and this issue is common. Try a different cable, different USB port, and try to re-install HTC Sync.
But you may have to resort to using another computer. Win7 and USB 2.0 (USB 3.0 is known to cause issues with RUU) are the best bet to get the RUU to run properly.
tyraek said:
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
Click to expand...
Click to collapse
Do not unlock the bootloader if you intend to RUU. Unlocked bootloader will actually cause the RUU to fail, by definition. RUU requires the bootloader by LOCKED or RELOCKED (or else you need s-off to run an RUU with the bootloader UNLOCKED).

recovery cant open last_install

HTC One m8 unlocked with s-on running android 5.0.2.
I downloaded the OTA for android marshmallow and trying to manually update but when I enter recovery and choosing "Apply from phone storage" it replays:
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: no CW Files. Skip cw installation.
then i choose to apply from phone storage (this is where the OTA file is) and my recovery says:
E: find no match PARTIOTION: for package path /date/medai/0/pt.zip
E: unknown valume for path [ ]
E: Can't mount
E: Failed to open last_install: no such file or directory
Finding update package...
opening update package...
E: failed to map file
anyone know how to fix this?

You can't manually install OTA on S-On device.
Post fastboot getvar all result without serial & imei no.
We'll see whether there is RUU that you can run directly to update your device.

ckpv5 said:
You can't manually install OTA on S-On device.
Post fastboot getvar all result without serial & imei no.
We'll see whether there is RUU that you can run directly to update your device.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d5206dbc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Harellevy said:
(bootloader)
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) security: on
Click to expand...
Click to collapse
You have 2 options -
1. Restore the non-rooted 4.24.709.3 stock backup and 4.24.709.3 stock recovery then do OTA to 6.20.709.2 (let the system install, not manual install)
You can get the files and how-to here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. Install RUU 6.20.709.2.zip as someone else already mention to you in other thread.

ckpv5 said:
You have 2 options -
1. Restore the non-rooted 4.24.709.3 stock backup and 4.24.709.3 stock recovery then do OTA to 6.20.709.2 (let the system install, not manual install)
You can get the files and how-to here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. Install RUU 6.20.709.2.zip as someone else already mention to you in other thread.
Click to expand...
Click to collapse
I am on 4.24.709.3 without root.
And when I try to flash the RUU he provided it says "can't load RUU.zip" when I try to flash

Harellevy said:
I am on 4.24.709.3 without root.
And when I try to flash the RUU he provided it says "can't load RUU.zip" when I try to flash
Click to expand...
Click to collapse
Most of the time it is because the hidden windows extension where you have RUU.zip.zip instead of RUU.zip
Also the RUU.zip must be placed in your fastboot/adb folder and you need to use htc_fastboot not generic fastboot
As you device is S-On you need to relock bootloader before you can install RUU and this will wipe everything in your internal storage.
I always prefer to use the nandroid restore method and do OTA, less hassle.
If you still want to use the RUU method, you need :
1. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. Follow this guide but replace the RUU.zip with yours - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
Most of the time it is because the hidden windows extension where you have RUU.zip.zip instead of RUU.zip
Also the RUU.zip must be placed in your fastboot/adb folder and you need to use htc_fastboot not generic fastboot
As you device is S-On you need to relock bootloader before you can install RUU and this will wipe everything in your internal storage.
I always prefer to use the nandroid restore method and do OTA, less hassle.
If you still want to use the RUU method, you need :
1. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. Follow this guide but replace the RUU.zip with yours - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I restored 4.24.709.3 and the recovery and I have no OTA, how is this possible?

Harellevy said:
I restored 4.24.709.3 and the recovery and I have no OTA, how is this possible?
Click to expand...
Click to collapse
I don't know the real reason but it seems like the OTA is no more on HTC server or HTC stop releasing OTA .. because I read few reports that no more updates when checking for update on other device region too. Even on EU WWE I read the same report.
So ... try the RUU method.

ckpv5 said:
I don't know the real reason but it seems like the OTA is no more on HTC server or HTC stop releasing OTA .. because I read few reports that no more updates when checking for update on other device region too. Even on EU WWE I read the same report.
So ... try the RUU method.
Click to expand...
Click to collapse
I cant seem to find the RUU for my device with my software.
I have CID HTC__621 with 4.24.709.3.
All I seem to find is OTA (this) but when I try to manually update it wont let me (see the first post).
Any ideas on how to update? Or if you know where can I get the RUU for my device?
EDIT: Someone gave me this as RUU for my device: https://www.androidfilehost.com/?fid=24391638059058090
yet it says its for 4.24.709.2 and im on 709.3. when I tried to flash it I got "cant load M8_UL_M60_SENSE70_MR_hTC_Asia_TW_6.20.709.2.zip"

Harellevy said:
I cant seem to find the RUU for my device with my software.
I have CID HTC__621 with 4.24.709.3.
All I seem to find is OTA (this) but when I try to manually update it wont let me (see the first post).
Any ideas on how to update? Or if you know where can I get the RUU for my device?
EDIT: Someone gave me this as RUU for my device: https://www.androidfilehost.com/?fid=24391638059058090
yet it says its for 4.24.709.2 and im on 709.3. when I tried to flash it I got "cant load M8_UL_M60_SENSE70_MR_hTC_Asia_TW_6.20.709.2.zip"
Click to expand...
Click to collapse
Already mentioned on post #2 - you cannot manually install OTA zip on S-On device.
That's not RUU ... and AFAIK there is no Marshmallow RUU for your device version.
I give you another way to update your device to stock Marshmallow :
Reference - my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Install latest TWRP 3.0.2-0
2. Download fw_6.20.709.2.zip from my thread - post #5
3. Download and restore 6.20.709.2 nandroid from my thread - post #3
4. After restore is complete, go to reboot menu then select reboot to bootloader
5. Depends on where you put the fw_6.20.709.2.zip - must be in fastboot/adb folder (or anywhere if using system-wide adb/fastboot) - open command promt
6. Run these commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_6.20.709.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_6.20.709.2.zip
fastboot reboot
Done ... now you have stock Marshmallow.
Note : if you want to install TWRP again, you need to re unlock bootloader with unlock_code.bin
and this process will wipe your internal storage - make backup first all your important files like photos & musics.

ckpv5 said:
Already mentioned on post #2 - you cannot manually install OTA zip on S-On device.
That's not RUU ... and AFAIK there is no Marshmallow RUU for your device version.
I give you another way to update your device to stock Marshmallow :
Reference - my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
1. Install latest TWRP 3.0.2-0
2. Download fw_6.20.709.2.zip from my thread - post #5
3. Download and restore 6.20.709.2 nandroid from my thread - post #3
4. After restore is complete, go to reboot menu then select reboot to bootloader
5. Depends on where you put the fw_6.20.709.2.zip - must be in fastboot/adb folder (or anywhere if using system-wide adb/fastboot) - open command promt
6. Run these commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_6.20.709.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_6.20.709.2.zip
fastboot reboot
Done ... now you have stock Marshmallow.
Click to expand...
Click to collapse
You are awesome!
I will do it as soon as I get back home from work and will let you know if it did
I though you can't flash firmware with s-on. maybe I dont recall right.

Harellevy said:
I though you can't flash firmware with s-on. maybe I dont recall right.
Click to expand...
Click to collapse
You can only flash HTC signed firmware on S-On device and the bootloader must be LOCKED or RELOCKED.

ckpv5 said:
You can only flash HTC signed firmware on S-On device and the bootloader must be LOCKED or RELOCKED.
Click to expand...
Click to collapse
Do I need stock recovery to flash the firmware?
EDIT: Okay I got marshmallow. Thank you very much!
1 last question - will I get any future OTA's?

Harellevy said:
Do I need stock recovery to flash the firmware?
EDIT: Okay I got marshmallow. Thank you very much!
1 last question - will I get any future OTA's?
Click to expand...
Click to collapse
No need for stock recovery because the firmware itself will install stock recovery.
Yes .. you'll get future OTA if any .. but being a two years old device and HTC usually stop the support after two years, I don't think there will be any future OTA.

Locked m8 same issue
I've been trying to find an answer to this issue everywhere mine is LOCKED and had software issues since purchase.. it has never successfully backed up no matter the route I tried.. it's freezing requiring restart at least 2x's a day and the restart is becoming less accessible.. everything is on this phone.. please help???
Harellevy said:
HTC One m8 unlocked with s-on running android 5.0.2.
I downloaded the OTA for android marshmallow and trying to manually update but when I enter recovery and choosing "Apply from phone storage" it replays:
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: no CW Files. Skip cw installation.
then i choose to apply from phone storage (this is where the OTA file is) and my recovery says:
E: find no match PARTIOTION: for package path /date/medai/0/pt.zip
E: unknown valume for path [ ]
E: Can't mount
E: Failed to open last_install: no such file or directory
Finding update package...
opening update package...
E: failed to map file
anyone know how to fix this?
Click to expand...
Click to collapse

Htc one m8 bricked?!?! Stuck on boot screen (htc logo)!

Hi guys I have an HTC ONE M8 running 4.4.4 with TWRP and Root installed and a few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual. When I did that and rebooted the phone, the phone is stuck on the HTC logo and I can only boot into bootloader mode and also into TWRP. Also TWRP is also saying I have lost root access.
What can I do to fix this problem can I restore back to 4.4.4 as a new device and re-root it and install TWRP? How do I get out of this mess? It is S-ON and Software Status is MODIFIED.
No matter how long I leave the phone it will stay on the logo until it dies or until I boot into bootloader.
Thank You Guys I Have Lost Hope Honestly.
IF ANYONE CAN HELP ME PLEASE PROVIDE THOROUGH INSTRUCTIONS! THANK YOU!

First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
TechMan123456 said:
few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual.
Click to expand...
Click to collapse
What does "and such" mean? Did you wipe anything besides cache and Dalvik?

redpoint73 said:
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
Click to expand...
Click to collapse
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.

TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup

xunholyx said:
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
Click to expand...
Click to collapse
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.

TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
you can use a card reader to put the rom or the backup on external sd card
or use an OTG USB flash memory
also connect the device to pc while you are in recovery this should work by it self no need to install MTP driver
which OS you have on your pc ??

TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
No OS is usually an easy fix. Download a ROM on your PC, put it onto your extSD, and flash the ROM in recovery. The reason you have no OS is because you wiped system in TWRP. If you do that, you need to flash a ROM after or you'll have no OS on a reboot.
It's best to never wipe system in TWRP as this is done by default in recovery when you flash a ROM. There will be the odd instance that it is suggested to wipe it ( I've never seen that with HTC based ROMs), but if it isn't then don't.
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
Ahhh, reding it a second time I realize you mean OS is blank in your bootloader. You should also update your TWRP version

TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
Not clear which drivers you are trying to install, the HTC drivers from their website, the ones which load from the phone, built-in Windows drivers, etc.?
Try going to HTC's website, and download HTC Sync, which will also install the drivers. If you already have this installed, try uninstalling, and re-install.
Alternately, the Android MTP device drivers built-in to Windows is a generic version of drivers which can often get at least adb/fastboot working, and probably also allow you to drag/drop to internal storage in TWRP. If these drivers are the ones failing to install, it would imply there is something wrong with your Windows installation (which there isn't a lot we can help you with) rather than anything with the phone.

hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank

Arslan8997 said:
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Click to expand...
Click to collapse
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?

redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
Click to expand...
Click to collapse
I also try RUU sprint version ROM but it didn't work
TWRP v2.7.0.2
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Arslan8997 said:
I also try RUU sprint version ROM but it didn't work
Click to expand...
Click to collapse
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Click to expand...
Click to collapse

redpoint73 said:
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
Click to expand...
Click to collapse
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Status of phone is
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Arslan8997 said:
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Click to expand...
Click to collapse
You need to flash the firmware 6.20.651.3 in order for the RUU to install (firmware and RUU are different things - so don't confuse the two). The firmware and how to flash are described here (as well as all the Sprint RUUs): https://forum.xda-developers.com/showthread.php?t=2729173
Just a heads up, if you don't know already: No need to relock the bootloader to do this (flash either firmware or RUU) since you are s-off, and no benefit in doing so. Plus, relocked bootloader gives you less options to recovery, so it is not recommended to relock it in your case.
Also, in regards to your original question (no boot after restoring TWRP backup): you never answered my question of how you picked a TWRP backup to download and restore (which I asked twice before). Now that I see you have the Sprint version M8, I will guess that you tried to restore the incorrect version backup. Sprint version uses different kernel from most other M8 versions. So if you don't restore the proper one, no boot is the expected outcome. Also, even if Sprint, it would have to be the same version you were on before (Kitkat) which is another reason it would not boot.