[OnePlus 8 ROMs, Kernels, Recoveries, & Other Devel] :
I seem to be getting kicked back to bootloader after installing this via fastboot and fastbootd.. Is anyone else having that happen? It's a bummer Awful. Heres my output -

*mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot flash recovery recovery.img

target reported max download size of 805306368 bytes

sending 'recovery' (98304 KB)...

OKAY [ 3.130s]

writing 'recovery'...

OKAY [ 0.350s]

finished. total time: 3.480s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot flash boot boot.img

target reported max download size of 805306368 bytes

sending 'boot_a' (98304 KB)...

OKAY [ 3.095s]

writing 'boot_a'...

OKAY [ 0.345s]

finished. total time: 3.440s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot flash dtbo dtbo.img

target reported max download size of 805306368 bytes

sending 'dtbo' (24576 KB)...

OKAY [ 0.784s]

writing 'dtbo'...

OKAY [ 0.082s]

finished. total time: 0.866s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot --disable-verity flash vbmeta vbmeta.img

target reported max download size of 805306368 bytes

sending 'vbmeta' (8 KB)...

OKAY [ 0.011s]

writing 'vbmeta'...

OKAY [ 0.005s]

finished. total time: 0.016s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot --disable-verity flash vbmeta_system vbmeta_system.img

target reported max download size of 805306368 bytes

sending 'vbmeta_system' (4 KB)...

OKAY [ 0.011s]

writing 'vbmeta_system'...

OKAY [ 0.002s]

finished. total time: 0.013s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot devices

a3c846ac fastboot

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot flash system system.img

target reported max download size of 268435456 bytes

Invalid sparse file format at header magic

sending sparse 'system_a' 1/4 (262092 KB)...

OKAY [ 8.591s]

writing 'system_a' 1/4...

OKAY [ 1.488s]

sending sparse 'system_a' 2/4 (262142 KB)...

OKAY [ 8.614s]

writing 'system_a' 2/4...

OKAY [ 1.494s]

sending sparse 'system_a' 3/4 (256813 KB)...

OKAY [ 8.579s]

writing 'system_a' 3/4...

OKAY [ 1.465s]

sending sparse 'system_a' 4/4 (133032 KB)...

OKAY [ 4.338s]

writing 'system_a' 4/4...

OKAY [ 0.802s]

finished. total time: 35.371s

mackisus@jmdesktop:~/Downloads/payload_dumper$ fastboot flash product product.img

target reported max download size of 268435456 bytes

Invalid sparse file format at header magic

sending sparse 'product_a' 1/6 (261729 KB)...

OKAY [ 8.545s]

writing 'product_a' 1/6...

OKAY [ 1.494s]

sending sparse 'product_a' 2/6 (261754 KB)...

OKAY [ 8.543s]

writing 'product_a' 2/6...

OKAY [ 1.485s]

sending sparse 'product_a' 3/6 (262088 KB)...

OKAY [ 8.550s]

writing 'product_a' 3/6...

OKAY [ 1.470s]

sending sparse 'product_a' 4/6 (261395 KB)...

OKAY [ 8.562s]

writing 'product_a' 4/6...

OKAY [ 1.474s]

sending sparse 'product_a' 5/6 (262060 KB)...

OKAY [ 8.520s]

writing 'product_a' 5/6...

OKAY [ 1.456s]

sending sparse 'product_a' 6/6 (191860 KB)...

OKAY [ 6.248s]

writing 'product_a' 6/6...

OKAY [ 1.148s]

finished. total time: 57.495s

mackisus@jmdesktop:~/Downloads/payload_dumper$ *

I made sure to switch to fastbootd after flashing the vbmeta image. Not sure what i'm doing wrong, i even did this without patching the boot.img file with magisk in order to troubleshoot it. I have not upgraded to OOS 11 yet either so possibly that could be a issue? I may have to MSM back because this process really screwed the device up, but i will try once more after that.. What could be the problem?

EDIT - I'm really starting to believe this will not work with the IN2017 model, no matter what. Still goes to bootloader trying to flash that yet again after MSM refresh, i really want to run this rom but there is no way to install it that works.