Database Develop

[Q] HTC White Screen - Bricked?

I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot

Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?

chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!

debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App

rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.

debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App

Have you tried ruu'ing it?
Sent from my HERO200 using XDA App

Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.

Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?

SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!

Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.

Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47

While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img

unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.

debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.

unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!

debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?

obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!

Awesome! Makes me feel better trying different ROMs

Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.

Please help me!!!

26th July 2012, 04:44 PM #51
Member
Thanks Meter 1
Posts: 62
Join Date: Nov 2008
Location: Jersey City
MORE INFO >
hey guys,
thanks for the post and the info. I am hoping I can get some help. I recently upgraded to a new ATT - HTC Vivid. I guess I was impatient in wanting to root and flash ROM so I used the [TOOL] HTC Vivid All-In-One Toolkit V2.2 to "un-lock bootloader" and get root. Afterwards I realized the phone had/has old software/rom (no ICS beats audio etc) - I tried updating the software manually and it would not take - kept getting error messege. Then I got notification that ATT/HTC was trying to "push" the update to my phone but when I tried to install the update it would not work. I keep getting what looks like a dead android with chest open with red exclamation point. I tried a few times and still nothing. so after some research I came across this thread. I am still a "noob" at this I guess so I could really use some help, please. I believe I have to "re-lock bootlaoder" but I am confused as to how to go about this. for example, how do you, "TRY FLASHING THE WCXRECOVERY.IMG USING FASTBOOT FIRST?" - please help! lol like I said - I'm still a noob I guess
I tried the video but it only further confused me
Today, 04:16 PM #52
Member
Thanks Meter 1
Posts: 62
Join Date: Nov 2008
Location: Jersey City
MORE INFO >
please help!!!! I really need it. I tried using your tutorial to re-lock my Vivid and update ROM to ICS. I got through the first part where I re-locked the phone ut when I got to the part to "unlock" again before flashing recovery I get the "Unlock bootloader" screen and I use volume button to select yes and hit power button but that's it - it's stuck at that scree and will not go further. now my phone won't start normally if I try etc and I even got a red exclamation etc - Please help, I dont know what I did wrong but now I have no phone!!!!!
Thanks a bunch for any and all help

This should probably be in the General forum, not development...
If you pull your battery, then put it back in, then hold VOLDOWN button and the POWER button, do you get into Bootloader mode?
If you can, choose Fastboot mode, and then connect your phone to the PC. (I'm assuming you have the right driver(s) installed so you can issue Fastboot commands to the phone?)
If you've gotten that far, and want to re-lock your bootloader using fastboot, the fastboot command is:
"fastboot oem lock"
Run that in a command prompt window. Make sure you have navigated to the folder that has fastboot.exe, of course. Are you familiar with using command prompt?
Once your bootloader is relocked, you can re-start your phone into bootloader mode, and then flash your stock carrier's RUU using your PC... I hope this helps.

LaZiODROID said:
This should probably be in the General forum, not development...
If you pull your battery, then put it back in, then hold VOLDOWN button and the POWER button, do you get into Bootloader mode?
If you can, choose Fastboot mode, and then connect your phone to the PC. (I'm assuming you have the right driver(s) installed so you can issue Fastboot commands to the phone?)
If you've gotten that far, and want to re-lock your bootloader using fastboot, the fastboot command is:
"fastboot oem lock"
Run that in a command prompt window. Make sure you have navigated to the folder that has fastboot.exe, of course. Are you familiar with using command prompt?
Once your bootloader is relocked, you can re-start your phone into bootloader mode, and then flash your stock carrier's RUU using your PC... I hope this helps.
Click to expand...
Click to collapse
thanks a bunch!!! I'm still a "noob" I guess and I will re-post in General. In the meantime, I can get into Bootloader mode but I am already "Relocked" - from what I understand at this point I was supposed to "Unlock" again and flash recovery using "unlock bin" but at the unlock bootloader screen on my phone after I select yes and press power button nothing happens. my phone freezes at that ponit. I dont know what to do now. any help is greatly appreciated.

rsuarez74 said:
thanks a bunch!!! I'm still a "noob" I guess and I will re-post in General. In the meantime, I can get into Bootloader mode but I am already "Relocked" - from what I understand at this point I was supposed to "Unlock" again and flash recovery using "unlock bin" but at the unlock bootloader screen on my phone after I select yes and press power button nothing happens. my phone freezes at that ponit. I dont know what to do now. any help is greatly appreciated.
Click to expand...
Click to collapse
I wonder (since you are already re-locked), if you should consider flashing your phones stock RUU (so the phone will be back to stock).
Then unlock your bootloader via HTCDEV again...
Then you can flash a custom recovery, then you can do a nandroid backup of your phone... then you can do your wipes and install a rom?

thanks again for responding, much appreciated. I wish I knew how to flash back to stock. I'm at a loss or stuck right now.I just found the stock RUU and I'm trying to download it but once I get it how do I flash it back to stock? That is actually what Ive been trying to do. You see I recently upgraded to the Vivid and "unlocked bootloader" and "rooted" before I realized I had old software (no ICS - beats audio etc). So after some research I read that I had to "re-lock" so that is what I was trying to do before I got stuck. what do you think I should do fromhere? I'd really like to at least get my phone working again with stock even, just working.
thanks again,
Rafael
LaZiODROID said:
I wonder (since you are already re-locked), if you should consider flashing your phones stock RUU (so the phone will be back to stock).
Then unlock your bootloader via HTCDEV again...
Then you can flash a custom recovery, then you can do a nandroid backup of your phone... then you can do your wipes and install a rom?
Click to expand...
Click to collapse

rsuarez74 said:
thanks again for responding, much appreciated. I wish I knew how to flash back to stock. I'm at a loss or stuck right now.I just found the stock RUU and I'm trying to download it but once I get it how do I flash it back to stock? That is actually what Ive been trying to do. You see I recently upgraded to the Vivid and "unlocked bootloader" and "rooted" before I realized I had old software (no ICS - beats audio etc). So after some research I read that I had to "re-lock" so that is what I was trying to do before I got stuck. what do you think I should do fromhere? I'd really like to at least get my phone working again with stock even, just working.
thanks again,
Rafael
Click to expand...
Click to collapse
OK. So since you are relocked, you should be able to flash your stock RUU.
The RUU is an EXE file. Just run it on your PC (with your phone, in fastboot mode, connected to the PC). It will detect the phone and perform the flashes and when it's finished, your phone will be like stock again.

Yeah...just use ruu like you would any other pc program...it will walk you through the steps in the program...
As for beats...I had beats audio on stock gingerbread? Confused why you don't...I only had gingerbread for a couple days before upgrading but I remember seeing the beats icon in notification...
Sent from my HTC PH39100 using Tapatalk 2

I tried what you said and I got an error message (error 104) and it would not update/flash the ROM. I am stuck.
and when my phone restarted I ended up with the red exclamation point in a triangle again. any more ideas? I hope I did not "brick" my phone.

rsuarez74 said:
I tried what you said and I got an error message (error 104) and it would not update/flash the ROM. I am stuck.
and when my phone restarted I ended up with the red exclamation point in a triangle again. any more ideas? I hope I did not "brick" my phone.
Click to expand...
Click to collapse
What is the exact file name of the RUU you are using?
Also, when your phone was working, what was the stock base that it had? Was it Gingerbread? or ICS?
From a quick google search, it seems Error 104 is "wrong hboot version". Interesting... I remember mine said that when I was trying to flash the old GB on my phone which had already been upgraded to ICS.

mg2195 said:
Yeah...just use ruu like you would any other pc program...it will walk you through the steps in the program...
As for beats...I had beats audio on stock gingerbread? Confused why you don't...I only had gingerbread for a couple days before upgrading but I remember seeing the beats icon in notification...
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I tried the old ATT RUU without ICS which is what I had originally and it did not take. I got an error message (error 104). I also did not have beats audio surprisingly enough when I first got the phone which is how I realized I did not have the new/current ATT ROM ICS.

LaZiODROID said:
What is the exact file name of the RUU you are using?
Also, when your phone was working, what was the stock base that it had? Was it Gingerbread? or ICS?
From a quick google search, it seems Error 104 is "wrong hboot version". Interesting... I remember mine said that when I was trying to flash the old GB on my phone which had already been upgraded to ICS.
Click to expand...
Click to collapse
name of RUU I tried: RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
and it was originally Gingerbread
thanks guys

We really need a mod to move this to the "Q&A" section...
Anyways assuming your on completely stock gingerbread you can call this number *#*#682#*#* that will do a force update...vant be root tho, and can't have an unlocked bootloader
Edit...discard this post just read above about the red exclamation mark...can you still get to hboot? If you can...can you verify that it says "re-locked" at the top?
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
We really need a mod to move this to the "Q&A" section...
Anyways assuming your on completely stock gingerbread you can call this number *#*#682#*#* that will do a force update...vant be root tho, and can't have an unlocked bootloader
Edit...discard this post just read above about the red exclamation mark...can you still get to hboot? If you can...can you verify that it says "re-locked" at the top?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I can't even get to the dialer.
yes, I can still get to hboot, I think. or bootloader and it does say "RELOCKED" at top.

Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Do this ^^^
All that you need to do it boot n hboot then select fast boot and when you plug it in the pc it should say USB next to fast boot then just run the ruu file and it should hook you up with stock ics

mg2195 said:
Use this ruu...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe this should update you to stock ics assuming you can still get to hboot...and from their fastboot...
-ill be back in about an hour...gotta go to church..hopefully your problem will be solved...if not ill be here to help as soon as I get home
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I tried running the RUU and it got stuck at 34% for a while. I unplugged the phone to attempt running the RUU again and now all I can get is black screen with HTC and 4 exclamation points in the corners of the screen - please help!!!
please dont tell me I "bricked" my phone.

Can you still get into hboot ? I wouldn't unplug the phone while its doing stuff I had that issue and just stopped the program and tried again , it takes some time to finish approximately 10 min so just let it do its thing . Just fyi

Bigtjmc said:
Can you still get into hboot ?
Click to expand...
Click to collapse
not anymore
I keep getting the HTC screen with exclamation points in the corners...

Pull the battery and try again . If that don't work then hopefully some of the more experienced guys can help.
---------- Post added at 07:46 PM ---------- Previous post was at 07:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1672425
That may help

The exclamation marks are a failed ruu...try running the ruu again...it should still work (I think) if not then try pulling the battery and trying again...
Yeah...next time do not pull the plug, I'm sure its still saveable tho..I've had failed ruu flashes before and it mentions something about exclamation marks in the corners, so Im pretty sure the ruu has a fix for it...if I get time ill see if I can get that info from a ruu...
Sent from my HTC PH39100 using Tapatalk 2

[Q]Possible brick after failed RUU install?

First of all I experimented with some custom ROMs. But after a while I wanted to go back to stock and tried to install a RUU I already used succesfull. But during the installation it hung up and I had to cancel it. And now it is impossible to use everything. The phone just show me the black background with the HTC log and four triangles in the corners. I can't use the bootloader, go into recovery or use adb, first of all because my PC doesn't recognize my phone anymore. Already tried to use adb and some tools like the AIO bye anders and the XL Multi tool. I also tried the Forum search for bricked stuff, but nothing worked so far. Any idea how to fix it?
And please excuse my bad english. It was a long day. ^^

In pretty sure that's completely bring, idk how yous brick the sxl, ivebdonebso much stuff to mine and I wonder how mines still perfect, you might wanna look into some articles about jtag!

Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.

Mr. Despair said:
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Click to expand...
Click to collapse
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app

I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!

ricky310711 said:
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
Click to expand...
Click to collapse
before jtag , if the phone is under 2 years , always try to send it in for repair they cant boot up the device , then they cant see if it is unlocked

Very true Anders! Just hope he has warrenty!

anders3408 said:
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
Click to expand...
Click to collapse
When yo flash RUU the phone goes into kind an own bootloader. The black screen with a silver HTC logo. This is the only thing i get into, but with four triangles, in each corner of the display. It doesn't matter what I do, tried to pull the battery, use the key combo, adb/fastboot etc. When the phone starts, it shows directly the screen described above.
Sent in for repair today and just can wait now. But thanks guys for your replies.

How did it go? Did they fix your problem? Also this happened to me, I discovered that the cause was because installing the ruu relocks the bootloader before it wipes the Rom, and mine failed just before wiping the Rom,I had a custom Rom installed so it would not boot into it because the bootloader was locked so I re-unlocked the bootloader then the phone booted up normally!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[Q] HTC ONE bricked

A friend of mine has a T-Mobile HTC One and he bricked it, he asked me for help, knowing I'm very good with tech and android. But the thing is that I know everything but from Samsung, I always try to read a lot and learn from new devices to fix them or even try something because I'm always asked for help from my family, sure you guys know about that, but sadly I'm in finals and I'm barely sleeping and I've read a little but not enough but need I to help him so that's why I ask you guys for help urgently. Here are the things I know:
The phone is trapped in a bootloop after the Cyanogenmod logo and restarts itself after a minute
It is S-ON but unlocked
It is the M7_UL T-Mobile model
It is on HBOOT 1.56
The Radio is on 4A.24.32.63.09
The OS 4.19.531.10
It can still enter recovery and is recognized by my PC
From what I've read that has been a little bit, I can restore it completely with a RUU (kind of like a .tar in ODIN for Samsung), but it has to be Relocked and in other sites it says that it has to be S-OFF, needless to say that I don't know what tools to use and then I've seen that that Hboot 1.65 is not supported and well right now I have to create my SQL project, sorry to ask you guys as I hate when other do it just to not read but I swear this is not the case.
Help to fix this will be very appreciated

*GalaxyDev* said:
A friend of mine has a T-Mobile HTC One and he bricked it, he asked me for help, knowing I'm very good with tech and android. But the thing is that I know everything but from Samsung, I always try to read a lot and learn from new devices to fix them or even try something because I'm always asked for help from my family, sure you guys know about that, but sadly I'm in finals and I'm barely sleeping and I've read a little but not enough but need I to help him so that's why I ask you guys for help urgently. Here are the things I know:
The phone is trapped in a bootloop after the Cyanogenmod logo and restarts itself after a minute
It is S-ON but unlocked
It is the M7_UL T-Mobile model
It is on HBOOT 1.56
The Radio is on 4A.24.32.63.09
The OS 4.19.531.10
It can still enter recovery and is recognized by my PC
From what I've read that has been a little bit, I can restore it completely with a RUU (kind of like a .tar in ODIN for Samsung), but it has to be Relocked and in other sites it says that it has to be S-OFF, needless to say that I don't know what tools to use and then I've seen that that Hboot 1.65 is not supported and well right now I have to create my SQL project, sorry to ask you guys as I hate when other do it just to not read but I swear this is not the case.
Help to fix this will be very appreciated
Click to expand...
Click to collapse
First thing, try this
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
Then reboot.
(you may need to try 2 or 3 times to get it right)
What recovery do you have?
CWM has problems with 4.4.2.
The rom bootloops
Install twrp 2.6.3.3
Make sure it's for your phone.
If that doesn't work, do you know how to post a fastboot getvar all.
Sent from my HTC One using Xparent Skyblue Tapatalk 2

bored_stupid said:
First thing, try this
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
Then reboot.
(you may need to try 2 or 3 times to get it right)
If that doesn't work, do you know how to post a fastboot getvar all.
Click to expand...
Click to collapse
Yeah I've tried that. The thing that I forgot to tell is that when I go into Recovery mode it shows all partitions in 0mb including Internal Storage and says it doesn't have any OS installed although the Cyanogenmod Logo appears at startup

Find stock recovery for Tmobile. Flash it. Factory reset from bootloader menu and reflahs custom recovery. You should be ok to proceed
sent from my mobile device

Thanks!
SaHiLzZ said:
Find stock recovery for Tmobile. Flash it. Factory reset from bootloader menu and reflahs custom recovery. You should be ok to proceed
sent from my mobile device
Click to expand...
Click to collapse
thanks!! it actually worked and it booted right up, you just saved me lots of time to work in my project. Time to continue really thanks

Red Triangle Stock Sense 6 update

Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.

Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.

SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.

What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?

Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....

mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port

alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?

mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)

Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse

Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.

alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?

Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence

alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.

Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia

akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?

kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.