Nexus 5X Stuck In Bootloop ( Not recognized by ADB & Fastboot ) - Nexus 5X Q&A, Help & Troubleshooting

Where to begin...
Okay, so I ended up flashing an incorrect .zip which caused my Nexus 5X to go into a boot loop. Usually, the fix is to go into TWRP and fix what I broke. Unfortunately, TWRP or Custom Recovery does not exist. The endless boot isn't booting far enough for ADB or Fastboot commands. Additionally, my volume down button my device is also broken so therefore I can not manually go into Custom Recovery. Also, I know I have the right drivers needed in my windows 10 machine to read the device. The device is not able to be seen by the computer currently either.
My question is, I am currently at the Firmware Update screen. This is the only screen I can currently go into manually. What is it that I can do from the Firmware Update screen ( Download Mode ) to restore my device?

There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.

KarimKh said:
There is a temporary fix or two so you can get back your data, but not permanent fix. The chipset will keep falling and the phone gonna die.
Click to expand...
Click to collapse
That explains a lot...Lol!

Luckily, there is hope for you!
should work
Can't test it since my device is in a deeper bootloop that requires Qualcomm files that nobody wants to build.

Related

Phone soft bricked after applying software updates

Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload

Help, might have killed my device

Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.

OP3 bricked and now won't boot after MSM

Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
AnnoyingZlatan said:
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
Click to expand...
Click to collapse
If you can get to bootloader, download and flash OOS 5.0.6. If not, try one of the MSM Tools on XDA. There are quite a few of them, search. Please also note that the Tool is different for 3 and 3T.
I had used one of the oldest Tools here on XDA a couple of times without any hiccups.
Did you get a solution to this? I am struggling with the same issue.
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
myserver57 said:
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
Click to expand...
Click to collapse
Did you try to sideload OOS using adb? Try the various versions of OOS.
TNSMANI said:
Did you try to sideload OOS using adb? Try the various versions of OOS.
Click to expand...
Click to collapse
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
myserver57 said:
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
Click to expand...
Click to collapse
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
TNSMANI said:
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
Click to expand...
Click to collapse
Thanks again for trying to help.
Sadly, bootloader is locked so flashing TWRP or even booting to TWRP is a no-go.
I don't think it's a hardware fault since it was working fine before the OTA update, but I guess you never know. Damn, if only sideloading would work, darn thing...

5T - device corrupt

Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.

Categories

Resources