No the official sources exist for lineage 16.0, there only is no one to build it at lineage sources 
Will add it to the list and share a test build ASAP
1 Like
Then if the sources work perfectly and fulfill LineageOS rules, why isnât it officially supported ?
You can see here that itâs not a version we can officially build for. The fact itâs on LineageOS github doesnât mean itâs officially supported.
But of course nothing prevents somebody to create a test build using this source, and it can work very well, but I think that it just doesnât fulfill all LineageOS criteria and thatâs why itâs on their github but not officially supported.
(According to what I know)
I really am not sure why it isn t official, there is arco maintaining the device tree, which is the one on lineage sources and also the one which i build the unofficial pi/e/ build for the device
@Manoj Test build flashed to OP3T with twrp-3.3.1-1-oneplus3.img already present on device as the recovery for previous /e/ version, no stock ROM required, working impressively well!
Flashed on Sony Xperia XA2 which was running versions of /e/ in each slot. Wiped/formatted with twrp-3.3.1-6-pioneer.img, no stock ROM required, working great.
Note: About a month ago flashed a stock Android 8.0 ROM. Looking forward to see how an OTA will perform on this one.
2 Likes
Thanks @chrisrg have added the details you shared in the table above.
Planning to build a device based install guide. Right now we have a generic guide on the same model as what exists on the Lineage wiki
A âone size fits allâ install documentation approach does not seem to be working .
These inputs will help us create / update the documentation and make it more helpful to usersâŚ
1 Like
Installed the Pie build on the Redmi 3S land . I do not have a SIM on this device so not able to test the calls. Rest it works well.
Steps are as under
Remember to remove any pins / screen locks or fingerprint in the Security & location before rebooting to start the flash process.
The way I did this was after removing the screen lock from my PC with adb enabled I type
adb devices
to check if the device is detected and the USB cable is ok 
next
adb reboot bootloader
I know this can be done by holding the buttons but this is an old phone and has its own set of problems
on the Fastboot screen - here you see a bunny wearing a military hat âŚnot sure why⌠anyway back to the topicâŚ
Again I check if the device is being detected
fastboot devices
This should show you device being detected with some weird numbers
Now we proceed to temporarily flash the TWRP image which I did by typing
fastboot boot twrp-3.3.1-1-land.img
wait for a couple of seconds
check the below screenshot for all these steps
Once the TWRP screen showed up on the phone I followed these steps.
- Wipe button
- Format data if encrypted
- Advanced wipe button
- Dalvik cache + System + data
- Swipe to wipe
- Back 3 times to come to Main screen
7.On PC terminal
$ adb push e-0.9-p-2020070861903-test-land.zip /sdcard/
This will show a message like this
e-0.9-p-2020070861903-test-land.zip: 1 file pushed. 30.2 MB/s (848387279 bytes in 26.806s)
and the screen would look something like this
-
In TWRP - tap install button Select the zip file you just pushed
-
Keep Zip signature verification unchecked
10 . Swipe to confirm flash
11. Wait and watch a blue lines cross the screen
12. Wait 5 min âŚmay be less screen will flash a lot of messages âŚthe last would be âŚdone
13. Reboot system
14. Mi logo shows up
15. The gif of the bouncing ball under the e logo will appear
16. Wait for 5 minutes for the main screen and complete the rest of the configuration.
4 Likes
Ok, sounds like the same as the âbare metal versionâ/ no preinstalled 20 Apps.
1 Like
Update: Samsung Galaxy A3 2016 (a3xelte) still running stably and smoothly.
@Rik pl can you share the TWRP details âŚi wanted to add all these details in the table above based on which we can build a better device specific install documentation for all devices.
Sure, do you mean which twrp version I am running?
Yes the version you used to flash the build initially
Tested Oneplus 5t and uploaded test protocol.
Only few minor bugs, Important stuff works.
Came from latest Oreo Build for Dumpling.
TWRP 3.4.0-0-cheeseburger_dumpling.
1 Like
the build was TWRP 3.3.0-0
I have successfully installed test build on Honor 5x (kiwi). There was only one problem: I could not install the test build with latest TWRP twrp-3.4.0-0-kiwi.img. There was an error during adb sideload. After installing twrp-3.3.1-0-kiwi.img the installation of the test build went smooth.
I tested most of the features except where SIM card is needed, as I do not have a SIM card for this device. All tests went well and I did not find any bugs or problems!
Summary: /e/ pie runs smooth on Huawei Honor 5x - kiwi 
3 Likes
Thanks @weichselbaumj have noted the details in the main post.
Interestingly a number of users have reported that the latest TWRP versions do not work âŚin all cases the solution was to go one version back.
Hi @Manoj, would this step be a general recommendation for flashing to any device? I noticed while flashing the pie build to my Xperia XA2 that I was entering password pins in twrp, which was a new thing for me.
Iâm trying to get a grip on this flashing business but itâs slow, and not a little confusing! 
Do firmware updates come with /e/ installs or does that have to be done separately? I notice the firmware version is unchanged from the Android 8.0 version I had previously.
Thanks.
Removing the pin or locks before flashing is to avoid unnecessary issues with the flashing later. We can always set up the pin later when the install is done.
Firmware is not a part of the /e/ ROMâs as yet. We are working to have it added to the builds so that the âFlash the stock ROM firstâ part can be avoided.