in command line (that is, start-run-input cmd) mode, if you enter the ADB shell command, two errors are generally reported. One is that" ADB is not an internal command or an external command, it is neither a running Program or a batch file. The second is "error: device not found ".
for the first error, the environment variable is not configured. The environment variables used by each application need to be used. In this case, the paths for pathstores, path.exe, And. Bat programs are not configured. When you enter a command in the command line, the computer will first report "ADB is not an internal command or an external command in the current directory (generally c: \ User \ Program, it is not a running program or batch file "error. There are two solutions: one is to add the adb.exetoken to the pathpattern, And the adb.exe is located in the platform-tools directory under the SDK directory. For example, if my android SDK file is located under D: \ Android, the correct path should be "D: \ Android-SDK-Windows \ platform-tools ". Append this string to the path of the system or user environment variable. Second, enter the patform-tools directory in the DOS environment. Take my machine as an example, run the "cd d: \ Android-SDK-Windows \ Users" file, and then run the "ADB shell" command.
for the second error, because the android virtual machine is not enabled. Because the ADB shell command is actually used to operate the current virtual machine, you need to enter the file structure of the current virtual machine. If you do not open the VM, this command will certainly report "error: device not found" (that is, the device is not found) error. The solution is to open the Virtual Machine and ensure that the first error has been solved. Enter ADB shell to enter the structure of the android virtual machine.