Can't flash system images in fastboot - FAILED (remote: 'sparse flash write failure') - Android Q&A, Help & Troubleshooting

Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help

Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.

shaon121$ said:
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
Click to expand...
Click to collapse
It still doesn't work as administrator and with the image in the C drive root.

Change your img file and try again..or download again... What is your phone model?

shaon121$ said:
Change your img file and try again..or download again... What is your phone model?
Click to expand...
Click to collapse
I have already tried different images, the phone is a Huawei P Smart FIG-LX1.

useless double posts
Can't flash system.img in TWRP - E:Cannot flash images to file systems
I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition. So when i try to flash the image i have two system partitions: Ona named "System" and one named "System Image". If...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com

slx23 said:
Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Click to expand...
Click to collapse
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com

Related

Nexus 9 can't flash system or vendor/userdata

hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
hsl43 said:
hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
Click to expand...
Click to collapse
Google updated the Android SDK (fastboot) in November of last year to enable flashing the extremely large Lollipop system.img files.
Update your Android SDK to the latest and you should be good to go.
FWIW: flash_all does not work.
RESOLVED. for the benefit of anybody else that may run into this problem...
after much Google sleuthing and gnashing of teeth, it turns out the solution was... to simply switch which USB port on my laptop the cable was plugged into. for the life of me, i don't know why, but i'll take it.
thanks @cam30era for your reply! your recommendation may have been a part of the solution, but as a developer, i keep my SDK reasonably up-to-date, so that particular issue didn't come into play in this instance. nonetheless, thanks very much again for taking the time to provide that info!

[Question] Problem with Recovery

I have two problems:
1. I tried to flash it with the SPFlashTool and with the scatter & recovery files. But the problem is that it loads the old stock recovery. While I got the green check that download is ok.
2. I tried to do this with ADB, but it seems like that this does not work either, I'm getting the error:
C:\Users\Laurens\Downloads\>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9214 KB)...
OKAY [ 0.315s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.332s
Does anyone have a idea how to solve this problem. I also tried the oem command to no avail.
Solved!
Used the SPFlashTool tool with an original OS & scatter file, and pointed the recovery to my own recovery file, and used the option 'format all + download'

y7 prime faild to flash twrp

hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Try this
cappone said:
hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Click to expand...
Click to collapse
Hi there,
was wondering did you put the recovery file into the installation folder of ADB
yes, thats not the the problem, i manage to root my phone but cant to write TWRP, i get the same msg tried many toolkits and results is the same...
Since Oreo: Partition names have changed and "recovery" changed to "recovery_ramdisk".
Try:
fastboot flash recovery_ramdisk twrp.img

partition table broken

Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
badkey212 said:
Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')​fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
​fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery​FAILED (remote: '')​fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
Click to expand...
Click to collapse
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
sd_shadow said:
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
That helped, thank you!

Can't flash system.img in TWRP - E:Cannot flash images to file systems

I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition.
So when i try to flash the image i have two system partitions:
Ona named "System" and one named "System Image".
If i try flashing it to the "System" partition i get this error:
Code:
[IMAGE FLASH STARTED]
Image to flash: '/external_sd/system.img'
Calculating restore details...
E:Cannot flash images to file systems
If this can help i have wiped the system partition containing the original ROM.
useless double posts
Can't flash system images in fastboot - FAILED (remote: 'sparse flash write failure')
Hi, i am trying to install a system.img to the system partition using fastboot using fastboot flash system C:\Users\user\Desktop\system.img but when i run the command i get this error: Sending sparse 'system' 1/7 (460796 KB) OKAY [...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com

Categories

Resources