Hello,
I recently got a Pixel 2 on stock Android 11 with the intent of flashing LineageOS + rooting. But I haven't had any luck getting ADB to recognize the phone so far. I am using Windows 10 and Ubuntu Linux 20.04 LTS.
As a prerequisite, I enabled developer options, USB debugging, and OEM unlock.
I'm pretty sure the USB port of the phone is okay because the phone still fast charges.
Here's what I've tried:
- using Minimal ADB (device does not appear when adb devices is run)
- using platform-tools ADB (same as above)
- using wireless ADB (ADB is able to pair but the phone still doesn't appear when adb devices is run)
- checking Device Manager (device does not appear)
- Installing Google USB drivers
- using OEM cables from Samsung and other Android OEMs
- using a micro USB cable with a micro-to-C adapter
- using a USB hub
Am I missing something? What should I be doing to get my phone to be recognized by my computer?
Thank you in advance.
Hi, sounds like you've tried all the usual trouble shooting bits with cables, ports etc. Only other things I can think of at a stretch are to try enabling file transfer when you connect to a pc and see if that makes any difference or booting into bootloader via the button combo from powered off and then running fastboot devices from your adb and fastboot to see if it is recognised in fastboot mode?
Related
I just had an idea. I know you can root some phones using ADB and I got to thinking. All android phones have an ADB daemon running in the background that you can connect to through usb on your pc using the ADB client application provided by google(adb.exe) and usb adb drivers provided by google.
Now that you can turn your phone into a USB host using USB OTG, wouldn't you be able to use your phone instead of a computer? With a Micro-B to Micro-B USB cable? Someone has already ported the ADB client to android(ARM-Linux ELF). So someone would just need to port over the drivers to android, and then we could connect to adb on one phone using another with a terminal emulator. Right?
What are your thought?
I have attached the adb and fastboot clients that were ported to android. (adb-fastboot for arm)
EDIT:
I found this for raspberry pi (which is arm based):http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130
So after reading a bit more it seems that the drivers aren't even needed. They are only needed when using ADB with windows. But, since Android doesn't use "udev" I don't know if or how android would recognize that another phone is connected.
Can someone explain me how to get ADB working on my SGS8? I've tried everything: installing drivers, Java, Android SDK, 15 sec adb driver, universal ADB driver, minimal adb. I can't figure out how to do that.
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
jaannnis said:
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
Click to expand...
Click to collapse
Thanks, will try that
i was having one hell of a time as well. I tried everything on my laptop to no success. So i actually gave up. Than i thought well maybe its my laptop. So i ended up trying another one i had in the house and viola it worked like a charm. It seems like certain pc are just unable to connect to the samsung s8 via adb mode. Which is totally weird because I had been using adb mode on my pixel xl with no issues what-so-ever. So try a different pc if you can, it worked for me flawlessly.
Might be the USB port.
I had a similar problem connecting my Lenovo laptop to a Kindle Fire. I used a different USB port and everything worked.
9 bin
Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs
Hello all,
My OnePlus 7 Pro, can't recognize USB through my Windows PC, I don't get the prompt to connect to my Win PC.
Also I enabled ADB with Developter Options. I go to fastboot and also after adb devices and fastboot devices command, he can't recognize my device.
My OnePlus 5T is working with ADB and normal USB Win PC, tried two cables and laptops.
I did an run Android 10, now 11, beta etc nothing works! The phone can charge etc.
Please help. Reset etc tried also.
it is known issue ADB don't work on USB 3.0 ports
just goto BIOS > Advanced > USB > XHCI and change the setting to Disabled.
This will make the ports run in USB 2 mode, and fastboot and ADB works as usual.
ineedroot69 said:
it is known issue ADB don't work on USB 3.0 ports
Click to expand...
Click to collapse
Can't confirm this. At least latest version of ADB works at me with USB 3.x ports.
Nvm I didn't read the thread well if the PC can detect the other phone on ADB perhaps you can try "revoking USB debugging authorization" so it would ask for permission again
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
furrymonster said:
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
Click to expand...
Click to collapse
What version of platform-tools (adb) are you running?
I installed LineageOS 18.1 on my Pixel 3 back in April of this year.
I grabbed the latest platform-tools (33.0.1) for Linux at the time and I am able to connect, transfer files, etc. with no issues.
Below is the version I have installed on my Linux desktop . Hope this helps.
$adb --version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as ~/bin/platform-tools-r33.0.1/adb