Database Info

[frustration free] restore to stock firmware moto g all versions

Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck

Reserved

reserved...:cyclops:

Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!

flowerpoweruk said:
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!
Click to expand...
Click to collapse
I am glad it helped you. Enjoy the amazing device.

my phone german retail. can i use this tutorial?

sinkadorable said:
my phone german retail. can i use this tutorial?
Click to expand...
Click to collapse
I think so. Just give a shot. if it doesnt work then just replace the stock firmware from GB to DE. Alles Beste!

it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
DONE!! i havent put the adb files in the firmware folder, but has flashed flawlessly now!! thank you for this solution!! :good:

Xin_TiGeR said:
it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
Click to expand...
Click to collapse
What would you like to achieve? / is your Moto G stuck in loop after factory reset? Give a full background about the issue

Thank you.It works.Excellent.

Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
What is meant by this ? what exactly am I removing ? Do I need to rename it to the firmware I am about to flash?
Cheers.
EDIT: I figured it out, I just had a noob moment in my despair and couldn't take the information in, What a difference some nicotine and a cuppa makes!
Thanks OP great work.

Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
help me guys
2 days back I was using my fone and it juz went off blank screen. tried many times with power button bt nothing. den went it to fastboot mode and tried recovery/normal powerup/factory but everytime got msg "failed to validate system image". followed d procedure given here http://forum.xda-developers.com/showthread.php?t=2700502 and got this result
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd..
C:\Windows>cd..
C:\>g:
G:\>cd moto g
G:\moto g>mfastboot.exe oem lock begin
...
(bootloader) Device is already locked!
OKAY [ 0.014s]
finished. total time: 0.016s
G:\moto g>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.001s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.396s
G:\moto g>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 5.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 11.343s
G:\moto g>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 5.059s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.084s
G:\moto g>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.554s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 11.077s
G:\moto g>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.532s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 11.061s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 19.204s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 33.653s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (237949 KB)...
OKAY [ 17.387s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 25.518s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (243326 KB)...
OKAY [ 18.015s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 34.875s
G:\moto g>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 7.540s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 12.576s
G:\moto g>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
G:\moto g>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 5.056s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.090s
G:\moto g>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.995s
G:\moto g>mfastboot.exe oem lock
...
(bootloader) Device is already locked!
OKAY [ 0.012s]
finished. total time: 0.015s
G:\moto g>pause
Press any key to continue . .
any solution guys

Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app

feartheanonymity said:
Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
does unlocking void the warranty?

yasir1234 said:
does unlocking void the warranty?
Click to expand...
Click to collapse
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.

26286998 5107
feartheanonymity said:
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.
Click to expand...
Click to collapse
how do I do dat?can u pls give me steps to do so..

well there are many threads explaining how to unlock bootloader, It basically consists of getting a code through adb, putting that code onto motorola website, getting the code and sending it to the phone. check the guides in the general section.
as for relocking it, is as simple as going into fastboot and typing (in adb / fastboot) fastboot oem lock.

Moto G Stuck in Boot Loop! Help
When I flash the stock firmware I keep getting these error messages
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
(bootloader) Failed to validate sparse image
and these all end with
FAILED (remote failure)
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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.448s]
finished. total time: 0.486s
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.490s]
finished. total time: 1.603s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.915s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.948s
target reported max download size of 536870912 bytes
sending 'system' (260606 KB)...
OKAY [ 8.415s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.950s
target reported max download size of 536870912 bytes
sending 'system' (239692 KB)...
OKAY [ 7.770s]
writing 'system'...
OKAY [ 9.293s]
finished. total time: 17.065s
target reported max download size of 536870912 bytes
sending 'system' (222205 KB)...
OKAY [ 7.165s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.684s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.583s]
writing 'modem'...
OKAY [ 1.304s]
finished. total time: 2.890s
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.068s
target reported max download size of 536870912 bytes
sending 'fsg' (721 KB)...
OKAY [ 0.125s]
writing 'fsg'...
OKAY [ 0.104s]
finished. total time: 0.231s
erasing 'cache'...
OKAY [ 0.362s]
finished. total time: 0.364s
erasing 'userdata'...
OKAY [ 2.560s]
finished. total time: 2.562s
I have tried to flash many different firmwares on it to get it out of the boot loop like "US Retail" (4.3 and 4.4.2), "Boost US" (4.3 and 4.4.2), and "Verizon US" (4.3 and 4.4.2). This always results in one of the 3 error messages or more. I have found the one that works with the least error messages is the Boost US firmware for 4.4.2 and it gives only the error message (bootloader) Failed to validate sparse image on the 3rd system file. Whenever I try to install the firmware it doesn't seem to work, and it results in the phone turning on with the Motorola logo then the phone vibrates once then turns off and repeats, or the phone shows the android logo on its back with the exclamation point after the single vibration and sits like that until it turns off a few minutes later repeating the process. I have tried everything including trying to boot normally, resetting to factory, going into recovery and wiping cache and deleting all data, and even attempting to install from ADB. I have actually successfully done this process before a few hours before trying it on this one where it ended up like this. I looked this up and apparently you can still fix the phone if it can reach the boot loader screen, but when I was working with the phone I forgot to put it in developer mode and turn on USB debugging so that might be an issue. If there is a way I could fix it that would be very helpful, but if it doesn't I can still return the phone in the next 4 days.
Thanks for the help!
Extra Info:
The phone's bootloader is locked and because it is new I do not have any backups.
Also I already have these following programs
Minimal ADB and Fastboot
RSD Lite
DFS
Mfastboot v2
r1-motog-modifiedrecoveryroot.zip
adt-bundle-windows-x86_64-20140321.zip
platform-tools.zip
Fastboot+ADB(20926).zip
adbfix.zip
These are all from other threads that have explained this issue but the fix they provided did not work.
Thanks Again!

Guys, I have a Moto-G that was sold to me as a XT-1032 US global GSM model. The guy who sold it to me said that after the OTA update for 4.4.2 was applied to his phone it never would see a signal again, and kept saying to turn off airplane even though it saw that a sim was installed. looking at the status it kept saying the radio was turned off. When I got it from him it was showing the unlocked bootloader message, but when I checked the status on the fastboot screen it was showing locked status 2, which indicates it had never been unlocked. I unlocked the bootloader and started trying different versions of the firmware to see if I could fix the issue, but nothing ever worked until I tried this method.
I only flashed the radio from the GB 4.4.2 version that the OP had provided the XML file for using the modified xml file he provided, and now my cell radio is working again. Since I had already voided any warranty on it, I went ahead with flashing the CWM recovery and the latest nightly for CM11 and it's working beautifully, very smooth. I had bought this for my wife if I could fix it, so now she's getting a nice upgrade from her old GSM galaxy nexus that had started developing issues where it had to be rebooted to get the radio to work again (on the stock 4.3 firmware mind you, just a hardware problem I think due to it's age)
So in short Thanks OP!!

Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
Thanks for posting this since my phone is having these exact issues! I was a little unsure of what you meant in step 1 above, so what I did is take the sample XML which you attached to the post and replaced the software version info in the header with the version information for my carrier's firmware. Not sure if that was what I was supposed to do. Anyway, everything works great except that it is failing to flash motoboot.img. The command windows says it's a remote error- preflash validation failed, and the phone displays an error that says the version has been downgraded for tz. Any ideas would be greatly appreciated!

[Q] question about a brick problem with motorola moto g (2013)

hello guys from XDA, my problem is this, I have a moto motorola g (2013) I install the GPE version moto g OTA update kk 4.4.4, using mototool (no problems for months), one day I was charging my Motog, this is reset and stayed at motorola logo.
I tried to repair it with mototool but the result did not work, then I try to do it manually with fastboot since the following result:
Code:
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.259s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 6.557s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.569s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 5.042s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.059s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.011s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.023s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (70 KB)...
OKAY [ 5.050s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.087s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.880s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 5.364s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.875s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.0
target reported max download size of 536870912 bytes
sending 'system' (255843 KB)...
OKAY [ 13.505s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 22.446s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.1
target reported max download size of 536870912 bytes
sending 'system' (245954 KB)...
OKAY [ 13.127s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.419s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.2
target reported max download size of 536870912 bytes
sending 'system' (235703 KB)...
OKAY [ 12.817s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 24.524s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.038s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.039s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot reboot
the room used was a GPE 4.4.4, then try with a stock version, and it did not work.
the result is always this:
Code:
C:\Users\LilDoggy\Desktop\gpt_new>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.259s
after dealing with the CM11, but when trying to install CWM recovery, I have the following error:
Code:
C:\Users\LilDoggy\Desktop\CWM>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 5.364s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.875s
I have tried everything I found on the internet about this but nothing.
any suggestions, please help.
and sorry for my poor English !!

LilDoggy said:
hello guys from XDA, my problem is this, I have a moto motorola g (2013) I install the GPE version moto g OTA update kk 4.4.4, using mototool (no problems for months), one day I was charging my Motog, this is reset and stayed at motorola logo.
I tried to repair it with mototool but the result did not work, then I try to do it manually with fastboot since the following result:
Click to expand...
Click to collapse
Questions goes HERE

try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.

trying
aayush_neov said:
try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.
Click to expand...
Click to collapse
ok, I'll try, although I tried other stock and GPE, even that hope dies at last, I will try these links

sorry for this start a new topic
Ja_som said:
Questions goes HERE
Click to expand...
Click to collapse
sorry for this start a new topic as well, only with many buttons and forums, I did not know where to express my question. Thank you

I forget to mention that my Motog is xt1032 16 gbs
aayush_neov said:
try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.
Click to expand...
Click to collapse
I forget to mention that my Motog is xt1032 16 gbs, I do not think this room to work on my Motog, although some commands come I have never used the first line.
thank you!!

LilDoggy said:
I forget to mention that my Motog is xt1032 16 gbs, I do not think this room to work on my Motog, although some commands come I have never used the first line.
thank you!!
Click to expand...
Click to collapse
Did you unlock the bootloader?

Yes of course
skyguy126 said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
Yes of course, I had already installed the rom stock version to rom GPE. My version of bootloader is 41.13

I have already written, download your phone specific firmware. from elsewhere on Motog G forums
You dont have to do anything just follow instructions properly and copy paste the code.
You took risk of installing GPE on your phone and afraid of these simple instructions !!

partition gpt.bin
aayush_neov said:
I have already written, download your phone specific firmware. from elsewhere on Motog G forums
You dont have to do anything just follow instructions properly and copy paste the code.
You took risk of installing GPE on your phone and afraid of these simple instructions !!
Click to expand...
Click to collapse
I have already tried but the result is always the same as they drew the "fastboot flash partition gpt.bin" command,
the result is always:
sending 'partition' (32 KB) ...
OKAY [9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. Total time: 15.259s.
KK this with 4.4.4 versions with versions older than 4.4.4 (eg 4.4.3) sends a partition error.
from what I read it is a common problem and is solved by downloading a new gpt.bin file but does not work in my case, I begin to think that the problem is my Motog.

LilDoggy said:
I have already tried but the result is always the same as they drew the "fastboot flash partition gpt.bin" command,
the result is always:
sending 'partition' (32 KB) ...
OKAY [9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. Total time: 15.259s.
KK this with 4.4.4 versions with versions older than 4.4.4 (eg 4.4.3) sends a partition error.
from what I read it is a common problem and is solved by downloading a new gpt.bin file but does not work in my case, I begin to think that the problem is my Motog.
Click to expand...
Click to collapse
Then you should search extensively on XDA, other members might be able to help you.

Try using mfastboot, available in this zip:
https://www.androidfilehost.com/?fid=23578570567719065​

Preflash validation failed trying to flash stock 4.4.4

I have a bootloader unlocked XT1032 MOTO G on UK EE network. I have been trying to flash stock 4.4.4 (so that I can upgrade to OTA lollipop) but am getting a 'Preflash validation failed error'.
I've tried various things to get it to flash the images but nothing has worked.
Can anyone suggest how I might get this work?
Code:
C:\motog>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.660s]
finished. total time: 1.660s
C:\motog>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.646s]
finished. total time: 1.647s
C:\motog>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s

Just skip flashing the gpt.bin and motoboot.img but flash the rest. The phone should still work.

audit13 said:
Just skip flashing the gpt.bin and motoboot.img but flash the rest. The phone should still work.
Click to expand...
Click to collapse
Thanks for the suggestion, however there's others that fail too:
boot.img won't flash
Recovery does flash but I get the broken android with 'No command' message when trying to boot to recovery
System images won't flash
Code:
C:\motog>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.840s
C:\motog>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.966s]
finished. total time: 1.645s
C:\motog>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259277 KB)...
OKAY [ 8.643s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.082s
It will still boot normally after that. Any ideas?

Crazy question but are you sure you are flashing the correct rom for your phone? Was it on gpe before?

audit13 said:
Crazy question but are you sure you are flashing the correct rom for your phone? Was it on gpe before?
Click to expand...
Click to collapse
I'm pretty sure I am. I did try and convert to GPE using the AIO tool (when trying to resolve the issues) but I've seen nothing to suggest this has actually worked.
The phone has previously been rooted, but isn't currently.
System version is showing as:
210.12.40.falcon_umts.EESL.en.GB
Build number:
KXB21.14-L1.40
Kernel version:
3.4.42-gb89c9dd
[email protected] #1
Fri Jun 20 07:09:11 CDT 2014
Thanks for the help, it's very much appreciated!

@audit13
Update for lollipop in moto G Don´t work, ota Says "Updated"
HELP..
Same problem here preflash validation failed for Logo, GPT and Motoboot
(Downgrade from Lollipop 5.1 (XD1039 RETBR) To Kitkat 4.4.4
BOOOTLOADER is Unlocked.

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.

Please help!! HARD-BRICKED MY MOTO G XT1033 on CM14.1.

I flashed the cm14.1 and gapps, worked fine... then i flashed the Google assistant zip on my moto g xt1033. After that, it would not boot up to anything.. I tried getting it into recovery but simply no response... when i press the power button for longer, it just shows the white page and the unlock bootloader details... then turns off back again.... then i try to get it into recovery, same situation... Whattodo?
Before this, to install the animated nav bar, i got the SYSTEMUI pk, modified its rw permissions as given ( http://forum.xda-developers.com/moto-g/general/cm-14-1-pixel-nav-animation-button-moto-t3509255 ) here and followed the same thing,, the navbar showed up with no problems and i used it with no problems at all.....
Please suggest a solution....
(awkwardly enough, i am experiencing it a little warm even after i'ts been close to 30-40 mins after is shut itself off)

can u access Bootloader menu?

jbanti said:
can u access Bootloader menu?
Click to expand...
Click to collapse
Yes i can access bootloader menu, sorry i took so late to reply because i was on a short trip lol..
SO, i just started it back by connecting it to PC via USb and it shows battery low(charging).
The bootloader is 41.1A(*)

Charge it for 4 hours and flash stock ROM using mfastboot from your PC.
Or flash TWRP from your PC, wipe all partitions, reboot and flash again CM+gapps.

In addition to what others have suggested, you can follow the instructions on the link posted below. Basically, you would unzip the file on your computer, boot into bootloader on your phone and run the 1-step bat file. After a few minutes, you will automatically be on 4.4.4. It is easy to re-root and flash a recovery (I used Philz, which offers you the ability to root in its reboot menu). Lastly, I updated the twrp to the latest and flashed a new ROM.
https://forum.xda-developers.com/showthread.php?t=2969729
Sent from my Moto G using Tapatalk

taadow1030 said:
In addition to what others have suggested, you can follow the instructions on the link posted below. Basically, you would unzip the file on your computer, boot into bootloader on your phone and run the 1-step bat file. After a few minutes, you will automatically be on 4.4.4. It is easy to re-root and flash a recovery (I used Philz, which offers you the ability to root in its reboot menu). Lastly, I updated the twrp to the latest and flashed a new ROM.
https://forum.xda-developers.com/showthread.php?t=2969729
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
OK just to give you some information:
So this is what happening to me:
I flashed wrong files on my moto g. I think the files i flashed on my moto g were of Moto G3 or something. So my phone was stuck in bootloader rebooting.
I gave it to a shop and he got it back to kitkat with a flickering screen. Then i got the OTA and i was updating it to lollipop via OTA. It then went off., i dont know what happened but it would not even turn on by pressing power button. Then i connected it to a charger and notification light was blinking. Eventually, i got here and tried the procedure. So my mobile was recognised as qhsusb_bulk and then i followed the procedure further and then it was also recognised as qualcomm 9008 etc.
I flashed the blankflash and my bootloader screen showed up with a bootloader of 41.1A(*). Device is locked. Status code:0.
so when it comes in fastboot it shows:
Fastboot reason:Failed to initialize partition table
USB connected.
Now i tried to flash stock rom
mfastboot flash boot boot.img
fastboot flash reocovery 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
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.395s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.414s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash reocovery recovery.i
mg
target max-sparse-size: 256MB
sending 'reocovery' (10240 KB)...
OKAY [ 0.359s]
writing 'reocovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.384s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash system system.img_sp
arsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.497s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.500s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash system system.img_sp
arsechunk.1
target max-sparse-size: 256MB
sending 'system' (256782 KB)...
OKAY [ 8.439s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.459s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash system system.img_sp
arsechunk.2
target max-sparse-size: 256MB
sending 'system' (260098 KB)...
OKAY [ 8.633s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.648s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash system system.img_sp
arsechunk.3
target max-sparse-size: 256MB
sending 'system' (160376 KB)...
OKAY [ 5.360s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 5.395s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.653s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.666s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.016s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.024s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.067s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.105s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.058s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.011s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>mfastboot reboot
rebooting...
finished. total time: 0.003s
E:\MOTO G ROOT\MOTO G LOLLIPOP 5.0.2 NOV 15>
WHAT DO I DO NOW? PLEASE HELP.
(I KNOW I MADE A SPELLING MISTAKE IN FLASHING RECOVERY, BUT ANYWAYS WHEN I DO IT RIGHT, THE PHONE WOULD NOT WORK, ONLY BOOTS IN BOOTLOAER)

moralesnery said:
Charge it for 4 hours and flash stock ROM using mfastboot from your PC.
Or flash TWRP from your PC, wipe all partitions, reboot and flash again CM+gapps.
Click to expand...
Click to collapse
Following the brick, i gave my phone to repair in a shop. I got it back on kitkat. So i eventually got the OTA. then i updated to the OTA and my phone went off half-way. Now it just reboots to the bootloader and has notice :
Fastboot reason: Failed to initialize partition table

Believe it or not, when i attempted to use mfastboot commands, mine didn't work either. I'm not sure what went wrong, as all of the commands succeeded. However, when I flashed the bat file I described above, my phone was back in action less than 5 minutes later. I don't recommend using the OTA to update from KitKat though. It's far safer and better to install Philz , obtain root, flash twrp and then flash an updated ROM of your choice.
Sent from my iPad using Tapatalk

taadow1030 said:
Believe it or not, when i attempted to use mfastboot commands, mine didn't work either. I'm not sure what went wrong, as all of the commands succeeded. However, when I flashed the bat file I described above, my phone was back in action less than 5 minutes later. I don't recommend using the OTA to update from KitKat though. It's far safer and better to install Philz , obtain root, flash twrp and then flash an updated ROM of your choice.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
How to install philz now? becuase my device is showing Bootloader is locked.

thatRAHULfellow said:
How to install philz now? becuase my device is showing Bootloader is locked.
Click to expand...
Click to collapse
I'm not sure. My bootloader is unlocked, but I used fastboot (threads in Moto G General which includes one's by Lost101 has the specific instructions) to load Philz. Once flashed, boot into recovery. Then when you boot back into system, the recovery will ask you if you want to root. Select yes and you are good to go. Lastly, flashify app in the Play Store can be used to quickly flash twrp. I guess another way to root would be to flash superuser (also in lost101's threads in the OP section) via recovery as well. There are easier and quicker steps to do what I outlined, but the main advice is to use the bat file to quickly restore your phone to GPE kitkat and afterwards avoid updating through Motorola.
Sent from my Pixel using Tapatalk

Im getting Error 7 when i try flash, how to solve?

moto g xt1033 dual sim bootloader unlocked status code 3 no recovery ı will tried retail ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml ı cant ınstall .please help me ?

C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.021s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.263s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 5.091s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.915s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>paus
e
Devam etmek için bir tuşa basın . . .
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 4.992s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.249s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 5.086s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.901s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 5.004s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.013s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.402s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.791s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.395s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.799s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 14.834s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 24.041s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 23.254s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 32.877s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260404 KB)...
OKAY [ 17.088s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 25.956s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166184 KB)...
OKAY [ 11.589s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 20.500s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 6.962s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.988s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.991s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.991s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 6.325s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 13.900s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.995s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>mfas
tboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
C:\Users\sezai\Downloads\XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml>paus
e
Devam etmek için bir tuşa basın . . .
ı cant ınstall