Related
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.
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.
Hey guys, back with a new problem.
So the wife has been having issues with her power button for a while now, and its getting to the point where it is pretty much intolerable. Last time she killed her battery it took almost a half hour of button mashing to get her phone to boot back up, and I'm worried that next time she kills the battery, I wont be able to get it to boot again.
Does anyone know a way to boot the G2/Desire Z without a working power button (other than disassembling the phone and shorting the contacts in the power button)?
Her contract is up next month, but I'm sure she'll drop it, kill the battery, or have to do a battery pull between now and then, so any help is appreciated!
I'm not sure but I think I had my g2 powered down and pluged it into my laptop and it booted.
Sent from my G2 running the random rom of the day.
like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Sent from my HTC Vision using xda premium
I had that booting issue with the Clockwork Mod touch recovery for our phones. Guess it can be helpful in this situation. This is the thread with recovery info and this is how to flash recovery.
Not sure if the files linked to in our recovery thread still work but here is link to CWM-Touch 5.8.1.0
Couldn't she do adb reboot or no?
Chancee said:
Couldn't she do adb reboot or no?
Click to expand...
Click to collapse
not if the phone is powered off already. need to be on to use adb
Sent from my HTC Vision using xda premium
In Mimistry ROM you can wake and unlock your phone by pressing a trackball.
andriens said:
In Mimistry ROM you can wake and unlock your phone by pressing a trackball.
Click to expand...
Click to collapse
Firstly, I think you mean Andromadus Mimicry, not mimistry
Secondly, trackpad wake/unlock is a feature in most custom roms.
Thirdly, wake is completely different to booting, which is what the question was about. A (maybe somewhat vague) analogy would be, you've lost the ignition key for your car, and you're trying to start the engine by shifting to first gear.
demkantor said:
like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Click to expand...
Click to collapse
I think the version you're looking for is Clockworkmod 3.0.0.5, which should be available in the Rom Manager app (under flash older/other recovery). can't find a working link for the img itself.
-Nipqer
So a friend of mine was updating ClockWorkMod and within about two reboots his phone would only flash the Samsung logo that pops up when the phone first turns on then nothing would happen (black screen). He reflashed the last version of CM stable (CM 10.1.2 for d2att) and nothing changed.
So I figure, we can just flash back to stock via ODIN but the device will only enter Download Mode for about a split second; it shows the green Android then flashes away to a black screen just like bootup. There was a video taken of the text in the corner, the flash counter was incremented and it said something like "QUALCOMM SECUREBOOT: ENABLED"
To be clear, we can enter CWM recovery just fine with no hiccups but we can't enter Download Mode or boot the device. I've tried booting into each mode with the device plugged into a computer and ADB will only recognize it in recovery mode, not in Download or normal bootup.
Is this a hardware failure? I can't tell and I'm not sure how to proceed. Would a Jig help?
Any help would be appreciated.
EDIT: It has now been discovered and confirmed that a loose power button is the culprit here.
Do you have access to a USB jig to force the phone into download mode?
audit13 said:
Do you have access to a USB jig to force the phone into download mode?
Click to expand...
Click to collapse
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
hakoda said:
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
Click to expand...
Click to collapse
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Larry2999 said:
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Click to expand...
Click to collapse
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
hakoda said:
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
Click to expand...
Click to collapse
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
audit13 said:
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
Click to expand...
Click to collapse
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
hakoda said:
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
Click to expand...
Click to collapse
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Larry2999 said:
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Click to expand...
Click to collapse
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
hakoda said:
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
Click to expand...
Click to collapse
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Larry2999 said:
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Click to expand...
Click to collapse
Can confirm that it's a stuck power button; tapping it continuously with an end of a chapstick tube while the phone booted got us all the way into Cyanogenmod; we confirmed that TWRP flashed successfully as well. However, we as soon as we stop tapping it, it goes back to the previous behavior.
We're now looking for some guides online to fix it, seems mechanical if tapping it continuously will keep it unstuck for short amount of time.
Thanks again guys
I've got a little problem with my Desire Z, I guess my question might make a change from "I can't boot my phone" I guess... Mine boots, and that's the problem, I can't turn mine off when it's connected to a USB power source!
If it's on battery I can turn it off... But... The moment I connect power (either PC USB connection, or a dumb power source) the phone boots up into recovery.
And it's always recovery it boots into. I then have to tell it to reboot and then I get the "real" phone.
It doesn't matter how I turn it off, from the full android "Power off" option, the terminal under SU and typing halt, or "power off" from inside recovery. It still starts up again if it is connected to external power via the USB.
Can anyone help?
I'll admit my phone has been abused to a huge extend, it's currently running Purekat 4.4.2 and Clockwork recovery 6.0.4.5
(I ended up trying 6.0.4.5 because TWRP and an earlier CW both thought they were installed, yet neither would actually start).
Buddy its not your phone's problem its with recovery because cwm 6.0.4.5 automatically open when we try to plug charger when phone is off . It was fixed in version 5.0.2.2 or 5.0.2.4 but after that it broken again . If you want to charge your phone in off then try 4ext recovery it will full fill your need.
Sent from my Desire Z
Super!
Thanks for the prompt reply!
That's a very silly bug!
Np
Sent from my Desire Z