[General Questions and Answers] malfuncion:
And now I have a working Vanilla treble LineageOS 18.1 build. Took a lot of trial and error of combinations, but I got it going. So these phones actually use a a/b slot which I found after unpacking the super image using lpunpack. To extract your super.img, use the following:

lpunpack super.img super/

I believe this tool comes with the Android Studio install or the platform tools.

From there it should spit out 3 files: vendor.img, product.img, and system.img. I used this guide to kind of walk me through the whole thing.

After finding a neat repo of project treble (gsi) builds, I had been trying single slot builds and failing. Finally I went after an Android 11, 64bit a/b config found here. There are other options available as well here. Just be sure to get at least the build you are on or higher (unconfirmed). Download it, extract it and you should have a new IMG file.

Go to the folder you extracted your super image to, delete the product and system images unless you just want to hold on to them to tweak a factory rom. Copy in the lineage or whatever img you downloaded. Now you need to get the sizes of these 2 images using stat. It's covered in the above guide. I however encountered a problem where the a/b lineage actually expanded some on build, and got an error. I just kept bumping up my number to the error size and it worked fine. Once you have the stat sizes, place them in the proper area of lpmake command below. Don't copy/paste it exact, it likely won't work for you.

lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:5771362304 --group main:2212761600 --partition system:readonly:1876303872:main --image system=./lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img --partition vendor:readonly:336457728:main --image vendor=./vendor.img --output ./linsuper.bin

so lpmake is more of the android studio or platform tools. the command is broken down as so-

lpmake, is the builder.

-metadata-size, is a size divisible by 512. this number will work fine.

-super-name, is the name of the partition: super.

-metadata-slots 2, this is because we are a/b super image.

-device super:####, use this number if your super image is 5.38GB. Otherwise Stat your super img for this.

-group main:####, this is the sum of all images you are putting in the super. they cannot exceed the 5.38GB.

-partition system######:main, this is teh stat size of the downloaded image file (Lineage).

-image system, this is the lineage or other downloaded image file.

-partion vendor, this is the vendor image file stat number

-image vendor, where you extracted the vendor file.

-output what you want to name the output.

Once done you can boot your system with MTKClient and perform the following erase partitions:

metadata, md_udc, userdata

Go to Write Partition:

- load the super.bin you created in the super.bin slot.

- load your vbmeta in all 3 vbmeta slots (unsure if 100% necessary, but I did).

- load the attached oempersists_clean.bin file (unsure if necessary, but I did).

- load factory boot image, otherwise it will likely fail play protect certification. You can try the steps here if you need root.

Flash and wait about 7 minutes or so.

Unplug, reboot, profit.

My super images that I just create, I will also link here. Watch that folder as I will likely be creating a few more ROMs for the A30 very soon now that I have the process down. I provide 0 support as these are unsupported and I'm winging it here as it is. The best I have found so far that works 100% without complaining of GP Ceritication is CherishOS A13 version (secure, no root). This is killer for me and checks a lot of the boxes. Lineage20 boots but has wifi issues currently. 18 doesn't pass play store certs for some reason, although it may be the non-secure version I was using. I am also going to try and fix the TWRP's fstab so that we can wipe partitions and get as much featureset out of it as possible.