ADB and Fastboot are two of the most essential tools for your Android device, if you are thinking about rooting, unlocking the bootloader, installing some custom ROM, or flash firmware. However, these two are considered the most complex things to deal with. People face difficulties working with their commands and as a result, end up with different kinds of errors. ADB is not recognized, or ADB command not found are some of the most common errors that you will come across while dealing with these tools.
So, if you are fed up with facing such errors, and looking for a solution to fix them, then you are at the right post. In this post, we will discuss everything about common ADB errors, along with their working solution.
Why ADB Is Not Recognized?
Frankly speaking, there can be more than one reason that you are facing this ADB error. Sometimes, the reason could be the unavailability of a driver, and sometimes it could be related to permission that you have not given. Below-mentioned is some of the common reasons because of which you are facing ADB is not recognized error.
- ADB and Fastboot are external software that you need to download and install on your PC manually, it doesn’t company pre-installed. Therefore, if you are trying to execute the ADB command in Command Prompt without having ADB and Fastboot installed on your PC, then you are most likely to face ADB-related errors.
- ADB and Fastboot related errors are very common with people who have not updated these tools for a long time on their PC. Therefore, make sure you remain updated with the latest updates of SDK.
- Always execute ADB commands from the location where you have “adb.exe”, and “fastboot.exe” installed on your computer. If you are executing ADB commands from a random location then you are most likely to face the consequences in form of error.
- If you are facing ADB errors while trying to flash an OTA zip file, a custom ROM, or a factory image, then make sure that you have this flashing file located in the same place where you have your ADB tools installed.
How To Fix ADB Is Not Recognized Error?
As there is not a particular reason behind the ADB errors, in the same way, there are several ways to solve this ADB error. Below mentioned are all the working methods that will help you to solve “ADB is not recognized as an internal or external command error”.
1. Work With ADB Command From “Platform-Tool” Folder
You must use the exact path or location of the “platform-tools” in the Command Prompt. There is more than one way of doing it.
Step 1: Go to the “platform tools” folder where you have kept the ADB and Fastboot files. In the address bar of that folder, type CMD and press enter.
Step 2: Go to the ‘platform tools‘ folder. Now click on ‘File’ located at the top-left corner, and then click on “Open Windows PowerShell”.
Step 3: In the “platform-tools” folder, press the shift key and right-click on a blank space simultaneously, and then click on “Open PowerShell Window Here”.
2. Use Correct Path In CMD
You will definitely get, “ADB is not recognized as an internal or external command” error if you have kept the ADB and Fastboot files in any place in your C drive, and trying to execute an ADB command by opening the Command Prompt or PowerShell on some other location.
It’s a cakewalk to solve this problem, all you need to do is to work with some Command Prompt commands. Use the “cd” command followed by the platform tools folder path. Look at the image to know how it’s practically done.
3. User Or System Variable Path
Let’s be fair, we want everything quick, no one likes to type in “cd” followed by folder path every time you want to access ADB commands, although this method works it’s quite time-consuming. We can reduce the time consumption by setting up system-wide ADB and Fastboot commands. Here’s how it’s done.
- Right-click on “This PC” in the File Explorer Windows, and then click on Properties.
- Click on Advanced system settings, and then click on Environment Variable.
- Click on any item under “System Variable”, and then click on “New”.
- Under Variable Name, type “Path”, and then click on browse directory select the place where you have saved the platform-tools, and then click on Ok.
- Now keep pressing Ok, on every dialogue box until you were out of the advanced system properties.
That’s it!! Now you can execute ADB and Fastboot commands from anywhere on your PC without facing the trouble of navigating every time to the “platform-tools” folder.
4. Download The Latest SDK Update
As we have mentioned earlier, if you don’t have the latest SDK version installed on your PC then you are most likely to face ADB errors. Koush’s Universal ADB Drivers, Minimal ADB, 15 Seconds ADB Installer, are the names of some ADB tools that really released their update, and if you are using any of these tools then you are most likely to face the ADB error. Moreover, you should avoid using such tools as they may contain harmful viruses.
Never trust any third-party driver. We recommend you install the latest Android SDK tool for Windows from the Google server itself. For your convenience, here’s the direct download link of the Android SDK platform.
So, that’s all the working methods to solve the “ADB is not recognized as an internal or external command” error. All the methods mentioned in this post 100% trustable, and you can completely rely on them. Moreover, if you are aware of any other way to solve the issue let us know in the comments, and don’t forget to share your feedback and suggestions.