[Q] Bootloop of Death? Is it Bricked? - EVO 4G Q&A, Help & Troubleshooting

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

Related

Confirm this?? If S-off, I can flash recovery with bootloader locked?

It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
syntropic said:
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
Click to expand...
Click to collapse
SO I said f*ck it... no big deal, and I unlocked the bootloader and flashed the stock recovery (btw, I flashed a stock recovery I found in the TMO forums that had a version number identical to the software version I had installed, this is correct right????). I had no problems flashing the stock recovery....so apparently, you need to unlock the bootloader whenever you are flashing recoveries irrespective of whether you have S-off.
But then, I tried to run the OTA, and got the red triangle error.... — Is this because my bootloader is now unlocked?
This seems to be going against everything I have read numerous times (namely that if you are S-off, the bootloader is not that big of an issue). I am assuming this is because my bootloader is now unlocked... so I will unlock it.
IGNORE
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ★★★★★★★★★★★★★
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
syntropic said:
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: DO NOT POST IMEI NUMBER
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
Click to expand...
Click to collapse
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
BerndM14 said:
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
Click to expand...
Click to collapse
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But as of now, I have re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number of the recovery matched exactly the version number of the software that is showing on my hboot screen. I thought that was a educated guess that wouldn't be too risky.
I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused....because aside from the recovery, I didn't touch any of the firmware.
NB: I do have a nandroid that I made that is entitled: 2014-09-24-14-06{whatever) release keys I don't know what release keys means.... I have made a lot of nandroids in my time... 95% of them on HTC devices using TWRP (at least since its inception), and I have never seen a "release keys" appended to the name of an nandroid like that.
I could restore this nandroid... but then I would have to unlock the BL, fastboot flash TWRP, flash SuperSU (although I know TWRP now prompts you which is very cool), then restore the nandroid, fastboot flash the stock recovery, then (apparently) re-lock the bootloader, and get the OTAs.... if the OTAs even work...
syntropic said:
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But I have no re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number matched exactly the version number of the software as shown in the hboot screen. So I assumed it was the right one. I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused.
Click to expand...
Click to collapse
Ok stock recovery flashed back is good then, you need to be completely stock to do OTA's i.e If you made changes to the system even removed pre-installed apps like Facebook, Twitter etc you need to restore those back as well. As the OTA will do a verification check to see that all those things are intact before it continues the update. If it's not stock then you're not getting OTA. Bootloader status won't make a difference, you can keep it unlocked.
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
BerndM14 said:
{...}
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
Click to expand...
Click to collapse
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
syntropic said:
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
Click to expand...
Click to collapse
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
BerndM14 said:
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
Click to expand...
Click to collapse
They also have the 2.22.531.6 stuff there so just make sure you select the correct versions, it's under the "clickable" buttons so...
OK.... I used a app called Nandroid Manager (very helpful app) which extracts anything you want from a nandroid. Since I had already disabled the Android Tweaker 2 App, and realized I had an original build.prop in that nandroid, I just extracted that and renamed the old one, and used the extracted one. I did a chmod 644, and then attempted OTA install.. And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
EDIT: Actually.... I would really like to avoid the htc unlock token as that erases the data partition as some kind of existential pennace ordained by HTC for unlocking your bootloader.
syntropic said:
[...] And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Click to expand...
Click to collapse
Glad it worked out :good:
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
Click to expand...
Click to collapse
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
Click to expand...
Click to collapse
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
Click to expand...
Click to collapse
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
syntropic said:
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
Click to expand...
Click to collapse
how did you get S-OFF? Firewater?
BerndM14 said:
how did you get S-OFF? Firewater?
Click to expand...
Click to collapse
He said SunShine on OP.
OP - try towelroot to gain root then use scotty's guide to unlock bootloader
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
Really ?
Read his problem again... His device has no root so can't do what you suggested
ckpv5 said:
Really ?
Read his problem again... His device has no root so can't do what you suggested
Click to expand...
Click to collapse
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
syntropic said:
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
Click to expand...
Click to collapse
Yeah, I had a bit of a brain fart on that one. I forgot you have to be able to su to execute that dd command, even s-off. However, I do know for a fact that you don't actually have to flash TWRP to re-root. When I did the same thing you are doing, I simply booted TWRP instead of installing it to preserve the stock recovery.
TWRP did have an issue booting for a while when using the firmware that came along with 4.4.3, but they appear to have fixed it in the last two versions. I ended up using CWM instead, but the effect is the same.
jshamlet said:
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
Click to expand...
Click to collapse
That is another good potential solution...and I know it works.... I will try and let you know!

[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.

M8 won't boot

Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(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__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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).

HTC One M8 stuck in fastboot screen since loading CWM Recovery Image

Hi, I attempted to root my phone for the first time following these instructions, which have the HTCDev.com unlocking bootloader instructions as part of them.
Output of "fastboot getvar all" is below
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0​
I did make a mistake, I loaded both the below images in the given order.
openrecovery-twrp-2.7.0.2-m8.img
philz_touch_6.26.6-m8.img
When I went into recovery I got philz touch and loaded the UPDATE-SuperSU-v2.37.zip that was instructed. However I am got stuck in permanent reboot.
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Is this removing the philz touch image? How is this done?
Or more what I'm after, how do I get to a rooted phone from here which is usable?
Thank you in advance for any help given!
The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.
maultasche said:
The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.
Click to expand...
Click to collapse
Many thanks!
Can I just clarify what flashing the latest TWRP and the latest SuperSU means? I'm running on windows, which fastboot instruction(s) in cmd do I need to run? (Sorry, I am very new to this.)
MonkeyBrains7532 said:
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Click to expand...
Click to collapse
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone. Flashing zips which are not for your device model could brick the phone.
The latest TWRP can be found here:
https://dl.twrp.me/m8/
Latest SuperSu:
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
maultasche said:
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone
Click to expand...
Click to collapse
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.
MonkeyBrains7532 said:
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.
Click to expand...
Click to collapse
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.
maultasche said:
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.
Click to expand...
Click to collapse
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...
MonkeyBrains7532 said:
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...
Click to expand...
Click to collapse
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware.
But before you go and restore a backup try to flash firmware as mentioned in post #5. You need to relock bootloader though.
maultasche said:
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware
Click to expand...
Click to collapse
It was originally just on the White with green "HTC" text boot screen. I'm now in fastboot.
So I have downloaded the following.
SuperSU-v2.82-201705271822.zip
twrp-3.1.1-0-m8.img
I also downloaded the below (on the mega-nz.com link).
hboot 3.19.0000 - 6.xx.xxx.x (Marshmallow)
CID ORANG001
MID 0P6B10000
6.12.61.4​
as well as the below from post #5
CID ORANG001
MID 0P6B10000
fw_6.12.61.4​
I attempted to flash the TWRP, but got "'flashboot' is not recognized as an internal or external command". I am still in the directory where I downloaded flashboot and this is a new error..
I then started on the instructions in post #5, all the way up to "fastboot flash zip fw_6.12.61.4.zip" but I get the same "...not recognized..." error. My phone is now on a screen similar to fastboot, but there is just the one option, "RUU". It was on a black screen with "HTC" in the middle a moment ago when I was trying to flash the zip.
@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command
maultasche said:
@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command
Click to expand...
Click to collapse
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.
MonkeyBrains7532 said:
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.
Click to expand...
Click to collapse
Don't worry. I've been through the same once
maultasche said:
Don't worry. I've been through the same once
Click to expand...
Click to collapse
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?
MonkeyBrains7532 said:
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?
Click to expand...
Click to collapse
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?
maultasche said:
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?
Click to expand...
Click to collapse
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...
MonkeyBrains7532 said:
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...
Click to expand...
Click to collapse
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?
maultasche said:
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?
Click to expand...
Click to collapse
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".
MonkeyBrains7532 said:
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".
Click to expand...
Click to collapse
Do you have philztouch still on your phone?
maultasche said:
Do you have philztouch still on your phone?
Click to expand...
Click to collapse
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.
MonkeyBrains7532 said:
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.
Click to expand...
Click to collapse
Yes, boot into Philz and try to find out if the recovery can flash .img files
Never used it so I don't know :/

HTC one m8 recovery mode and factory reset black screen red triangle

Hello ..
i have htc one m8 and for some reason it's on deep freeze like on a same system restore point everytime i reboot i find the same
apps installed , pics and missed calls no matter how many times i erase all that and if i installed new apps every reboot it's
not there , and everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up +
power to reboot) ,tried to unlock bootloader using htc dev did all steps and when finally get to unlock bootloader screen on my
phone , i clicked yes and phone rebooted to black screen with red triangle and when i rebooted it's like nothing has been done
and still locked, i tried using official twrp from play store i managed for 1 time to open recovery mode and i wiped all data ,
erased the cache and when i rebooted it's the same issue .. tried to flash recovery using cmd still doesn't work (failed : remote
not allowed) , and also HTC sync manager doesn't recognize the phone , dk what to do , wasted alotta time trying to solve this
but no vain , plz help
*FastBoot*
*** Locked ***
M8_WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.18.0.0000
RADIO-1.08.20.0612_4
OpenDSP-v38.2.2-00542-M874.0311
OS-3.30.651.2
eMMC-boot 2048
Jul 7 2014,20:03:18.3
*getvar all*
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.08.20.0612_4
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: **************
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d4c3cae5
hbootpreupdate: 11
gencheckpt: 0
Try to flash stock ruu, if isn't working it's probably a dead nand.
Devil_55 said:
Hello ..
everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up + power to reboot)
Click to expand...
Click to collapse
Black screen with red triangle is the stock recovery. So that is expected. Hold vol up, and press and release power button, to show the stock recovery menu options.
Devil_55 said:
tried to flash recovery using cmd still doesn't work (failed : remote not allowed)
Click to expand...
Click to collapse
That message is expected when trying to flash custom recovery with a locked bootloader. TWRP is only going to flash if the bootloader is unlocked.
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173
You can try any of the RUUs there. But note that if you try the Marshmallow RUU, you will have to flash corresponding Marshmallow firmware.zip before the RUU will install properly (this is clearly indicated in red caps text on the linked thread).
I also agree with the previous response. The behavior is really suspicious (changes don't "stick", bootloader does not unlocked) and NAND failure is a real possibility, especially if the problems persist after RUU.
lucyr03 said:
Try to flash stock ruu, if isn't working it's probably a dead nand.
Click to expand...
Click to collapse
Thanks for your Help
redpoint73 said:
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571.
Click to expand...
Click to collapse
I tried this method but still locked
redpoint73 said:
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173.
Click to expand...
Click to collapse
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000) , i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible) (i'm just guessing i dk if we could use this information)
and Huge thanks to you
Devil_55 said:
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000)
Click to expand...
Click to collapse
Both HK and non-HK versions have the same model number 0P6B70000. The only different is in software/firmware.
Your OS number in getvar (3.30.651.2) leads me to believe it was originally non-HK (the "651" signifies this). But it's possible that the previous seller changed it from HK to non-HK (although I'd say that is unlikely).
Really since you are SuperCID, either RUUs will work (HK or non-HK). You can try 3.30.651.2, or the one you downloaded 4.25.651.14 is fine as well.
Devil_55 said:
i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
Click to expand...
Click to collapse
The .exe format RUU is probably the simplest method. PC is required.
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?
Devil_55 said:
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible)
Click to expand...
Click to collapse
No, that isn't possible. The Sprint version M8 is different from all other versions. Trying to flash Sprint version firmware/RUU to any other M8 version results in a radio brick (no SIM, no cell service).
We see on this forum a lot of folks with the Sprint version M8 which have been made s-off and SuperCID (by seller/vendor) to unlock them for use in other countries, and to appear "unbranded" (when they are in fact, far from it).
your Help is much appriciated
redpoint73 said:
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?).
Click to expand...
Click to collapse
It did nothing bcuz phone was on bootloader menu but when i tried RUU while phone was booted , wizard moved on to the next step ,
wizard tried to flash RUU but it's stuck on waiting for bootloader , and instead of the phone boot into bootloader it just reboot into the same restore point as if nothing happened.
-https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B%21340&parId=root&o=OneUp
- it kinda does that in every process before last step (rebooot) , I tried
1-Flash Firmware via Hboot (requires micro sd card)....
-rename firmware to 0P6BIMG.zip
-copy 0P6BIMG.zip to ext_sd card
-boot into bootloader
-make sure hboot is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
*reboot after pressing up
2- Flash Firmware via fastboot, no ext sd card needed....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
* Reboot regularly after fastboot oem rebootRUU
3- ARUwizard to flash 3.30.651.2 stuck at same point (waiting for bootloader) then phone reboot regularly
Is there any other way to flash

Categories

Resources