FP4 Root Access is possible, maybe a bit risky

OK, let’s try to figure this out:

  • If you do a factory reset, do you have working wifi?
  • Did you flash the A.067 boot instead of booting from it? (don’t!)
  • Are you still on A.081?

Without any more information, I would suggest:

  • Do another factory reset
  • Got wifi? Stop there for now
  • If not and your build number matches with one on the kernel page flash that img.
  • Otherwise try one of the stock images I uploaded, A.081 could be boot_a :thinking:

Good luck :crossed_fingers:

Oh and changing the boot slot if you booted the other one successfully won’t work, probably Rollback-Protection

2 Likes

Thanks, Hirnsushi!
I just did again a factory reset.

Still no wifi, no sound, no phonecalls

Yes, according to rar0 instructions I flashed the image. After I renamed it to A.081…
I remember your root post of warning not to flash, but I thought, rar0‘s image was different and ok to flash.
I think I flashed all three images from FP homepage:(

Still build A.081

Have you tried flashing one of the images I uploaded?
Those are the boot_a and boot_b my device shipped with and at least one of them is a build between A.067 and A.091, so may well be your A.081.

Or you can tell me the security patch level of your A.081 build (Settings->About phone->Android version->Android security update) and I can tell you which one it should be.

yes, I did. I am trying again. I used 067 for root with Magisk

Please try boot_a from my upload, that’s patch level September.

A.067 shouldn’t be used for anything apart from temporarily booting and using that to install Magisk. That build is ancient, patch level July, I’m pretty sure no device shipped with that.
When I wrote my initial instructions, that was the only image Fairphone had made available.

Android Update 5.th September
Build Fp4.FP3I.A.081.20211026

That should match the boot_a I uploaded. What happens if you flash that?
If it doesn’t work, make sure it actually gets flashed to the right slot (the slot might be chosen based on suffix :thinking: ) either rename it to your current slot or in fastboot do:

$ fastboot getvar current-slot
$ fastboot flash boot_[your_slot] path/to/boot_a.img
4 Likes

I cant believe it! it worked! I did it the same way yesterday…
oh thank you so much!!!
sound works, wifi works, it believe the rest of it, too!

5 Likes

:tada:
Nicely done :metal: :smiley:
Now you just have to wait for the update again… :smirk:

4 Likes

Maybe you can sync your Slots…

I used it on a OPO6T, but the script is manufacturer independent

Pre-install instructions

In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional.

To do this, sideload the copy-partitions-20210323_1922.zip package by doing the following:

    Download the copy-partitions-20210323_1922.zip file from here.
    Sideload the copy-partitions-20210323_1922.zip package:
        On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
        On the host machine, sideload the package using: adb sideload copy-partitions-20210323_1922.zip
    info_outline
    Note: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz, but isn’t signed with LineageOS’s official key, and therefore when it is sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
    Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”

https://wiki.lineageos.org/devices/fajita/install#pre-install-instructions

Good work folks !
:sunglasses:

I tried that, didn’t work. It is flashable from the OEM recovery and the script will execute just fine, but the other slot won’t be bootable.
Probably something to do with hashes still wrong for Verified Boot, but I really don’t know anything about how that works exactly.

As this is turning waaay OT here, could someone with privileges move the last 10 posts or so over to the FP4 Root Access is possible, maybe a bit risky topic maybe :thinking: :pray:

2 Likes

Unfortunately update again didn’t work. But, naaaa, I won‘t try it again today. I wanna enjoy my working phone for a while. Maybe I just wait for twrp and e-rom.

Once again, thanks folks!

Didn’t you get a update notification or did it fail during the update process and if so at what point?
Have you rerooted your phone before updating?
There has to be a way to get this working, what are we missing here :thinking:

1 Like

No, not yet rooted.
build no. still the same A.081…
all google apps activated
download: ok
installation Error

Huh, interesting… is that the same error you had before?
Maybe there’s still some modification to system files left somehow. I wouldn’t now how, but who knows :thinking:
OK, here’s a crazy idea:

  • Install the Magisk app
  • Boot (not flash) your prerooted boot.img
  • Perform a Magisk uninstall in the Magisk app

That shouldn’t work, a factory reset should have purged all the remnants of Magisk off of /data, but hey, worth a shot.

Apart from that, could Titanium Backup have messed this up somehow, I don’t really know how it works these days, haven’t used it in almost a decade…

Third option, your other boot slot could be tainted, maybe because you flashed a wrong boot.img to it at some point. The updater usually flashes to the unused slot, maybe then, the failure gets triggered.
So try flashing that boot_a.img you used to get your phone working again to the other slot.

1 Like

Have moved several posts here as proposed.

2 Likes

I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)

https://code.fairphone.com/projects/fairphone-4-kernel.html

https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img

And that works perfectly, that’s my daily driving phone, and no problems :wink:

4 Likes

Hey!
I tried to root my FP4 on /e/os using Magisk.
It worked using the default stock rom on FP4, so rooting the device works.
However, using /e/os Magisk just crashes when I try to modify the boot.img using the install button in Magisk.

This happens with v23 and the canary build. Does anyone have an idea how to fix it? Could it be any permission issue?

Cheers!

I just uploaded a Magisk patched version of the /e/ boot.img here.

Could you please try to flash that in fastboot

$ fastboot flash boot_a boot_magisk_e.img
$ fastboot flash boot_b boot_magisk_e.img

I hope you have your important stuff backed up from your phone, hic sunt dracones :smirk:

3 Likes