Database Develop

QHSUSB_DLOAD mode??

Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?

Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.

Already tried, no luck. Tells me the device has not been found.

I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.

Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse

I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One

Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!

Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app

I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app

lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.

same here
Any idea how to fix it?

Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk

My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.

Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..

QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry

My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..

danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?

My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.

danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far

Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:

Qhusb_dload?

Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?

dlnas said:
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
Click to expand...
Click to collapse
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.

iElvis said:
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
Click to expand...
Click to collapse
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?

dlnas said:
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
Click to expand...
Click to collapse
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.

iElvis said:
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
Click to expand...
Click to collapse
Before it died. I unlocked the phone and the only thing I could do was pull the notification drawer down. It would not let me open any app or even the app drawer.

dude this sounds frightening

Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.

postfatal said:
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
Click to expand...
Click to collapse
That fix is only for a couple of specific issues:
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.

tousary shall
iElvis said:
That fix is only for a couple of specific issues:
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
Click to expand...
Click to collapse
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.

Had the same problem after flashing the wrong recovery..
THis means it is hardbricked and unrecoverable..
You could ask here: http://forum.xda-developers.com/showthread.php?p=43750389#post43750389
Else send it in for repairs

dlnas said:
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Click to expand...
Click to collapse
It's a hardware fault, from everything I've seen, and HTC or AT&T should replace it. AT&T tends to be very easy about this. If the phone won't power on at all, they shouldn't give you a hard time.

[Q] nexus 6 after new 5.1.1 update BIG PROBLEM(Keeps turning off

Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance

Sounds like battery defect. Has same issue on my n4 with regards to being ok when plugged in
Sent from my Nexus 6 using Tapatalk

benthebratt said:
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Click to expand...
Click to collapse
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.

Evolution_Tech said:
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Click to expand...
Click to collapse
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120

benthebratt said:
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
Click to expand...
Click to collapse
Return merchandise authorization.

[Poll] Has your phone randomly powered off?

Has your 7 Pro randomly shut down since you have had it?
Seems like it's been happening for a fair few people on multiple carriers and versions of the phone, including myself. You can see complaints in the below thread.
https://forums.oneplus.com/threads/one-out-of-2-oneplus-7-pro-is-now-dead.1043492/
You can get your phone back on by holding power+vol up for a few seconds! This is super annoying as I use my phone as an alarm and now can't trust it to work.

Yes I have.

Nope

Twice...now I'm rooted we'll see if it continues
Sent from my GM1915 using Tapatalk

exxpired said:
Has your 7 Pro randomly shut down since you have had it?
Seems like it's been happening for a fair few people on multiple carriers and versions of the phone, including myself. You can see complaints in the below thread.
https://forums.oneplus.com/threads/one-out-of-2-oneplus-7-pro-is-now-dead.1043492/
You can get your phone back on by holding power+vol up for a few seconds! This is super annoying as I use my phone as an alarm and now can't trust it to work.
Click to expand...
Click to collapse
Could be Hardware/Software issue. But if you were able to revive it with the said shortcut, then I think it's a software issue.
Btw never faced this issue.

I have had this happen as well a few times but it was due to a certain kernel I was using.

Yup, was rather scared as even long pressing power didn't do anything. Thought it was completely game over. Luckily mentioned power-on button combo brought it back to life.
Has happened twice now. So far this and the worthless A/B partition shizzle has left a bad taste for now.

You could always check to see if this is ticked to make sure you don't miss an alarm.

I have this since day one no reboots at all

I have the T-Mobile version and converted to International running stock OS w/ elemental kernel. No issues since I bought it..

none so far. I have had my phone since last thursday and has a build date of 6.4.2019 everything works great no issues.

Not experiencing anything of that nature on my end luckily.

Happened to me the other day. I just assumed I drained the battery although I knew there was no way I used it that much since taking it off the charger. I just left it off for a while and then turned it on by attempting to go into the BL.

luckylui said:
I have the T-Mobile version and converted to International running stock OS w/ elemental kernel. No issues since I bought it..
Click to expand...
Click to collapse
Same here.
Sent from my GM1915 using Tapatalk

Happened to me 3 times already when I go to bed. So I miss my alarm to wake up. Since I have turned off that sleep optimization crap it hasn't happened. Not sure if that did anything to be honest.

mac796 said:
Happened to me 3 times already when I go to bed. So I miss my alarm to wake up. Since I have turned off that sleep optimization crap it hasn't happened. Not sure if that did anything to be honest.
Click to expand...
Click to collapse
Clock>Settings>Power off alarm

Nope. Only once got recory bl but was my own fault and was easilly fixable

No Issues since my possession at product launch.

B3311 said:
Clock>Settings>Power off alarm
Click to expand...
Click to collapse
Does that still power the device on in the powered off state?

exxpired said:
Does that still power the device on in the powered off state?
Click to expand...
Click to collapse
Yes. If that's turned on and your phone is off, it'll basically turn the phone on like you normally would using the power button. It does this a minute or two before your alarm is supposed to go off.

Black screen and freeze - MIUI Global 10.2.14 stock

Today I have had the same issue 3 times. Not a single one before (MI9 6+128 global since July).
Check the phone, lock, to the pocket. Later, take the phone to check it and screen off, not responding to anything.
At the third occurrence I tried to connect via adb, but no device detected.
The only way to revive was to Pwr+VolDown to Fastboot and then Pwr until reboot. Some bootloops happened though but it finally came through, for now.
Any idea what is happening??? As mentioned, phone is 100% stock, no root or custom stuff whatsoever.

Hi friend,
So you can try "factory reset".
Good luck.

[email protected] said:
Hi friend,
So you can try "factory reset".
Good luck.
Click to expand...
Click to collapse
Today happened again. I managed to PWR+VOLUP to reboot. So far so good.
30min of standby later, irresponsive again. No key combination would switch on the phone. No reaction to charger, PC connection, nothing.
Incidentally, both occurrence sets (yesterday and today) happened at home; in the office I have had no issues. Some wifi issue? A neighbor testing a EMP device?
Let's go for warranty... but I seriously doubt I will keep with this brand... they need to take software and QA more seriously. My wife's Redmi Note 5A is also victim of these spurious "blackouts" though they have been recoverable so far.