My Nexus 5X is rooted, oem unlocked with stock rom(July patch), twrp 3.0.2 recovery
My phone suddenly stuck and reboot itself when I was using it. And it went into bootloop after that.
I can enter bootloader mode, but can not enter recovery. I have try to flash the stock rom of august (MTC20F) but got the same issue.
And I can not enter download mode too, the download mode loading screen appears for a few seconds and bootloop again
Phone info:
HW VERSION - ver_1.0
BOOTLOADER - BHZ10r
BASEBAND VERSION -M8994F-2.6.32.1.13
CARRIER INFO - N/A
secure boot -enabled
device state - unlocked
Any help will be appreciated
plug the device up (preferably not the quick charger) for a good 15 minutes. and try to get in bootloader again
I have exactly the same issue. I tried to flash the stock ROM with the command prompt and with the WugFresh toolkit but doesn't work.
Had this same problem last week. I was on n beta but fully stock and locked otherwise. Couldn't flash a factory image and adb sideloading image failed. Spit back the error of something like 'this image is for "bullhead" but this device is ""
Seemed like a lot of people on reddit had the same problem. Some thought it was the August update, others the July. I was on the n beta.
Seems to be a hardware issue. Got my refurb yesterday.
Sent from my Nexus 5X using Tapatalk
My wife's phone had the same issue last night. Was this after updating to the latest Android Security Update? I have not done the update on my phone yet, but she did on hers.
We ended up contacting Google, and they are sending us a new phone since we couldn't get recovery to work at all. It will be interesting to see if the security update causes any more of these?
WOW, so many people have the same issue. I had contact Google, and they have sent me a replacement.
But this phone is really let me down, I had only used it for less than 8 months
And the replacement is very inconvenient as I'm in China
My phone freezed and got into a bootloop last week. I just shutdown it and restarted it again, it was okay.
Related
I own a N5x 16gb (h790 with Android N DP2)
Yesterday I was opening Inbox by Gmail and I get some FC after open some mails so I started to get more FC from other apps (It was a webview beta problem https://goo.gl/k4SZ6i) so I tried to reflash Android N and I get bootloop on boot animation (that with colored points), I tried to flash MDB08I and MHC19J and occur the same bootloop.
After some trys the bootloader goes locked and now i cant unlock it
here some links i've tried:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/constructing-16gb-tot-file-t3337443
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/page4
Any ideas?
vinaaa said:
I own a N5x 16gb (h790 with Android N DP2)
Yesterday I was opening Inbox by Gmail and I get some FC after open some mails so I started to get more FC from other apps (It was a webview beta problem https://goo.gl/k4SZ6i) so I tried to reflash Android N and I get bootloop on boot animation (that with colored points), I tried to flash MDB08I and MHC19J and occur the same bootloop.
After some trys the bootloader goes locked and now i cant unlock it
here some links i've tried:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/constructing-16gb-tot-file-t3337443
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/page4
Any ideas?
Click to expand...
Click to collapse
The bootloader just cant magically lock itself. Anyway, try following the instructions HERE to sideload the N ota. Once in Android go to developer options and allow OEM unlocking and unlock your bootloader. Then reflash the latest marshmallow images and dont mess with your phone anymore.
PiousInquisitor said:
The bootloader just cant magically lock itself. Anyway, try following the instructions HERE to sideload the N ota. Once in Android go to developer options and allow OEM unlocking and unlock your bootloader. Then reflash the latest marshmallow images and dont mess with your phone anymore.
Click to expand...
Click to collapse
I already tried this two or three times, it remains on boot animation
mine to , when i was using it for chatting the phone starts freezing , and it's dead
i can't boot it up and can't go to recovery , even i did flashing manually with ADB / NRT same problem still can't boot up , don't know what happen , can't go to download mode to
This happened to me as well
I recently bought a used 5x on eBay, the H790 model. It was cheap.
Everything was fine until I ran through the updates., and was downloading apps from the Play store.
Since then, the phone would unpredictably reboot no matter what ROM was installed. The logcat logs didn't show anything helpful. Typically it didn't take too much longer than 60 seconds for the phone to reboot itself.
I messed with it every way I've seen published, including the links you included. I'm having to send the phone back. Thankfully, for a full refend.
I will note that the LG G4 had a hardware bootloop problem. I don't know if it's at all similar to this issue. My other thought is it could be faulty RAM but I don't know how to do a memory check on Android.... maybe LG had a bad batch of 5x's that got out there.
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for there help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys :good:.
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Any kind of suggestion will be very much appreciated.
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload
Hi All,
My Nexus 5x 32 GB phone suddenly died on me last night. The situation as of now:
1. Cannot boot normally. Shows Google logo and everything goes dark.
2. Can boot into Fastboot with holding down power and volume down buttons
3. But not able to go into recovery. When I select Recovery in Fastboot mode, it just tries to reboot and the screen stays dark. Nothing happens.
4. The bootloader is locked. I think OEM protection in Developer tools is on, so not able to unlock bootloader through Fastboot commands.
What an I do?? Factory reset would be great, if option is there.
Please help!! Thanks.
Try to flash Factory image by command adb and fastboot if your pc recognized your nexus 5x
unlock oem if necessary After
Funny enough, I've got a very similar issue
I can boot into recovery though, but there's a catch, and I think it applies to everything past boot, the phone freezes and restarts after like 3-5 seconds.
I can't boot to system, as it takes way too long to boot up, but I can only see the first panel of the recovery before it dies and restarts.
I have flash official images, and even TWRP recovery to see what I can do, but this doesn't work out in the long run, as the issues are ever persistent
Thanks for the quick replies!
Tried everything, including Nexus toolkit... But nothing worked. So I finally took it to service center as its still in warranty. They said the problem is hardware related and it might have happened because of recent update. They also said they have been getting lots of phones with this problem. So they they are replacing the motherboard free of cost. Wish they could have given a new phone
Once again, thanks all!
Dude that's wild, this same exact issue literally happened to me 2 weeks ago while I was on tour. Was on 7.1.1 (Pixel ROM to be specific) and my 5X just died on me out of nowhere. Absolutely the same things happening here, would boot up, go black, and then start bootlooping. Could access fastboot, but I couldn't get into recovery. Called Google and got a replacement because it was definitely hardware failure and I was still under warranty (just a few days past a whole year). I wonder if the new 7.1 betas are breaking peoples' phones
Sent from my Nexus 5X using Tapatalk
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Scratch. said:
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Click to expand...
Click to collapse
Have you tried flashing the stock images? If you can get to fastboot, you can flash the stock image and unroot your phone. You should also then be able to lock your bootloader (if it is unlocked) and then do your warranty at that point.
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
so people saying android 7.1.1 brooking devices, so will that be safe to upgrade the phone from 7.0 to 7.1 .1 when stable release will be available ?
Scratch. said:
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
Click to expand...
Click to collapse
Sounds like the hardware bootloop issue that has been hitting 5x devices hard lately. Mine started looping last week and I had to send it in.
Are you still within your 1 year manufacturer's warranty? If so, you can call LG and report the issue to them. Your device may get fixed, but it was also reported Thursday that LG has started issuing full refunds because they ran out of the needed part.
The company have started offering refunds
https://www.neowin.net/news/lg-to-issue-full-refunds-to-customers-with-faulty-nexus-5x-handsets
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.