Database Info

[Q] HELP? I'm stuck in QHSUSB Download Mode?

I went to flash some things...and now it's stuck in the qualcomm download mode? How the hell do I get out of it??

You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium

redrumsilence said:
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?

What exactly did you do to cause this?
Sent from my HTC One X using Tapatalk 2

random1204 said:
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
Click to expand...
Click to collapse
When it happened to me, I found the QHSUSB drivers and installed them, my computer recognised my Sensation, but nothing else.
I scoured XDA, Google, all sorts, I couldn't find anything, I just sent mine in under insurance and got a new one
Sent from my GT-I9100 using xda premium

Your not screwed. Pmed
Sent from my HTC One X using xda premium

Galaxy s3 Tmobile in same state
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey do you have any info on this mode? I would love to have some kind of info as to a course of action, even though this is for a different model...

18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.

rob219 said:
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
Click to expand...
Click to collapse
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.

iElvis said:
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
Click to expand...
Click to collapse
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.

rob219 said:
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
Click to expand...
Click to collapse
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.

iElvis said:
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
Click to expand...
Click to collapse
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.

I had the same problem with the QHSUSB Download it turns out my phone had a really drained battery so how I managed to fix it was had it plugged into my computer and let the lights flash until i got a solid amber light. after about 15 minutes, I turned it on and it worked fine!

on my tablet i pressed for a really long time the power button and then it started up
it enters almos allways in qualcomm download mode when the battery is depleated.

you revived a dead thread to say something about your tablet?

I'm going to go revive some too now
Sent from my HTC One XL using Tapatalk 2

DvineLord said:
you revived a dead thread to say something about your tablet?
Click to expand...
Click to collapse
Someone can find my reply useful, compared to you and the other troll that did not say anything useful.

Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"

atombone said:
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
Click to expand...
Click to collapse
I'm guessing you flashed an international ROM on your One XL. That will do it.

iElvis said:
I'm guessing you flashed an international ROM on your One XL. That will do it.
Click to expand...
Click to collapse
Its a One X (ATT) but your probably right. I downloaded it from ONEXROOT.com. just strange to me that because i flashed a rom it screws the bootloader. ugh... sucks

Tip/warning rom manager recovery for htc one x (gsm)

I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.

Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.

Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium

nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.

rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only

sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app

Zombie thread alert!

Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app

_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike

MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita

bricked after flashing rom please help

I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help

We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2

superchilpil said:
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i got the rom from onex.com and they said the rom was for the one x, and no no boot

omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
IceColdJelly is for the international One X, not the AT&T One XL.
Someone else managed to brick their phone doing this. Check this thread and do what I told the other guy:
http://forum.xda-developers.com/showthread.php?t=1953975

omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
Goto - http://forum.xda-developers.com/showthread.php?p=33198089
User had similar issue and he solved

omarh3 said:
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
Click to expand...
Click to collapse
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.

denversc said:
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
Click to expand...
Click to collapse
same thing happened to me and it was the same rom i think please help in any way you can

nvidia31337 said:
same thing happened to me and it was the same rom i think please help in any way you can
Click to expand...
Click to collapse
You flashed IceColdJelly? Your phone is completely dead?

iElvis said:
You flashed IceColdJelly? Your phone is completely dead?
Click to expand...
Click to collapse
yeah completely and says same message in device manager

nvidia31337 said:
yeah completely and says same message in device manager
Click to expand...
Click to collapse
You're bricked, sorry. There is a way out if you have access to a Linux computer; see that other thread.

yea same here cant even get into recovery, same error sound when connected to the pc. Dont have access to a linux computer, No effect when i try to put in recovery mode or anything. Looks like im going to have to get a new phone

Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux

area51avenger said:
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
Click to expand...
Click to collapse
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.

redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
Cannot confirm if this can fix a corrupted hboot partition, but it's worth a shot. Haven't found any solid guides for pushing a new hboot partition to the phone while in this mode yet. Also do not want to brick my phone to test it

redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
didn't beaups write something about this at some point, trying to find it again..

what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon

omarh3 said:
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
Click to expand...
Click to collapse
and ive run the commands that were in the link and it says command not found

Did you pay attention to: Type the following commands (note: linux is case sensitive)

Crappyvate said:
didn't beaups write something about this at some point, trying to find it again..
Click to expand...
Click to collapse
Totally possible. I don't recall, or haven't seen it. I've seen a few posts to the effect of "if you have Linux, it can be fixed, PM me" but that is all I've seen. Would be nice if there was a writeup we can point people to (and I can add to my index thread).

Go to Evo 4g LTE forum and go to original development. 1st page should have a thread by yarrimapirate about downgrade. He recently figured how to brick, downgrade hboot and get s-off from QHuSB. Mode. The guys is a genius. That thread may have some answers or at least some help or info for you. People in that thread are stepping over themselves trying to help people.
Good luck.
I'd post a link, but I know as soon as I step out of this thread I'll never find it again (xda app)
Edit: go here http://forum.xda-developers.com/showthread.php?t=1940512
[HBOOT][10/24/12] 1.15/1.19 downgrade tool (Linux)
hurled from my AOKP'd Evo LTE. Enjoy.

[Q] Is there a way to completely wipe HTC One XL?

Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.

Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...

don't flash ICJ, just relock bootloader and ruu.
if you have no physical damage why are you getting a replacement phone?

Did you flash boot.img?
And how about you not ask how to defraud att because you don't know how to flash and fix a botched flash.

schumachermp said:
Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Click to expand...
Click to collapse
... and this is why we can't have nice things. Thanks, guy.

All I can think is, at least he did not throw it under his car.
It can be salvaged, where as other clown just destroyed it for nothing.
WR
Sent by WR's One XL

omario8484 said:
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
Click to expand...
Click to collapse
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.

schumachermp said:
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
Click to expand...
Click to collapse
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2

InflatedTitan said:
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I did flash boot.img. It just never moved past the CM10 starting animation. And honestly, not super familiar with fastboot three days ago... fairly familiar at this point. But nothing seems to get this thing to work. Please tell me what to do!
(BTW - I only called warranty at the advice of an AT&T employee in the store. I'd love to just fix my phone)

Twrp 2.3.1.0, wipe everything, flash boot.img in fastboot, and flash cm10 and gapps in twrp.

How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

schumachermp said:
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL

WarRaven said:
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
Click to expand...
Click to collapse
Ok, great. I've downloaded the TWRP recovery image and the Goo Manager APK... now how do I use Goo Manager on a device that won't boot up?

You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2

InflatedTitan said:
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.

schumachermp said:
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
Click to expand...
Click to collapse
I'm happy you got your phone running.

Don't get it all sticky with all that love.

Lol good job bro
Sent from my One X using Tapatalk 2

ECEXCURSION said:
... and this is why we can't have nice things. Thanks, guy.
Click to expand...
Click to collapse
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started

rodpgfx said:
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
Click to expand...
Click to collapse
Completely agreed. The notion astounds me (and disappoints me also) that the OP was going to send the phone in for a warranty replacement simply because they didn't do the proper research and learning before modding the phone. And when the condition was completely and easily reversible. If the screen comes on with this phone, it can be recovered.

recover memory maybe? hope?!

okay so as many of you know I ruined my phone and i said i was going to send it to jtag repair. as much as i want that to happen i dont have the funds at the moment to do so. what i did was call AT&T and then told them that i had a problem when updating to jelly bean, theyre sending me a new phone and so heres my question! is there any hope what so ever to recover my memory? i went to go see "In Flames" and i really would like to get my pictures and videos before i send it in, in 4-6 days. any ideas? and please, be nice to me on this one, i made a stupid mistake. but now i can learn from it. :/

I don't believe there's any way to do it short of jtag.
When you're in QHUSB_DLOAD mode, what that means is that the CPU can't find instructions on how to boot up, in this case, hboot. Either it's corrupted or the partition map is unreadable so it can't find it. That means it has no way to read the onboard memory because it has no OS to work with. It's like trying to start your PC without a bios in place--nothing happens.

Hi Elivis, you responded awhile back on my thread here: http://forum.xda-developers.com/showthread.php?t=2187491
I tried everything that was suggested by you and others with no luck, my question is am I having the same problem as the OP?

iElvis said:
I don't believe there's any way to do it short of jtag.
When you're in QHUSB_DLOAD mode, what that means is that the CPU can't find instructions on how to boot up, in this case, hboot. Either it's corrupted or the partition map is unreadable so it can't find it. That means it has no way to read the onboard memory because it has no OS to work with. It's like trying to start your PC without a bios in place--nothing happens.
Click to expand...
Click to collapse
Thank you... That's what I thought :/ okay well it was worth a shot asking
Sent from my HTC Inspire 4G using xda app-developers app

Okkoto said:
Hi Elivis, you responded awhile back on my thread here: http://forum.xda-developers.com/showthread.php?t=2187491
I tried everything that was suggested by you and others with no luck, my question is am I having the same problem as the OP?
Click to expand...
Click to collapse
No. He has a corrupted hboot, most likely. It can happen when your phone dies in the middle of a firmware update, which seems to be what happens during an OTA with SuperCID.
You have some strange connection error that's preventing your computer from communicating with your phone.

My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Sent from my One X using Xparent Green Tapatalk 2

twisteddroid said:
My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Sent from my One X using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Well look at it this way , computer can't read anything on phn, its like some1 who speaks English trying to read a mixed up word puzzle in Chinese. Maybe try hooking up with linnux but It still may not wrk
Sent from my HTC One X using xda premium

twisteddroid said:
My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Click to expand...
Click to collapse
He's on the 2.20 base. There is no unbricking tool for that.

iElvis said:
He's on the 2.20 base. There is no unbricking tool for that.
Click to expand...
Click to collapse
I'm on 2.20 and used unbrick method to unbrick mine after running jet. A week before s-off I was pissed cause I almost had a paperweight when I could have waited one more week lol
Sent from my One X using Xparent Green Tapatalk 2