Oh yeah, had to unlock the bootloader to even install /e/OS in the first place.
I’ll definitely take a look at APatch, thanks for the resource! Did you use this to root an FP6 running /e/?
Usually one locks the bootloader after flashing the ROM, because leaving it unlocked makes the phone insecure. BUT DON’T DO IT YET, there seems to be issues that can brick your device atm.
yep, rooted the FP6 on /e/OS 3.0.2, also updating to version 3.0.4 (beta) worked fine, root still works!
2 Likes
Oh cool, root survived an update? That’s a nice feature. If it supports modules too, I’m convinced. Will give it a shot and report back with results.
Just out of curiosity, did you try rooting with Magisk at all? Or just APatch? I’m wondering whether Magisk would work for you…
Edit - APatch did the trick, thank you!!
I merged your topic here to this existing, as the rooting process is unrelated to the installed system.
1 Like
I didn’t try magisk, I heard about APatch a while back and was just waiting for an opportunity to give it a try.
Android updates with APatch work in the same way as Magisk:
- Do OTA update (don’t reboot)
- Open APatch manager and pick “install to the other slot”
- Now reboot and it’s all done
The APatch documentation has more infos about how OTA updates work but these 3 steps is all it takes for each update basically. 
2 Likes
So it seems at the moment rooting with magisk doesnt work, if related to the fact that fastboot boot doesnt work/exist is unclear. APatch seem to use a different way to root the device and is working on the FP6. So for the time being it seems to be the way to go
Confirmed, APatch worked on the first try to root my FP6 with /e/OS 3.0.2
Apatch uses a completely different concept to root a device. There is also no way switching between these two concepts. So Apatch is no solution while Magisk is not possible. Please work on enabling rooting FP6 with Magisk soon.
Thanks in advance!
~julric
1 Like
I cant I’m no employee.
What does that mean?
1 Like
Actually magisk (as well as KSU) also works on FP6. You just have to patch and flash init_boot instead of boot. (This is actually what also happens if you would do with a direct install in the app, after fastboot boot)
2 Likes
Unfortunately my banking app detects all three rooting methods though, even with additional hiding modules.
Can someone be so kind and try Native detector (GitHub - reveny/Android-Native-Root-Detector: A tool for detecting root on android) on an unrooted FP6? For me it always says “Detected Magic Mount”, even if I flash back the stock boot.img and init_boot.img.
But I don’t know if that’s because of some traces of previous rooting attempts or a false positive.
I get the same on stock unrooted and locked bootloader.
1 Like
Update is available here after rebooting my phone. I managed to root my FP, will I lose root when I install this update?
I moved your post here.
So how did you root? Else see above
1 Like
Normally you have to install your root method into the inactive slot after installing the update but before rebooting, then you don’t lose it
1 Like
The interesting thing is I tried apatch first, it flashed the boot.img without any error.
Rebooted and checked aPatch app. It indicated “working”. Opened root check but no root. Flashed again using magisk app. Rebooted again and then I did get root. So not sure which tool actually did the trick. Both apps mention “installed” or “working”..
If you use apatch, you have to grant root permissions to your apps in the apatch app, there is not popup
1 Like
I see, so it might have been Apatch that actually did the root but since I did not provide root checker superuser perms it indicated incorrectly that there was no root? So I should Patch again and the method you mentioned earlier to keep root after installating the new update?
Update: I think it was actually Magisk who rooted the phone:
Using Apatch and OTA
I think it doesn’t really matter which root method you use, depends on your preference
APatch is a bit more difficult to detect by banking apps etc.