I have a T-Mobile HTC One, unrooted and running the stock OS. A few hours after installing the 4.3 OTA update, the phone had a series of crashes in UIServer (or something similar), and when I attempted to restart it, it didn't start up again. The phone was charging at the time, and its red charging LED stopped working shortly afterward.
Now the phone won't boot, and when I connect it to my computer it shows up as QHSUSB_DLOAD. What can I do?
i<3burritos said:
I have a T-Mobile HTC One, unrooted and running the stock OS. A few hours after installing the 4.3 OTA update, the phone had a series of crashes in UIServer (or something similar), and when I attempted to restart it, it didn't start up again. The phone was charging at the time, and its red charging LED stopped working shortly afterward.
Now the phone won't boot, and when I connect it to my computer it shows up as QHSUSB_DLOAD. What can I do?
Click to expand...
Click to collapse
Unfortunately I have the same issue. I have contacted HTC and they told me to do the volume up and down and power button to recalibrate the battery but to no avail. I have tried using the T-mobile RUU but it doesn't recognize the device when plugged in to the PC. I bought the phone unlocked so I am not sure if T-mobile will even help me send it into HTC. I would be grateful for any help!
Can you get into the bootloader?
No, the phone is completely unresponsive, can't get into boot loader, the light and volume key thing didn't work either. I'm starting the phone is just hardware bricked. My device is completely stock too, how could HTC allow a manufacturer software update hardbrick their phone? Not sure if I will ever buy HTC again after this.
fenrir604 said:
No, the phone is completely unresponsive, can't get into boot loader, the light and volume key thing didn't work either. I'm starting the phone is just hardware bricked. My device is completely stock too, how could HTC allow a manufacturer software update hardbrick their phone? Not sure if I will ever buy HTC again after this.
Click to expand...
Click to collapse
Hold down the power button for 20 seconds or so. This brought me to boot loader from this issue. Flashed an RUU from that point to get working again.
(You will have to hold down the power button until it gets the HTC screen every time the RUU says 'waiting for bootloader' unless it's already there.)
Sent from my Nexus 10 using Tapatalk 4
Related
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
If you can get into hboot you arn't bricked.. Tho you usb port may be dicked like a broken part..
I would try to go stock for the hell of it.. I haven't had any issues.. I have in the past hung my phone locked it and dicked sense up.. But a battery pull always helped get back into hboot
So I wonder what is going on with yours.
Have you tried using a different usb cable ?? Or pluggin the phone in and let it charge over night ??
#Root-Hack_Mod*Always\
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
youre not bricked... you get into hboot fine... its running that you have a problem with so we go tier up...the eMMC of it all...there is a post by unknownforce that is for downgrading hboot 1.5 to .14 or less but follow those directions to the T and it willrewrite everything in there and then if you choose to do so you caqn update to hboot 1.5 and the new RUU and all from there
Can't get into hboot anymore.
can't get into hboot anymore, and if I'm s-off I can't run the process.
thermbug said:
can't get into hboot anymore, and if I'm s-off I can't run the process.
Click to expand...
Click to collapse
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
w0rdOo said:
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
Click to expand...
Click to collapse
A slight wiggle is alright. If your led light is coming on and off then somethin is broke.
Sent from my PG86100 using xda premium
Try taking the battery out for a few hours and letting the phone rest. This worked somehow for a few users.
Im trying to unlock my bootloader but RSD lite gets stuck at "Please manually power up this phone" even though its already in Android Homescreen. Anyone have an idea?
EDIT: Apparently it was a driver issue. Fixed it and finally got my phone unlocked. Running MROM now.
It sounds like our phone is boot looping leave phone plugged in pull battery put back in hold power button down volume down factory reset reboot still plugged in
Sent from my HTC One X+ using xda premium
markwoo said:
It sounds like our phone is boot looping leave phone plugged in pull battery put back in hold power button down volume down factory reset reboot still plugged in
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
No its already in the OS itself ready to be used. Nothing happens at all even when I rebooted and oh I cant get into recovery because the bootloader is not yet unlocked.
Basically what happens is I boot the phone into RSD mode, start to flash it with the proper sbf, it restarts a bunch, then it boots into android and stays there, it goes 100% but says "Please manually power up this phone" and then nothing.
Can anyone please help?
The RDS lite completed all the steps, I think at one point the phone reboots not remember.
But if the RDS completes all the steps and says the process finished, restart your phone and see if when you turn says "unlocked". It happened to me (can not remember if unlocking or putting a stock rom) not restarted automatically and told me that it.
sidVici0us said:
The RDS lite completed all the steps, I think at one point the phone reboots not remember.
But if the RDS completes all the steps and says the process finished, restart your phone and see if when you turn says "unlocked". It happened to me (can not remember if unlocking or putting a stock rom) not restarted automatically and told me that it.
Click to expand...
Click to collapse
Wait... I dont need to fastboot to unlock my bootloader? Im confused...
Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
I don't know that CWM was ever fixed to work properly on this device, which means that, combined with trying to flash firmware with a low battery could be bad news.
Leave it on a charger all day, and then come back to it and see if it turns on.
leeoniya said:
Hey guys,
As of 1 hour ago, I'm a sad panda. I think i hard-bricked my Jewel. While flashing the the 3.17.651.4 "Full" Firmware zip from here.
Battery was low, so i plugged it into USB while flashing. After it rebooted, screen wouldn't come back on (maybe a driver glitch, it happens sometimes and all is fine), so I unplugged it and tried pressing the power button to reboot it. It probably went into bootloader mode, found the IMG zip and started flashing it. I plugged it back in, nothing. Now cannot get any response out of it. Once the battery dies, maybe it will happily come back to life and all will be okay, but maybe it won't.
I've been flashing for years and have soft-bricked many times and been able to ADB my way out of it, but this time is different. Symptoms are:
- Screen is black, no lights no sounds.
- Phone will not turn off after holding pwr button for 30+ secs
- The only way i know that it's on is when I plug it into my desktop, i hear the usb connection sound. (Win 8.1 x64 with driver signing disabled)
- Device manager does not show any new device, no ADB or Android or HTC Phone.
- Phone will probably run out of battery in a couple hours it was around 5% to begin with
I'm on Hboot 2.09.2222 (DirtyRacun S-OFF) Firmware was 1.12.something. Was happily running CM10.2 and Clockworkmod 6.0.4.8.
anything I should try?
thanks a lot,
Leon
Click to expand...
Click to collapse
Did you ever get this working? I've got the same symptoms with my phone. Appears to be off and wont turn on but when plugged into the pc, the pc detects it.
This happened this moring for no apparent reason, i moved a file for a game to be installed (final fantasy iv) in the android/oob folder and rebooted, and it never fully did.
Im stuck on the HTC logo forever.
At 1st i said to myself, lets go to hboot and make a factory reset, so i pressed volume - and power, and when i did, instead of restoring the device (wich was unlocked and rooted) it went back to the neverending htc logo, and it does the same for the recovery and the erase everything one, so from that point i tried installing a few firmwares from my carrier which is videotron, and it alway failed either because the signature is not compatible or simply because the device is not detected... it seems to get worst try by try...
I also tried to install from the sd card, adb or Amaze_All-In-One_Kit_V5.1 and 4.0.
Nothing works, please help me.
I just bought this phone used a month ago, and i loved it, and its unfair for it to die for no serious reason.
Are you able to access bootloader?
stuck
syedbilal093 said:
Are you able to access bootloader?
Click to expand...
Click to collapse
If it went to the HTC logo, you probably accidentally bypassed the recovery.
Turn the phone off, remove battery wait 10 seconds, install battery, wait 10 seconds, hold the volume DOWN button, while holding the volume DOWN button, press and release the power button. Keep holding the volume DOWN button until the bootloader screen appears, and then release it.
See what you can do with that.
If it doesn't help, find the RUU for your carrier--there's a list of RUU's in General section, "They're all here now" thread, and find the instructions for properly renaming it and placing it where it needs to go to have it install.
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
androidnj7 said:
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
Click to expand...
Click to collapse
At any point can you get it to answer
Fastboot devices
?
dottat said:
At any point can you get it to answer
Fastboot devices
?
Click to expand...
Click to collapse
I can not get it to receive any signals from me in the bootloader as it shuts down immediately. I tried connecting it to my computer for use with adb, but fastboot WAS enabled and developer tools were DISABLED (i think), plus it cannot keep a constant connection, so that wasn't working.
After doing some research I think I can save it IF I can get it to a stable state from the one it is currently in, and then using the bootloader screen to do a factory reset ( or use
"adb reboot recovery"), but like I said that is depenednet on getting it to stop the boot loop.
I also tried doing something called an RUU (I have limited knowledge of this, i sued the dottat one), but since it cannot establish a constant connection, it did not work.
Im open to any suggestions at this point! Thanks
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
androidnj7 said:
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
Click to expand...
Click to collapse
Possibly. What does the device show up as in device manager?
dottat said:
Possibly. What does the device show up as in device manager?
Click to expand...
Click to collapse
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
androidnj7 said:
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
Click to expand...
Click to collapse
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
dottat said:
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
Click to expand...
Click to collapse
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
androidnj7 said:
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
Click to expand...
Click to collapse
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
dottat said:
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
Click to expand...
Click to collapse
You are right unfortunately, I can absolutley not stay in the bootloader with any sort of stability. I read on another thread that opening it up and disconnecting the battery from the motherboard would help, so thats what I did. As soon as I sealed it back up, the reboot-loop started right up again. My guess is that the motherboard is fried, its either that or the battery is holding no charge whatsoever.
If the board is fried, im done right?
if its the battery, is there any way to manually charge not going through the board?
Thanks for all your help btw!