Database Info

[Help] Phone Bootloop

Hi guys, so i flashed a Moto G GPE rom onto my phone, got sick of seeing 3G rather then H or H+ and have decided to move back to Stock Retail.
I have a problem though when i use the guide on the FAQ ( the mfastboot way) everything i flash gets the okay appart from the system spasrsechunks? that gets some sort of error and it says error okay? Well apart from that after i reboot the phone, it has the warning sign but then uses the google bootanimation? ive left it on a good couple of minutes to see if it will boot but it doesnt seeem to want to..

Clarkiieh said:
Hi guys, so i flashed a Moto G GPE rom onto my phone, got sick of seeing 3G rather then H or H+ and have decided to move back to Stock Retail.
I have a problem though when i use the guide on the FAQ ( the mfastboot way) everything i flash gets the okay appart from the system spasrsechunks? that gets some sort of error and it says error okay? Well apart from that after i reboot the phone, it has the warning sign but then uses the google bootanimation? ive left it on a good couple of minutes to see if it will boot but it doesnt seeem to want to..
Click to expand...
Click to collapse
Google animation means that you still have the gpe rom on your phone. This happened to me before when i flashed the GPE rom too. What you need to do is flash your firmware again. Download the stock firmware form this guide: http://forum.xda-developers.com/showthread.php?t=2542219 Then what you need to do is run these commands MANUALLY! As in 1 by 1.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

Yeah I sorted it thanks no 4.4.2 ROM would work trued multiple times until I tries a 4.3 and downgraded then it worked and updated to 4.4.2 ora
Sent from my XT1032 using Tapatalk

DROID MAXX stuck at Motorola screen/fastboot "Boot up failed"

Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?

digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Which FXZ did you actually flash? Go through and manually flash the FXZ and see what happens. Also run an md5 check on the FXZ

Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
MD5 matched. Argh.

digitaloutsider said:
Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.
FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.
These are the steps that I used:
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
MD5 matched. Argh.
Click to expand...
Click to collapse
Well im out of suggestions. May be bricked

digitaloutsider said:
Huy guys, very strange issue on my XT1080M.
I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.
The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".
I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.
I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)
Any ideas at all?
Click to expand...
Click to collapse
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.

aviwdoowks said:
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
Click to expand...
Click to collapse
He did. Look at the post you just quoted.

Same problem here. Rebooted one day, never booted back up. Can't get the phone to charge enough to even complete most flashing commands.

Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!

digitaloutsider said:
Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.
Sigh. Such is life!
Click to expand...
Click to collapse
Can you flash a custom recovery and get it to boot to that using the broken device?

The old one had a locked bootloader.

Have you tried house of moto to flash yet?
what system version were you on prior to having problems?

I ran into this same issue and never recovered from it. I had an unlocked bootloader prior to attempting to recover. Now it fails to boot and shows the boot loader is now locked.

my moto x fails to boot up and shows no command when I boot up the phone. Fastboot shows boot up failed

I have one that's having a similar issue. Shows the Motorola logo then nothing. Stock ROM and nothing modified.
Edit: It's a Verizon model (If that has any bearing)

So is there no fix to this issue? I tried to flash a custom recovery using fastboot and got stuck in fastboot mode because the image was too large, and failure to flash.
Also now adb can't find the device

motorola droid max stuck black screen at BLBROKE. help me

How to fix XT1032 Boot loop after factory reset

Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess

I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14

I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.

legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.

ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.

fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.

audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?

Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.

@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.

audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?

fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.

fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.

worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban

Soft bricked Moto G and random reboots

I know the title is a bit confusing, but I will try to explain the context of my situation so you can understand it better.
I have a x1032 since the end of 2013. When the first image of the Google Play Edition went "public", I converted my device to it, and it stayed that way, doing all the OTA updates, until the 5.1 GPE appear.
When I did the update to this version (5.1 GPE), my compass didn't work with some apps (for example, GPS tools and c:geo), and as it is a sensor that I use most of the time, I decided do revert my device from fastboot to the 4.4 “stock Motorola” (don’t remembre if it was 4.4.2 or 4.4.4) and then update it to the 5.0.2.
In the process, I think that I had a soft brick: when I turned on the device, he stayed in the “unlocked bootloader” image, and he didn’t move forward. But, after trying, I saw that I had access to the bootloader menu and to the recovery, without any problem. I tryed to install the images via fastboot, even the new 5.1 GPE and 5.02 Motorola ones, but none of them works.
I searched, and searched, and finally understand that in this cases, the problema is the /system, /data and /cache partitions that need to be formated, and then I can flash any zip rom via recovery.
And now, this is where I stay: Via fastboot I installed the 5.1 GPE rom. Then I installed philz touch recovery, formated all partitions in ext4, wipe them all (just to be sure ), and did an adb push to have the GPE 5.1 zip ROM from @lost101 in my sdcard, and installed it. AND IT WORKS!
Now, the actual problem: I’m having form time to time some random reboots. They always appear after I try to turn the screen on, and after 3 or 4 seconds, the phone reboot.
Can this be related to the softbrick? I tought it could be a rom problem, but no one else have the same complains and @lost101 says that maybe this is from my phone.
Thanks in advance, and sorry for the long text and my bad english.

I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.

lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
You are absolutely right: there were no errors (except the "normal" validation erros because it's a GPE image), and in the end, I didn't need to format the partitions manualy.
I think the problem was the fastboot (I was using the one from the sdk... my bad!).
Now I know that any problems don't come from the software side, because in that part, everthing is ok.
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Thank you very much for your help. You really made my day.

RBras said:
I will just ask you two more things:
- What custom recovery do you recomend?
- Your Low Memory Killer Tweak works without any problem in the 5.1 GPE installed via fastboot?
Click to expand...
Click to collapse
Latest TWRP. Yes, the LMK Tweak will work in that case.

lost101 said:
I suggest you try flashing the GPE 5.1 Firmware Image available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Make sure you use only the following commands and use mfastboot available here: https://www.androidfilehost.com/?fid=23578570567719065
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
You should not need to manually format partitions. The above commands will do everything for you. The reason for your sensor issues are that the fastboot flashing previous was not successful.
Please do the fastboot commands manually, one at a time, and log everything and post it here.
Click to expand...
Click to collapse
Unfortunately, random reboots are still present
I have installed 5.1 Google Play edition factory image, with the mfastboot you told me, but it still reboots randomly. Did the same with the 5.02 EU from Motorola, and it behaves the same way.
The random reboots happen more or less, one time a day, and it's when I try to turn the screen on, it doesen't respond, and after 3 or 4 seconds, the system reboots.
Any clue of what can be? Is there a way to grab some logs to try to understand what's happening, or it is too difficult and it's better I don't have too many hopes?

It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.

lost101 said:
It would appear some sort of corruption has occured. I can't say anything with certainty - but I do believe Bootloader corruption could cause what you are experiencing.
It's possible you could fix this by reflashing the Lollipop Bootloader. I did not include the fastboot command to do this above.
Here it is: mfastboot flash motoboot motoboot.img
Try that and report back.
Click to expand...
Click to collapse
During my time with Moto G, I flashed it using fastboot, dozens of times, but I was so desperate in the other day that I didn't even notice that your list with commands didn't have the bootloader one.
Now I undestand why the bootloader I have is the one from 5.1 GPE.
I'm gonna try it. In the last 2 days I didn't have any random reboot, but I will take my risk and flash the bootloader from the 5.0.2 EU, and I will report back in the next days.
I'm buying you a beer today, for being so helpful and nice. Thank you very much.

I'm reopening this thread to try to see what's happening with my phone.
So, after flashing the bootloader of the 5.1 GPE, the phone was really better than it was in the OP.
My Moto G didn't reboot anymore when I tryed to turn the screen on, but instead, it started to reboot randomly every 2 or 3 weeks, without needing to touch the phone (the phone was rebooting by itself).
In the last month or so, I'm using the XT1032 Retail EU 5.1 (Optimized) v1.0 from @lost101, and now the behavior is, once again, the described in the OP: I try to turn the screen on, the phone doesen't respond, and after 3 or 4 seconds, it reboots by itself.
And this is happening once every 1 or 2 weeks.
So, can anyone give me some help to try to understand what's happening? @lost101 @luca020400 @LuK1337 @matmutant
Usually, I have the original firmwares from Motorola or GPE, or I can have the optimized versions from @lost101 with TWRP.
Thanks for your help, guys!

Just for the record, I get occasional sudden / unexpected power off. It's rare, but stuff can happen when you are dealing with a complex device such as a smart phone. This is especially so, if you are rooting / modifying the operating system.
The problem could be related to something you are installing. Also, I recommend a clean install once every few months.

Restoring Moto G (2nd gen) after failed rooting

Hi all,
I could really use some help on the following, and any advice would be greatly appreciated.
I wanted to root my Moto G (2014, 2nd gen, dual sim) in order to use the RAM more flexibly. Unlocking the device was no problem at all. However, when I initiated the rooting process, the trouble started. I first tried superboot, which did not work, but also did not destroy anything. Then, I switched to using TWRP and the supersu image (I found the info on here). TWRP worked fine, but after initiating the installation of the supersu image, the phone got stuck in a boot loop -- it stayed on the unlocking warning page and would not boot up anymore. I figured out a way to get back into fastboot (also by looking through the forum here, thanks to you all!) -- by pressing the power button until the screen switched off, and then pressing the Volume down button as well for a few seconds.
However, none of the recovery methods I found in other threads worked (I tried deleting the cache etc. through various methods, but the loop persisted). So, next, I attempted to use the method I found on droidviews.com to restore the phone to a working status (any working status would do at this point).
Since I was not able to access the debugging options anymore, I did everything except the initial 'adb reboot bootloader' command. Here is the list of commands:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
NB I am doing this on MacOS, so I used the osx-fastboot command instead of mfastboot. Up until 'flash boot boot.img', everything worked, but when I tried the 'osx-fastboot flash recovery recovery.img' command, I got the following error message in the Terminal window:
(bootloader) Preflash validation failed
FAILED (remote failure)
And the error message on my phone reads:
hab check failed for recovery
Failed to verify hab image recovery
What can I do at this point? Since I followed the instructions as closely as possible, I also used the 'osx-fastboot oem lock begin' command, and now my device indicates that it is locked. Did I wreck my phone or is there any way out of this at all?
As I said, I would be most grateful for any advice at all. If you need more information, I am happy to provide it.
Thanks!
-sleepingweather

I am still looking for ways to get the phone into any sort of working order. Do any of you have advice on this? Is it possible?
I ran Lollipop on it before it crashed, if that is helpful information.
Thanks

After connecting the device to a Windows 7 PC, I can confirm that the Windows system does not recognize the Moto at all, so it appears that the method in the main thread on unbricking & restoring Moto Gs back to 4.4.4 / 5.01 would not work either, right? Is there anything else that I can do?
If anybody were to give me even the most spurious bit of advice, or some feedback on how I should go about finding a solution on the forum (I am trying my best, but might not have observed all the etiquette etc. out of ignorance), I would be tremendously grateful.
Thanks

Here is the solution a very friendly user -- inFiniTyz_Z , many thanks!-- on here pointed me towards:
If a bootlocker is unlocked and then relocked, as was mine, it is entirely possible to unlock the bootloader again. One needs the unlocking key from Motorola and the command
fastboot oem unlock UNIQUE_KEY
With the bootloader unlocked, I was able to flash TWRP again, which of course helped tremendously.
After this, I managed to install a Brazilian stock ROM -- the German one I would need did not work, but I will look for ways to get the phone to work regardless. At the moment, Android is up and running, but it does not connect to the network (because of the Brazilian settings, I guess). I might switch to CyanogenMod anyways.