HTC M8 stuck on HTC One logo boot - One (M8) Q&A, Help & Troubleshooting

Hi, I'll keep this short and simple. The phone is locked, with S-ON and everything is stock, it's running Lollipop 5.0 with stock sense. I've had my M8 since Oct 2014, served me well until Dec 2017 when I switched to the HTC 10. At any rate, I've migrated the majority of my content to the new phone except for a few like telegram secret chat etc. Since I made the switch, I usually keep the M8 switched off and I used it like 4-5 times only since December. My last usage was around early March.
Anyway, come last week. I turned it on and it got stuck on the HTC logo (first time ever). So I booted into recovery which is when I noticed that the software status is now modified vs Official despite never tampering with it. I cleared the cache and attempted a reboot and it got stuck on the "HTC One" logo but that' about it. The only way out of this state is power button + vol up which reboots it again and on and on this goes. It just refuses to go past that stage. Occassionally "android is optimising apps" appears for like 2 sec before the htc One logo shows up again and remains there indefinitely.
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

So just an update, it seems that right now, my device goes straight into fastboot regardless if I choose power down (powering it on again boots it back into fastboot) or restart it (again goes into fastboot).

hemingway60 said:
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
Click to expand...
Click to collapse
Probably unlikely to get the phone working and keep your data.
It appears your OS has become corrupted or damaged in some way (it happens). This would explain why it goes straight to bootloader instead of booting to OS. It may also explain why it says software "modified" when you haven't done any mods. Although I haven't seen that happen specifically (showing "modified" due to OS damage on an otherwise stock device); but it does seem logical it would say this (it is possibly reading the damage as some unknown "modification").
Your best bet is to restore factory image using RUU, following the instructions on the following post: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe all data on the phone. But in the current condition (as mentioned), I don't think you have much choice anyway.
The RUU should restore the OS, in addition to updating it to Marshmallow (the last version HTC released for this device).

Hey, appreciate the reply. That's disappointing, considering the phone was literally just sitting inside a desk. Anyway, I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Thanks.

hemingway60 said:
I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Click to expand...
Click to collapse
Both are build number 6.12.401.4.
So I doubt there is any actual difference. If there was any change, it would have a different build number (6.12.401.5 or whatever).

Related

[Q] Factory Unlock HTC One M8 Softbrick HELP!

HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you flashed a custom recovery on the device? If yes, just try to restore a nandroid back from @Mr Hofs thread and your phone will be fine
Problem is, I don't think there is any nandroid backups available for his device LRA__001. First time I've seen that CID mentioned. Going by MID doesn't help much either, I think the Verizon has the same MID. Going by the "product: m8_wlv" it also indicates Verizon. I do see that he's on AT&T on his profile though but...
Being stuck on bootloader screen for 10minutes or more won't be surprising at all if he flashed a 2.xx.xxx.x firmware based custom ROM instead of a 1.xx.xxx.x version. Need to upgrade firmware in order to do that.
You don't happen to recall what version software your device ran?
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
fgarcia10 said:
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
Click to expand...
Click to collapse
Honestly if its that much of a hassle, you should stick with something safe, Change the MID and CID to a Dev Edition/Europe, to do a full convert and you wont have to worry about the LRA_001. If you do those 2 steps the the OTA will be automatic as follows.
Else just flash a custom recovery, wipe data/cache and so and restore with one of the TWRP backups posted around here and you'll be good to go :good:
Cool I will try that. I did not know that.
fgarcia10 said:
Cool I will try that. I did not know that.
Click to expand...
Click to collapse
Don't forget though, best steps as follow, change MID, CID, restore via TWRP backup. If youre in Europe then change the MID to EUR, but the CID change it to super CID. Youve gotten past the hardest part which is the SOFF so everything is a breeze from there on out.
You won't lose your internal data if you do any of the following steps but dumping them on your SD card would be safe too.
I had an SG manufactured one, and the OTA came out pretty weird, was an unbranded one too. changed it to Dev/Unlocked MID and the super CID, downloaded the B_US002 TWRP dump thats posted here and restored that. Might want to download the OTA too aswell would save massive time after the first 159MB ota.
Awesome. Thanks!
was any one here ever able to get things working?
i am on LRA__001 and got my radio to stop working, no phone signals
contacted HTC dev and they provided me a zip, flashing that didn't help much, still no signals and can't boot into stock recovery.
seems like i've flashed the wrong hboot or something that's causing everything to be flashed on wrong partition addresses.
any help ?
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
hey
were you able to get it working ?
do you still have that phone?
i need some help
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
redpoint73 said:
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
Click to expand...
Click to collapse
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
genious_t said:
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
Click to expand...
Click to collapse
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
redpoint73 said:
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
Click to expand...
Click to collapse
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
read bout the boot process and got to know that hboot reads IMEI and baseband while booting up and holds into some shared memory variables which later read by kernel.
just trying to figure out things and also looking for somebody who can provide dumps so i can try flashing them.
genious_t said:
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
Click to expand...
Click to collapse
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
redpoint73 said:
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
Click to expand...
Click to collapse
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
I did get it to work again, HTC help me to get it back to stock. I still have the phone. They send me the files to restore it.
genious_t said:
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
Click to expand...
Click to collapse
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
fgarcia10 said:
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
Click to expand...
Click to collapse
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
genious_t said:
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0Bw_sCYzL1RITbGkzRExWTmU1d1U/view?usp=sharing
https://drive.google.com/file/d/0Bw_sCYzL1RITN0ttSVBZZ3VUYkk/view?usp=sharing

Out of options, phone fails to work.

Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
boomboxie said:
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
Click to expand...
Click to collapse
UPDATE: Seems like it`s mostly happening when installing new apps, or recovering them. Tried to remove sdcard , did`t help.
boomboxie said:
H
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
Click to expand...
Click to collapse
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
redpoint73 said:
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
Click to expand...
Click to collapse
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Will try to convert to stock GPE with RUU and update on results.
boomboxie said:
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Click to expand...
Click to collapse
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
boomboxie said:
Will try to convert to stock GPE with RUU and update on results.
Click to expand...
Click to collapse
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
redpoint73 said:
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
Click to expand...
Click to collapse
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
Click to expand...
Click to collapse
Be careful with your terminology there, to avoid confusion. From your previous post, you stated you just flashed a GPE ROM.
This isn't the same as "converting" to GPE with RUU, which puts you on GPE firmware, GPE partitioning, etc.
boomboxie said:
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
I don't know what that means, if you don't give details on what you did, and the specific results. But I'm assuming you know how to use command prompt to issue adb/fastboot commands, entered the command, and get no response (or device offline)?
If so, check that you are in bootloader-fastboot mode, have HTC drivers installed, or try different cable or USB port.
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
bombo_b said:
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
Click to expand...
Click to collapse
I tend to agree that its a hardware problem. But its always a good idea to return to full stock by RUU, to eliminate the possibility its a software issue, before concluding its a hardware problem.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
1) at first go to bootloader
2) connect device via usb cable into pc
3) confirm you are in fastboot mode
4) install drivers through htc sync manager
5) download the following zip
6) at first create a new folder in desktop. then copy zip into that folder & extract.
7) while press ''shift'' right clik on the new folder & select ''open command window here''
8) on the command prompt type fastboot getvar all
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Disregard this post.Sorry
boomboxie said:
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
umesh.lk said:
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
Click to expand...
Click to collapse
What would be the best way to do that ?
boomboxie said:
What would be the best way to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
boomboxie said:
I have newest TWRP installed.
Yes firmware is up to date.
Click to expand...
Click to collapse
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
redpoint73 said:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
Click to expand...
Click to collapse
Thanks, will update on outcome.
EDIT: I thought i was "up to date" i guess i wasn`t lol, my bad.
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failure.
(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.401.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: HTC__203
(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
all: Done!
finished. total time: 0.049s
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
boomboxie said:
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failur
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
Click to expand...
Click to collapse
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
umesh.lk said:
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
Click to expand...
Click to collapse
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
boomboxie said:
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
Click to expand...
Click to collapse
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
umesh.lk said:
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
Click to expand...
Click to collapse
By that you mean: Connecting phone to PC and flashing Newer recovery or OS ?

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs
ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

Stuck in bootloop with no access to recovery after official update

Hi Peeps,
I have read alot of threads which seem to be close to my issue but they seem to be able to get in to recovery via HBOOT, or the same issues have been posted but no answers or follow ups, if they have fixed the issues. Most annoying thing that, fixing the issue but not posting how. There does seem to be a lot asking the same question but no answer. I had asked in other threads, i have removed them and wrote this more complete thread. So any help would be appreciated, not only me but anyone else with this issue::angel::fingers-crossed:
Ok, The phone is a friends who got this phone with it already in a bootloop. According to the seller, When they did the official update (not sure if from KK-LP or LP-MM, but the) seller said it was on 5.0.2 Lollipop.
As usual from HTC, they have 10s of different OS versions of the same device, not helped by the fact they have dual and single sim models, plus, Snapdragon and MediaTec models.
This is the dual Sim 820N Snapdragon 615 model.
I don't know if its been rooted or has USB Debugging on. I have relocked the bootloader via fastboot. I can get CID and getvar all from fastboot but when I try and flash recovery I get signature verify fail. Also, I have downloaded All In One Flash Tool but it wont connect to the device.
Here is the NBOOT Screen info
*** Software Status: Official***
*** Relocked ***
A51_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-0.1.01.010-U10305041_08.01.50512
OS-2.10.401.4
eMC-boot 2048MB OC
Nov 13 2015,16:02:23
This is the report from Fastboot getvar all command
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U10305041_08.01.50512
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CC53LYC03732
(bootloader) imei: 357586061067150
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ40000
(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: da038a09
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 1001
all: Done!
Any help would be great, I have been trying this issue everyday for over a week. I'm not a total NOOB but, I am a beginner still
Thanks in advance - Also ***I WILL POST BACK WITH THE FIX, IF AND WHEN I FIX IT***
Or can anybody tell me where I can download the RUU and the flash tool if that would work. I have looked at loads of sites trying to find the right RUU then see if I can somehow update it with that. I am trying everything I can, Someone must know something, anything. Its not like its a crap phone with hardly any development. Its a good mid-range device with loads of support - I just can't find the right answer to my issue. I don't want to give up, The answer is out there. Even have looked under other devices, Thats how I've come across the RUU option
Ok, as promised... I spent hours upon hours trying to find the RUU download so here it is https://www.androidfilehost.com/?fid=24369303960690247
This is for the Desire 820N dual sim Europe A51_UL
I've not tried it yet, in the process of doing it.
Download then change the name to 0PFJIMG.zip, put on SD Card, VOL down + Power Button to load bootloader - it should automatically read the update and load in.
I'll post back if it was successful
Update;
I have tried to rename and copy to SD card, in fastboot, it reads the SD card but not the 0PFJIMG.zip.
So I started to look around why that could be then seen a few vids on YouTube showing how to RUU.
Best way was to extract the RUU file, Run the RUU.exe from the unpacked files and it should do everything for you.
So I tried to use winrar to unpack but got;
WinRAR: Diagnostic Message
C:\Users\Desktop\820nRUU\full\0PFJIMG_A51_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.10.401.2_R_Radio_01.01.010_U10305041_08.01.50512_release_454261_combined_signed.zip: The archive is corrupt
C:\Users\Currys\Desktop\820nRUU\full\0PFJIMG_A51_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.10.401.2_R_Radio_01.01.010_U10305041_08.01.50512_release_454261_combined_signed.zip: Checksum error in C:\Users\Currys\Desktop\820nRUU\full\userdata_16g.img. The file is corrupt
C:\Users\Currys\Desktop\820nRUU\full\0PFJIMG_A51_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.10.401.2_R_Radio_01.01.010_U10305041_08.01.50512_release_454261_combined_signed.zip: The archive is corrupt
I did however download another source which was password protected, Having found the password, I extracted that file too which gave me the same error's.
I downloaded WinZip and got an error through that too.
Is it too much of an ask, if anybody could shed a light on whats going on there?
As I said, I'll post everything I find and what I did to fix the issues. No doubt I'll have to figure it out myself...again :0)
Another quick update, I downloaded any random RUU from HTC-DEVs, Unzipped that and got the same errors???
Thats too much of a coincidence 3 different files, 3 different sources but the same 3 errors. Could it be google chrome download?, Should I try diferent Laptop? Different profiles? Might As well talk to the wall:cyclops:
I have the same issue, and i cant access recovery mode or get to start it
I have the same issue. i cannot access the recovery mode. keeps on rebooting. any fix yet?
I have Custom Rom Installed (Desire 820u) Which Was working Fine.Now Its Stuck @bootl
Is there Any Fix To Solve This Problem??I have Been Trying To enter Bootloader Mode....But Its Not Entering!As soon I plug In to Charge My Phone....A Red Light Starts Blinking! I'm Not Able To Enter Bootloader or TRY to Start My Phone!!Can anyone Help To fix This Problem plz...I have Ported A New Custom rom (LineageOS) for My Htc 820u!I wanna flash It....But Unfortunately I'm Not Able to enter Bootloader Mode...Or Atleast Start up My Phone....

Bootloop problem; can't restore to TWRP backup with root.

A somewhat similar problem to this one: https://forum.xda-developers.com/ht...soft-brick-t3504692/post69758285#post69758285
I have a HTC one M8 (obviously).
It successfully has TWRP installed, and until today it had both SuperSU (2.78) and x-posed installed and working.
Earlier today, I was struggling with suspected power failure in the device (it said it had 20-30% power left but it shut off as if completely out of power).
As a result of this, once I started charging it, it could boot fine but had forgotten all my personalization options (what start screen icons, alarms, ringtone etc. and even android device-ID changed, according to titanium backup) though the installed apps were untouched.
So, after I reset the device ID back to the original with titanium backup, I shut it off, made a backup in TWRP, and tried to reload the previous backup with the correct personalization settings.
however, it seems unable to boot into any of the backups I have, not even the one I just made, except for the completely untouched backup that I original made before beginning on rooting.
every other one I try to boot into, it gets stuck on the "HTC powered by Android" splash screen, including the backup of a state that worked mere hours ago.
If anyone has an idea what could be going on I would appreciate the help.
What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
getvar all resulted in:
Code:
(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:
(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: VODAPE17
(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
Since this, I've been working on it some more. I think something went wrong with the system or boot partitions, since restoring to factory default and then getting the latest backup of the data on did work. Since then I've been working on re-rooting the phone with majisk.
Though it isn't urgent anymore now that the phone is no longer effectively soft bricked, the fact that TWRP backups didn't work is very disturbing to me, so help getting that working is still appreciated. Hopefully it's just something simple/stupid, like an out of date TWRP.
wild_dog said:
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
Click to expand...
Click to collapse
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/
redpoint73 said:
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/
Click to expand...
Click to collapse
0_0 welp, lucky me then that it still was able to go back to the old stock backup... just flashed a new TWRP and am now running a new backup. looks like it also backups more, or at least has a finer controlled partitioning in what it does backup. i'll play around with that a bit, caus I now see that a data backup does not include storage, which is something I would want.

Categories

Resources