I was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
K... so i tried using unrevoked to push a new recovery and it wont run from hboot.
but, i can get into recovery now IF the phone is plugged into usb and unrevoked is at "waiting for device."
if i unplug usb then it does the 5 vibrations w/ black screen and flashing green blinker.
problem is the phone wont mount sdcard.
i saw other people having problems with new CW, but mine still says 2.5.0.5
Bad SD Card?
RMarkwald said:
Bad SD Card?
Click to expand...
Click to collapse
Tried three.
daftlush said:
Tried three.
Click to expand...
Click to collapse
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
wwjdd44 said:
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
Click to expand...
Click to collapse
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
daftlush said:
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Click to expand...
Click to collapse
FinalBoss said:
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
Click to expand...
Click to collapse
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
wdfowty said:
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
Click to expand...
Click to collapse
I don't know about that...I have an SLCD handset and I flashed .92 with no issues whatsoever.
daftlush said:
I was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
Click to expand...
Click to collapse
Sounds like your SD card isn't formatted fat32..... it has to be or hboot won't read the PB31IMG.zip try reformatting
Sent from my Incredible using XDA App
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
FinalBoss said:
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
Click to expand...
Click to collapse
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
newtoroot said:
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
FinalBoss said:
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
I hate to say it but it sounds toast bro.... if the ruu didn't fix it then it had to be a hardware problem sorry I couldn't help.....
Sent from my Incredible using XDA App
Had this happen to 3 INCs already, call for a refurb.
I'm going to get another one from VZW. Is there any way to make sure this doesn't happen again? I'll start off by not flashing CM7 in the mean time. Anybody have any suspicions on what could cause this?
I just had the same thing happen to mine this morning after flashing the HeyItsLou #9. I can only access ClockworkMod Recovery when I'm plugged in but can't access the sdcard. I've scoured multiple forums for hours and nothing seems to work. I just tried the RUU and it says "wrong image". There seems to be no reason why this happens and there's no one thing that causes it, I've read that it happens to both rooted and non-rooted users.
I filed a claim with Asurion and my new one will be here on Tuesday. It worries me a little that I can't get CWM off of it.
dpwhitty11 said:
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
Click to expand...
Click to collapse
Same here.
I just pulled the battery, rebooted into recovery then did a recovery from one of my backups.
Now I'm worried there might be a issue with CWM 3.0.0.8 or something causing this to happen to people....? I just read that CWM 3.0.0.8 is known to have issues clearing data or something when installing new ROMs ..
FinalBoss said:
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
It would appear that it's for sure bricked if you've tried this.
Rooted my Incredible yesterday...with relative ease...some very helpful guides out there.
After searching a little...I can't find anything similar to my issue, and the pieces I can find don't piece together for me.
Was accessing hboot (power plus volume -) this morning and accidentally hit the power button to select "fastboot", rather than the "recovery" option i was wanting to get to to make another backup since I had added a few apps after my root.
My phone booted into froyo without any issue...and all my rooted apps worked fine (mainly wireless tether...the main reason I rooted). I shut down the phone and attempted to access hboot again...but got 5 vibrates and a green blinking led, with a blank black screen.
Pulled the battery...and let the phone boot normally (which I was hoping for since I thought I may have bricked it) and all is well...still with root applications working fine. I have tried hboot again with same result (5 vibrates and green flashing led), so I have let the phone stay with froyo for fear that if i screw around with it too much I may brick it after all.
Am I over-reacting to the lack of hboot? Suggestions for a fix are appreciated!
This is wierd, the only time ive heard this prob is when someone tries to flash a rom and then this happens. Sry man i have no idea its strange
Sent from my ADR6300 using XDA App
Download Rom Manager if you dont already have it a then install CWM recovery through it. It just sounds like it didn't install correctly the first time. That usually works for me when I get the problem of only being able to get into HBoot and Fastboot.
Not sure why, but I restarted my phone today and now it just gets stuck at fastboot. None of the buttons work. If I take the battery out and put it back in it will just immediately reboot. I can't get it to stay off with the battery in.
If I plug it in, I can recognize the device using fastboot, and if I reboot the device using fastboot reboot I can get it to start properly, but none of the buttons are working. Power, Volume, Menu, Home, Back and Search all don't work. The OJ works, but pressing the button down does nothing.
I've tried flashing an RUU but it says it can't find the device. I can't get it to show up in ADB either, and even though USB Debugging is enabled, I don't get the notification that says it does.
Any ideas on what I can do?
If I hold power+volume down when I put the battery in it will switch to hboot, and I can get it back to fastboot with power+back, so the buttons should be working.
Can't you just run RUU when your in hboot or fastboot? If you can get to hboot surely you can go recovery, then you can use an RUU for defo since it should come up as being connected. Unless you have further issues.
I can get to hboot, but none of the buttons respond, so I can't get to recovery.
I managed to get a Telus RUU working from fastboot.
Now I'm using the 0.93 HBOOT, but nothing is working.
It won't boot into Android now though. My question is, since I flashed the official RUU am I still rooted? The phone is still under warranty, so I'm go to see what I can do about getting it repaired.
No, installing an RUU will remove root and wipe everything on the phone. I also believe that it changes it back to s-off, so if you sent it for repair as it is it should be fine
Sent from my HTC Desire using XDA App
Dear XDA developers,
a few days ago my internet connection started to fail so i decided to normally reboot my HTC desire by using the power button. After the restart it kept rebooting and showing the AlphaRev boot screen. I decided to reflash the phone by using a standard RUU. I tought it all worked out well, untill it crashed at 99%.
When i press the power button, the phone starts a continiuous vibration and shows a black (blanc) screen. I can not enter the bootloader / fastboot / recovery. It seems to react on nothing. I tryed to charge it, in case it was a battery issue, but no luck and no charging led.
I was running Leedroid + root + s-off with H-Boot 0.93.
On the XDA forum i found a way to blindly access the bootloader if there is no screen, this is not working out either.
Can someone help me out? Or is it ready to throw away? Besides that, is it possible to send it for guarantee? Or would there still be rooted/custom rom footsteps on the device?
it sounds like u flashed the wrong ruu. theres 2 types
amoled
or slcd
find out which ur phone is and flash that ruu
I will try but the computer does not recognize the device. Keep you updated.
edit:
Don't think this has anything to do with the screen. On the forum i found a topic with a trick (blind navigating to the recovery screen), but i think nothing happens when i follow this steps.
Maybe the HBOOT got fubar'd. If that's the case, your phone may be bricked. Take it to HTC for a look-see.
alpharev.nl said:
Is there any risk involved?
Yes, there is. Flashing HBOOT will flash a critical part of your phone, if that gets corrupted, your phone WILL be bricked.
[...]
If your phone no longer turns on anymore, please return to HTC for warranty purposes.
Click to expand...
Click to collapse
Do you think the warrenty will void if i send it for repair? Because there hase been a custom ROM and bootloader installed?
OK.
I will put in a detailed info about what happened.
A week back, my wildfire's touchscreen started to function abnormally.
I was rooted and on Cyanogenmod 7.0.3
So, I flashed the phone with DK custom FROYO to make it look like sense so that the warranty is not void and took it to the HTC store.
They replaced the touchscreen for a flat fee (It was water damage according to them. But the phone was never used in wet conditions nor exposed to water)
But anyway, the phone was working fine when I brought it home from their store.
Then I flashed CM7.0.3 again.
And everything was working fine.
I OCed acc. to CM's settings to 652-352 Mhz.
And left the phone to charge in charger overnight.
When I woke up, the phone was off and there was just the red LED light blinking.
I tried to boot it again, but nothing works.
Pressing the power button does not do anything.
The phone still boots into recovery. At times.
I don't know what makes it boot into recovery. But at times it does, at times it doesn't. (Right now it's not booting into recovery no matter what I do)
Just the red LED keeps on blinking.
Please help.
I am not familiar with pushing commands onto the wildfire since I use a mac.
Please suggest any methods. If they involve using command line, I can use my windows PC for that. But please give a how-to of length enough for a noob ) ) to understand.
Thank you.
Pulz
EDIT :
I got to boot into recovery once. Tried to reflash CM7.0.3
It came to "Installing update" and then failed to go further.
Tried to install DK Custom Froyo 4.5
And it went to opening package and then failed to go further.
Now entering into a panic mode !
Red light blinking generally occurs when phone is hot and plugged in to wall socket. Is it so at that time ?
Unplug the charger or usb. Remove the battery and reinstall the battery. Try to boot into hboot mode (volume down + power) or fastboot mode (trackpad + power) . If your phone can boot into hboot/fastboot mode and has no restarts or power offs, then I think you can solve it.
Try to clear storage from hboot menu. Or factory reset from recovery once you enter it. If still it is not solved, try using "pc49img" method of flashing an RUU from the hboot menu. Hope it helps. Shouldn't help if there is hardware issue.
Sent from my Blade using XDA App
hye another noob here running on cm7.
actually i have the similiar problem my wildfire start rebooting over and over again but the cause is different.
this problem happen after i want to know what class my micro sd is.
what i do is i go to settings>storage>unmount sd card.
so after knowing the class were i insert back the card then the problem happens.
my phone start to crash then cm7 logo appear after that i enter my pin no so brought me back to the home screen after few seconds the logo appear again so i have 2 repeat the same steps...
this happen many times what i do is i remove the battery wait few hours then turn back on..
so help me if someone have the similiar problem and solutions.. thanks!!