I used to be able to transfer data from my android FP5 to my Win11 laptop without issues, now it doesn’t appear in my explorer anymore. I can however eject it like any USB stick. The calyxOS FP4 of my bf doesn’t work either, my work phone (samsung, android) works just fine.
Things I did:
Trying different ports. Different cables. Switching out the USB-C port on my FP5. Updating drivers. Making sure everything else is up to date. Everything on the troubleshoot page FP provides (selecting file transfer, clearing cache).
I am out of ideas…Why are only the FPs not appearing in my explorer?
win11 version: 25H2
android: 15
Hi and welcome to the community 
Could you report your OS build number? Go to
Settings > About phone > Build number
This is certainly strange in that suddenly (do you have any context info on that, such as recent OS update?), neither of the two FPs are connecting, whereas the Samsung is. You might do a few more tests to narrow things down yet more:
- Apart from charging, are you able to use the USB ports of the phones for other purposes, such as wired headphones or tethering?
- Have you tried connecting the FPs to another PC or Mac?
- Is the Windows 11 PC yours, or from work like the phone?
While this problem is getting sorted, you might transfer files over Wi-Fi Direct or Bluetooth, or by cloud sync.
Thank you for your response!
Build number: FP5.VT2Q.C.092.20260330
-
Yes, I connect it to my car for music/navigation sounds
-
Yes, on our linux mint PC it works
-
It is my private laptop
Thank you! it is not urgent I would just like it to work again…
OK thanks for the info.
When you connect the FP to the Windows 11 PC over USB,
- Does the PC react at all? Sound? Notification?
- Does the FP react at all?
- Does the phone appear in Windows File Explorer, and in which case in what manner? A device with no storage?
One thing that shouldn’t be necessary but that has in the past helped, is to use a Developer option to set the default USB configuration to File transfer. To save time, I indicate below how to enable Developer options because you may not know.
- Disconnect the phone from the PC.
- Go to
Settings > About phone > Build number (yep, you’ve been there already but we’re doing something different)
- Tap the rubric “Build number” seven times. If at the first tap you see the message “No need”, then continue with the next step.
- Go to
Settings > System > Developer options
- Scroll down to the “Networking” section (at least five screen lengths) until you see “Default USB configuration”. Tap that setting, and choose “File transfer”.
- Exit Settings and restart the phone.
- Connect to the PC.
Please note that Developer options are by default hidden to avoid inadvertent modifications of settings that most users don’t need to change. Never change one of these settings without good reason and knowing what you’re doing. Always keep a record of what changes you make, and when.
- Yes, it makes a sound. It also makes a sound when i switch to file transfer
- Yes, it vibrates bc its getting charged and it gives me the silent notification
- Not at all
When I eject it I get a windows notification “Google nexus ADB interface” can be removed from the pc.
Tried it, unchanged sadly…
Well, your remark about the notification at deconnection is helpful. For me, this would indicate that the PC isn’t seeing the FP properly. The message should mention “Android Composite ADB Interface”, not “Google nexus”.
From what I’ve been able to gather from a quick search, it looks like a Google Nexus-specific driver has been installed on the PC, such that the phone isn’t seen properly as a generic Android device.
Next time the opportunity arises, I suggest you connect the phone and then open Windows Device Manager to check how the phone is seen. Normally, under “Portable devices” you would see something like this:
Could you report back with a partial screenshot or text description of the device.
It’s likely just a driver that needs to be replaced or installed, but it would be interesting to know how the wrong driver got installed in the first place.
Ohh interesting. I have no idea how this could have happened. Maybe bc my bf used my laptop to install calyxOS? There has never been a google nexus device around my laptop ever.
I also specifically repaired my Universal ADB Driver bc of these issues (idk if that was necessary)
this is what it looks like when I add it:
OK so we know what the problem is: wrong driver. I’ll check and get back.
Before (re)installing the OEM driver, it might be a good idea to remove the Google Nexus driver.
To do that, from Windows Device Manager, right-click on “Google Nexus ADB Interface” and in the context menu
choose “Uninstall device”.
Then, you might just reboot the PC and see if it finds the Farphone device straight away. If it doesn’t, then there are (at least) two ways of getting the correct driver installed.
-
Either you can work through the standard Windows Update interface
Settings > Windows Update > Advanced options > Optional updates
-
Or else, you can go to the relevant Android developers’ page and follow the instructions for Windows 10. The first thing to do will be to download the correct OEM driver for your particular PC (list of manufacturers at the lower part of the page).
Thank you!! I just removed the driver and it worked!
I never connected the dots, thank you for taking the time to help me! 
