1. badcat's Avatar
    Hello,

    My 5x has gone into the dreaded bootloop and I was wondering if there were any other options that I might try. I was on vacation and the phone started acting up with the display going mental and what looked like it was responding to phantom touches. Things flipping on and off, the notification shade going up and down and some UI freezes. Booting into safe mode seemed to fix it so I tried uninstalling any apps that were recently updated but nothing seemed to work so I just decided to limp home in safe mode so I could recover all my pictures. Once that was accomplished I figured I would try the O beta because I was going to do a hard reset anyway. The O beta installed fine but when I reset the phone it went into the bootloop.

    What I've tried so far:
    Wiping the cache partition from recovery (3X)
    Performing a hard reset from recovery (2X)
    Tied all of the above charging and unplugged.

    Googling around seems to suggest that this is a hardware issue and the phone is toast.

    I plan on contacting Google Support once they open. Any suggestions would be much appreciated.
    06-06-2017 08:27 AM
  2. N4Newbie's Avatar
    If this were me, I would grab the Nexus Root Toolkit here Nexus Root Toolkit v2.1.9 and run it with the bootloop/bricked option.

    If that doesn't fix it, then I would suspect a hardware problem.
    06-06-2017 08:36 AM
  3. badcat's Avatar
    Google support has pretty much told me they won't do jack. Just pointed me to the official builds. Completely useless. Maybe I'll try your suggestion. Thanks.
    06-06-2017 09:28 AM
  4. milleniumdroid's Avatar
    Could very well be a hardware issue such as dying RAM or flash ROM. In the worst case, it may be your SoC dying.
    06-06-2017 10:13 AM
  5. badcat's Avatar
    Could very well be a hardware issue such as dying RAM or flash ROM. In the worst case, it may be your SoC dying.
    I think it's a hardware issue myself. I am not happy with Google right now. Way to stand behind your products. I won't be buying anything from Google again.
    06-06-2017 10:39 AM
  6. milleniumdroid's Avatar
    If you are experiencing random shutdowns when your phone gets warm from use, then you definitely have an SoC issue. I have a retired HTC 7 Trophy T8686 with a QSD8250 that craps out after a few minutes of video recording or web browsing...
    06-06-2017 11:06 AM
  7. badcat's Avatar
    If you are experiencing random shutdowns when your phone gets warm from use, then you definitely have an SoC issue. I have a retired HTC 7 Trophy T8686 with a QSD8250 that craps out after a few minutes of video recording or web browsing...
    It's not random shutdowns. It's bricked. It's bootlooping and locks up about two seconds into the boot process. I definitely think it's a hardware problem.
    06-06-2017 03:23 PM
  8. badcat's Avatar
    If this were me, I would grab the Nexus Root Toolkit here Nexus Root Toolkit v2.1.9 and run it with the bootloop/bricked option.

    If that doesn't fix it, then I would suspect a hardware problem.
    Thanks for that suggestion. I had a few false starts but eventually got it to work. But unfortunately whenever it tries to reboot the phone it can't reconnect so I'm stuck at trying to unlock the bootloader. I think the phone is toast but Google Support is telling me because I was on a beta of O when it puked I'm on my own and I was asking for it. All they want to do is point me to the Nexus 5X image page. He even suggested I unenroll from the beta and go back to N! I told him that's not going to work if the phone doesn't boot but he didn't seem to get that...

    Edit: Google has decided to escalate my case to a specialist so at least they're doing more than blowing me off. I will make certain to keep updating this thread with any progress.
    06-06-2017 03:28 PM
  9. N4Newbie's Avatar
    I've had that "unable to reconnect" problem in the past but don't exactly recall the fix. Pretty sure it is simple though.

    Check the WugFresh site forums at WugFresh
    06-06-2017 03:47 PM
  10. badcat's Avatar
    I've had that "unable to reconnect" problem in the past but don't exactly recall the fix. Pretty sure it is simple though.

    Check the WugFresh site forums at WugFresh
    Thanks. I will. The phone does freeze and reboot so I attributed the inability to reconnect to that. But it still wouldn't reconnect even after I got back into the bootloader.

    Tried a few things but NRT still won't reconnect after the reboot when it tries to unlock the phone.
    06-06-2017 05:56 PM
  11. Cdn_Hammer's Avatar
    Having very similar issues, which just started yesterday. Just got off a chat with LG Canada, and they agreed to fix the phone at no charge, but only if I agree to downgrade from 32 gigs to 16 gigs. Apparently the Google Play purchased phone (purchased in Canada) is actually a US model so LG Canada will only fix it with a downgrade. Pretty ridiculous if you ask me. I'm currently in a chat with Google to see what they will do.

    edit - The fix is reportedly a new motherboard.
    06-07-2017 04:11 PM
  12. Cdn_Hammer's Avatar
    Google has agreed to give me a replacement under a 'one time exception'. They are paying for all costs, including return shipping. Great outcome!
    06-07-2017 04:19 PM
  13. badcat's Avatar
    Google passed on giving me any real help and just told me to talk to LG. LG told me they will repair it for free and provided me with a shipping label. We'll see how things go. It should take two weeks or so. Good thing I have another phone.
    06-07-2017 08:48 PM
  14. sk1win's Avatar
    Agree with Cdn_Hammer, I had the same issue. Google is sending me a replacement phone.
    06-11-2017 07:45 PM
  15. badcat's Avatar
    Well good for you guys. I got stiffed. Oh well.
    ElderHallow likes this.
    06-12-2017 08:41 AM
  16. ElderHallow's Avatar
    Thanks for that suggestion. I had a few false starts but eventually got it to work. But unfortunately whenever it tries to reboot the phone it can't reconnect so I'm stuck at trying to unlock the bootloader. I think the phone is toast but Google Support is telling me because I was on a beta of O when it puked I'm on my own and I was asking for it. All they want to do is point me to the Nexus 5X image page. He even suggested I unenroll from the beta and go back to N! I told him that's not going to work if the phone doesn't boot but he didn't seem to get that...

    Edit: Google has decided to escalate my case to a specialist so at least they're doing more than blowing me off. I will make certain to keep updating this thread with any progress.
    I've just had this. It's happened to me twice now. I've recently got my phone back from LG who replaced the Main Board (took em about a month to do it mind!).

    I don't think this is a software issue. When it happened to me the first time on Christmas Eve Google pretty much told me to get bent and go back to the manufacturer.

    Interestingly both times it's happened are right after software updates.

    So unfortunately I think your best bet is to contact LG who will sort it for you. You'll need proof of purchase though and like I said don't expect your phone back in any less of a time frame than a month.

    Good luck.
    06-17-2017 04:19 PM
  17. badcat's Avatar
    The LG repair center in Texas has the phone and it is working it's way through their process. It should be shipped out sometime next week. It took about 3 mins in a chat with an LG rep to get an RMA issued. I believe LG has seen enough bootlooping devices recently and they just issue RMAs as soon as they believe the device is unrecoverable. I'm not thrilled with Google's response but so far LG has been ok.

    I never thought it was software either. While it did occur after I installed the O beta the phone rebooted and ran O just fine. The issue started when I tried to do a hard reset. The Google rep blaming it on the O beta was beyond the pale. That's when I understood I wasn't going to get any help from them at all.
    ElderHallow likes this.
    06-18-2017 07:21 AM
  18. badcat's Avatar
    Well I just thought I'd update the thread. LG has finished repairing the phone and has already shipped it. They say they replaced the main board and it is covered under warranty. Can't say I was thrilled with Google's response but LG has done right by me so far. Should have the phone back Friday and if it boots I'll be happy. 😀

    Update: Received the phone this morning and it boots! It acted flakey for awhile but I'm chalking that up to the 24 app updates and two OS updates. After it settled down I opted back into the O beta and have that running now. It's now officially my third phone because I just picked up an S8 from Samsung. Couldn't pass up that deal. Maybe I'll sell it.
    06-21-2017 04:41 PM
  19. ElderHallow's Avatar
    Well I just thought I'd update the thread. LG has finished repairing the phone and has already shipped it. They say they replaced the main board and it is covered under warranty. Can't say I was thrilled with Google's response but LG has done right by me so far. Should have the phone back Friday and if it boots I'll be happy. 😀

    Update: Received the phone this morning and it boots! It acted flakey for awhile but I'm chalking that up to the 24 app updates and two OS updates. After it settled down I opted back into the O beta and have that running now. It's now officially my third phone because I just picked up an S8 from Samsung. Couldn't pass up that deal. Maybe I'll sell it.
    How long did LG have it for mate?
    07-01-2017 08:42 AM
  20. badcat's Avatar
    The entire thing (shipping to and from LG) was about ten days with four of them being shipping. As far as I'm concerned, LG has done right by me.

    I do have to say the fact that you had two bootlooped 5Xs has me concerned. Why would they replace a defective board with one that they should know is defective? You would think LG would only want to repair it once.
    07-01-2017 02:40 PM
  21. ElderHallow's Avatar
    The first time it happened on my original 5X they had it for a month (the whole of January) and only replaced the board. Can't believe it took them so long.

    I had the phone back for about 2 hours and it bricked. So they had it for another 3 weeks and then gave me a new phone (refurbished I expect).

    That phone that got stuck in a boot loop about 2 months ago. Again they had it for a good month before I got it back with a new board.

    I don't know why they don't just cut losses the 5X and offer an alternative when they come back with this problem.
    07-01-2017 04:29 PM
  22. badcat's Avatar
    Yeah because it seems like they don't know how to fix it or what the problem actually is. Throwing more bad phones at bad phones doesn't seem like a good idea.
    ElderHallow likes this.
    07-01-2017 09:44 PM

Similar Threads

  1. Why can't I see any usb debugging option in Nexus 5X?
    By AC Question in forum Ask a Question
    Replies: 1
    Last Post: 06-06-2017, 05:49 AM
  2. How can i fix my karbon sparkle v it is struck in a bootloop?
    By AC Question in forum Ask a Question
    Replies: 0
    Last Post: 06-06-2017, 02:54 AM
  3. how to unblock in coming sms on android nexus phone
    By AC Question in forum Ask a Question
    Replies: 1
    Last Post: 06-04-2017, 08:09 PM
  4. How to get back after disabling Google app on Nexus 5?
    By AC Question in forum Ask a Question
    Replies: 1
    Last Post: 06-03-2017, 02:35 PM
  5. Nexus 4 won't charge
    By AC Question in forum Ask a Question
    Replies: 1
    Last Post: 06-02-2017, 02:31 PM
LINK TO POST COPIED TO CLIPBOARD