[HELP!] Moto X stuck in boot loop!

neo.dcm

Member
Sep 30, 2012
16
3
3
My Moto X 1st Gen (XT1052, Locked bootloader, default Lollipop 5.1.1) went dead out of nowhere. I noticed that my WhatsApp was FCing every few minutes. I ignored it, but the phone just went dead. When i pressed and held the power button, the phone went into a boot loop. I can access the recovery menu but it does not go into any of the options, just goes back to bootloop after selecting any option.
Also, i notice that the screen flashes for about half a second, every 20 secs and i can see the Android bot lying on its back with the Red exclamation and 'No command' text below it.
What's the solution to this?
 
Last edited:

sd_shadow

Recognized Contributor
Sep 21, 2011
16,792
7,629
253
South Dakota
goo.gl
My Moto X 1st Gen (XT1052, Locked bootloader, default Lollipop 5.1.1) went dead out of nowhere. I noticed that my WhatsApp was FCing every few minutes. I ignored it, but the phone just went dead. When i pressed and held the power button, the phone went into a boot loop. I can access the recovery menu but it does not go into any of the options, just goes back to bootloop after selecting any option.
Also, i notice that the screen flashes for about half a second, every 20 secs and i can see the Android bot lying on its back with the Red exclamation and 'No command' text below it.
What's the solution to this?
what options are available?

Sent from my XT1060 using XDA Labs
 

YedanyXD

Senior Member
Dec 22, 2015
323
80
0
My Moto X 1st Gen (XT1052, Locked bootloader, default Lollipop 5.1.1) went dead out of nowhere. I noticed that my WhatsApp was FCing every few minutes. I ignored it, but the phone just went dead. When i pressed and held the power button, the phone went into a boot loop. I can access the recovery menu but it does not go into any of the options, just goes back to bootloop after selecting any option.
Also, i notice that the screen flashes for about half a second, every 20 secs and i can see the Android bot lying on its back with the Red exclamation and 'No command' text below it.
What's the solution to this?
recovery stock? Or TWRP