HTC One M8 stuck on black screen after rebooting - One (M8) Q&A, Help & Troubleshooting

Hello,
In the past I had rooted my Rogers HTC One M8, but have since unrooted it and relocked the bootloader. I had accidentally installed the wrong version for something when bringing it back to stock, which caused no issues until I tried to install the OTA for Marshmallow (had "htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-keys", but found out I needed "htc/rogers_wwe/htc_m8:5.0.1/LRX22c/463267.3:user/release-keys" or "htc/rogers_wwe/htc_m8:6.0/MRA58K/667457.7:user/release-keys"). I kept the notification up for a while, then decided to try to upgrade to the newer android version. I rooted my phone again to grab the OTA file from my device, then flashed the recovery and boot image files from this OTA file, then did "fastboot oem lock" to re-lock the device, up until which everything worked fine. After the device re-locked, whenever I turned it on, it would go to the white HTC screen like normal, then go to a black screen (but the backlight would be on, so it was obviously not off). I can press power + vol-up to get the phone to briefly turn the backlight off before repeating this process of white HTC screen and black screen with backlight on. Sometimes, it will turn off, if the timing is right, instead of repeating this process. When turned off, if I plug it in , the charging battery animation shows up like normal and the phone charges normally. I can also get to the bootloader by pressing vol-down right after the backlight turns off but before the white HTC screen shows up. I can get to the recovery from the bootloader, and do everything else you would normally be able to do from the bootloader. I just can't get the phone to fully boot up. I've wiped the cache and dalvik cache, and wiped my phone.
Fastboot commands work fine, but adb commands don't. Here is the result of "fasboot getvar all" if that would help diagnose my issue:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: Nonez
(bootloader) version-main: 4.20.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: 4a2bcc8a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
Thank you for any help! If you need any more information, just ask!

Have you tried using an RUU?
I think that you should try to use an RUU to fix your phone. When my M8 acted up, I downloaded the RUU from HTC's website for my model, ran it, and had it do it's thing. It will nuke everything on your phone, but it is a good option if it will work.

yumi1996 said:
I think that you should try to use an RUU to fix your phone. When my M8 acted up, I downloaded the RUU from HTC's website for my model, ran it, and had it do it's thing. It will nuke everything on your phone, but it is a good option if it will work.
Click to expand...
Click to collapse
There is no Rogers RUU available.

Related

Boot Loop crash, RUUs and Recovery not working

Hello,
This morning I woke up to my Verizon HTC one rebooting constantly. The night before I had done nothing unusual, just some games and youtube. I have not changed any system or xposed settings in at least 2 weeks. A few days ago the phone had begun randomly rebooting and I thought I would just flash a new rom soon so I didn't worry too much about it. I was/am running clean rom.
Right now I just want to get something functional, I can not seem to do much with device other than reboot it. TWRP is installed, but it crashes and reboots a few seconds after loading. I tried the RUU from this thread 3 times (verified the MD5 too) and no change. I had to use the SD card as the fastboot oem rebootRUU just seems to boot up the phone normally.
Additionally I tried flashing CWM and that did not "Stick" it appeared to flash successfully, but attempting to boot into recovery only brings up TWRP.
I've tried wiping the cache several times, but that did not seem to help at all.
If anyone has suggestions I would love to hear them. Bonus points if you know what caused this. Right now I just want something that will function as a phone even if it means unrooted stock. I had this exact issue one month ago and I had Verizon replace the phone, I doubt they will be as willing to replace it a second time.
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0222
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(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: 3a4162f9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
In short, verizon m8 is stuck in a boot loop, recovery is in accessible and unflashable, fastboot and hboot work. RUU failed and I am out of ideas.
Trcx said:
This morning I woke up to my Verizon HTC one rebooting constantly.
Click to expand...
Click to collapse
I'm not familiar enough with the verizon specific issues to help beyond offering the suggestion that you post the same question in the verizon M8 section. Hopefully, there's a "restore to stock" type thread in the verizon area that would be helpful to get things normalized again.
Trcx said:
Hello,
This morning I woke up to my Verizon HTC one rebooting constantly. The night before I had done nothing unusual, just some games and youtube. I have not changed any system or xposed settings in at least 2 weeks. A few days ago the phone had begun randomly rebooting and I thought I would just flash a new rom soon so I didn't worry too much about it. I was/am running clean rom.
Right now I just want to get something functional, I can not seem to do much with device other than reboot it. TWRP is installed, but it crashes and reboots a few seconds after loading. I tried the RUU from this thread 3 times (verified the MD5 too) and no change. I had to use the SD card as the fastboot oem rebootRUU just seems to boot up the phone normally.
Additionally I tried flashing CWM and that did not "Stick" it appeared to flash successfully, but attempting to boot into recovery only brings up TWRP.
I've tried wiping the cache several times, but that did not seem to help at all.
If anyone has suggestions I would love to hear them. Bonus points if you know what caused this. Right now I just want something that will function as a phone even if it means unrooted stock. I had this exact issue one month ago and I had Verizon replace the phone, I doubt they will be as willing to replace it a second time.
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0222
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXXXXX
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(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: 3a4162f9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
In short, verizon m8 is stuck in a boot loop, recovery is in accessible and unflashable, fastboot and hboot work. RUU failed and I am out of ideas.
Click to expand...
Click to collapse
Just to verify, when flashing your recovery you are using
fastboot flash recovery twrp.img
and not
fastboot flash boot twrp.img?
an0ther said:
Just to verify, when flashing your recovery you are using
fastboot flash recovery twrp.img
and not
fastboot flash boot twrp.img?
Click to expand...
Click to collapse
Yes, I am definitely flashing to recovery rather than boot. On boot I get the clean rom loading screen (not twrp).
I did manage to get CWM up for a few minutes using fastboot boot, but that eventually crashed as well.
Checkout the last post
http://forum.xda-developers.com/showthread.php?t=2765027

fastboot reboot without usb debugging enabled - phone now bricked?

I typed fastboot reboot into cmd while usb debugging mode was not activated in the phones settings, and now the phone has booted into a blank screen. Is there anyway to get out of this?
The phone is on, but a blank screen? Or not responsive at all (like its powered off)?
What happens if you hold power + vol up for 30 seconds or more? This should force a reboot in virtually all situations (except a true brick). But what it reboots to, is another question.
The phone was stuck on the bootloader screen. I could connect the phone to cmd and got serial number etc, but as a soon as I typed fastboot reboot into cmd and hit enter, the phone went blank screen and never came back on. I have tried all button combinations loads of times and left it on charge for hours.
I think the phone is done, all I see in device manager now is QHSUSB_BULK. Shame since it was on bootloader screen before hitting fastboot reboot and could have been repaired.
Did you do any fastboot command that may have led to this?
Did the phone previously boot into OS, then was unable to (stuck on bootloader screen).
I guess what I don't understand, is the exact sequence of events; and you exact actions, commands, etc.
when I got the phone it would not boot into recovery or OS. I tried reboot from the bootloader screen and the bootloader would reload. I tried recovery from the bootloader screen and the bootloader would reload.
I was advised to try this:
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
When I tried the first step; fastboot reboot-bootloader - my phone switched off and has never switched on since.
Im not 100% sure what the previous owner did to the phone, it did say software modified at the top of the bootloader screen, but thats all I know.
This was the fastboot devices output
C:\adb>fastboot getvar all
< waiting for device >
(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) serialno:
(bootloader) imei:
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.295s
Thanks for clarifying. Unfortunately, there wasn't anything obviously wrong done with the phone (that might lead us to a fix); and it doesn't look good if its charged for several hours, and no response to button combo power+vol up.
Try the button combos with and without the charger connected (a few folks have had luck with this - for no discernible reason). Other than that, I don't think there is much you can do, short of maybe JTAG.
A couple suspicions (and they are just guesses, really):
1) emmc was already fried, which caused the phone to no longer boot into OS in the first place. Then it eventually went from "virtually" bricked to a black screen brick when you were trying to work with it (by no wrong actions of your own). We've seen a couple instances on this forum, where this appeared to be the case.
2) previous owner flashed something they shouldn't have. Similar to case #1 above, just waiting to go to full-on black screen brick. But the effect of flashing something that bricks the phone is usually more immediate.

HTC ONE M8 takes hours to start up

Hi folks, i've got a completely messed up Htc One over here. I dont know what else to do - I tried everything that came to my mind. Nothing helped.
The story so far:
A friend of mine got an already softbricked HTC One M8 from his son. He gave it to me and I managed to fix it by flashing the following RUU (bootloader open, S-On):
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Afterwards the phone ran flawlessly. Two weeks ago, my friend received a message, which was displayed on the lockscreen. My friend unlocked the screen and accidently tapped the message notification. Instantly an unknown installation process of some kind started. He paniked because he couldn't stop the process and powered down the device by holding down the power button. After that the phone didn't show any response to the power button. We thought it was completely broken now. After three hours, the phone suddenly started up. The os was working fine despite the fact he couldn't establish internet connection. He then made a factory reset. Nothing changed. Even if you plug in charging cable, it won't charge. Again I'm in charge now to fix it up.
What I did until now:
I managed to boot the device into bootloader mode via adb reboot bootloader. After 3 hours the bootloader mode was ready to go. First I changed to fastboot mode and flashed TRWP (openrecovery-twrp-2.7.1.0-m8). It worked. After that I flashed Android_Revolution_HD-One_M8_53.1_c8bf38 via recovery. No errors occured but the phone still takes hours to restart.
Can anyone help?
I'm from germany so please forgive me if I've made some mistakes.
Update:
Three hours after flashing the Android Revolution rom, the phone started up and finished the rest of the installation process without problems. The rom itself runs excellent. But after restarting the phone the problem remains - I guess I have to wait again 3 hours to proceed. Really annoying.
It sounds like your friend interrupted an OTA update, which is a very bad idea. Interrupting the process (by powering down) while a critical partition is being rewritten can lead to issues, even a brick!
Factory reset (if that is what you mean by "He then set it back to factory settings") won't do much in this case, all that does is wipe user data (doesn't actually restore OS or any other partitions).
Custom ROM is not a bad idea, but that is only 2 partitions (system and boot.img) while an RUU will restore all partitions (around 40) to proper factory software and firmware.
I would suggest running the same RUU again. Although the RUU that you mentioned may not run, depending on what the OTA did. Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
I will do as you said... as soon as the phone wakes up. Thanks.
Allright, here we go:
(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: HT-
(bootloader) imei: 357-
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s
Update: Just tried this:
I renamed 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed to 0P6BIMG.ZIP and saved the file on the sdcard. The Bootloader now says: "Device halted due to Large Image update fail! Press Power to reboot."
Renamed the file again and then tried via TRWP. Failed as well. Error in zipfile.

[SOLVED][help][modified][sense home unfortunately stopped]

Hello, Greetings XDA members
I have HTC M8x, unlocked bootloader, S-ON,rooted, stock rom, software status was official.
the phone and keys were in the same pocket and i guess volume up + power button might have been pressedd while the phone was in pocket.
the phone vibrated and restarted and was stuck on HTC screen with the famous red warning saying this build is for developement purpose..............and took 1 minute to boot, when the phone booted a screen came saying "ANDROID IS STARTING, OPTIMIZING APPS"
normally when this screen comes the total apps to optimize are 176 , but this time it was only 43, finally the phone booted completely. Now all i have is lockscreen and notification bar i cannot use the phone as it pop comes on a blank screen saying
1-"Sense home stopped unfortunately do you want to send this report to HTC"
2- .the process.com.google.gapps has stopped
3-exchange service stopped
i booted the phone into bootlader the software status has changed to modified.
i had made a nandroid after rooting the phone but the backup being of 7 gb i shifted it to SDcard.
i booted the phone to TWRP recovery to restore the backup but TWRP is unable to find it, it shows nothing when i select sdcard at recover option in twrp( i think its in sdcard so)
and now my phone takes lot of time to reboot. as everytime i restart my phone it gets stuck a while at htc screen with red warning message.
i cannot transfer the backup to twrp internal storage as i do not get the pop to select file transfer when i connect my phone to my laptop
i do have a RUU of my phone matching my region. I will have to relock my phone to flash the ruu
can i unlock it back i do have the unlock.bin file.
what shall i do.
PS: any way to remove the red warning i just dont want to wait so long for my phone to boot
below is my phones getvar all
version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT53LWM01208
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
HTC backup solved the problem.
it restored the apps and later downloaded sense home playstore

stuck at bootloop and recovery shuts off

Hi all,
My HTC One M8 is rooted with TWRP. I was having issues with it, so I decided to wipe it to see if that would help . However, it's now stuck in a bootloop, and when i try to get to recovery it turns off, or get a computer to recognize it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA44NWM02554
(bootloader) imei: 352628060928852
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ayouuuuub said:
Hi all,
My HTC One M8 is rooted with TWRP. I was having issues with it, so I decided to wipe it to see if that would help . However, it's now stuck in a bootloop, and when i try to get to recovery it turns off, or get a computer to recognize it.
Click to expand...
Click to collapse
What problems were you having exactly (before you wiped)?
What partitions did you wipe?
The phone is not turning on, it boot for a 2-3 sec that the logo shows up then it turned off, i've tried Volume UP+Volume Down+power method , Volume UP+power,but that's not working,also i tried factory reset ,then flashed RUU, the phone turned on for few minutes, while i was plugging it then it turned off and back to the previous problem. I think it's a battery problem but i don't know cuz it showed that is charged +90% and still not turning on.
It does look like battery issue. And I believe you wiped the OS so it can't boot when connected to charger.
Had same experience on my M7, only can switch on when plugged to charger (I didn't wipe anything so OS was still there and able to boot).
ckpv5 said:
It does look like battery issue. And I believe you wiped the OS so it can't boot when connected to charger.
Had same experience on my M7, only can switch on when plugged to charger (I didn't wipe anything so OS was still there and able to boot).
Click to expand...
Click to collapse
I installed a RUU from HTC's website and it took a few minutes to turn off and not switching on again

Categories

Resources