SCRCPY is the best tool for viewing and controlling your Android phone on Windows, however, it relies on the Android Debug Bridge (ADB) to establish communication with your device. And if ADB encounters issues, SCRCPY will not function properly. So this guide will help you troubleshoot common ADB-related errors that can prevent SCRCPY from working. From "ADB not found" to "Device unauthorized" and a few other random ones as well.

Takeaways:

  1. Learn how to fix the most common SCRCPY ADB related error messages.
  2. Why does SCRCPY keep crashing when opening?

How to Fix SCRCPY ADB Not Found Errors

"SCRCPY cannot locate the ADB binary in your system's PATH" is one of the most common error messages you get when trying to launch SCRCPY on your computer. But there is a fairly easy fix for this problem.

Ensure that ADB is accessible from your system’s PATH.

On Windows: adb.exe is included in the SCRCPY release. Ensure you are running SCRCPY from the directory containing adb.exe, or add that directory to your PATH.

On Linux/macOS: install ADB via your package manager (e.g, sudo apt install adb or brew install android-platform-tools) and confirm it’s properly installed in your PATH.

SCRCPY Device Not Detected Error

If you get the following error message when launching SCRCPY "ERROR: Could not find any ADB device." You've configured something wrong during set up.

Ensure that USB debugging is enabled on your Android device:

  • Open Settings, go to Developer Options (enable it if not already), and toggle USB debugging.

Verify if your device is detected by running the command:
adb devices.

  • If your device is not listed, you may need additional drivers (Windows users may need the USB driver for Google devices).

I highly suggest checking out our full set-up guide on SCRCPY here as you have probably missed an important step.

SCRCPY Device Unauthorized Error

If SCRCPY shows an unauthorized device error such as this one: "ERROR: Device is unauthorized." You probably didn't accept one of the prompts that appeared during the set-up process.

When connecting your device, a popup should appear asking you to authorize USB debugging.

  • Tap "Allow" to authorize the connection.

  • If the popup does not appear, disable Developer Options and retarded the entire set-up process.

Several Devices Connected

If SCRCPY detects multiple devices and shows "ERROR: Multiple (2) ADB devices." You'll need to pick the specific device you want to open. Essentially, if multiple devices are connected, specify the target device using one of these options:

  • scrcpy -s <device_serial> for a specific device.

  • scrcpy -d for a single USB device.

  • scrcpy -e for a single TCP/IP device.

ADB Version Conflicts

This is another annoying error message and is usually caused by an adb conflict. "adb server version (41) doesn't match this client (39)."

This occurs when different programs use conflicting ADB versions. Resolve this by checking and doing the following things:

  • Identifying the program using the conflicting ADB version.

  • Overwriting the ADB binary in the conflicting program with the version used by SCRCPY.

  • Alternatively, tell SCRCPY to use a specific ADB version by setting the ADB environment variable:

    • On Linux/macOS: export ADB=/path/to/your/adb

    • On Windows Command Prompt: set ADB=C:\path\to\your\adb.exe

SCRCPY Device Disconnected Error

If SCRCPY stops unexpectedly with the message: "Device disconnected." There's a good chance you have a faulty cable or you haven't connected it properly.

The ADB connection might have been interrupted. Try the following:

  • Use a different USB cable.

  • Plug your device into another USB port on your computer.