Develop Bugs

[q] hard bricked

OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman

I can't help... but am in the same boat as of last night with the 5.0 update.

Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.

Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!

im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?

When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.

ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.

tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.

When i boot to recovery i get the TWRP startup screen but stays stuck.

Bump
bump.. any ideas?

i have the same :/

kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."

tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?

NO success because I cannot unlock the bootloader.

Another Bricked Nexus 7 after Lollipop

Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.

this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!

I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".

Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.

Tried all NRT options including force flash.
Problem is none work with the locked bootloader.

Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.

IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?

Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.

Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."

I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!

As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..

Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.

tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..

tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?

dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.

tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does

I ve given up . Bought a Nexus 9. Wasted too much time on this.

Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.

My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.

Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk

[Q] 5x boot loop / soft brick

EDIT: solved. Thanks!
My 5x seems to be in a boot loop / soft brick type of situation. I had the N preview 3 installed, but no unlock, root, etc. I just got it recently and wanted to see how it performed stock (other than N).
I did install CameraX to use slowmo, stabilization, etc. That's actually what I was using when the device rebooted randomly. No big deal, I expected a reboot every once in a while. But now, it's stuck on the "4 dot" animation and won't go any further. Even left it overnight. Finally, after a few manual power-offs with no change, I entered recovery to do a factory reset. That seemed to work, but it still won't boot past the animation.
I would just push a factory image, but I never checked the box in developer options to unlock bootloader. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?

the john said:
My 5x seems to be in a boot loop / soft brick type of situation. I had the N preview 3 installed, but no unlock, root, etc. I just got it recently and wanted to see how it performed stock (other than N).
I did install CameraX to use slowmo, stabilization, etc. That's actually what I was using when the device rebooted randomly. No big deal, I expected a reboot every once in a while. But now, it's stuck on the "4 dot" animation and won't go any further. Even left it overnight. Finally, after a few manual power-offs with no change, I entered recovery to do a factory reset. That seemed to work, but it still won't boot past the animation.
I would just push a factory image, but I never checked the box in developer options to allow ADB. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?
Click to expand...
Click to collapse
Boot into bootloader, ADB works in there.

the john said:
I would just push a factory image, but I never checked the box in developer options to allow ADB. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?
Click to expand...
Click to collapse
It wasn't clear what you were saying, I think you meant you didn't check the box to allow bootloader to be unlocked.
If that is the case, download the full (as opposed to differential) OTA from here
https://developers.google.com/android/nexus/ota
then boot into recovery and flash using adb sideload.
If you actually can unlock the bootloader, then use these images
https://developers.google.com/android/nexus/images
If you get an error during flash, then probably your EMMC is dying.

sfhub said:
It wasn't clear what you were saying, I think you meant you didn't check the box to allow bootloader to be unlocked.
Click to expand...
Click to collapse
Right, that's what I meant -- sorry! I actually did ADB the OTA and it didnt boot. So I used LGUP and refurbished it. Didn't take then, either. As a last resort I did ADB OTA again, and it worked.
Thanks for the response. :good:

Darke5tShad0w said:
Boot into bootloader, ADB works in there.
Click to expand...
Click to collapse
I actually did that, but it didn't work the first time. After trying a couple more times, and on a different computer, it finally worked.
Thanks for the reply.

Bootloop, soft brick?

I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked

shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.

Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...

enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?

UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...

shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.

Mine is @ LG as I haven't bought from Google... Let's see...

talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.

Nexus are impossible to brick, unless you flash stock factory image...

I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus

LG Nexus 5X bootlooping+Device won't go to recovery mode.

So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help

Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.

Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.

ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing

indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:

Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.

This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).

iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.

synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.

aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!

Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.

aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.

I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app