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 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"
TWRP For Moto G5s Montana
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
Custom Oreo arm64 release????
rssxda said:
Custom Oreo arm64 release????
Click to expand...
Click to collapse
No, first we want a arm32 build.
Can't decrypt/mount my fs with this. Works on Squids TWRP.
Moto G5S XT1794
Can use Treble imagem?
Hello, here is a new version of the twrp arm / arm64.
twrp.fstab file modification
old twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
new twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/vendor ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="Vendor";backup=1;wipeingui
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display="EFS"
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/logo emmc /dev/block/bootdevice/by-name/logo flags=display="logo";backup=1;flashimg=1
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
I'm no longer this model for now because I gave it to my wife, if anyone can try it. But it should work properly
link AFH > https://androidfilehost.com/?fid=746163614322269316
Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.
tafiir said:
Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.
Click to expand...
Click to collapse
whay you whant to backup your stok recovery?
you can flash it on the phone any time with fastboot/mfastboot comand's
just remember wich stok rom you used last time and flash the propper recovery from it!
Thankyou!
Hello New twrp 3.2.2-0 > https://androidfilehost.com/?fid=5862345805528040464
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
PERGUNTA
Essa versao 3.2.2-0 ela e 32/64 bits
kaique teixeira said:
Essa versao 3.2.2-0 ela e 32/64 bits
Click to expand...
Click to collapse
64bit!
teble
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?
tiagoneo said:
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?
Click to expand...
Click to collapse
Of course not. Treble isn't even here yet
Sent from my Moto G5S using XDA Labs
What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?
1ZeeN said:
What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?
Click to expand...
Click to collapse
No encryption support, but installs DU perfectly
will this work for XT1795 model?
going to stock rom instead of twrp
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s
Akshay K yatheendran said:
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s
Click to expand...
Click to collapse
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!
Some random said:
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!
Click to expand...
Click to collapse
It will be shown even on official twrp. You have to disable overwiting recovery by stock system. For example, magisk can handle it
GoldeneyeS2 said:
TWRP For Moto G5s Montana
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
Click to expand...
Click to collapse
I need perfect gapps for motog5s montana please help me??
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