Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

A phone is plugged in over USB but Android Studio and adb do not list it

ErrorAndroid Studio's device drop-down shows No Devices, or the phone is missing from Device Manager

Short answer

adb lists a phone only when four things hold: USB debugging is on, you accepted the computer's RSA key on the phone, the computer has a driver or udev rule for the device, and the cable carries data to a running adb server. Run adb devices -l, then work down the causes below; Tools > Troubleshoot Device Connections walks the same path.

  • Applies to Android Studio (current stable), Android SDK Platform-Tools (current stable), macOS 26, Windows, Ubuntu Linux
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Ask adb directly, with its own server freshly started, and watch whether the phone appears or what state it reports. Studio uses the same server, so what adb shows is what Studio can use.

    adb kill-server
    adb start-server
    adb devices -l
  2. 2Match what you see, then jump to its fix

    1. 1adb devices shows nothing at all, and Settings > Developer options on the phone shows USB debugging switched offUSB debugging is off, or Developer options is not unlockedFix
    2. 2The phone shows an Allow USB debugging dialog with an RSA key fingerprint, or you dismissed that dialog earlier and it has not returnedThe computer's RSA key was never accepted on the phoneFix
    3. 3On Windows the phone appears in Device Manager under Other devices or Portable Devices with a warning icon, and adb devices stays emptyWindows has no USB driver for the phoneFix
    4. 4On Ubuntu or similar the phone shows in lsusb but not in adb devices, or adb prints a plugdev group messageLinux: the user is not in plugdev or the udev rules are missingFix
    5. 5The phone charges but nothing happens on the phone or in Device Manager, and another cable or port makes it appearThe cable or port does not carry dataFix
    6. 6Everything on the phone is right, yet adb devices stays empty until adb is restarted, or Studio cannot even connect to an emulatorThe adb server is stale or Platform-Tools is out of dateFix

What does the error look like?

  • Android Studio's device drop-down shows No Devices, or the phone is missing from Device Manager
  • adb devices prints List of devices attached with nothing below it
  • adb devices lists the phone with the state offline
  • flutter devices does not show the phone

Cause 1 of 6

USB debugging is off, or Developer options is not unlocked

1Check

adb can talk to a phone only when USB debugging is enabled on it. On the phone open Settings, then Developer options, and check the USB debugging switch. If Developer options is missing from Settings, it is hidden until you unlock it, and Android's own page explains how.

adb devices -l   # then check the USB debugging switch on the phone itself

2Fix

Turn on USB debugging in Developer options, then unplug and reconnect the cable.

adb devices -l

3Verify

The phone shows up in adb devices -l and in Android Studio's device list.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 6

The computer's RSA key was never accepted on the phone

1Check

From Android 4.2.2 the phone asks whether to accept the RSA key of the computer before debugging over USB is allowed. Until you unlock the phone and accept, adb commands cannot run. The dialog is easy to miss on a locked screen.

adb devices -l   # the phone must be listed with the state device

2Fix

Unlock the phone, unplug and reconnect the cable, and tick Always allow from this computer in the dialog before tapping Allow. If no dialog ever appears, use Revoke adb debugging authorizations in the phone's settings, then reconnect.

adb kill-server
adb start-server
adb devices -l

3Verify

The state column reads device.

adb devices

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 6

Windows has no USB driver for the phone

1Check

On Windows a USB driver is needed for the device to talk to adb; macOS and Linux need none. Open Device Manager with the phone connected and see whether it has a working driver.

adb devices -l   # then look for the phone in Device Manager

2Fix

Download the driver for your phone's maker from the list in Android's OEM driver page, or use the Google USB driver in your SDK folder (android_sdk\extras\google\usb_driver) for Google devices, and install it by choosing Update Driver for the device in Device Manager.

# Device Manager > right-click the phone > Update driver
# > Browse my computer for drivers > choose the driver folder
adb kill-server
adb devices -l

3Verify

The device name appears in adb devices -l.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

Cause 4 of 6

Linux: the user is not in plugdev or the udev rules are missing

1Check

On Ubuntu, each user of adb has to be in the plugdev group, and udev rules that cover the device must be installed. Android's docs name the android-sdk-platform-tools-common package as the source of a community-maintained rule set.

id | tr ',' '\n' | grep plugdev
lsusb

2Fix

Add yourself to plugdev, install the rules package, log out and back in (group changes apply at login), then reconnect the phone.

sudo usermod -aG plugdev $LOGNAME
sudo apt-get install android-sdk-platform-tools-common

3Verify

id lists plugdev and adb devices shows the phone.

id | tr ',' '\n' | grep plugdev
adb devices -l

Confirmed by developer.android.com

Did this fix it?

Cause 5 of 6

The cable or port does not carry data

1Check

Android's troubleshooting steps for USB connections include swapping the cable. If you have only one cable, try a second phone: if the second phone is detected, the cable is fine and the first phone's settings are the problem.

adb devices -l   # run it once per cable and per port

2Fix

Use a cable that you know carries data, try another port on the computer, and retry.

adb kill-server
adb devices -l

3Verify

The phone is listed on the new cable.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

Cause 6 of 6

The adb server is stale or Platform-Tools is out of date

1Check

Studio and the command line talk through one adb server process. Android's troubleshooting page lists restarting that server, and, if Studio cannot connect to an emulator either, downloading the latest SDK Platform Tools. Compare your adb version with the current release.

adb --version
which -a adb

2Fix

Use the Restart ADB server button in Tools > Troubleshoot Device Connections, or restart from the terminal, and update SDK Platform-Tools in the SDK Manager. Make sure only one adb is on your PATH.

adb kill-server
adb start-server
adb devices -l

3Verify

adb devices -l lists the phone, and Studio shows it after you reopen the device menu.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Keep SDK Platform-Tools updated from the SDK Manager and keep a single adb on your PATH.
  • Keep a USB cable you know carries data, and label it.
  • Accept Always allow from this computer once, so the RSA prompt does not return after every reconnect.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Flutter's Android build stops: JAVA_HOME is not set

ERROR: JAVA_HOME is set to an invalid directory

The Gradle wrapper script needs a Java runtime and looks in two places: the JAVA_HOME variable, then a java command on PATH.

3 causes, each with a fix

Mobile apps

flutter doctor cannot find the Android SDK

Unable to locate an Android SDK.

Flutter looks for the SDK in a fixed order: its own android-sdk setting, then ANDROID_HOME, then ANDROID_SDK_ROOT, then the default folder for your system.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.