Database Info

[Q] HTC Aria will not boot if plugged in

EDIT: Wrong category, sorry. I'm new.
Rooted Aria/Liberty won't turn on if it's plugged in (wall charger or USB). The orange charging light is on and the screen is lit but black. The menu buttons do not turn on. I have to remove the battery after unplugging it for it to turn on.
The phone is rooted and the problem is consistent no matter what ROM I use. I believe it is a problem with the bootloader, but I'm not very advanced with these things.
I rooted the phone with Unrevoked and whenever I boot into recovery mode it says "Revolutionary CWM v4.0.1.4."
Any suggestions on how to make this problem go away? I know it's minor, but it is my mother's phone and every time I'm on the phone with her she complains about it.

The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!

juzz86 said:
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
Click to expand...
Click to collapse
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.

ellaizee said:
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
Click to expand...
Click to collapse
Tried this one mate?

juzz86 said:
Tried this one mate?
Click to expand...
Click to collapse
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.

ellaizee said:
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
Click to expand...
Click to collapse
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704

glevitan said:
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
Click to expand...
Click to collapse
You are MAGICAL. Thank you so much! And thanks to juzz86 for the suggestions as well.
I used fastboot to flash the recovery and now it does the normal battery image when the phone is off and charging.

No problem. When that happened to me, I panicked but after a couple of google searches I came across that...glad you solved it.
Sent from my Inspire 4G using XDA

All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
hahaha sorry for that. As u can see, I realised after writing it and erased it, but you probably saw it first.....

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!

juzz86 said:
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
Click to expand...
Click to collapse
Even in UK they use mate a lot....but it is no defense for me...I am in Argentina... lol

[Q] Did official Jelly Bean update, stuck in QHSUSB_DLOAD

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.

Black screen boot, can't detect EMMC Partitions.

Hello,
In a last ditch effort to try and get an aokp rom on my one x sooner rather than later I tried running my telus RUU and returning to stock so I could then reunlock the bootloader and get to flashing however things did not go as planned and now I am stuck in that black screen that gets power but nothing boots up (no light, black screen)
So Here's everything I've done:
First off I had the Stock Telus 4.1 OTA installed when I started all this.
unlocked bootloader using htcdev installed TWRP 3.3.3.0 which obv did not work as I had 4.1 OTA, flashed 3.3.3.1
Installed custom rom yay!
Discovered I could not use aokp roms due to Touchscreen FW update in 4.1 OTA
Downgraded Hboot to 1.09 using Jet which got me bricked
Used unbrick thread to get unbricked
Still no AOKP D:
modified my mmcblk0p23 from 3.17.xxx,xx to 1.00.000.00
Ran RUU.
RUU claims to have completed successfully but phone is now in black screen, no power light
Does show up in linux as Bus 003 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) but I cannot detect any emmc partitions.
Whoo, that was a lot of typing. If anyone has any ideas as to anything I can try, I'd be grateful indeed!

This doesn't look to good might of needed your phone up if you can't get those partitions out....I know you did your reading and had an understandig so I feel bad looks like you need jtag service..... Go to mobiletechvideos.com and maybe you could ask them about s off while you're at it

a box of kittens said:
This doesn't look to good might of needed your phone up if you can't get those partitions out....I know you did your reading and had an understandig so I feel bad looks like you need jtag service..... Go to mobiletechvideos.com and maybe you could ask them about s off while you're at it
Click to expand...
Click to collapse
I'll just contact HTC and explain what happened. It's weird for an RUU to kill the phone especially if it said it completed successfully. if I need to pay to have it repaired then so be it I guess. Alternatively, I could bring it to telus and tell them running the RUU bricked my phone. I wonder if they can tell the bootloader was unlocked while it's in this state.

exad said:
I'll just contact HTC and explain what happened. It's weird for an RUU to kill the phone especially if it said it completed successfully. if I need to pay to have it repaired then so be it I guess. Alternatively, I could bring it to telus and tell them running the RUU bricked my phone. I wonder if they can tell the bootloader was unlocked while it's in this state.
Click to expand...
Click to collapse
Since its completely dead the people there will not be able to tell what actually happened unless they plug into their specialized machines at HTC and see what got corrupted...so its up to you and how you feel you should handle this

a box of kittens said:
Since its completely dead the people there will not be able to tell what actually happened unless they plug into their specialized machines at HTC and see what got corrupted...so its up to you and how you feel you should handle this
Click to expand...
Click to collapse
I called HTC. They told me they'd charge to fix it and they'd have to replace the motherboard so they told me my carrier would probably do it for cheaper and faster so I went to telus and they replaced it for free since its only a week old

exad said:
I called HTC. They told me they'd charge to fix it and they'd have to replace the motherboard so they told me my carrier would probably do it for cheaper and faster so I went to telus and they replaced it for free since its only a week old
Click to expand...
Click to collapse
I'm glad it worked out for you now go enjoy some team venom

a box of kittens said:
I'm glad it worked out for you now go enjoy some team venom
Click to expand...
Click to collapse
lol Team venom's pro choice but I am more excited to try out 4.2 which I could not do previously as I had the 4.1 ota! WOOHOO!! Just flashed jellybam 5.2 SO SEXY

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.

OTA Update turns into Hard Brick

I rooted my Htc One X, and things went array at that time, but ended up flashing a miui rom. Eventually tried to flash other roms, and they never worked, I did everything perfectly, but no response.
I went ahead and unrooted and relocked the bootloader, and was back on stock rom for a while and gave up because I couldn't unlock the bootloader once again. So today I did an OTA Update because it had been persistently annoying me, and it ended up bricking my phone. Hard brick, can't boot into bootloader...
Previously, I have done this OTA Update and it worked, but I would try to root phone and ended up factory data wipe, but no brick previously.
What's different in this situation? What can I do?

There are (unfortunately) numerous threads on this problem. It seems to happen if you take the jelly bean update with supercid. There is some bug that causes the update to crash and corrupt hboot. No one is sure why. I'm not sure if anyone has been able to fix it except via a jtag repair. You might try the JET in the Development forum.
Next time don't take an OTA when rooted. It's never a good idea.

iElvis said:
There are (unfortunately) numerous threads on this problem. It seems to happen if you take the jelly bean update with supercid. There is some bug that causes the update to crash and corrupt hboot. No one is sure why. I'm not sure if anyone has been able to fix it except via a jtag repair. You might try the JET in the Development forum.
Next time don't take an OTA when rooted. It's never a good idea.
Click to expand...
Click to collapse
Jtag is confirmed to fix this type of brick
Sent from my VENOMized HoxL

I had tampered flag set but locked boot loader and HTC repair depot replaced/fixed phone free.