Database Develop

[Q] Moto X stuck in a boot loop

Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE

darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?

I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?

Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.

MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache

serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.

Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode

Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!

[Q] Sprint OTA 4.4 on rooted (locked) 4.2.2 - Now reboots every 30 secs

So I had a rooted Sprint 4.2.2 (not unlocked, just rooted) and I got the OTA alert.
I accidentally installed it and it failed and now when it restarts, it gets to android for about 30 secs and then does the "powering off" bit and restarts... over and over.
In that 30 secs I can get to the settings and see that the version is still 4.2.2 so it didn't take. But it almost seems like it in stuck in that mode where it thinks it is doing the upgrade.
I tried killing memory resident stuff to prevent the restart to no avail.
I cannot get into any kind of stock recovery, it just reboots to normal mode
My only option is to go into Bootloader which does work.
But when I try to use RSD Lite and flash back to that last stock image, it shows
Failed flashing process 2/17 flash partition "gpt.bin"
I read that this may be due to the phone not allowing me to downgrade to a version lower than I currently have? Also read it could be the battery needs to be charged more.
Thoughts?

Can you get to the factory reset in that thirty seconds?
Sent from my XT1056 using xda app-developers app

If you can get to boot loader, will it go into recovery? If so, try restoring a backup. Likely you will have to do THIS, and I recommend doing this, the ota, then reroot.
Edit: if it boots to ROM for 30sec, try wiping cache and dalvik, then fix permissions, then reboot.

Ok so after reading around and doing some of my own playing around, I figured out how to fix it with some ideas from this thread
First off, the moto x rooting process actually REMOVES the recovery.img file from your phone, so what seems to be happening is that the upgrade downloads and starts to install... it attempts to load the recovery to flash the image, but since it doesn't exist, it just restarts the phone. When the phone restarts, the upgrade process still thinks it needs to run the upgrade, so it powers down.. this is where it gets stuck in the loop.
The solution is actually simple. Get into Bootloader mode (Power + Vol Down) which was slightly tricky since the phone always rebooted and never actually powered down. So I had to catch it at the end of the power off cycle, before it restarted. Once I was in bootloader mode I could use the following command:
Code:
fastboot erase cache
That seems to remove the downloaded update files as the phone stopped rebooting over and over.
But now I get Mobile IP Registration Error 67 (MIP) which basically means my registration data got wiped.. not sure I understand why that would happen.. but it basically means I need my MSL and have to enter the code to reset registration which will force a wipe of all data. At least I have the opportunity to back everything up over wifi now that I've stopped the looping.
The second part of this fix I haven't tried, but based on an educated guess, to actually GET the update correctly, I would need to flash the stock recovery image back using:
Code:
fastboot flash recovery recovery.img
where the recovery.img file comes from the zip file for the moto x stock image from the sbf repo:
http://sbf.droid-developers.org/phone.php?device=0
That of course needs to be done before I call Sprint to get my MSL and perform the reset.
All in all, a minor setback overall... better than a paperweight Perhaps instead of doing the erase cache step and just flashing recovery may have saved my MIP data
---- EDIT-----
Ah, gokart2, I see you had a similar process. Cheers

Turns out the Mobile 67 error was because my friend changed her service back to her old phone.... I should add that this wasn't my phone by my friend's phone.

[Q] Phone only turns on through fastboot.

I purchased the VZW Dev phone, using it for T-Mobile.
Rooted at some point, TWRP installed. I was using my old phone charger every now and then, but eventually the phone stopped recognizing it, forcing me to use the charger cable it came with. Come earlier this week, I see there's a software update out. Thinking it was Lollipop, I tried to install. Phone shut down, vibrated, refused to reboot without going through fastboot. So I turn the phone on through fastboot, the update says its been deferred, and then the phone shuts down by itself as if trying to update, and just vibrates.
I do a factory reset through TWRP, still have to turn on through fastboot, but the phone is working. I let the battery drain, charge to full, then try to update again. Same thing.
I plan to try flashing back to stock once Motorola gives me access to the file, but other than this, I'm stumped.

So you are trying to take an OTA with TWRP on your phone, rather than stock reocvery?
Yup, it will loop like that. You can NOT take an OTA update unless you have stock recovery on your phone.
Please see => http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425

Problem is resolved. After flashing back to stock, the device still refused to power on without doing so through fastboot. By chance, I stumbled upon your post about flashing a stock LOGO.bin, @KidJoe. Forgot I was using one to bypass the rooted message.

Tried to install OTAvwith TWRP, phone boots normally but then reboots to recovery

I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.

I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!

getting replacement phone, can only get into recovery, can i backup apps?

I have a early LGG4 from sprint, one of the first. Things have been great, was starting to think I was one of the lucky few.
Yesterday I set my phone down and about 45 mins later when I returned it was at the boot screen, and hot. I pulled the battery and let it cool. Since then I'm in a boot loop, however I can get to recovery. Sprint is ordering me a new phone, but I have 3 days to wait. I can boot into recovery and it seems to not freeze/reboot there. From time to time I can get my phone booted but it freezes and reboots within minutes.
Can I backup my apps/data from recovery? If so, how?

Getting a similar issue, but I can't even boot at all. I was all stock ZV9 with no root and now I can only get to recovery. I haven't tried factory reset yet, was going to see if I can push the ZV9 update again from ADB, so I won't lose everything. Fingers crossed I don't destroy anything.