For issues specific to the Android Debug Bridge (adb), a command-line tool to interact with Android devices and Emulator instances. See the full tag wiki for details and hints.
Android Debug Bridge (ADB)
Android Debug Bridge (adb) is a versatile tool that lets you manage the state of an emulator instance or Android-powered device.
adb is part of the Android SDK and is the essential managing tool for Android device development. Quoting one of the tutorials2:
ADB or Android Debug Bridge is a command line program which is used to communicate with your Android phone (or an emulator used by programmers). The use of ADB for Android phone users ranges from using it as a tool to get the logcat- A realtime log of the Android system, which allows one to know the cause of any errors. It is very helpful to app hackers to know exactly what block of code does what, and to modify apps accordingly
For Windows, one usually needs a device-specific driver to get ADB working. If you cannot find one for your device, you might want to check with the Universal ADB driver.
A device should have USB debugging enabled in order for ADB to be used on that.
You can also use ADB between two Android devices, wirelessly. Note that, however, with Marshmallow (Android 6) the
adb binaries have been removed from within Android. To get them back, you can e.g. use Magisk and its adb-Installer module.
See also, here on this site:
- What is this
adbutility I keep getting advice to use?
- What's ADB and why is it used for? How do I install it on my device?
- Is there a minimal installation of ADB?
- How do I get my device detected by ADB on Linux?
- Configuring ADB on Ubuntu
- Accessing "no-name" devices which are ignored by ADB