Develop Bugs

[Q] Bricked Desire HD

I have a Desire HD, rooted with Visionary, ENG S-OFF, Radio S-OFF, Super-CID and SimUnlock'd, I installed ClockworkMod using ROM Manager and chose to boot into recovery, the phone now doesn't boot whatsoever, when turning on it vibrates 3 times and the amber LED flashes continuously about every second. If I hold down and press power, the phone vibrates 5 times and a green LED flashes instead, but nothing on the screen. Back and Power does the same as turning it on normally. When plugged into USB, my computer searches for the Qualcomm CDMA Technologies MSM driver which it cannot find...
Does anyone have any idea how I can get the phone into recovery mode, fastboot mode, or any other mode where I can flash a RUU?
Thanks, Jordan.

:::im not sure about this, and whatever happens, im not responsible, this is entirely your decision:::
But if i was in your shoes, given that it doesnt want to open at all but just flashes (the LED), ... , i would take the battery out and try again.
But if this keeps happening, then you should sent it to HTC.

Take your battery out, then try and flash into recovery mode
If you get into recovery mode then either install a new Rom or if you backup your Rom restore it
Sent from my Desire HD using XDA App

Taking the battery out and putting it back in does nothing, left the battery out for hours, nothing. No way to get into recovery...

If u flashed a 2.x.x.x version of CWM u could try use the bug thats now corrected in 3.x versions.
By taking the battery out then plugging USB in to charge and replace the battery. that used to start my DHD into recovery. if u flashed the 3.x.x..x CWM it wont have that bug.

^it's actually a feature which was removed...^
Sent from my Desire HD using XDA App

As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).

b_bhavu said:
As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).
Click to expand...
Click to collapse
Which of course works only if you can get into fastboot.
@OP: If you connect your phone to the computer and turn it on, does the computer recognise it?

as he said, windows searches for "Qualcomm xxx"-drivers.
i had a similar issue with my nearly-bricked hd2 some months ago.
but you know: hd2 and dhd aren't really the same when compared on bootloader level
DN41

Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?

JordanT92 said:
Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?
Click to expand...
Click to collapse
does your phone carrier offer extended warranty? as in full coverage?... basically i did this once.. my gf got pissed (as they do).. and basically tossed her phone towards me lol missed completely.. bounced off a wall, then off a metal heater, and then the floor.. thus .. screen completely broken.
We went onto our carriers website, added a 3 dollar a month full coverage warranty (12 month commitment). and after 2 weeks sent it in .. fully repaired 2 week later ...

[Q] htc one x bricked. not charging. not booting. only bootloader

usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed

http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!

kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...

FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up

hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)

Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA

Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.

Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/

Help: hard bricked from Stock Rom?

Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!

Forunke said:
Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!
Click to expand...
Click to collapse
Okay, did you flash the ruu's stock boot.img and system recovery the relock the bootloader before flashing the ruu?
---------- Post added at 02:37 AM ---------- Previous post was at 02:24 AM ----------
sorry i misread it. You flashed a backup of your stock rom and flashed the boot.img. i would recommend trying to flash the original ruu if youre getting errors. The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc

XxJibblesxX said:
The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc
Click to expand...
Click to collapse
I hope that's the problem, but I can't imagine my phone using up 70% of the battery plus the usb hub power in about half an hour.
...this all seems to me like there's a hardware fail (which I really don't want to) as the system booted and then crashed into brick mode.
I'm not home tonight but the phone is on usb and tomorrow I'll try the tool and report my findings
Edit:
Ok, the phone spent 6 hours plugged into the pc and until now it was plugged into the wall but nothing. It seems to be completely dead -.-
Tried the batch file but there's nothing much to try when I can't even get into fastboot. The phone simply won't react to anything...
I will send it back as it's only about a month old and hope the warranty will fix it.
There is a stock rom with stock kernel on it so I hope they don't bother about the bootloader beeing unlocked.
But what I think is that there is a serious hardware problem. As I continued to read through other posts I realized that I had the same audio problems (stuttering and slowing down of the music) like some others...
If HTC tells me something about what caused the problem I'll post it here.
So far thanks for your help

Need some help - possible defective hardware?

First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...

You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4

dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.

This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.

wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...

US Unlocked stuck in bootloop. Unable to boot into recovery/download.

Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you

bmx4lfe said:
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
Click to expand...
Click to collapse
Hold down the power button and vol down until your phone reboots. It'll take 20 seconds or so, and the capacitive button lights should flash until it reboots.
That should take you to download mode where the RUU.zip on your SD can be flashed.
If that doesn't work, try power + vol up + vol down, then switching to power + vol down when the screen goes black. I think I remember having to do that once when I first got the 10 for a different problem, but it could have been a different device