Thanks MrRecursive, adb finds the device on linux mint but not on Windows 11.
A window pops up saying “usb debugging” but no option to allow. Howver works with Linux.
Not tried flash yet but at least adb sees the device. Hopefully get time at the weekend.
Thanks everyone for all the input! You’ve been great! Looks like this part of the process sorted by using linux rather than windows. I want to get my head round the issue of inconsitant security patch dates described in another thread before trying to flash. Don’t want tyo turn my new phone into a brick 
Hi Max,
I have the identical issue with my phone (FP6) and was wondering if you mananged to get everything working? I think I’ve set up everything as I should have when initialing the eos installer (on vivaldi/chrome) but I dont get a popup ‘allow usb debugging’.
I have both Win 11 and Linux Mint but have the same issues on both systems. My old motorola does get a ‘allow usb debugging’ prompt.
Thanks, Willem
So the common cause seem to be the installer from e/OS?
Any reports in the e/OS forum?
Edit: what about attaching the FP and allow USB debugging before starting the installer
I posted on the e/os forum but no reply so far. Couldn’t find a similar existing issue there (lots of generic trouble with installing the os).
Can’t start the installer without connecting the FP. Immediatly after pressing the ‘connect’ button, I can still select the FP6 (meaning the installer can detect the phone).
Ok but cant you allow USB debbuging for this PC without being asked again? So attach allo, remove, start, Attach?
(thanks for replying, before I forget)
Yes, I can allow usb-debugging via a work-around.
I can go to Developer Options > Revoke USB Debugging Authorizations.
After that, when I connect the cable with Windows, I get the ‘USB File Transfer’ message in the phone’s top bar, where you can change the ‘Use USB for’ settings.
If I change that to ‘No Data Transfer’ and then plug in the usb cable, suddenly the popup ‘Allow USB Debugging’ appears! Also shows my RSA key and the box asking ‘Always allow from this computer’ that I can tick.
Unfortunately, after having done that (and changing the usb preferences back to File Transfer, the e/os installer his the exact same reaction as before; not working.
1 Like
I think I never set the USB mode to “File Transfer” for USB debugging/using adb.
Have you tried just leaving it at “No Data Transfer”?
I have now, but also doesn’t work. The error message (cannot connect to adb) now appears instantly, instead of takes minute or two.
It seems to be in the instructions…
I would address this rather in the e/OS forum as its connected to the web installer
1 Like
Might be a good idea. I’ve made another post on the e.foundation community page ( Web Installer issues - FP6 - ADB connect issues? - Web Installer - /e/OS community ). I’m happy to get suggestions in both forums as this might also be a specific Fairphone 6 issue (problems with adb or connection issues in general).
Hi WillemS, I havent tried the web-based installer again as now I have adb working, I feel more in control with this. Have you tried installing adb on linux and then typing “adb devices”? For me this resulted in the correct popup on both phone types on linux. On windows 11 it only works for the Samsung not the fairphone.
I’ve never had that message.
Hi Yvmuell, For me it wasn’t the installer. It was that adb wasn’t finding the device, which presumerably was stopping the installer. I suspect for me it is that Windows is associating an action to the phone when it connects. I have told it not to do this in control panel but it still opens a file manager every time the phone connects.
I have now managed to install e/os, but via the A15 community file build.
I had the same issue, that adb wasn’t working. After many attempts to get it working, the above method did work in the end (with many minor issues). I ended up using Windows 11 and Linux Mint keeps giving me connection issues. Even after the successful install of e/os, I still can’t connect my mint to my phone.
Thanks WillemS,
I’m still stuck on connection issues. Only trying it on old Samsung at the moment as want to make sure I understand process before using it on new fairphone. I get as far as downloading the recovery file (according to the computer end) but it then fails to close connection. When I reboot phone into recovery it still says android recovery at the top, which I assume is wrong.
Not sure if this fits 100% here but anyway, I’m trying to enable USB Debugging on Fairphone OS/Fedora and it doesn’t work. adb devices at best says unauthorized (even though that one time I authorized the computer). Otherwise it’s either offline or not listed at all. Tried all sorts of combinations including setting USB Mode to File Transfer but none worked. Note - on other phones it’s enough to enable USB Debugging and authorize the computer.
This is really annoying and problematic to any developer I’d assume. On the bright side - debugging over wi-fi seems working.
Just asking the obvious. You did tap 7 times on the Build number in the app Settings, About phone to get access to the Developers options?