Installing E/OS on FP5 with Web Installer Fails "Error on step: connect-bootloader

/e/OS Devices Fairphone
,
41

you mean like in the past century ? Lol

.

more seriously :
from the Official instructions we can see

Unlocking the bootloader

use built-in windows command-prompt

Installing /e/OS

Tip: For Windows users, we advise to use Git Bash. For more info about Downloads and Installation see Official Documentation

42

Unfortunately i need it for my work.

I’m trying to unlock the bootloader but when running : fastboot flashing unlock
the response is waiting for any device.
What have i done wrong ?

43

Windows + What have i done wrong = Drivers

44

I installed adb, fastboot and gitbash

45

Good … here was a short answer My computer cannot find my CMF Phone 1 on fastboot - #2 by aibd.

Slightly longer answer: /e/os web installer cannot connect to Fairphone 3 in Fastboot mode - #2 by aibd

46

boot the device in bootloader / fastboot mode

open the windows device manager for monitoring, the presence of a :warning:

from the windows main menu, launch a windows update → enable including optionnal updates → driver update

47

I followed the steps but at the end i locked the bootloader and when my phone try ta start again i see the e of murena for a second and it boots back in the bootloader, status locked

48

so using the buttons you cannot boot normal system mode (start) nor recovery mode ?

49

no it comes back to bootloader, i’m running ```
chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh

51

was it relocked by the script ? or by your intervention ?

in windows command prompt :
fastboot flashing lock_critical
reboot to bootloader
fastboot flashing lock

.

bootloader have to be unlocked to run

in Git Bash :
chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh

52

Yes i don’t know why the script didn’t finished so i had to unlock it again and launch it again but i finally succeded !
Merci !

1 Like
53

Welcome to the /e/ users community !

check all the app permissions, you could be surprised…

54

There’s a big difference.
I love the «mur de la honte»

55

Ok - linux user here, and installed on Fairphone 5 the latest /e/os/ march 2025 patch level yesteray, painfully! . . .

Only a few things stood out: this is @manoj perhaps good to mention in the main FP5 guide page.

  1. I did not know that FP5 does not support this and i got stuck on the same area this post’s OP did. (/e/OS Installer) and i got to this page from the first link on this page (Info about Fairphone FP5 - FP5). I wonder what @piero mentioned on this page, if it is not supported, maybe the main FP5 page should have a message on it until its fixed, or not have that link there at all. Or if it is OS / browser specific then that mentioned there as well.
  2. The downloaded latest zip file form the march 2025 fp5 official contained a fastboot which i thought was problematic (maybe it wasnt) but i replaced that fastboot (2.3mb roughly) with a newer version of the fastboot (2.7mb roughly) from the latest android SDK sources. My real problem was probably #3 below.
  3. For the life of me, i could not get the script to run, i edited the script to use android SDK version’s fastboot mentioned above because the android SDK version was giving me the correct outputs for ./fastboot devices and the script was silently stuck at detecting device… tens of times. and what finally worked after half a day of wrestling with it was stupendously… sudo SU… then run the script as root. I had tried sudo chmod… running the script and it would not budge…

This “only running as root works but sudo does not” maybe should be mentioned in the FP5 commandline install guide page. And i understand maybe it has something to do with me… or something… just so that we are clear, i am on tuxedo computer’s hardware with their official tuxedo OS and no customizations (no ricing / no kernel upgrades / no cutting edge packages / no external sources… no nothing… just the factory tux os (its ubunti base) with KDE).
Unsure if this has anything to do with it. Interesting to know if someone else ran into this issue.

Kind regards, and thanks for all the help everyone on forums…

PS: after running as root, there was 0 issues. . . .

1 Like
57

The easy-installer is depreacated. As @piero stated e/OS/installer (web) has to be used.

With easy-installer I don’t recall that FP5 was supported, but with e/OS/installer it works. Not sure what you meant with

58

Where one has a difficulty recognising an Android device and an issue with requiring root on Linux this page Set up a device for development provides an answer. I will quote the whole relevant section.

Ubuntu Linux: Set up the following:

  • Each user that wants to use ADB needs to be in the plugdev group. If you see an error message that says you’re not in the plugdev group, add yourself to it using the following command:
sudo usermod -aG plugdev $LOGNAME

Groups only update on login, so you must log out for this change to take effect. When you log back in, you can use id to check that you’re in the plugdev group.

  • The system needs to have udev rules installed that cover the device. The android-sdk-platform-tools-common package contains a community-maintained default set of udev rules for Android devices. To install it, use the following command:
apt-get install android-sdk-platform-tools-common

/quote

If you “system install” platform-tools [1], notice how your package manager will install android-sdk-platform-tools-common as requires or depends (check for example this package page https://ubuntu.pkgs.org/24.10/ubuntu-universe-arm64/android-sdk-platform-tools_28.0.2+10+nmu1_arm64.deb.html).

[1] Edit Note that system install is not recommended in this /e/ documentation page Installing adb and fastboot on a Linux PC, this reason is given

Caution: The default adb installation on OS like Ubuntu can be outdated and can cause errors. We would recommend that linux distribution users ensure they use the installation process given here.

59

The easy-installer is depreacated. As @piero stated e/OS/installer (web) has to be used.

i did also try web, that didnt work, finally command line worked.