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.
Related
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
Hey everyone,
I'm new to the forum and didn't find a thread that quite matched my problem, so I started this one. I hope I am at the right place
So I converted my m8 to GPE 5.0.1 with the RUU from graffixnyc. I am S-OFF with sunshine. (It is a GSM international version)
I didn't have root access to the phone at this moment.
Then I wanted to switch back to Sense, so i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2733523
All worked out pretty good until the command fastboot reboot-bootloader. Since then I am stuck in a bootloop and after 2-3 times seeing the HTC logo in green, it shows a screen with a red triangle. (picture attached)
I can only manage to get in the recovery mode by pressing volume up + power. (picture attached) I don't now what I have to flash now to get it to work again. A new firmware, ROM or RUU? My current CID is 11111111 as I followed the guide.
Please help me fix this problem, I appreciate your help very much!
Best regards,
N4PSTEr17
Post your fastboot getvar all result minus serial no. & imei no.
Do you have in mind, which version of Sense that you want your device to be ?
Thanks for your fast answer!
As I wrote in the title, I can't access the phone from the computer. When it is plugged in, I hear a sound, but "adb devices" shows no devices found.
When in recovery (2nd pic) select reboot system now ... when it goes dark, press & hold volume down button. This will take you to hboot. Then go to bootloader and do that fastboot getvar all.
If stuck and seeing the HTC logo in green, press & hold both volume up and power button. When the screen goes off, release both buttons and quickly press & hold volume down button. This will take you to hboot. Press power once, you'll be in bootloader screen
Thank you, that worked perfectly!
My goal was to get to sense 6.0 with the stock version from HTC.
So now that I am in fastboot, can I just follow the rest of the tutorial?
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
That tutorial is not updated for quite some time. The last update was 26th May 2014
What you need to do now :
Download RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10 exe here : http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 - the first link
This will update your device to the latest lollipop 4.16.401.10
1. put your device in bootloader/fastboot mode and connect to PC
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Worked perfectly!!
Thank you so much :good:
Hello, you glorious bastards
Trying to revive customer's One X, CID 032 after the original system started to crash and factory reset didn't help.
After tons of failed RUU, rom and recovery flashes (only cwm 5.8.4.0 worked because of the touch-problem) I was able to flash Revolution JB Deodexed 4.18.401.3 through recovery.
For the first time ever it went past "quietly brilliant" logo and booted to a certain point where it even showed a force-close error. I was happy with that At least it's something.
This is where things took the turn for the worst:
> Bootloop
> Remembered to flash boot.img :angel:
> boot.img flash crashed/freezed!!! (either because it got LOCKED after flashing rom or the battery was on the edge of the acceptable %, i'm not sure)
> rebooted to fastboot, SCREEN FLICKERED once (showing black-white stripes) and the backlight was dead after that and still is.
> tried unlocking again with the Unlock_code.bin but unlock token check failed
> checked "getvar all" and saw this (model id used to be PJ46100) :
Code:
C:\AndSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.401.2
(bootloader) serialno: [B]123456789012[/B] <<<------------------
(bootloader) imei: xxxxxxxxxxxxxxxxxxxx
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: ▲©”į▼"kĻ├I╗↑ <<<----------------------
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3770mV
(bootloader) devpower: 28
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.861s
Now i can't flash anything because it's locked and model id is jibberish (also serial).
Can't read any info on screen because backlight is off or broken (can only enter fastboot by pushing buttons by memory)
I might have forgotten some details because I was tired and had been working on it non-stop for 6 hours.
You guys have any ideas?
Could the hardware itself be faulty? Because nothing has gone the way it should.
Can a failed flash cause blacklight faliure?
P.S. My first post in many years and have to say... not even million thanks-buttons wouldn't show how amazing you developers all are. Keep it up.
texic said:
Hello, you glorious bastards
Trying to revive customer's One X, CID 032 after the original system started to crash and factory reset didn't help.
After tons of failed RUU, rom and recovery flashes (only cwm 5.8.4.0 worked because of the touch-problem) I was able to flash Revolution JB Deodexed 4.18.401.3 through recovery.
For the first time ever it went past "quietly brilliant" logo and booted to a certain point where it even showed a force-close error. I was happy with that At least it's something.
This is where things took the turn for the worst:
> Bootloop
> Remembered to flash boot.img :angel:
> boot.img flash crashed/freezed!!! (either because it got LOCKED after flashing rom or the battery was on the edge of the acceptable %, i'm not sure)
> rebooted to fastboot, SCREEN FLICKERED once (showing black-white stripes) and the backlight was dead after that and still is.
> tried unlocking again with the Unlock_code.bin but unlock token check failed
> checked "getvar all" and saw this (model id used to be PJ46100) :
Code:
C:\AndSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.401.2
(bootloader) serialno: [B]123456789012[/B] <<<------------------
(bootloader) imei: xxxxxxxxxxxxxxxxxxxx
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: ▲©”į▼"kĻ├I╗↑ <<<----------------------
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3770mV
(bootloader) devpower: 28
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.861s
Now i can't flash anything because it's locked and model id is jibberish (also serial).
Can't read any info on screen because backlight is off or broken (can only enter fastboot by pushing buttons by memory)
I might have forgotten some details because I was tired and had been working on it non-stop for 6 hours.
You guys have any ideas?
Could the hardware itself be faulty? Because nothing has gone the way it should.
Can a failed flash cause blacklight faliure?
P.S. My first post in many years and have to say... not even million thanks-buttons wouldn't show how amazing you developers all are. Keep it up.
Click to expand...
Click to collapse
This look like Black screen of dead
Thant said:
This look like Black screen of dead
Click to expand...
Click to collapse
I don't think so. The symptoms are totally different.
When it still had factory installed system it just started crashing and rebooting. The display, backlight and all the touchy functions worked perfectly.
Now the display itself works, I can see the boot logo and fastboot menu under certain angle and light condition (it's just hard to see the text because it's so small)
Only the backlight has "died"... along with the model ID.
Any other ideas?
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.
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.