I am trying to install /e/OS on an Android Fairphone 6. I have successfully activated the developer options, unlocked the OEM function, enabled USB debugging and enabled File Transfer (in the Default USB configuration menu).
The next step (“We’ll now connect your phone to the browser. When this pop-up appears, select your telephone from the list.”) goes fine - the popup appears, I select my phone and I click connect.
The next step says “A pop-up window will then appeared on your phone. You will have to check always allow from this computer before pressing ok.”, but this popup window (the one that the image says should be headed “Allow USB debugging?” never appeared on my phone. The installer remained on this same screen, and if I try to click Connect again, the popup on the computer says “paired” next to my phone, and the following error message appears:
Error on step: device-detection
Cannot execute command connect adb
The device is not connected Failed to connect: Cannot connect ADB Cannot read properties of undefined (reading ‘deserial’)
Proposal: Check connection and that no other program is using the phone and retry.
I’ve tried that, it doesn’t help. Whatever I do, every time I click Connect in the “Device detection” step of the installer it fails and gives me the error message from above.
From the error message, the only thing I can think is that something else on the computer is somehow using the phone, but I don’t know what it could be or how to check.
I’m facing the exact same issue when trying to install e/OS on my new Fairphone 6 with the web installer:
developer options activated,
unlocked the OEM function,
enabled USB debugging,
enabled File Transfer (in the Default USB configuration menu),
no pop-up window when connecting phone and browser.
I tried Opera under Ubuntu 25.04 and Edge under Win11 without success and I’m sure that the USB data cable is working. Therefore, I decided to follow the advice in this thread and I’m trying to install e/OS via the command line option. My question:
The latest official e/OS build with /e/OS version 3.2 includes Android security patches available as of 2025-10-01. And my Fairphone says Android Security Update 2025-10-05. I understood that the Android Security Updates of my phone must be older. Should I wait for a new e/OS version and how long will it take for it to be published approximately? Or should I install e/OS version v3.1.4-a15 with Android security patches as of 2025-09-01? I mean will my phone update to the latest e/OS version after installation automatically then if I go for the latter?
forget about the web installer if you don’t want to loose your time and energy !
i have tried it yesterday to see…
even well skilled on the topic of flashing /e/ since 5 years, i failled like all other peoples,
it is not your fault.
you can install e-3.2-a15 without relocking the bootloader,
update to e-3.3-a15 next week, and then relock
Well, I have bad news. I waited for e-3.2-a15 and compared the Android security patches and it was fine, i.e. the patches of my phone were older than the ones of the e/OS build. I oversaw that I have to wait for e-3.3! I misunderstood that I could install v3.2-a14 without relocking and tought with e-3.2-a15 it was fine to relock. I’m sorry for this!
And yes, it is bootlooping. I followed this installation guide and no errors occurred until the very last step “fastboot flashing lock”. I could unlock the bootloader again: In bootloader mode it says “DEVICE STATE - unlocked”.
Want can I do now? Should I try to install e-3.3? The release notes say it already there, but it is not linked yet?
