I've got a backup XC I can test your A10 boot image on both with treble pie and treble 11 vendor. Not sure how that would go but if we can get A10 gsis working that might be ideal for now. There are many solid A10 roms to choose from.
Sorry been busy with another project and haven't had much time; here you go (attached below) . For the vendor.img go here: ( https://androidfilehost.com/?fid=10763459528675571027 )
Make sure you don't mix up the boot supplied here and the boot supplied in the .zip from the link, just use the vendor from it. Remember to use an A/B system.img with whatever 10 variation you choose and you might also need to set SELinux to permissive with: ( https://zackptg5.com/downloads/Kernel-Sepolicy-Patcher.zip )&( https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip ) disable encryption of data as it can cause issues with any type of locking method and verity so it will boot. Test everything and post your results when you get a chance.
It could be just an A system - try that first, then if it doesn't boot try it with the 11 vendor from here. It's all I can offer thanks to the build system wanting to inflate libraries at quite the expense. Did you try AndyYan's GSI vndklite (try both a/b & a)?Thanks for this - wasn't able to get it going with any treble 10 a/b gsi though.
I used the boot image you provided and the vendor image from the zip, set selinux to permissive by flashing the zip, and it still wouldn't boot to system. Got stuck in a boot loop that just loaded TWRP after each restart. Will try flashing some other combinations to see if anything else might work.
Try without the SELinux patch to permissive; disabling verity wouldn't hurt for the testing either, did you do that as well after disabling SELinux? Do you have the correct OEM libraries installed: ( https://androidfilehost.com/?fid=6006931924117907560 ) ? I will go over the boot again and see if somehow I wrote in the line for treble to be enabled incorrectly (don't believe I did, but will look). If @Sjll would reply to someone we might be able to get an updated tutorial for 10 and 11 treble.Alright no luck so far. I've used the following combinations to no avail:
All of these scenarios result in bootloops. The only combination that got me the furthest is:
- Your boot + your vendor + Andy Yan's LineageOS 17.1 A/B
- Your boot + your vendor + Andy Yan's LineageOS 17.1 A only
- Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A/B
- Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A only
- Your boot + A11 treble vendor + Andy Yan's LineageOS 18.1 vndklite A/B
This one gets me to the OS boot screen but hangs and never loads system successfully.
- Treble 9 boot + your vendor + Andy Yan's LineageOS 17.1 A only
It's a coffee motivation xD
we know about it but it's not critical at this time... wi'll fix it on a one of next updates (if we can)
we'll see, if we don't touch system partitions, then we can flash over previous build, and if we touch they, you must flash update as a clean rom from zero.
Binaries has dependence from kernel version, not from Android version.