If I understand correctly, I shouldn’t have booted in Murena OS after critical lock? In the FP “how to lock and unlock bootloader” article this is mentioned. I didn’t see this detail earlier because I followed your instructions. (That’s my own responsibility.) It mentions:
“6. Hold the Volume down button immediately as your Fairphone reboots to return to fastboot mode.”
Is it possible to add this piece of information to your guide?
An other piece of feedback is about the first part of your guide. It mentions: “Your Stock OS Android version, must be the latest available relative to the /e/OS build you want to install → not higher ! (this don’t apply to Fairphone devices)”
It’s multi interpretable that it says that this doesn’t apply to fairphone devices. At first I even thought that the rollback warning does not apply to fairphones.
Overall I like your guide way better than the official ones. So thank you for your work.
Back to my problem. You don’t have a device to test with. I get it. But does this mean you have got an idea? Can you talk me trough it? (This FP5 is my test device. So what’s the worst that can happen ) Point is, I wanna learn from my mistakes. Otherwise I don’t know if I dare to install Murena again on my own.
Worst is relocking with an older “Android Security Patch”, that brick your device and you must send it to “Cordon Electronic” the Fairphone partner who will restore you device for 60€ .
Also relocking when “unlock_ability” return 0 will let your device working but make it nomore unlockable.
Relocking with a 4 days older “Android Security Patch” will make your device unbootable but unlocking again will save the situation.
Yes, Unlock critical if possible and restart from scratch..
FAILED (remote: ‘Flashing Unlock is not allowed’)
fastboot: error: Command failed
Flashing to FPOS is not possible with locked critical. Unlock critical is not possible with unlock ability = 0. And locking the bootloader completely makes the device no more unlockable. That will make me even more stuck than the current situation?
So I’m trying to find other solutions:
Leo (Brave) advises to check out fastboot d mode. But commands don’t work here:
“With that out of the way, download the boot.img and the Magisk.apk (for others trying this on a different ROM, please use the corresponding boot.img for that ROM!) from those two links to your PC…
…and enable ADB debugging on your FP4 if you haven’t already.
Install the Magisk app by either running adb install Magisk-v24.3.apk or transferring the .apk to your phone
adb reboot bootloader and fastboot boot calyx-3.3.2_magisk_boot.img should boot you into a Magisk enabled Calyx
adb shell su -c 'resetprop ro.boot.flash.locked 1' should show a prompt on your phone screen to grant root privileges…
Change OEM unlocking to on in Developer options.
adb reboot bootloader and most importantly check if fastboot flashing get_unlock_ability actually returns 1
Pray to the ancient gods
fastboot flashing lock"
Can someone help me to rewrite the following command for /e/os?
fastboot boot calyx-3.3.2_magisk_boot.img
Last option that I can think of is asking FP helpdesk for reinstalling FPOS. If someone has other possible solutions please let me know.
Oke, I managed to toggle the oem unlocking button with Magisk. I checked get unlock ability –> 1. So I locked the bootloader. After that I got the “corrupt” screen. I probably had to unlock critical first? Anyway I can still connect to the phone:
I’m gonna try to start from scratch, because the phone wont boot into Murena anymore. I tried several things, like reinstalling murena. That didn’t work. Then I selected recovery mode? And out of the blue the phone restarted. I could toggle oem unlocking and USB debugging. Unlock ability was still 1. So locking the bootloader worked.
Long story short. I don’t know how I’ve managed it exactly. But I’m able to boot into Murena with a locked bootloader!
) Point is, I wanna learn from my mistakes. Otherwise I don’t know if I dare to install Murena again on my own.
Pray to the ancient gods 