Hi,
I unlocked my bootloader as described for FP5 successfully. The bootloader says unocked.
While trying to boot from a connected PC via
adb reboot bootloader
fastboot boot magisk_patched_boot.img
I get the message, that the boot failed because the device says
“unknown comand”
There was an equal problem with Fairphone 4 devices some years ago but the problem came up with /e/ and not with FairphoneOS.
Has anyone this Problem, too or an easy work-around?
Thanks in advance
Julric
It may be, that the command fastboot boot is not supported on FP5. In this case it can be possible to use fastboot flash instead. But i can not guarantee that it will work. Be ready to reflash if things goes wrong.
Normally a rather bad idea when rooting
I used apatch and fastboot boot also didn’t work for the same reason
but fastboot flash boot worked like it should
Thanks for the answers!
I want to provide You with some more information:
I downloaded the package from Fairphone (FP6.QREL.15.91.0), extracted the boot,img, copied it to the FP6, patched the file with magisk and copied it back to my computer. (developer options activated, device unlocked(_critical), adb active:
adb reboot bootloader
fastboot boot magisk_patched_boot.img
downloading 'boot.img'...
OKAY [ 2.571s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.571s
doing it by fastboot flash boot (or boot_a or boot_b) magisk_patched_boot.img
and fastboot reboot afterwards gives no success: device boots, but in magisk app ist just says
installed: not available
zygisk: no
ramdisk: yes
so I am not able to patch the device (which shouldn’t be necessary when flashing a patched boot.img) - there is still no root.
Today I tried something new:
I took the complete installation-package, extracted it, replaced the original boot.img with my magisk_patched_boot.img, corrected the sha256sum for the boot.img and made a complete factory reset as fairphone describes. Everything successful, but still no root-access.
Has anyone an idea, what goes wrong?
Is there a problem with magisk as root-tool?
Do I forget something else to do?
Thanks in advance
Julric
Just linking the instructions working since the FP4 for reference
Hi Yvonne,
that is exact, what I did and what I described!
So my question: what changed at FP6, that there is no rooting along the known way possible?
Android 15?
~Julric
@lucaweiss could you probably shed some light on this topic? Does fastboot boot really not work/exist?
Right now it’s not available, it was missed to be enabled in the bootloader. Hopefully a future update soon will enable “fastboot boot”!
Maybe @Kalibri could provide their patched boot.img?
I mean I did the exact same thing, just with apatch instead of magisk. If I patch it with apatch and flash it, root works for me. Should be the same for everyone.
But I haven’t tried magisk
Will it be possible to root the FP6? Yes or No?
I didn’t find any announcements about it.
I already own a FP3. Back then I expected to be able to root it, but it wasn’t possible, at least not right from the beginning.
I then found some announcements that the FP3 will be rootable after some future updates, it was planned to make it possible.
So I started using my non-root FP3. Later it was made possible to root the FP3, but too late for me 
Rooting the phone would have required to backup the entire phone, which isn’t possible with a nonrooted phone. So I never rooted it, because I was afraid of the backup and restoration procedure. I didn’t want to do an incomplete backup.
Now I ordered the new FP6, and I wonder if I will be able to root it before I start using it. And I’m afraid that it will be the same as with FP3 back then, shortly after its release date.
Please read above. For now the fastboot boot command isnt working and fastboot flash will cause you issues during updates.
I have read about fastboot issues. But to me it isn’t obvious that it means that it isn’t possible to root the FP6.
Also, questions remain.
Is this just a bug? Or is this a feature not provided yet (as it was with FP3)?
Will this issue fixed soon (as I would expect with a bug. Like, maybe someone from dev just forgot to enable a checkbox or set an option before compiling to enable fastboot)?
Or will it take a little bit longer (that’s what I would expect if rooting still needs to be implemented)?
Have you read it? Rooting is possible with apatch.
Answered already a few posts above yours.
What do you think when this might get fixed in an update? This really doesn’t sound like a big deal to do.
But I don’t know about the FP update roadmap, including which other fixes and todos are in the pipeline.
Is this merely a matter of days or of weeks or longer?
Definitely at least a few weeks, the process for releasing Android updates is quite slow due to all the tests and certifications. I hope that the patch will be in the update after the upcoming one.
Hello! I have a shiny new Fairphone 6 running /e/OS 3.0.2, and I’m having trouble rooting it with Magisk.
I’ve been using rooted custom ROMs for a while now, so this procedure is very familiar to me:
1 - Extract the boot.img file from the installation file (in my case, here)
2 - Download the latest version of Magisk. Currently 29.0 is the most recent stable version, and the latest pre-release version is 30.1. I tried using each one on separate runs with the same result.
3 - Install Magisk on the FP6 and use it to patch boot.img. Put the patched image on my computer (laptop running Ubuntu, if it matters).
4 - Reboot to bootloader, run ‘fastboot flash boot [path to patched boot.img]’. The process appears to go fine, taking under a second.
5 - Reboot to system. Magisk and Root Checker both report no root.
Am I doing something wrong here? Do I just need to wait for Magisk to be updated for this more recent OS?
Any input appreciated! Thanks in advance!
Is your bootloader unlocked?
I 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.