Database Info

Help me find a way

So,tpday was a hard day for me. Yesterday i installed 4.4.2 GPe rom on my xt1032 and immediately got a 4.4.4 update,and of course,i updated. Tried to install aero kernel,and i ended up in a boot loop,so i tried to install a stock eu xt1032 firmware,and ended in a brick. I managed to unbrick it and install a custom rom (i can post a tutorial on unbricking if you guys want) but,i want to install stock xt1032 firmware,but when i try to flash it,it's constantly giving errors. For instance, gpt.bin always throws an error,and i have to flash a custom rom again. Can anyone help? Thanks in advantage
Sent from my Moto G using Tapatalk

DeHuMaNiZeD said:
So,tpday was a hard day for me. Yesterday i installed 4.4.2 GPe rom on my xt1032 and immediately got a 4.4.4 update,and of course,i updated. Tried to install aero kernel,and i ended up in a boot loop,so i tried to install a stock eu xt1032 firmware,and ended in a brick. I managed to unbrick it and install a custom rom (i can post a tutorial on unbricking if you guys want) but,i want to install stock xt1032 firmware,but when i try to flash it,it's constantly giving errors. For instance, gpt.bin always throws an error,and i have to flash a custom rom again. Can anyone help? Thanks in advantage
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
gpt and motoboot will give you errors, you should skip those in order to downgrade, the rest of the files should flash without problems. I have flashed stock 4.4.3, downgraded to 4.4.2, installed GPE 4.4.2 to get 4.4.4 and then I flashed 4.4.2 Germany to get stock 4.4.4. Since I upgraded to 4.4.3 I had to skip gpt and motoboot and had no issues.

alresave said:
gpt and motoboot will give you errors, you should skip those in order to downgrade, the rest of the files should flash without problems. I have flashed stock 4.4.3, downgraded to 4.4.2, installed GPE 4.4.2 to get 4.4.4 and then I flashed 4.4.2 Germany to get stock 4.4.4. Since I upgraded to 4.4.3 I had to skip gpt and motoboot and had no issues.
Click to expand...
Click to collapse
Thanks bro,i did not know that! Saved me a lot of nerves!
So,does anyone want a tutorial on how to succesfully downgrade?
Sent from my Moto G using Tapatalk

edit:no,cannot install stock with this method man. i got sparsechunk errors. and i really want to boot stock rom,i'm sick of custom roms.i regret the day when i converted my moto g to GPe. if anyone has a way to return to xt1032 from 4.4.4 GPe,please share it.and for those that don't know,don't ever convert your moto g to GPe.

I went from GPE 4.4.4 back to stock yesterday without flashing gpt.bin and motoboot.img with no issues. I then got the official Moto 4.4.4 OTA which worked fine.
I have an unlocked UK device so I flashed the most recent UK 4.4.2 ROM (Blur_Version.176.44.1.falcon_umts.Retail.en.GB),
The sparsechunk files have different names to those mentioned in the downgrade guide though.
Here's the commands I used:
Code:
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

rec71 said:
I went from GPE 4.4.4 back to stock yesterday without flashing gpt.bin and motoboot.img with no issues. I then got the official Moto 4.4.4 OTA which worked fine.
I have an unlocked UK device so I flashed the most recent UK 4.4.2 ROM (Blur_Version.176.44.1.falcon_umts.Retail.en.GB),
The sparsechunk files have different names to those mentioned in the downgrade guide though.
Here's the commands I used:
Code:
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Yes,i know that..wierd,since i tried to flash UK rom yesterday and noting..when i try to flash sparsechunk files,it says image too large on my phone's screen..
Sent from my Moto G using Tapatalk

Bootloop after downgrading to 4.3 .. pls help ?

hello,
I had to downgrade to 4.3 from 4.4.3 because I had a serious battery drain issue..
I followed the steps posted on this thread..
http://forum.xda-developers.com/showthread.php?t=2542219
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_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
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
I had faux kernal installed before downgrading to 4.3.. should I have to install a jelly bean kernal first before running these commands ? now I'm stuck on a bootloop ? pls help me ?
is there any way to install custom rom or any rom using fastboot?

I installed TWRP recovery "it says- unable to mount data" then I flashed CWM it also says "can't mount sd card"
what is the issue here ? pls help me I'm about to have a massive heart attack

As far as I am aware, you cannot boot Stock 4.3 with an updated Bootloader (you flashed motoboot, but that will not have downgraded the bootloader). If you can find the custom kernel for 4.3 Faux created - that may work. Otherwise, you have to install 4.4.2 or newer.

lost101 said:
As far as I am aware, you cannot boot Stock 4.3 with an updated Bootloader (you flashed motoboot, but that will not have downgraded the bootloader). If you can find the custom kernel for 4.3 Faux created - that may work. Otherwise, you have to install 4.4.2 or newer.
Click to expand...
Click to collapse
thanks for the reply.. later I managed to flash GPE rom and got it working again..
http://forum.xda-developers.com/showthread.php?t=2646404

I was about to downgrade from stock Kitkat 4.4.4 to JB as well... now I'll hold back. Anyone got a correct way to downgrade from 4.4.4 to JB ?
*I'm rooted with unlocked BL running stock rom

There is no known way to downgrade the Bootloader (to the 4.3 compatible-version) and you should be warned it is dangerous to experiment in this area. The 4.3 Kernel will not boot with an updated Bootloader.

Moto G Won't boot anymore.

Hello Guys,
after a week using Paranoid Android my moto g xt1032 acted weird, so I reinstalled stock using fastboot.
I am pretty familiar with the use of fastboot and flashing and so on (Guess I've flashed, and fixed over 20 different phones)
But now I've come to the point I can't even fix my own phone.
What does it do?
Well, when I start my phone, it will only show the "warning bootloader unlocked" message, and just restarts and does the same.
Sometimes it even gives a blue screen > restarts.
I can boot into fastboot mode, I tried to flash a RETAIL UK 4.4.2 And RETAIL UK 4.3 stock firmware, even though I am from The Netherlands,
but UK or German roms are the closed to mine, and as far as my knowledge goes, EU firmware are usually the same.
I managed to go into stock recovery, but when I flash philz or twrp, it just stays at the "warning bootloader unlocked" screen.

Going to try XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip right now.

same result.

bump

bump

Try this - http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
While my situation below may not be yours, at least this may get you back to a stable and functional device. I hope it helps. And as you are aware this will COMPLETELY wipe your phone. If you can, backup any pictures or files you want to keep before doing this.
My situation was like many others that had flashed a 4.4.4 GPE or custom ROM and ended up with a mini wifi tablet as the radio was off (as stated by dialing 8#8#4626#*#*). I have gone two days with no cell signal due to this. Trying to flash a stock image (http://sbf.droid-developers.org/phone.php?device=14) resulted in boot loops. I believe that is what everyone else is calling it. I never saw the loop as it stayed on the initial logo screen before the animation begins. Maybe it is looping fast and just showing the same screen again instead of it simply not changing. Oh well. I'm fixed now but on EU ROM. Now I'm attempting to install Blur_Version.174.44.1.falcon_umts.Retail.en.US. The EU ROM currently installed is 176.44.1, and while it works I simply want to be stock US version for now. I mention this because there is also a 174.44.4 US ROM on SBF-DROID-DEV. I tried that one (among many others) when trying to revive my phone. None of the stock images worked and I'm currently not happy with any of the custom ROMs. Stock or rooted stock will be good for me. On a tangent but I have a XT1032 purchased from AIO Wireless (now Criket but still part of ATT). Well AIO tweaked Motorola's ROM to disable tethering. I actually use Red Pocket for service (another ATT MVNO) and only bought from AIO becausse they had a sweet deal. Wasn't so sweet after I found I could not tether and after 6 months found a way to unlock bootloader, which cost another $25. In short it spent just as much money and had much frustration that could have been avoided if I had purchased directly from Motorola and got a FULLY stock and unlockable device.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
Pass this along also to anyone looking: theroot.ninja worked for me to unlock the bootloader (I've not posted enough to XDA so posting true URL is disabled. Google "sunshine bootloader unlock"). I found a vague reference on XDA somewhere but don't recall thread. Basically, certain carriers (like ATT and its MVNOs) have agreement with Motorola to restrict bootloader unlocking on devices they resell. Like I said, cost me $25, but it worked and I've wasted more $$ on less.

My bootloader is unlocked, I can't get into recovery, only fastboot.
and it stays at the "warning bootloader unlocked screen" aka logo screen, and it restarts so now and then.
When I start it up for the first time, the screen turns blue right away, and restarts, after a couple of restarts, it stays stuck on the logo screen :S
I tried lots of stock firmware, but none of them worked, I wonder if it's a hardware fault, but I reassembled everything, without success.

http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.

lost101 said:
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
Click to expand...
Click to collapse
I am pretty sure I am using 4.4.4
I used these commands:
Code:
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_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache

I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​

lost101 said:
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​
Click to expand...
Click to collapse
Tried it, no change.

Jur13n said:
Tried it, no change.
Click to expand...
Click to collapse
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.

meekrawb said:
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
Click to expand...
Click to collapse
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing

Jur13n said:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Click to expand...
Click to collapse
Okay. Good luck!

Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.

e.martin.howell said:
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=14 is offline atm, I'll try it.
What do you mean with three downloads o.o?
I only see him saying Blur_Version.174.44.1.falcon_umts.Retail.en.US

Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​

lost101 said:
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​
Click to expand...
Click to collapse
Tried it, didn't work.
Going to try the Blur_Version.174.44.1.falcon_umts.Retail.en.US one right now.

-- edit --
no result, also tried to convert it to gpe, no result either.
I guess it's a hardware problem somehow (maybe reading the harddisk fails?)

If you still have the box that the phone came in look at it and it will tell you which Moto G you have.

Moto G (2013) GPE 5.0.1 to Motorola´s 5.0.2

Hello guys, I´m in doubt here, and although i´ve been reading some posts, I cannot seem to understand the procedure to install Motorola´s 5.0.2 in my Moto G, actually on 5.0.1 GPE.
As far as I know, I need to wipe it off, then convert partitions to f2fs and then flash via custom recovery?
I´ve tried twice, but cannot install TWRP, will try with Phillz.
BTWy, my device is rooted and bootloader unlocked.
Thanx for any guidance you may lend me, I´m at work and cannot dwelve deep into hundreds of threads. I have already downloaded Blur_Version.210.12.40.falcon_umts.Brasil.en.BR.zip the official Motorola 5.0.2.
Thanks!!

you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF

Thanx!
Well thank.you sir, very informative response.
Just to be super super-sure, no need to un-root or lock the bootloader right?
AgentChaos said:
you need the 4.4.4 firmware first and mfastboot v2 files to go back to stock motorola firmware.
and since you updated to 5.0.1 GPE, your bootloader has been updated, so when you downgrade to 4.4.4, you will see screen flickers.
Here are the commands,you must enter these commands one by one using command prompt (hold shift, and right click and choose open command window here) in the folder where the firmware files are (including the mfastboot files)
connect your phone to the computer with usb cable and type the command to go into the bootloader
adb reboot bootloader
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and you need this firmware to be installed first before installing the lollipop update
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF
Click to expand...
Click to collapse

Hello guys I would like to do the same, I have the Gpe and install Motorola 5.0.2, but before I want to know how to fix the flicker screen, I don't get it using android but when I'm on twrp, it's annoying, do you have any idea how to fix it?
Sent from my XT1058 using XDA Premium 4 mobile app

nice!
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.

donlloreda said:
So i´ve flashed 5.0.2, with the method described here, it was *too* easy.
I did not, how ever, get the flickering screen bug...
So thanks again. and this is a safe way to go from gpe 5.0.1 to moto 5.0.2.
Click to expand...
Click to collapse
Which recovery do you have?

antarix said:
Which recovery do you have?
Click to expand...
Click to collapse
Stock recovery mate, well my happy story has come to a misterious error I cannot by any means sort out..
please see this post: Weird issue

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.