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] AIO wireless moto G, is it bricked?

Hi! i've been a long time lurker of the site for a couple of years now, I've happily been able to solve almost all of my problems just by searching the forums. but know I have no idea what to do, so i made an account and see if anyone has any insight on this
Here's the rundown:
recently bought a used moto g and started playing around with it and when i tried to upgrade the firmware manually. i kinda bricked it.
right now it's stuck on the bootloader screen (the one with AP fastboot flash mode (S))
my device is locked, from what i understand this particular model of moto g, the AIO wireless one, can't be bootloader unlocked.
i tried flashing US_retail_XT1032_KXB21.14-L1.32_CFC using the guide on [GUIDE] Moto G - Restore stock firmware
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
those commands worked correctly, but the next one,
mfastboot flash boot boot.img gives me the following error
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.354s]
writing 'boot'...
(bootloader) Preflash validation
FAILED (remote failure)
finished. total time: 0.850s
On the phone it says "hab check failed for boot"
after about an hour of research i was able to figure out which firmware was the original one, using the getvar all command, and it gives me this one
motorola/falcon_aio/falcon_umts:4.
4.2/KXB20.9-1.10-1.9/12:user/bldac
fg,release-keys
: Blur_Version.173.44.9.falcon_umts
: .AIO.en.US
now i was able to get that firmware after a while, and i tried to reflash it to the phone, but now i get these errors
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.071s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.458s
on the phone it says "version downgraded for primary_gpt"
on the next command i get this
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.147s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.493s
and on the phone it says "version downgraded for tz"
the logo flashes fine , but boot gives me another error
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.401s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.916s
and the phone says "version downgraded for boot"
now ive tried pretty much all the 4.4.2 retail US and 4.4.3 retail US firmwares and i get the same errors, or a combination of them
i have no idea what to do now, and i cant seem to find a 4..4.3 firmware for AIO wireless, and there does not seem to be one
does anybody has some information to signal me in the right direction? i'm afraid i just bricked it, and i barely even used it lol

[Q] XT1033 from US retail to Asia

Guys,
A friend bought a used Moto G Dual Sim xt1033 and it was rooted with kitkat 4.4.4 US Retail version 210.12.61.facon umts.retail.en.US
We need to lock the bootloader and go back to stock Asia Dual Sim Retail 4.4.4.
Current Baseband version is:
MSM8626BP 1032.390.81.01B, DFLT FSG
Build Number:
KXB21.14-L1.61
System Version:
210.12.61.facon umts.retail.en.US
Kernel version:
3.4.42-gc146877
[email protected] #1
Sat Aug 30 03:48:28 CDT 2014
Click to expand...
Click to collapse
I need to know if Flashing the Stock 4.4.4 ASIA Retail version & Locking the bootloader is possible on this without bricking the phone. I will follow the following guide:
http://forum.xda-developers.com/showthread.php?t=2700502
Thanks.

Yes,It is possible :good:

srisurya95 said:
Yes,It is possible :good:
Click to expand...
Click to collapse
Hi,
I tried the the following but it gave error. Now the baseband has been changed to the ASIA but it failed to flash the rom.
mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 2.648s]
finished. total time: 2.653s
mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.384s
mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
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.319s]
finished. total time: 1.435s
mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.146s]
finished. total time: 0.232s
mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.425s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.935s
mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.434s]
writing 'recovery'...
OKAY [ 1.026s]
finished. total time: 1.467s
mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (260949 KB)...
OKAY [ 10.671s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.173s
mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (248721 KB)...
OKAY [ 9.106s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.272s
mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (254187 KB)...
OKAY [ 10.472s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.598s
mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.3': No error
mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.775s]
writing 'modem'...
OKAY [ 2.388s]
finished. total time: 4.170s
mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.115s
mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.026s]
finished. total time: 0.027s
mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 5.305s]
finished. total time: 5.394s
mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.087s]
finished. total time: 0.090s
mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.747s]
finished. total time: 0.752s
mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.080s]
finished. total time: 0.084s
pause
Press any key to continue . . .
mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse

abhibhp said:
Hi,
I tried the the following but it gave error. Now the baseband has been changed to the ASIA but it failed to flash the rom.
Click to expand...
Click to collapse
It seems like u r flashing 4.4.4 firmware
do one thing ..flash 5.0.2 and don't use the command fastboot oem lock begin and fastboot oem lock
let the phone boot first then we can lock the boot loader
so exclude the first and last command and flash the firmware images

srisurya95 said:
It seems like u r flashing 4.4.4 firmware
do one thing ..flash 5.0.2 and don't use the command fastboot oem lock begin and fastboot oem lock
let the phone boot first then we can lock the boot loader
so exclude the first and last command and flash the firmware images
Click to expand...
Click to collapse
Thanks for the suggestion, will try that.
Using the 5.0.2 rom listed here.
http://forum.xda-developers.com/showthread.php?t=2700502
https://drive.google.com/file/d/0B5uo5LCdnblrcHJMblF3MlhaUjQ/edit
Also I got the following error earlier during partition:
mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.384s
Click to expand...
Click to collapse

abhibhp said:
Thanks for the suggestion, will try that.
Using the 5.0.2 rom listed here.
http://forum.xda-developers.com/showthread.php?t=2700502
https://drive.google.com/file/d/0B5uo5LCdnblrcHJMblF3MlhaUjQ/edit
Also I got the following error earlier during partition:
Click to expand...
Click to collapse
Ignore the errors
If the device doesn't boot,skip gpt and motoboot.img

srisurya95 said:
Ignore the errors
If the device doesn't boot,skip gpt and motoboot.img
Click to expand...
Click to collapse
Thanks a lot man. Bug ups!
Everything worked perfectly.
Just need to lock the bootloader now.
Do i just use the
mfastboot.exe oem lock
Click to expand...
Click to collapse

abhibhp said:
Thanks a lot man. Bug ups!
Everything worked perfectly.
Just need to lock the bootloader now.
Do i just use the
Click to expand...
Click to collapse
glad to know
no u have to type
fastboot oem lock begin
____flash stock firmware again____
fastboot oem lock

srisurya95 said:
glad to know
no u have to type
fastboot oem lock begin
____flash stock firmware again____
fastboot oem lock
Click to expand...
Click to collapse
SST failure while OEM Lock after stock firmware flash.

abhibhp said:
SST failure while OEM Lock after stock firmware flash.
Click to expand...
Click to collapse
I assumed that would happen
happened to everyone who tried it
I don;t know whatsa the problem exactly but can I ask u why u want to lock?

Please help!! phone doesn't boot up

hey guys,
I used a youtube video and I did a thing with 5.x to 4.4.4 gpe but after my phone just doesn't boot up.
Do I have a bricked phone? It's Stuck at the bootloader menu with the error ''Boot up failed'' please help!!!
(sorry for bad english)

Be careful with downgrading. What model Moto G do you have?

lost101 said:
Be careful with downgrading. What model Moto G do you have?
Click to expand...
Click to collapse
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this

poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
I already tried to flash TWRP, CWM and Philz but it didn't work it still said Boot up failed

poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
EDIT: Since you just updated the post to state you have a 4G Moto G - do not flash non-4G ROMs or firmware images - that includes GPE!

lost101 said:
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
Click to expand...
Click to collapse
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)

poolta321 said:
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)
Click to expand...
Click to collapse
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development

lost101 said:
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development
Click to expand...
Click to collapse
yes I know but when I flash TWRP and I go to recovery it says boot up failed

poolta321 said:
yes I know but when I flash TWRP and I go to recovery it says boot up failed
Click to expand...
Click to collapse
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Tried the 4G tutorial before... it didn't work

poolta321 said:
Tried the 4G tutorial before... it didn't work
Click to expand...
Click to collapse
but im going to try this again.
what is the difference with retial europe and orange europe?

poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
I'm also being helped here http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617

poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.

lost101 said:
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.
Click to expand...
Click to collapse
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)

poolta321 said:
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:

poolta321 said:
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:
Click to expand...
Click to collapse
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.

lost101 said:
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.
Click to expand...
Click to collapse
yes but he said that the bootloader was messed up and that there was no way to fix it

poolta321 said:
yes but he said that the bootloader was messed up and that there was no way to fix it
Click to expand...
Click to collapse
I read what he said, but I do not agree. I suggest you do as I describe above.

lost101 said:
I read what he said, but I do not agree. I suggest you do as I describe above.
Click to expand...
Click to collapse
Okay so what do I need to do?
(I'm away for a while)

poolta321 said:
Okay so what do I need to do?
(I'm away for a while)
Click to expand...
Click to collapse
Okay I'm back. and I did what you said but it didn't work. when I turn on my phone it says: Fastboot Reason: Fall-trough from normal boot mode.
Here is the cmd log:
G:\Program Files\SDK\platform-tools>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
G:\Program Files\SDK\platform-tools>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.366s
G:\Program Files\SDK\platform-tools>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.140s]
finished. total time: 0.218s
G:\Program Files\SDK\platform-tools>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.841s
G:\Program Files\SDK\platform-tools>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.381s]
writing 'recovery'...
OKAY [ 0.964s]
finished. total time: 1.348s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.0
target max-sparse-size: 256MB
sending 'system' (260841 KB)...
OKAY [ 8.458s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.1
target max-sparse-size: 256MB
sending 'system' (236285 KB)...
OKAY [ 7.760s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.827s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.2
target max-sparse-size: 256MB
sending 'system' (257383 KB)...
OKAY [ 8.364s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.437s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.3
target max-sparse-size: 256MB
sending 'system' (33384 KB)...
OKAY [ 1.163s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.236s
G:\Program Files\SDK\platform-tools>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (59132 KB)...
OKAY [ 2.200s]
writing 'modem'...
OKAY [ 2.831s]
finished. total time: 5.037s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.088s]
finished. total time: 0.090s
G:\Program Files\SDK\platform-tools>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 5.061s]
finished. total time: 5.170s
G:\Program Files\SDK\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.105s
G:\Program Files\SDK\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.218s]
finished. total time: 0.219s
G:\Program Files\SDK\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.003s

Returning to Stock Fail

Phone:MOTO G Turbo Edition (Indian)
I had been using a custom rom for quite sometime but now i want to return stock rom
I downloaded the firmware.
Guide im using is https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
but when i flash gpt.bin it says
Code:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.366s
can anyone help?
this is my only working device.

https://android.stackexchange.com/q...-2015-due-to-preflash-validation-failed-error
Check this and see if it helps.