Hi all,
I’m new here and wanted to try /e/ OS in my beloved Honor 9 Lite (LLD-L31). Bootloader is unlocked, TWRP as recovery installed, Kirin 659 (A) = Arm64, treble info stated VNDK 28.0, A-only system partition (read out on stock ROM EMUI 9.1.0.189 (C432E10R1P4), but yes I used for flashing A/B-image due to GSI / Android 12, see further below).
I tried accordingto the how-to with the official actual /e/ OS builds from here: How to /e/ on a non supported device?
But I got an error. “FAILED (remote: sparse flash write failure)”
E:\adb-fastboot\platform-tools>adb devices
List of devices attached
FPMDU18119009229 device
E:\adb-fastboot\platform-tools>adb reboot bootloader
E:\adb-fastboot\platform-tools>fastboot flash system IMG-e-1.1-q-20220630200240-dev-treble_arm64_bvN.system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 15.649s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 15.910s
It’s possible for me to get it running with an old /e/ OS version which I found here: e-pie-20200416-UNOFFICIAL-treble_arm64_beN.img
E:\adb-fastboot\platform-tools>fastboot flash system e-pie-20200416-UNOFFICIAL-treble_arm64_beN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/5 (460796 KB)...
OKAY [ 15.755s]
writing 'system' 1/5...
OKAY [ 3.818s]
sending sparse 'system' 2/5 (424008 KB)...
OKAY [ 14.514s]
writing 'system' 2/5...
OKAY [ 2.970s]
sending sparse 'system' 3/5 (460796 KB)...
OKAY [ 15.619s]
writing 'system' 3/5...
OKAY [ 3.217s]
sending sparse 'system' 4/5 (460796 KB)...
OKAY [ 15.703s]
writing 'system' 4/5...
OKAY [ 3.248s]
sending sparse 'system' 5/5 (158048 KB)...
OKAY [ 5.424s]
writing 'system' 5/5...
OKAY [ 1.117s]
finished. total time: 81.412s
Is there a parameter for fastboot to ignore the sparse flash write failure?
I already tried “–force” but maybe I put it at the wrong point.
E:\adb-fastboot\platform-tools>fastboot --force flash system IMG-e-1.1-q-20220630200240-dev-treble_arm64_bvN.system.img
fastboot: unknown option -- force
E:\adb-fastboot\platform-tools>fastboot flash system IMG-e-1.1-q-20220630200240-dev-treble_arm64_bvN.system.img --force
fastboot: unknown option -- force
I guess it comes from the little system partition. Is there a /e/ OS treble / GSI version available which is smaller?
IMG-e-1.1-q-20220630200240-dev-treble_arm64_bvN.system.img | 2,63 GB (2834985240 Bytes)
I also tried the older ones, like IMG-e-0.23-q-20220514185542-dev-treble_arm64_bvN.system.img but same error.
IMG-e-0.23-q-20220514185542-dev-treble_arm64_bvN.system.img | 2,46 GB (2652426496 Bytes)
Best regards,
Pollux
Btw: Due to the fact, that I can’t get an actual /e/ OS running, I’m using Lineage-OS. This could be installed, also with the hint but not failed.
lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img | 1,90 GB (2046554112 Bytes)
E:\adb-fastboot\platform-tools>fastboot flash system lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (449028 KB)...
OKAY [ 15.723s]
writing 'system' 1/5...
OKAY [ 3.350s]
sending sparse 'system' 2/5 (460796 KB)...
OKAY [ 15.676s]
writing 'system' 2/5...
OKAY [ 3.269s]
sending sparse 'system' 3/5 (460080 KB)...
OKAY [ 15.873s]
writing 'system' 3/5...
OKAY [ 3.243s]
sending sparse 'system' 4/5 (460796 KB)...
OKAY [ 15.368s]
writing 'system' 4/5...
OKAY [ 3.236s]
sending sparse 'system' 5/5 (134276 KB)...
OKAY [ 4.528s]
writing 'system' 5/5...
OKAY [ 0.949s]
finished. total time: 81.243s