What went wrong:
CMD cannot find adb command in path path,
is because the adb.exe file exists in the android-sdk installation directory platform-tools/ subdirectory, and this path is configured into the environment variable.
Solutions:
Add environment variables as described in the book: C:\ Android-SDK-Windows \ Tools, then add
platform-tools to the environment variable
. For example, if The Android-SDK is installed in the root directory of C disk, then add the environment variable: C:\ Android-SDK-Windows \ platform-Tools
Read More:
- Install Android SDK — stopping ADB server failed (code – 1)
- How to Fix adb_server_notify: ADB server connection failed
- 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)
- After adb is connected to an android phone, remount failed: operation not permitted when adb remount is a roundabout solution
- Stop: job failed while stopping
- Solve the problem of garbled code when Python connects to ADB
- The ADB server port is changed to 10001, and appium cannot connect to the device
- Command not found: ADB appears on Mac
- ADB：INSTALL_ FAILED_ UPDATE_ Incompatible [solved]
- SQL Server 2008 R2 MSSqlServer failed to start. Error code 17058
- Winscp failed to upload the file to the server, indicating permission denied with return code 3
- Unable to install SQL Server (setup.exe), VS Shell installation has failed with exit code 1638.
- Solutions to ADB failed to start daemon
- ADB remount failed: operation not permitted
- Android stdio reports an error: “XXX keeps stopping” solution
- Solve the problem that the connection between ADB and nocturnal God cannot be solved
- Error running app:Instant Run requires Tools | Android Enable ADB integration‘ to be enabled.
- Python server run code ModuleNotFoundError Error [How to Solve]
- Vs_ Code remote SFTP connects to the server to modify the nginx configuration information and reports all configured authentication methods failed