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
Related
XDA,
I just got into a bootloop while on the Facebook App and I pressed the home button. I read that it happens to random people, but I want to make sure that I am safe.
I rooted roughly 5 months ago, when I got this phone and I've never had an issue.
What are my options? If I call VZ/LG will they accept my rooted phone? Or can I fix this bootloop? Will using this method http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 help me ?
Thank you,
-J
EDIT: My phone booted up, the apps were optimizing, but then it just rebooted back to the LG screen and now it's stuck there.
[removed by dentralp]
dentralp said:
Don't want to do fear mongering just keep people in the know...
If you are stuck on LG screen you could have the same issue as;
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
I had full bootloops apart from when MM was installed, it just sat there on the LG logo. Could be that your on MM with the issue?
I have tried LG Bridge, Flash Tool and LG Up with various different roms, both LP and MM nothing worked.
Mine is also Rooted, with the bootloader unlocked. LG UK have been sat with my phone for over a month - hopefully I will find out soon if they have fixed it using the warranty - but even if they do, mine is with LGUK not LGUS ...
Think what I am trying to say is, try all the methods and if it doesnt work send it for RMA with your fingers crossed :/
Click to expand...
Click to collapse
Just so I understand you, I basically have to RMA my phone? All the other options seem like they resulted in a bootloop. And RMA I'm assuming you mean using warranty?
And I'm not on MM.
Just out of curiosity, would the fact that I rooted my phone disqualify me for using mywarranty?
I guess you rooted with injected system.img. If you can go to download mode you could write the original system.img back, so then you are not rooted. Or you could write a KDZ file in LGUP.
ObiDanKenobi said:
I guess you rooted with injected system.img. If you can go to download mode you could write the original system.img back, so then you are not rooted. Or you could write a KDZ file in LGUP.
Click to expand...
Click to collapse
As far as I'm aware, simply restoring an original unrooted system.img backup will still show "Modified" in the download mode status, once it's been rooted. The only way to clear that status is by flashing the KDZ. (You can still keep your personal data with that option though.)
iamjerry123 said:
XDA,
I just got into a bootloop while on the Facebook App and I pressed the home button. I read that it happens to random people, but I want to make sure that I am safe.
I rooted roughly 5 months ago, when I got this phone and I've never had an issue.
What are my options? If I call VZ/LG will they accept my rooted phone? Or can I fix this bootloop? Will using this method http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 help me ?
Thank you,
-J
EDIT: My phone booted up, the apps were optimizing, but then it just rebooted back to the LG screen and now it's stuck there.
Click to expand...
Click to collapse
Based on what I've read in the main bootloop thread, the bootloop issue is a hardware problem that requires the phone motherboard to be replaced so I don't think they will be able to detect the root during the RMA process:
...
I have received confirmation from LG that series from May, June, July and August are afflicted by this issue and that the revision number doesn't matter. They also said that it is not necessary that all phones in these series will fail, but that under certain circumstances (not disclosed to me) they will start producing the bootloop issue which is h/w bound.
...
Update: It seems not all bootloops are due to deffective motherboard as on some phones they were able to detect the root and refused the repair under warranty.
So maybe for some G4's stuck in bootloop there might be a solution to be soft repaired.
I saw this in another thread, can you try this?:
...
Using DL mode (device off -> press and hold volume up while(!) connecting to PC) and LGUP you should be able to push any KDZ on your device and get out of the boot loop.
...
I don't have the bootloop problem so I can't test it but it might.
What's the build date of your G4 (between May-August 2015?)? What are the 1st 3 digits of your phone's S/N?
If you root any phone you automatically void your warranty. There's no exception to this and I actually understand why they do that because most people don't need to be rooting their phones lol but if u find a KDZ you're str8, use the flashtool and you'll never get into a permanent bootloop and you can use your warranty. But most likely something you modified or something another app was doing caused the bootloop not a hardware issue. Also it'd probably the last thing you ever even thought that caused it lol
Sent from my VS986 using Tapatalk
Have you tried a hard factory reset? Usually helps
Hi!
So earlier today I was using the phone as usual and I decided to update some apps because I had wifi available for once.
I go to the Xposed installer and updated a youtube addon and Gravitybox, about 20 seconds later the phone freezes and turns off (before I even get to reboot myself).
Since then it continues to bootloop - I try to access TWRP and the phone just freezes on the kernel bootscreen, or restarts.
My computer won't recognize the phone and there's nothing I can do.
Sometimes my phone actually goes further than just the kernel bootscreen, it acctually boots the system, but it always freezes before I get to do anything (but the time is random)
Although the phone doesn't freeze when I'm in the recovery menu (the white one, but as soon as i click yes for twrp, it gets stuck)
I have a regular H815, BL is unlocked and im using the Genysis Rom. (Marshmallow)
What I've tried:
Access TWRP through ADB
Access TWRP through the phone ( vol down etc)
Access Download Mode, computer won't recognize the device.
Boot normally.
Remove SD/Sim and do the above.
I'm stumped guys. So I came here. Any help would be apprecieted.
Deciding to bump this popular thread by updating my progress.
I managed to make download mode work, I flashed a KDZ matching my current rom, it was successfull according to the LGUP program, but the phone is still rebooting, I cleared data, but it's still not booting up.
I later tried downgrading and wiping the whole phone. Flashed the original rom i had when I bought the device... The screen with Lg and (Bootloader is unlocked) is still the only screen I get, anything I do doesn't seem to work and I'm starting to lose hope.
Although I've noticed, that everytime I flash KDZ, it still shows the same rom of origin, even if i just flashed another, meaning the flash wasn't effective. Is there any other programs than LGup? the LG flashtool won't find it, although Up will
It seems like the phone broke completely, yet it's still actually starting up. After googling I found that there was a common flaw with it actually bootlooping because of hardware issues - which I'm starting to think is the issue.
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
innocence07 said:
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
Click to expand...
Click to collapse
It's definetly a 505... lol.
y bootloaders been unlocked, meaning warranty is void. How would you reccomend hiding the fact its UBL?
Perhaps I could dirtyflash it with the wrong kernel, making it completely bricked. And just cluelessly leave it for warranty, but although I feel like that's a risk.
As far as I know there is no going back once you Unlock your bootloader and no warranty will be given whatever you do as IMEI of your phone is sent to LG when you unlock the device thru their site so when you do claim your warranty they will check to see if yours are unlock/lock. If you still push for a warranty they will charge you 200-250 dollars(estimated cost in our country) for the mobo replacement. Friendly advice, since its a paperweight now you could just sell it on ebay for 80-100 so dollars and buy a new phone.
Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.
Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app
Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk
I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?
I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.
Have you found any solution?
vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers
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
So my brother updated his Nexus 5X to the new OTA Update of 7.1.2 (probably) yesterday and after the update, it's stuck on bootloop with the Google logo sign.
Phone wasn't rooted.
Bootloader is locked.
Plus with the bootloader menu, I can't manage to open recovery, it just keeps on restarting.
I've searched around and till now I've only seen threads like it has caused to be a hardware issue but how can Google be irresponsible with such unstable OTA updates. Anyway, help would be really appreciated.
DawoodSahi said:
So my brother updated his Nexus 5X to the new OTA Update of 7.1.2 (probably) yesterday and after the update, it's stuck on bootloop with the Google logo sign.
Phone wasn't rooted.
Bootloader is locked.
Plus with the bootloader menu, I can't manage to open recovery, it just keeps on restarting.
I've searched around and till now I've only seen threads like it has caused to be a hardware issue but how can Google be irresponsible with such unstable OTA updates. Anyway, help would be really appreciated.
Click to expand...
Click to collapse
The fault does not lie with Google but with LG since the phone has been manufactured by them, not Google. But anyways, there's a LOT of rumors going around about the possible causes of this bootloop issue that has crippled many Nexus 5X's and it's not even the only phone of LG that does this. I've also heard reports of LG's G4, v20 and G5 doing this. This may point to a hardware fault like inferior soldering or other defects. But if you and your brother live in the US you could join the class-action lawsuit against LG for bootlooping phones. The article also contains a link to a survey that you can fill out
Sahri said:
The fault does not lie with Google but with LG since the phone has been manufactured by them, not Google. But anyways, there's a LOT of rumors going around about the possible causes of this bootloop issue that has crippled many Nexus 5X's and it's not even the only phone of LG that does this. I've also heard reports of LG's G4, v20 and G5 doing this. This may point to a hardware fault like inferior soldering or other defects. But if you and your brother live in the US you could join the class-action lawsuit against LG for bootlooping phones. The article also contains a link to a survey that you can fill out
Click to expand...
Click to collapse
Unfortunately, not from the US and there are literally not many LG or Google mobile service centers around here in Pakistan from where I could get a replacement or anything as my brother got the phone from UAE.
Anyway, is there any solution to the problem from which the phone could be fixed manually or is it just a dead end?
DawoodSahi said:
Unfortunately, not from the US and there are literally not many LG or Google mobile service centers around here in Pakistan from where I could get a replacement or anything as my brother got the phone from UAE.
Anyway, is there any solution to the problem from which the phone could be fixed manually or is it just a dead end?
Click to expand...
Click to collapse
Some people tried to fix it by putting it in the oven but if I were you I'd send it to LG for repair. If you got the phone from your carrier then you'll have to send it to your carrier.
Sahri said:
Some people tried to fix it by putting it in the oven but if I were you I'd send it to LG for repair. If you got the phone from your carrier then you'll have to send it to your carrier.
Click to expand...
Click to collapse
Okay so it kinda worked. I just kept the phone in warm environment as it's pretty hot here around 42 Celsius. It popped into recovery menu, cleared cache partition. Restarted, didn't work. Kept trying and phone automatically started although yeah phone's heaten up with low battery and I've put it on charge now.
Update: Crap again, I enabled usb debugging and allowed the bootloader to be unlocked after the phone booted just in case it'd get stuck again and yep after a while, It got stuck, phone restarted and back to bootloop.
Update2: Back on again, is there anything specific I should do in the meantime?
Unlocked bootloader. Flashed old 7.1.1 firmware.
Didn't work, stuck on bootloop.
DawoodSahi said:
Unlocked bootloader. Flashed old 7.1.1 firmware.
Didn't work, stuck on bootloop.
Click to expand...
Click to collapse
Factory reset might work. May I ask how far device boot before starting again or is it in endless boot animation?
kulvertti said:
Factory reset might work. May I ask how far device boot before starting again or is it in endless boot animation?
Click to expand...
Click to collapse
Unlocked bootloader and it already wiped everything. Degraded software so well.
It just has a bootloop with the Google logo.
Not to forget that phone sometimes automatically starts, boots successfully with really low battery of course, I put it on charge and then like after 5-10 minutes, it reboots and back to bootloop.
DawoodSahi said:
Unlocked bootloader and it already wiped everything. Degraded software so well.
It just has a bootloop with the Google logo.
Not to forget that phone sometimes automatically starts, boots successfully with really low battery of course, I put it on charge and then like after 5-10 minutes, it reboots and back to bootloop.
Click to expand...
Click to collapse
With similar symptoms I get out of bootloop once with wiping and downgrading from beta 7.1.2 to 7.1.1 firmware which end to other bootloop. But doing factory reset via settings app fix it. Second time with 7.1.2 firmware I get out from bootloop by first turning device completely off, booting up and before it restart turning wifi off. But problem with your brother device might be different.