Hey guys,
So the other day I decided I wanted to root my zf2 and I went ahead and downloaded the wrong firmware. I downloaded a zf5 root and ran it.
The first fastboot commands in the .bat file I ran was this:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
After The root failed to complete (wrong firmware), I realised I had flashed the wrong fastboot firmware.
I tried to go back into fastboot through the power + vol up only to meet a usb logo screen. I did some research, and found that many zf5's were soft-bricked at that screen as well.
My question is will a firmware update on my current zf2 fix/update the fastboot.img? Will a factory reset from my phone fix it?
If not, what can I do to fix it?
Thanks!
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
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
New to XDA, so hopefully this is in the right place!
My problem
I tried to install a new ROM and it's gone badly wrong. First, I couldn't get the recovery bootloader to launch or to re-install. Then suddenly ADB wasn't working any more, and I was unable to boot up into the system.
Now I get boot loops with the Oppo logo. If I hold down volume up + power, I have access to Fastboot. I can use my Mac to send commands with Fastboot, but I cannot get ADB to find my device. Typing Fastboot getvar all gives me 'All: ' in response, which is not a good sign.
Attempted solutions
I've tried installing TWP and CWM, but both of them just end up booting to a black screen. At one point I tried to flash stock Oppo recovery and got a black and white flickering recovery screen for my trouble, which was unresponsive..so I wiped it and started over. I suspect it was not the correct recovery file, as I really struggle to find what are definitely the correct files now the OppoStyle Forums where I used to download recovery files no longer seem to be active.
After two days of reading various threads and trying solutions, I am really out of ideas now. So any help would be greatly appreciated!
Before embarking on this journey I cleared my phone of anything important, made sure it was rooted and enabled USB debugging. I also wipe everything from Fastboot whenever attempting any fresh flashes.
More context
I've had problems with my Find7 ever since I tried to unify my storage a couple of years back. In the end, I got unified storage to work but on a very old version of ColorOS. I had a lot of problems getting to that point, so from then I decided to just live with the outdated OS. But finally, the frustration of apps not being compatible got to me a few days ago and so I decided to try and install a new ROM. That's when my recent troubles began! I think legacy issues from my initial problems years ago may have contributed to the mess my phone is in now.
So what next?
Ideally, I'd love to get my Find7 completely wiped clean and a modern, stable ROM with unified storage working on it. But at this point, I'd settle for original ColorOS with non-unified storage again if I had to!
Hoping someone here has some suggestions I can try! Can't get worse surely
hi, so i'm not going to even start how much trouble this bootlop caused me.
it happened overnight so my alarm did not go off and i came late a work,...
i searched for 5 hours straight, downloaded more than 5gb .img files and twrp versions.
i even tried lineage os but nothing is working
until i stumbled upon this guide -> https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/
i download the img file used adb to flash it and now the phone is stuck on the google logo.
before this my phone would go on and off and showing a warning that my bootloader is unlocked now its just stuck.
i installed different versions of bullhead and still had no success.
if there is anyone with the same problem and found a solution please lord show him this thread so he can help me.
thank you in advance.
myphoneisfucced said:
hi, so i'm not going to even start how much trouble this bootlop caused me.
it happened overnight so my alarm did not go off and i came late a work,...
i searched for 5 hours straight, downloaded more than 5gb .img files and twrp versions.
i even tried lineage os but nothing is working
until i stumbled upon this guide -> https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/
i download the img file used adb to flash it and now the phone is stuck on the google logo.
before this my phone would go on and off and showing a warning that my bootloader is unlocked now its just stuck.
i installed different versions of bullhead and still had no success.
if there is anyone with the same problem and found a solution please lord show him this thread so he can help me.
thank you in advance.
Click to expand...
Click to collapse
Probably the boot loop of death.
Check this post: https://forum.xda-developers.com/nexus-5x/general/tool-bootloop-death-blod-workaround-t3819497
Since you already have your bootloader unlocked, you should just have to flash the BLOD 4 cores fix zip.
I'd you've needed up your phone, flash the latest Google image (flash-all) then the BLOD 4 cores fix before the phone restarts into the OS.
I need a little bit of help here with this, because I'm practically banging my head against the wall trying to figure this out. I'm trying to unlock my LG L38C Optimus Dynamic, and the problem is that every time I try to run
Code:
adb reboot bootloader
it refuses to actually boot into the bootloader at all, it just reboots normally and fastboot doesn't see anything at all. I know it can be done because I've seen videos of people who HAVE an unlocked LG L38C, and I can't go to the LG website to get this sorted out since my device isn't on the supported devices list. I would really like to get this unlocked so that I can start installing custom roms, but the only "recovery" it seems to have is hard resetting the device (which basically wipes everything and starts it fresh.) I've been trying to google this for the last 45 minutes and nobody seems to have an answer besides "use adb reboot bootloader" or it will give me guides for phones that are not what I have at all.
If anyone is able to help me out with this, I'd greatly appreciate it.