Ways to root the FP6

[yvmuell]

at the moment it seems only APatch works, just to make that clear again.
Magisk works with a different command

@Kalibri

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)

@jvds1987 do some reading in this topic here.

[Kalibri]

No, that it not true.
Magisk, APatch and KernelSU work (currently using KernelSU).
I tried all three.

@Kalibri

You just have to patch and flash init_boot instead of boot.

(For magisk)

[yvmuell]

thanks for the reminder you mentioned that before, I forgot about it

@Kalibri

You just have to patch and flash init_boot instead of boot.

[yvmuell]

Another try to summarize what is currently known reg. rooting the FP6 to add this info to the first post

fastboot boot currently does not work/exist and its unclear when/if it will be added

@lucaweiss

now it’s not available, it was missed to be enabled in the bootloader. Hopefully a future update soon will enable “fastboot boot”!

Still its possible to root the FP6 using APatch

@Switch

flashed APatch today (uses the exact same installation-procedure as Magisk) and it worked right away. It supports Magisk modules and has more capabilities in general, so maybe give it a shot!? Apps won’t ask for root access here, so you have to manually enable it for each app in the APatch Manager.

Ways to root the FP6 (while [fastboot boot] is not available

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.

Those still wanting to use Magisk

@Kalibri

magisk (as well as KSU) also works on FP6. You just have to patch and flash init_boot instead of boot.

In the past flashing boot with Magisk prevented a smooth OTA route,

@Kalibri

install your root method into the inactive slot after installing the update but before rebooting, then you don’t lose it

@Kalibri did you test this after flashing init_boot using Magisk?

[Kalibri]

@yvmuell

@Kalibri did you test this after flashing init_boot using Magisk?

No, just with KernelSU

[Kalibri]

@Kalibri

Detected Magic Mount

Interestingly enough, I don’t get this anymore after the new update
So it doesn’t detect root anymore
My banking app still doesn’t work, bit that’s also maybe because of something else

[mike_1312]

@Kalibri

I used apatch and fastboot boot also didn’t work for the same reason
but fastboot flash boot worked like it should

@Kalibri
As you rooted your device very early after its availability on the market can you give a short feedback if you also have done android updates on your rooted device? I mean there were already two updates on my phone.
Did you face any problems doing it the regular way (deactivating the “magic” app, applying the update, re-installing the “magic” app in inactive slot after reboot, reboot)?
Or did you have to unroot, apply the update and then had to root and flash the boot.img again?

I’m asking these questions because I’m still not familiar with Apatch. I was using Magisk only over the last years.

[Kalibri]

I did the update with KernelSU installed, had to flash the stock init_boot and boot img though (did this with the Kernel flasher app). I don’t know if this is also necessary with apatch but you will know if the installing of the update fails.
After installing the update, I had to install in the inactive slot which worked, and after a reboot, the update was installed with root.

[mike_1312]

Thanks for the feedback and confirming me that the regular way for updating and keeping root is still possible. I also had the same backup plan with reflashing the boot.img in my case with Apatch.
I’m sorry for asking, but it seems to be 4-5 years ago when I bought my still Asus Zenfone 8 (Android 11 or so). And Android in general changed a lot, in my opinion. I haven’t been aware of the current situation with bootloader, rooting etc. Because the last years there was no need to keep the “Android memory” in my brain updated. But now, as my phone comes to an end and I was dealing with the idea to replace it with an FP5 3 months ago, I started reading topics again, mainly about FP5. And then suddenly the release of FP6 appeared and I found my device for hopefully the next bunch of years. So I want to set up the phone as ideal for me as possible, also with some more work as an average user would do, but the maintenance work over lifetime is way less for me

[Kalibri]

You don’t have to say sorry for asking

[jvds1987]

Tried to install the update today but unfortunately it failed

Used Magisk to root my FP6. Should I flash the stock init_boot and boot.img and try it again?

[jvds1987]

Sorry for mixing in. Could you please explain what you mean by deactivating the “magic” app? Am I right to assume you mean Magisk? How does one deactivate the app? My install of the latest patch failed and looking for a way to fix that.

[mike_1312]

I assume that you have rooted your phone with Magisk (this is your “magic” app, I’ve done the rooting with Apatch, so this is my “magic” app) and flashing the modified init_boot.img, right?
In this case the regular way would be the following:

• open Magisk → select Uninstall Magisk and then Restore images
• open your Settings - System - Update and perform the update, do NOT reboot the phone
• open Magisk again → select Install and then Install to inactive slot (After OTA)
• now you can restart your device and check if it was successful.

[jvds1987]

I used Apatch first with boot.img, flash was successful but according to root checker I didn’t get root. Then I installed Magisk app and did it from the app. That seemed to work and gained root.

Yesterday I did the restore to “restore images” in the Matiek app, once that was done tried the update again but still no luck.

Root checker shows my phone is rooted with Magisk but I have the feeling that it actually was Apatch that did the trick but I didn’t grant super user to Rootchecker when I checked.

Could you please tell me how I should disable Apatch like you did before installing the update?

Is that “remove patch” in the Apatch app?
No reboot → install update → install Apatch to inactive slot → reboot? Or are there other steps involved?

[mike_1312]

For Apatch the procedure is the following:

• open Apatch → Uninstall → deactivate Android Patch
• open your Settings - System - Update and perform the update, do NOT reboot the phone
• open Apatch again → select the smartphone wizh arrow down symbol in the top → select Install and then Install to inactive slot (After OTA)
• reboot
• open Apatch → activate Android Patch again

[jvds1987]

The only option I see is “remove patch”

.

Not disable patch, should I do that and proceed as mentioned in your guide?

[mike_1312]

Yes, Remove AndroidPatch!
Sorry, used the wrong trasnslation. I’m not a native english speaker.

[jvds1987]

No problem at all! Appreciate all the help

[FroggyFP6]

@Kalibri

I used apatch

So I did and it brings root to the apps I need so far. Thanks for the tip ! One question, I’d like to relock the bootloader. Locking critical was OK (better than nothing but still not safe enough) but I got a bootloop when trying fastboot flashing unlock. So I had to factory flash and start over again. Did you manage a full lock, if yes, how did you ?

[mike_1312]

Check the ability to close the bootloader, before you try to close it, with this command:
fastboot flashing get_unlock_ability
Only if it returns “1” as a result it’s safe to lock the bootloader.