Related
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 normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .
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.
So, today I've decided to root my Z1 Compact and install some custom roms. I've done this before on many other android phones without any trouble and today is the first time I ran into a brick (not sure whether it's soft or hard, I assume it's hard cause I cannot get into recovery anymore).
Basically, what I did was root the phone using Easyflash (the towelroot method), installed a recovery and then tried to flash PA the same way as I used to do on my other phones, but after the process my phone shut down and only gives a red blinking light while connected to the charger, powering on the device will only make it vibrate. The only thing that seems to "work" is when I hold the volume-up button + power and am connected to my PC, when I do that the device will show a blue LED, but other than that it's still unresponsive.
If anyone knows what to do here, or knows whether I should even bother or not, please tell me. I've tried searching and didn't come up with any relevant results.
Rzarector said:
I've tried searching and didn't come up with any relevant results.
Click to expand...
Click to collapse
"I've tried searching and didn't come up with any relevant results" = I'm lazy.
Try flashing a ftf file and report back. Xperias are different so you need to relearn a little. http://forum.xda-developers.com/showthread.php?t=2631291
Rzarector said:
So, today I've decided to root my Z1 Compact and install some custom roms. I've done this before on many other android phones without any trouble and today is the first time I ran into a brick (not sure whether it's soft or hard, I assume it's hard cause I cannot get into recovery anymore).
Basically, what I did was root the phone using Easyflash (the towelroot method), installed a recovery and then tried to flash PA the same way as I used to do on my other phones, but after the process my phone shut down and only gives a red blinking light while connected to the charger, powering on the device will only make it vibrate. The only thing that seems to "work" is when I hold the volume-up button + power and am connected to my PC, when I do that the device will show a blue LED, but other than that it's still unresponsive.
If anyone knows what to do here, or knows whether I should even bother or not, please tell me. I've tried searching and didn't come up with any relevant results.
Click to expand...
Click to collapse
http://forum.xda-developers.com/sony-xperia-z1-compact/help/lb757-how-to-update-to-rooted-108-t2822957
Just use my guide#5 to wipe the whole phone and reflash everything.
vol up + power will give you blue LED and it is fastboot mode. vol down + power will enter flash mode but no LED light.
XperienceD said:
"I've tried searching and didn't come up with any relevant results" = I'm lazy.
Try flashing a ftf file and report back. Xperias are different so you need to relearn a little. http://forum.xda-developers.com/showthread.php?t=2631291
Click to expand...
Click to collapse
This is the first thing I tried, but it doesn't seem to recognize my phone under windows (even after installing the drivers).
TheEndHK said:
http://forum.xda-developers.com/sony-xperia-z1-compact/help/lb757-how-to-update-to-rooted-108-t2822957
Just use my guide#5 to wipe the whole phone and reflash everything.
vol up + power will give you blue LED and it is fastboot mode. vol down + power will enter flash mode but no LED light.
Click to expand...
Click to collapse
Thanks a lot for the guide, the stupid thing I did was holding the power button and volume down cause it used to be like that with my previous phones. It seems to be flashing now, so hopefully all is well!
EDIT:Flashing ended succesfully but upon booting the phone the only thing I get is a flashing red led, so I'm assuming it's a hardware defect or I did something terribly wrong while flashing a custom ROM.
EDIT2: After holding volume up + power it shut down and then rebooted
I swear, troubleshooting a phone was never this hard/confusing on my HTC/Samsung phones :V but I'm glad it's not a paperweight
I agree that it's very confusing first, but that's mainly because there are so many old, confusing, wrong or incorrect guides. Once you understood how things work in general you start to like it. After getting used to it, I actually feel more comfortable than with my old devices.
Rzarector said:
Thanks a lot for the guide, the stupid thing I did was holding the power button and volume down cause it used to be like that with my previous phones. It seems to be flashing now, so hopefully all is well!
EDIT:Flashing ended succesfully but upon booting the phone the only thing I get is a flashing red led, so I'm assuming it's a hardware defect or I did something terribly wrong while flashing a custom ROM.
EDIT2: After holding volume up + power it shut down and then rebooted
I swear, troubleshooting a phone was never this hard/confusing on my HTC/Samsung phones :V but I'm glad it's not a paperweight
Click to expand...
Click to collapse
If you can get in flashmode and also successfully flashed .ftf but still a no go then you should send it back to Sony.
It's working fine, it just seemed like the phone was still on after flashing. I turned it off by holding power and volume up, and it works fine now.
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
jinakanishi said:
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
Click to expand...
Click to collapse
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
jembot said:
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
Click to expand...
Click to collapse
It had to have been a virus or corrupt os, I restarted into recovery and flashed it to stock and it works perfectly now with no issues, the button was not stuck internally or externally, as pressing it caused no issues as well as if the device button was stuck it should have navigated the recovery menu if it was stuck. either way after flashing it works perfectly so no it wasnt stuck, and besides i have a galaxy s7 active, trying to disassemble that thing is a nightmare