During the development of projects, it is often necessary to use ADB command for debugging. When the mobile phone is connected to the computer and ready to use adb shell command, the following error occurs
jason@zhanghailongdeMacBook-Pro ~ % adb shell
error: more than one device/emulator
According to the error prompt, the error is caused by the connection of multiple devices on the computer, and adb shell command does not know which one to operate, so the error is exploded. Check with ADB Devices:
jason@zhanghailongdeMacBook-Pro ~ % adb shell
error: more than one device/emulator
According to the error prompt, the error is caused by the connection of multiple devices on the computer, and adb shell command does not know which one to operate, so the error is exploded. Check with ADB Devices:
jason@zhanghailongdeMacBook-Pro ~ % adb devices
List of devices attached
LGUS9982d76c740 device
192.168.201.7:5555 device
Sure enough, several devices appear. If you want to debug for a particular device, you need to specify the name of the device for adb command, such as debugging for device 2F54EE0:
jason@zhanghailongdeMacBook-Pro ~ % adb -s LGUS9982d76c740 shell
Joan:/$
In this way, it is possible to debug normally. If there is still a problem with the above method, the following scheme is recommended:
// Kill adb Server first :adb kill-server
// Restart ADB Server: ADB Start-up – Server
Read More:
- How to eliminate ADB error “more than one device and emulator”
- Error: ADB prompts device unauthorized
- [Solved] adb shell error: error: device unauthorized
- adb shell error: device offline [How to Solve]
- On the error report after the command of ADB shell error:device not A solution of found
- The ADB server port is changed to 10001, and appium cannot connect to the device
- Error while waiting for device: Time out after 300seconds waiting for emulator to come online
- Android error: ADB port is occupied( adb.exe ,start-server’ failed — run manually if necessary)
- Android ADB command adb devices error: protocol fault (no status)
- An error is reported after Android studio creates a new virtual machine. Emulator: emulator: error: unknown AVD name
- An error is reported when starting the Android emulator: Emulator: audio: Failed to create voice `goldfish_audio_in’
- How to Fix adb_server_notify: ADB server connection failed
- Ubuntu cannot access USB device, failed to create a proxy device for the USB device
- After adb is connected to an android phone, remount failed: operation not permitted when adb remount is a roundabout solution
- [Solved] adb shell error: no devices/emulators found
- [Android test] solution for error closed after the carriage return of the ADB shell
- device no response, device descriptor read/64, error -71
- ADB connection error
- You must restart ADB and eclipse
- Solve the problem that the connection between ADB and nocturnal God cannot be solved