[Huawei Mate 9 Questions & Answers] Monster.Kali:
ok

got all missing img files from update.app with 7zip, not with update extractor.

on some of them, i have different sizes

here is the log of fastboot.

many of them flashed ok.

some not.

C:\Users\MONSTER>fastboot flash hisee_fs F:\dload\UPDATE\hisee_fs.img
target reported max download size of 471859200 bytes
sending 'hisee_fs' (8192 KB)...
OKAY [ 0.288s]
writing 'hisee_fs'...
OKAY [ 0.092s]
finished. total time: 0.386s

C:\Users\MONSTER>fastboot flash dfx F:\dload\UPDATE\dfx.img
target reported max download size of 471859200 bytes
sending 'dfx' (16384 KB)...
OKAY [ 0.561s]
writing 'dfx'...
OKAY [ 0.161s]
finished. total time: 0.728s

C:\Users\MONSTER>fastboot flash rrecord F:\dload\UPDATE\rrecord.img
target reported max download size of 471859200 bytes
sending 'rrecord' (16384 KB)...
OKAY [ 0.562s]
writing 'rrecord'...
OKAY [ 0.157s]
finished. total time: 0.725s

C:\Users\MONSTER>fastboot flash fw_lpm3_a F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3_a' (256 KB)...
OKAY [ 0.017s]
writing 'fw_lpm3_a'...
FAILED (remote: image verification error)
finished. total time: 0.061s

C:\Users\MONSTER>fastboot flash fw_lpm3 F:\dload\UPDATE\fw_lpm3_a.img
target reported max download size of 471859200 bytes
sending 'fw_lpm3' (256 KB)...
OKAY [ 0.015s]
writing 'fw_lpm3'...
FAILED (remote: image verification error)
finished. total time: 0.059s

C:\Users\MONSTER>fastboot flash reserved3_a F:\dload\UPDATE\reserved3_a.img
target reported max download size of 471859200 bytes
sending 'reserved3_a' (3840 KB)...
OKAY [ 0.136s]
writing 'reserved3_a'...
OKAY [ 0.056s]
finished. total time: 0.198s

C:\Users\MONSTER>fastboot flash hisee_img_a F:\dload\UPDATE\hisee_img_a.img
target reported max download size of 471859200 bytes
sending 'hisee_img_a' (4096 KB)...
OKAY [ 0.141s]
writing 'hisee_img_a'...
OKAY [ 0.058s]
finished. total time: 0.205s

C:\Users\MONSTER>fastboot flash fastboot_a F:\dload\UPDATE\fastboot_a.img
target reported max download size of 471859200 bytes
sending 'fastboot_a' (12288 KB)...
OKAY [ 0.423s]
writing 'fastboot_a'...
FAILED (remote: image verification error)
finished. total time: 0.466s

C:\Users\MONSTER>fastboot flash vector_a F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector_a' (4096 KB)...
OKAY [ 0.145s]
writing 'vector_a'...
FAILED (remote: image verification error)
finished. total time: 0.189s

C:\Users\MONSTER>fastboot flash vector F:\dload\UPDATE\vector_a.img
target reported max download size of 471859200 bytes
sending 'vector' (4096 KB)...
OKAY [ 0.145s]
writing 'vector'...
FAILED (remote: image verification error)
finished. total time: 0.189s

C:\Users\MONSTER>fastboot flash isp_boot_a F:\dload\UPDATE\isp_boot_a.img
target reported max download size of 471859200 bytes
sending 'isp_boot_a' (2048 KB)...
OKAY [ 0.074s]
writing 'isp_boot_a'...
OKAY [ 0.055s]
finished. total time: 0.135s

C:\Users\MONSTER>fastboot flash isp_firmware_a F:\dload\UPDATE\isp_firmware_a.im
g
target reported max download size of 471859200 bytes
sending 'isp_firmware_a' (14336 KB)...
OKAY [ 0.494s]
writing 'isp_firmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.539s

C:\Users\MONSTER>fastboot flash fw_hifi_a F:\dload\UPDATE\fw_hifi_a.img
target reported max download size of 471859200 bytes
sending 'fw_hifi_a' (12288 KB)...
OKAY [ 0.424s]
writing 'fw_hifi_a'...
FAILED (remote: image verification error)
finished. total time: 0.467s

C:\Users\MONSTER>fastboot flash teeos_a F:\dload\UPDATE\teeos_a.img
target reported max download size of 471859200 bytes
sending 'teeos_a' (8192 KB)...
OKAY [ 0.286s]
writing 'teeos_a'...
FAILED (remote: image verification error)
finished. total time: 0.329s

C:\Users\MONSTER>fastboot flash recovery2_a F:\dload\UPDATE\recovery2_a.img
target reported max download size of 471859200 bytes
sending 'recovery2_a' (65536 KB)...
OKAY [ 2.230s]
writing 'recovery2_a'...
FAILED (remote: image verification error)
finished. total time: 2.273s

C:\Users\MONSTER>fastboot flash dts_a F:\dload\UPDATE\dts_a.img
target reported max download size of 471859200 bytes
sending 'dts_a' (16384 KB)...
OKAY [ 0.562s]
writing 'dts_a'...
FAILED (remote: image verification error)
finished. total time: 0.603s

C:\Users\MONSTER>fastboot flash trustfirmware_a F:\dload\UPDATE\trustfirmware_a.
img
target reported max download size of 471859200 bytes
sending 'trustfirmware_a' (2048 KB)...
OKAY [ 0.077s]
writing 'trustfirmware_a'...
FAILED (remote: image verification error)
finished. total time: 0.123s

C:\Users\MONSTER>fastboot flash modem_fw_a F:\dload\UPDATE\modem_fw_a.img
target reported max download size of 471859200 bytes
sending 'modem_fw_a' (57344 KB)...
OKAY [ 1.943s]
writing 'modem_fw_a'...
FAILED (remote: image verification error)
finished. total time: 1.988s

C:\Users\MONSTER>fastboot flash reserved4_a F:\dload\UPDATE\reserved4_a.img
target reported max download size of 471859200 bytes
sending 'reserved4_a' (51200 KB)...
OKAY [ 1.743s]
writing 'reserved4_a'...
OKAY [ 0.413s]
finished. total time: 2.162s

C:\Users\MONSTER>fastboot flash modemnvm_update_a F:\dload\UPDATE\modemnvm_updat
e_a.img
target reported max download size of 471859200 bytes
sending 'modemnvm_update_a' (81920 KB)...
OKAY [ 2.762s]
writing 'modemnvm_update_a'...
OKAY [ 0.648s]
finished. total time: 3.416s

C:\Users\MONSTER>fastboot flash patch_a F:\dload\UPDATE\patch_a.img
target reported max download size of 471859200 bytes
sending 'patch_a' (32768 KB)...
OKAY [ 1.117s]
writing 'patch_a'...
OKAY [ 0.275s]
finished. total time: 1.398s

C:\Users\MONSTER>fastboot flash version_a F:\dload\UPDATE\version_a.img F:\dload
\UPDATE\version_a.img
target reported max download size of 471859200 bytes
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\MONSTER>fastboot flash vendor_a F:\dload\UPDATE\vendor_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (460726 KB)...
OKAY [ 16.785s]
writing 'vendor_a'...
OKAY [ 4.661s]
sending sparse 'vendor_a' (340470 KB)...
OKAY [ 12.505s]
writing 'vendor_a'...
OKAY [ 3.312s]
finished. total time: 37.272s

C:\Users\MONSTER>fastboot flash product_a F:\dload\UPDATE\product_a.img
target reported max download size of 471859200 bytes
sending 'product_a' (196608 KB)...
OKAY [ 6.675s]
writing 'product_a'...
OKAY [ 1.536s]
finished. total time: 8.218s

C:\Users\MONSTER>fastboot flash cust_a F:\dload\UPDATE\cust_a.img
target reported max download size of 471859200 bytes
sending 'cust_a' (196608 KB)...
OKAY [ 6.705s]
writing 'cust_a'...
OKAY [ 1.507s]
finished. total time: 8.218s

C:\Users\MONSTER>fastboot flash system_a F:\dload\UPDATE\system_a.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 593316360 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 112839176 is not a multiple of t
he block size 4096
sending sparse 'system_a' (457291 KB)...
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1070983688 is not a multiple of
the block size 4096
OKAY [ 16.816s]
writing 'system_a'...
FAILED (remote: sparse flash write failure)
finished. total time: 22.552s

C:\Users\MONSTER>fastboot flash frp F:\dload\UPDATE\frp.img
target reported max download size of 471859200 bytes
sending 'frp' (512 KB)...
OKAY [ 0.025s]
writing 'frp'...
OKAY [ 0.022s]
finished. total time: 0.052s

C:\Users\MONSTER>fastboot flash persist F:\dload\UPDATE\persist.img
target reported max download size of 471859200 bytes
sending 'persist' (2048 KB)...
OKAY [ 0.075s]
writing 'persist'...
FAILED (remote: partition length get error)
finished. total time: 0.093s

C:\Users\MONSTER>fastboot flash reserved1 F:\dload\UPDATE\reserved1.img
target reported max download size of 471859200 bytes
sending 'reserved1' (5120 KB)...
OKAY [ 0.182s]
writing 'reserved1'...
FAILED (remote: partition length get error)
finished. total time: 0.204s

C:\Users\MONSTER>fastboot reboot

any idea of some img to load into ram?

or is there a method, that, allows me to flash files on emmc, over serial port?

i mean, serial port allows me to load them into ram.

but i wonder if it's capable to see the emmc.

[MENTION=8180641]user4774[/MENTION] - i noticed that, flashing img's in the order that you gave me, beginning with vrl and vrl_backup, the write prim vrl failed error is gone.

so all of them,in that log,are flashed in order.