Database Info

One S in QHSUSB_DLOAD mode

My HTC One S is stuck in QHSUSB_DLOAD. I tried to bring it out of it using Unlimite.io's solution for One V, though it finished successfully One S didn't come out of this mode. Is it completely dead and should be sent to company or is it still un-brickable?

Does it boot into HBOOT after running the tool?
Sent from pixels to more pixels

Nothing happens.Just blank screen and charging led which remains orange forever.

same here man.. didnt work with one v unbricker either ...

This is not going to help you (sorry), but maybe provide some insight for everyone..
Do you know how you got into this state?
I've seen reports from others deleting large files from their sdcard partition.
Do you remember what you did right before it died?
Thanks,
-Jobo

Your HBOOT might have become corrupted. This happened to people with a Sensation after writing S-ON flag from S-OFF for warranty purposes. A re-flash of your bootloader would be good. But since you can't get into the bootloader, this is quite hard. Have you tried following the Sensation unbricking guide, using a different, One S HBOOT?
Sent from pixels to more pixels

Same problem here after flashing the new OTA...
Any solutions

Same threat here:
http://forum.xda-developers.com/showthread.php?t=2064202
We tried almost anything to get it out of dload, nothing seems to work.
I made a new threat here to collect all info about this issue.

Vauix said:
Same threat here:
http://forum.xda-developers.com/showthread.php?t=2064202
We tried almost anything to get it out of dload, nothing seems to work.
I made a new threat here to collect all info about this issue.
Click to expand...
Click to collapse
Does it mean that we to reflash the bootloader? Mine cant go to HBoot nor Bootloader.
Sent from my GT-S6500D using XDA Free mobile app

MPRG8260.hex
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.

carbonat87 said:
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.
Click to expand...
Click to collapse
Im guessing, even with the file you provided, no one i gonna take a look at it, i mean everyone here probably had an upgrqde from the One S surely after this issue even myself.
Sent from AssForMini

carbonat87 said:
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.
Click to expand...
Click to collapse
Hi, do you happen to have 8260_msimage.mbn
Anyone ?
thank you

Unbricking HTC One S C2 [S3]
Hello my friends. Newly I faced with the same problem. Phone did not react and was defined as QHUSB_DLOAD.
I solved a problem thanks to a topic http://forum.xda-developers.com/showthread.php?t=1522351
Instead "pyrV.VV.nb0" I put file hboot.nb0 which took from a RUU firmware for my device. Also you can find it in firmware.zip
RUU roms: http://androidruu.com/?developer=VilleC2
And how get hboot.nb0 there: http://forum.xda-developers.com/showthread.php?t=2534428. Good luck!

AxNx666 said:
Hello my friends. Newly I faced with the same problem. Phone did not react and was defined as QHUSB_DLOAD.
I solved a problem thanks to a topic http://forum.xda-developers.com/showthread.php?t=1522351
Instead "pyrV.VV.nb0" I put file hboot.nb0 which took from a RUU firmware for my device. Also you can find it in firmware.zip
RUU roms: http://androidruu.com/?developer=VilleC2
And how get hboot.nb0 there: http://forum.xda-developers.com/showthread.php?t=2534428. Good luck!
Click to expand...
Click to collapse
i will try this thanks
currently i got two htc one s (c2) bricked both detected only as qhsusb_dload in windows
just out of the blue..one when it died on battery and the other one when it hangs and i try to restart it by holding the power button
few years ago this happened once to one of them but i fixed it 'accidentally' by following the instruction at unlimited,io (i dont know what i was doing that time)
i will give this a try and report back

QHSUSB_DLOAD mode any help?

Hi,
I tried changing my bootscreen in this thread (http://forum.xda-developers.com/showthread.php?t=1777223&page=20) but messed up, that I S-OFF'ed a friend's phone and not mine. So I basically flashed the h-boot 1.06 (which is the right one for me) on my S-ON One S. Ì then rebooted in TWRP and my screen won't turn on anymore and my computer just says it's searching for QHSUSB_DLOAD drivers. I've googled a bit and it doesn't look very good for my One S.
Any, any, any help out there? :/
Thanx in advance,
Don

This has been asked so many times here. Have you bothered to look around here at all? Look in general or look in one of the many threads here in q&a with nearly same title
Sent from my HTC VLE_U using xda premium

http://unlimited.io/qhsusbdload.htm

No. I do not recommend using the unlimited.io tool, in many cases it will prevent the phone from showing it's EMMC partitions to ubuntu. Use that if, and only if, this fails multiple times. Then it might work.

usaff22 said:
No. I do not recommend using the unlimited.io tool, in many cases it will prevent the phone from showing it's EMMC partitions to ubuntu. Use that if, and only if, this fails multiple times. Then it might work.
Click to expand...
Click to collapse
I have by now tried both versions and both will not work. Sad story but I guess that's it for my 1S or does anyone have another idea?

donverse said:
I have by now tried both versions and both will not work. Sad story but I guess that's it for my 1S or does anyone have another idea?
Click to expand...
Click to collapse
Any error messages? How doesn't it work? Or was it too late - had you already tried the QDL reset tool, did qdl keep restarting

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

[Q] Phone dead!

Hey guys, need your help! I updated my AT&T One X using this manual method:
http://www.htc.com/us/support/news.aspx?p_id=464&p_name=htc-one-x-att
And now my phone is not even turning on. Its completely dead. Can't go into download mode or recovery mode! Volumes keys and power key not working. Please help!
Thanks ahead!

Was the phone completely stock, or was it previously SuperCID, rooted, etc?

No, I had rooted it previously and then unrooted it back because I couldn't go into the recovery mode then. Yes I was on stock!

If your phone is the AT&T version and you were rooted, you must have had SuperCID.
SuperCID + 3.18 RUU = brick (unless you are also s-off).
Sorry to say, you are now bricked. You missed my warning at the top of the General forum: http://forum.xda-developers.com/showthread.php?t=2181929
Your best bet know is to find a repair shop that can JTAG the phone.

redpoint73 said:
If your phone is the AT&T version and you were rooted, you must have had SuperCID.
SuperCID + 3.18 RUU = brick (unless you are also s-off).
Sorry to say, you are now bricked. You missed my warning at the top of the General forum: http://forum.xda-developers.com/showthread.php?t=2181929
Your best bet know is to find a repair shop that can JTAG the phone.
Click to expand...
Click to collapse
Okay sure I will go to the service center then! Thanks for your time

Why in the world would anyone who wants a rooted phone do an ota or ruu to a unrootable firmware? Patience us a virtue even with a phone.... Wait a day or two, read and read more.. then decide, easier than "woops I upgraded and now help me" threads like this entertain me, sorry but true
Sent from my HTC One XL using xda app-developers app

i have a similar issue, i just installed 5.4 elemental kernel and when it got done it through a bunch of errors then cut off and now wont come back on, im s-off was running latest viper rom, am i completely screwed or do i have options

jrlatta said:
i have a similar issue, i just installed 5.4 elemental kernel and when it got done it through a bunch of errors then cut off and now wont come back on, im s-off was running latest viper rom, am i completely screwed or do i have options
Click to expand...
Click to collapse
Plug your phone into your computer and see what comes up in Device Manager. If you see QHUSB_DLOAD, you're bricked. The JET tool might help you, otherwise it's jtag.

im bricked i guess, this blows, wonder what went wrong ive flashed that kernel before it went fine

jrlatta said:
im bricked i guess, this blows, wonder what went wrong ive flashed that kernel before it went fine
Click to expand...
Click to collapse
It's been happening. There may be some bug in recovery.

my computer has windows 8, the jet thing calls for linux or ubuntu, is there anyway to fix it with what i have

jrlatta said:
my computer has windows 8, the jet thing calls for linux or ubuntu, is there anyway to fix it with what i have
Click to expand...
Click to collapse
Make a linux boot disk/flash drive. It's easy.

ive gotta get a usb stick the dvd player isnt working, about how hard is it to set it all up and do, will i be up all night or is it a quick set up and job

I have tried connecting it to my PC and it says QHUSB_DLOAD in the device manager, what do I do? Can I fix it all on my own?

Sorry my friend but you're bricked. Sounds like you'll need a jtag repair to me.
Sent from my One XL using XDA Premium

ive got same problem but ive been suggested to try the jet tool too bad i dont have a clue as to what im doin with ubuntu

ive decided to create a guide for prepping an ubuntu usb stick for noobs to try unbricking. ill have it up within a few minutes to an hour depending on how many distractions occur. I will link here when I am done.
*EDIT*
As Promised: http://forum.xda-developers.com/showthread.php?p=40002934#post40002934
Guide to creating linux live Ubuntu for use with Jet.

[Q] Hard Bricked? Don't see how....

Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan

ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?

Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app

exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!

ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.

mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...

mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.

pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.

mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.

pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...

I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app

3 words: Dropbox Camera Upload.

exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app

iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.

I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app

phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off

anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app

31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question