Develop Bugs

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

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

bricked nexus 5x out of nowhere

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

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

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

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

Bootloader unlock bootloop on 2.0

Hey guys,
So I was able to return my HW to a normal state on AW 2.0. It turns out as soon as I unlock the bootloader, it goes into a bootanimation bootloop (a few times, it displayed an error then finally booted AW). And I can't get into the stock recovery. It seems like this one is screwed up somehow. Flashing TWRP works though.
I really don't understand this. I thought this was supposed to be like a Nexus/Pixel device. Has anyone else experienced this behavior? I would really like to unlock it and flash Negalite ROM.
Thanks!
Edit: OK so the watch only works if I flash the custom ROM from AW 1.5 using TWRP. It goes all the way and doesn't bootloop. SO WEIRD.
---------------
Original post:
Hi everyone,
I got my HW today and it's already messed up! I've been flashing ROMs and such for a long time now but I'm stomped. Initially, I wanted to install Negalite ROM.
Here's what happened:
- I used my watch for a bit on 1.5, connected it to my phone, did the initial setup and OTA updated to 2.0.
- I decided to unlock the bootloader. Worked but watch got stuck on a recovery bootloop (with the open bugdroid). Managed to get rid of it by factory resetting through TWRP (which I fastbooted).
- Watch was restarting (on 2.0) but got stuck on another bootloop (on Nougat bootanimation). Sat there for about 20 min.
- I decided to downgrade to 1.5. Used fastboot to flash boot.img, recovery.img and system.img. The system.img gave me an error at first while flashing but proceeded all the way (9 steps out of 9) with success (?)
- Now the watch is still stuck on bootanimation (I think it's the MM one, with the flying around dots) and won't go any farther.
Note: I can get into fastboot and TWRP 3.0.3 is installed. But multiple factory resets from TWRP don't change anything. I can't adb push anything to the watch from TWRP either (I tried the ADB sideload option). ADB drivers should be OK on my Windows 7 x64 machine (I used Google drivers from the SDK).
Any HELP please? I really don't know what to do now since I can't push any file to the watch... and I've read many threads on here to no avail.
Thanks in advance.
edit: IT BOOTED! I used a different system.img (the one from sturgeon-m6e69f-factory-e659286a.tgz) and flashed it with fastboot and IT WORKED! Thanks to whoever posted this version! Now I will try again to install Negalite.

Rooting help: bootloop, possible soft-brick

Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?

Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!

Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.

Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me