@Smojo
Indeed CHECKIN is only if the OEM Unlock is still grayed out on some devices.
And while you may not be relocking, especially while rooted, you should probably still flash the avb file.
There are some device specific steps here: https://divestos.org/builds/LineageOS/fp3/install.html
but you can really just substitute any other recovery recovery (TWRP/OrangeFox/Lineage), so that you can flash your addons.
Finally found some time to go on with this.
While flashing DivestOS to the FP3 I got an error and idk the reason.
fastboot update divested-20.0-20231110-dos-FP3-fastboot.zip
working until …
Sending ‘vendor_b’ (1048576 KB) FAILED (remote: ‘data too large’)
fastboot: error: Command failed
I ignored that and just went on with the other install steps.
Works as described 
Have them very detailed documented here, so if one still needs that one day, feel free to ask.
I was confused as it was stated that the boot takes several minutes and I thought I have wait while I was seeing this picture which felt a bit cropped at the bottom.
Until I realized that this is already the start screen and I have to scroll down to start with the setup.
Not sure if it can be adjusted to the device display resolution?
Also rooted successfully: How to root the Fairphone 3? - #105 by Smojo
The internet says your fastboot command could be outdated.
You could try with the one from the current Android SDK Platform Tools, really make sure by checking fastboot --version.
latest
fastboot --version
fastboot version 34.0.5-10900879
@AnotherElk
actually the opposite, an older version may be necessary
@Smojo
the website recommends 33.0.3: Bootloader - DivestOS Mobile
Will re-do the whole install procedure with older android tools. Generally the OS runs, but I just realized that the Divest OS apps (like browser etc.) are missing or at least they are not visible. Installing an Mull update from F-Droid at least tells me that the signing is different so something is there. ^^
F-Droid also shows a timeout when syncthing the Official Divest Repo. Could be another issue but we will see.
@Smojo
Do not bother restarting the steps over.
Your system is correctly installed if it is booting and you sideloaded it.
Mull is NOT included by default due to space issues, and F-Droid will prompt to install it on first run.
None of the other Divested apps are included either by default, the system is kept very minimal based on user feedback.
The signing isn’t different for the version in the DivestOS repo enabled by default, sometimes on first run it doesn’t refresh all repos correctly, try manually refreshing.
Hm refreshed manually several time and I always get:
Alternatively tried Neo Store and it gets a Network Error as well (only for the divest repo).
Have to check what’s wrong there, I had issues from time to time loading divestos.org in general in my private network, not sure what is the reason for that.
Edit:
Indeed I cannot reach divestos.org in my home WLAN. (same for the FP4 right now - as explained I remember that I had that from time to time)
Switching to mobile data on the FP4 and provide a hotspot to the FP3 it syncs the repo and installs Mull and Mulch (the probably missing initialization steps)
Have to check if this is an DNS issue or so. And why only for the divest website.
@Smojo
It is highly likely you tripped the firewall and were permanently blocked.
Are you using any severely outdated web browsers? Like not updated in a year? Such as Firefox <100 or Chromium <100?
Also please don’t use Neo Store, it doesn’t support mirrors or delta index updates which results in increased load on the primary servers of f-droid.org and divestos.org.
Not aware of any.
Different devices and a lot of different browsers (LibreWolf, Chromium on the PC; Fennec, FOSS Browser, Mull, Cromite, etc. … Mobile) but non of them is so outdated.
But it explains why a router reboot solved it last time → new IP.
I’m in good contact with the Neo Apps main Dev so will ask about this (he is probably already aware).
Will switch to F-Droid on the FP3 at least to not bring to mich load on your repo.
@Smojo
Only the official F-Droid (and Basic) client does it proper:
Is there an easy way for you to see why an IP was blocked?
(e.g. if I pm you my IP or restart the router and send you the new IP) I’m really wondering what goes wrong for me.
Forum says you don’t accept PMs right now (or maybe one can set this generally in the forum).
So idk, maybe leave me a message first I can reply to or we use another channel.
Reading the Forum several years helped me solving some quirks at FP2, Lineage and Apps. Thank you all the forum members for sharing handy hints.
In June ′23 i switched to FP4/DivestOS due to FP2 sometimes was very slow, got hot or crashed.
On my new FP4 I mastered to install DivestOS by first updating FairphoneOS, unlocking the bootloader etc. carefully Step by Step as described at Install Section of Divest OS and here in the Discussion. 
This was a huge step to stay up to Date including Security and self-determined use of personal Information. All the OTA updates afterwards worked well.
Thanks to excellent Work and Documentation of patient answering @SkewedZeppelin!
So, I would like to contribute my part to that total artwork and pm you or vice versa.
Did I lost out your pm? (did′nt have seen one to check for a Time spent for maintenance of projects)
You ′re busy - I know. And yes, it′s a pitty there is only one button to hide the public profile and presence features, which are different Things.
Your Profile seems to be hidden, how can I get a contact for that?
Does anybody have DivestOS rooted and tried to Update just followimg the procedere like described for other Roms?
Will probably try it that way after Christmas
