ADB or Android Debug Bridge is a command line tool, part of the Android SDK and Platform Tools. It basically creates a bridge that allows successful communication between your Android device and your PC. Some of the most important Android customizations are possible thanks to these ADB commands. These include unlocking the bootloader, installing a custom recovery, booting your device to recovery or fastboot mode, installing apks, and more. However, some unexpected errors pop up from time to time. Among them, the most popular is “adb” is not recognized as an internal or external command, operable program, or batch file. We will look at different steps to fix this Adb not recognized error.
Fix error adb not recognized
The above mentioned error occurs when Command Prompt or PowerShell cannot identify the ADB command. This is due to the variable environment (system) is missing regarding the Android SDK. To fix this error, adb does not recognize this error, first make sure you familiarize yourself with the prerequisites below.
Please note that the above two points are just the initial steps in fixing adb not recognized error. Similarly, they will not fix the problem until you follow the detailed instructions given below.
Add missing environment variables
- Click on the Windows icon and search for Advanced System Settings.
- Next, click Environmental Variables. It will be the last option, just below Settings.
- Similarly, you will see two sections: User Variables and System variables. We will handle the following error in fixing Adb not recognized error.
- In System Variables, double click on the keyword Path.
- The Edit environment variables selection will now pop up. Click option Browse.
- Navigate to the location where you installed the ADB and Fastboot binaries and select the folder platform-tools. Then click OK.
- The selected variable will now be successfully added to the environment variables. Click OK to close the dialog box.
- Watch System variables in Environment Variables. The path section will also have the path of the recently added variable. You can now close this dialog box by clicking OK. Finally, click OK again to close the System Properties dialog box.
That’s it. The missing environment system variables were added successfully. You have also successfully fixed the error Adb does not recognize the error. Now you can go ahead and test the fix as mentioned in the next section.
Check and fix error adb
There are two methods to check if you have successfully performed the fix for Adb not recognizing the error. The first one is related to the use of Command Prompt while the second one is done through PowerShell Windows. For both of these methods, you will have to navigate inside the directory first platform tools ADB and Fastboot . Once you get there, you can try any of the two methods below:
- Using Command Prompt: This is shorter and easier of the two methods. In folder platform-tools, go to the address bar and type cmd. Press enter and the Command Prompt window will pop up. Type adb and you will get a list of ADB commands and its uses (as shown in the image below). If that is the case, then the fix for Adb not being recognized error has been done successfully.
- Using PowerShell Window: Inside folder platform tools , right click on an empty area while pressing Shift key. Now choose option Open PowerShell here. That’s it. Import adb and when you see a long list of ADB codes (see image below for reference) you will rest assured that the error is gone.
So here is a detailed guide on how to fix Adb not recognizing error. Let us know if you face any difficulty while performing any of the steps above.