I’ve tried installing e/os using the web installer in Windows 11, but it always got stuck at the “Device Detection” step, where even though the phone was visible, it couldn’t connect (no pop up on phone), even though I followed all the previous steps correctly.
I heard it might work on Linux, so I installed Zorin (was thinking of doing that anyway), and tried the web installer again. This time i did get the popup on the phone, and after downloading the files it booted into the bootloader, but it there I got stuck again. I forgot the message it gave me but it was something to do with the bootloader (in the bootloader menu it says the bootloader is still locked btw). I can’t check again because now, for some reason, when trying, it won’t go past the “Device Detection“ step.
When running “adb devices“, it shows up. When running “fastboot devices“ it wont. I have tried multiple different cables and multiple different ports.
For the record, I’ve never used Linux before, so I’m a total newbie when it comes to that. And I have no experience with running commands or whatever.
Is anybody able to help or direct me to somewhere else for help? Thanks in advance!
I had the same result a month ago with my fairphone. I tried to install via the web installer via windows and linux but neither worked. I think The FP6 simply isn’t supported yet on the web installer. In the end I did install murena using the other method and it was surprisingly easy.
Edit: not sure if you checked, but there are several topics in the /e/ forum about installing on the FP6, maybe one of those has useful information. Not sure what search terms to use best, but the list of topics with the “eosinstaller” tag has a couple of FP6 entries:
Sorry, I haven’t seen this point.
Maybe first check if your FP6 is recognized correctly by the computer when in fastboot-mode. Just to check if the connection between phone and computer is OK.
My PC recognises the phone when running adb devices just as is, no mode, have not tried recovery mode yet. When running fastboot devices the same way it doesn’t see it. When my phone is in the bootloader menu I think, if I remember correctly, my PC doesn’t seem the phone at all.
Probably gonna have to try that, I did buy a new cable, hope that helps.
Yeah I saw that requirement, I tried both chrome and brave
Yeah if the web installer doesn’t work with my new cable, I’m gonna try to do it manually. Thanks for the info
Just to check, when you say “in fastboot mode”, what do you mean exactly? Is that the bootloader menu you get after OEM unlocking? The menu with the plain text where it shows phone stats?
When the FP6 is in fastboot mode, fastboot commands should work. adb commands don’t work in this mode (by design).
Similar to the above: when the normal system is running (and USB debugging is allowed of course) adb commands should work. fastboot commands don’t (again, by design).
Ok yeah that the screen I was thinking of. I don’t remember if I tried running the fastboot command while the phone is in fastboot mode, I’ll try that soon.
Ok yeah then it makes sense.
Thanks for the info. I’ve no experience with any of this, so it’s a bit overwhelming knowing what all the terms mean and what people are referring to
As @Ingo already mentioned, this is the way to go. Get into fastboot mode (adb reboot fastboot in terminal) and check if the phone gets recognized correctly by your computer (fastboot devices in terminal).
If this is OK, there should be no longer trouble with the web installer.
I purchased a Fairphone 6 with a preinstalled Android 15. I want to switch to /e/OS. I updated Android, I unlocked the bootloader, I activated USB debugging, following the instructions on the support site. The web based installer ( /e/OS Installer ) didn’t work (“Cannot connect ADB No device connected”), so I downloaded the installer to my Ubuntu laptop and tried from the command line. It copied and apparently installed many images, but failed eventually. I got the message:
Error: Critical partitions are still locked.
Did you execute ‘fastboot flashing unlock_critical’?
Unfortunately, unlocking the critical partitions doesn’t work either:
$ fastboot flashing unlock_critical
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
A factory reset in Recovery Mode also fails with a permission error. The phone is presently stuck in a boot loop. I cannot even reinstall Android. How do I get out of this?
I tried it with the official FP USB cable, and it seemed to go as intended, but now it gets stuck in the webinstaller with this message:
Error on step: connect-bootloader
Cannot execute command flashing unlock
Cannot execute command flash devcfg_a devcfg.img
error flashing file devcfg.img Bootloader error: Bootloader replied with FAIL: Flashing is not allowed for Critical Partitions
The phone still boots thankfully, so not in a bootloop. But I’m not sure what the issue now.
The bootloader is definitely unlocked, it says so in the fastboot menu, and like I mentioned it definitely got further than before (I guess a good cable really does make a difference)…but yeah, no idea what this issue is about…
