Rooted my Incredible yesterday...with relative ease...some very helpful guides out there.
After searching a little...I can't find anything similar to my issue, and the pieces I can find don't piece together for me.
Was accessing hboot (power plus volume -) this morning and accidentally hit the power button to select "fastboot", rather than the "recovery" option i was wanting to get to to make another backup since I had added a few apps after my root.
My phone booted into froyo without any issue...and all my rooted apps worked fine (mainly wireless tether...the main reason I rooted). I shut down the phone and attempted to access hboot again...but got 5 vibrates and a green blinking led, with a blank black screen.
Pulled the battery...and let the phone boot normally (which I was hoping for since I thought I may have bricked it) and all is well...still with root applications working fine. I have tried hboot again with same result (5 vibrates and green flashing led), so I have let the phone stay with froyo for fear that if i screw around with it too much I may brick it after all.
Am I over-reacting to the lack of hboot? Suggestions for a fix are appreciated!
This is wierd, the only time ive heard this prob is when someone tries to flash a rom and then this happens. Sry man i have no idea its strange
Sent from my ADR6300 using XDA App
Download Rom Manager if you dont already have it a then install CWM recovery through it. It just sounds like it didn't install correctly the first time. That usually works for me when I get the problem of only being able to get into HBoot and Fastboot.
Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .
I defy you to be bricked the 2 days. Put in office the night the morning was completely blocked with the LED flashing green. I reinserted the battery and then turn on nos. I installed cynogem 7.1. By connecting to a PC is recognized for 2 seconds and then disconnects. I tried mcgiver mode but nothing is ever disconnected after 2 seconds. The battery is charged.
What can I do? help me please
Sorry for my english
Help me please
Try installing Froyo Official [don't use custom ROM until you get back to normal state]
and as you are saying, it disconnects after 2-3 seconds, probably your battery is done [not sure but you may check another battery]
so Install Froyo Official 2.2 [from Defy Android Development section] & hopefully you'll get your phone back in action.
PS: Defy can't be dead as far as it got locked bootloader
I have tried with other battery on a shop but don't turn on.
Try using some Universal Charger to charge your battery [or buy new one]
otherwise Best option would be to try it on some other PC, or change USB slot but trying on different PC will be good.
Hey i am having a similar problem. i just put CyanogenMod 7 on my defy and went to install the Google apps. All went good then rebooting i am now stuck on the Motorola logo. The led lights are not coming on it just sits there frozen. i have tried getting it into the boot menu and to use RSD lite but nothing is working. Please help as if freaking out.
1. Pull the battery, wait, and reinsert
2. Push and hold Volume Down button, tap the power button, while still holding the volume down. (This will boot you into the stock recovery)
3.Now, push both Volume Up, and Volume Down buttons to allow for more options than, just the triangle screen.
4. From Stock recovery, Wipe and Factory Reset.
5. Reboot once it is finished wiping
That's all I can say.
If still not work, head back to Quarx's CM7 thread & mention your problem there.
Just make sure you followed all directions properly.
PS: CM team have not officially released any ROM for DEFY, so this is MODs work, ask them further for any help.
Best of Luck
all good now after a hour of yelling at the phone i got boot loader to work.
Mr_hell said:
all good now after a hour of yelling at the phone i got boot loader to work.
Click to expand...
Click to collapse
Congratulations,
Take Care
Today i have tried with a new battery charced completely but the defy unplug from pc after 2 second no led.Help me please
Today the cell connected to pc has a white led but pushing the power and volume up is recognized in rsd lite as blank omap360 but starting flash at 67% the cell is disconnetted. Naturally the process fail .Help fo my defy please
Hi,
I've got a HTC One x, which worked fine untill i flashed it with Cyanogenmod.
To start from the beginning.
I never liked the HTC Sense stuff to much, so i did with my HOX what ive done with all my other android phones. I unlocked it and installed Cyanogenmod. When i did that i started having stability problems, suddenly acore stoped, then gmail stoped and so on.
So i decided i wanted to try another rom, without much luck. After fidling around with it for a couple of days, it started behaving strangely.
Suddenly it could wouldnt turn on after beeing powered down, i had to leave it for days, then suddenly it would pop back on when left connected to a computer for a while.
I RUU'ed the phone, going back to HTC Sense, still giving me acore and other application errors. Then i installed a another ROM ( Jellybean ), and when i woke up one morning the phone was dead. It would not boot, not in normal mode, not into recovery, nothing. Ive tried all the tricks in the book, volum down + power, volume up&down + power, just power, just volum down and so on.
Ive been googling alot trying to figure out if the phone is beyond repair, or if there is any hope left. I noticed one day when fidling with it that when i connected to my windows 7 machine, the computer made a "USB CONNECTED sound". i looked in the device manager section, and there i see a unknown device called APX. I unplug the phone and it goes away, so i google and find that this is some low lever mode on the phone. My hopes are that this is a way of flashing some sanity back into the phone.
I found some APX drivers lying around on the net, and now it identitfies itself as "NVIDIA USB Boot-recovery driver for Mobile devices", not that this helps my in any way.
I read somewhere that you can use nvflash, but its not giving me much info.
Soooo....i have a phone which is pretty much dead, except for entering into APX mode ( the screen is black as if the phone is dead, no leds, no nothing ). Anyone have any smart ideas to how i can get the phone back to life ?
Nope. If you search this forum, the only APX advice I've seen is to drop the phone. Actually serious. (Don't do that)
Anyway, looks like you'll be returning it and hoping it gets fixed without them figuring out that you broke it.
hey do you already solve this problem ?? i solved mine by pressing volume + then plug the charger .. wait for sec. a red light will apear in your phone and it will charge.. charge it for atleast one night or for an hour. then try to boot in fastboot.. when you boot in fastboot flash RUU file or if you have a custom recovery try to flash a custom rom. ) press thanks if you helped you . )
---------- Post added at 05:11 AM ---------- Previous post was at 05:01 AM ----------
hey do you already solve this problem ?? i solved mine by pressing volume + then plug the charger .. wait for sec. a red light will apear in your phone and it will charge.. charge it for atleast one night or for an hour. then try to boot in fastboot.. when you boot in fastboot flash RUU file or if you have a custom recovery try to flash a custom rom. ) press thanks if you helped you . )
contact xmoo he might be able to help, so far all i can tell you is that your phone is dead. htc should fix it if you act stupid and say it stopped working overnight.
Okay so here's what happened. I unlocked my device just fine, and attempted to install a ROM, didn't work, So i decide I'm going to try to install cyanogenmod. I go this (wikiDOTcyanogenmodDOTORG/w/Install_CM_for_a5 )wiki tutorial [/URL] and I attempt to flash clockworkmod recovery via this link (builderDOTunstableappsDOTCOM/#/latest/clockworkmodrecovery/a5) When i flash, it installs. But then upon booting I get the app for developement only screen, and it's stuck showing my battery charge screen, with the orange charge light. Anyways I can't boot using the power down volume combo. I'm currently waiting on the battery to die so I can reflash the stock recovery, because fastboot won't recognize the device when I plug it in, even though my computer makes the device connected tone. So should I just wait until the battery dies? Or is there something else I can do?
Any help will be appreciated, thanks
Solved
I actually solved my problem. I waited for the phone to die, powered it on normally. Then to reset the device and held the power and up button as soon as the screen went black hit down on the volume and got into my bootloader.