Its rare but this can indeed happen when there are serious issues and it can always happen that rollout is delayed for a provider. And VF DE currently is always behind.
1 Like
ahh i see, thanks for the clarification!
Iām trying to root using magisk on 122. Bootloader is unlocked but boot.img patched flashes fine but magisk does not detect patch. I think your going to tell me to patch with apatch and then magisk will work and I can uninstall apatch. Is that the only way still on 122?
Also wondering how anykernel helps or works, not familiar with anykernel3.
Patch init_boot.img instead of boot.img and flash that file. I would not recommend to flash with Patch first and after that flash with Magisk. That will create all kinds of issues when you want to install OTA updates.
I also had to unlock critical but since your flash with just the bootloader seemed to work ( I got an error) maybe that is not required.
Yeah I finally got it. Magisk was patching the file but the patched labeled file was not showing up. Once I flashed the right patched init_boot.img I got root with magisk via direct install (assuming thatās what your referring to above). I know about the update process, disable, update, no reboot and re-enable root alt slot & reboot
Thanks
1 Like
Great to hear it worked! Enjoy root, one last piece of advice when it comes to OTA updates. Reboot from the OTA menu, do not reboot using the Magisk app after install to inactive slot. That have me all kinds of issues
Ok good point Iāll remember that. Thanks for the help, Iām still using apatch on my phone, you can reboot with itās menu I believe, Iāve always used magisk before. My friend wanted magisik so it was his I was working on.
Are you sure? The normal way should be vice versa. Like explained here:
It explicitly advises you NOT to boot via system update but instead via Magisk.
Interesting, last time I did that the update did not finish and lost root. When I rebooted using the āreboot nowā in OTA menu the update finished and kept root.
This is also what Kalibri advised in his reply from August 10th:
Hi,
Today my FP6 arrived. I already enabled oem unlock, but I still need to finally unlock the bootloader. As it factory-resets the phone, and I already kinda configured it, I was wondering, did anybody already managed to install Magisk via sideload or is a flash of a patched boot a requirement?
In either case, how does Magisk on the device impact the updates on a 6?
Thanks in advance.
Please read above this should have answers
Thanks, Iāll look into it while I use the fp stock. When I get to annoyed with all google junk and ads, itāll be the time to reinstall. (I suspect that would be a task for this afternoon 
, when it rains and I canāt paint the house)
The main reason would be to install minminguard, a great add-block lsposed module. (Root for real backups would be a great bonus)
2 Likes
Ok, Iām doing something wrong trying to install Magisk 29.
Iām on the 122 image, itās in slot b (105 is in a), patched init_boot.img, flashed it and after reboot Iām back at the bootloader (refuses to boot OS).
When I flash stock boot.img folowed by patched init_boot.img, same result.
When I flash patched init_boot.img folowed by stock.img Iām in the image, but no Magisk.
What am I doing wrong?
Edit: PEBKAC
init_boot needs fo be flashed with the patched init_boot.img, not bootā¦ Magisk is installed. (yeah)
1 Like
Hello. Iām experimenting with root on a Fairphone 6. Iām using APatch. I had installed it with FP6.QREL.15.122.0 for which a full factory image is available for download.
Now Iām trying to get root for the new OTA update, FP6.QREL.15.148.0, but I couldnāt find an image for download.
Installing the OTA was not possible while boot.img was patched by APatch. Only after I flashed the original boot.img from FP6.QREL.15.122.0 installing the OTA update worked. But as a result, I no longer have root.
How can I get it back? Should I re-flash the previous boot-patched.img into the inactive slot (which has the previous version), then activate that slot, boot from that slot and activate root, and use that to extract the newer boot.img from the other slot? Then patch that, flash it the to inactive slot, then activate and boot that newer slot?
most you post here, the general on how to OTA update is described above
the idea I posted 2 hours ago didnāt work. I just tried. If I flash again the apatch patched boot.img from 122 into the inactive slot, then set that slot active and boot, I get a bootloop, it doesnāt boot up. I was able to recover, keyboard command power + volume down, used fastboot āset-active={other slot}, and I get back into the latest system.
Does Fairphone usually release a full factory image for every software version?
Hi all,
āfastboot bootā is now available with release FP6.QREL.15.148.0. Thank you for your patience!
Regards
Luca
1 Like
Unfortunately this release, like all other updates before, is not available to every FP6 users. All the Vodafone users seem to blocked from any update.
Kindly dont use this topic here to discuss the VF issue