Suggestions for things to try with bricked 5x - Nexus 5X Q&A, Help & Troubleshooting

I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...

olm3ca said:
I was getting a notice on boot that said "Your device is corrupted and cannot be trusted," so I held down the power and volume down buttons to get it to fastboot mode. However, I couldn't get it to be recognized in fastboot on my laptop. At one point I selected "reboot bootloader" and the phone promptly shut off, black screen and completely unresponsive.
From that point on, I can't get it to do anything. I've tried holding power + volume down for 20 seconds and then plugging it in (as noted in another thread) as well as taking it apart and disconnecting the battery to see if that would reset it somehow. No dice.
Any other suggestions before I give up? Thanks very much in advance...
Click to expand...
Click to collapse
my device is for the most part of the time in qualcomm mode, but I managed to have access to the phone 3 days ago, installing apps & stuff, worked perfectly well until I had
the bad idea to try to charge it through the charger instead of charging it through my computer...
how I've done it?
I used the power reboot technic :
1) pressing the power button for 1 minute
2) doing nothing for some seconds
3) pressing the power button again for 1 minute
4) connecting the phone to the charger, the red light flashed
5) the battery icon appeared soon after
6) waiting for complete charge, phone rebooting
it worked once, so I suppose it can work again. fingers crossed.

Related

[Q] Bootloop help (cannot access fastboot/adb)

I just rooted and S-off my HTC via rumrunner.
No flash roms install or custom recovery installed.
I wanted to see if I still had CWM from my last root (I returned to stock via http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on.
So I went into the bootloader or fastboot (I don't remember) and hit recovery. This did not send me to a CWM, but it appeared to be the stock version of recovery. The process took too long (I know impatient) so I turned it off via power button + volume down.
Now I come to you in need, my phone is constantly turning off/on only displaying the green htc text, no red text, then pausing for 8 seconds, then off again to black screen. The whole process lasts 12 seconds, and this had been going on for about 10-15 min atm.
Plugging it in, my computer does not have the time to recognize it with adb, or fastboot.
I cannot use the power button + volume down to go into bootloader, and pressing the power button does nothing.
Please help me.
So the problem still persists and I assume it's going to keep turning on and off for a while.
I'm just going to wait until the battery dies and see if it can charge and turn it back into bootloader. I'll report back on that.
On a side note in the case that this is bricked, anyone recommend any future phones out there better than the one with verizon? If not I'm probably just going to stick to this phone.
geeibara said:
So the problem still persists and I assume it's going to keep turning on and off for a while.
I'm just going to wait until the battery dies and see if it can charge and turn it back into bootloader. I'll report back on that.
On a side note in the case that this is bricked, anyone recommend any future phones out there better than the one with verizon? If not I'm probably just going to stick to this phone.
Click to expand...
Click to collapse
Hold down the volume down and power button at the same time, until the white hboot menu appears.
This may take a good 15 seconds or more, keep holding them down until the hboot menu appears.
Sounds like you aren't holding down long enough. If that doesn't work, try both volume up and down and power all at once.
Then when the screen goes black, let up on the up volume key, so that you enter fastboot via volume down and power.
Then you should be able to fastboot flash whatever you need to get back up and running again.
I wouldnt just let it keep looping until it dies though.
Probably won't damage anything but I doubt that it's real great for the device.
santod040 said:
Hold down the volume down and power button at the same time, until the white hboot menu appears.
This may take a good 15 seconds or more, keep holding them down until the hboot menu appears.
Sounds like you aren't holding down long enough. If that doesn't work, try both volume up and down and power all at once.
Then when the screen goes black, let up on the up volume key, so that you enter fastboot via volume down and power.
Then you should be able to fastboot flash whatever you need to get back up and running again.
I wouldnt just let it keep looping until it dies though.
Probably won't damage anything but I doubt that it's real great for the device.
Click to expand...
Click to collapse
So here's the update.
Screen is now black, meaning the boot up/down process has stopped.
I have tried these:
A. Hold down the volume down + power button for 20+ seconds.
B. Hold down the volume up + volume down + power button for 20+ seconds and let up on the volume up button when screen goes black.
These two methods results in a single boot up to green HTC text then black screen.
I suspect the device has lost most of its power. Tried it for a third time, the device is now unresponsive and remains at black screen.
Now I plugged the usb cable connected to the power adapter.
The device enters the aforementioned continuous boot loop.
I tried method A and B, and there are no results, the boot loop continues. Now the device returns to the low or no powered state.
Now the device is connected to the computer. The same happens as if it were connected to the power adapter.
Method A and B still do not work.
Results: holding down buttons longer do nothing for me. The device seems to have lost power, but when charged, immediately the device enters the boot loop state.
Note: when doing method A and B the trials were done when screen is on and when screen is off, still no results.
Now the screen is off and not connected to anything. The problem still persists.
ak074 said:
leave the phone charging for at least 10-15 min on the AC adapter. press and hold both vol buttons then press and hold power for 2+ minutes. after 2 minutes, let go of all buttons except volume down. success?
---------- Post added at 10:10 AM ---------- Previous post was at 09:40 AM ----------
actually doing that will destroy the battery. well maybe destroy is too strong of a word but it will damage it for sure. this is a very useful site for anything battery...
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Click to expand...
Click to collapse
I actually tried the 2+ minutes because I saw someone had success with another phone and they said they did it for 3 1/2 min. However it did not work.
Update: Welp, I gave up. I'm going to get my replacement soon and I'll be turning it into Verizon. Really it's not that bad of a loss since I just wiped the phone, only thing is I lost my screen protector and carbon skin
ak074 said:
have you tried to just let the phone bootloop while holding vol down?
Click to expand...
Click to collapse
Yep, nothing happened.
Bootlooped too!
Hello I have a HTC Thunderbolt that is S-ON Unlocked and unrooted with stock recovery that is in a bootloop that does now show on ADB or Fastboot. PLEASE HELP!!!!! I REALLY NEED IT!!

[Q] Phone won't boot

Yesterday my phone was taking a really long time to do something simple (open an app I use all the time or something) and it was unresponsive to the normal power button function, so I pressed and held the power button until the phone turned off. I put it back in my pocket and forgot about it (at work). A few hours later I went to use my phone and it was nearly entirely unresponsive. If I press the power button it vibrates briefly and then does nothing. Same behavior after plugging in USB for power and after letting the phone charge for a while. I've also tried removing and replacing the battery and removing the external SD card.
I'm also not able to boot into recovery (TWRP installed). When I press and hold the volume up and down keys while booting the phone, I see SAMSUNG flash briefly and then the phone seems to shut back off.
Any ideas for recovery?
Thanks
Never mind, figured it out
greenmaze said:
Never mind, figured it out
Click to expand...
Click to collapse
It would be nice if you let us know what you did to fix it? Because my phone is now doing the same thing.

Hard reset fastboot is enabled

Hello everyone, my girlfriend is having an issue where her m8 won't turn on. We looked at it last night and put it on the charger (although we didn't expect it would be dead already) and then left it over night. Woke up this morning and it's still having the same issue. I tried doing both a hard reset and soft reset, just anything to get it out of this weird loop it's in. Everywhere I look for information on hard resetting it says you need to disable fastboot - something a little difficult to do if your phone won't turn on. Are there any other tricks or work arounds that maybe I'm overlooking? I'd prefer to stay away from 3rd party fixes if possible that will void the warranty as I don't want her phone to get rejected if we need to send it out for repair. The closest repair facility is a bit of a distance so I want to see if there is something we can do from home first.
Thanks!
Disabling the "fastboot" option isn't really necessary.
Although I'm not sure what "weird loop" means. If its actually doing a boot loop, and rebooting, then just hold vol down to enter bootloader.
Otherwise, if its just "stuck" on the boot screen, then hold power and vol up to force a reboot (hold for maybe 10 seconds or so); and the moment the screen goes dark, let go of vol down and start holding vol down and don't let go until you see bootloader.
redpoint73 said:
Disabling the "fastboot" option isn't really necessary.
Although I'm not sure what "weird loop" means. If its actually doing a boot loop, and rebooting, then just hold vol down to enter bootloader.
Otherwise, if its just "stuck" on the boot screen, then hold power and vol up to force a reboot (hold for maybe 10 seconds or so); and the moment the screen goes dark, let go of vol down and start holding vol down and don't let go until you see bootloader.
Click to expand...
Click to collapse
My apologies, my terminology may be incorrect.
The display is not turning on. Holding power + volume up or power + volume down do not get the screen to turn on.
The instructions I looked at all say disable fastbooting before trying to force boot or hard reset. So that was my confusion.
I really appreciate the help.
JoshOohAh said:
The display is not turning on. Holding power + volume up or power + volume down do not get the screen to turn on.
Click to expand...
Click to collapse
Any charging LED when charger connected? Any response from computer if you connect the phone?
Leave the phone on charger (wall charger, not connected to a computer) overnight, and try the button combos again (also, try just holding power down, no other buttons; in addition to the button combos you listed). Try this with the charger connected, as well as without.
Some folks have gotten their seemingly dead M8's to revive with apparently random combinations of button pressing (often holding the buttons for a long time, 1 to 2 minutes) charger plugged in, etc.
JoshOohAh said:
The instructions I looked at all say disable fastbooting before trying to force boot or hard reset. So that was my confusion.
Click to expand...
Click to collapse
The only reasons instruction say that, is that the phone either needs to be "real" power off, or a reboot in order for the button combo to go into bootloader (power + vol down) to work. When "fastboot" is selected in Power settings, it actually prevents a real power down (its actually just a sleep state). But if you reboot, it doesn't matter. A reboot is a reboot, it doesn't matter if "fastboot" is enabled. And Power + vol up is one way to force a reboot.
None of this matters, if the phone is not responding (screen not coming on) at all in the first place.
redpoint73 said:
Any charging LED when charger connected? Any response from computer if you connect the phone?
Leave the phone on charger (wall charger, not connected to a computer) overnight, and try the button combos again (also, try just holding power down, no other buttons; in addition to the button combos you listed). Try this with the charger connected, as well as without.
Some folks have gotten their seemingly dead M8's to revive with apparently random combinations of button pressing (often holding the buttons for a long time, 1 to 2 minutes) charger plugged in, etc.
The only reasons instruction say that, is that the phone either needs to be "real" power off, or a reboot in order for the button combo to go into bootloader (power + vol down) to work. When "fastboot" is selected in Power settings, it actually prevents a real power down (its actually just a sleep state). But if you reboot, it doesn't matter. A reboot is a reboot, it doesn't matter if "fastboot" is enabled. And Power + vol up is one way to force a reboot.
None of this matters, if the phone is not responding (screen not coming on) at all in the first place.
Click to expand...
Click to collapse
I did leave it on the wall charger last night and was playing with different combinations. I'm going to try plugging it into my computer when I get home. I'm not noticing any LEDs come on however which is what is making me think it's not a screen issue.
redpoint73 said:
None of this matters, if the phone is not responding (screen not coming on) at all in the first place.
Click to expand...
Click to collapse
JoshOohAh said:
I did leave it on the wall charger last night and was playing with different combinations. I'm going to try plugging it into my computer when I get home. I'm not noticing any LEDs come on however which is what is making me think it's not a screen issue.
Click to expand...
Click to collapse
I recall reading that someone got a similar issue sorted by hold Volume Up or Volume Down + Power button while holding the phone under a bright light(proximity sensor at the front needs to be directly under light).
There was similar threads/methods on the old HTC One(M7) too that apparently worked. Don't know if it's just coincidence or what Might be worth a shot.
Edit: Volume UP OR Volume down, not both at the same time
BerndM14 said:
I recall reading that someone got a similar issue sorted by hold Volume Up or Volume Down + Power button while holding the phone under a bright light(proximity sensor at the front needs to be directly under light).
There was similar threads/methods on the old HTC One(M7) too that apparently worked. Don't know if it's just coincidence or what Might be worth a shot.
Edit: Volume UP OR Volume down, not both at the same time
Click to expand...
Click to collapse
Seems goofy - but no luck! Thanks for the input though.
Any other suggestions?
JoshOohAh said:
Seems goofy - but no luck! Thanks for the input though.
Any other suggestions?
Click to expand...
Click to collapse
Have you tried holding Power and Vol Up button when the phone is pluged in?
Tri taking SD Card and SIM card out and start.
Have you tried another charger?

Phone not bricked, but usually won't boot in any way

Hello everyone, thank you for your time.
TL;DR: Phone boots into download mode up until "Downloading...", recovery mode until "RECOVERY BOOTING," and can only boot right when I put the battery in. The battery is fully charged, and I can boot up until my home screen only once so far. Will a jig fix the issue, or should I try to get the phone replaced by TMobile warranty as I have before?
I have a Galaxy S3 from TMobile, and have been running CyanogenMod for about a year now. 2 days ago I flashed a nightly release, which I assume was unstable. Yesterday, my screen was on and then my phone turned off (low battery, but 99% sure it was a crash rather than a power off), and did not boot up again. After attempting to pull the battery out, charge for hours, turn on and plug in (in different combinations), the furthest I could get was a couple of seconds of the CyanogenMod Galaxy S3 logo initial boot screen (not the rotating splash screen).
I took my phone to TMobile today and was about to get it replaced until I realized I didn't mask the flashes.
The last time I was in an exact same situation with the same phone model, and my flash counter was still showing custom firmware, yet I did manage to get it replaced effortlessly, but I didn't want to risk what was a possible fluke again.
I get home, and here's my current situation.
The only way the phone boots up in any manner is when I take the battery out and the charger is not plugged in. Here are the scenarios I run into:
1. Boots into download mode, can press VOL + to get to the "Downloading..." screen, then shuts off 2 seconds after.
2. Boots into recovery mode, only up until "RECOVERY BOOTING", then shuts off.
3. Boot by pressing power button, plug charger in, shows grey battery icon.
3. Boots into download mode, can press VOL -, either shuts off, OR
3b) Only after tons of tries, it booted up all the way up until my actual home screen, then shut off.
I can't have the charger plugged in while booting (pc or wall), and I can only boot right after I put the battery in.
Are there any suggestions as to what I should do? I was thinking of buying a jig from Amazon, but I don't know if it is hard bricked or not. Should I just attempt to get it replaced under warranty once again, even though it shows the flash count?
Thank you very much!
FIX: STUCK POWER BUTTON PROBLEM
So, one thing I didn't check. Take the battery out of the phone, wait about a minute. If it buzzes as if its powering on, that means that your power button (either the actual button itself or the switch on the mainboard) is stuck.
Solution: Smack the power button with your battery until your battery has a (small) dent. If it doesn't work, smack it a couple more times. Took me 2 tries, second try, phone didn't buzz when I put battery in. I press the power button, works like new. Absolutely....ridiculous

January 2017 patch bricked my Pixel XL 128GB?!

Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Have you held power and volume down for 14 seconds?
vincent.lorentz said:
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Click to expand...
Click to collapse
How long have you had it plugged in? It sounds like the battery is empty.
Try to leave it on the charger for a couple of hours.
If it does not boot by pressing the power button, you can try to boot bootloader by pressing volume down and power at the same time.
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
vincent.lorentz said:
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
Click to expand...
Click to collapse
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Golf c said:
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
vincent.lorentz said:
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
Click to expand...
Click to collapse
Your screen may be black, but there is a small chance your still in the bootloader. I have read that other people have recovered from a black screen. I still think its worth a try to connect to a PC and see if the factory image flashes after holding power and volume down and after vibration. Those vibrations have meaning.
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
vincent.lorentz said:
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
Click to expand...
Click to collapse
I thought there might be a small chance. At least you will get a new phone. Best of luck.
I hate to tell you this but I had the same issue with a 32 GB 5 inch pixel...It was dead...Everything you have said is what happened with mine.
What happened was the slot the phone was trying to boot into had no bootloader or it was a bad flash...Either way, the slot didn't have a bootloader on it when it tried to boot and that black screen is the result...Google sent me a new one and all was well and they will do the same for you.
This is why I don't trust OTA updates...I manually flash everything and I'm sure to flash the bootloader to both slots anytime I update my phone...Good way to keep this from happening again....Best of luck man
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Thank you very much for your kind support, guys.
Your explanations is very interesting. This means that the strategy implemented for the bootloader itself is not very safe. I would be interested in knowing how such a faulty flash can happen and what are the possible reasons behind. Is there a procedure that can increase the chances for a successful flash by doing some things before the OTA update is allowed to be installed?
xocomaox said:
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Click to expand...
Click to collapse
Believe me, I pressed the button for a very long while also (hours) by blocking the button in such a was that the phone boots up until the battery is discharged. So also such an extreme tray was made. The only consequence was the red light flashing.
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
droidan said:
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
Click to expand...
Click to collapse
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
5.1 said:
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
Click to expand...
Click to collapse
Yes. Bad OTA Flash.
Hold 30secs still nothing.
droidan said:
Yes. Bad OTA Flash.
Hold 30secs still nothing.
Click to expand...
Click to collapse
RMA is your only option so

Categories

Resources