S7 migrate from LineageOS 17.1 to /e/

[Crankey]

Thanks. The problem wasn’t having the wrong device file, the problem was I had tried to install Oreo on the S7 using TWRP 3.4, which at the time was new and I wasn’t aware (and it wasn’t made clear) that the two were incompatible.
However, now I’m stuck.
I tried reverting to TWRP 3.3.1 and it just gets stuck in a boot loop, unable to go into recovery. The message is about kernel header length, I think, but I’m just going from memory. So I reinstalled 3.4 but then the phone only booted into TWRP and I couldn’t get the OS back. So I reinstalled 17.1 (unoffical) and has success getting that booting, but I haven’t done anything else with it.
What I’d like to do from here is either get a functioning official /e/ installation or migrate to the GSI version you mentioned here, which I suspect might be a long term solution.

[GSI] Q-GSI --- new version download location. See post 73

Excellent @anon26953564, you’ve learned quickly to build a GSI eOS ROM that works right out of the box. Thank you for taking the time to do this. I installed your latest eOS ROM on my treblesized Galaxy A3 2017 ‘a3y17lte’ via TWRP 3.4.0-0, previously running @harvery’s eOS-Q-Full-_arm64_bvS-20201017 ROM, and was only able to briefly test three key features. [poco2] On first start-up, the SIM card is immediately recognised and the PIN is requested. Incoming and outgoing calls and text messag…

Any suggestions on how to proceed? I think I have a couple of options. Maybe.

1. Somehow downgrade to TWRP 3.3 and go with the official /e/ build
2. Stay with TWRP 3.4 or greater and move to a newer unofficial release or a GSI build. I don’t know the requirement for a GSI install, so I don’t know if that’s feasible or how to go about it. I’ve done more Linux installs, including partitioning, over the years than I could count, so I’m familiar with the ideas that seem to be at play but don’t know the details of their implementation on Android.
   Thanks