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. 
@Smojo
if you’re fine with that you can
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.
@Smojo
I allowed messages from you, try again.
1 Like
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.
2 Likes
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?
- uninstall magisk (restore images)
- install OTA Update (do not reboot)
- use install magisk in inactive slot (after OTA)
- reboot
Will probably try it that way after Christmas
@Smojo
you can probably skip the uninstall step
2 Likes
I tried to find the answer for an important question. After installing DivestOS, are all updates for Fairphone provided OTA including major? The problem is manual updating and losing data due to wiping all data. This is a common problem using /e/ if no OTA update is available (which usually is avvailable for Fairphone if one uses stable).
@Undertaker
DivestOS always supports in-place upgrades when possible.
You do not need to wipe for minor or major updates.
DivestOS additionally includes all necessary firmware for FP3 and FP4.
I’ve even tested upgrades across multiple versions at once, eg. from Android 7 to 10, from Android 9 to 11, Android 11 to 13.
Major upgrades do require manual installation, either by downloading the update and importing it into the Updater app or by adb sideloading it. No wipe is required here. It is just forced to ensure the user reads the website for any changes and to ensure they backup first.
2 Likes
Thanks for your answer. How do you answer all these posts in a ‘foreign’ forum…
Okay, that was unclear. With ‘all updates’ including major I thought about upgrades as well. (No native speaker so sorry for that). If no wipe is required, why do users have to backup? Is it simply a data security step (just to be sure) or what is the point? Some apps do not provide possibility for backups (like FF/Mull (sync is no choice)). That’s why I’m asking.
Additional question: I noticed that eSIM is supported for FP4. As OpenEUICC is used and as I read, that OpenEUICC is not a completed implementation (and it is only used by Divest compared to other established custom ROMs), I wonder if there could be problems with specific providers. Can you say something about that?
@Undertaker
You should always be backing up, no matter what computer, device, or software you use.
with specific providers
Most people I know have had no issues with activation using it. But all of those reports were on Pixel devices, not FP4.
Okay, not exactly the answer but it is apparently what I said.
Well that sounds not very confident to me. And it is not easy to find sufficient information about these points. So unfortunately I have to wait until hopefully some users can confirm this is working.
DivestOS on FP4, re OpenEUICC: I see warnings that it “has stopped” or so but have ignored that for the moment.
eSIM worked without a hitch, I use it for data with a second provider; the physical SIM for phone and texting only.
Updates are smooth from within the system settings, and to know when to update (and for other news) I recommend a site monitor like visualping.
1 Like
FP3: I shifted from Lineage OS to Divest OS yesterday. Everything went good.
I also experienced the “Sending ‘vendor_b’ (1048576 KB) FAILED (remote: ‘data too large’)
fastboot: error: Command failed” error mentioned by @Smojo . Ignored the message as suggested by him and went through with the installation.
I get the “You have installed a differt system” screen when booting. I guess it is so?
Thanks a lot. Coming back to Divest OS. I am happy.
I think is the case for every Custom Rom (every Rom except the original one - Fairphone OS).
I just installed CalyxOS on an FP4 + locked the bootloader again and it it shows that screen as well. I think somewhere in this thread it was already discussed - e.g. here: Divest OS: Everything about Divest OS on the Fairphones - #47 by AvidAlbatross
1 Like
This is an issue with the latest fastboot 34. Version 33.0.3 is recommended.
But it sounds like your install is fine 
1 Like
Hello, my adb commands are working fine but I have a problem that when i try to use fastboot commands, nothing happens or it says < waiting for any device > and does not change (tried in the bootloader), I was wondering where I went wrong?
Also, should I update from android 11 (never updated once since i got the phone) to the latest update (android 13) or will there be some anti-rollback feature?
Thank you a lot for the help!
Maybe this thread will help you with this issue: Command "Fastboot device" is not recognising the FP3
But idk if you use Windows as Desktop OS
2 Likes
First try other cable and Ports, else when using windows you most likely need to update the bootloader driver
3 Likes