Database Info

Can;t restore/flash phone!

So I followed the [GUIDE] Moto G - Restore stock firmware
However, when I get to step 2 it asks me to type in the folder the firmware is located and I do that and press enter but it just keeps popping up asking for another input. The copy address is:
Code:
C:\Users\[name]\Desktop\US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml\US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(http://i.imgur.com/VKVEvzM.png?1) <--- Link incase picture does not load.
Can someone please explain to me what I am doing wrong?
Thank you!

Help
Anyone Please?
Thank you![/QUOTE]

Canuckfan101 said:
Can someone please explain to me what I am doing wrong?
Thank you!
Click to expand...
Click to collapse
in the guide, did you do the c)?
If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
edit:
if the downloaded stock firmware is xml.zip then:
1. download drivers and everything from that guide steps a), b), c) and d)
1. make new folder named whatever you want (for example aaa) in C:\ directory
2. extract with WinRar downloaded firmware into that directory (in my example it's C:\aaa\ so extracting there)
3. download mfastboot-v2.zip and extract it in that directory (c:\aaa\) too
4. copy all files from C:\Program Files\Minimal ADB and Fastboot into that directory too
5. connect phone to PC and reboot to bootloader
5. open cmd.exe as admin and type: cd c:\aaa\
6. copy and paste commands in that guide in step 3b)

2hipso said:
in the guide, did you do the c)?
edit:
if the downloaded stock firmware is xml.zip then:
1. download drivers and everything from that guide steps a), b), c) and d)
1. make new folder named whatever you want (for example aaa) in C:\ directory
2. extract with WinRar downloaded firmware into that directory (in my example it's C:\aaa\ so extracting there)
3. download mfastboot-v2.zip and extract it in that directory (c:\aaa\) too
4. copy all files from C:\Program Files\Minimal ADB and Fastboot into that directory too
5. connect phone to PC and reboot to bootloader
5. open cmd.exe as admin and type: cd c:\aaa\
6. copy and paste commands in that guide in step 3b)
Click to expand...
Click to collapse
I followed the steps but nothing happened same problem here is what i got :
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd C:\FIrmware
C:\FIrmware>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.437s]
finished. total time: 0.470s
C:\FIrmware>mfastboot flash motoboot.img
unknown partition 'motoboot.img'
error: cannot determine image filename for 'motoboot.img'
C:\FIrmware>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.087s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.522s]
finished. total time: 1.615s
C:\FIrmware>mfastboot flash logo logo.img
target max-sparse-size: 256MB
error: cannot load 'logo.img': No error
C:\FIrmware>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.072s]
writing 'logo'...
OKAY [ 0.127s]
finished. total time: 0.207s
C:\FIrmware>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 1.112s]
finished. total time: 1.478s
C:\FIrmware>mfast flash recover recovery.img
'mfast' is not recognized as an internal or external command,
operable program or batch file.
C:\FIrmware>mfastboot flash recovery recover.img
target max-sparse-size: 256MB
error: cannot load 'recover.img': No error
C:\FIrmware>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.370s]
writing 'recovery'...
OKAY [ 1.149s]
finished. total time: 1.526s
C:\FIrmware>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (260606 KB)...
OKAY [ 8.214s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.112s]
finished. total time: 22.333s
C:\FIrmware>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (239692 KB)...
OKAY [ 7.620s]
writing 'system'...
OKAY [ 14.548s]
finished. total time: 22.173s
C:\FIrmware>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (222205 KB)...
OKAY [ 7.004s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.217s]
finished. total time: 30.229s
C:\FIrmware>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47484 KB)...
OKAY [ 1.536s]
writing 'modem'...
OKAY [ 2.395s]
finished. total time: 3.936s
C:\FIrmware>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.025s
C:\FIrmware>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.025s
C:\FIrmware>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (721 KB)...
OKAY [ 0.110s]
writing 'fsg'...
OKAY [ 0.136s]
finished. total time: 0.253s
C:\FIrmware>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.069s]
finished. total time: 0.071s
C:\FIrmware>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.254s
C:\FIrmware>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\FIrmware>

Canuckfan101 said:
I followed the steps but nothing happened same problem here is what i got :
C:\FIrmware>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (260606 KB)...
OKAY [ 8.214s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.112s]
finished. total time: 22.333s
C:\FIrmware>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (239692 KB)...
OKAY [ 7.620s]
writing 'system'...
OKAY [ 14.548s]
finished. total time: 22.173s
C:\FIrmware>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (222205 KB)...
OKAY [ 7.004s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.217s]
finished. total time: 30.229s
Click to expand...
Click to collapse
Change those three commands to:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system sysyem.img_sparsechunk.3
and try again. Who knows why that guide has never been corrected.

meekrawb said:
Change those three commands to:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system sysyem.img_sparsechunk.3
and try again. Who knows why that guide has never been corrected.
Click to expand...
Click to collapse
Thanks for the reply!
Okay is that the reason why I am also getting several errors like PIV or invalid signature in purple on my phone

While flashing the images i am getting, "Image is too large" error in bootloader screen of the phone.
Can anyone please help me with it?

Moto g stuck in bootloop! Tried flashing etc!

Hi, I've tried flashing but my phone keeps restarting.
CMD gives me this:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.033s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.444s]
finished. total time: 0.483s
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.539s]
finished. total time: 1.657s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.347s]
writing 'boot'...
OKAY [ 1.097s]
finished. total time: 1.450s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.365s]
writing 'recovery'...
OKAY [ 1.118s]
finished. total time: 1.490s
target reported max download size of 536870912 bytes
sending 'system' (260606 KB)...
OKAY [ 8.202s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.050s]
finished. total time: 22.259s
target reported max download size of 536870912 bytes
sending 'system' (239692 KB)...
OKAY [ 7.569s]
writing 'system'...
OKAY [ 14.513s]
finished. total time: 22.089s
target reported max download size of 536870912 bytes
sending 'system' (222205 KB)...
OKAY [ 7.007s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.327s]
finished. total time: 30.342s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.540s]
writing 'modem'...
OKAY [ 2.384s]
finished. total time: 3.930s
erasing 'modemst1'...
OKAY [ 0.069s]
finished. total time: 0.072s
erasing 'modemst2'...
OKAY [ 0.115s]
finished. total time: 0.119s
target reported max download size of 536870912 bytes
sending 'fsg' (721 KB)...
OKAY [ 0.116s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.228s
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.122s
erasing 'userdata'...
OKAY [ 0.282s]
The error I get on Moto G is :
Code:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system
Motorola Driver tells me my firmware is: But I've used this firmware and same error !!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks In advance!

That image is 4.4.2. Maybe try the 4.4.3 Retail US image here:
http://sbf.droid-developers.org/download.php?device=14&file=928​

This worked for me - http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Took additional step and loaded Blur_Version.174.44.1.falcon_umts.Retail.en.US from sbf.droid-developers.org/phone.php?device=14
This will get you a usable device again with 4.4.2 or use the 4.4.3 as mentioned by lost101
Good luck.

e.martin.howell said:
This worked for me - http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Took additional step and loaded Blur_Version.174.44.1.falcon_umts.Retail.en.US from sbf.droid-developers.org/phone.php?device=14
This will get you a usable device again with 4.4.2 or use the 4.4.3 as mentioned by lost101
Good luck.
Click to expand...
Click to collapse
Should I go to the first page of the guide or to the comment?

Canuckfan101 said:
Should I go to the first page of the guide or to the comment?
Click to expand...
Click to collapse
Sorry. First page.
http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
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.

I took the phone to my repair shop and they said it couldn't be repaired because of physical damage to the circuit board. But I believe that is not the case as the phone is in mere perfect condition

First of all, are you sure of the model?
If XT1032, try again, this time with the EU Retail 4.4.4 image. It doesn't matter where you are in the world.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​
If XT1034 (AWS), here is a compatible 4.4.4 image:
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354​

Hi, i checked my customer agreement and it says TXT1032, I sent it in for repair but they said it can't be fixed. Maybe due to the fact its unlocked.

Is there anyone who can help please!!

Have you followed the guides above?

Canuckfan101 said:
Is there anyone who can help please!!
Click to expand...
Click to collapse
Using a 4.4.4 firmware image, follow this post:
http://forum.xda-developers.com/showpost.php?p=56123205&postcount=8​

Yes I have and I either get errors or it does not work.

Did you erase userdata? Erase everything, flash stock firmware, erase userdata and cache after and boot after that.

XT1032 - unable to run system

MORE INFO: I would like to add that my bootloader is 41.19 and that bootloader/fastboot and recovery works ok. Only when I try to start system, it ends at BOOTLOADER UNLOCKED. I tried 4.4.4, 5.0.2 and 5.1 ... and none of them works ... And in TWRP, I can see "Unable to mount /cache" and "Unable to mount /system" ...
Hi, Ive got a problem:
Ive been using the stock DE 4.4.4. ROM + 5.0.2 OTA on my XT1032 fine for about six weeks. Today I wanted to lock it, so I
1) entered "sudo fastboot oem lock begin" (Im on Linux Mint btw)
2) flashed the DE 4.4.4 ... and the phone just doesnt boot to system; there is the WARNING BOOTLOADER UNLOCKED message and thats it.
The bootloader is still unlocked of course. And I dont think the problem is related to the locking ...
These are the commands I used (they are just from the DE 4.4.4 ROM):
Code:
sudo fastboot flash partition gpt.bin
sudo fastboot flash motoboot motoboot.img
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot reboot
And this is the output
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.305s
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.365s
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.208s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
OKAY [ 0.794s]
finished. total time: 1.166s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.375s]
writing 'recovery'...
OKAY [ 0.770s]
finished. total time: 1.146s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.639s]
sending 'system' (255397 KB)...
OKAY [ 8.085s]
writing 'system'...
OKAY [ 12.824s]
finished. total time: 21.548s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.576s]
sending 'system' (254868 KB)...
OKAY [ 8.054s]
writing 'system'...
OKAY [ 10.562s]
finished. total time: 19.192s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.608s]
sending 'system' (231159 KB)...
OKAY [ 7.294s]
writing 'system'...
OKAY [ 19.144s]
finished. total time: 27.046s
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 1.407s]
finished. total time: 2.934s
erasing 'modemst1'...
OKAY [ 0.065s]
finished. total time: 0.065s
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 5.611s]
finished. total time: 5.693s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.415s]
finished. total time: 0.415s
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
rebooting...
finished. total time: 0.001s
And when I try to sideload the OTA phone says "Installation aborted" ...
Im using the same files I used six weeks ago.
I tried EU 4.4.4 but it is not working either - theres only Motorola logo and thats it.
Any suggestions, please?

The gpt.bin and motoboot files won't flash because you are trying to downgrade both versions which cannot be done.
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.

Alright, my not-so-perfect yet-working solution.
I flashed TWRP. In the recovery (wipe-advanced-repair or format) I realized that all the partitions (system, cache, data) are corrupted and showing size zero. So I formatted all of them to ext4 and (just to be sure) ran REPAIR.
After repairing the partitions I enabled MTP - it didnt show in my PC, but reboot helped - and copied GPE 5.1 Untouched (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) into the storage. Then, I installed the ROM in TWRP and rebooted - dont let the recovery install SU, it ended in loopback (during first boot only: after successfully entering my google information and rebooting into recovery, I let it install SuperSU and it worked fine).
Voila, phone working again.
I checked the process once again and it worked. But when I try to flash anything now, partitions get corrupted. Weird.
audit13 said:
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.
Click to expand...
Click to collapse
I know, but I was going to sell the phone and I hoped relocking would make the Warning Bootloader Unlocked sign go away. Later, I read it doesnt - too bad.
But generally I'm quite satisfied now - the phone has a newer system, no Bootloader Warning, it has Czech language now and the new user is a total newbie so Im glad that (thanks to the TWRP) she wont lose her internal storage files when doing factory reset.
UPDATE: I flashed stock recovery (Brazilian 5.0.2) to make Factory reset be able to format even the /media/data partition, as was intended. Just to make sure the partition can be wiped in case of trouble. GPE 5.1 recovery didnt work btw.

sorry people, may be yo´ve heard about but if you know about the mbm-ci5 files needed to un hard brick a moto g ??? do you thing there is a hope o may be other methods to unbrick a moto g xt 1032 - sorry if its not the right place, just looking for help to revive mines...

Blue Screen after booting up, any tips? I have already tried flashing new stock rom!

My xt1033 has been acting up and I can't boot it anymore. It literally finishes the boot on a full blue screen (nothing on the screen but the blue) and reboots. I have tried flashing a new rom following both "[GUIDE] Restore softbricked phone after Lollipop update" and "[ROM][4.4.4][STOCK][FLASHABLE ZIP] Stock Motorola KitKat ROM Collection" found on the stickies but they didn't fix my issue and now I am out of ideas... can someone please help me?
Thanks.

Follow the flashing instructions in first post exactly:
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection​

Wipe data via recovery or fastboot. This #$%$#%# bug is pretty common on Motorola's stock ROM.

Tried both recommendations and different stock roms (4.4.4, 5.0.2, 5.1 untouched and patched) and it simply won't boot... Decided to give CM a go, and it works on the first try. I guess I wil have to learn how to use CM...
Edit: And I was happy for only a few minutes... back to square 1 and bs resets/blue screens

dambros666 said:
Tried both recommendations and different stock roms (4.4.4, 5.0.2, 5.1 untouched and patched) and it simply won't boot... Decided to give CM a go, and it works on the first try. I guess I wil have to learn how to use CM...
Edit: And I was happy for only a few minutes... back to square 1 and bs resets/blue screens
Click to expand...
Click to collapse
In TWRP, did you Format Data (Wipe > Format DATA > Yes) ?

lost101 said:
In TWRP, did you Format Data (Wipe > Format DATA > Yes) ?
Click to expand...
Click to collapse
Yes, I always start the process by doing it, as specified in the threads.

It sounds to me like a hardware fault. Maybe try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
It sounds to me like a hardware fault. Maybe try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I am starting to consider to be a hardware fault as well. I already tried the factory firmware, same result :/ Just one thing about wiping data: should I do it AFTER finishing the flash as well?

dambros666 said:
I am starting to consider to be a hardware fault. I already tried the factory firmware, same result :/ Just one thing about wiping data: should I do it AFTER finishing the flash as well?
Click to expand...
Click to collapse
Provide a log - copy and paste command prompt screen - take screenshots. Fastboot cannot be trusted, flashing can completely fail without a single error message.

lost101 said:
Provide a log - copy and paste command prompt screen - take screenshots. Fastboot cannot be trusted, flashing can completely fail without a single error message.
Click to expand...
Click to collapse
This is the log for the Factory Firmware XT1033_FALCON_RETBR_DS_5.1_LPB23.13-56_cid12
Code:
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.313s]
finished. total time: 0.342s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.114s]
finished. total time: 1.215s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.060s]
writing 'logo'...
OKAY [ 0.096s]
finished. total time: 0.157s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.377s]
writing 'boot'...
OKAY [ 0.917s]
finished. total time: 1.295s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.387s]
writing 'recovery'...
OKAY [ 0.920s]
finished. total time: 1.309s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257535 KB)...
OKAY [ 8.095s]
writing 'system'...
OKAY [ 16.439s]
finished. total time: 24.536s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256925 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 15.465s]
finished. total time: 23.545s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (256980 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 15.421s]
finished. total time: 23.502s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (175936 KB)...
OKAY [ 5.549s]
writing 'system'...
OKAY [ 11.219s]
finished. total time: 16.770s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.607s]
writing 'modem'...
OKAY [ 2.228s]
finished. total time: 3.836s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.036s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.066s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.093s]
writing 'fsg'...
OKAY [ 5.315s]
finished. total time: 5.409s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.096s]
finished. total time: 0.097s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.721s]
finished. total time: 1.721s
d:\Users\Marinho\Desktop\New folder>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s

Everything looks okay with the flashing process. I've never heard of the issues you describe before.

lost101 said:
Everything looks okay with the flashing process. I've never heard of the issues you describe before.
Click to expand...
Click to collapse
I took some rain last week, and I am guessing it was the problem...
This is what I see after thr boot, and then it resets:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I got the same issue today, please help. Mine is pure stock lolipop 5.1.1

same issue, I have tried different kernels, roms and recovery but, still same. Is there anybody who knows how to fix this?

Facing the same problem.Getting restarted automatically and stucked at Blue scree.
It look like a hardware problem. Anyone tried to contact motorola service center?

same problem with blue screen stucked sometimes
Hi all... i have the same problem. my phone moto g xt1032 is stucked at blue screen sometimes.... i tried different roms and recovery and still the issue
the last i tried it was check on logcat in adb, waiting... and when the phone is stucked on blue screen... the log cat say something about... corruption internal...
sorry i cant save the screenshot of the logcat
actually i have installed the last stock firmware 5.1 EU version with the stock recovery
sorry for my poor english
@lost101 can you help me please??

@manjs - Via a PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

hi, i also got this problem.. i think its a hardware problem..

appu1988 said:
hi, i also got this problem.. i think its a hardware problem..
Click to expand...
Click to collapse
Most likely. It's certainly not a software issue I have ever seen.

Just insert a sim card
idk how but it solved in my case.

How can i make my moto g dual sim again...

Hi this is my first request for help ever, have tired almost all roms available on xda
I never needed to touch my rom till was on kitkat, i had heard the hole world crying for bugs with kitkat but my phone never reported any major bug (i had not even rooted my phone) then came the curse LOLIPOP 5.02 there were two things that made me force to unlock bootloader 1> slow 2nd> ghost windows showing up in taskbar
from the day i flashed to stock rom kitkat 4.4.4 us retail (xt1032) availabe on xda forum i lost my second sim working
till this date i have flashed endless roms even cwm 12 and all versions of stock for asian retail have not tried flashing and brazil fimware.
it just doesn't detect if any sim is inserted.
i have tried the stock radio thread for kitkat 4.4.4 , 5.02, 5.1 none of them work.
If anyone is having moto g xt1033 indian stock rom with dual sim working
can you please send me a screen shot of about section in settings
i want to check what baseband version you guys are having
one last thing i had made a backup using cynogen recovery but on restoring the backup my moto g never boots it was of stock lolipop can anyone help in this regards..
currently am on stock lolipop 5.1
my baseband version is MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
i think 1032 in above baseband means radio of xt1032 while i need 1033 (i guess)
i have updated using indian ota update of stock rom using stock recovery.
Issue still persists sim 2 not detected, both sims used to work before flashing any firware manually.

Simply flash the latest XT1033 Retail Asia 5.1 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log of the flashing process if this does not resolve your problem. Copy and paste the contents of Command Prompt. Take screen-shots if necessary.

edit: above method

new problem
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

huzeifa88 said:
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
Click to expand...
Click to collapse
now flashed 5.02 and it too just shows me the boot logo saying warning bootloader unlocked nothing else is happening getting a little tense now log for 5.02
C:\adb>flash.bat
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

Please stop trying different Firmware Images. Only do as directed for your own safety.
Edit: Manually type commands, do not use a .bat file or script. Skip the command related to motoboot.img - repeatedly flashing the Bootloader is dangerous and completely unnecessary.
Type the following command before any other:
mfastboot oem unlock​

lost101 said:
Please stop trying different Firmware Images. Only do as directed for your own safety.
Click to expand...
Click to collapse
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.

bootleoader version is 41.1A system is 5.02
huzeifa88 said:
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.
Click to expand...
Click to collapse
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.

huzeifa88 said:
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.
Click to expand...
Click to collapse
Stop flashing / messing with the Bootloader. Period. You will end up with a dead phone.

Finally back from dead
I flashed kitkat stock rom without trying to downgrade boot loader as i knew it could brick my phone and just as usual phone did not boot past boot logo of boot recovery stating boot loader unlocked...
but my luck turned kitkat stock rom recovery started to work without wasting time i flashed twrp recovery over kitkat stock recovery
once twrp i flashed cm12 last stable built volla cm12 booted
now still only one sim will work but i guess i had enough experiments i had once tried the donkey kernel on cm12 it never booted. so lets forget dual sim.
please dont recommend anyone to flash 5.1 stock rom i has some bug never boots or maybe coz i already had 5.1 installed using ota method.

@huzeifa88 - You are going to destroy your phone. I have tried to help you, but you ignore what I say.
Do not flash old Firmware Images and then accept an OTA Update. Your phone will switch off and never turn on again. I have already warned you to stop trying random Firmware Images.

phone doesnt boot on 5.1 had no options
I did flash the 5.1 lolipop image but phone did not boot it would just kept stuck at bootloader spash image (White color image saying boot loader unlocked) and did not reach the motorola animated boot screen
I left it there for around 30 mins after which i was sure its not gonna boot
Again even tried deleting all data and cache using fastboot command
even the recovery would not open it would stay on the bootloader splah screen
what i am experiancing with this phone is rare and happened 1st time maybe all those who have updated their boot loader should not mess with there cell anymore
anyway all is GOOD now i am HAPPLY using CM12 ROM and am never gonna flash any stock rom again.