Device: ACER ICONIA ONE 7 (B1-730HD)
did:
1. Fasboot erase cache
2. Fastboot oem erase cache
went well
then I made C: \ adb> fastboot flash system system.img.gz
and gives the error:
Reported target max download size of 613534378 bytes
Invelid sparse file format header at magi
Anyone know how to fix this error or how to flash the image of otherwise system? The tablet is stuck in boot acer walked because the change files in the system folder. Thanks!
Related
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!
As the title said, i'm having some errors while i try to flash something in fastboot, i'm folowing this steps:
First i open CMD (with administrator rights) or Terminal (root mode) and Type this:
Code:
adb devices
adb reboot-bootloader
My device reboot into bootloader, then i use:
Code:
Fastboot devices
Fastboot flash [partition] [path to file]
In this case: Fastboot flash recovery recovery.img
And here is where the problems begins
Code:
Fastboot flash recovery (path to the recovery.img file)
Sending 'recovery' (42834 KB) Failed (remote: 'not support "-u" option')
Fastboot: error: command failed
I do a little research about "-u" and got something about erasing a overwriting stuff so...
Code:
Fastboot erase recovery
(Everything is ok)
Fastboot flash recovery (path to the recovery file)
Sending 'recovery' (42834 KB) OKAY
Writing 'recovery' FAILED (remote: 'write partition:recovery')
Fastboot: error: Command Failed
I can't even do a Fastboot boot because of the '-U' option error...
I've tried with RKtools (because of my rk3368h chipset) and there i can flash everything succesfuly but when i try enter in recovery mode my device get stuck in the initial boot image (not the CR boot image)
So, i don't know if i'm using a wrong recovery.img or if my device is the problem. I hope someone can help me :laugh:
P.D: My device is a generic (unpopular) Android, so the only useful info that can i bring you is:
Android version is 8.1 (November 2018 security patch)
Device uses a rk3368h chipset
Bootloader is Unlocked
Obviously isn't rooted (that's why i'm trying to flash a CR)
Similar device: Teclast P10 (probably the m3f5)
And i'm trying to flash a ported TWRP (ported by ME )
That's all, thank you for reading my post and trying to help me.
I've just unlocked the phone, via minimal ADB
tried fastboot getvar current-slot and got the output that my slot was a
then I've tried flashing TWRP at a utilizing
fastboot flash recovery twrp.img
then got the following output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 803868672 bytes
sending 'recovery' (39780 KB)...
OKAY [ 1.663s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 1.695s
so, I've tried fastboot flash boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 803868672 bytes
sending 'boot_a' (35452 KB)...
OKAY [ 1.063s]
writing 'boot_a'...
OKAY [ 0.183s]
finished. total time: 1.254s
then I've manually pressed the power button + volume up and successfully entered TWRP
there, I've gone to advanced wipe and wiped
Dalvik / ART Cache, system, Data and Internal Storage
I didn't know Internal Storage would give me problems... After that, I couldn't access my internal storage from the PC to copy the .zip of the custom rom.
Tried going to mount into TWRP to mount different partitions, no succes.
Then I thought that maybe if I restarted the phone it would be ok. So I've restarted and TWRP told me "no system installed, do you wish to continue?" I said yes.
Now, I'm stuck at fastboot and can't boot into twrp anymore...
I've tried repeating the same commands above and got the same outputs.
fastboot flash boot twrp.img got me the "OKAY" messages. But now, even if I hold the power + vol up button, I won't get to recovery.
I've tried
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.291s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.298s
because my frient told me to do so, but this command does not exist.
How can I proceed?
Try using mi flash tool
I was also stuck in fastboot mode I then tried installing twrp again with no success.
So I then went and flashed stock rom again into my phone using mi flash tool.
(Having a new account, I can't post link to these files. So download the files from official mi website, it is available there)
Steps to flash
1- Place the Flash File on Desktop.
2- open flash tool application.
3- Assign the Folder path.
4-Go to slot a using adb
5- Click on refresh & then tap Flash button
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
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