“Requirements […] 2. Make sure your computer has working adb and fastboot . Setup instructions can be found here.”
… where here is a page explicitly telling you to download adb and fastboot directly from Google.
One issue is Linux distributions offering seemingly outdated or otherwise unfit adb and fastboot commands.
Another issue is interested users not following written instructions telling them to “make sure” something works, and how exactly to achieve that if in doubt.
No act of moderation here will fix either issue.
Perhaps /e/'s install instructions could use some bold, signal red lettering in the right place instead.
I’m sorry if there’s a running Lineage thread somewhere, but I couldn’t find the current status of Lineage for FP3.
I saw on the official page that there were a few nightlies for FP2, but is there an active group of people unofficially curating an FP3 version? Or is it more advisable to install /e/ at the moment and customize from there?
I could have sworn there was a thread here but I can’t find it anymore.
EDIT: thanks @Ingo!! I had only searched in Discuss and Help, but forgot about Development.
I just joined the forum and wanted to send a big Thank You for writing this post. That was massively helpful for me as a new Android user, and without this (and the TWRP port) I probably wouldn’t have been able to run Resurrection Remix for the last few months
I don’t know if you are still having an issue with fastboot -w but it is probably because your mke2fs tool is out of date like me. I fixed it by installing the platform tools strait from Google rather than the Debian repos like they recommend in the LineageOS guide here: https://wiki.lineageos.org/adb_fastboot_guide.html
@pigpig: phhusson has added a hardware overlay for the FP3 on my pull request. So with the next GSI builds by phhusson or AndyCGYan installation should become easier. You may want to replace steps 3.-6. simply by fastboot --disable-verity flash vbmeta_a vbmeta.img && fastboot --disable-verity flash vbmeta_b vbmeta.img - there would be no further need to enter twrp…
BTW, on the most recent 0045 firmware LineageOS 17.1 works smoothly - at least my own build which is based on the same sources like AndyCGYan’s but includes a quick & dirty OTA option.
@The_Little_Death: I fully understand your position as I’d prefer an official LOS17.1 for microG myself. However, as nobody so far appears to volunteer as a maintainer, I went my own GSI based route, which is likely easier and provides at least myself with a working phone. AFAIK, so far the GSI approach hasn’t become part of LOS - so my route has virtually no chance to become official.
At first: Big thanks to [pigpig] - great post and I easily (https://forum.fairphone.com/u/pigpig)
installed LineageOS 17.1 with OTA 3 days ago.
The only thing I noticed is that no sound is being redirected to my bluetooth headset (it gets connected, every service incl. HD Audio shows as in use but sound only comes out of the speaker)
Has anybody also seen this issue?