How to Fix “adb not recognized” Error

ADB or Android Debug Bridge is a command-line tool that is part of the SDK and Android platform tools. This essentially creates a bridge that allows for 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 boot loader, installing a custom recovery, starting your device in recovery or quick start mode, installing APK files, and so on. However, most often, some of the other errors creep in. Of these, the most common is "Adb" is not recognized as an internal or external command, a usable program or a batch file. We will examine the different steps to correct this error "unrecognized adb".

Fixed "unrecognized adb" error fix

The aforementioned error is caused when the command prompt or PowerShell is not able to identify the ADB command. It's because of the missing environmental variable (system) in connection with Android SDK. To correct this "unrecognized adb" error, first make sure to familiarize yourself with the prerequisites described below.

Note that the two points above are just the initial steps of the error correction "unrecognized adb". Likewise, they will not solve the problem until you follow the detailed instructions below.

Add missing environment variables

1. Click on the Windows icon and search Advanced system settings.
2. Then click Environmental variables. This will be the last option, just below Settings.
3. Under the same, you will see two sections: User variables and System variables. We will take care of it by fixing the error "unrecognized adb".
4. In System variables, double-click on Path keyword.
5. the Edit the environment variable the option will now appear. Click on leaf option.
6. Navigate to the location where you installed the ADB and Fastboot binaries and select the platform tools folder. Then click D & #39; AGREEMENT.
7. The selected variable will now be added to the environment variables. Click on D & #39; agreement to close the dialog box.
8. Take a look at System variables under 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 D & #39; agreement again to close the System Properties dialog box.

That's it. The missing environmental variables were added successfully. You have also successfully corrected the "adb not recognized" error. You can now check if the fix is ​​mentioned in the next section.

Check the adb error fix

There are two ways to verify that you have correctly implemented the fix for "unrecognized error" or not. The first involves the use of Command Prompt while the second one is via PowerShell window. For both of these methods, you will first need to navigate to the ADB and Fastboot directories. platform tools folder. Once there, you can try one of the methods below:

• Using the command prompt: It's much shorter and easier of the two methods. Inside of platform tools folder, go to the address bar and type cmd. Press Enter and the command prompt window will appear. Type adb and you should get a long list of ADB commands and their use (as shown in the picture below). If this is the case, the fix for the "unrecognized adb" error has been correctly implemented.
• Using the PowerShell window: Inside of platform tools folder, right-click on an empty area while pressing the shift key. Now select the Open the PowerShell window here option. That's it. Enter adb and seeing a long list of ADB codes (see image below for reference), you would be reassured that the error is no longer there.

It was therefore a detailed guide on how to correct the "adb not Recognized" error. Let us know if you are having trouble while performing any of the above steps.

Read more: ApkTool – Decompile and Edit APK (Windows, Mac & Linux)