HTC 10 - Rooted - S-ON - Unlocked - Sprint - 2.42.651.63
********************************************************
My HTC 10 decided to have some sort of a system crash the other day. The phone was around 90% when this all occurred and I was not doing anything out of the ordinary when the screen just decided to go black and stay black. It never changed, just stayed right there. In order to shut down the phone, I held down the VOLUME DOWN and POWER buttons at the same time. After this, the phone was completely unresponsive. It would not charge, would not boot and the LED wouldn't even light up to show that it was charging.
After many attempts at trying different key combinations and charging it from anywhere between 10 minutes to 3 hours and attempting the different key combinations again, I was left with a paperweight. It would not do anything at all.
I attempted to charge the phone again over night, but the LED, nor the screen ever lit up. I also noticed that the charger was not warm to the touch as it would be if it was charging, so I determined that the phone in fact was not receiving a charge.
I unplugged the phone and let it sit over night again. I simply hit the power button and it turned on but then froze on the boot screen. I held down the VOLUME DOWN and POWER buttons at the same time to shut down the phone. (My theory here is that it needed to drain whatever power was left in the battery, but honestly, I have no idea).
Tried to power it up again and nothing. Waited about 20 minutes and then plugged the phone in. It was now charging, however it was still unresponsive to any attempt to power the phone on.
I held down the VOL UP, VOL DOWN and POWER buttons at the same time for about a minute and a half to enter the bootloader. I had to LET GO of them all AS SOON AS the bootloader vibrated and the screen turned on. If I did not, I had to repeat the process. Once there, I attempted to enter recovery and the phone just shut off. I repeated the process to enter the bootloader again, this time attempting to enter download mode. It worked, but download mode states that there is a "MODE ERROR" and all of the phone's information (Radio, Serial number, Etc.) either said "ERR" or "UNKNOWN".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This brings me to where I am stuck now. Anybody have any thoughts? Any help is appreciated greatly.
I am at the moment attempting to relock my bootloader in order to flash a stock recovery. I am receiving an error here too, saying that I am not unlocked, yet my device clearly says "UNLOCKED".
z0ne_tripper said:
HTC 10 - Rooted - S-ON - Unlocked - Sprint - 2.42.651.63
********************************************************
My HTC 10 decided to have some sort of a system crash the other day. The phone was around 90% when this all occurred and I was not doing anything out of the ordinary when the screen just decided to go black and stay black. It never changed, just stayed right there. In order to shut down the phone, I held down the VOLUME DOWN and POWER buttons at the same time. After this, the phone was completely unresponsive. It would not charge, would not boot and the LED wouldn't even light up to show that it was charging.
After many attempts at trying different key combinations and charging it from anywhere between 10 minutes to 3 hours and attempting the different key combinations again, I was left with a paperweight. It would not do anything at all.
I attempted to charge the phone again over night, but the LED, nor the screen ever lit up. I also noticed that the charger was not warm to the touch as it would be if it was charging, so I determined that the phone in fact was not receiving a charge.
I unplugged the phone and let it sit over night again. I simply hit the power button and it turned on but then froze on the boot screen. I held down the VOLUME DOWN and POWER buttons at the same time to shut down the phone. (My theory here is that it needed to drain whatever power was left in the battery, but honestly, I have no idea).
Tried to power it up again and nothing. Waited about 20 minutes and then plugged the phone in. It was now charging, however it was still unresponsive to any attempt to power the phone on.
I held down the VOL UP, VOL DOWN and POWER buttons at the same time for about a minute and a half to enter the bootloader. I had to LET GO of them all AS SOON AS the bootloader vibrated and the screen turned on. If I did not, I had to repeat the process. Once there, I attempted to enter recovery and the phone just shut off. I repeated the process to enter the bootloader again, this time attempting to enter download mode. It worked, but download mode states that there is a "MODE ERROR" and all of the phone's information (Radio, Serial number, Etc.) either said "ERR" or "UNKNOWN".

This brings me to where I am stuck now. Anybody have any thoughts? Any help is appreciated greatly.
I am at the moment attempting to relock my bootloader in order to flash a stock recovery. I am receiving an error here too, saying that I am not unlocked, yet my device clearly says "UNLOCKED".

This brings me to where I am stuck now. Anybody have any thoughts? Any help is appreciated greatly.
I am at the moment attempting to relock my bootloader in order to flash a stock recovery. I am receiving an error here too, saying that I am not unlocked, yet my device clearly says "UNLOCKED".

Click to expand...
Click to collapse
Outside of trying to flash a RUU, I'm not sure what options you have outside of sending it in for service.
@OMJ @Captain_Throwback Do either of you have any suggestions?
Magnum_Enforcer said:
Outside of trying to flash a RUU, I'm not sure what options you have outside of sending it in for service.
@OMJ @Captain_Throwback Do either of you have any suggestions?
Click to expand...
Click to collapse
I cannot seem to flash and RUU without being S-OFF. I've tried multiple ways with no luck. And isn't the warranty void with it being "SOFTWARE MODIFIED" and "UNLOCKED"? I'm not sure they will fix it.
So after hours of experimentation, I have determined that in its current state, the only functions that I have are SOME fastboot commands. ADB does not work and Recovery hasn't worked since the very beginning. The phone will not "REBOOT" into any mode. By selecting any of these type of options, the phone simply shuts off. The ONLY way to get it to turn on is by holding down the VOL UP, VOL DOWN and POWER buttons for that minute and a half.
Would formatting a partition via fastboot help me at all? Or possibly using the "flashall" command?
Sounds like a hardware failure. I doubt there's much you can do.
Adb does not work in bootloader or download mode, only fastboot
You would need to flash stock recovery before locking bootloader. Once you’ve locked, you won't be able to do much and since the phone won't boot you won't be able to unlock again.
I would attempt to flash stock recovery, then chat with HTC support to get it repaired, it shouldn't matter even if it's unlocked
Sent from my unknown using XDA Labs
OMJ said:
Sounds like a hardware failure. I doubt there's much you can do.
Adb does not work in bootloader or download mode, only fastboot
You would need to flash stock recovery before locking bootloader. Once you’ve locked, you won't be able to do much and since the phone won't boot you won't be able to unlock again.
I would attempt to flash stock recovery, then chat with HTC support to get it repaired, it shouldn't matter even if it's unlocked
Sent from my unknown using XDA Labs
Click to expand...
Click to collapse
Thank you. I am not even sure I can flash a stock recovery. I've tried pretty much every way possible. I think i'm just gonna have to send her in. Hopefully this serves as reference for somebody not to waste their time on this if this happens.
z0ne_tripper said:
Thank you. I am not even sure I can flash a stock recovery. I've tried pretty much every way possible. I think i'm just gonna have to send her in. Hopefully this serves as reference for somebody not to waste their time on this if this happens.
Click to expand...
Click to collapse
I would attempt to flash stock recovery, from download mode: fastboot flash recovery nameofrecovery.img
if it don't flash, I wouldn't worry too much about it, u don't have much to lose by sending it to HTC...if there's a hardware failure, they may not even know u had twrp on it
OMJ said:
I would attempt to flash stock recovery, from download mode: fastboot flash recovery nameofrecovery.img
if it don't flash, I wouldn't worry too much about it, u don't have much to lose by sending it to HTC...if there's a hardware failure, they may not even know u had twrp on it
Click to expand...
Click to collapse
It's in the mail to HTC as of 15 minutes ago. Fingers crossed lol.
z0ne_tripper said:
It's in the mail to HTC as of 15 minutes ago. Fingers crossed lol.
Click to expand...
Click to collapse
good luck!
OMJ said:
good luck!
Click to expand...
Click to collapse
Thank you :fingers-crossed:
Just wanted to say that I got my phone back today, finally. And it was covered by the warranty, so I didn't have to pay a dime. I am now re-rooted and ready to go. Thank you guys for your help.
Well... It happened again. Slightly different this time. The phone powers on just fine but enters a bootloop. Trying recovery just causes it to reboot. I can get to the bootloader but cannot enter download mode. Last time I could enter download mode but it said "Mode Error". I don't really want to send my phone back for another month and a half. Any help would be greatly appreciated.
same exact issue here. Sprint model turned off and just died, finally got into fastboot/download mode but MODE ERROR and all polling of hardware says ERR on the screen. you posted an excellent summary of the symptoms...unfortunately it seems like a emmc corruption or something to me, especially since it failed again after HTC fixed yours. luckily, I bought mine on ebay less than a month ago so I can return it. I hope you were able to get a new model from HTC directly.
Related
I've got a new (or refurbished, can't tell) Desire from HTC customer care yesterday, i rooted/s-off, and was playing with it withoout any issue. Then i booted in fastboot mode, trying to flash a custom splash image, but fastboot got stuck on the message "waiting for device". I waited for a while, then chose the option "reboot bootloader". Tried using fastboot again, but still the same. Tried to reboot into recovery, but the phone was stuck at the alpharev splash screen. I waited some minutes, pulled off the battery and put it back in. The phone doesn't power on. When plugged to pc or AC, the led does not turn on. I also tried removing the sim card, the sd and the battery and plugging it again to AC, but it's still not working. Seems totally dead. Is there something i can try before sending it to HTCfor repair (again!!!)? Will they be able to tell that the phone was rooted even if it is practically impossible to boot it?
did you try to press the power button and the down volume key for about 20 seconds? sometimes that kicks it on. Also htc will not be able to tell if it is rooted or not. I sent one in for repair that was s-off and a custom rom and the same one came back fixed and reflashed with proper rom. I had to s-off and root again. Hope this helps.
I tried holding vol- and power for about 30 seconds twice, but nothing happened. I'll send it for repairs tomorrow. Thanks anyway for the advice.
Sorry your having problems. Good luck.
Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>
c4p3fi3rr said:
Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>
Click to expand...
Click to collapse
Rule #1 when rooting and flashing..... always have a back-up phone. (I keep 3)
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.
I was at work the night before, and my capacitive buttons stopped responding, so I went for a restart in hopes they would kick back on, this just caused my phone to enter a boot loop. Soft resetting and hard resetting both continue the loop, trying to enter recovery mode throws me back into the loop, entering download mode locks the phone on the small HTC screen. I tried to flash the current RUU onto the phone, but it won't proceed with the install due to a low main battery error despite the fact I've had it charging for 6 hours. The only thing I can think of doing now is sending it back in hopes they fix it, but theres a lot of information I ignorantly haven't backed up, and now can't access before sending it back.
If anyone has any helpful tips or ways to move forward I would be grateful.
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
silegeek said:
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
Click to expand...
Click to collapse
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Snickie12 said:
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Click to expand...
Click to collapse
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
Holding Volume up just continued the loop, I can get into the bootloader like you said, but theres not very many options, download locks the phone onto the HTC logo and doesn't proceed, the recovery option just restarts the phone into the loop.
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
silegeek said:
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
Click to expand...
Click to collapse
Whenever I plug it in while off, it shows the low battery icon and tries to turn itself on.
I had exactly the same problem...were you able to sort it out?
same problem except I can charge mine will I be able to ruu even if it is locked ?
isaac1993 said:
same problem except I can charge mine will I be able to ruu even if it is locked ?
Click to expand...
Click to collapse
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
No,it's not. I'm bl ul,s-off,and I can ruu anytime.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
I thought it was charging but now fount out it wont charge
isaac1993 said:
I thought it was charging but now fount out it wont charge
Click to expand...
Click to collapse
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
singlemalt said:
I had exactly the same problem...were you able to sort it out?
Click to expand...
Click to collapse
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Snickie12 said:
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Click to expand...
Click to collapse
Did they tell you what they did to fix it by chance? Thanks.
singlemalt said:
Did they tell you what they did to fix it by chance? Thanks.
Click to expand...
Click to collapse
No they didn't sorry.
singlemalt said:
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
Click to expand...
Click to collapse
My friends s7 completly bricked doing the N update. If you havnt done anything to your phone just take it back and get a new one.
Same exact issue here after the Verizon OTA update.
Failed after the first reboot after the update.
The storage was pretty maxed, wonder if that has something to do with it.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
I have very similar htc 10 issue : (
https://www.reddit.com/r/HTC10/comments/9j8nyk/htc_10_oreo_stuck_in_boot_loop_i_can_only_access/
how do you do fastboot commands when only at bootloader screen when you cant access download mode or recovery : ( also my htc 10 was low on stoage space I must have corrupted the htc 10 oreo : (
Yesterday evening my Google Pixel XL suddenly went off and won't boot anymore. I can get into the fastboot menu, but every option I select(recovery mode, reboot bootloader), doesn't do anything.
The phone is stock android 8.0 and has never been unlocked, rooted or anything. I have tried the following:
- Holding the power button for several minutes, it vibrates every minute(I think this is the simulated battery pull).
- Trying to flash it from fastboot with adb & fasboot, but this doesn't work because I can't unlock the phone from fastboot.
- Left it off for the whole night charging, but also this didn't help, I can still only boot it in fastboot.
I tried some options, but they all require a unlocked phone, which I cannot manage from fastboot mode. Is this just an RMA or are there any other things I can try.
Haven't left stock in a while so not sure if still doable but have you tried --> fastboot boot twrp, then flash the full ota?
same issue
kidh0tsh0t said:
Yesterday evening my Google Pixel XL suddenly went off and won't boot anymore. I can get into the fastboot menu, but every option I select(recovery mode, reboot bootloader), doesn't do anything.
The phone is stock android 8.0 and has never been unlocked, rooted or anything. I have tried the following:
- Holding the power button for several minutes, it vibrates every minute(I think this is the simulated battery pull).
- Trying to flash it from fastboot with adb & fasboot, but this doesn't work because I can't unlock the phone from fastboot.
- Left it off for the whole night charging, but also this didn't help, I can still only boot it in fastboot.
I tried some options, but they all require a unlocked phone, which I cannot manage from fastboot mode. Is this just an RMA or are there any other things I can try.
Click to expand...
Click to collapse
Today I had almost the same thing happen. Was typing then the phone froze. No response. Then turned off. Won't turn on. Can use power and volume down I too can get into fastboot menu, but like you, when i chose anything, i see the Google start screen for a split second and then it turns off again. It seems like it wants to start up but then something is preventing it. This is all stock. Google said go to uFixiBreak, they think its the motherboard and can't do anything. Of course warranty is up. I fear there is nothing to do. Has anyone helped you out yet?
kidh0tsh0t said:
Yesterday evening my Google Pixel XL suddenly went off and won't boot anymore. I can get into the fastboot menu, but every option I select(recovery mode, reboot bootloader), doesn't do anything.
The phone is stock android 8.0 and has never been unlocked, rooted or anything. I have tried the following:
- Holding the power button for several minutes, it vibrates every minute(I think this is the simulated battery pull).
- Trying to flash it from fastboot with adb & fasboot, but this doesn't work because I can't unlock the phone from fastboot.
- Left it off for the whole night charging, but also this didn't help, I can still only boot it in fastboot.
I tried some options, but they all require a unlocked phone, which I cannot manage from fastboot mode. Is this just an RMA or are there any other things I can try.
Click to expand...
Click to collapse
Exactly what's happens with me. In my case i left charging over night and in the morning i couldn't even enter fastboot. Black screen all the time. Holding power button didn't nothing. Using fastboot buttons combination gave me some vibrations and that's all. I had to sent my Pixel to Google for a exchange. Still waiting my replacement device.
Check if warranty still covers your device and starts a RMA for a replacement.
dlhstick said:
Today I had almost the same thing happen. Was typing then the phone froze. No response. Then turned off. Won't turn on. Can use power and volume down I too can get into fastboot menu, but like you, when i chose anything, i see the Google start screen for a split second and then it turns off again. It seems like it wants to start up but then something is preventing it. This is all stock. Google said go to uFixiBreak, they think its the motherboard and can't do anything. Of course warranty is up. I fear there is nothing to do. Has anyone helped you out yet?
Click to expand...
Click to collapse
Cristiano Matos said:
Exactly what's happens with me. In my case i left charging over night and in the morning i couldn't even enter fastboot. Black screen all the time. Holding power button didn't nothing. Using fastboot buttons combination gave me some vibrations and that's all. I had to sent my Pixel to Google for a exchange. Still waiting my replacement device.
Check if warranty still covers your device and starts a RMA for a replacement.
Click to expand...
Click to collapse
Apologies for the late response, I kinda forgot I had this thread here
I started the RMA process the same day and I sent it to Google that day. They replaced the phone with a new/refurbished one that works now. They didn't tell me what the problem was or had any steps I could take to fix the problem(all the steps they had me go through didn't work)
So unfortunately sending it in for a RMA is the only thing I know about that works.
dlhstick said:
Today I had almost the same thing happen. Was typing then the phone froze. No response. Then turned off. Won't turn on. Can use power and volume down I too can get into fastboot menu, but like you, when i chose anything, i see the Google start screen for a split second and then it turns off again. It seems like it wants to start up but then something is preventing it. This is all stock. Google said go to uFixiBreak, they think its the motherboard and can't do anything. Of course warranty is up. I fear there is nothing to do. Has anyone helped you out yet?
Click to expand...
Click to collapse
I am having the EXACT same issue as you. Did you get the recent Android update?
Everybody have 128gb models?
Mine just did the same thing on the 6th last month. I can't boot further than the first Google logo, and OTA images do nothing. Completely stock and locked.
For reference, I have the standard size, 128 GB model. I can at least report that my flash memory is Toshiba, and the ram is from Hynix. I've been emailing with Google support for nearly 3 weeks now, and am unfortunately outside of the warranty.
Louisss15 said:
Mine just did the same thing on the 6th last month. I can't boot further than the first Google logo, and OTA images do nothing. Completely stock and locked.
For reference, I have the standard size, 128 GB model. I can at least report that my flash memory is Toshiba, and the ram is from Hynix. I've been emailing with Google support for nearly 3 weeks now, and am unfortunately outside of the warranty.
Click to expand...
Click to collapse
I have the same model and it won't turn on too,have to RMA
I had this happen back in October, and again in November.
Yes, it happened to the same Verizon Pixel XL 32GB, bootloader unlocked.
A few days after it abruptly shut down. I woke up one morning, and it was fully booted, data intact.
And again in November. I did a full teardown to try and troubleshoot.
It ended up being the oem charger block.
1 broken pin in the block crossed 2 other pins, and that was that.
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??