Problem bootloader installing e/os

[Ullie]

Hello.

I am stuck trying to install e/Os on my fairphone 6 running android 16. I’ve used the webinstaller succesfully until I reach step 9, then I get this message:

When running adb and the fastboot command ¨flashing unlock” in the terminal, I get the message ¨waiting for any device” and am unable to go further.

In the bootloader screen on my phone it keeps saying the phone is locked…

We checked this forum and murena but we didn’t find anything that worked…

Thanks a lot!

[yvmuell]

Most likely you need to install bootloader driver when you use a windows PC

How to: ADB/Fastboot (Windows)

Platform Tools runterladen von hier Zip Ordner entpacken Entpackten Ordner öffnen, den darin enthaltenen Ordner auch öffnen In diesem Ordner: Shift+rechte Maustaste drücken und Terminal Eingabeaufforderung/Powershell öffnen Wenn das FP im Fastboot nicht erkannt wird: Kann es am Kabel oder USB Port liegen, meist ist es aber ein Fastboot Treiber Problem (unter Windows). Um den Treiber zu aktualisieren: verbinde das FP im Fastboot Modus mit dem PC, gehe zu Windows Updates, suche manuell n…

[piero-e]

Hello @Ullie, Welcome to the Fairphone users forum.

A safe guide to install /e/OS on your Fairphone

[e] because even well illustrated, the “web-installer” often don’t work, and because the install instructions provided by /e/ can be imbuvable for some new users and can lead to errors. Here is a safe guide to install /e/OS we will take the Fairphone 6 as example, Expand to see the guide : Feel free to ask if you still encountred issue. or want i made some corrections / additions you may also be interested by : A clear guide to Upgrade your /e/OS to a new Android major version without l…

[Ullie]

Thank you for your answer, but I am not on a windows pc, but on a linux (zorin 18) pc.

[piero-e]

@Ullie

¨waiting for any device”

is the device in Bootloader mode ?

do you use a real Data capable USB cable ?

[Ullie]

Yes, it is in bootloader mode and I am using a data cable.

[piero-e]

@piero-e

if not properly "installed in your path” as explained in Installing adb and fastboot on macOS and Linux PC,

simply add ./ at the beginning of all your adb or fastboot commands,

will use the version included into the relative folder (the latest you downloaded) instead of the one installed on your system (that can be outdated)

like recommended in this guide :

@piero-e

if you have a Linux Computer :

• download the “platform-tools for Linux”,
• just extract the .ZIP, not more.

open the newly created “platform-tools” folder in your file manager, then

• Use the right clic of your mouse, and choose "open a terminal in this folder").

you will get something like :

[Ullie]

Thank you for all the help! I’m so happy people are here to contribute ideas. Next weekend, I will try to follow the steps of the safe guide you send. I’ll let you know if it worked out!

Have a nice evening!

[Ullie]

Thank you. I have managed to install e/OS now with this guide. I was hesitant to try this at first, because it felt a bit intimidating to me. Apparently the trick is not to start using online installer and when it gets stuck, switch to using the terminal with adb and fastboot.
Now my only question is if it would be safe to relock the bootloader. The SPL of Android 16 that was previously installed is february 5 2026. The SPL of e/OS is newer (march 5 2026), but this build is based on Android 15. So I am not sure if that would cause any problem.

[Lidwien]

./fastboot flashing get_unlock_ability

if the return is 1
→ you will be able to unlock

if the return is 0
→ you will not be able to unlock now,

[yvmuell]

@Ullie

The SPL of Android 16 that was previously installed is february 5 2026. The SPL of e/OS is newer (march 5 2026), but this build is based on Android 15. So I am not sure if that would cause any problem.

The Android Version isnt relevant in this case just the SPL and as its newer (ssme should be sufficient as well) there should be no issues.

[Ullie]

Is there a difference between “Android security update” (my phone now says it is 1 March 2026) and “Vendor security patch level” (my phone says it is 5 december 2025)? And is it still safe to relock the bootloader now, since the SPL of Android 16 that was previously running on my phone was 2 february 2026?
Sorry for asking again, but I really don’t want to brick this phone.

[yvmuell]

See Lidwiens post, if its 0 better dont lock. Re-install, dont boot into system, recheck as per Lidwiens advice and lock if 1.

[Ullie]

YES! Thank you! It worked and my phone has started into e/OS.