e/OS/ install gets stuck in bootloader

[MichaelK]

I’m trying to install e/OS/ on top of a new Fairphone 6.

No SIM card added to the FP so far, only WiFi.

Host OS is Windows 11 Prof. with all the latest patches applied.

I tried the Web Installer and failed at a certain point. I tried manual install and failed at the same point. I tried several different USB cables - again failing.

USB debugging and OEM unlock are both set active.

Any which way I try to install, whenever the FP boots into Boot loader no USB connection is possible. I cannot see my FP in Windows Systray, even worse in device manager I detect a USB device named Android without any driver.

This changes when I start the FP from Boot loader into the installed Google Android.

As soon as this happens, the Android device gets replaced by a working Fairphone device.

I can connect using commandline adb tools, however only when FP is not in boot loader mode.

Did someone face the same issue?

[piero]

Hello @MichaelK,Welcome to the /e/ users forum.

@MichaelK

I’m trying to install e/OS/ on top of a new Fairphone 6.

Did someone face the same issue?

yes numerous …

@piero

according to Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”

If you plan to relock the bootloader after the installlation

(not mandatoty, only available with Official version, why relocking ?)
Most important thing to take care about is the “android Security Patch Level” in the already installed Operating System on your device before you start the install process.

It must be OLDER than the “android Security Patch Level” included in the /e/OS build you want to install, otherwise you risk to change your device into Brick.

• You will find this information about stock OS on the device :

settings --> about phone --> android version 15 --> android security update

.

@piero

What could go wrong

[Solved] Windows does not see my phone in Fastboot mode because needed drivers are not correctly installed

[GabrielT]

@MichaelK

never the FP boots into Boot loader no USB connection is possible. I cannot see my FP in Windows Systray, even worse in device manager I detect a USB device named Android without any driver.

This changes when I start the FP from Boot loader into the installed Google Android.

If you are installing from a Windows PC, look into the optional updates of Windows update, the needed fastboot driver might be offered to download there. If not, go to fairphone website and download the dedicated USB driver for that phone.

Universal ADB Drivers

[MichaelK]

thanks for the hint, however as I said, all the latest patches have been applied, even all labeled optional and drivers.

My fault, however I didn’t mention, that Universal ADB Drivers have been installed as one of my first activities

[aibd]

@MichaelK

I cannot see my FP in Windows Systray, even worse in device manager I detect a USB device named Android without any driver.

In light of the post above, please can you explain this in different words.

In Device manager as you switch from regular phone to Bootloader / Fastboot what is the actual change you observe?

The typical problem (fix linked above) is that in Fastboot mode the phone shows as Problem device.

[MichaelK]

well, somewhere on your desktop, there’re a couple of symbols called systray. For example there’s an icon for WiFi, battery status, etc. And there’s an icon listing connected USB devices whenever you click on it. FP in boot loader mode, will not be listed.

Checking Control Panel - Device Manager shows an Android USB device with a driver issue.

The ADB Driver package has been installed. All Android related drivers from Settings - Update have been installed.

I think there’s some interference between any of the android drivers and something else installed on my laptop.

Additional:

Sometime yesterday I installed Android Studio, because of a post stating that there’s an option for updating android drivers. After uninstalling Android Studio a few minutes ago, in boot loader mode my FP shows up in Systray and without issues in device manager (Android device - Android Bootloader Interface). This seems to be part of the interferences.

However my FP cannot be found in commandline adb devices. (repair of Universal ADB Driver package has been done)

[aibd]

@MichaelK

shows an Android USB device with a driver issue.

I am sorry but it seems you are reading Windows advice (I cannot account for veracity of this, as different Windows installs can have different levels of lockdown to other sources / platforms) but you describe no reaction to my suggestion which among other things includes

@aibd

[1] GIF from Fairphone support:

[MichaelK]

Good morning

thank you all for all your ideas.

However ALL drivers have been installed.

As of now, I assume that there is some interference with an other active process, or a driver incompatibility within Windows 11.

The screen shot aibd provided is one of a Windows 10 system. It looks like Windows 11, however internal processing might be different.

Is there any experience with installing e/OS/ from a Windows 11 system?

Next steps:

I will setup up a fresh Windows 11 without any additional applications installed.

This system will be used for my next attemps.

If not successful, I will install a fresh Windows 10 without any additional applications and try based on this system.

Michael

[aibd]

@MichaelK

The screen shot aibd provided is one of a Windows 10 system

I am apologetic but did you actually read the multi times linked [Solved] Windows does not see my phone in Fastboot mode?

There are a number of approaches including a fresh start with drivers. The gif approach does at least include the idea that you might be better directed to Google flavoured drivers rather than specific Fairphone. Fairphone 6 additionally is very new. Continual updating wrong drivers does not seem the way to go. The provision of Fairphone Drivers is a little “unusual”, and the specific difficulty hard to see from this distance. I do not think a new Windows install is required.

However in light of your future anticipated success I will be happy to include anything you learn wrt Windows 11.

Good luck.

Edit. Here is a Windows drivers success story Sdkmanager / adb install via Raspberry Pi OS? - #4 by beta-L-user.

[aibd]

Alternatively …

@MichaelK

However ALL drivers have been installed.

Is it then the case that the Device manager situation as

@aibd

Fastboot mode the phone shows as Problem device.

no longer exists?

is your difficulty still the OP “e/OS/ install gets stuck in bootloader”?

[piero]

@MichaelK

The ADB Driver package has been installed

adb is not needed for that device, but fastboot…

[MichaelK]

Hello

Thanks for all your valuable hints.

Eventually e/OS/ has been successfully installed now.

Please see my description what I needed to do:

On top my first laptop 2 Android related applications had been installed:

Google Android Studio and Visual Studio Community 2022 (Android Workload).

This has been the enviroment for my very first post.

So I installed a fresh Windows 11 Prof. laptop with both applications installed on top + Universal ADB Drivers. No additional applications installed.

I failed to install e/OS/ as described in my very first post.

So I reinstalled this laptop, however only Visual Studio Community 2022 (Android Workload) + Universal ADB Drivers installed on top.

A very different behaviour could be observed.

I followed the documentation for Web Installer.

However in Developer Options “Automatic System Updates” need to be disabled.

Web Installer connected to my Fairphone 6 as described in e Foundation document including Download phase and boot into Boot loader. .

My FP6 booted into boot loader mode. At that point I needed to install 3 drivers from Windows settings - Updates:

(1) Google - Android Bootloader Interface

(2) LeMobile - Android Composite ADB interface

(3) LeMobile - Android ADB Interface

In Device Manager my FP6 showed up as Kedacom USB Device - Android Bootloader Interface

The rest of the setup happened as documented.

And finally e/OS/ has beeen successfully installed.

Michael