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:(
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.
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.
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 ) either rename it to your current slot or in fastboot do:
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”
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.
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.
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
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
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.
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?
