Database Info

mfastboot' is not recognized as an internal or external command

hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
3b) If you downloaded and extracted a firmware in .xml.zip format.
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
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
mfastboot erase userdata
mfastboot reboot

AndroidHtc101 said:
hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
Click to expand...
Click to collapse
Sounds like you don't have mfastboot.exe in the same folder as the files you are trying to flash. Make sure you have downloaded and extracted THIS package to the same folder as the firmware you're flashing.

hi finish i put fastboot in working until now i get this error
mfastboot flash system system.img_sparsechunk2 max sparse size 256 error cannot load system image
thanks for your help on this one

Confirm that you are inputing the correct filenames. For example my first system chunkfile number was zero, and maybe it had a dot before the number.

There is an XT1032 Global GSM 4.4.4 firmware image now available:
http://forum.xda-developers.com/showpost.php?p=54365926&postcount=292​
It's intended for Retail Brasil, but should work anywhere.

Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash

AndroidHtc101 said:
Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash
Click to expand...
Click to collapse
You're welcome.

One quick question Ive noticed I dont have superuser do I needed to do that all again after i upgrade to 4.4.4?
cheers

To avoid possible problems with upgrading process, first upgrade and then re-root.

ok thanks
Did that last process make my bootloader locked again? It was so long ago cant remember how I unlocked bootloader and rooted

No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/

Finnish Flash said:
No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
Click to expand...
Click to collapse
thanks for all your help:_)

XT1039 now showing as XT1032

I softbricked my Moto G 4G this morning & the only way I could get it out of the bootloop was to flash with a X1032 firmware. I have subsequently managed to flash the latest stock XT1039 ((Moto_G_LTE_XT1039)_RET-EU-SS_4.4.4_KXB21.14-L1.46_cid7_CFC_1FF.xml) firmware but when I plug the phone into my PC it is shown as XT1032. Is there anything I can do to revert it back to its correct model number?

Did you use an included .bat file to flash or a series of fastboot commands? If the latter, what commands?

lost101 said:
Did you use an included .bat file to flash or a series of fastboot commands? If the latter, what commands?
Click to expand...
Click to collapse
Its was an included bat file. I used the files from this thread
http://forum.xda-developers.com/moto-g/help/easy-unbrick-moto-g-restore-4-4-4-stock-t2850282

You might want to consider doing the fastboot commands manually. If all commands are used, ant trace of XT1032 should be gone.
http://forum.xda-developers.com/showthread.php?t=2542219​

lost101 said:
You might want to consider doing the fastboot commands manually. If all commands are used, ant trace of XT1032 should be gone.
http://forum.xda-developers.com/showthread.php?t=2542219​
Click to expand...
Click to collapse
That was the method I used after using the bat file.
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
mfastboot reboot
these all worked OK without issue
I had to modify the sparsechunk files to match the ones in the rom that i downloaded

All Models of Moto G have 1032 in the baseband, is it possible your phone was always recognised on PC as XT1032?

It was definitely showing as1039 before the soft brick

Then obviously something is remaining from the XT1032 firmware. If you have a Custom Recovery, try the wipe options there.
Alternatively, the following command in Fastboot might be enough: fastboot erase system
BTW, never use the Fastboot command: fastboot erase all

lost101 said:
Then obviously something is remaining from the XT1032 firmware. If you have a Custom Recovery, try the wipe options there.
Alternatively, the following command in Fastboot might be enough: fastboot erase system
BTW, never use the Fastboot command: fastboot erase all
Click to expand...
Click to collapse
I have tried the wipe option before. I will try fastboot erase system then reflash the stock rom

This didn't solve the issue

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

Messed up my Moto G, really need some help please :(

Hey guys. I got a telus moto g xt1032. It was on official 5.0.2. I flashed TWPR 2.8.5.0, and encountered the bootloop bug. I proceeded to flash the only stock telus firmware i could find- 4.4.4. I followed the guide on XDA to the tee and resulted in my moto go being stuck at the "Warning, boot loader unlocked" screen. I have no idea what to do and would really appreciate some help, as I am new to this. Am even willing to donate if it results in me fixing my phone. Thank for taking the time to read

Try doing the following Fastboot commands manually:
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_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.

lost101 said:
Try doing the following Fastboot commands manually:
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_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
I also have this problem. I am trying to downgrade to 4.4.4 stock firmware (from 5.02) and I'm getting an this error:
$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.042s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.336s
Click to expand...
Click to collapse
All the other commands are successful but the device remain stucked on the boot screen after the reboot :crying:

I have this problem too, trying to factory reset my phone but it's still stuck on the bootloader. CWM says can't mount sd card now aswell so any help would be appreciated

I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1

lost101 said:
Try doing the following Fastboot commands manually:
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_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways

audit13 said:
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP

butthurtlocker said:
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
Click to expand...
Click to collapse
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.

butthurtlocker said:
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
Click to expand...
Click to collapse
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.

lost101 said:
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
Click to expand...
Click to collapse
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?

audit13 said:
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
Click to expand...
Click to collapse
did that file have a boot.img?

butthurtlocker said:
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
Click to expand...
Click to collapse
Fastboot Tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219​

Yes, the boot.img file is included.

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.