Many developers may encounter a problem, that is, each time they use the ADB command, they need to CD to the directory where Android-SDK/platform-tools is located for execution. Otherwise, they will prompt that ADB is not an internal command, how can this problem be solved?
In fact, the system prompts that ADB is not an internal command, that is, the system cannot find this ADB command. Why can't it be found?
The mechanism is the same as that in Linux. The system will find it in the path contained in the environment variable path. if it finds it, it will execute it. If it cannot find it, it will prompt that it is not an internal command, then we can understand that, in fact, we only need to add the path of the Android-SDK to the environment variable path. The specific method is as follows:
1. Choose computer> Properties> advanced system Settings> environment variable> New one.
Here, the name android_sdk_home should not be changed. The value below is the directory where your SDK is located. Note that you only need to go to/....../SDK.
2. In Path, add the following parts:
; % Android_sdk_home %/platform-tools; % android_sdk_home %/tools
Pay attention to the percentage and semicolon position. After setting, you can open CMD and try again.