hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Same problem
tekweezle said:
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Click to expand...
Click to collapse
My incredible started doing this yesterday, Ive tried this option it doesn't work for me. I can get the menu but it when I choose factory reset or any of the other options it flashes the htc incredible screen and starts the loop again, any more suggestions would be appreciated.
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Htc loop
wanted167 said:
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
Click to expand...
Click to collapse
tekweezle said:
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
No I was getting ready to root it the day this started. Will rooting help this problem?
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Htc loop
tekweezle said:
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Click to expand...
Click to collapse
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
SuzyQangel said:
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
Click to expand...
Click to collapse
This sounds quite a bit like an Inc I have lying on my shelf. It was a friend's and he gave it to me to see if I could fix it. As far as I can tell, the phone's emmc storage simply failed. These phones are aging and that happens sometimes. Anyway, I tried all the usual stuff, including running RUU's (flashing signed PB31IMG.zip's since the thing had never been rooted and was still s-on), and yeah, just boot looped.
I did get the phone working, but it was complicated and messy. Here's more or less what I did: I was able to successfully run the RUU that updates HBOOT to 1.02 (or 1.07, either one works), which allowed me to unlock the bootloader via HTCdev. (see one of the root / s-off guides if this doesn't make sense.) This made it possible to flash ClockworkMod recovery using fastboot, and boot into recovery. From there, I was able to get to a root shell through adb (plugged into my computer) and proceeded to downgrade and get s-off, following the guide. It now works, though it's running Froyo and there is hardly any space for apps due to the messed up storage. I've been wanting to try this hack on it but I haven't gotten around to it yet.
stuck in boot loop, keys dead
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
spappy said:
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
Click to expand...
Click to collapse
Sounds hosed to me. You could try to flash an RUU zip but that'd require use of the keys in HBOOT. If there is an RUU option that does not involve touching the phone, it's possible. Otherwise, no. I guess you could open the phone and check the button connections are there but it may be locking up at the HBOOT screen. Give it a chance to charge up a bit. However, I believe this phone is a lost cause. I seem to be seeing more frequent bootloop phone reports lately.
Related
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.
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
DiGiTY said:
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
Click to expand...
Click to collapse
It is normal for it to scan and give you that 'wrong image' message. If you had a PC36IMG on your sd card, that's when the bootloader would find it, and ask you to update. Since you dont have a PC36IMG on your card, it scans and finds nothing, so it says 'no image or wrong image'. No worries. What were you trying to accomplish by holding power and volume up? Its power and volume down that puts you to the bootloader. What were your intentions once you got to the bootloader? Were you trying to get to recovery, to clear cache or reflash a rom or something? If you want to reboot your phone without really doing anything, from where you're at in the bootloader, you'll see an option that says 'fastboot'. Select that. Once at the fastboot screen, you'll now see an option to reboot phone, and to power phone off. Select reboot, and see if she powers up for you. Shouldn't be any issues
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
DiGiTY said:
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
Click to expand...
Click to collapse
I'm not sure what would cause the problems you're describing. What ROM are you currently on? Have you tried wiping cache and dalvik cache? Perhaps it's an issue with the Gmail app itself. In any case, I'd first try wiping cache and dalvik. If that works, great. If it fails, I'd probably do a complete wipe and fresh install. That usually solves any issues for me.
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
DiGiTY said:
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
Click to expand...
Click to collapse
Yea, its power down and volume that takes you to the bootloader. You wont get directly to recovery unless your rom has the 4 option quickboot, then u can select recovery. Anyways, so once youre at the bootloader, you just need to select recovery. Then youll boot to clockwork. From there, you can make a new backup, flash a new rom, wipe caches etc.
Sent from my PC36100 using XDA App
Oh, okay. Thanks again!
DiGiTY said:
Oh, okay. Thanks again!
Click to expand...
Click to collapse
You're welcome. I'm glad to help out
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
I'm running MrGarak's fantastic MIUI rom however I've found that the kernel is booting my phone into that white HTC diagnostic screen by default. Unfortunately my volume down button is dead and so I can't navigate the menu; the only way I can boot my phone at the moment is to boot it connected via USB as that makes it boot to Recovery and I can reboot from there.
Any ideas? I think this and another rom I tried both used LordMUE's kernel, could that be the reason the boot preferences don't default to just booting the OS?
Any help and/or pointers would be greatly appreciated
So you can access bootloader and recovery!
So just flash another kernel. What's your problem?
Put a zip on your SD (with a SD reader or ADB pull), then go in recovery, navigate with the 4 keys under the screen (or vol+ and power)... and flash.
What is strange for me is that it seems to happen sudenly... so how do ou know it's the kernel. Anyway...
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
_david_94 said:
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Unfortunately it boots into the white HTC area (dunno what it's called). The one where you can see if your phone is S-OFF or not.
Also, I'm not sure what is to blame... but I've only just recently noticed that my phone cold boots this way so I assumed it was a recent rom that I applied. Will test this theory later.
Sounds to me like your volume down button is stuck in.
Definitely not a ROM issue, as it has nothing to do with the bootloader.
Sent from The App that Time Forgot.
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
xtremedelta said:
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
Click to expand...
Click to collapse
Ah, I'm definitely beyond warranty. The thought of vol+down being stuck down makes a lot of sense!
I'll just take it to one of the dodgy Asian repair shops, if it's a hardware issue I'm sure they'll know what to do.
Cheers for your help everyone!
So I used to have an iPhone, and then it got stolen. My sister, who currently lives across the country (university) has a friend who gave her their old HTC One V. She turned it on and it worked, and then shipped it to me. I went to Bell and then their employee set it up with my account, did a factory restore, and then rebooted it. I saw it turn on and work properly in front of my own eyes, but I had to go charge it at home as it was dead.
I get home, connect it to a charger, the orange charging light on the top turns on, and it opens up a menu that says "ClockworkMod Recovery v5.8.3.1" The options below say: Reboot system now, install zip from sdcard, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, and advanced.
Now, at the Bell store we factory reset, and rebooted the system, and then the phone worked. However, now when I press "reboot system now," it goes black, the orange charging light turns off, and then it gets frozen on the "HTC One, quietly brilliant" screen. It stays that way until it dies, and I can't even hard reset while it's frozen. It is completely frozen. I even tried to connect it to HTC Sync Manager, but when I plug it in, nothing happens. It doesn't detect the phone. I'm on a Macbook Pro, for context.
Help? I can't even do anything on my phone, and being a new Android user, I have no idea what to do.
AlvinTheChoster said:
So I used to have an iPhone, and then it got stolen. My sister, who currently lives across the country (university) has a friend who gave her their old HTC One V. She turned it on and it worked, and then shipped it to me. I went to Bell and then their employee set it up with my account, did a factory restore, and then rebooted it. I saw it turn on and work properly in front of my own eyes, but I had to go charge it at home as it was dead.
I get home, connect it to a charger, the orange charging light on the top turns on, and it opens up a menu that says "ClockworkMod Recovery v5.8.3.1" The options below say: Reboot system now, install zip from sdcard, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, and advanced.
Now, at the Bell store we factory reset, and rebooted the system, and then the phone worked. However, now when I press "reboot system now," it goes black, the orange charging light turns off, and then it gets frozen on the "HTC One, quietly brilliant" screen. It stays that way until it dies, and I can't even hard reset while it's frozen. It is completely frozen. I even tried to connect it to HTC Sync Manager, but when I plug it in, nothing happens. It doesn't detect the phone. I'm on a Macbook Pro, for context.
Help? I can't even do anything on my phone, and being a new Android user, I have no idea what to do.
Click to expand...
Click to collapse
Dang it, you have MANY things to learn I propose you to search some noob threads on this forum and learn what root, bootloader, recovery, kernel, S-ON/S-OFF and ROM is and how to flash them... but SEARCH first instead of asking, it will help you in the future
btw, you will have hard times because of your Mac it's the worst and useless thing people could buy
Hiya,
so to be clear you can still boot the phone into ClockWorkMod or not? One way to do this is to turn phone off then, turn it back on while holding the volume down button.
Do not despair there are many ways out of your problem! However I think if you OSX it may make things a little more complicated.
Feel free to google for answers, check the HTC One V forums here (good search bar up top right) or just ask away.
regards
parkourz said:
Dang it, you have MANY things to learn I propose you to search some noob threads on this forum and learn what root, bootloader, recovery, kernel, S-ON/S-OFF and ROM is and how to flash them... but SEARCH first instead of asking, it will help you in the future
btw, you will have hard times because of your Mac it's the worst and useless thing people could buy
Click to expand...
Click to collapse
haha my apologies, it's just very overwhelming and at the time I was very frustrated and as a result, impatient. Another concern I had is that since this is not a new phone, I have no idea what had been done to it already. My friend even told me this isn't the default software?
mcgi5sr2 said:
Hiya,
so to be clear you can still boot the phone into ClockWorkMod or not? One way to do this is to turn phone off then, turn it back on while holding the volume down button.
Do not despair there are many ways out of your problem! However I think if you OSX it may make things a little more complicated.
Feel free to google for answers, check the HTC One V forums here (good search bar up top right) or just ask away.
regards
Click to expand...
Click to collapse
Sorry, not exactly sure what you mean. To explain further, if the phone has any power at all, and not frozen on the loading screen, it loads the ClockWorkMod recovery menu. Because pressing the power button at that menu just selects whatever is highlighted, I can't turn it off. Hard reset (down volume + power) similarly doesn't work, because down volume just moves the selection down. And when it's frozen on the loading menu, hard reset, power off, nothing works. So because I can't even turn the phone off or anything, I think my answer to your question is no. I may just be extremely nooby and be turning it off wrong :cyclops:
AlvinTheChoster said:
haha my apologies, it's just very overwhelming and at the time I was very frustrated and as a result, impatient. Another concern I had is that since this is not a new phone, I have no idea what had been done to it already. My friend even told me this isn't the default software?
Sorry, not exactly sure what you mean. To explain further, if the phone has any power at all, and not frozen on the loading screen, it loads the ClockWorkMod recovery menu. Because pressing the power button at that menu just selects whatever is highlighted, I can't turn it off. Hard reset (down volume + power) similarly doesn't work, because down volume just moves the selection down. And when it's frozen on the loading menu, hard reset, power off, nothing works. So because I can't even turn the phone off or anything, I think my answer to your question is no. I may just be extremely nooby and be turning it off wrong :cyclops:
Click to expand...
Click to collapse
Hi Alvin,
do you have the SDcard the phone had before? Can you put ADB and Fastboot on your computer? I can then work with you to explain how to put your own rom and kernel on the phone to get it to boot.
https://www.google.co.uk/search?q=adb+and+fastboot+for+mac+osx&oq=adb+and+fastboot+for+mac+osx&aqs=chrome..69i57.5280j0j1&client=ubuntu-browser&sourceid=chrome&ie=UTF-8
mcgi5sr2 said:
Hi Alvin,
do you have the SDcard the phone had before? Can you put ADB and Fastboot on your computer? I can then work with you to explain how to put your own rom and kernel on the phone to get it to boot.
Click to expand...
Click to collapse
No, unfortunately I do not have the SDcard from before. Is that necessary? And I believe I have put ADB and Fastboot on now. What is the next step?
I appreciate the help.
AlvinTheChoster said:
haha my apologies, it's just very overwhelming and at the time I was very frustrated and as a result, impatient. Another concern I had is that since this is not a new phone, I have no idea what had been done to it already. My friend even told me this isn't the default software?
Sorry, not exactly sure what you mean. To explain further, if the phone has any power at all, and not frozen on the loading screen, it loads the ClockWorkMod recovery menu. Because pressing the power button at that menu just selects whatever is highlighted, I can't turn it off. Hard reset (down volume + power) similarly doesn't work, because down volume just moves the selection down. And when it's frozen on the loading menu, hard reset, power off, nothing works. So because I can't even turn the phone off or anything, I think my answer to your question is no. I may just be extremely nooby and be turning it off wrong :cyclops:
Click to expand...
Click to collapse
What happens when you keep pressed the power button for at least 10-15 seconds? This action should turn the phone off.
kvestas said:
What happens when you keep pressed the power button for at least 10-15 seconds? This action should turn the phone off.
Click to expand...
Click to collapse
I was entertaining the possibility the power button is partly broken, and I think that's the case. Sometimes pressing the power button doesn't trigger what is selected in the menu and takes a couple tries. However, because of your comment I tried a few more times to turn it off and I think it actually turned off once. I held it down and it faded to black, but there was no "Power Off" button I had to touch before it went black. Is that just because I was in the ClockworkModRecovery menu? Did it actually shut off that one time?
EDIT: I've been able to do the same thing a few times now, even once in the frozen "HTC quietly brilliant" screen! However, I can't seem to hard reset, and I'm thinking maybe my volume down key is similarly faulty.
AlvinTheChoster said:
I was entertaining the possibility the power button is partly broken, and I think that's the case. Sometimes pressing the power button doesn't trigger what is selected in the menu and takes a couple tries. However, because of your comment I tried a few more times to turn it off and I think it actually turned off once. I held it down and it faded to black, but there was no "Power Off" button I had to touch before it went black. Is that just because I was in the ClockworkModRecovery menu? Did it actually shut off that one time?
EDIT: I've been able to do the same thing a few times now, even once in the frozen "HTC quietly brilliant" screen! However, I can't seem to hard reset, and I'm thinking maybe my volume down key is similarly faulty.
Click to expand...
Click to collapse
Indeed the power button is quite sensitive on HOV so you might need to keep trying several times when using it.
Holding power button is a hard shut down and it shouldn't ask you to confirm this action. It's ok. Unless you have the system already started it may ask you for reboot options. Even in this case the phone will shut down if you'll still keep the power button down for a long time.
At first you may try the simplest thing I guess. Start recovery (you might remember it should start automatically when you turn off the phone and plug in a charger) and choose the menu option "wipe cache partition". Restart the phone after clearing the cache. There is a small chance but this might help.
If not you have to continue your research with adb commands.
Another option is to asquire sd card, I think it would be easier for you when you are using mac.
AlvinTheChoster said:
So I used to have an iPhone, and then it got stolen. My sister, who currently lives across the country (university) has a friend who gave her their old HTC One V. She turned it on and it worked, and then shipped it to me. I went to Bell and then their employee set it up with my account, did a factory restore, and then rebooted it. I saw it turn on and work properly in front of my own eyes, but I had to go charge it at home as it was dead.
I get home, connect it to a charger, the orange charging light on the top turns on, and it opens up a menu that says "ClockworkMod Recovery v5.8.3.1" The options below say: Reboot system now, install zip from sdcard, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, and advanced.
Now, at the Bell store we factory reset, and rebooted the system, and then the phone worked. However, now when I press "reboot system now," it goes black, the orange charging light turns off, and then it gets frozen on the "HTC One, quietly brilliant" screen. It stays that way until it dies, and I can't even hard reset while it's frozen. It is completely frozen. I even tried to connect it to HTC Sync Manager, but when I plug it in, nothing happens. It doesn't detect the phone. I'm on a Macbook Pro, for context.
Help? I can't even do anything on my phone, and being a new Android user, I have no idea what to do.
Click to expand...
Click to collapse
Well you can flash an RUU to get the stock rom back, it will get rid of the recovery and you will be able to start from stock.
kvestas said:
Indeed the power button is quite sensitive on HOV so you might need to keep trying several times when using it.
Holding power button is a hard shut down and it shouldn't ask you to confirm this action. It's ok. Unless you have the system already started it may ask you for reboot options. Even in this case the phone will shut down if you'll still keep the power button down for a long time.
At first you may try the simplest thing I guess. Start recovery (you might remember it should start automatically when you turn off the phone and plug in a charger) and choose the menu option "wipe cache partition". Restart the phone after clearing the cache. There is a small chance but this might help.
If not you have to continue your research with adb commands.
Another option is to asquire sd card, I think it would be easier for you when you are using mac.
Click to expand...
Click to collapse
Yeah, unfortunately the cache partition isn't working. If I buy a SD Card, and I put it in my phone and start, what do you anticipate will happen? Because it's fresh, will it load up as if I am turning on the phone for the first time, or will that depend on whether or not my problem is related to the ClockworkRecovery or the phone itself? Sorry for all the questions, but I really appreciate the help.
parthinhell said:
Well you can flash an RUU to get the stock rom back, it will get rid of the recovery and you will be able to start from stock.
Click to expand...
Click to collapse
Thanks for the feedback, but unfortunately, I mentioned my computer doesn't recognize it because based on the research I did, flashing an RUU requires the computer to recognize the device and that didn't work, so that seems to not be an option.
AlvinTheChoster said:
If I buy a SD Card, and I put it in my phone and start, what do you anticipate will happen?
Click to expand...
Click to collapse
You will be able to place ROM file on sd card (using a computer), insert the card into your phone and install new ROM through recovery. Be aware you might need an adapter to use micro sd card on your pc (usually they have a general size sd socket).
You might need to try installing several ROMs because we don't know which kernel has been flashed by Bell guys earlier.
AlvinTheChoster said:
Yeah, unfortunately the cache partition isn't working. If I buy a SD Card, and I put it in my phone and start, what do you anticipate will happen? Because it's fresh, will it load up as if I am turning on the phone for the first time, or will that depend on whether or not my problem is related to the ClockworkRecovery or the phone itself? Sorry for all the questions, but I really appreciate the help.
Thanks for the feedback, but unfortunately, I mentioned my computer doesn't recognize it because based on the research I did, flashing an RUU requires the computer to recognize the device and that didn't work, so that seems to not be an option.
Click to expand...
Click to collapse
OK so get yourself a micro SD card pal and stick a ROM on it. If possible find out form your sister/friend what the previous ROM was so we can all take a guess at what kernel you have on the phone and so select a ROM that will work with it straight away.
As a point of interest did the phone have an SDcard in it at the shop when it booted?
Also could you try doing the three full wipes on the phone from ClockWorkMod. These are
-Factory reset
-Clear Cache
-Advanced Options --> Wipe Dalvik
Then reboot?
regards