Because my FP is rooted, I couldn’t install the update right away.
Couldn't update, installation problem
The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on
This is how I was able to install the update:
Return to stock boot.img
Get current build number →
Settings -> About phone
Download stock boot.img →
(replace 091 with your current build number) Reboot to bootloader →
adb reboot bootloader
Flash stock boot.img →
fastboot flash /path/to/boot.img
Install OTA update
Install update normally Re-root
Disclaimer: You do this at your own risk! I’ve been running my phone this way only for about an hour, this might still eat your data, make backups!
I managed to get Magisk working, here’s what you need:
adb & fastboot
Magisk app installed
The stock boot.img provided by Fairphone
Patch the downloaded stock boot.img with Magisk
Transfer / adb pull that patched boot.img to your PC
Reboot to fastboot $ adb reboot bootloader and temporarily b…
Thank you very much for reporting, I was waiting a rooted user feedback
Will follow your steps when/if the update decides to show up on my device !
I don’t have any error message, but I didn’t get any update after the 091 one.
Rooted with Magisk I followed your way, but
> Flash stock boot.img → fastboot flash /path/to/boot.img
Didn’t work for me, I had to do
Flash stock boot.img → fastboot flash boot /path/to/boot.img
But I still no have OTA…
I’d tried also that way Install OTA Updates on Rooted Android Devices with Magisk | iHax still no messages/no update.
Well, there’s the nuclear option, just factory reset the phone like others suggested
That’s what I did (because I keep doing that anyway), that worked great…
Ooh! Nuclear option - a bit scary for many
I got FP3Q.A.094 update yesterday in normal way, without any trick, on my rooted FP4. I just forgot to install Magisk on Inactive Slot (After OTA) prior to reboot, so I had to reinstall it again after reboot. Now all things seems ok.
Last stock boot.img downloadable is
For future references, current version is A.116 and images are available
But I don’t think we have to necro this thread
Thank you! I tried updating FP3V.A.0116 from A.103-boot.img but no wifi and it did not work. I was afraid… With A.107-boot.img the update is working as usual.
I couldn’t quite follow you there, but broken Wifi, usually coupled with no sound and a hot phone, is usually due to running an outdated kernel. The current software version is A.116 but as of now FP only provides the A.107 kernel for manual download.
You should not manually flash a kernel, but use Magisk to patch the currently running kernel from within Android
The guide by OP is a bit misleading
I just followed OP guide, maybe the A.103 kernel I patched with Magisk was outdated. Starting again with patched A.107 kernel works fine. Thank you.
You shouldn’t flash a
boot.img to a device running
A.116, next time just follow these simpler steps to perform the OTA update:
In Magisk press
Uninstall Magisk → “Restore Images”
Install OTA-update and let it perform a full reboot
Use any Magisk patched boot.img you have lying around and fastboot boot from it
Choose “Direct Install” in Magisk as usual, reboot and have fun
It doesn’t matter which boot.img you use, you just won’t get usable wifi (and some other problems) with the older ones, but since we only need to install Magisk that doesn’t really matter.
I uploaded a Magisk patched boot.img from the…
I have already uploaded a patched
boot.img for the latest release here:
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
If you need a stock
A.0116 I can upload that as well.
As a general rule, don’t flash any
boot.img if you don’t have to, just follow the original root guide, it’s still valid.
@amoun nice thought , but that’s only the
ota.zip file. There is a
“hidden” in there but it’s unnecessarily hard to get it out, copying one from a already updated system is way easier
@hirnsushi ! I hadn’t seen that.