Database Develop

[Q] AP Fastboot failure after Official OTA .906

I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?

I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA

HEMItude said:
I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?
Click to expand...
Click to collapse
I would use RSD lite to flash 5.6.890 by booting with M+Power and then AP Fastboot mode.
Atrixn00b said:
I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA
Click to expand...
Click to collapse
This won't work because he doesn't have root or boot/safe strap installed and you can't wipe partitions/dalvik through stock recovery.

ohhh makes sense. haha

I'm still confused about the difference between x+power and m+power

Would this be something Motofail one click could fix?

DoubleYouPee said:
I'm still confused about the difference between x+power and m+power
Click to expand...
Click to collapse
X+Power gets you to stock android recovery. M+Power gets you to the selection menu where you can boot into AP Fastboot mode to flash, or boot into BP Tools to access Bootstrap (Hash's in particular).
MerCiLeSS28 said:
Would this be something Motofail one click could fix?
Click to expand...
Click to collapse
Most likely not because he can't access the phone to connect via Charge Only nor is he able to install Boot/Safe Strap. Maybe root through ADB and push it that way? Maybe...

I was able to get into Clockwork. During that brief few seconds that it would boot back into Android, I was able to quickly use the Boot Into Recovery option. As using the hard key combinations wouldn't work, it just kept bringing me back to the AP boot failure.
Once in Clockwork, I was able to do a factory wipe and cache clears. After that, I could succesfully boot into the OS and gain access to the device without it continually trying to reboot. But it didn't help....as I tried to download and install the OTA to .906 it restarted the device to atempt the install and it brought me right back to the same boot failure loop.
My final resolution was to use psouza4's 890 update script to get back to a complete fresh stock image of .890. Once I did that, the official OTA to .906 installed perfectly. I re-rooted and was good to go.
There was probably a much simpler solution, but I didn't know it. Plus I felt better starting over from scratch anyway.
Not sure exactly what it was causing it...probably my own stupidity.

[Q] Aw Crap. My phone wont factory data reset. Help

A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?

It looks like I need to reflash the stock recovery image. I believe I have that (as long as the stock recovery is the same for all moto x phones (verizon, sprint, tmo, att, etc).
The problem I am having now is that I don't know how to flash the stock recovery image. All the instructions that I find require the phone to be in fastboot mode, but I have a locked boot loader....so. ..wud am I supposed to do??

dzlvs8 said:
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
Click to expand...
Click to collapse
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.

_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Click to expand...
Click to collapse
Well your phone is technically rooted when you boot normally, but you don't have write capabilities to /system which is why nothing is sticking. You need to boot the phone into recovery mode to make those changes, and then reboot normally to use them. To boot into the recovery mode with write protection off you need to power your phone down, and power it back up while holding volume down. That gets you into the bootloader and from there you choose recovery and then your phone will reboot with write protection off. It's kind of annoying to have to do it this way but blame Motorola for locking the phone down as well as they did.
To flash the stock recovery back, you need to put the recovery file in your adb folder and then the command is "fastboot flash recovery recovery.img" without the quotes, but if you are unfamiliar with adb I don't recommend doing it. You can just flash the whole stock image with RSDLite and start from square one. I've not personally used RSDLite but here is a video tutorial for you- http://forum.xda-developers.com/showthread.php?t=2446515

dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
Click to expand...
Click to collapse
also just a quick note:
"adb reboot recovery" will boot you into recovery/writeable system
"adb reboot bootloader" will boot you into fastboot for using rsdlite which is all described in the instructions given by metalhead

[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...!!!

Moto X Verizon Dev Edition TWRP, boot loop

I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?

and of course, i am to stupid to have no backups made

KhAjUr said:
I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?
Click to expand...
Click to collapse
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.

jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
Awesome. gorked like a charm.
just a note for someone else trying this.... first time i booted up after doing a "fastboot clear cache", i got a warning saying failed to load info. I clicked okay and I would get no service. Rebooted normally again, and everything worked fine.
Thanks again fro the response.

So are you now on 4.4.2?

The Tallest said:
So are you now on 4.4.2?
Click to expand...
Click to collapse
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.

KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
If you're stock rooted, you just need to flash the stock recovery (available from the moto dev site) and make sure you don't have any missing or modified system files. You can then just take the OTA like normal, then reflash TWRP after.

KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
There are a lot of threads discussing this.
If you have a Dev Edition X with an unlocked bootloader, as long as you have stock recovery on the phone, and are close enough to stock, you can just take the 4.4.2 OTA and re-root using the same TWRP and SuperSU process. (more details -> http://mark.cdmaforums.com/MotoX-OTA.html which is based on many threads here on XDA)
Downgrading to 4.2.2, etc.. while rooting was for locked bootloaders only.

jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!

TWRP is recovery, not bootloader / fastboot
You will need to plug into your computer, you should probably read more before you break things worse tho.
Start here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358

vennardk said:
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!
Click to expand...
Click to collapse
TWRP is a RECOVERY, not bootloader.
Do you remember how you flashed TWRP on your phone? You booted the phone into Fastboot/Bootloader mode. Connected the phone to PC via USB cable, then from command prompt on the PC used the Fastboot or mFastboot command... Same thing. However in this case the command to clear your phone's cache is... mfastboot erase cache
The other option is, you can see if there is an "erase cache" menu option while in TWRP as that would work too.
Then to take an OTA, you need to flash stock recovery back on your phone. If you try to accept an OTA while TWRP or other custom recovery is on your phone, you will get stuck in a boot loop like this.

On a custom rom but cannot get into recovery >_>

EDIT: So after various attempts at rooting(pureRoot, multi-tool etc - I was able to root and install the updated su binary With the Windroid app. Also, I now know that Vol Up selects in fastboot. thanks to all who replied.
So I have the Moto X 2014 pure edition & thought I had rooted and unlocked bootloader. (I did because I'm on a custom ROM now...) But somehow I retardedly forgot to flash gApps and now don't have any way of getting apps etc restored. I go into fast boot and hit "recovery" but it doesn't do anything. The only way I was able to flash this custom ROM was because I had twrp manager app installed on stock ROM. But now since I can't get any of my apps back, I'm stuck. I got superSu apk but it says binary needs to be updated and keeps coming up with an error every time I try. I'm thinking I need to root again? I'm kinda at a loss... Don't know what happened. Any help is appreciated! Thanks

Flash twrp recovery.
Sent from my XT1095 using Tapatalk

I'm pretty sure I did that like 3 times through adb before I switched over to a custom ROM.. Couldn't get into it so that's why I downloaded the twrp app. :/

lilly0x said:
I'm pretty sure I did that like 3 times through adb before I switched over to a custom ROM.. Couldn't get into it so that's why I downloaded the twrp app. :/
Click to expand...
Click to collapse
Not to assume anything, but are you hitting the power button to select recovery from the fastboot menu? That was my mistake, lol. New to Moto. You have to hit volume up instead of power. That acts as the enter key for Moto. At least on this device. If that's what you're doing, can you connect to a computer and fastboot boot twrp.img ?

Wait so power isn't enter? I've been hitting power. -_- I could have swore power got me into recovery when I first rooted... I'm gonna try and if that's the problem. I'm such a fail at phones.

Okay so I got into recovery. d'oh! (Volume up selects. It says RIGHT THERE. Sorry guys lol) anyway, now my root apps can't verify root access. So I think I have to root again? It's been a couple years so please bear with me :/