oh man…I totally confused myself with the aborted OTA and magisk reinstall, that I didn’t take any notice of the wrong fastboot prompt… sometimes the trick is too easy, thank you so much!
Is there any clean “how-to root the FP6” anywhere, currently?
This topic gets more and more confusing, and more and more harder to find helpful information within this topic, also thanks to several mergings of other topics into this one.
I successfully rooted mine with magisk a while ago.
Now with the current Android 16 I have serious trouble with hiding root from apps. It is not successful at all right now. Play integrity check fails totally.
So I wonder whether I should root the phone in a different way, without magisk.
Any recommendations?
You’re right, there’s not really an “all-in-one-guide”, and you have to collect all the required information, this might be challenging and confusing.
You can try to root your device with Apatch . The procedure is the similar to the procedure with Magisk.
I’ve tried this method first time with my FP6 and it seems I have less trouble with apps detecting root with repect to all my devices before which were rooted with Magisk.
Hi Michael,
I can give a short “how-I-rooted-my-FP6-finally” (still works under Android 16):
- get the factory image from https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone
- unpack / extract the init_boot.img and patch it on a device with Magisk installed (must not be rooted or the later FP6)
- unlock bootloader as described by Fairphone
- reboot to bootloader
- flash the magisk-patched init_boot.img
- boot device
- install magisk-app (if not done before)
- install magisk into bootloader within magisk-app
- reboot
up to now I was able to install all Updates inline:
- within magisk-app recover original bootloader (do not reboot!)
- install OTA-Update (if You use a root-firewall, deactivate it first)
- before reboot change to magisk-app, patch bootloader in inactive slot
- return to OTA-Installer and reboot from there
doing this keeps root, also hiding apps with Hail does fine.
Yours,
~julric
And if you prefere Apatch instead of Magisk you can follow the same procedure but use the boot.img file and not the init_boot.img file.
can you describe, how you are able to hide root from apps?
Somehow preventing root detection is a bit more tricky with the current Android.
Hi Michael,
this is my way of hiding root from apps:
I use Magisk for root and Hail for Hiding (available in f-droid).
First, in Magisk settings, I acivated Zygisk and Enforce DenyList (maybe a reboot is necessary), second, I setup Configure DenyList with the Apps, I want to hide from. third, You have to Hide the Magisk-App (rename to “Settings” whatever). For the last step, You have to go into Hail → Apps an search for Your renamed Magisk, mark it and hide it via the snow-flake. - Unhiding works by just clicking on the grey App-icon within Hail.
That’s all.
If an app was used before hiding, it can be necessary to clear all settings of the app - some banking-apps store the root-detection even if You hide root. After updates of apps, You hided from root, You have to look in Magisk→Settings→Configure DenyList, if the app has changed and the hiding-mechanism for the app has gone. (mostly I saw this behaviour for banking apps)
Good Luck!
I just rooted on the latest LineageOS with APatch, you don’t even have to hide root, it’s hidden by default and you enable it for the apps you want to have root access. No problems with my banking app.
when using Hail to hide the hidden Magisk, which mode do you use? Hail offers a couple of different ways. I see following hiding options: Shizuku, Root , Dhizuku, Device owner, Insular.
I have no idea what are the differences between them.
Sorry, I forgot to reply:
I use the root-method of Hail to hide apps. Works for me without problems.
~julric
Hi, ive been rooted with apatch since I got my fp6 & want to switch to kernelSU. Rather not mess this up, any tips for switching to kernelSU? I keep reading online you need a patched kernel for kernelSU & there is this new one called kernelSU NEXT which adds to the confusion. Can you provide a quick how to? I’m currently back to unrooted but unlocked bootloader. I had a bunch of issues with apatch after the last update 11219.
Should be pretty similar to apatch. Patch the stock init_boot and flash it through Fastboot. Later on an update you can just patch the inactive slot. You can use both KSU and KSUN, doesn’t matter so much.
OK great, im comfortable doing that but 1 last lynch pin question. I have what was a beta build of FP6.QREL.16.95.0 that build recently went public & I think there were no changes. Because I unrooted with apatch I can’t pull my exact init_boot.IMG & had to grab a copy from here:
It looks like its fine & should be the exact same thing. But I hate to end up switching partitions & or have worse issues because I got it wrong. What do you think? Should I be OK? Or better yet do you have a copy of FP6.QREL.16.95.0 init_boot.IMG?
UPDATE: I went for it & the files at the above link can be trusted.. Got kernelSU Next running… Thanks