Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
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: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?
Related
I'm trying to flash a recovery image to a Razr Maxx HD, but I'm not entirely sure that I'm doing it correctly.
Code:
$ sudo fastboot flash recovery ~/recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7340 KB)...
OKAY [ 0.589s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.734s
Afterwards, my phone says “invalid image size for partition recovery.” The image I'm using is at goo .im /devs /Hashcode /vanquish, and I've tried all three versions. Am I on the right track at all or no?
Edit: Never mind. Gotta unlock the phone first. Problem solved.
I also saw that error when it was the wrong carrier recovery image
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!
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
Hello,
I stuck in "fastboot flash mode", when i unlock my bootloader, I want to flash stock rom, becouse old was broken, but when I try to flash rom I gets message:
<bootloader> Filed to erase partition
Help!
//sorry for my bad english ;/
When I want to flash new recoevry (stock or cwm/twrp) i gets message:
C:\Users\x\Downloads\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (7878 KB)...
OKAY [ 5.226s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.249s
Try flasing fastboot partition gpt.bin
404
Boss442 said:
Try flasing fastboot partition gpt.bin
Click to expand...
Click to collapse
When i try flash gpt.bin:
C:\adt-bundle-windows-x86-20140702\sdk\mfastboot-v2>mfastboot flash partition gp
t.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.405s
Download a diferent gpt, and try with normal fastboot
When I try flash orther gpt.bin:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash partition g
pt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 4.991s]
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.435s
or
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash partition g
pt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKEY [ 5.039s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. total time 5.554s
I try with 4-5 different gpt.bin but is the same error
maggig said:
when i try flash orther gpt.bin:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash partition g
pt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 kb)...
Okay [ 4.991s]
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.435s
or
d:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash partition g
pt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 kb)...
Okey [ 5.039s]
writing 'partition'...
(bootloader) preflash validation failed
failed (remote failure)
finished. Total time 5.554s
i try with 4-5 different gpt.bin but is the same error
Click to expand...
Click to collapse
me also same problem
I flashed many time moto e but getting first time this problem any one solved this so share that it is firmware's problem or some other
brother , did you get any kind of solution for that because i have same problem too. my email [email protected] give me reply if you have any kind of solution thanks in advance
I am facing the same problem. .if i try to flash anything via mfastboot it gives an error of failed to erase partition..please help
Got mine working after similar problem for days...cm 14.1 installed
guys the only solution i worked out for this problem is..
1. unlock bootloader (not sure if it is a must)
2. using fastboot boot into twrp version 3.1.x.x or later using comamd
mfastboot boot twrpimagename.img
3.flash a twrp img file to the recovery from there i can confirm versions 3.1.1.0 and 3.1.0.0...
nb. you can install it to either boot partition or recovery either will do
4. use ur newley istalled recovery to install a twrp compatible rom, either stock or custom...
there u go
OK I HAVE A MOTO G3 , SKU=XT1541 , VER=P2B , BUILD MP.124.107.55 , SYS VERS=24.61.55OSPREY
It is an unlocked euro version with 1gb ram , i.e not locked to any carrier or ever has been.
I was able to unlock the bootloader , I then followed very carefully the instructions on this site to get the image , usb drivers and everthing required.
However once ono entering the commands at the dos window to start flashing a new rom it comes back with an error , I think I have the incorrect image or there is not one on this site.
I am a complete nuubie can anyone help me please.
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
some progress
robin red said:
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
Click to expand...
Click to collapse
ok I managed to get to the part when I load the sparse files 0-5 , it send them all but reports failure on them all every other command on the list executes correctly.
After this it locked for a while a rebooted in version 6 marshmellow.!!!!! well I guess I am learning.
Anyone any ideas , guess I am lucky I did not brick the thing.
here is what I am getting after entering the third command
C:\Users\Robin L\Desktop\roby>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.470s