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.
Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Paulius Sirv said:
Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*
Click to expand...
Click to collapse
Did u wipe the system file and data before flashing new ROM?
redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
Ive tried your technique, few times actully. Phone does not want to show any indication of life. I might have flashed the rom on low battery I just found out that the cable I was using to flash roms ir damaged and does not function properly. Now Im using a new power cable to charge the device but still, no signs of life.
Thank you very much for helping
justinchao740 said:
Did u wipe the system file and data before flashing new ROM?
Click to expand...
Click to collapse
Revolution HD has a aroma installer, I wiped it during instalation process
Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Paulius Sirv said:
Revolution HD has a aroma installer, I wiped it during instalation process
Click to expand...
Click to collapse
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand
sayad1 said:
Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand
Click to expand...
Click to collapse
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).
Paulius Sirv said:
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).
Click to expand...
Click to collapse
Wc reply if this method work for you
redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
I left my phone to charge overnight and the LED light came on (Its a really good sign). At first it was flashing orange, later it was only orange and now its green, so that means that my battery was fully drained. However, I tried holdin power + vol up for atleast 3-4 minutes but nothing happened except that the LED light is not greeen nor orange anymore. If I connect my phone to a pc, in the device manager "Qualcomm HS-usb qdloader 9008" shows up for 20-30 seconds and dissapears, after few secs it reappears again and so on. I was looking for a solution for a few hours and I think I found a decent tutorial how to unbrick it but Im not able to find neccesary firmware for my phone because I dont know my CID (link: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/). Any other ideas?
BTW, thank you very much for trying to help
I've never seen these "unbricking" guides work on this device. If you can't get to at least bootloader, you are probably looking at JTAG, new motherboard, or new phone.
Really, your best bet is to keep playing with the button combos with the charger attached and unattached.
Hello friends.
I got my Pixel XL 2 yesterday and today I'm in trouble already.
I unocked the bootloader, installer twrp and rooted with magik succesfully, but I had trouble installing my apps (titanium backup gave me a parcing error and the googgle play store wanted me to pay again for my purchases for some reason), so I figured I do a factory reset so I get prompted to restore from my old phone via cable. So I went to settings -> factory reset.
The problem is that when android rebooted to erase the data, I instead got dumped into twrp on a screen that says Mount Decrypt Data and is asking me for a lock pattern. But the screen doesn't responds, so I can't proceed. The power hard button just toggles the screen on and off but it does not reboot or turns the phone off when I hold it, so I don't know how to get to my bootloaded to maybe reinstall a factory image or what else to do.
I'm just stuck on that screen without options.
I would very much appreciate any advice.
Hold power, vol up and down buttons until your device turns off.. then go into bootloader by holdind vol down and power
I thank you very much for your reply.
I did booted succesfully into bootloader, but now I'm affraid I jumped from the frying pan into the flame because now my phone doesn't power up at all. If I connect it to the charger I don't get the battery with a lighting bolt that I'm supposed to get. The only life sign I get is if I plug it via USB to my computer, I do get the sound that windows plays when yoy connect something, but other than that, the phone seems to be dead.
I'm guessing it's something with the hardware?
hold the power button till it shuts off
flex360 said:
hold the power button till it shuts off
Click to expand...
Click to collapse
It is off. I can't turn it on at all. It's unresponsive.
BreadedChicken said:
It is off. I can't turn it on at all. It's unresponsive.
Click to expand...
Click to collapse
Was the battery low when you started this?
Are you familiar with ADB? When plugged into the computer type adb devices or fastboot devices does it return your device serial number? If so type adb reboot bootoader.
If not I would hold the power button for a good 20-30 second and see if you can force it to turn on or reboot and immediately hold volume down to get back to bootloader.
BreadedChicken said:
It is off. I can't turn it on at all. It's unresponsive.
Click to expand...
Click to collapse
Did you get anywhere with this? Just curious. I know you're probably upset, we're here to help if we can. :good:
Thank you very much to everyone for your time and help.
Thanks to your advices I was able to solve it. In case anyone ever finds himself or herself out in a similar situation, here's what ended up happening:
After holding the power button for about 30 secs as Namolas sugested the phone did reboot itself and brought me back to that twrp mount decrypt data screen asking me for a lock pattern. It was then just a matter of adb booting to the bootloader and install a factory image as usual.
Thanks again. I appreciate it guys.
First off, I did do a search, but as far as I can tell no one has had this problem so far.
This is all after modding using a tool kit: (i can't include the url but it is the toolkit by neisor on the oneplus forums)
tldr: phone stuck in bootloop, computer wont recognize the phone, maybe because it keeps shutting off and then booting to the 1+ logo, then shutting off again, would drivers help? what can I do about the volume up button?
So for a while my volume up button hasn't been working, and the mega unbrick post shows that I need to hold the volume up button for at least 25 seconds and while holding, plug my phone in. I have also seen some posts that say the volume up button could be a software issue, and the button itself could be working, and it is just not registering, as well as someone saying that you could take the back off and manually press the button, instead of using the bar on the outside of the phone (would this work?). I have gotten the button to work in the past by pressing the volume up button to the side instead of straight in, but I haven't been able to get it to work since my phone got bricked.
Another issue: my phone is stuck in a boot loop, I can't access fastboot, and I'm unsure of recovery because my volume up button is not working. would it be worth it to deal with the constant vibrating to try to get it to recovery?
I have been able to shut the phone off by holding the power button for something like a minute and a half, though.
This is my first post, and if I have broken any rules I am very sorry, but I need help and am tired of not having a phone.
Thank you everyone,
Mark
Edit: this is what I did to root the phone:
1. download the toolkit
2. unlock bootloader (when fastbooting the phone said unlocked at the bottom, and a message about not being secure showed every time I rebooted the phone)
3. flashed twrp (no issues, still booted, recovery went to twrp. for some reason I had to flash multiple times as every now and then recovery would revert to stock op, although I did make a backup through twrp)
4. send supersu zip file to phone, install using twrp (phone would not boot, op logo stayed on phone for 2 hrs + until I rebooted to fastboot and tried to reinstall the backup I made, still nothing)
5. Try magisk (still stuck on op logo)
6. try to go back to stock, accidentally lock bootloader (now the phone is stuck in bootloop, don't know what to do from here as I cant get to fastboot and am unsure of recovery's accessibility.)
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Thanks
150208 said:
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
Click to expand...
Click to collapse
thanks for the correction, I will keep trying the volume buttons, if it doesn't work by the end of today I will search for a new volume button.
Thanks again,
mark
Ouch
badabdba said:
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Click to expand...
Click to collapse
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
MarkTheFur said:
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
Click to expand...
Click to collapse
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
MarkTheFur said:
... what can I do about the volume up button?
Click to expand...
Click to collapse
Can you boot into recovery by pressing power+volume down buttons?
Update: Got phone to show on computer as qualcomm under coms and ports
So last night I went ahead and held volume up for about 20 seconds, then plugged the phone in, keeping the volume up button pressed the entire time. my phone stopped bootlooping and showed up as a qualcom device! So I have downloaded the new driver the stock os, and am going to proceed to try to unbrick my phone.
Wish me luck,
Mark
Yes, I did, and its working so far
tnsmani said:
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
Click to expand...
Click to collapse
I still need to turn off the signed drivers features ( a huge bi*ch, I have to use another computer to contact microsoft or something to get my computer to load when I turn off safe boot or whatever its called), but once I do that I can install the driver and attempt to reinstall the stock os. Hopefully everything will go well.
Thank you,
Mark
Not as far as I know
rk2612 said:
Can you boot into recovery by pressing power+volume down buttons?
Click to expand...
Click to collapse
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
MarkTheFur said:
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
Click to expand...
Click to collapse
Glad to hear that there is some progress. Best of luck and keep us informed.
Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!
Hi,
If you cannot turn on your phone, it'll be difficult to help you. Pressing other 30 sec power button doesn't run ?
In parallel did you contact the Google pixel support ?
It's not to scare you, but I had the same issue on a old Samsung S8 and it was the motherboard 🫤
Hope it's not the case for you !!
Fadey_Fadington said:
Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!
Click to expand...
Click to collapse
So this is in fact just an undocumented Emergency Download Mode that Google Custom Exynos SoC has natively built into it in case of the rare event of a bad boot loader.
I’ve been doing an extreme amount of research lately about bootROM’s, how they communicate, the Driver rule support for interfacing with the phone while it’s Pixel ROM Recovery. The viewable name for the Exynos USB DownLoading mode.
Can I get you to dm me on Telegram? It might be helpful to have more people. I’ll be glad to help in getting this figured out. It could help a lot of other people who don’t have a Pixel 6 too
I have the same issue after trying to update to 1205. I see the Pixel ROM Recovery and a COM port.
If you cannot enter fastboot mode, no way to recover your phone.
Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.
redplayer5 said:
Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.
Click to expand...
Click to collapse
if u can boot into fastboot just flash the latest factory image from google
w_tapper said:
if u can boot into fastboot just flash the latest factory image from google
Click to expand...
Click to collapse
Can I do that even though my device is locked?
Is there a tutorial?
redplayer5 said:
Can I do that even though my device is locked?
Is there a tutorial?
Click to expand...
Click to collapse
nvm i dont think u can do it if bootloader is locked