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
Related
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!
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!
HELLO PEOPLE, I need your help, I have a mate 10 RNE-L23, which had the [ROM] [MorfuZ V3.4] EMUI 8.0 Kangvip Mate 10 Lite of Catuva21,
https://forum.xda-developers.com/ma...her-development/rom-emui-8-0-kangvip-mate-10- lite-t3784834
*
which gives me the fpr, in the fastboot mode close the bootloader again, but forget to install the recovery stock, then gave me this error, Error mode: error 11 no recovery, error 2 failed to load,
Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
https://forum.xda-developers.com/huawei-p9lite/help/error-mode-error-11-recovery-error-2-t3740112
buy dc-phoenix but I can not find the stock on this page for the RNE-L23
search in many pages and I have 12 different roms but at the moment of installing in (RECOVERY MODE) it stagnates in 5%
DC-PHOENIX
Looking for a device in upgrade mode
COM6: DBAdapter Reserved Interface (COM6)
COM7: Android Adapter PCUI (COM7)
16/7/2018 12:40:29 Starting to write device in UPGRADE mode...
File to update: UPDATE.APP
Current version: RNE-AL00C00B001
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 22: SHA256RSA...OK
Writing file 2 of 22: CRC...OK
Writing file 3 of 22: CURVER...OK
Writing file 4 of 22: VERLIST...
Error downloading file 4 of 22
EditQuote Comment Flag Like 0
#3
1 day ago
TELOKLAVO
TELOKLAVO
Junior Member
Join Date: Jul 2018 Posts: 5
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: M4VDU18417000099
16/7/2018 12:55:45 Starting extracting partitions from file UPDATE.APP
Current version: RNE-AL00C00B001
Cannot create extract directory: C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\tmp\20180716_125545_UPDATE\
Extract files to directory: C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: SYSTEM OK
16/7/2018 13:02:37 Extracting partitions finished OK
16/7/2018 13:02:38 Starting to write device in FASTBOOT mode...
Device found: M4VDU18417000099
IMEI: 866224034319763
Build number: :MorfuZ-*ƒæ¢ 3.4
Product model: RNE-L23
Writing XLOADER partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Cannot activate backdoor
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Dell\Desktop\__DANIE__\RNE-L23\DC_Phoenix_v57\SYSTEM.img
SYSTEM partition UPDATE ...OK
Software written
16/7/2018 13:11:28 Writing device finished OK
Waiting for fastboot device...
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
COM6: DBAdapter Reserved Interface (COM6)
COM7: Android Adapter PCUI (COM7)
16/7/2018 13:25:17 Starting to write device in UPGRADE mode...
File to update: UPDATE.APP
Current version: RNE-AL00C00B001
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 22: SHA256RSA...OK
Writing file 2 of 22: CRC...OK
Writing file 3 of 22: CURVER...OK
Writing file 4 of 22: VERLIST...
Error downloading file 4 of 22
I already consult dc-unlocker forum but I have not had an answer, if anyone could help me I would appreciate it,
on this page no logo get the rom For this specific model (RNE_L23), this for the RNE-L21 RNE-L22, can I install some of these?
+ info
Which recovery its installed? Have you flashed a firmware N or O?
Paniaguajuanm said:
Which recovery its installed? Have you flashed a firmware N or O?
Click to expand...
Click to collapse
I had installed twrp oreo, then I installed more than 12 official ROMs between nougat and oreo with DC-PHOENIX and it does not manage to install the rom completely, it continues indicating the same model of Rom
Found Phone: RNE-L23
Model: Huawei phone in fastboot mode
IMEI: 86622403xxxxxxx
Serial NR. : M4VDU184xxxxxxxx
Firmware: MorfuZ-ðŸ'½ 3.4
I think that is why it is not a base firmware because the dc-unloker page is not available for this model RNE-L23
Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
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