Fastboot Commands Not Working Getting Fail Amazon Moto G4 Play Stock Firmware

Yous are using an out of engagement browser. It may non display this or other websites correctly.
You should upgrade or use an
alternative browser.

I use custom Rom in my game Moto G4 play, and at some point in fourth dimension I try to become back to the rom stock, but I always get this fault:

FAIL (Command write failed (argument invalid))

Preflash validation failed

Another error is also (Data tranfer failure <Too many links>)

I already tried Rsd lite and information technology also did non work, and also clear by adbfastboot

This may have happened because in Twrp I deleted the system, internal memory, it was kind of a layman, and I was too curious, only able to use custom rom.

Nougat coming to G4 play and I with this problem.

Can anybody help me, cheers very much? :chorando:

Concluding edited:
Jun 27, 2017

#two

I’m having this problem to get dorsum to Stock ROM, my prison cell phone is a Moto G4 play xt1603, I apply a custom ROM, have any tips, I already tried Rsd lite and nothing …

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot oem fb_mode_set
…
OKAY [-0.000s]
Finished. Total time: -0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash partition gpt.bin
Target reported max download size of 268435456 bytes
Sending ‘partition’ (32 KB) …
OKAY [0.078s]
Writing ‘partition’ …
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Freeboot flash bootloader bootloader.img
Target reported max download size of 268435456 bytes
Sending ‘bootloader’ (2546 KB) …
OKAY [0.219s]
Writing ‘bootloader’ …
(Bootloader) flashing sbl1 …
(Bootloader) flashing aboot …
(Bootloader) flashing tz …
(Bootloader) flashing hyp …
(Bootloader) flashing rpm …
OKAY [1.722s]
Finished. Total time: 2

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash logo logo.bin
Target reported max download size of 268435456 bytes
Sending ‘logo’ (751 KB) …
FAILED (data transfer failure (Too many links))
Finished. Total time: 0.187s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash boot boot.img
Sending ‘kicking’ (16384 KB) …
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader alert from
S)> fastboot flash recovery recovery.img
Sending ‘recovery’ (16484 KB) …
FAILED (command write failed (Invalid argument))
Finished. Full time: 0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sblocked)> fastboot wink dsp adspso.bin
Error: can not open ‘adspso.bin’

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash oem oem.img
Sending ‘oem’ (13464 KB) …
FAILED (command write failed (Invalid statement))
Finished. Total time: -0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system system.img_sparsechunk.0
Sending ‘system’ (262141 KB) …
FAILED (control write failed (Invalid argument))
Finished. Total time: 0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot wink system system.img_sparsechunk.ane
Sending ‘organisation’ (262142 KB) …
FAILED (command write failed (Invalid argument))
Finished. Total fourth dimension: -0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.2
Sending ‘system’ (262140 KB) …
FAILED (command write failed (Invalid statement))
Finished. Total fourth dimension: 0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader alarm from
Sb)> fastboot flash arrangement system.img_sparsechunk.3
Sending ‘organisation’ (259676 KB) …
FAILED (command write failed (Invalid statement))
Finished. Total fourth dimension: -0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system arrangement.img_sparsechunk.4
Sending ‘system’ (262140 KB) …
FAILED (control write failed (Invalid statement))
Finished. Total time: 0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system organization.img_sparsechunk.5
Sending ‘system’ (262141 KB) …
FAILED (command write failed (Invalid statement))
Finished. Total time: -0.000s

C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system arrangement.img_sparsechunk.6
Sending ‘organization’ (262142 KB) …
FAILED (command write failed (Invalid argument))
Finished.

: April 13, 2014

: 572

: 995

: 21

: Pilar

Try flashing from a shorter path and remove spaces, Windows (and even Linux) are kinda stupid on handling these types of path, mainly Windows.

I’m almost sure it’s handling it like: C:\Users\Vin\ius\Downloads\Roms\Rom3\ADB at every command not matter what you write.

Similar threads