[Q] Did official Jelly Bean update, stuck in QHSUSB_DLOAD - AT&T, Rogers HTC One X, Telstra One XL

So, for some weird reason, after RUUing my phone, updating once to a newer version, then trying to update again for the Jelly Bean update (all within the phone on the stock ROM using the official updater and etc) my phone decided that it felt like entering QHSUSB_DLOAD mode right after the update was done installing, like it didnt even boot once, it just straight crashed to it.
Im kinda lost as of what to do, I already tried the fix on the website unlimited.io and that didnt do it. Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
The phone is a HTC One XL (obviously) hboot 1.09 (at least before the official updates that crashed my phone) from Rogers.
Please help!

Sam.Lambert said:
So, for some weird reason, after RUUing my phone, updating once to a newer version, then trying to update again for the Jelly Bean update (all within the phone on the stock ROM using the official updater and etc) my phone decided that it felt like entering QHSUSB_DLOAD mode right after the update was done installing, like it didnt even boot once, it just straight crashed to it.
Im kinda lost as of what to do, I already tried the fix on the website unlimited.io and that didnt do it. Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
The phone is a HTC One XL (obviously) hboot 1.09 (at least before the official updates that crashed my phone) from Rogers.
Please help!
Click to expand...
Click to collapse
This may be a stupid question but are you sure your phone is rogers... I've only heard of hboot 1.11 for rogers correct me if wrong...head over to the unbricking thread myrder grim or shadow will probably be more than happy to you help you because I think you're still fixable

Did you happen to have superCID?
HTC one s users who had supercid and took the ota bricked somehow.. the one x and one s are nearly identical

absolutelygrim said:
Did you happen to have superCID?
HTC one s users who had supercid and took the ota bricked somehow.. the one x and one s are nearly identical
Click to expand...
Click to collapse
Yes I have SuperCID, this might be why.
And yes my phone is definitely from Rogers, the phone shipped with hboot 1.09 but the updates most probably brought my to 1.11. I'll go see in that thread if anything can be done, thanks!

If your phone is not bone-stock, you should not be taking an ota. Too late for the OP, but maybe anyone else reading this will see why.
Sent from my Nexus 7 using Tapatalk HD

iElvis said:
If your phone is not bone-stock, you should not be taking an ota. Too late for the OP, but maybe anyone else reading this will see why.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have a replacement coming in for a dead speaker on the phone. Let's hope this little problem won't prevent me from having my phone accepted for the replacement.

Sam.Lambert said:
Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
Click to expand...
Click to collapse
You are in Qualcomm download mode, meaning your hboot is f_cked. The only thing that can be done is to re-partition using a Linux computer (see unbricking thread in General). Other than that, you're pretty much screwed.

Related

[Q] HTC Sensation rebooting after root

Hi all, I am sorry if this is already posted or answered but I spent all day yesterday searching and reading and cannot find the answer.
I have 2 Htc sensations that I messed up some how and would be very grateful if you could help me with them.
Phone 1 has been rooted for a long time and in preparation for ICS I flashed T-mobil: Download 3.32 from here
http://forum.xda-developers.com/showthread.php?t=1459767
and now the phone works but it will randomly reboot. I have wiped the cache, delvak cache and battery stats.
I am completely lost please help.
Phone 2 I think I may have messed up real bad here is what I did to it.
I rotted it from here
http://forum.xda-developers.com/showthread.php?t=1192300
I got to step 2 sub step 6 and now it continuously reboots it starts with the white screen with HTC on it then goes to another white screen that says HTC Quietly brilliant for a second and repeats.
Please help me yes I am a noob and grateful for any help.
Wow that was a fun ride (not really) it appears I did not flash the PG58IMG file correctly, after I flashed it correctly I got Insert Coin installed and so far it seems that they both are working. only time will tell.
Thanks anyway guys.
A.J.
If you are trying to install the latest firmware and having the HTC log restart problem. Try to super wipe on the recovery and install first the 3.12 firmware.
HTH
Did you install supercid after root?
Sent from my HTC Sensation 4G using xda premium
Both phones are working fine but I have a new question, I can not get the voice dialer to work ie I long press the button on my plantronics bt and say call tom.
I have tried vlingo from the market and this fix
http://forum.xda-developers.com/showthread.php?t=1133246
but nothing has worked. is it just not working in Insert Coin rom?
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
which of the 2 phones you are talking about?
In a previous post you said that problem was solved, now what?
Also, it would be better to know what your bootloader says and what you were attempting to do before black screen.
area1509 said:
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
Click to expand...
Click to collapse
Sounds like a brick to me, but since the problem is unclear, it's possible to fix. I wish I could help but I don't understand your issue to be honest!
I had 3.32 on it with Insert Coin ICS and thought I have 2 so might as well restore one to factory setting that's when I tried to flash the 1.17 and it never started again.
T-Mobile HTC Sensation 4G
The other one is working so I am not messing with it.
I had the same thing happen to me and it was over for the phone. Took it in to tomo and told them it died and after I charged it and went to turn it on, bam, went black and never came back. They never got it to work either and replaced it for me
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
kualmente said:
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
Click to expand...
Click to collapse
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
mugetsu666 said:
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
Click to expand...
Click to collapse
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
No what's happened to him is what happened to me. It's like it gets fried or something. The screen goes black and u can't turn it on or get into bootloader. Tmobile told me when it happened it was dead and got me a new 1
kualmente said:
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
Click to expand...
Click to collapse
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
area1509 said:
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
Click to expand...
Click to collapse
Good luck mate. Just let us know if it worked

Bricked HTC ONE X AT&T

I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium
you cant get to hboot? 0.o
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope
sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.
so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??
lol
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Just pull the batte..... oh
jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X
modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.
No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA

Phone bricked after At&t update

So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Should have read this first:
http://forum.xda-developers.com/showthread.php?t=2181929
Sent from my One X using Tapatalk 2
No, I don't have neither..
iElvis said:
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
the whole process took awhile for me, felt like it rebooted a few times also. about 20 minutes i think, you could of got in a hurry during the process and messed it up. does the phone detect? maybe u can reruu?
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
The LED does not come on, believe me I have tried keeping it on the charger all night, with no success.
redpoint73 said:
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
Click to expand...
Click to collapse
I tried this, and nothing happened.. I will head to my nearest AT&T store soon to get a replacement hopefully.. I guess its not all bad though, I have been enjoying my Lumia 920 with Windows phone 8, but I am missing my Android!
iElvis said:
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
Click to expand...
Click to collapse
hrrsncrawford14 said:
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Click to expand...
Click to collapse
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
nmupparaju said:
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
Click to expand...
Click to collapse
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I'm sure it's the same thing.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I did get supercid, unlocked bootloader installed cm10 relocked bootloader, ruu to 2.20 used for few days, used update tool from htc website to update to jellybean, after using the tool phone never booted back , dead (I guess brick)
When connected to windows pc qhusb_dload shows up
nmupparaju said:
When connected to windows pc qhusb_dload shows up
Click to expand...
Click to collapse
You've got a brick. Sorry. It's not clear why this is happening, but once you're in that mode, you're done.

[Q] Did the JB ATT RUU brick my phone?

Starting with where I am now: my ATT One X is totally unresponsive. Power button held, Power plus either of the volume buttons held, nothing produces any response. When I plug it into a wall adapter, the charging LED doesn't light up. It is both looking and talking like a brick.
Here's how I got here, and I'm hoping someone may have some kind of suggestion .
I had been running Tachi91's original Sense JB ROM. TWRP recovery. I used the AT&T JB update RUU from HTC's site.
Before doing this, I rebooted to bootloader and re-locked the bootloader. After this, I seemed to be unable to reboot back into system, so I just ran the RUU while the phone was sitting in the bootloader (figuring that the first thing the RUU seems to have done in the past is reboot to the bootloader).
The RUU went through its usual lengthy, multi-reboot thing. No errors whatsoever, everything seemed totally fine. Clicked "Finish" at the end...and my phone's screen went black. I figured it was rebooting, but unless it's taken the past 40 minutes to reboot (which seems unlikely! ), something is obviously amiss. See beginning of post for what I've tried since and results.
Any suggestions?
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
...yeeeeah, total violation of item #1 on that list. And here I figured I was relatively safe with an RUU. Oops.
Thanks for pointing that post out to me. At least I know where I stand now! Better than sitting here making my thumbs go numb trying different power/volume combinations.
Why oh why do many people persist in thinking they don't need s-off??
Sent from my Nexus 7 using Tapatalk HD
Please help!
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
buy a jtag
Nicobesso said:
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
Click to expand...
Click to collapse
Could try the JET. Check the Development forum.

[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.

Categories

Resources