I’ve uploaded a new boot.img taken from the latest FPOS update (A.0116) and patched with Magisk v24.3.
Everything still working fine with Magisk 
4 Likes
@hirnsushi Would you like to elaborate a bit on this?
In particular, I installed iodé and rooted the phone (with a patched boot image and Magisk) and I wonder if it’s possible (and advisable?) to relock the bootloader (I know about checking get_unlock_ability) and have Verified Boot enabled (after flashing iodé’s avb_custom_key). Or will I need to unlock the bootloader again for e.g. system updates?
You can’t lock the bootloader if you rooted your phone.
I am by no means an expert in AvB, that’s why I’ve called it a minefield, but since rooting your phone does alter your boot partition the hashes wouldn’t match anymore and hashes that changed are no longer verified 
You have two choices:
- If you switch to stock (unrooted) and relock the bootloader you don’t have to unlock the bootloader to perform OTA updates, but you also won’t be able to use root.
- If you want to stay rooted you’ll have to disable Magisk every time there’s an OTA update:
Ok that’s good to know. Thanks a lot! 
1 Like
Hi,
I’m new here and do not own a Fairphone 4 yet. But I like the concept and I think it has everything I need from a smart phone.
Since I want to OWN the phone I want to root it. The rooting process as described here needs Windows or MacOS at some point – I only have Linux available.
Is a howto available with respect to that?
How is OS update OTA possible?
Thanks a lot for your help.
I wrote the tutorial from a Linux PC, rooting works perfectly fine on Linux.
Oh and welcome to the community btw 
1 Like
Thank you!
For now I don’t want to replace stock OS with . Did it when using an old Samsung S3 → CyanogenMod. But with the new FairPhone I would try it with stock OS first. Just Magisk is mandatory. When later changing to another OS I have Titanium Backup to save my data.
Your tutorial: I am stuck at point 1. How do I patch the downloaded stock boot.img with Magisk?
Where can I get the boot.img? [EDIT: Sorry, overlooked the link in FP4 Root Access is possible, maybe a bit risky - #43 by hirnsushi]
I know how to handle Linux but I am quite unexperienced in flashing phones.
Any problems to get the Fairphone recognized by my Linux PC?
You have to install the Magisk app to your FP4, select 
Install → Select and Patch a File and choose the boot.img.
Don’t use the old boot.img that’s linked there, you can get newer ones here.
Depends on your distribution, but generally not a problem. You’ll need the Android platform tools for adb and fastboot, but those should be packaged already. If they don’t work without sudo you might need android-udev-rules as well.
Some USB-cables / -ports can sometimes be a problem with fastboot but that’s not Linux specific and can only really be solved by trial and error, other than that you should be fine
3 Likes
Ok, will try when I have bought my Fairphone. Will take some time. But I am quite sure that I return here then.
2 Likes
I installed Xposed, however when searching for modules it couldn’t find anything. Is there no module officially available? I didn’t knew this risks to brick a device, too.
Hi. In Magisk I have activated Zygisk, then I have installed LSposed-Zygisk release and I have all kinds of modules in LSposed app, such as GravityBox (R). AFWall+ is recognized too, or Greenify
Just to be sure: This does work with the official rom from fairphone?
currently I restore the image, install the update, do one reboot, boot from an older image and patch the current image, and reboot. patching directly after install and before reboot would save quite some time.
It does, I’ve successfully used it with both CalyxOS and stock FPOS 
1 Like
Tried it with my present phone (HTC U11). It’s easier than expected. Both, adb and fastboot, are available as packages from ditribution.
sudo apt install adb fastboot
was all I had to do.
Connection worked on the first try. Later this year I’ll buy my Fairphone 4. Thank you!
2 Likes
I’ve uploaded a boot.img for the latest FPOS release A.142 patched with Magisk 25.1 for people who want to skip the first two steps
3 Likes
Just a little add for those who might do it directly after receiving the FP4.
I got this after the first reboot after flashing the patched boot.img
After I hit OK and it rebooted, Magisk was not installed anymore. (Probably an A/B slot issue)
I reflashed it and did it on the described way. The message in the screenshot I never saw again.
So just hit cancel and follow the described way. 
1 Like
I used the boot.img in the CalyxOS installation file (FP4-factory-22307020.zip). That zip includes a image-FP4-sq3a.220705.003.a1.zip, which contains the stock boot.img. I patched that one, booted from it and was able to direct install via Magisk app. Thanks!
2 Likes
Thanks for reminding me, I should probably change the wording of those instructions to be a bit more general. And that link to the boot.img still points to the oldest one available 
Glad everything worked fine for you
Edit: Updated
2 Likes
I’ve uploaded a new FPOS-A.163-magisk-boot.img, patched with Magisk v25.2, for people who want to skip patching the boot.img.
5 Likes