OKay I shot myself in the Jimmy
Moto x4, 1900-1 unlocked bootloader, tried to use CF Auto ROOT to root and after the CF Auto Root batch ran its stuck in an endless boot screen loop along withthe usual warning about the bootloader being unlocked and the verity mode set to disabled. I can get back to the recovery screen and thankfully power it off but thats it.
Any ideas for a next course of action.
Thanks you for your time.
Related
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
littlalex said:
I could only find three references to boot loop in the Moto G troubleshooting area...so here I type.
phone is XT1064
Was trying to side load Lollipop. Got to the boot menu no problem...when I selected Recovery the phone rebooted and got stuck on the Moto logo screen "powered by android."
I'm able via external reset get back to the boot menu, but whatever option I choose I end up looping...
Just spent a couple of hours with Moto tech support...painful, avoid if possible. The script pages were turning so fast I thought there were wind gusts in the tech office!
Any ideas would be greatly appreciated.
Littlalex
Click to expand...
Click to collapse
did you have your xt1064 rooted? i have mine rooted in lollipop, i also have the boot loop when starting sometimes, so far you can uninstall root via super user app and solve the problem or have patience untill some good developer fix this problem, to get out of the boot loop i find that connecting to charger the phone does the trick for me, it take like 3 minutes to start, if i uninstall root it starts very fast, im waiting for a solution.
My out of the box Nexus 6 is now stuck looping on and off at the Google boot screen after it tried to install the system update.
I've used the toolkit 1.9.8 to go back to stock. It goes thru the steps appearing to show OKAY and finished at each step. It never reboots the phone at the end. I try to force reboot after waiting for several minutes and it still boot loops. I try again the process again and sometimes it loops and a few times it actually starts up to the welcome screen. However, if I try to root or update recovery (using the toolkit), I get the boot looping again.
Did google bork my phone during a failed update? Is there anything else I can do to completely restore the phone? I've also downloaded the images on google and flashed---same boot loop.
Ultimately, my phone is now booting up to the welcome screen as expected and shows LRX21O. BUT, if I try to do anything (root or recovery), boot loop results again.
(I was able to unlock the phone and know about the usb debug and OEM unlock settings in dev menu, fyi).
I've had CM12/12.1 installed on my motoX 2013 for a few months now and have had no problems. Last night when i tried to type in my password my phone would just freeze. I restarted it and eventually i got in and went to disable the password. On the way there it crashed again and now when ever i try to start my phone it just gets stuck at the warning bootloader unlocked screen. I can get into fastboot and when i go to my recovery it just gets stuck on the teamwin screen. This happened without me changing anything, no update or anything
So I successfully rooted my lg k8 2018 (lg aristo 2). I decided to install gravitybox and turned on some things. I rebooted my phone and now it's stuck on the boot logo. I can't boot into recovery because I get the bootloader is unlocked message. (Not possible to re-lock it w/o putting my phone into a boot loop). I can get into fastboot by holding down and plugging in my phone. What should I do?
Update: I need to be able to get into recovery to flash xposed uninstaller. However, because I get the bootloader is unlocked message, I cant. I tried at least a thousand times. I also tried the button combination to disable xposed on startup. That didn't work. It was running android 7.X (I think 7.1 or 7.2)
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.