Hello together,
right now i tried to flash my honor 9 via DC Phoenix, because it has a brick. In the process with flashing via DC Phoenix i got a message which says that the process failed. Now i have two questions.
1. Question: Which files exactly i need for DC Phoenix for flashing, because you can download three files. Do i need the update.zip or update_data_full_public or update_full_STF-L09_hw_eu or all three?
For the flashing i just use the UPDATE.APP from the unpacked update.zip file
2. Question: You can see my Log from DC Phoenix. I don't understand the error. What should i do now?
Thank you very much for an answer. I really despair for many days now and i don't know what i should do.
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 8BNDU17A23004272
21.01.2018 23:13:20 Starting extracting partitions from file UPDATE.APP
Current version: STFC999B000
Cannot create extract directory: C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\tmp\20180121_231320_UPDATE\
Extract files to directory: C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: VECTOR 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: SYSTEM OK
Extracting partition: ISP_FIRMWARE OK
Extracting partition: MODEM_FW OK
Extracting partition: HISEE_IMG OK
Extracting partition: HISEE_FS OK
21.01.2018 23:13:43 Extracting partitions finished OK
21.01.2018 23:13:43 Starting to write device in FASTBOOT mode...
Device found: 8BNDU17A23004272
IMEI: 864597030324735
Build number: :System 5.1.0.78(0GIU)
Product model: STF-L09
Writing XLOADER partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing VECTOR partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\VECTOR.img
VECTOR partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\DTS.img
DTS partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\SYSTEM.img
SYSTEM partition UPDATE ...FAILED
Writing ISP_FIRMWARE partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\ISP_FIRMWARE.img
ISP_FIRMWARE partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Writing HISEE_IMG partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\HISEE_IMG.img
HISEE_IMG partition UPDATE ...OK
Writing HISEE_FS partition with file C:\Users\Alexander\Desktop\Neuer Ordner (2)\DC_Phoenix_v50\HISEE_FS.img
HISEE_FS partition UPDATE ...OK
Software written
21.01.2018 23:15:57 Writing device finished - INCOMPLETE
Waiting for fastboot device...
Device found: 8BNDU17A23004272
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
COM4: Android Adapter PCUI (COM4)
COM5: DBAdapter Reserved Interface (COM5)
21.01.2018 23:16:58 Starting to write device in UPGRADE mode...
File to update: UPDATE.APP
Current version: STFC999B000
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 26: SHA256RSA...OK
Writing file 2 of 26: CRC...OK
Writing file 3 of 26: CURVER...OK
Writing file 4 of 26: VERLIST...OK
Writing file 5 of 26: PACKAGE_TYPE...
Error downloading file 5 of 26
Error writing software
21.01.2018 23:17:48 Writing device finished with ERROR
Cannot update device in upgrade mode
Don't you think the good and helpful folks at dc-unlocker.com are the best qualified to answer anything related to their software?
1. All of three I guess... Never used DC.
2. It seems it successfully flashed a recovery... Could you boot on stock recovery mode(vol+ and power)?
i have same problem with CMR-W19, cant writting SYSTEM.img
"Writing SYSTEM partition with file C:\Users\stevi\Desktop\DC_Phoenix_v57\SYSTEM.img
SYSTEM partition UPDATE ...FAILED"
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 all,
I am new of this forum but I read yet a lot of threads for multiples problems in the past.
Sorry for my english, I am french.
I create a thread because I try to help a little girl which has its Asus MeMO Pad 8 ME181CX bricked.
It can boot anymore.
SInce 2 days, I read a lot of resources on internet (google) and tried a lot of methods without success.
I tried the factory reset => Not works
I got the "UL-K011-WW-3_1_23_172.zip" file from ASUS => the file correspond to the "WW" tablet version
I tried adb commands (adb sideload) method => Not works
I tried fastboot flash => Not works
I tried flash a new recovery system (TWRP) => Not works, the tablet was not rooted so the bootloader prevents to flash the recovery mode.
My principal problem is that there is not the "system.img" file inside the official zip archive.
There is only "boot.img" and "fastboot.img".
I can flash them but it is not enough...I must flash the "system".
I have only the "system" folder so I searched a way to generate a "system.img" file from this folder.
Very not easy to do such a thing.
I booted on a Linux (Ubuntu) partition and I generated an ISO file from system folder, then with "dd" command I generate the "system.img".
All these things take a long time to do because of the size of datas to manipulate (between 500 MB and 1.5 GB).
Even with a "system.img" file, I cannot flash it on the tablet.
I tried first this :
C:\adttools>fastboot flash system system.img
target reported max download size of 569289386 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 525682688 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (544845 KB)...
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
OKAY [ 33.907s]
writing 'system' 1/3...
FAILED (remote: flash_cmds error!
)
finished. total time: 34.735s
So I tried after this :
C:\adttools>fastboot -S 512M flash system system.img
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 635275264 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 139831296 is not a multiple of the block size 4096
sending sparse 'system' 1/4 (500349 KB)...
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
OKAY [ 28.740s]
writing 'system' 1/4...
FAILED (remote: flash_cmds error!
)
finished. total time: 29.448s
I found a program "SparseConverter_1.0.1" to try to chunk the "system.img" but it does not work because "system.img" has a size which is not a multiple of the block 4096.
And now, I cannot find another solution.
The ideal situation would be to find an authentic "system.img" file but it seems that ASUS does not want to give it for "WW" version.
Is someone has a idea to succeed to have this damned "system.img" file ?
Thanks a lot for any help I could receive on this problem.
I cannot imagine to say to this child that her tablet must go to the garbage.
yoyomaster73 said:
Hello all,
I am new of this forum but I read yet a lot of threads for multiples problems in the past.
Sorry for my english, I am french.
I create a thread because I try to help a little girl which has its Asus MeMO Pad 8 ME181CX bricked.
It can boot anymore.
SInce 2 days, I read a lot of resources on internet (google) and tried a lot of methods without success.
I tried the factory reset => Not works
I got the "UL-K011-WW-3_1_23_172.zip" file from ASUS => the file correspond to the "WW" tablet version
I tried adb commands (adb sideload) method => Not works
I tried fastboot flash => Not works
I tried flash a new recovery system (TWRP) => Not works, the tablet was not rooted so the bootloader prevents to flash the recovery mode.
My principal problem is that there is not the "system.img" file inside the official zip archive.
There is only "boot.img" and "fastboot.img".
I can flash them but it is not enough...I must flash the "system".
I have only the "system" folder so I searched a way to generate a "system.img" file from this folder.
Very not easy to do such a thing.
I booted on a Linux (Ubuntu) partition and I generated an ISO file from system folder, then with "dd" command I generate the "system.img".
All these things take a long time to do because of the size of datas to manipulate (between 500 MB and 1.5 GB).
Even with a "system.img" file, I cannot flash it on the tablet.
I tried first this :
C:\adttools>fastboot flash system system.img
target reported max download size of 569289386 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 525682688 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (544845 KB)...
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1072334848 is not a multiple of the block size 4096
OKAY [ 33.907s]
writing 'system' 1/3...
FAILED (remote: flash_cmds error!
)
finished. total time: 34.735s
So I tried after this :
C:\adttools>fastboot -S 512M flash system system.img
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 635275264 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 139831296 is not a multiple of the block size 4096
sending sparse 'system' 1/4 (500349 KB)...
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1118210048 is not a multiple of the block size 4096
OKAY [ 28.740s]
writing 'system' 1/4...
FAILED (remote: flash_cmds error!
)
finished. total time: 29.448s
I found a program "SparseConverter_1.0.1" to try to chunk the "system.img" but it does not work because "system.img" has a size which is not a multiple of the block 4096.
And now, I cannot find another solution.
The ideal situation would be to find an authentic "system.img" file but it seems that ASUS does not want to give it for "WW" version.
Is someone has a idea to succeed to have this damned "system.img" file ?
Thanks a lot for any help I could receive on this problem.
I cannot imagine to say to this child that her tablet must go to the garbage.
Click to expand...
Click to collapse
If you have root you can figure out your devpath to the system partition and use dd commands to make a system.img.
Example:
/dev/block/platform(or bootdevice)/(chipset)/by-name/system
You have to figure out the path to the by-name folder and also take note of how it is labeled. It could be system, System, or SYSTEM.
then to execute
adb shell
su
dd if=/dev/block/platform/sdhci-pxav3.2/by-name/SYSTEM of=/sdcard/system.img
This is the exact command for my TAB3. Your dd if path will be slightly different.
This can also be done in linux with a folder, I think this is what you need to do.
dd if=/path/to/system/folder of=/path/to/output/system.img
If I had an access to the file system of the tablet, I could directly copy the content of the system folder.
But I do not have such an access.
I have only 2 possibilities :
- fastboot (volume UP + power button)
- adb sideload (via recovery mode) => I cannot use other command adb such as adb pull or adb push
And adb, I cannot do charge the official zip because the system says that there is a signature problem (it stoppes each time between 95-99%)
So the only way I see is to obtain the "system.img" file.
I have only system folder for the official zip file.
But I have other problems when I try to create myself the necessary "system.img".
I tried another method putting an "update.zip" file on a external sdcard..but this method does not seem to have any chance to work.
So I searched for the "system.img" file.
I see that a lot of person ask it on internet but nobody seems to have it.
For information, I have just tested to download the "TW" version (Taiwan I suppose).
As the "WW" version (World Wide, I suppose), there is not "system.img" file inside the zip archive file named "UL-K011-TW-3.1.23.191-user.zip".
Not easy to find some information to solve my problem.
I found a link which helped me a little to generate a "system.img" file :
https://android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
I share the information to help other persons in the same situation than me.
The command is :
make_ext4fs -l 1792M -s system.img ./system
With that command, I could flash the system with these commands :
fastboot -S 512M flash system system.img
fastboot -S 512M flash fastboot fastboot.img
fastboot -S 512M flash boot boot.img
=> fastboot.img AND boot.img are given by ASUS in the ZIP archive file
But even if the flash are OK, that did not make the ASUS MeMO PAD 8 work when I reboot the tablet.
I think that there is another problem from the "system.img" file...but I don't know what.
Any idea someone ?
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
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