Cannot connect ADB via USB on Pixel 4

Using /e/OS Troubleshooting
1

Last year I installed /e/os on my Pixel 4 and noticed that USB for data transfer stopped working. It only works to charge the battery. Current installed version /e/os is 2.1.

When the phone is connected to a PC, the USB section in the settings looks like this:

Screenshot_20241102-214128_Settings
Screenshot_20241102-214128_Settings1080×2280 118 KB

And when disconnected from the PC, it’s like this:

Screenshot_20241102-214210_Settings
Screenshot_20241102-214210_Settings1080×2280 110 KB

This problem was irrelevant to me before and I didn’t deal with it. But now I want to get the original Pixel firmware back so I can use this phone for banking apps.

ADB can’t find the phone over USB, but I can connect over wifi. And after doing adb reboot bootloader I can’t unlock the bootloader because the phone is inaccessible.

What could be the problem with USB? I tested plugging in with another cable, also on Linux and MacOS.

I ran some commands in the console of the phone. Maybe something else is needed?

flame:/ $ getprop init.svc.adbd
running

flame:/ $ getprop | grep usb
[init.svc.usbd]: [stopped]
[persist.data.df.dev_name]: [rmnet_usb0]
[persist.sys.usb.config]: [adb]
[sys.usb.config]: [adb]
[sys.usb.configfs]: [2]
[sys.usb.controller]: [a600000.dwc3]
[sys.usb.mtp.device_type]: [3]

Here after 21:25 I unplugged and plugged the cable and also ran adb usb: dmesg.txt

2

Did you try another cable ?
There are USB cable for data and some without data transfer capability (e.g. only charge)

My bad, I’ve read too fast :

3

I was first going to say is there an odd selection in

Settings > Developer options > Default USB configuration ?

But I saw there “and your phone is unlocked” …

I never worked with a Locked bootloader … but you say you used this command …

… what is the result of

fastboot devices

… is that recognised, once you boot to fastboot mode after shutdown with button presses

  • With the device powered off
  • hold Volume Down + Power

EDIT
Later I saw that I seemed to reproduce your images with
Setting > Developer options > USB debugging – toggled off !

If you remember noticing it stop working, maybe the phone’s USB module failed.

Further edit I did read your dmesg. This runs for 35 minutes, I wasn’t quite sure what I was looking for, did you try a certain action repetitively? I noticed 20 records

android_work: did not send uevent (0 0 0000000000000000)

(I am only guessing if I thought you might have tried adb via USB 20 times?) android_work represents a Work profile, UEvents are quite fundamental, zero has significance, but I don’t think I can explain in this context, other than the line sounds a double negative from my understanding so far.

Would there be any possibility that Work profile was in some way not fully within your control ?

4

I’ve tried selecting other items here, but it doesn’t affect anything.

Nothing

% ./fastboot devices
%

Yeah, I could have :slightly_smiling_face:

No. I have now uninstalled it and erase all data (factory reset). That didn’t help.

Isn’t there a way to unlock the bootloader and install another OS without USB?

5

I’ve never tried but these seem to say you can:

Last time did I cut my quote too short:

… I thought if you issued one fastboot command can you issue another instead over wifi

fastboot devices

… but I guess you gave the answer already ?

6

I was wrong. I typed adb reboot bootloader. Corrected it in the first post.

After booting into fastboot mode, no fastboot commands are executed:

IMG_20241103_163742
IMG_20241103_1637421920×3413 281 KB

% ./fastboot
fastboot: usage: no command

% ./fastboot devices
%

% ./fastboot flashing unlock
< waiting for any device >

It looks like there is indeed something wrong with the USB module. Thanks for trying to help.

7

This topic was automatically closed after 60 days. New replies are no longer allowed.