FP4 Root Access is possible, maybe a bit risky

[echo1]

@H_Verweij @cortomalese

I installed Xposed, however when searching for modules it couldn’t find anything. Is there no module officially available? I didn’t knew this risks to brick a device, too.

[cortomalese]

Hi. In Magisk I have activated Zygisk, then I have installed LSposed-Zygisk release and I have all kinds of modules in LSposed app, such as GravityBox (R). AFWall+ is recognized too, or Greenify

[ccgx]

@hirnsushi

Once an OTA update arrives follow those steps:

1. In Magisk press Uninstall Magisk → “Restore Images”
2. Install OTA-update and don’t reboot
3. In Magisk select Install and choose “Install to Inactive Slot (Atfer OTA)”, reboot and have fun

As always don’t follow any of those steps without proper backups!!!11

Just to be sure: This does work with the official rom from fairphone?
currently I restore the image, install the update, do one reboot, boot from an older image and patch the current image, and reboot. patching directly after install and before reboot would save quite some time.

[hirnsushi]

It does, I’ve successfully used it with both CalyxOS and stock FPOS

[jochen0]

@hirnsushi

Depends on your distribution, but generally not a problem. You’ll need the Android platform tools for adb and fastboot, but those should be packaged already. If they don’t work without sudo you might need android-udev-rules as well.

Tried it with my present phone (HTC U11). It’s easier than expected. Both, adb and fastboot, are available as packages from ditribution.
sudo apt install adb fastboot
was all I had to do.

Connection worked on the first try. Later this year I’ll buy my Fairphone 4. Thank you!

[hirnsushi]

I’ve uploaded a boot.img for the latest FPOS release A.142 patched with Magisk 25.1 for people who want to skip the first two steps

[Smojo]

@hirnsushi

Open the Magisk app, choose direct install and reboot

Just a little add for those who might do it directly after receiving the FP4.

I got this after the first reboot after flashing the patched boot.img

After I hit OK and it rebooted, Magisk was not installed anymore. (Probably an A/B slot issue)
I reflashed it and did it on the described way. The message in the screenshot I never saw again.

So just hit cancel and follow the described way.

[Singulus]

I used the boot.img in the CalyxOS installation file (FP4-factory-22307020.zip). That zip includes a image-FP4-sq3a.220705.003.a1.zip, which contains the stock boot.img. I patched that one, booted from it and was able to direct install via Magisk app. Thanks!

[hirnsushi]

Thanks for reminding me, I should probably change the wording of those instructions to be a bit more general. And that link to the boot.img still points to the oldest one available

Glad everything worked fine for you

Edit: Updated

[hirnsushi]

I’ve uploaded a new FPOS-A.163-magisk-boot.img, patched with Magisk v25.2, for people who want to skip patching the boot.img.

[hirnsushi]

Patched FPOS-A.170-magisk-boot.img, in case someone needs it

[jochen0]

Where did you find A.170?
On Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation are only up to build A.142.

[hirnsushi]

Thankfully there are at least updated factory images available (but I just pulled the patched image directly from the phone in this case )

@hirnsushi

You can download the factory images and use the boot.img from that archive.

[jochen0]

Thank you.
If I want to use the A.170 patched by you I think I have to “direct install” that file with Magisk.
Magisk 25.1 (or 25.2) does not offer that, There is only one option available “Install” → “Select and Patch a File”. If I understand you that’s already done with the file from FP4 Root Access is possible, maybe a bit risky - #236 by hirnsushi

Now I’m stuck.

[hirnsushi]

Are you following the instructions above?

You only need to download the patched boot.img and start with the 3rd step in the instructions.
If you don’t have direct install available, have you fastboot booted a patched image?

[jochen0]

Yes, I am at point 5.

But there is no “direct install and reboot”.
In Magisk I selected “Install” (upper right corner).
Install shows
(-) Method
( ) Select and Patch a File

That’s all. Nothing like “direct install and reboot”.
It’s Magisk v25.1 (2022.6.19).

What shall I do?

If you don’t have direct install available, have you fastboot booted a patched image?

Yes, that’s what I have done.

[hirnsushi]

Sounds like you aren’t booted into a rooted enviroment …
I’ll have to check if everything’s fine with the image I uploaded, give me a second.

[jochen0]

The only reason for that was, that I could not find the boot.img for A.170.

Now I downloaded the huge FP4-FP4G-factory.zip.
The unpatched boot.img is images/boot.img, right?

Can I repeat fastboot boot boot.img with that file or does that cause damages?

[hirnsushi]

I just checked the boot.img I uploaded, and that’s working just fine. Any particular reason you are using Magisk 25.1 instead of .2? Maybe that’s causing issues, since it’s been patched with the newer version

You can absolutely boot the stock boot.img, but if you don’t patch it beforehand, all you get is the same experience as if you would have booted into your normal system.

[jochen0]

@hirnsushi

Any particular reason you are using Magisk 25.1 instead of .2? Maybe that’s causing issues, since it’s been patched with the newer version

You wrote that you patched the A.170 you provided with Magisk 25.1. That’s the only reason.
25.2 makes no difference.