bricked nexus 5x out of nowhere - Nexus 5X Q&A, Help & Troubleshooting

hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers

trier09 said:
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
Click to expand...
Click to collapse
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.

indian84 said:
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
Click to expand...
Click to collapse
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend

trier09 said:
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
Click to expand...
Click to collapse
LG Support it is for you. They have know to replace units that have passed the warranty period by one or two months. Give it a shot

Related

Galaxy Nexus stuck on Google logo boot loop help [GSM]

I am running the stock rom without root and unlock and I got the 4.0.2 OTA update 3 days ago. Today when I do the pattern unlock my phone froze and reboot. Now I cannot get pass the Google logo boot screen.
I am able to get into the recovery mode but I don't want to do a factory restore as I don't have anything backup yet.
Is there any solution to this boot loop problem? I am surprise that I am getting this problem as I am running the stock rom without any root / mod.
If there is no solution to this, is there any way I can backup my phone before doing the factory restore?
Many thanks!
You can back up via adb. Try searching in the General threads, since there's a long topic on this...
Good luck!
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
When i got stuck at the Google screen with a bootloop i booted into the bootloader/fastboot screen with vol up+down power and i redid the one click all process and it basically rewiped my device and put it back to working again with unlocked bootloader rooted etc....
All you have to remember is what build number you have and let the toolkit work its magic.
tigersgt said:
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
Click to expand...
Click to collapse
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
danger-rat said:
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
Click to expand...
Click to collapse
I can't find a way to backup without going into Android. I can only go to Fastboot Mode.
Anyone know how to backup the file using abd without getting into android?
Why did make 2 threads about this. Unlock the boot loader and use adb to flash your stock. Image files. You will loose all data unfortunately but I think that's the only way to fix it.
Sent from my Galaxy Nexus using xda premium
Ok I'm stuck with the same problem now. I wanted to flash a ROM, so I downloaded AOKP, flashed it and rebooted and the phone refuses to boot past the Google logo and keeps rebooting again and again. I am able to get into the recovery. I have flashed the ROM several times and its still the same. I have done a complete wipe as well. Still no go.
Fastboot command doesnt work in the bootloader either. I have made sure the drivers are installed, still there is nothing when I type fastboot devices. If I type any fastboot command it just says <waiting for device> or something like that.
Any other suggestions? :-s

After successful (?) upgrade to MM, can't boot past Verizon screen.

I was on 13B rooted, then flashed the stock system to return to unroot status. Everything worked fine. Plugged into computer and Verizon Upgrade Assistant suggested upgrade to 13C, so I bit. After a 4 hour (!) download of a 2 Gb file, the upgrade install proceeded without incident, and resulted in a successful completion according to the Assistant. Phone started booting and the Upgrade Assistant re-read the phone as being on 13C, but, the phone stalls and refuses to boot past the Verizon red splash screen. I have pulled battery and tried numerous times to boot, with no luck. It just sticks at the same spot.
Any suggestions? I'm nervous about re-flashing 13 B for fear of bricking it, so perhaps flash 13C kdz?
Thanks in advance for any help.
I have now tried flashing the 13C kdz unsuccessfully a number of times. I verified the checksum on the downloaded kdz file, and attempted to flash it on three separate computers where I had successfully flashed the G4 in the past. Each time that I tried flashing the 13C it reads: "Required Information cannot be found. Contact the system administrator."
I am still stuck here. Even in the flash tool, the phone is read as having 13C on it, but it still will not boot past the Verizon splash screen. Any thoughts on whether I should dare try flashing 13B, or would I end up with even more of a brick then I have now?
Thanks again.
DO NOT FLASH 13B!
Isn't Android 6 24c?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
fr4nk1yn said:
DO NOT FLASH 13B!
Isn't Android 6*?
I got stuck on the Verizon screen, but a wipe fixed it at that point.
Click to expand...
Click to collapse
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Katmeat said:
Thanks, and you are correct on the number, MM is 24C.
May I ask, how were you able to wipe when stuck on the Verizon splash screen? I would love to do that if possible.
Thanks again.
Click to expand...
Click to collapse
Hold volume down and power on if I remember correctly to put the phone in recovery mode. From there you can choose to do a wipe/factory reset.
I had issues with way long boot times, the wipe fixed that, but then apps kept FC. I ended up downloading the KDZ file and used the flash tool to reflash 24C. Everything is stellar now.
Thank you so much, mikeewhite! I followed your instructions and they worked perfectly, so I am back up and running. You are the reason that I love this list so much, as there are so many people like you generous with their time and advice.

Help! Soft brick, but I can't solve

OK, I flashed full Nougat factory image with flash-all bat file, now it bootloops. Tried restoring a nandroid and still bootloops...
Flashing marshmallows factory image, still bootloops.
I can access bootloader and recovery.
I have no solution yet, but I'm on same boat. My phone gets stuck at google dot animation.
I tried adb sideload for almost all Images in nexus stock factory webpage. It installs successful but gets stuck again at same point.
It appears everyone is having same problem. Google forum is filled with same issues. Waiting for something official fix or some genius on xda to solve this.
vmchakka said:
I have no solution yet, but I'm on same boat. My phone gets stuck at google dot animation.
I tried adb sideload for almost all Images in nexus stock factory webpage. It installs successful but gets stuck again at same point.
It appears everyone is having same problem. Google forum is filled with same issues. Waiting for something official fix or some genius on xda to solve this.
Click to expand...
Click to collapse
I can't even get into recovery, only bootloader. Did anybody ever solve this?
mr.gpvecchi "incredibly", the same situation as with me.I just fell in love with this phone :crying:
I hope end wait.
----------------------Sorry for my english----------------------
I bought my phone through Project Fi and I chatted with them and they said I will be able to get a replacement. Also, I just read this: https://productforums.google.com/forum/#!topic/nexus/89jWX-WVap8;context-place=forum/nexus
Looks like a few other people had the same problem today. Fi support told me "Seen this plenty of times. One of the issues I dislike the most."

Boot Looping Help Please

I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state

Stuck at Google logo

I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.

Categories

Resources