[Honor View 10 ROMs, Kernels, Recoveries, & Other D] abisdad:
So this is where I try to remember the steps we went through to resolve this...

Ended up back at the EMUI screen, with 3 options: 1: Download latest version and recovery, 2: reboot 3: Shutdown.

Was advised to do the following:

flash twrp

flash lineage

flash gapps (preferably mindthegapps)

Got TWRP working OK (again Chris Panton's You Tube video).

Then tried to flash linage, using ADB sideload (don't wipe Dalvick Cache & Wipe Cache).

But I got an error: "could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: Failed to mount /dev/block/bootdevice/by-name/system at /system: Invalid argument Failed to unmount /system: no such volume script aborted (no error message)"

So tried to mount wipe/format /system in twrp, then remounted again in twrp, and tried adb sideloading lineage again, but similar problem with an error E1001 - Failed to update system image.

So then tried:

fastboot format system

fastboot format cache

Rebooted into Fastboot and ran both commands, but same response for both: FAILED (remote: Command not allowed)

Next tried:

fastboot erase system

fastboot erase cache

But then system erased OK, but Cache FAILED (remote: Command not allowed), so then went back and tried adb sideloading lineage again, but again failed with a similar error.

Next tried:

adb shell make_ext4fs /dev/block/bootdevice/by-name/cache

But got this msg back:

Could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system

adb shell make_ext4fs /dev/block/bootdevice/by-name/cache

critical error: ext4_create_fs_aux_info: filesystem size too small

Creating filesystem with parameters:

Size: 134217728

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 1024

Label:

Rebooted twrp and tried to sideload again, but got this message:

171026.006.H1/712f20571b:userdebug/test-keys could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system: invalid argument Failed to unmount /system: No such volume script aborted (no error message) Updater process ended with ERROR: 7

Finally used:

adb shell make_ext4fs /dev/block/bootdevice/by-name/cache

This gave me:

adb shell make_ext4fs /dev/block/bootdevice/by-name/cache

critical error: ext4_create_fs_aux_info: filesystem size too small

Creating filesystem with parameters:

Size: 134217728

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 1024

Label:

Then used:

adb shell make_ext4fs /dev/block/bootdevice/by-name/system

Which gave me:

Creating filesystem with parameters:

Size: 5905580032

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 22528

Label:

Blocks: 1441792

Block groups: 44

Reserved block group size: 351

Created filesystem with 11/360448 inodes and 47971/1441792 blocks

Rebooted twrp before trying to sideload again.

SUCCESS! ? But didn't go to 100% - but was told that ~46% was good!

serving: 'lineage-15.1-20180715_120335-UNOFFICIAL-berkeley.zip' (~42%) serving: 'lineage-15.1-20180715_120335-UNOFFICIAL-berkeley.zip' (~43%) serving: 'lineage-15.1-20180715_120335-UNOFFICIAL-berkeley.zip' (~44%) serving: 'lineage-15.1-20180715_120335-UNOFFICIAL-berkeley.zip' (~45%) serving: 'lineage-15.1-20180715_120335-UNOFFICIAL-berkeley.zip' (~46%) Total xfer: 1.00x

Then used twrp to mount system (just tick system, then hit back button)

Then adb sideloaded gapps (full):

SUCCESS! ? But it took over an hour! Got stuck for a long time (15mins) on ~6%, then stuck again on ~38% -Installing search.... Finally after 1 1/2 hours, hit ctrl + C, and was rewarded with a message saying Installation complete!!!

Was going to flash another recovery_ramdisk image from Luk, but missed getting into Fastboot! :(

HOWEVER, LINEAGE BOOTED SUCCESSFULLY! :)

Saying Hello, G English Australia, Emergancy call and START

---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------

Thanks for the offer of help - managed to sort problem with help from Luk.

I wouldn't have been able to tell you the answer to this before, as I didn't know how to find out, but I do now, so thought I'd post an answer for others: BLK-L09.

I found this out by reading the (very small) label on the back of the phone.