Related
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!
Hi Mates!
Ive got a soft bricked moto g, it says bl is locked, i cant flash retail firmware (hab check fail error), ive got the unlock code, but if i try to unlock the bl with fastboot oem unlock, it says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
Any suggestions?
Here is my fastboot prompt:
d:\MotoG\442>fastboot.exe flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.147s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.565s]
finished. total time: 1.714s
d:\MotoG\442>fastboot.exe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.125s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.252s
d:\MotoG\442>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.429s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
d:\MotoG\442>fastboot.exe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.395s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.426s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (255768 KB)...
OKAY [ 8.714s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (244360 KB)...
OKAY [ 8.304s]
writing 'system'...
OKAY [ 10.235s]
finished. total time: 18.541s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (220989 KB)...
OKAY [ 7.533s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.965s
d:\MotoG\442>
d:\MotoG\442>fastboot.exe flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47476 KB)...
OKAY [ 1.648s]
writing 'modem'...
OKAY [ 1.479s]
finished. total time: 3.128s
d:\MotoG\442>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.104s]
writing 'fsg'...
OKAY [ 0.076s]
finished. total time: 0.181s
d:\MotoG\442>fastboot.exe reboot
rebooting...
finished. total time: 0.001s
Try using "mfastboot" it could maybe work... Just a thought.
Destr0y3r said:
Try using "mfastboot" it could maybe work... Just a thought.
Click to expand...
Click to collapse
I already tried it with no luck...if you look at getvar data you will see cid is 0xDEAD thats why i am worried.
Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried many firmware without luck, the problem is in the BL i see devices locked status 0, but the unlock command doesn't work.
You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the message i've got after fastboot oem unlock "unlockcode"
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
This is the story: the former owner tried to root the phone, as he said he unlocked the bootloader, then something went wrong. He tried to install CM, and he softbricked the phone. It has the IMEI but there is some problem with CID and UID as a look at the prompt from fastboot getvar all. Somehow the unlock commands doesnt work, and i ve got preflash vaildation faild errors, when i try to flash boot or recovery or system img. The phone wont boot if i turn it on it goes to bootloader.
Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.
Well I think you are the first person who has faced this problem...I think there is something wrong with the commands you are typing....
Sent from my Moto G using XDA Premium 4 mobile app
my theory
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Awesomeslayerg said:
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...
Wipe simply everything from your phone and then restore the stock firmware
Sent from my XT1032 using XDA Premium 4 mobile app
randras83 said:
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2623587
Found this you could try this.
I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.
check device manager on windows and see if you have unknow devices on your phone and change adb from there
tal.aloni said:
I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.
Click to expand...
Click to collapse
It has been quite a while since you posted this, but I have the same problem where I overwrote the cid partition and I am unsure how to get it back. Any chance you remember this trickery?
Thanks,
Nathan
I have the same problem. Any fix?
ISSue XT0133
randras83 said:
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.
Click to expand...
Click to collapse
same issue, i'm also facing bro any solutions?
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?
Can somebody help me?
After blankflash bootloader 411A* i can revive
my phone with any rom.
XT1032 moto g 2013.
Every time it gives error with:
Preflash validation failed or permission denied
I've try to blankflash again by forcing drivers
in win 10 to see it.
The device is seen (device manager)as qualcom 9008.
It doesn't do anything said waiting for device when i try to blankflash again.
So i am stuck in a crazy locked bootloader with
no partition on phone nothing.....
I've try to flash almost all available rom for it.
Same result,every time failed with permision denied
or partition downgraded for gpt
(blue letters warning)
or Preflash validation failed .....
Any idea how can i flash a moto or boot image of
any rom to revive it?
I am tired of trying so many.....
If i can make the phone be seen
by RSD lite i can try to flash thru it.
But is not recognize by any of
the RSD Lite versions....
I think i'm gonna bin it.
Thanks for any idea........
Oh,and the story behind....
Original:moto g 5.02 tesco firmware....
Unlocked bootloader.....
Flashed 4.4 GPE....OK
Updated OTA....bricked....
only seen in
PC as qulcomm.....
Next...bankflashed.....ok
Bootloader shows status locked
Phone booting in fastboot and that's it....
'Preflash validation' error is normally due to having a locked Bootloader and trying to flash an older firmware than previously installed, i.e 5.0.2 over 5.1. You may have corrupted the Bootloader by applying the OTA Update after flashing 4.4.4. You are breaking every rule in the book and seem intent on completely destroying your phone.
Flash the latest XT1032 Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
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
Use mfastboot to flash. However, ultimately, you may need to apply the unbrick method - http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
Thank you!
I have try all above....
It looks like the blankflash locked the
bootloader (previously was unlocked)
and is not responding to
unlock it....even with the proper unlock key....
(permission denied)
That why i need an idea how to
blankflash/rewrite bootloader again.
I will post later on some screenshots with getvarall.
Yes,i sort it out, if other people having same problem need to flash only gpt.bin.
And this one extracted ONLY from 5.1 brazilian rom.
Any other procedure will not restore bootloader
to initial state.
After that you can flash any other compatible rom...
Thanks to all especially to Chalkydri who point me
to the brazilian rom.
Google * unbrick moto g*. You will get a xda thread dated june 2016. Follow the steps worked for my hard bricked moto g might as well work for you.
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
mihaidenis said:
Yes,i sort it out, if other people having same problem need to flash only gpt.bin.
And this one extracted ONLY from 5.1 brazilian rom.
Any other procedure will not restore bootloader
to initial state.
After that you can flash any other compatible rom...
Thanks to all especially to Chalkydri who point me
to the brazilian rom.
Click to expand...
Click to collapse
which brazilian rom do you use?
7servin said:
which brazilian rom do you use?
Click to expand...
Click to collapse
Have a look in here I think is this one:
http://forum.xda-developers.com/devdb/project/dl/?id=14560
If is not working google for 5.1 brazilian rom for moto
g 2013.
I suppose you have XT1032.
Presently I don't own the Moto G.
Been stolen.....
Good luck.
mihaidenis said:
Have a look in here I think is this one:
http://forum.xda-developers.com/devdb/project/dl/?id=14560
If is not working google for 5.1 brazilian rom for moto
g 2013.
I suppose you have XT1032.
Presently I don't own the Moto G.
Been stolen.....
Good luck.
Click to expand...
Click to collapse
yes i have one xt1032 i google that and download but not working
i have de same error Preflash validation i tried with yours
mihaidenis said:
Can somebody help me?
After blankflash bootloader 411A* i can revive
my phone with any rom.
XT1032 moto g 2013.
Every time it gives error with:
Preflash validation failed or permission denied
I've try to blankflash again by forcing drivers
in win 10 to see it.
The device is seen (device manager)as qualcom 9008.
It doesn't do anything said waiting for device when i try to blankflash again.
So i am stuck in a crazy locked bootloader with
no partition on phone nothing.....
I've try to flash almost all available rom for it.
Same result,every time failed with permision denied
or partition downgraded for gpt
(blue letters warning)
or Preflash validation failed .....
Any idea how can i flash a moto or boot image of
any rom to revive it?
I am tired of trying so many.....
If i can make the phone be seen
by RSD lite i can try to flash thru it.
But is not recognize by any of
the RSD Lite versions....
I think i'm gonna bin it.
Thanks for any idea........
Oh,and the story behind....
Original:moto g 5.02 tesco firmware....
Unlocked bootloader.....
Flashed 4.4 GPE....OK
Updated OTA....bricked....
only seen in
PC as qulcomm.....
Next...bankflashed.....ok
Bootloader shows status locked
Phone booting in fastboot and that's it....
Click to expand...
Click to collapse
mihaidenis said:
Thank you!
I have try all above....
It looks like the blankflash locked the
bootloader (previously was unlocked)
and is not responding to
unlock it....even with the proper unlock key....
(permission denied)
That why i need an idea how to
blankflash/rewrite bootloader again.
I will post later on some screenshots with getvarall.
Click to expand...
Click to collapse
please reply if you got any suggestion
thank you
please help me to flash locked bootloader
mihaidenis said:
Yes,i sort it out, if other people having same problem need to flash only gpt.bin.
And this one extracted ONLY from 5.1 brazilian rom.
Any other procedure will not restore bootloader
to initial state.
After that you can flash any other compatible rom...
Thanks to all especially to Chalkydri who point me
to the brazilian rom.
Click to expand...
Click to collapse
The same issue i am facing here i am trying flash all version of gpt.bin file but no use it always shows bootloader unlock disabled and unknown partition name
please advise to rectifie it
Fortboy said:
please reply if you got any suggestion
thank you
Click to expand...
Click to collapse
Try some 5.1 brazilian rom.Google for it.
You must have XT1032 moto G for this to work.
And try flash whole rom.
Even if it gives you some errors you might be able to unlock bootloader to previous state....
Good luck!
Fortboy said:
please reply if you got any suggestion
thank you
Click to expand...
Click to collapse
Try some 5.1 brazilian rom.Google for it.
You must have XT1032 moto G for this to work.
And try flash whole rom.
Even if it gives you some errors you might be able to unlock bootloader to previous state....
Good luck!
Please put link here
mihaidenis said:
Yes,i sort it out, if other people having same problem need to flash only gpt.bin.
And this one extracted ONLY from 5.1 brazilian rom.
Any other procedure will not restore bootloader
to initial state.
After that you can flash any other compatible rom...
Thanks to all especially to Chalkydri who point me
to the brazilian rom.
Click to expand...
Click to collapse
hi i am facing the same issue here please let me know the which gpt.bin file was supported to you
Thank you in advance
Hi guys, I am Brazilian and user of xt1033, after an unfortunate downgrade, I caused a hard brick in my smart, the first time that happened I managed to recover without any problem by the post here of xda, but now I think I have the same problem the guy there, when I flash in 'flash5.1' gives some error and the process does not conclude, look:
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.300s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.122s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>pause
Pressione qualquer tecla para continuar. . .
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.033s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.307s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.147s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.065s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.385s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.385s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.431s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257535 KB)...
OKAY [ 8.674s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.689s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256925 KB)...
OKAY [ 8.623s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.676s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (256980 KB)...
OKAY [ 8.651s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 8.689s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (175936 KB)...
OKAY [ 5.933s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 5.986s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.694s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.726s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.053s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.084s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.115s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.047s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.053s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>mfastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Eduardo\Desktop\HARDBRICK MOTO G 2013>pause
Pressione qualquer tecla para continuar. . .
I tried several ways to install the stock but without success, and I also tried to unlock the boatloader and also failed, I tried to install another version of the boatloader and without success. I'm sorry for my bad english, I'm using google translator to talk to you. And sorry if I did something wrong, this is the first time I participate in a forum here.
This smart is my main device and I really need it, if you can help me, I thank you very much.
Hey guys, I've the same problem with the XT1032 model. My phone was bricked 4 days ago, and I tried to flash a 5.0.2 Retail US with a 41.1A Bootloader, after to flash this motoboot.img, I can't flash anything. All the times appears this same message:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition
My bootloader is corrupt :crying:
I don't know how to solve this problem, I've tried flashing with 9-10 ROM's for my model, and all times appears this message, I tried in 3 different PC's. Anybody did solve this problem?
Hello,
Someone succeed ? If yes how ?
Thanks
please reply urgently .if anyone got any suggestion. Please
mihaidenis said:
Thank you!
I have try all above....
It looks like the blankflash locked the
bootloader (previously was unlocked)
and is not responding to
unlock it....even with the proper unlock key....
(permission denied)
That why i need an idea how to
blankflash/rewrite bootloader again.
I will post later on some screenshots with getvarall.
Click to expand...
Click to collapse
Same here and what's intriguing is that now the BL version is 0.5 with unknown Baseband. Whereas before blankflashing it was 2.7 with a baseband. Tried everything like you but without a working baseband, I can flash ROMs but no cellular connectivity. SIM cards turn out disabled
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