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.
Related
I rooted my TB the other day and everything went well. I've been using it with no problems until now. I wake up this morning and it's stuck on the bootloader or fastboot screen and no option that I choose allows my phone to boot up normally. Any help with this matter would be greatly appreciated. Thanks.
Similar Issue
I've had the same thing happen with mine, except after multiple boot loader reboots I can eventually get the phone to boot. Eventually it will display the message "Shutting Down" The longest it's worked before rebooting is 30 minutes, but I've not allowed the VZ update to go through. Any suggestions? Thinking of trying to flash a rom.
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
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