I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Related
Ok, so had it unlocked, but running stock. Ran fine, then one day it stopped working and got stuck in a boot loop on the google screen. Managed to get it into CWM and then wiped, after lots of tries, and back to CM7 and unlocked. Then backed it out to stock and locked the bootloader(was planning on giving it to a friend who doesn't like to play with phones like that). But now it gets stuck on the google screen. Can get to fastboot, but if I do fastboot oem unlock it just has "..." and holds for hours(until I manually stop it) and then says it failed too many links. Can't get it unlocked, can't get it to boot into anything usable(either fastboot or the google screen and no further) and I'd really like to turn it back into a tablet for the kids to use since I've moved on. ADB devices shows error device not found but fastboot devices shows the serial number. I just really need to know how to unlock it so I can get it back and running. I think what screwed it up was I flashed it back to the way it came locked bootloader and then it said there was a OTA update, I said ok, downloaded it and when it rebooted it wouldn't go past google screen or past fastboot screen. If I try and do the recovery I get the triangle with exclamation point(yellow) and if I hit the power button a few times it tries to reboot and hangs. And yes, when I do the unlock the screen comes up, I move it to yes, hit power and then it freezes. Thoughts? Thanks in advance.
Ever Fix This?
Did you ever get this figured out? This is where I'm at after hours and hours to get to this point.
I have a Moto G (from Republic Wireless) and started having the Boot loop problem.
When I try to go for fastboot, then volume up to select recovery, the motorola logo appears, but no android logo after. Then the boot loop starts again. Anyone help me please?
Did you flash an older android version?
Same same but different
I have the same issue. Although I actually get as far as to getting to the lock screen and unlock that and then I get about 3 seconds then I get the 'Powering Off' message and the phone turns itself off.
I have enough time to go in and put it in debug mode but the phone never recognises the computer once in bootloader, I think it most likely have something to do with the driver for 'Fastboot falcon s' not working. Can't install a new one or in any way make my phone communicate with my computer. Have all the latest Moto device manager stuff installed too. I also think I have the wrong firmware installed (US and not AUS version) along with a heavily corrupted (or even completely missing) recovery image.
Have tried flashing a new recovery image but I keep getting either a blank response from 'adb devices' or 'fastboot devices' and whenever I try and issue a command that would hopefully result in anything other than the **** I am currently stuck in I get a 'waiting for device'.
All this because I tried to go from Unlocked Bootloader and CM11 (that wouldn't let me use mobile data or kept crashing on me, like 24/7) to stock Android and Relock the Bootloader.
I am pretty much losing my **** here, just happy it was only a $250 device though.
Does anyone have anything on this?
oh well, giving up on this. Contacted Republic Wireless and and they're sending me a replacement.
Hi all,
I have a Nexus 5 that I bought second hand. It powers up but is stuck in a bootloop. The Google Logo appears and it starts to load but it does not progress. I can get in to boot loader and I have tried to do a factory reset but it it still stays in the boot loop. I have tried to install the new factory software using the Nexus Root Toolkit but nothing. The Phone is also locked and I cant unlock the phone so the Nexus Root Toolkit wont allow me to try to flash the stock image? I am at the end of my knowledge base as I have tried almost all the normal methods to unbrick and fix the boot loop. The Phone can access the boot loader. When I try to unlock the phone using the Nexus Root Toolkit, it unlocks it but does not write the data and it becomes unresponsive! I have no idea if USB developer is on in settings as I have never got in to the Android operating system as I cant get past the bootloop.
Your help and suggestions would be most helpful as I am now at an end of my abilities until I am further educated about how to resolve the issue.
Res
I haven't tried this myself (no need), but since you seem to have nothing to lose give it a go. It's official Google, and comes with instructions.
https://developers.google.com/android/nexus/ota#instructions
Does the fastboot oem unlock command work?
Do you have all the correct usb and adb drivers installed??
First off, I suggest doing some reading up on adb and fastboot. Then manually flash factory images first and try to boot the phone completely.
The links @dahawthorne will help a lot.
Then try the command that @audit13 mentioned.
Hi everybody !
I have messed up my phone while installing and removing different progs like twrp and magisk. Now i'm stuck in a loop and can't figure out how to get out of it,despite having read many posts here and there. Here is what i have done:
- My phone is a Mi A2
- When i push the power button, i see briefly the android one logo, then a first message saying "your device can't be checked for corruption, please lock the bootloader", followed by a second message saying "your device has loaded a different operating system". Then it boot again with same messages infinitely.
- So i opened the phone, shorted the test points and flashed the "jasmine_global_images_V10.0.13.0.PDIMIXM_9.0" with miflash tool, apparently successfully. (By the way, i have never been able to boot in edl mode when the battery was disconnected) But alas, when rebooting after successful flashing, the phone did nothing more or less than before flashing: still stuck in the same loop.
- Pushing power and volume up does nothing else than bringing the loop mentioned above.
- Pushing power and volume down bring up fastboot, but then the device is not recognized in device manager, and i can't figure out why, as i already used adb and fastboot commands sometime ago before i messed up the phone.
Thank you in advance for any advice, and keep care of yourself and everyone around you all over the world !
Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.