Develop Bugs

[Q] Bootloop of Death? Is it Bricked?

Any help would be appreciated ...
I got this EVO 4G phone 2nd hand recently. The device keeps rebooting at the initial white "HTC Evo 4G" splash screen. And I cannot access RECOVERY.
I CAN access the BOOTLOADER screen that allows me to switch between HBOOT, HBOOT USB, and FASTBOOT modes.
I CAN access the device using FASTBOOT
I CAN reapply the original RUU exe. The RUU process finishes just fine, but it still doesn't fix the phone. The phone still continually reboots.
I CAN reapply the same RUU version using the PC36IMG.ZIP method. Same experience - process finishes just fine, but it still doesn't fix the phone.
I CAN switch the device's BOOTLOADER from "UNLOCKED" to "RELOCKED" (and back again) easily using HTC Unlocker method via FASTBOOT.
I CAN flash a custom recovery image, but it never seems to "take". Meaning afterward, it still wont boot the recovery after successfully flashing the recovery image/partition. Just simply reboots over again.
I CAN download and setup the CORRECT Windows Drivers. All that seems fine.
I cannot get access to the stock recovery, even after the RUU flash seemingly completes successfully.
I cannot access any custom recovery, even seemly after I flash one successfully (tried RA, CRM, and others).
I cannot access "Recovery" at all. Either by using VOLDWN+PWR, or from the BOOTLOADER selection choice. When I try, it just simply reboots continually still.
Obviously, I cannot access the Android OS - so I cannot "enable USB debugging"
I cannot get access ADB. It has always said "No Devices Found" - the Windows Drivers are installed.
I cannot get unReVoked or Revolutionary to work. They always "waiting for device" even if the phone is in connected via FASTBOOT.
I cannot switch to S-OFF, since I really only have access to BOOTLOADER and FASTBOOT.
I've reviewed a ton of threads over the past 5 days. Tried everything I can think of, and everything I found on the internet.
I would like to ROOT this device, or downgrade it's HBOOT, or go to S-OFF. But the problems listed above have limited me from doing those things, in one way or another.
It's hard to believe that I can access FASTBOOT, and UNLOCK/RELOCK the BOOTLOADER, and "seemingly" flash images - and still not fix this issue.
The phone is not under warrenty. Sprint wont take it back or fix it.
This is a VERY SIMILIAR ISSUE to the thread http://forum.xda-developers.com/showthread.php?t=187926
I'm looking for new ideas.
Is this the definition of "bricked"?
Is this considered the Bootloop of Death, and has no cure?
Is there a way to downgrade the HBOOT using just FASTBOOT? Seems like everything hates 2.18.00001.
Is there a way to flash a new KERNEL using just FASTBOOT? Would that help?
Any kind of help would be appreciated.
Here's my GETVAR ALL (using FASTBOOT):
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0001
(bootloader) version-baseband: 2.15.00.12.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 4.67.651.3
(bootloader) serialno: (hidden)
(bootloader) imei: (hidden)
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3809mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4b46e889
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 1

kennedystephen said:
Any help would be appreciated ...
I got this EVO 4G phone 2nd hand recently. The device keeps rebooting at the initial white "HTC Evo 4G" splash screen. And I cannot access RECOVERY.
I CAN access the BOOTLOADER screen that allows me to switch between HBOOT, HBOOT USB, and FASTBOOT modes.
I CAN access the device using FASTBOOT
I CAN reapply the original RUU exe. The RUU process finishes just fine, but it still doesn't fix the phone. The phone still continually reboots.
I CAN reapply the same RUU version using the PC36IMG.ZIP method. Same experience - process finishes just fine, but it still doesn't fix the phone.
I CAN switch the device's BOOTLOADER from "UNLOCKED" to "RELOCKED" (and back again) easily using HTC Unlocker method via FASTBOOT.
I CAN flash a custom recovery image, but it never seems to "take". Meaning afterward, it still wont boot the recovery after successfully flashing the recovery image/partition. Just simply reboots over again.CM
I CAN download and setup the CORRECT Windows Drivers. All that seems fine.
I cannot get access to the stock recovery, even after the RUU flash seemingly completes successfully.
I cannot access any custom recovery, even seemly after I flash one successfully (tried RA, CRM, and others).
I cannot access "Recovery" at all. Either by using VOLDWN+PWR, or from the BOOTLOADER selection choice. When I try, it just simply reboots continually still.
Obviously, I cannot access the Android OS - so I cannot "enable USB debugging"
I cannot get access ADB. It has always said "No Devices Found" - the Windows Drivers are installed.
I cannot get unReVoked or Revolutionary to work. They always "waiting for device" even if the phone is in connected via FASTBOOT.
I cannot switch to S-OFF, since I really only have access to BOOTLOADER and FASTBOOT.
I've reviewed a ton of threads over the past 5 days. Tried everything I can think of, and everything I found on the internet.
I would like to ROOT this device, or downgrade it's HBOOT, or go to S-OFF. But the problems listed above have limited me from doing those things, in one way or another.
It's hard to believe that I can access FASTBOOT, and UNLOCK/RELOCK the BOOTLOADER, and "seemingly" flash images - and still not fix this issue.
The phone is not under warrenty. Sprint wont take it back or fix it.
This is a VERY SIMILIAR ISSUE to the thread http://forum.xda-developers.com/showthread.php?t=187926
I'm looking for new ideas.
Is this the definition of "bricked"?
Is this considered the Bootloop of Death, and has no cure?
Is there a way to downgrade the HBOOT using just FASTBOOT? Seems like everything hates 2.18.00001.
Is there a way to flash a new KERNEL using just FASTBOOT? Would that help?
Any kind of help would be appreciated.
Here's my GETVAR ALL (using FASTBOOT):
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0001
(bootloader) version-baseband: 2.15.00.12.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 4.67.651.3
(bootloader) serialno: (hidden)
(bootloader) imei: (hidden)
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3809mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4b46e889
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 1
Click to expand...
Click to collapse
WOW that's a lot of info, trying to make this simple again, did you make sure the hboot radios match the RUU's?

Wows,right,but what you need to do is download a custom recovery.... http://forum.xda-developers.com/showthread.php?t=1661543 ,rename it to PC36IMG.zip and boot into fastboot/usb,connect your usb to the computer,make sure you have the HTC sync driver installed.... http://www.htc.com/www/help/ ,drop the custom recovery onto the root of your sd card and boot into bootloader,let it check for the zip,then follow instructions to install,when its finished,scroll to recovery and click it,now go here.... http://forum.xda-developers.com/showthread.php?t=1158993 and follow instructions,after your finished go here... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD and install this and find the rom you want o install,then you should be good to go.

Diablo67 said:
Wows,right,but what you need to do is download a custom recovery.... http://forum.xda-developers.com/showthread.php?t=1661543 ,rename it to PC36IMG.zip and boot into fastboot/usb,connect your usb to the computer,make sure you have the HTC sync driver installed.... http://www.htc.com/www/help/ ,drop the custom recovery onto the root of your sd card and boot into bootloader,let it check for the zip,then follow instructions to install,when its finished,scroll to recovery and click it,now go here.... http://forum.xda-developers.com/showthread.php?t=1158993 and follow instructions,after your finished go here... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD and install this and find the rom you want o install,then you should be good to go.
Click to expand...
Click to collapse
Thank you for helping me.
I downloaded a custom recovery from your first link (specifically PC36IMG_ra-supersonic-4.3-smelkus-aokp.zip). I immediately renamed it to PC36IMG.ZIP and put it on the root of the SD Card.
The bootloader (in RELOCKED mode) found it, did initially loadingof it, went to "Checking...[PC36IMG.ZIP]", and then went straight back to the BOOTLOADER screen. Nothing else happened. I tried to select "Recovery" and it simply rebooted, and then continually rebooted.
The bootloader (in UNLOCKED mode) found it, did initial loading it, went to "Parsing...[PC36IMG.ZIP]" and stays there. Never does anything else. Hangs.
I tried a second recovery image from your first link. Specifically PC36IMG_ra-supersonic-4.3-smelkus-cm9.zip. I extracted the .IMG file from the zip file. I made sure to have the HTC drivers installed from the HTC link you provided. I ran FASTBOOT FLASH RECOVERY recovery-ra-supersonic-4.3-smelkus-cm9.img. I got this message back:
sending 'recovery' (4134 KB).
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 1.685s]
finished. total time: 2.824s
I rebooted the device and tried to enter recovery (both via the BOOTLOADER recovery selection, and via VOLDWN+PWR). Neither took me into RECOVERY, and both immeidately rebooted the phone - into a boot loop. It really doesn't seem like it will boot into recovery.
Since this first part did not work, I was not able to continue with the rest of your instructions, because the links you provided assumed I could access RECOVERY.
Thanks again for trying to help me.

Mavman42 said:
WOW that's a lot of info, trying to make this simple again, did you make sure the hboot radios match the RUU's?
Click to expand...
Click to collapse
I used "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe" which (I think) matches my hboot radios.
Thank your for your help on this. I appreciate it.

kennedystephen said:
Thank you for helping me.
I downloaded a custom recovery from your first link (specifically PC36IMG_ra-supersonic-4.3-smelkus-aokp.zip). I immediately renamed it to PC36IMG.ZIP and put it on the root of the SD Card.
The bootloader (in RELOCKED mode) found it, did initially loadingof it, went to "Checking...[PC36IMG.ZIP]", and then went straight back to the BOOTLOADER screen. Nothing else happened. I tried to select "Recovery" and it simply rebooted, and then continually rebooted.
The bootloader (in UNLOCKED mode) found it, did initial loading it, went to "Parsing...[PC36IMG.ZIP]" and stays there. Never does anything else. Hangs.
I tried a second recovery image from your first link. Specifically PC36IMG_ra-supersonic-4.3-smelkus-cm9.zip. I extracted the .IMG file from the zip file. I made sure to have the HTC drivers installed from the HTC link you provided. I ran FASTBOOT FLASH RECOVERY recovery-ra-supersonic-4.3-smelkus-cm9.img. I got this message back:
sending 'recovery' (4134 KB).
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 1.685s]
finished. total time: 2.824s
I rebooted the device and tried to enter recovery (both via the BOOTLOADER recovery selection, and via VOLDWN+PWR). Neither took me into RECOVERY, and both immeidately rebooted the phone - into a boot loop. It really doesn't seem like it will boot into recovery.
Since this first part did not work, I was not able to continue with the rest of your instructions, because the links you provided assumed I could access RECOVERY.
Thanks again for trying to help me.
Click to expand...
Click to collapse
Did you make sure you uninstalled HTC Sync from your computer, and make sure that your PRI and PRL radios match too. Try using Captain_Throwback's guide here, It might not work, but give it a try. What other options do you have?
http://themikmik.com/showthread.php?11114-GUIDE-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark!-)&

Hmmmm.....
Where is Captain Throwback when you need him?
Sent using my HTC EVO 4G and a magic wand

Mavman42 said:
Did you make sure you uninstalled HTC Sync from your computer, and make sure that your PRI and PRL radios match too. Try using Captain_Throwback's guide here, It might not work, but give it a try. What other options do you have?
Thank you for trying to help me.
I tried two different computers. One with HTC Sync + Drivers installed. One with just the Drivers (no HTC Sync). Neither helped. Same results as described above.
How do I make sure my PRI and PRL radios match? I dont think this is something I've tried? Can I somehow use FASTBOOT to check this?
I cannot access the device (Android OS), nor flash a recovery. So Captain_Throwback's link won't help. It assumes I can successfully flash a new recovery, and then access it. If my device would take a new RECOVERY, I'd be set.
If the radios are the problem, is there a way to use FASTBOOT to flash a new radio version?
It's hard to believe that I can access FASTBOOT, and UNLOCK/RELOCK the BOOTLOADER, and "seemingly" flash images - and still not fix this issue.
Thanks again.
Click to expand...
Click to collapse

kennedystephen said:
Mavman42 said:
Did you make sure you uninstalled HTC Sync from your computer, and make sure that your PRI and PRL radios match too. Try using Captain_Throwback's guide here, It might not work, but give it a try. What other options do you have?
Thank you for trying to help me.
How do I make sure my PRI and PRL radios match? I dont think this is something I've tried? Can I somehow use FASTBOOT to check this?
If the radios are the problem, is there a way to use FASTBOOT to flash a new radio version?
It's hard to believe that I can access FASTBOOT, and UNLOCK/RELOCK the BOOTLOADER, and "seemingly" flash images - and still not fix this issue.
Thanks again.
Click to expand...
Click to collapse
Check the RUU file it should tell you which PRI and PRL radios you should have. Like say you have hboot 2.18, on the RUU file it should tell mainly on the file name itself. Or you can go here > http://forum.xda-developers.com/wiki/HTC_Evo/ROMs
If you're not sure which radios you have just download that match your hboot again and flash again in bootloader.
Click to expand...
Click to collapse

Mavman42 said:
kennedystephen said:
Check the RUU file it should tell you which PRI and PRL radios you should have. Like say you have hboot 2.18, on the RUU file it should tell mainly on the file name itself. Or you can go here >
If you're not sure which radios you have just download that match your hboot again and flash again in bootloader.
Click to expand...
Click to collapse
Thanks. I have version 4.67.651.3, Radio 2.1 5.00.12.19, and hboot 2.18. Previously, I used "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.1 5.00.12.19_NV_2.33_release_234563_signed.exe" which (I think) matches my hboot radios. I ran it, it completed "successfully", but never seemed to restore anything. I still could not access RECOVERY or ANDROID OS.
Click to expand...
Click to collapse

kennedystephen said:
Mavman42 said:
Thanks. I have version 4.67.651.3, Radio 2.1 5.00.12.19, and hboot 2.18. Previously, I used "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.1 5.00.12.19_NV_2.33_release_234563_signed.exe" which (I think) matches my hboot radios. I ran it, it completed "successfully", but never seemed to restore anything. I still could not access RECOVERY or ANDROID OS.
Click to expand...
Click to collapse
Man, that's all I got for now. Because a couple of months ago. I had almost the same prpblem, except I could access my recovery which made all the difference. I will still look in it for you. Tried taking it to a Sprint store? Lol.
Click to expand...
Click to collapse

Mavman42 said:
kennedystephen said:
Man, that's all I got for now. Because a couple of months ago. I had almost the same prpblem, except I could access my recovery which made all the difference. I will still look in it for you. Tried taking it to a Sprint store? Lol.
Click to expand...
Click to collapse
Well, thanks for the help anyway. I didn't think this was a lost cause - being that I could access BOOTLOADER, unlocked and relocked modes, and access the device using FASTBOOT. But for whatever reason, flashing the RECOVERY just wont take.
I wonder if it's because I have S-ON. I wish there was a way to obtain S-OFF with just being able to access FASTBOOT. Most the instuctions to obtain S-OFF have you going into RECOVERY or using ADB (which I can't do).
Would this CAPTAIN THROWBACK person even be able fix this?
Click to expand...
Click to collapse

kennedystephen said:
Mavman42 said:
Well, thanks for the help anyway. I didn't think this was a lost cause - being that I could access BOOTLOADER, unlocked and relocked modes, and access the device using FASTBOOT. But for whatever reason, flashing the RECOVERY just wont take.
I wonder if it's because I have S-ON. I wish there was a way to obtain S-OFF with just being able to access FASTBOOT. Most the instuctions to obtain S-OFF have you going into RECOVERY or using ADB (which I can't do).
Would this CAPTAIN THROWBACK person even be able fix this?
Click to expand...
Click to collapse
Wait a sec. In the recovery.zip, is there a Android_info.txt with the recovery? I remember trying to flash a recovery without that. And it pretty much did like what you said earlier, nothing. So make sure it has that, and flash it. Via main bootloader. And maybe the captain can fix it if he looks into it. Who knows. Make sure bootloader is unlocked.
Click to expand...
Click to collapse

kennedystephen said:
Mavman42 said:
Well, thanks for the help anyway. I didn't think this was a lost cause - being that I could access BOOTLOADER, unlocked and relocked modes, and access the device using FASTBOOT. But for whatever reason, flashing the RECOVERY just wont take.
I wonder if it's because I have S-ON. I wish there was a way to obtain S-OFF with just being able to access FASTBOOT. Most the instuctions to obtain S-OFF have you going into RECOVERY or using ADB (which I can't do).
Would this CAPTAIN THROWBACK person even be able fix this?
Click to expand...
Click to collapse
S-on or S-off won't matter as far as trying to install a different recovery. If you were trying to flash a radio update or kernel, it would, but as far as recovery goes, no. I'm baffled by what the issue is here, though.
Sent using my HTC EVO 4G and a magic wand
Click to expand...
Click to collapse

FinZ28 said:
kennedystephen said:
S-on or S-off won't matter as far as trying to install a different recovery. If you were trying to flash a radio update or kernel, it would, but as far as recovery goes, no. I'm baffled by what the issue is here, though.
Sent using my HTC EVO 4G and a magic wand
Click to expand...
Click to collapse
I wonder if the radio flash isn't taking because of S-ON. The RUU attempts to "Flash Radios...", and the RUU seems to complete successfully. But it never really fixes the problem. It continues to boot loop. But even when the phone is in RUU update mode, I can't flash the radios using FASTBOOT. So, I'm thinking, if I could get S-OFF, the RUU might rewrite the Radios correctly. I'm wondering if the firmware items (nv, radios, etc) aren't truely getting rewritten by the RUU since I have S-ON.
Click to expand...
Click to collapse

I think u need S-OFF before u can even flash a custom recovery.
Sent from my PC36100 using xda premium

pr0xyw0rm said:
I think u need S-OFF before u can even flash a custom recovery.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
If that's true, that would answer why the RECOVERY flashes aren't "taking" - even though the flashing process seems to complete 100%.
The only ways I've seen people gain S-OFF is by using REVOLUTIONARY or UNREVOKED, but those requires ADB access. And because I cannot access the Android OS, I cannot "enabled USB debugging" required to use ADB. Either way, I cannot access ADB. My phone simply does not show up as a ADB listed device. Which makes me think I cannot get S-OFF.
Thoughts?

pr0xyw0rm said:
I think u need S-OFF before u can even flash a custom recovery.
Click to expand...
Click to collapse
You do not need S-off to flash a custom recovery. If that were the case, there would be plenty of us running Hboot 2.18 (myself included) who would have never been able to load a custom recovery. S-off only has to do with flashing radios and kernels.
Sent using my EVO 4G and a magic wand

If you're s-on you need to fastboot flash the recovery isn't it?
An enviousOG

Robobob1221 said:
If you're s-on you need to fastboot flash the recovery isn't it?
An enviousOG
Click to expand...
Click to collapse
That's one way to do it. I did it through the bootloader the PC36IMG.zip way, though.
Sent using my EVO 4G and a magic wand

[Solved] Cannot install CM12 due to outdated bootloader

Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.

ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.

Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.

ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.

xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse

ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.

xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse

ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.

xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?

ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?

ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!

Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!

I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.

I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho

noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).

ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?

raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.

xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.

S-OFF,ROOT,SUPERCID and harman kardon mod

Hey
I have a pretty new htc one m8 i have ordered
I would like to have it rooted so i can install avast rooted version plus harman kardon mode.
I am running stock rom 5.0.1 (4.16.401.10)
I know that i need to have S-OFF for my htc m8 in order to have karman kardon mode. I have just wanted to download recovery stock so i can go back and have OTA updates when i need to
after running fastboot getvar all script its seems my cid is supercid (111111) how come? it's S-ON,Locked, without root & running stock
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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-ON
(bootloader) serialno: Moderator Removed
(bootloader) imei: Moderator Removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
thanks

efi2222 said:
I have a pretty new htc one m8 i have ordered
after running fastboot getvar all script its seems my cid is supercid (111111) how come? it's S-ON,Locked, without root & running stock
Click to expand...
Click to collapse
Was the phone purchased used or refurbished? If so, its possible someone unlocked the bootloader, SuperCID, and also S-off in order to make the bootloader LOCKED again, than s-on.
I don't think I've ever heard of an HTC device come from the factory with SuperCID. Although I suppose its in the realm of possibility; since SuperCID exists in the first place, HTC must use it at some point.

Yes, refurbished from aliexpress. As far as i know they come directly from HTC with the box and everything and they look like new.
So what do you suggest? There is anyway of backup the currect recovery ?

Moderator Information,
I have removed the Serial Number and IMEI numbers from your post. This is personal information and you should not post it online.
Many thanks,
Stephen

efi2222 said:
So what do you suggest? There is anyway of backup the currect recovery ?
Click to expand...
Click to collapse
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it with command:
fastboot boot recovery.img
(where "recovery.img" is the actual file name of the desire TWRP version).
Once booted into TWRP, you can then backup the stock recovery. After that, flash TWRP and root and apply whatever mods you like.
Alternately, you can get the .401 stock recovery from the following thread: http://forum.xda-developers.com/showthread.php?t=2701376

redpoint73 said:
Was the phone purchased used or refurbished? If so, its possible someone unlocked the bootloader, SuperCID, and also S-off in order to make the bootloader LOCKED again, than s-on.
I don't think I've ever heard of an HTC device come from the factory with SuperCID. Although I suppose its in the realm of possibility; since SuperCID exists in the first place, HTC must use it at some point.
Click to expand...
Click to collapse
redpoint73 said:
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it with command:
fastboot boot recovery.img
(where "recovery.img" is the actual file name of the desire TWRP version).
Once booted into TWRP, you can then backup the stock recovery. After that, flash TWRP and root and apply whatever mods you like.
Alternately, you can get the .401 stock recovery from the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I don't understand. first i know that i have to unlock the bootloader throught htcDev and everything gets deleted. after that why would i flast TWRP? that would flash my recoevery before i can backup it.
Can't i just unlock bootloader and root and then use this app ? https://play.google.com/store/apps/details?id=com.gocshare.flashrecoveryboot
thanks

I have one more question - htc one m7 had an issue when people unlock their bootloader some few system apps got deleted because they were stored on /data and not on /system. they have fixed it on the m8?

efi2222 said:
I don't understand. first i know that i have to unlock the bootloader throught htcDev and everything gets deleted. after that why would i flast TWRP? that would flash my recoevery before i can backup it.
Click to expand...
Click to collapse
Nope. Read more carefully what I typed:
redpoint73 said:
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it
Click to expand...
Click to collapse
So in this instance (boot TWRP before flashing it) you are actually running TWRP on the phone remotely, where the TWRP file is still on your computer, and the stock recovery is still on the phone.
efi2222 said:
Maybe i should root and then use this app ? https://play.google.com/store/apps/details?id=com.gocshare.flashrecoveryboot
Click to expand...
Click to collapse
I'm not that familiar with that particular app, but I'm aware of others that do similar (Flashify). You can use it if you like. But I personally don't recommend such flashing apps; since they just are doing the same things you can do "manually" with fastboot/adb. Plus, such apps just add a unnecessary layer of complexity or additional point of failure. I've seen instances where folks have had issues performing a task with an app or toolkit; only to have it fun perfectly when they do it with fastboot; so pretty clear to me that the problem was the app/toolkit.
Plus, fastboot and adb are good tools to know (if you don't already) as they can be very useful when your phone doesn't boot into OS (something an app can't do).
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
efi2222 said:
I have one more question - htc one m7 had an issue when people unlock their bootloader some few system apps got deleted because they were stored on /data and not on /system. they have fixed it on the m8?
Click to expand...
Click to collapse
This issue still exists. You can get the apk's for the apps in question on this forum, and install them after you root.

redpoint73 said:
Nope. Read more carefully what I typed:
So in this instance (boot TWRP before flashing it) you are actually running TWRP on the phone remotely, where the TWRP file is still on your computer, and the stock recovery is still on the phone.
I'm not that familiar with that particular app, but I'm aware of others that do similar (Flashify). You can use it if you like. But I personally don't recommend such flashing apps; since they just are doing the same things you can do "manually" with fastboot/adb. Plus, such apps just add a unnecessary layer of complexity or additional point of failure. I've seen instances where folks have had issues performing a task with an app or toolkit; only to have it fun perfectly when they do it with fastboot; so pretty clear to me that the problem was the app/toolkit.
Plus, fastboot and adb are good tools to know (if you don't already) as they can be very useful when your phone doesn't boot into OS (something an app can't do).
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
This issue still exists. You can get the apk's for the apps in question on this forum, and install them after you root.
Click to expand...
Click to collapse
Thank you for replying
1. How can i boot TWRP remotely?
2. oh ****,which apk's get lost in the process? if i will not have the same exact apk's i would not be able to make OTA updates
3. Firewater is no longer active? the only way of doing S-OFF is by paying 25$?

efi2222 said:
Thank you for replying
1. How can i boot TWRP remotely?
2. oh ****,which apk's get lost in the process? if i will not have the same exact apk's i would not be able to make OTA updates
3. Firewater is no longer active? the only way of doing S-OFF is by paying 25$?
Click to expand...
Click to collapse
1) I already described this in Posst #5 above.
2) Only the system partition is checked during OTA install. Since (as you mentioned) the "missing" apps aren't on the system partition, it won't prevent OTA.
3) Correct. Firewater was an online service. So it doesn't work even if you have the binary (if you were wondering). Sunshine is the only way.
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
efi2222 said:
Thank you for replying
Click to expand...
Click to collapse
There's a button for that.

I don't see that you have mentionted which apps gets lost.... can you please give me a link?
2. you are right!
3. wow that's a shame.... i don't know if the whole process for having the harman kardon mod worth 25$
4. there is a way only rooting without changing the recovery?
thanks

efi2222 said:
I don't see that you have mentionted which apps gets lost.... can you please give me a link?
Click to expand...
Click to collapse
I don't know off hand, and may differ from one carrier version to another, anyway.
There is a thread about it, so just search. I don't have a link off hand.
efi2222 said:
4. there is a way only rooting without changing the recovery?
Click to expand...
Click to collapse
I think you can actually boot TWRP as I've described(instead of flash TWRP) then use TWRP to root.
Never done this myself and not sure it works; but I'm pretty sure another member here said it can be done this way.
Also keep in mind, its easy to swap back and forth between stock and custom recovery. You could have already done so in the time you took to ask the question and wait for an answer.

redpoint73 said:
I don't know off hand, and may differ from one carrier version to another, anyway.
There is a thread about it, so just search. I don't have a link off hand.
I think you can actually boot TWRP as I've described(instead of flash TWRP) then use TWRP to root.
Never done this myself and not sure it works; but I'm pretty sure another member here said it can be done this way.
Also keep in mind, its easy to swap back and forth between stock and custom recovery. You could have already done so in the time you took to ask the question and wait for an answer.
Click to expand...
Click to collapse
I will search for it.
I know that's an easy thing and i have done that to my friend about 6 months ago. Unlocked his m8, flashed recovery and made root then flashed original back to get OTA.
The thing is that i don't have CID so i can't download anything from the thread... Last time i have checked his cid so i knew which stock recovery i should download but now i don't know because my cid is 111111
As for the apps i am download a system dump of the rom, i hope the apks will be there.
That's really a shame that the only way to S-off is by paying 25$

efi2222 said:
The thing is that i don't have CID so i can't download anything from the thread....
Click to expand...
Click to collapse
You want the 4.16.401.10 stock recovery that corresponds with your main version.
Your MID of 0P6B10000, which corresponds to Europe, also would indicate that the .401 recovery is what you want.

Mr. Hofs Helped me before with this boot recovery so here's what I did
1. unlock bootloader
2. fastboot boot recovery.img
2.a flash supersu on recovery (now Im rooted with stock recovery intact)
3. Install flashify to back up my stock recovery (keep it very important)
4. now flash the TWRP by fastboot flash recovery recovery.img
5. go to your TWRP back up your stock rom (keep it again)
6. flash custom rom
7. enjoy

htc one m8 twrp won't boot

Hello,
i have a problem with my htc one m8 any help will be appreciate.
i wan't to install the new rom viperone m8 but when i try to flash twrp latest version the recovery don't load it's reboot the bootloader only and don't get access to twrp to install rom
i'm able to flash philz_touch_6.26.6-m8.img and install skydragon latest rom
i'm also able to flash twrp-2.7.0.2-m8.img
here is my getvar all
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: <----------- i have doubt on this why it's empty
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__247
(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: eb00c9d0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
there is any solution for my problem?
can i install viperone 4.6.0 with wrp-2.7.0.2-m8.img
bootloader is unlocked and phone is s-off
Thank you in advance for your help.

First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery

Hello,
thank you very much for your help.
i was on 4.21.1020.1
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
it's boot to bootloader it don't show twrp recovery.
very strange
thank you for your assistance
ckpv5 said:
First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery
Click to expand...
Click to collapse

Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.

i had to S-Off because in skydragon installation guides requirements
s-off is more easy
there is any solution to back and redo everything.
Thank you
ckpv5 said:
Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.
Click to expand...
Click to collapse

Hello
Anyone got this type of problems?
There is any solution ?
Thank you

novalayer said:
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?

redpoint73 said:
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?
Click to expand...
Click to collapse
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424

whiperhack said:
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424
Click to expand...
Click to collapse
Good info. Makes sense since he was able to flash TWRP 2.7.something.
But it would be useful for folks when they seek help to actually give the exact fastboot commands used, and not just cut and paste from somebody else's post (so we can't even be sure if he is using the right commands to install TWRP).

For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000

Petert87 said:
For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000
Click to expand...
Click to collapse
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).

redpoint73 said:
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).
Click to expand...
Click to collapse
I'm at work so atm cant provide a getvar all. What I did:
write cid 11111111, flashed 1.54.401.5-W_Splash.zip, reboot stock recovery, factory reset, installed TWRP. Again factory reset in TWRP. Then installed MaximusHD. Then I installed the first Nandroid I had from my software x.xx.161.x. Then did all OTA's. I think my hboot never updated during OTA.s

Petert87 said:
Then did all OTA's. I think my hboot never updated during OTA.s
Click to expand...
Click to collapse
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.

redpoint73 said:
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.
Click to expand...
Click to collapse
I thought that OTA updates the firmware automatically

Petert87 said:
I thought that OTA updates the firmware automatically
Click to expand...
Click to collapse
Yes, it does.
But why do you think it failed to do so?

redpoint73 said:
Yes, it does.
But why do you think it failed to do so?
Click to expand...
Click to collapse
Because I'm on old hboot and latest lollipop.

Petert87 said:
Because I'm on old hboot and latest lollipop.
Click to expand...
Click to collapse
You stated your were on hboot 3.19; which is the latest hboot there is.

redpoint73 said:
You stated your were on hboot 3.19; which is the latest hboot there is.
Click to expand...
Click to collapse
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3

Petert87 said:
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3
Click to expand...
Click to collapse
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.

redpoint73 said:
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.
Click to expand...
Click to collapse
I tried every version until one works and stopped at that one.

HTC ONE M8 stuck in bootloop

Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!

M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.

redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!

OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(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: 0P6B10000
(bootloader) cidnum: HTC__102
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping

M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!

redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!

M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.

redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?

M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.

redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!