I’m trying to install e/os through the installer here: /e/OS Installer
I’m going through all steps and it is getting stuck at the step where it needs to connect to my phone after a reboot. The web installer is not able to see my Fairphone 5 again. In the previous step where the OS is downloaded it could connect.
It’s saying the web installer should support Fairphone 5. So how do I get this to work?
I previously started to research the element of your error
Error: Failed to request USB device: Failed to execute `requestDevice` on `USB`: Must be handling a user gesture to show a permission request.
This looks like a permissions error within your “chromium-based” browser. I believe the error is generated as is described in the following link.
If you feel like helping others who follow, please can you give the exact browser and version used. Just my guess, you might check available updates or extensions or “less secure” variants of the browser.
However to actually install /e/OS please follow the guide above.
Edit An example of a blocker for “gesture to show permission request” would be if your browser has denied popup windows.
I don’t understand this. One of the things that makes /e/OS unique is that it’s so easy to install. It even has my device on the supported list of devices for their web installer. So according to you, this is just not true?
When I visit Install /e/OS on a Fairphone FP5 - “FP5” and choose the other option to install through command line it says: > It is advisable to flash your device only if you know what you are doing and are ok taking the associated risk.
And I don’t know what I’m doing. That’s why I choose the web installer option.
In a previous step it does connect to my device. So I don’t know why the second time it would be a permission issue. Why do you think that?
I’m using Vivaldi Browser:
Version
7.9.3970.47 (Official Build) (arm64)
Chromium Version
146.0.7680.182
Extended Stable channel (may also include additional security patches)
Channel
Official Build
Platform / OS
macOS Version 26.4 (Build 25E246)
Use our /e/OS Installer
The /e/OS Installer is a web application which helps users install /e/OS on supported devices in just a few clicks! It works with browsers supporting WebUSB.
Thank you for showing other potential users a possible “unsupported” browser. My uneducated guess is that Vivaldi + Mac [1] is a little unlikely to release required permissions.
OK, forgive my initial jaded response, but “so easy to install” is quite subjective.
Your problem: It seems your browser is not fully supporting WebUSB. Edit, or from later info, USB cable issue.
Well different things happen in the installer. We can tell from your image that your device was identified by an adb command because a download was made. However the phone is not now able to “connect bootloader” again in your image.
Can you tell from your phone that the phone at this point booted to Bootloader and now is in Fastboot mode, that is Fastboot will appear highlighted in red in the upper centre part of the screen?
Another older post, Mozzilla, who I understand do not support WebUSB for security reasons, show an interesting graphic of webUSB supporting browsers on this page WebUSB API - Web APIs | MDN.
At the point where I get stuck, is indeed the point where my phone is booted to Bootloader and I can see Fastboot in red.
If Vivaldi would be the problem. What browser is recommended to use? Could you also elaborate a bit more what these required permissions to release are?
I just tried Chrome Version 146.0.7680.178 (Official Build) (arm64)and I got the exact same problem.
An example of a permission I already mentioned … in your new Chrome browser are, perhaps, popup windows blocked? You might also notice something in the browser Settings > Security; if a line mentions USB just say OK.
Either the browser or perhaps Mac do not want to allow you to progress without (if the highlighted error is relevant) a “user gesture”. However, the error contains different ideas also. I will not be to do step by step debug of the eosinstaller. However you do have good evidence to Report an issue preferably in this location Work items · e / devices / eOS Installer · GitLab.
I can’t create an issue on Gitlab. It prompted me to make an account and then says:
1 error prohibited this user from being saved:
Email is not allowed for sign-up. Please use your regular email address. Check with your administrator.
I really think my phone is in some state that fastboot can’t connect. On my local machine I can connect to my phone with adb . Later I also try fastboot devices when the phone is in Fastboot and it gives no results. While adb devices does give result when the phone is turned on “normally” (not in Fastboot).
Hi, I’m currently going through the same process and encountered this issue as well.
After some searching I came across this post: Fairphone 5 not recognized in fastboot mode on any computer - Fairphone 5 - Fairphone Community Forum
Which led me to this post: Fastboot flashing unlock - <waiting for any device> - Fairphone 5 - Fairphone Community Forum
The latter post had the solution for me, which was to install an optional driver update in windows update. In windows 10 it’s under Settings → Update & Security → View optional updates (under the “Check for updates“ button). I don’t know how to find the exact name of the driver, but it was from Google and had “fastboot“ in the title/description.
Worth noting is that while I managed to get past this step I did get stuck at a later step in the installer. Hope this helps
This is dealt with in the Report an issue link under “Getting an error message in new ID creation on /e/OS Gitlab?”
This is the Mac? The preferred method to install platform-tools is Installing adb and fastboot on a Linux PC. There are no Mac specific instructions but Mac users use the download linked as, quoting that link:
The android site has different versions of the Platform Tools
Zero output is unusual please can you show the output of
fastboot --version
fastboot devices
Zero fastboot output can be caused by a USB cable issue.
Perhaps look at the whole USB chain. It has been reported that certain USB will not carry fastboot commands or complex fastboot commands. You will need a good quality (full capacity) data cable, so not a thin, skinny cable.
Avoid USB hubs including any USB hub that might be hidden in the PC / laptop.
Avoid a USB-C to USB-C cable as it may be provisioned through a hidden hub.
For predictably good results check (if necessary with a manual) that you are connecting to a USB-2 port soldered to the motherboard.
Is the FP5 locked or unlocked? It will be shown on the same screen with big green START and red highlighted Fastboot.