with current v131 (same as with v127) update i have same problem with on-phone reroot and work same method
EDIT: anybody here with succes on-device reroot without problem as i have?
Just a short info:
Installed /e/OS on my FP5 yesterday and rooted it. The FP4 rooting method (as described in the first post; which I also used that time on my FP4 with CalyxOS)
is useable and went fine for the FP5 as well.
OTA Updates to be tested when the next /e/OS Update arrives.
2 Likes
Hi
I successfully rooted my device and the OTA updates worked more or less out of the box (v106 â v112 â v127).
But now I donât get the notification for the update to v131. âSytem updateâ still shows my system is up to date with Android security update November 5, 2023âŠ
Maybe I have debloated too much stuff⊠but at the moment I have absolutely no clue why my FP5 doesnât see v131
I have the same problem 
. Shows me only the November update. Doesnât matter, if I try it with mobile data or WiFi.
Switched to iodéOS before I started to use the FP5 as my daily driver (mainly because I can uninstall preinstalled apps there more easily) and rooted it again - same procedure.
OTA Update procedure still to be tested.
Hi FairPhone Community,
as the title states, I am trying to root my FairPhone 5 with Magisk and would appreciate any help I can get.
I already tried rooting it by patching the boot image with Magisk and then booting the image in Fastboot mode.
This did in fact install a stub Magisk app on the phone, but when I used it to bootstrap to a complete Magisk app and rebooted the phone it still showed:
Installed N/A
The full description of what I did
- Unboxed phone
- Updated to version FP5TT40.A.131.20231130 via phone updater and over Wi-Fi
- Enabled OEM Unlocking and USB-Debugging
- Successfully tested adb connection
- Installed Magisk and patched the boot.img I got form the FP5-TT40-factory.zip from the official website
- Transferred the patched boot.img to my PC (and renamed it to âboot.imgâ for convenience)
adb reboot bootloaderfastboot flashing unlock- (Maybe a reboot to see if it did work, shouldnât matter, though)
fastboot boot boot.img(I moved the boot.img to the same directory as the adb files, again, for convenience)
| My phoneâs build number: | FP5TT40.A.131.20231130 |
| Magisk Version, I got from topjohnwuâs GitHub: | 26.4 |
| The instructions I followed: | How to root the FP5 and OTA update - at your own risk |
How should I proceed?
I could try the same process again, hoping for a different outcome (maybe I made a mistake the first time).
I could also try the custom recovery approach with installing the Magisk .apk as a .zip file.
Any advice is greatly appreciated
I moved you question to the original root topic.
1 Like
Maybe you miss before reboot, in Magisk app:
âMagisk Install, Direct Install (recomended)â ?
(which is final instalation to boot partitiion in internal storage)
1 Like
Can you explain what happened exactly after you executed:
?
It should boot into the OS (afaics you run the normal FairphoneOS still) and you can open an App which needs root, already at that point â it should ask via popup to get root granted by Magisk (remember the Magisk App was already installed before as you patched the boot.img).
If this all works then you can and should do as @k3dAR suggested and âreallyâ install/flash root into the boot partition/boot.img, which is on the phone (via direct install)
The the 'fastboot boot' command doesn not do this, it just boots from the provided boot.img, but does not change anything on your phone.
@k3dAR @Smojo
The option âMagisk Install, Direct Install (recommended)â does not show up, indicating that the phone is not rooted at that point. The tutorial was very adamant about not flashing the boot image but instead just booting it. This was really weird to me, but I just went with it.
Retrospectively, I think itâs quite obvious I should definitely use fastboot flash boot boot.img.
Do you agree?
If so, I apologize for wasting your time, will just flash the boot image and see myself out.
I personally donât agree. I rooted my former FP4 and my FP5 two times (3 different ROMs), and it always worked smooth that way. I mean it is a safe way, isnât it?
First you just boot a patched boot.img - if something fails, you can just reboot and you still have a working unrooted phone.
Imaging you directly flash it and whatever is wrong goes wrong or you end up in a bootloop. Imho direct flash is more risky. Still you can flash an old boot.img and hope that it works again - still I think the risk higher.
I donât see it right now, but it feels like something went wrong during the patch and/or boot from this patched boot.img. I would just repeat the steps and as explained ones booted from the patched boot.img, you should be in a rooted OS already (before the direkt install). You can check in the Magisk App or a root checker app or, as explained, just start an App which needs root. Maybe do not rename the patched boot.img, it is not needed actually. You will use the correct filename in the fastboot boot command - it does not required a file with the exact name boot.img.
2 Likes
Thank you for your input. I see now that itâs safer practice to only boot the boot image.
I went through the whole process again and this time it worked.
I think that I rebooted my phone right after updating the Magisk app and before doing the direct install. This would at least explain why I didnât see the option.
Seems like @k3dAR had the right idea from the start.
Thanks again.
1 Like
OTA Update of iodéOS is simpler than with CalyxOS for instance (which I did several time on my former FP4).
One step less - the first one is not needed here.
(Same as for DivestOS btw. which was even confirmed/approved by the Dev - see Divest Thread if interested)
- OTA install (via Settings > System > Updater ) donât reboot
- install Magisk in inactive Slot â reboot
Idk what the detailed technical difference is that the CalyxOS OTAs will fail to install without Magisk uninstall before. (I remember @hirnsushi explained there are different kind of OTAs ⊠Full OTAs can just be installed; donât remember the other one - probably somewhere in the CalyxOS Thread 
)
1 Like
If you have unfortunately uninstalled Magisk (picture above) and restarted your phone because the OTA Update failed:
Get the boot.img for your actual build (you have to extract it from the actual zip file https://support.fairphone.com/hc/en-us/articles/18896094650513-Installing-Fairphone-OS-Manually) and copy it to your phone. (e.g. /storage/emulated/0/Download/boot.img)
Open Magisk and patch the copied boot.img (Install - select a file to patch)
Magisk tells you the name and path of the patched file. (e.g. /storage/emulated/0/Download/magisk_patched_boot_file.img
Copy the patched file to the PC
adb reboot bootloader
fastboot boot magisk_patched boot_file.img
Wait until the phone booted again, open Magisk
Install - direct Install (recomended)
1 Like
iodéOS 4.10 OTA (February) Update went smooth as last time. (and with the same simple approach)
with current v144 (same in previous months with v141, v131, v127, v112) update
i have same problem with on-phone reroot and must still use this (re)root via PC method
so last working reroot on phone for me be with v106 (= 2023/09 patches)
every next month i hope ânow will be without problemâ, but not and alway is same 
please, is anybody here with succes on-device reroot without problem as i have?
I am looking for a âgoodâ instruction to root CalyxOs on the phone FP4 and later also FP5.
This instructions from the XDA is that also applicable for CalyxOs? I look a bit critical to this because it is mixed up the file boot.img from the ROM of the manufacturer with the CalyxOs. I am not sure if this is a good idea.
I have seen also a small instruction given from the user @hirnsushi in this forum. And it looked a bit different.
I would like to root as soon as possible 
Just look at the first post here for this instruction from FP4 working on the FP5 as well
2 Likes