What should I do if I get an error error when I run the adb shell?

Enter adb in command line (just start-run-cmd) mode

Shell commands typically report two types of errors: "adb is not an internal or external command, nor is it a runnable program or batch file", or "error:device not."

found”。

For the first error, it's because the environment variable isn't configured. The so-called environment variable is the information to be used by each application, and the main thing here is that the path path is not configured, and the path is. exe and.

The path where the BAT program is executed. Because when entering a command in the command line, the computer will first look for the program in the current directory (usually C: user administrator), and if it does not find it, it will find it through the path in the environment variable (the paths in the path are in English format; If there is no program in each path in the path, the error "adb is not an internal or external command, nor is it a runnable program or batch file" will be reported.

There are two solutions: one is to add the path to the path path, which is located in the platform-tools directory of the SDK, such as my Android

The SDK file is located under D: Android, then the correct path path should be "D: Android Android-SDK-Windows Platform-Tools".

Append this string of characters to the path of the system or user environment variable; The second is to enter the patform-tools directory in the DOS environment first, take my machine as an example, and use "cd".

d: android android-sdk-windows platform-tools" command into the platform-tools directory, and then use "dir" (windows) to see that there are files in the list, then run "adb".

shell" command on the road.

For the second type of error, it is because the android virtual machine is not turned on. Because of ADB

The shell command is actually an operation on the current virtual machine, and you need to enter the file structure of the current virtual machine. If the VM is not enabled, this command will of course report "error:device not."

found" error. The solution is to open the virtual machine, make sure the first error is resolved, and enter adb

The shell can enter the structure of the Android virtual machine normally.