[Q] SOS Can I save my Incredible? [SOLVED!] - Droid Incredible Q&A, Help & Troubleshooting

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!

Related

help (i hope)

Ok here is my situation....
I was able to fully root using toast's method. I than tried to flash my radio from the link the forums.
It installed everything properly, but then got stuck on the htc evo boot screen. i left it alone for 2 hours and it did nothing.
Is there something that can be done or did I brick it?
Thanks in advance.
Owl
owleyes said:
Ok here is my situation....
I was able to fully root using toast's method. I than tried to flash my radio from the link the forums.
It installed everything properly, but then got stuck on the htc evo boot screen. i left it alone for 2 hours and it did nothing.
Is there something that can be done or did I brick it?
Thanks in advance.
Owl
Click to expand...
Click to collapse
Just turn it off, hold the volume button down and then hit the power button, this will put you in recovery so you can flash again
tried that, but it will not let me back into custom recovery. or do i have this wrong. I am still kinda new to all this.
what does it show? a red exclamation mark?
doing the volume down, then power. it brings me to that screen. errr the 3 androids on skateboards screen lol
damn 5 min wait between posts lol. ima be at this all night it looks like lol.
once you are there, you should be able to reboot into recovery. right when you enter that screen it should start looking for PCIMG36.zip and once it can't find that, a menu should pop up. scroll down the menu using the volume button until you hit recovery. press your power button and it should boot you into recovery. if it takes you to a screen with a red exclamation point, then you would need to plug in your phone to your pc and run the bat file that came in the first part of rooting instructions to get into recovery.
once i hit recovery from that menu, it takes me right back to the htc evo splash screen and locks up.
i really do not understand this. all these reports of this radio installing with no issue and I get this >.> ah well. i guess i knew the risks when i started this.
well if your phone can still boot up then it's definitely not bricked. did you try a battery pull and reboot?
yeah....well that is good to know anyway lol.
how do these terminal emulators work, and can i get one on my phone in this condition?
I am reading the sd and usb fix thread...but i don't understand how to run the emulator on the phone.
RUU?
_________
justinisyoung said:
RUU?
_________
Click to expand...
Click to collapse
Excellent idea, just go here http://forum.xda-developers.com/showthread.php?t=685835 and download the RUU.
Once you run this you are back to stock and will have to re-root your phone via toasts instructions. Hopefully this works
tried that as well. It says there is no phone connected.
I dont know man, you gotta try combinations. Like hold the volume down to get to that recovery and then try to run the RUU perhaps?
believe i am trying everything lol. i even put the pcimg file back on and try to go from that but the phone does not even recognize it now meh it's a process. at least i know there is some hope lol
i don't have an evo (yet), but when you get into the bootloader screen (with the androids on skateboards), is there an option to go to Fastboot mode? if you RUU, that's the mode you wanna be in.
ok i put the original pc36img back on the card and got it to boot back into android!!!!!!
so now i have the root pc36img file on there. I am scared to keep going and rerooting it lol
Will i have to redo it all? I am not sure where to go from here.
everything seems to be working again.
any advice for me now? should i RUU it and just go back to stock or can i keep going from this point with the root steps again? (this time leaving the radio flash alone lol)
If you were able to get root in the first place, you are fine.
Download Flipz Stock Rom with Superuser. No flashing radios necessarily. Just flashing an update.
And you are set. You will be rooted with stock rom. Supposedly.
I did manage to get it fixed last night. Now I am fully rooted and running the fresh rom.
I really appriciate all the advice from everyone who was on here at 4am with me lol. Kinda sucks my first posts on here had to be about breaking my phone, but you guys are awesome!
I got stuck in a boot loop once too when trying to flash a rom. It was because I didn't clear the Data/Stock Image. I had cleared Cache/Dalvik, but not data.

[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.

[Q] Root gone wrong, my screen is blank [non branded HTC Desire]

Hey guys!
Now this happened for some time ago because i switched phone to my blackberry in anger over the brick of the Desire, and i can't remember exactly this happened!
I think i rooted it and then the screen suddently went blank when i started it.
Now i searched the web for looooong time, and also some threads in here, to find my golden answer - but nothing hat helped yet. But i got a wierd feeling in my stomach that i'm doing something wrong.
So since i can't do it myself i decided to wright to you, and hope that helps!
My HTC Desire is not branded.- at least im pretty sure it isn't!! There is no place it's physically branded. And it's bought in Denmark, and i don't think we've got branded phones here as in UK and USA
I've tried this guide because i saw some people had succes with it:
QUOTE''
You don't need to root or do anything unusual in order to apply the FroYo update, you only need that for custom recovery. It's not impossible to do with a broken screen, just do this:
1. Make sure the update.zip file is on your goldcard and correctly named.
2. Take the battery out first to ensure the phone is powered off. Then hold vol down and press the power button, and hold vol down for about 5 seconds. That will get you into the bootloader even though you can't see it.
3. Press vol down once. This will select recovery.
4. Press the power button once. This will start the recovery. The phone will vibrate briefly.
5. Wait 20 seconds or so. Then press vol up and the power button and wait a few seconds. You'll now be in system recovery.
6. Press vol down once to select 'apply sdcard:update.zip'.
7. Press the power button once to start the recovery.'' QUOTE END.
But nothing happens.
And i also tried Unrevoked3, but neither did that helped, it got stock at ''Waiting for root... (safe to restart if this doesn't work)''
I would really appreciate if you would take your time to help me today! Because i really want my HTC Desire back, because it is a really sweet phone after all
I know you guys are much more wiser to this than me, so i hope you got at magical form to solve this out.
So... when you boot holding the vol down key what happens?
Well the tricky part about it is that i can't see anything! But if i go into boot (atleast i think i do) i can push VOL- and then Power button, and then it vibrates briefly, so i think it's going in to recovery.
Right, try this...
Download this RUU (2.29.405.5):
http://www.multiupload.com/LEJCW182AH
Turn the phone off (remove the battery to be sure) and turn it on holding the BACK button. Hold back for about 5-10 seconds to be sure you're in FASTBOOT. Connect to the PC and assuming the drivers are installed wait a further 20 seconds
Then run the RUU. If you're unbranded it will install and should get you back up and running. If it completes and you still can't see anything the screen is dead and will need replacing
So what happens when you turn it on normally, vibrates and then you can't see anything? Maybe try this thread.
@EddyOS
Thank you!
I'm going to try the FASTBOOT right now! - i have slow internet, so i assume it's gonna take while to download the RUU - but i'll response the results here as quick as i can.
@TheGhost1233
Nothing happens, but i can see that there is light in the screen, because it turns slightly light-darker.
Also when i powered up the phone i can lock it up with my fingers and still use my touch, so it's not the ''touch'' function that there is broken.
touch is seperate to the screen anyway, lets hope its not a hardware fault and can be fixed! post your results
I'm trying with another RUU i have - while im downloading the on you've linked to - 8RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed is the one i'm trying with right now.
When i start the desire with holder down Volume (DOWN) and Power button for 5 seconds, and then plug the phone into USB there comes an jingle on my computer(which always appears when connecting any phone) but then it wont find more.
I can't see the device in ''My computer'' ?
And i get the ERROR [170] Connecting Error?
That's an old RUU so use the one I linked to
This is what i'm doing now:
Volume- and power in 5 seconds.
Plug the USB cable to the phone. (Now i can hear ''dy-dy'' from my computer, which means that my computer has detected a hardware. BUT i can't find the phone's SD Card in ''My computer'' - should i could do this?
But in my Applications i can find it under ''Special applications'' - i think i will translate i too - as ''Android 1.0''.
Now i run the RUU which you've linked to, but then i geat Connectin Error 170.
hmm?
You should be holding BACK, not volume down, when you turn it on as you need to be in FASTBOOT not HBOOT to run an RUU
Lol okay, i feel like a morron now, sorry for not have seen this.
But i still get the error 170, usb connection error!
Do i need to install HTC Sync? I've uninstalled it for the sake of unrevoked3.
And is there another way to do this? Over the phone exclusively maybe - if my USB connection fails all the time.
No you don't need HTC Sync. Sounds like you've USB-bricked the phone. You could try extracting out the PB99IMG.zip from the RUU and flash it that way but as you can't see what you're doing it's hard
And how can i see which HBOOT i got? Just want to check regarding to this thread - http://forum.xda-developers.com/showthread.php?t=748498
Haven't a clue, doens't matter as the RUU I posted is the newest one so will work regardless
Oh, okay.
Well i'm trying to flash PB99IMG now. I'm just hoping im doing it right allthough i can't see anything.
I'm doing as following: http://www.youtube.com/watch?v=ucBs9RVGL0w
You don't flash it like a custom ROM. You get the PB99IMG.zip from the ROM, copy it to the root of the SD card and then turn on into HBOOT. The phone will then find it and ask if you want to flash it - say yes and that's it!
Oh okay. Just from the ROM you've linked to me?
And can you remember how to say yes, just power button?
Normally it says press up for to continue but I can't remember off the top of my head
EDIT: Yep, volume up to start
Thanks mate, i'll keep on trying various of thing.

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] EVO Cannot boot normally or into recovery

I am using a rooted EVO 4G gingerbread with clockworkmod
Current symptoms are as follows:
Boots into a blank screen (backlight is on, but nothing on the screen at all)
Vibrates once you turn it on, but nothing after that.
Stays there until I pull the battery.
Occasionally vibrates twice and a green light will start to blink above the screen.
Tapping power still toggles the screen and backlit buttons when in this state.
Throughout today it's gone through several different symptoms.
At first it was stuck on the quickboot screen doing nothing, but the buttons were completely unresponsive. It would sometimes also constantly vibrate. I took out the battery for awhile and it would just show the screen again when I put it back in and tried to boot.
When I got home later that day, it stopped doing that, but just would refuse to boot at all. It would sometimes show the white screen and just be stuck there unless i pulled the battery out. Now it's doing the symptoms I posted in the beginning.
Any ideas on what's going on and how to fix this?
Can you get into Hboot? If you can you can RUU and hopefully that will do something.
Sent from my PC36100 using XDA Premium App
tropicalbrit said:
Can you get into Hboot? If you can you can RUU and hopefully that will do something.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thank you for the reply
No I cannot get into HBoot, it literally just boots up (whether or not I'm holding the volume down button or not) into the blank screen I described.
Reioumu said:
Thank you for the reply
No I cannot get into HBoot, it literally just boots up (whether or not I'm holding the volume down button or not) into the blank screen I described.
Click to expand...
Click to collapse
Turn off your device and then remove the battery AND the SD card. Wait about 30 seconds and then re-insert the card and battery. Now simultaneously press the DOWN volume button and the power button until the device starts. You *should* be taken to the HBOOT screen. If so, select 'recovery' from the menu and then go from there. I suggest a re-wipe and re-flash of your rom.
If you still cannot get to the HBOOT screen or recovery, download one of the RUUs from my signature, specifically one with an .exe extension and run it from within Windows while your device is connected to your PC via USB.
Still nothing. Thanks though.
I think I have to just return and get another phone... I haven't seen this error anywhere. I removed the microSD card for about a minute, put everything back in, still tried to boot in recovery (vol- and power) didn't work. I tried one of the RUU .exe and no good, when the phone was on, the program didn't recognize that my phone was there or something. Afterward, I tried the other RUU link where you have to drag files, coudln't see anything when I tried to boot in recovery still.
This is looking like i have to get a new phone
new symptom. Just vibrated 5 times. Longer than normal too.
HELP
Reioumu, what did you do?
i have this exact same problem and im freaking out. any suggestions?
same symptoms...with 5 vibrations and need for a battery pull.
EVO 4G
CYANOGEN MOD 7.1 RC
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
I can get into hboot (by pressing vol-down + power)
I cannot get into recovery.
It splashes to the white htc evo screen, then flicker of the LED, 5 vibrates, and a black screen.
i was backuping my system using ROM MANAGER. When i turned on the phone, it couldnt detect the SD card. When i rebooted all the issues you described started to happen.
I'm at wit's end. I did a bunch of googling on the issue. "vibrate 5 times black screen evo" and there seems to be some sort of fix but i dont understand how to implement any of it. I got as far as installing the Android SDK but cant get fastboot to work. The issue seems to be with the USB port AND the SD card detection.
I was planning to just give up and give it to Sprint to fix but the rep said i need to unroot it before i send it to them. [email protected]#[email protected]#. I cant do that without recovery!

Categories

Resources