Develop Bugs

Desire will not start up, just keeps rebooting itself

Hi guys, first post for me here, im having major problems with my desire.
I was opening a zip file on my phone to change the font on it, and followed the instructions for a restart, upon restarting the phone the usual pink circle appeared in the centre of the screen (presumably because im on t-mobile), eventually this circle goes off, as it normally does, and i was expecting the t-mobile logo to appear as per usual, however the phone just restarted and the pink circle appeared again and kept doing this until i took the battery out the back to turn it off, when i turned the phone on again it just did the same thing.
I tried removing the sd card and the sim card but still made no difference. Im a bit of a noob at this type of thing so any help you can give me would be greatly appreciated.
Im a UK resident on t-mobile, im using a rooted phone.
I also tried a factory reset but this didnt work either, any help you can give would be a major help as i really miss my phone

Hi, try to do a full wipe trough recovery (hold vol down and power on), follow the onscreen instructions. If it doesn't work, try flashing the stock rom - t-mobile - http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_127570_signed.exe
post if you come across problems

sorry as mentioned before, i am a noob, what do u mean by flashing?

ooops, sorry and welcome to xda
first download the rom in the link, it is an official t-mo rom, then connect your phone with the PC, make sure usb debugging is on (settings\applications\development you should have a green thick). Then start the exe and follow the onscreen instructions. Unfortunately you might need a goldcard which is a bit more complicated , that is if you get an error.
are you sure your phone is rooted? If that's the case power down, then power on while holding vol down, then navigate to "recovery" by pressing volume down, when you enter recovery look for "wipe device" "factory reset" or "full wipe", do it and see if you are alright then
try the second method first, with the recovery

hi thanks for the reply, i tried doing the full wipe on the phone unfortunately that didnt work. When trying to run the rom it says it cannot connect to the phone and i cant get into the phone to turn on debugging as it wont load up. this to me seems like it might be terminal unless you experts have any other advice.

Sometimes, when flashing an update ZIP, the framework might be wrong for your ROM and cause it to go into a bootloop (which it appears yours is doing).
Flashing the stock ROM is probably the best way, just need to get the correct RUU for your phone, make sure HTC Sync is connected and then run the file. If you can't turn the phone on the get HTC Sync to connect, turn off the phone and turn it back on whilst holding the back button to get into FASTBOOT. Connect to your PC again and then once it says FASTBOOT USB try again and it should work

It worked!! Thank you so much for helping me out guys, i really appreciate it!!

[Q] SOS Can I save my Incredible? [SOLVED!]

SOLVED
So, I did a silly thing
I rooted my new Incredible using Unrevoked 3.21 and it worked like a dream. Super impressed with how easy it was compared to when I rooted my original Droid. I decided I wanted to run Cyanogen Mod, since I loved it on the Droid.
The mistake I made was thinking I could install like I did on my Droid - I juts downloaded Rom Manager and downloaded and told it to install the latest version. Now I know that was bad.
My phone now boots only to the white HTC Incredible splash screen and sticks. The only way to power down is to pull the battery. If I pull the battery, and boot using the volume + power button, it vibrates 3 times and the screen goes black.
If I plug it into my computer while it's stuck on the white splash screen Unrevoked will pick it up and start the push. I thought awesome, because it rebooted it back to the hboot screen -- but then it restarted again and stuck on the white splash.
Then I tried stoping unrevoked at the hboot screen and trying clear storage and i tried recovery when that didn't work. Pushing the power button to select the option makes the phone vibrate once and go back to the white splash.
Am I doomed? I tried a Froyo RUU and it can't find it via USB. I'm feeing antsy with no phone and a little nervous I wrecked my Incredible.

Hmm, I've heard there are ways to manually recover via USB, but I'm not sure of how to do it. Also, how long have you let it sit at the HTC screen. Many roms take about 7-10 mins on the first boot and may seem like they are frozen.

If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.

Maybe take a look at this.
androidforums.com/incredible-support-troubleshooting/187107-3-vibrates-no-recovery.html

Thanks, so now I can get into hboot - when I volume down to select 'recovery' it vibrates one and goes to the white splash screen again. Then, it goes black with white bars on the right and left sides

jensenist said:
If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.
Click to expand...
Click to collapse
Holding volume up and power enables Qualcomm diagnostics (vibrates three times). Pull the battery and put it back in then hold volume down and power. That should get you to hboot.
Sent from my ADR6300 using XDA App

Yea I've made it into hboot now, but it doesn't seem to do anything? It goes to the white HTC Incredible screen, or a black screen with two white bars.
Are the some zip files I should have on my SD Card?

Ok, I found this thread: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=806734
But the recovery file linked is a dead link?
EDIT: Think I found the file needed: http://www.dougpiston.com/files/Recovery/
in there. Trying to put that on the card now.

Update: I used the file from the thread I found and this time it actually came up withs ome prompts. once I opted yes, though, it went back to the white HTC Incredible screen.
Am I missing anything else? That recovery file is the only thing I've put on the SD card. Do I need any other images?

Call *611 and get a refurb. something happened. same thing happened to me. I flashed shadowrom(not blaming this rom) and instead of booting up i hear 3 beep, black screen flashing green notification light. only way to pull batt. then i try turn on, 3 beep same ****.. weird enough, i could plug it in, get a red light turn it on, and use it fine, i was s-off, this turned me to s-on somehow, and when i had the phone booted finally from having it plugged in, once rebooted, samed 3 beep, and if i tried turning it on while plugged in and pulling the cord before fully booting, it would do the 3 beep, i just got a refurb for this, just flash the signed PB31IMG.zip file to set it back to s-on and stock recovery...

I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.

If you have recovery working you're good to go

jensenist said:
I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.
Click to expand...
Click to collapse
Step 1: Download this file: http://www.mediafire.com/?n3bmd2bkz55k1b9
Step 2: Connect your phone to your computer.
Step 3: Save all of the files on your sdcard to a folder on your computer.
Step 4: Format your sdcard to fat32.
Step 5: Place the "PB31IMG.zip" file that you downloaded onto the sdcard in the bottom directory.
Step 6: Power down the phone.
Step 7: Hold the volume button down while pressing the power on button. (This will place you in HBOOT)
Step 8: HBOOT will find the file on the sdcard named "PB31IMG.zip" and ask if you wish to update with it. Answer yes. (It will start to load and restart HBOOT and scan for the file again, don't panic, let it do it's thing.)
Step 9: When it is finished it will ask you to reboot the device, press volume up to reboot.
Step 10: Remove "PB31IMG.zip" from the sdcard.
Courtesy of dadicus at http://forum.xda-developers.com/showthread.php?t=760306
I just cleaned it up a bit and made sure it works. This will revert your phone to complete stock 2.1 to include the recovery, radio, splash, etc, ready to receive the 2.2 OTA. After this, just run unrevoked again. Any problems/questions, let me know.

Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.

jensenist said:
Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.
Click to expand...
Click to collapse
Since you already did a restart, tried a battery pull? Detected in adb?
I read a quote once (forget from where), it's not doomed till it doesn't power on.

I haven't tried adb -- I'll have to wait til I get home. battery pull doesn't seem to make a difference. Buttons at the bottom vibrate as I run my finger over them and are responsive - just can't see anything on the screen :\

Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.

jensenist said:
Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.
Click to expand...
Click to collapse
adb is good to know. It'll let you edit your phone and manipulate it when it's connected to the computer. Very good if your screens broke, and it's quicker than just typing in commands on your phone. Assuming your device is detected, at least. Once you get it up and running, try the command
Code:
adb devices

Well it looks like it's detected. I'm at work, and while they block the USB ports so I can't do anything with the device it is saying "Hey you've connected something, it'll charge but you can't use it"
So hopefully when I get home I can ADB in and fix this nonsense.
I am a little confused why volume+power doesn't do anything, but oh well. Onward!

So I'm not super certain what I did. But I pushed volume and power until it booted, I now appear to be back to stock 2.2 thanks to the img PonsAsinorem linked -- but when I try and make a call it says verizon can't validate my phone.
They give a #8899 number to dial, but I want to ask here what's up before I call it and get an operator that's like "YOU ROOTED AND MESSED UP YOUR PHONE, DIE!" or something less or more severe
EDIT: Nevermind, I called anyway and it took 2 seconds for them to get it back on. I am back at stock 2.2 and working!

[Q] Possible EVO Brick

Tonight, I was trying to load the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe and everything seemed to be going smoothly. I hit a few screens that I cannot recall exactly and am embarrassed to say but, I cleared all the cache and storage, thinking that I should do this as I have for other ROMs that I have loaded.
The curious question is always "why were you loading that?" I need to send my phone back to sprint because of a warranty issue. Nothing hardware related, just a screen that is loose. In order to make sure that I have a good device, I wanted to send them an original type device. Now that we have that out of the way, here is where I am.
First off, I am somewhat new but have changed ROMs around a lot; Baked Snack, CyanogenMod, Fresh, etc. I like trying out different versions to see what they do.
I saw that I needed to have my SD formatted to FAT32, so I have already done that.
I also have PC36IMG.zip loaded to my SD root.
The symptoms that I am experiencing are:
1. If I hit the power button while pushing the up volume, i get 3 vibrations and thats it. Nothing ever comes on the screen.
2. If I just turn on the device, I get the recovery screen. Once it finds the PC36IMG.zip, it starts loading and has a blue status bar on the right that goes from bottom to top as it loads.
After that, I am pretty much in the endless loop. If I restart it in recovery after that, it gives me the red triangle with a red bang.
The only thing that it will do is boot into recovery and that is it. It seems pretty well blanked out.
For diagnostic, here is what the screen says when i get into recovery:
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0-79.0000
MICROP-041f
TOUCH PAMEL-ATMEL224_16ab
RADIO-1.39.00.04.26
April 14 2010,15:41:34
I am beside myself and humbly ask for anyones advice on what a good step would be to get this thing running again.
I thank you for taking time to read my plea.

OK...
1)The first thing I would recommend is to delete the PC36IMG.zip from the sdcard otherwise everytime you boot into the bootloader it will ask to flash it and it will just waste time. There are a number of PC36IMG files around here and they are not all the same. It is a generic name for the RUU and if you try and flash the wrong one it won't work. And, that seems to have happened to you.
2)The white screen you arrive at by holding down the volume down button and tapping the power button is called the bootlader. Take note of that because we'll need it in a minute.
3) Downloaded the stock Sprint unrooted RUU. It needs to be the same version or newer than what's already on your phone but since you are sending it in anyway I recommend just downloading the newest one (3.7.651...) Here is a link:
http://shipped-roms.com/index.php?category=android&model=Supersonic
4)Download HTC Sync and install it on your computer. You can get it from HTC's site or Sprint or through a google search. It will install the necessary drivers to your computer to see the phone. [EDIT] Here is a link:
http://www.htc.com/us/support/evo-sprint/downloads/
5) Once all the above is done boot the phone into the bootloader (hold volume down and tap the power button while still holding the volume down button). When the menu shows up use the volume keys to navigate to "FASTBOOT" and press the power button to select and enter FASTBOOT. Plug the phone into your PC and run the RUU.exe you just downloaded and it will return it to a completely stock unrooted state.
6) Breathe easy and take phone back to Sprint.

Thanks!!!
Worked like a flippin' charm!!!
Thank you very much for your help. Everything is fine and I am setting it back up to get me through until I can turn it back in.

Thank you, thank you, thank you.. and did I say Thank You!
Been trying to figure out how to use the RUU for two hours... this was the clearest most concise instructions for the process.

The 3 vibrate brick - Please Help {SOLVED}

Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin

msticlaru said:
Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin
Click to expand...
Click to collapse
call for a refurb. I had it happen twice.

ACD168 said:
call for a refurb. I had it happen twice.
Click to expand...
Click to collapse
I have a refurb sitting next to me lol. I wanted to root the old one so that I could do a backup and then restore that backup on the new phone. Wife saves pictures and videos to the phones memory (i know) so i would like to recover this if possible.
Also, it seems like this is something that has to be recoverable. Some sort of software is telling it vibrate 3 or 5 times. I am still doing research on this

Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?

k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
For referance. I just 5vibed my last inc last week, i know all about it.
k_nivesout: oj + power boots fastboot
For the OP, your device is now in qualcomm diagnostic download mode. Hence qualcomm devices in device manager.
To date this is still a none recoverable issue. NO ONE has ever recovered from this.
Good news is if your still in warrenty VZW will send you out another one for free over night. Just call Tech support directly. Just tell them your phone vibed 3 times and shut off. They'll have you do some things to it over the phone. If what they have you try dosn't work, they'll send you one out over night.
Hope this helps a little and hopefully this will save you from countless hours researching. Took me three days, before I realized I had been beaten, lol.

k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device

msticlaru said:
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device
Click to expand...
Click to collapse
Wait, wait, wait just a minute. i wanna talk to you in private. check your pm

msticlaru said:
The 3 vibrate brick - Please Help {SOLVED}
Click to expand...
Click to collapse
Glad I could help you fix this. Don't forget to post what we did to solve this so others can learn from us

This is written for the HTC incredible, please ensure you get the proper ruu image for your particular phone. For example, the HTC wildfire will be PG76IMG.zip, not PB31IMG as I have written below. the rest of the steps are applicable to all HTC phones.
Click to expand...
Click to collapse
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download (see above comment)
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about

Nicely done! I've never encountered this issue but I'm remembering this for future reference just in case.

Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....

nate2830 said:
Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....
Click to expand...
Click to collapse
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.

wildstang83 said:
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.
Click to expand...
Click to collapse
Oh sorry!! Thought it was a similar problem, but had a feeling it wasn't since the stock image didn't resolve my issue. Thanks!

My DINC was suffering from the 5 vibe syndrome. If I used it for anything that stressed the system or even used the phone for a few minutes it would result in a reboot that ended with a black screen, 5 vibes, and the indicator flashing green. At first I could pull the battery for a few minutes and it would recover. Eventually I ended up putting it in the freezer for a bit to get it running again. This progressively got worse until it was nearly unusable. Then I stumbled upon this thread..
http://forum.xda-developers.com/showthread.php?t=982454
Turns out mine was a hardware failure as the processor's BGA grid was failing. I heated the processor and now have a fully functional DINC. I had nothing to lose by trying this as I bought it second hand and didn't want a fancy paperweight on my desk.

Thanks guys, for helping me out with a 3-vibe brick i just had for no reason at the gym today. Was listening to music, texting, working out. All of a sudden, music stops, phone completely unresponsive. Battery out, 30-second wait, restart gives me boot-screen boot loops. Volume up + power gave me a 3 vibe brick.
Thanks to you guys, I discovered that i could get into hboot, boot into recovery from there, do a full wipe, reflash of CM7.0.3 and get the phone to start again. However, that's when the next BIG PROBLEM started. Screen went to sleep while restoring apps from the Market and now when i press the power button, the soft buttons light up but the screen doesn't. This is just super-duper to have problems like this on the same day I was telling a friend that I wouldn't trade this phone for anything else VZ has right now. Anyone have any advice?
PS - The only thing I did today besides "normal" use, is i updated Handcent and changed the LED flash rate.

msticlaru said:
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about
Click to expand...
Click to collapse
Sounds good, I'm hearing a RUU will work just as well?

This got my phone to turn on, but now im in a boot loop. How could i fix this? I appreciate all the help.

I actually recovered from a 5 vibrate error. I had flashed the leaked GB over a stock sense without doing a wipe and got stuck in a boot loop. Every time I tried to either power up into hboot or recovery (- vol and power, or + vol and power) I would get 5 vibrations and then a blank screen. If I tried to power up normally nothing but boot loop after the white htc screen. So I just kept trying to get hboot to load and then after about 5 tries it worked and I was able to get into recovery and flash a backup ROM. I still have problems getting hboot to load properly and it appears its a problem with how hard I press the volume keys. If I press it too hard I get five vibrations followed by the blank screen and it still takes a number of tried to get it to work right. Getting into recovery from ROM Manager is no problem it works flawlessly and I can flash ROMs with it no problem, just have problems when I manually try it. Otherwise the phone works great.

Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.

k_nivesout said:
Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.
Click to expand...
Click to collapse
Like I said it does it with the - volume and power combination too, + volume and power used to go straight into recovery bypassing hboot.
Its not so much the amount of pressure but the length of time I press the buttons, if I hold them too long I get the 5 vibrates, if I press them both then quickly relase them the phone will usually boot normally into hboot but not always. The button psuhing could all be coincidence and the phone just randomly works right after so many tries so I don't want to mess with the phone too much as I'm sure that eventually it will stop responding at all some day. I've never had problems flashing through ROM Manager so I will just use this and skip trying to do anything manually.

[Q] Help please! 3x vibrate and amber flashing light after removing battery! (brick?)

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 .