Recover from the dread QHSUSB DLOAD

[Camicia]

Lately my HTC One shut off while typing on it and it was dead.
Holding power for 10 seconds (and any of the combination with the volume buttons) did not help.
And when you connect it to the power does not even had the red led indicating that is charging.

If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.

So the phone is dead but not really completely dead.

Clearly that QHSUSB_DLOAD is a Qualcom hook that could be use to debug and probably re-flash the phone. The question is what is this tool and how do you use it?

I think there is some sort of standard way to recover across phone (maybe not all with a Qualcomm but I am sure that the protocol is the same among a few processors).

There are a few examples out there:
[UNBRICK] HTC Unbricking Project - http://forum.xda-developers.com/showthread.php?t=1627886
DLOADTool - https://github.com/posixninja/DLOADTool
http://xiaomi.eu/community/threads/ultimate-cure-to-the-qhsusb_dload-of-mi2-s.20567/

And a lot of info about HTC internal here: http://tjworld.net/wiki/Android/HTC/Vision

So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).

 

[PhoenixPath]

If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.
So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).

First: Wrong thread. Mod will likely move it to Q&A. (Hopefully not before I'm done trying to post this to help you out)


This normally occurs if you have a modified hboot meant for downgrading your device via RUU or some-such.

Best solution is to plug it in to a Windows 7 (32-bit) machine, and download an RUU.

If you hold the power-button for 15 seconds or so, you should feel it "bump". Basically, it was in a broken fastboot mode and you just put it into RUU mode, but with no on-screen indication of it.

Running the RUU at this point should work but remember: Whenever the RUU utility states "Waiting for Bootloader", you will need to hold the power-button in until you feel the bump again or it moves from "Waiting for bootloader" (should be around 15 seconds, every time).

I've made multiple full conversions on my device and run into this problem periodically before I started flashing rumrunner's hboot prior to conversion.

Hope this helps.

For future reference - some helpful links:
(added to sig)

 

[Camicia]

I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.

 

[PhoenixPath]

I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.

Most of those links are XDA. The others are HTC, RumRunner and such.

By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)

Sorry I couldn't be of more help.

 

[Camicia]

Most of those links are XDA. The others are HTC, RumRunner and such.

By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)

Sorry I couldn't be of more help.

Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.

 

[PhoenixPath]

Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.

Well, it's been used by countless people with no reports of any trojan or otherwise. I've used it several times myself (I use it every time I convert to get back to T-Mobile stock and make sure OTA's work before moving on to the next conversion). The only reason it isn't a thread here for it is due to politics I try not to get involved in. Just trying to help folks out.

As always though, I do strongly suggest that everyone use their own judgement and that they do not do *anything* with their devices that makes them uncomfortable or that they feel may have unintended consequences.

That said; I use chrome exclusively and haven't seen any warnings from it. Even Google Search isn't reporting issues with the link. If I were you I would check and make sure that you don't have any "helper objects" like toolbars or search-assist add-ons installed as those sometimes hijack page-requests.

Regardless of all of that, I am sorry I could not be of more help. The only time I've seen the DLOAD issue - the above steps fixed it. Seems my experience is not enough to solve this one. Hopefully someone else can pitch in. Best of luck!

 

[Pons]

Thread closed as duplicate/triplicate/quadruplicate of QHSUSB_DLOAD - What is the protocol?. Please continue the discussion there.