As for why LOS disables it, I believe because of the reason @dk1978 stated above: to allow the sideloading of additional packages on top of LOS (like gapps).
So the main consequence is that you cannot do that - anything that modifies the protected partitions will break the verity check. This means that any changes you want to make (other than ‘normal’ user changes, which modify the userdata partition), you need to make at build time.
I followed those at first but it didn’t work out tbh. The phone somehow never booted to recovery when I followed the procedures exactly. It worked better with this guide
Oh, yes, you are right, the instructions on the wiki page are wrong! (or so I believe)
@dk1978 please correct the wiki page ASAP. It currently tells to flash the recovery to the boot partition (???) And the 5. title shouldn’t state “temporarily flash” but “temporarily boot” a recovery. The right command would be
fastboot boot <recovery_filename>.img
and not
fastboot flash boot <recovery_filename>.img
Or did I really miss something here? (Edit: I did)
Edit: Checked in web.archive.org and it was like this before, so I guess it’s normal. But I still miss something important here.
Edit2: Okay, sorry, my bad. Wikis for other devices have the same procedure (and the same error about boot_a that should be boot_b).
But isn’t there one error in the instructions, though?
There is a whole section called "Temporarily booting a custom recovery using fastboot" and item 5. in it says "Temporarily flash a recovery on your device by typing: fastboot flash boot <recovery_filename>.img"
Shouldn’t that be fastboot boot <recovery_filename>.img?
No, I think the recovery flashing (rather than just booting directly) is intended. I don’t know the full background and the history of this stuff yet, but I do expect it to work. With the “temporary” flashing you end up with the LineageOS boot partition image in both slots, and that may be beneficial when the system is up and starts checking for updates.
I got the error “Couldn’t parse partition size ‘0x’” when running the “fastboot flash” command as per the official instructions. It worked fine using “fastboot flash:raw” instead so I hope this didn’t cause anything bad to happen. This was when switching from an /e/ OS install.
Hey, welcome to the community
I also found this solution on the web… I use fastboot flash boot_a boot.img or fastboot flash boot_b boot.img instead, don’t know what’s better. BTW A and B are some kind of different slots where you can install your system on, as far as I know.
I think I ran into some trouble. I was on 16.0 and some days or hours ago I saw there is an upgrade to 17.1. Thus, I went to the wiki of lineage OS and performed like it is intended. Thinking of everything seems easy and it’s rapidly done, I did not backup before… now I’m in a boot loop and don’t know what to If I don’t wanna loose my data.
OK first, I was on 16.0 with magisk and without gapps. I did the adb sideload thing like described, not realizing that its the lineageos recovery… as I was done I did a reboot, as I don’t use gapps and went into the bootloop. “oh snap! Probably it’s becaus of the recovery” thus, I fastbooted into twrp via fastboot flash boot <recovery_filename>.img to adb sideload and just did the upgrade again same problem. I thought perhaps its because of magisk therefore I went again to twrp via fastboot flashed the 17.1 again, without rebooting the system i booted again into twrp via fastboot and flashed the newest magisk. Bootloop again…
What options do I have. Can I at least backup some data of some apps via twrp to my computer or did I just overlook something easy?
EDIT: wipeing cache or dalvik chache does result in the loss of my personal data, wright?
Is it worth to try the ‘fix recovery bootloop’ function in twrp > advanced?
When I perform a backup via twrp which partition do I have to select for saving messages, contacts, notes and so on?
This seems to be a problem with the zip expecting different mountpoints during recovery according to this LOS issue
The workaround from F-Droid forum seems to work for me (unzipping and pushing the files with adb root)
Another thing I noticed is that on my FP3+ the “Night Light” feature doesn’t work, no visible “redshift” when turning on/off or using the intensity slider. I couldn’t find a LOS issue about this, does anyone else here have this too?
(adaptive brightness does work)
And a minor thing in the installation instructions:
Maybe good to mention that between the Fairphone unlock actions and flash/booting the LOS recovery, I had to unlock with fastboot oem unlock
I found this in the /e/ install guide
They also mention to lock the bootloader again after install, which I also did.
Night light doesn’t work for me either. Neither does any color adjustments on the screen. On the other hand, these things did not work in /e/ OS either.
Night Light: Doesn’t seem to change anything. Side note: I do have a Samsung S7 with LineageOS 17.1 as comparison. There I can go to Display -> LiveDisplay and configure the color temperature and it works (which seems to be the equivalent of “Display -> Night Light” - not sure why this is different between LineageOS on the S7 and FP3). It would be really great if this would work in one of the next releases.
I also had the same experience having to to the unlock coming from /e/. I also locked it again right after the first successful boot.
Another thing I struggled with: I had to use "fastboot flash boot_a ./lineage-17.1-20210104-recovery-FP3.img " (instead of “… boot” (without the _a) as written in the documentation). Not sure if that was caused by me making some kind of mistake. In the end it took me a couple of iterations with “fastboot flash boot_a” and “fastboot flash boot_b” until it was successful.
Apart from that everything seems to run very smoothly so far. Thanks again, @dk1978
Another side note: I’m using an FP3 (not the +) and both camera modules worked nicely. I started with the original camera module and just inserted the camera+ module and didn’t observe any issues with either of them.
That is not good. My advice - before you do anything else, go into TWRP, do a backup of your data partition and use adb pull to transfer the backup to your PC. At least then, you have a good change of restoring the phone to the state it was in before, if necessary with a factory reset + TWRP restore, and then backups of vital stuff like contacts, photos, etc.
Then, with that done, you can think of how to update.
I was waiting for this ROM. It solved some issues I had with the official build, finally my phone works properly. I see that Lineage expanded the support for dual sim operation but the button to turn off sims is still missing, not too bad.
Thank you veeeery much
I’m interested in building my own LOS 17.1. Following the instruction, I see that I need to be root to extract proprietary blobs… Is there another way to obtain them ? I’m currently running the official Fairphone OS.
I get a lot of “file not found in source” when executing the extract-files.sh. Not to all files but a lot of them.
Great that you want to build yourself! The more people that get skills and experience with own 17.1 builds, the better.
First of all, you probably don’t need to mess with extracting blobs yourself. Just PM me and I will point you to the location where you can download them, ready to be used by the build.
I am not sure what you mean by being root. You mean being root on your Linux PC? That is definitely not necessary, since adb can be used as a normal user.
The reason you got “file not found in source” is likely that I decided to move some of the Qualcomm blobs out of the system partition (where they do not belong, that should be AOSP-only land) to the system/product subdirectory. We are not using a dedicated product partition, since the stock one is just too small (128 MB) to be of use.
Maybe you can use this bash script from @maba007?
I didn’t use it for my own FP2->FP3 migration, probably would have tried it out if I’d found it last monday
:
