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.
Related
So I just purchased a used Oneplus One off of Swappa (seller claimed phone had been used for 1 week, minimal damage, etc.) and upon receiving it and trying to boot it, I was greeted with a bootlook where the phone never makes it past the boot animation (the oneplus logo with android at the bottom). I figured the easy solution was to simply sideload a stock image of the latest software. However, when I put the phone into fastboot, it would not be detected by either adb or fastboot. I know the phone is rooted and unlocked, but because I cannot turn it on, I cannot tinker with any USB-related dev settings. I have reinstalled android sdk, adb, fastboot, and the google usb driver, all to no avail. Even tried all of this on a second Windows laptop. Is there something I'm missing or is there some fix to have this phone detected while in fastboot? The phone is the Cymd edition with stock recovery. Thank you.
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.
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?
I unrooted my phone through Magisk Manager to get the Android 10 update, and I guess I missed a step. Because when my phone rebooted, it comes up with the "No Command" screen after showing the unlocked bootloader warning.
I am able to enter the recovery mode and all of those settings, but my phone wont boot normally. It doesn't even show the Motorola "M". If I leave it on for a bit, it will switch between the unlocked bootloader warning and the no command screen. I've already tried a factory reset but that does nothing.
Am I stuck with a broken phone, or is there another hope? I'll do my best to provide more info if needed. Please help!
Randomsamm said:
I unrooted my phone through Magisk Manager to get the Android 10 update, and I guess I missed a step. Because when my phone rebooted, it comes up with the "No Command" screen after showing the unlocked bootloader warning.
I am able to enter the recovery mode and all of those settings, but my phone wont boot normally. It doesn't even show the Motorola "M". If I leave it on for a bit, it will switch between the unlocked bootloader warning and the no command screen. I've already tried a factory reset but that does nothing.
Am I stuck with a broken phone, or is there another hope? I'll do my best to provide more info if needed. Please help!
Click to expand...
Click to collapse
What recovery u using I would look for orange fox and fastboot into that there is more things u can do if you don't want to save any thing I would reflash using orange fox recovery the rom u want I would use bliss or havoc I'm on now supper stable everything works and it's Android 10
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.