My IodéOS FP5 isn't detected by ADB

Installation Help
1

Hi

I’m trying to flash a stock OS image on my IodéOS FP5 (with IodéOS 6.6 installed), but despite enabling USB debug, disabling USB restrictions, and verifying the default USB mode, I can’t get it to show in ADB (latest version, v36).

I verified with my new phone (a FP6), with the exact same setup (usb cable and port, adb release, phone settings, etc.), everything works.

I even opened my phone, cleaned the USB port pins (external as well as internal), and nothing seem to work. Charging works though.

Note : I never saw the “trust computer” prompt on my FP5, but did on my FP6.

Other infos :

  • OS tested : Fedora Silverblue (latest), Fedora KDE (liveOS)
  • Tools version tested : 34 (Fedora repositories and officials), 36 (official)
  • USB port tested : case port, usb hub and direct connexion to MB were tested
  • USB cable tested : AtoC, CtoC, multiple of them, none worked with FP5, all worked with FP6
  • Factory reset tested : yes (2 times)

Best regards

2

I just got feedback from another user on the brax forum that their System Settings > Security * privacy > More security & privacy > Trust > Restrict USB was set to Deny USB connections. Setting it to Always allow USB connections which I think is default worked for them in that case.

3

No luck on my side unfortunately. The USB port was kinda getting finicky with data connection lately, so I’m currently considering hardware issue… I’m gonna call support tomorrow.

1 Like
4

And what happens if you plug a USB stick directly to the device?

5

USB stick is detected. So maybe not an hardware issue after all.

6

For Linux, i found this:
If the device is not detected, it may be necessary to add udev rules with the device vendor ID so that Linux recognizes the device. For Fairphone, the vendor ID is usually 2ae1.

https://xdaforums.com/t/guide-linux-installing-adb-and-fastboot-on-linux-device-detection-drivers.3478678/

7

Unfortunately I won’t be near my computer for a while, so I won’t be able to try that, but I already can give you those Infos:

  • device was not listed on lsusb
  • device was not listed on device manager on my W11 work computer

It also worked great without udev rules previously.

8

I ended up staying at home later than expected, so I tried it. No success unfortunately.

Still no device, even on lsusb. On the other hand, when I connect my FP6, I get a Bus 007 Device 004: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP) added to lsusb, even when USB debug is off.

9

Windows only:
when you connect the device to Windows computer and you look into the device manager. As the device manager flickering when you connect it?

When the device is connected, does the device switch from battery to charging?

10

Did you check that “Trust” setting for USB connections I noted earlier? System Settings > Security & privacy > More security & privacy > Trust > Restrict USB needs to be set to Always allow USB connections

11

Yes, I did. USB connections are unrestricted. I even switched it on, then off, as there was a bug on /e/OS that made another setting not properly apply until such manipulation was done.

12

No flickering.

Charge starts, but no data connection is available, as if the USB restrictions was fully on (despite not being on in the UI)

13

Have you tested Disabling USB Debugging, restart device and reenabling it?

14

Tried, but no changes, I cannot even see the popup asking to change the usb mode between PTP, media transfert, etc… nor can I see the phone on the computer,

15

So the same host machine (let’s stick to Linux here for simplicity :-), same port, same cable. FP6 no issues connecting via adb, FP5 not detected? Lint cleaned out of phone port? :slight_smile: Switch cable upside down? (I had one phone require that, not sure if a pin was damaged or what).

@volker01 do you have a FP5 you confirm is working?

16

I tried multiple computers (1 Linux, 2 Windows, one being W10, the other W11). In all cases the FP5 was not detected other than for power, and FP6 was detected without any problem. FP6 is on stock OS, FP5 on IodéOS 6.6.
With the amount of time I connected and disconnected, I suppose the other side would have been tried at least once, so I doubt it will work.

17

I really can’t think of what else may be blocking it, but if you aren’t seeing any USB activity in dmesg (or lsusb) and the USB permissions are there on iodé then it is a bit baffling. Especially if you are in the bootloader on the phone it is before the OS.

So, probably not an interest of yours to go all the way back to FP5 stock Android, but it would be the best way to confirm it isn’t any hardware issue we are banging up against.

I think we need to see if other FP5 users report the same problem.

18

ADB detection on Windows:
This should help:
Connect device, then switch to the ADB tools with a CMD. Enter adb --devices. At the latest then the query of the ADB should come.

That’s how it was for me now, with the tablet S5e

19

Tried many times already, the device never showed up.

20

So, I got some news.

The problem was indeed physical, as replacing the usb-c port fixed the issue. I’ll see with Fairphone to reimburse the port, but I should now be able to flash the stock OS back.

1 Like