ADB not available on FP3

[yvmuell]

USB debugging is activated and allowed I guess?

[FPbonn]

Yes.

I assume a broken bottom-module, which apparently isn’ available at the Fairphone Web-Shop (Out-of-Stock). I think, that the fastboot protocol is more robust compared to adb and also works with weak electrical contact.

[yvmuell]

So you can charge , use fastboot, what about normal mode? I would be suprised when you else have no issues with the bottom module, that this is the root cause. And you did not amswer my question, is USB debugging enabled and confirmed on the device for this PC?

[FPbonn]

USB debugging is enabled within LOS, but USB-mode is greyed out. That’s why I assume a broken bottom-module. The charging is also very very slow.

[FPbonn]

I think the bottom module is definitly broken. All 3 issues leads to this conlusion:

• USB-mode is greyed out, if you connect the FP3 with a computer
• Very very slow charging
• No ADB available - only conection via fastboot

[FPbonn]

Connected with my computer:

Everything greyed out. None of the choices are available.

[yvmuell]

I guess we cant be of much help here, in case other cable or charger dont help…so you are sure you are using a data cable?

[FPbonn]

As I mentioned before, the cable is a high quality cable made by Anker as well as the charger from Anker.

Is is the reason why I assume a broken bottom module.

[anon9989719]

@FPbonn

the cable is a high quality cable made by Anker

Maybe not a quality issue but is it IF data compatible not just a power cable.

You can try and clean the contacts in the USB C port even take it apart to have a better look.

FP3 Bottom & Top module breakdown

Hi. Images below taken with an FP3+ I have a defunct F3 that I disassembled to see if I could fix it; No luck; but whilst at it I thought I’d take a look at the bottom module as one issue was that it wouldn’t charge. The bottom module can be prised open, it has four small latches, two stainless steel and two plastic, so be careful. I opened the steel one first. Here is the inside of the two halves of the surround. Centre is the slot for the USB C port. The shiny B98CBC is probably the vibrato…

[FPbonn]

It’ a data cable. Also fastboot mode works, but not adb.

I dismantled the bottom module and cleaned the USB-C connector - no success.

[FPbonn]

From syslog:

.
.
Jul 23 23:07:25 mycomputer kernel: [1011156.052349] usb usb1-port1: attempt power cycle
Jul 23 23:07:26 mycomputer kernel: [1011156.464276] usb 1-1: new full-speed USB device number 34 using xhci_hcd
Jul 23 23:07:26 mycomputer kernel: [1011156.464504] usb 1-1: Device not responding to setup address.
Jul 23 23:07:26 mycomputer kernel: [1011156.672468] usb 1-1: Device not responding to setup address.
Jul 23 23:07:26 mycomputer kernel: [1011156.880262] usb 1-1: device not accepting address 34, error -71
Jul 23 23:07:26 mycomputer kernel: [1011157.008290] usb 1-1: new full-speed USB device number 35 using xhci_hcd
Jul 23 23:07:26 mycomputer kernel: [1011157.008449] usb 1-1: Device not responding to setup address.
Jul 23 23:07:26 mycomputer kernel: [1011157.216518] usb 1-1: Device not responding to setup address.
Jul 23 23:07:27 mycomputer kernel: [1011157.424293] usb 1-1: device not accepting address 35, error -71
Jul 23 23:07:27 mycomputer kernel: [1011157.424382] usb usb1-port1: unable to enumerate USB device

That means, that the FP3 not responds in the expected way.

[FPbonn]

On the pics of the bottom module circuit I cannot see any other things than resistors, capacitors and the vibration motor - no active devices. I’am afraid, that this components are located on the main board.
In the case the replacement of the bottom module won’t help at all.

[FPbonn]

That’s what it looks like, if I connect the FP3 of my wife with that Anker cable:

Jul 24 08:26:04 mycomputer kernel: [1015627.253198] usb 1-2: new high-speed USB device number 93 using xhci_hcd
Jul 24 08:26:04 mycomputer kernel: [1015627.403850] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.09
Jul 24 08:26:04 mycomputer kernel: [1015627.403857] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 08:26:04 mycomputer kernel: [1015627.403860] usb 1-2: Product: FP3
Jul 24 08:26:04 mycomputer kernel: [1015627.403862] usb 1-2: Manufacturer: Fairphone
Jul 24 08:26:04 mycomputer kernel: [1015627.403865] usb 1-2: SerialNumber: A20AB5RXXXXX

[struppi]

Oh, so you’ve got 2 FP3 devices at hand? Try swapping the bottom modules between those two

[FPbonn]

My wife doesn’t want me to dismantle her FP3

[anon9989719]

@FPbonn

I’am afraid, that this components are located on the main board.
In the case the replacement of the bottom module won’t help at all.

Yes it’s largely a passive pass through, all the charging arrangements are done on the core module.

Still a good clean may stir something up. Any short on the module can send a signal to the core module etc.

[Aras]

Since fastboot works, maybe try to fastboot boot into recovery (from file on PC), I don’t see how, fastboot would work if it was a hardware issue, maybe just software, maybe try different recoveries.

[FPbonn]

As I mentions before, fastboot works fine. ADB sideload does not work neither with LOS-Recovery nor TWRP. Also ADB does not work if the FP3 ist booted into LOS and USB-Debugging is enabled within the developer options.

I assume a broken bottom module (e.g. broken soldering, resistor, …) or defektive main/core module.

[FPbonn]

Today I received 2 brand new bottom modules for FP3. One of them I installed for testing purposes into the FP3 we are talking about here. And voila: It’s fully functional again.

Summary:
I recommend using USB-cable of top brands (e.g. Anker) and if you are struggling with USB-issues first change the cable and second the bottom module, which isn’t too expensive.