first of all, there are two possibilities:1. Just do not configure the environment variable, this only need to install Android: for example, C:\Program File\android-sdk-windows\tools added to the system variable path, it should be noted that path will be configured with other paths, You need to add it to the Android path, and then paste the path above it to make it OK. 2. Whether the environment variable is configured to enter ADB in cmd or "ADB is not an internal or external command", then swipe down: I found many ways to configure the Android environment variables on the Internet when I first learned Android. Also according to their statement to configure the environment variable Android, and then enter the ADB, others can display a lot of information, but I was wrong, but I am clearly in accordance with the way the internet said to do, and most of the same, I find the wrong ah, find a half a day to find Ah, it is not found, is not the configuration of an environment variable, what good Configuration Ah, later look at the file folder, found in the \platform-tools under the Adb.exe, and in the Tools folder below, the original is such. android2.2 and Android 2.3 are not the same, android2.3 Adb.exe is placed under the Android-sdk-windows\platform-tools directory, And 2.2 is placed under the Tools directory, so I'm the path to Platform-tools below, and then enter the ADB, success!!! There is another workaround:
to see if Adb.exe is in the Platform-tools folder of the SDK, and if so, add the path to the environment variable path, as my environment variable adds: D:\android-sdk-windows\ Platform-tools if not, you can download Adb.rar on the Internet; after extracting the three files inside the system System32 folder, and then enter the ADB under DOS See if there is a missing AdbWinApi.dll file error, then look down, copy the AdbWinApi.dll file again to the system directory under the systems directory, OK, now enter the ADB test. Okay, it's done.
