I have been having no luck with fastboot flashing unlock step during my attempt at flashing iodeOS on FP6 with /e/os preinstalled. I did not need to retrieve a code from FP to enable OEM unlocking. Updated the device to /e/os 3.4 which supposedly has the “open source device tree”
OEM unlock done
Adb activation shows the device serial number in consol
Adb reboot bootloader switches the device into fastboot mode, however device state reads “unlocked”
Fastboot flashing unlock does not trigger anything, device remains in fastboot mode
Consol reads “waiting any device”
Any idea how to clear the fastboot flashing unlock stage?
This seems to already be unlocked then? I do note in our documentation you need to unlock the “critical” partition as well: fastboot flashing unlock_critical. Here is the documentation: ota / ota · GitLab
Can you report what fastboot get_unlock_ability returns? I can’t recall if you need to add flashing to this or not.
OK so this seems to match the FP5 user with a similiar issue. I can’t understand how you had unlocked the devices before installing iodéOS if get_unlock_ability was 0? Any insights there would help for “post mortem” but unfortunately if it is truly unlockable and it doesn’t boot then it is not something we can solve… it may need warranty service?
Note that if a device fails to boot ??5-6?? times successively it should revert to the “other slot” (prior installation). Let’s hope that would happen, but possibly the install process wiped both A and B slots?
OK, just to clarify. I have not been able to get past fastboot flashing unlock. Therefore, I have not able to install iodeOS yet. When I am in fastboot mode, fastboot flashing get_unlock_ability also returns I think I will read through a bit through the FP forums as well…
Update: it has taken a while and a few attempts but was able to flash iodeOS on my FP6. The initial problem was my windows machine was missing some adb and LeMobile driver updates apparently. They were pending under optional updates and once installed I was able to unlock the bootloader. However, I soft bricked the device couple of times when I tried to relock the bootloader after flashing iodeOS. This was the warning on the device after flash was completed: ( wording may not be exact!) “if you relock the bootloader you won’t be able to run a custom os on this device” soi left the bootloader unlocked.
In my last attempt, I did not select to relock the bootloader and device booted to IodeOS. However, it seems I have a couple of apps already that do not work as expected. (ProtonMail and Bitwarden) Protonmail simply crashes and I can’t seem to get a prompt for 2FA for Bitwarden. For now, back to my Pixel 6a.
Will iodeOS be available at some point for Fairphone6 with bootloader relocking functionality?
OK thank you for clarifying. The bootloader should be able to be relocked, but after doing so you will need to perform a “Factory Reset” from Recovery. This regression is serious but we don’t have a solution for it yet (it also is affecting the FP4).
The way users have ended with a hard lock is if “Allow OEM Unlocking” from Developer Options is not enabled, and then they lock the device, and then it doesn’t boot. With that combination, the device can’t be unlocked but can’t boot.
So if you make sure that option is set before attempting to lock, you should be able to lock it, and then if it fails to boot go to Recovery and “factory reset”, after which I think it will boot (and still be locked). If you are willing to report back on that process it would be helpful. But again please please MAKE SURE that you have “Allow OEM Unlocking” enabled in Developer Options before attempting any lock of the device!!
About Bitwarden and Protonmail, please start new threads. Both should be working fine.
Unfortunately, this did not work for me. First I tried locking the bootloader right away via fastboot lock. The bootloader locked , phone did not boot and would not even go to recovery. I reflashed IodeOS and tried again, the same result. I think I will just wait for a solution while using my pixel 6a with a locked bootloader. By the way, I have been able to experiment and troubleshoot with all this using brave’s chatbot. Otherwise, I would have bricked the phone already I suspect
I still think you were hitting rollback protection in this case. The newer v7.2 builds are now available. If you have NOT installed the newest FPOS Feb patch, then you should be able to install iodéOS and relock the bootloader. But please please make sure in “Developer Options” you ensure “Allow OEM Unlocking” is enabled. This way if you hit a no-boot situation after locking you can safely unlock and try again.
