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:

[Q] HTC One Mini 2 Freeze in Charge-Screen

Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer

lol
peacer95 said:
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
Click to expand...
Click to collapse
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.

peacer95 said:
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
Click to expand...
Click to collapse
What he did was a hard reboot, accomplished by holding the power and vol-up buttons for about 10 seconds. Just wanted to add this.

Hey guys,
any solution to this problem??
Got the same issue. unlocked bootloader with htcdev, installed TWRP Recovery and rooted phone, everything worked fine yesterday.
Today I installed xposed framework, then I plugged-in the charging cable and turned off the phone because I wanted to flash xposed in Recovery. But when the phone turned off, it only showed the charging screen with the message ("This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.") and didn't react to any button pressings until the battery finally died.
Then I plugged in charging cable again. Now I have again the charging screen, only difference is that the LED doesn't flash permanently but it now blinks. Computer recognizes phone but I can't send fastboot commands since it is turned off.
Any help would be appreciated!
EDIT: After a lot of tries, I finally also managed to fix it with 10 seconds power + volume up....

Super Hard Brick Stock Moto X 1st Gen

My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.

Brett316 said:
My brother just bought a new in box Moto X off eBay (ruling out any warranty) about a week ago. Today it asked to update the OS, which he accepted. During the update (green android robot with blue swirly thing inside) the phone simply blinked off and ceased to respond. And I mean NO response. I don't get LED's, boot, fast boot, recovery, charge, ANYTHING. Plugging it into a computer also gives no response.
My bro didn't take note of the OS that it was updating to, but it was just an OTA. He had no suspicious apps, hadn't played with ROM's, just barely had his phone working before this happened.
I spent a long time googling for this same problem, but no results. Everyone at least gets SOME response out of their phone. I can't imagine this is a hardware problem, and I'm certain he had plenty of charge when he initiated the update (only half a day of use on the charge, should have been at %50-60 on the low side).
Anybody have an idea on how to proceed? Any info would be greatly appreciated, even a link to a helpful thread that I missed.
Phone is a 1st gen (2013) Moto X on AT&T.
Click to expand...
Click to collapse
I'm in the same boat... I recently bought a Moto X (2013) on eBay and having had the Atrix HD previously, I thought rooting should be simple.. yeah, no, it wasn't... i'm now hard bricked. I followed a guide about updating the driver and using the program that tricks the driver signing, and it all went as stated, except the phone still won't turn on. Adb can't see it, neither can mfastboot.. RSD Lite does see it tho it fails flashing.. I don't know what to do.. I don't have much $ and I had just saved up for awhile so any help would be appreciated

Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?

platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working

amg0005 said:
ya exactly
i have the same problem but in my case the phone was good but while coping video the phone just turned off.
that's it after that im stuck at boot loader unlocked ...
pls somebody suggest me what to do to get back my moto x working
Click to expand...
Click to collapse
I started here: http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
After step 3, manually installing the unsigned drivers, I had to follow this: http://forum.xda-developers.com/moto-x/general/how-to-unbricked-hard-bricked-phone-t3146036
I skipped to "Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat"
It took a bit of time, but the phone rebooted and I am rooted.

platinumthomas said:
Brett and Elisha, are you running Windows? If so, when you connect your phone, does Windows chime as if it recognizes something is connected via USB?
Click to expand...
Click to collapse
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???

sachinrao13 said:
yes!! it does recognize when i connect it to the computer. can i do anything to get it on ???
Click to expand...
Click to collapse
There's a thread on this forum titled 'Resurrecting a dead Moto X'. It describes your scenario in detail and explains a way to fix it.

Idol4S (Android) - No power, blinking LED

Hello everyone,
Having major issues with my Idol4S. It is the unlocked version (Cricket). It was working just great until a few days ago when I plugged it into the car charger. Phone instantly shut off, and got stuck with a blinking (rapid) LED light. This happens if plugged into my PC, or my Alcatel charger (both the wall and car).
The phone has suffered no damage (had a cover, but it was never dropped or exposed to external weather damage, nor water - I took great care of it), and was working quite well. I'm unable to boot it into any sort of recovery mode (as the screen is black, so I wouldn't be able to see anything anyways). The only indication of life is the flashing LED when plugged in ..(charging loop, maybe?)
I am using my idol4S Win10 (TMO/unlocked) phone in the meantime, but the base model was working just fine before this happened. I was also mindful of checking voltage/Amps when using chargers, so I would not have exposed it to any incorrect input/output. QuickCharge worked great too (sorely missed on Win10 model).
The phone was never rooted so it has the stock ROM, and whatever the last update Alcatel had pushed out for it. I did have developer mode and USB debugging on for MSVC/NSDK.
Is there anything I can do? After awhile being plugged in, the LED shuts off. I kind of need it as I was porting my game engine to it (using the SDK), plus it was my primary. I love the Win10 version too, but the Android idol4S was my primary phone. Kind of disappointed in Alcatel - I read it doesn't have an external battery otherwise I would attempt to transplant the battery (if that is even the issue). . .
Any tips, advice, or suggestions would be greatly appreciated! <3

what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.

PizzaG said:
what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.
Click to expand...
Click to collapse
Okay, but would it work even though the phone gives no indication of being plugged in to the computer, or the chargers for it? I plugged it into the PC just now, brief flash of light and then nothing. .
Should mention again that the screen does not turn on, ever since that day, the screen has not came back on -- so I really can't do anything, even accessing 'download mode' does not show anything on-screen, nor does Windows 10 alert me of the USB device being connected.
I wouldn't mind starting from scratch at this point. I'm definitely interested in getting up and running again! It's not like I can do anything else at this point except spend money and get it repaired by TCL.
Would it be rude of me to ask for links to the TWRP/CricketROM from you? Maybe a quick-start guide, I pick up on things easy, but I've never properly flashed with TWRP =)
Also @PizzaG, THANK YOU for your help!! Definitely appreciated <3
Oh! @PizzaG, I also have an older Onetouch Idol 3 that has the _exact_ same symptoms, I wonder if that too could be recovered? ... ^__^

well I guess the first thing to do would be plug it into the PC. Hold volume+ and volume- then hold power until you feel the buzz and let go of power. Hopefully you get the red Download mode screen? I didn't realize it had no life at all, I thought it was just messed up. It's sounding like more may be wrong then just a simple reflash.
New TWRP and ~CriketRom~ Beta5: https://forum.xda-developers.com/idol-4s/development/rom-twrp-recovery-t3792659

Phone restarts every time I plug in the AC charger

Does anyone face this problem as well??
Whenever I plug in the charger, or even the USB type-c cable into my phone, if the other end is connected to any power source, my phone would freeze for a while and then restart.
Does anyone have an idea about this problem?

Have you tried different adapter/cable/USB port? How old is the phone? Using stock firmware?

simar811 said:
Does anyone face this problem as well??
Whenever I plug in the charger, or even the USB type-c cable into my phone, if the other end is connected to any power source, my phone would freeze for a while and then restart.
Does anyone have an idea about this problem?
Click to expand...
Click to collapse
It's **** as hell check this
https://zentalk.asus.com/en/discussion/12715/rog-phone-2-12-512-freezes-and-auto-restart-problem
https://youtu.be/LRlp6M7GjOU
My phone got repaired two times from asus still the issue peeists.No solution u revert back to android 9 still u will have the same problem.check the links

simar811 said:
Does anyone face this problem as well??
Whenever I plug in the charger, or even the USB type-c cable into my phone, if the other end is connected to any power source, my phone would freeze for a while and then restart.
Does anyone have an idea about this problem?
Click to expand...
Click to collapse
Hay, my suggestion, backup all data, fully reset and format internal, i have this problem long ago, after update new firmware, escepcially if then place TWRP, doing root with magisk and kernel custom.

MyronAz said:
Have you tried different adapter/cable/USB port? How old is the phone? Using stock firmware?
Click to expand...
Click to collapse
Yes, I have tried a bunch of cables, adapters and USB ports. I've tried one plus & Samsung chargers, tried plugging in the car, laptop and also some battery banks. There's nothing much I can do now. It seems that the moment the type c port is in contact of a current source, it freezes and eventually restarts.
The phone is almost a year old now, bought it last October. I started experiencing this problem in March. I have been living with it quite a while now. I was waiting if anyone else experienced this particular problem but it seems that no one has. The only freezing videos I saw were from another issue wherein the phone automatically restarts while being used. Mine won't restart abruptly, it would do that only when it actually touched a power source. But here I feel the problem is quite different.
I'm still using the stock firmware. I have tried factory resets and also followed the instructions on this link too.
https://forum.xda-developers.com/rog-phone-2/how-to/repair-rog2-phone-edl-modeofficial-t4012175

Niks6164 said:
It's **** as hell check this
My phone got repaired two times from asus still the issue peeists.No solution u revert back to android 9 still u will have the same problem.check the links
Click to expand...
Click to collapse
Another issue is that I bought it in India last year, and now I'm located in Canada. I can't go back to India to get it fixed by ASUS since they don't provide an international warranty.

Arthuer said:
Hay, my suggestion, backup all data, fully reset and format internal, i have this problem long ago, after update new firmware, escepcially if then place TWRP, doing root with magisk and kernel custom.
Click to expand...
Click to collapse
I might root it pretty soon and flash a custom kernel. But I hardly think it's gonna solve any problem