Hi, I wondered if anyone could point me in the right direction. I am trying to install on new FP5, Android 14, security update 5 January 2025. I’m using an Ubuntu 24.10 PC. Keep getting the following on step 9. The phone reboots to bootloader, I click connect and then get this
Error on step: connect-bootload
Cannot execute command connect bootloader
The device is not connected Failed to connect: Cannot connect Bootloader
Proposal: Check connection and that no other program is using the phone and retry.
I’ve made sure phone is not mounted, tried different cables using different computer ports. Always the same error.
FP5 is not supported by the “easy-installer”,
Try using the “/e/ web-installer” or the “open android installer”
Or better Install /e/OS on a Fairphone FP5 - “FP5”
All seemd to be going well, until I tried to re-lock it, got an error something like “Your device is corrupt. It can’t be trusted and will not boot.” and then it rebooted into bootloader but I can get no further. Can anyone help?
Thankfully “fastboot flashing unlock” and then reinstalling seem to of got my phone back. I was only sweating slightly! The question is should I try and lock it again? Bit scared now. All seems working, boots into E/OS, just get a warning about the phone being unlocked on power up.
It will probably do the same thing if you re-lock the bootloader. You might be running into the “anti-rollback” problem. It’s what happens when the security update level of the OEM Android instance is newer than the level of /e/os you’re installing. Personally I’d just leave it unlocked. It’s really not a big deal for the average user though you’ll see statements saying it’s strongly recommended to lock it.
When I checked the date on the latest e/os/ build it said 5 January 2025, I thought this meant it would be ok. In the caution section it says the android version is NOT relevant. Am I getting something confused? This is what my phone now says;
Security fixes
This /e/OS 2.8 version includes the Android security patches available as of January 2025.
However my community e-2.8-a14-xxx build has Android SPL 1 January 2025. If your update has this same date, the bootloader would still not be lockable. Edit in light of your image below.
Official builds are generally released towards the end of the release period.
Thanks, the image shows the link I used to download. I had been waiting for the latest release after buying the phone.Think I’ve got something very muddled.
Is my confusion due to “security patch” being different to “security update,” because otherwise as the dates match I have a different problem? Phone is now offering update to 2.8, does this mean that I can reasonably safely lock my phone once this update is installed? (being fully aware it will reset my phone)
Thank you, that’s absolutly bonkers mind, not really filling me with confidence. Not sure if I want to risk locking it again now knowing that the dates can’t be trusted.
I suspect there are some steps missing in the web installer instructions, as I don’t understand how it can work unless fastboot and adb are installed first.
Yes, this is what I followed in the end thanks to @piero, and I am now using e/os succesfully.
The original post and @0_xavier_0 was asking about a problem encountered at step 9 of the web installer however. Where, I don’t recall being instructed to install adb or fastboot or did I miss something?
Security fixes
. Device state is locked. Might be the issue?