@Overcook3265 recently ran through the System Setup steps and encountered issues with adb not being found, with an bash: adb: command not found error message:
martin@DESKTOP-UJBONIT MINGW64 ~
$ adb
bash: adb: command not found
which adb yielded the following (not including the PATH addition by @Josehower in #18 mentioned below):
martin@DESKTOP-UJBONIT MINGW64 ~
$ which adb
which: no adb in (/c/Users/marti/bin:/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/mingw64/bin:/usr/bin:/c/Users/marti/bin:/c/Python312/Scripts:/c/Python312:/c/Program Files (x86)/Common Files/Intel/Shared Libraries/redist/intel64/compiler:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/WINDOWS/System32/WindowsPowerShell/v1.0:/c/Program Files (x86)/QuickTime/QTSystem:/c/WINDOWS/System32/OpenSSH:/c/ProgramData/chocolatey/bin:/c md:/c/Program Files/nodejs:/c/Program Files/Microsoft VS Code/bin:/c/Program Files/PostgreSQL/16/bin:/c/ProgramFiles/Docker/Docker/resources/bin:/c /Users/marti/AppData/Local/pnpm:/c/Users/marti/AppData/Local/Microsoft/WindowsApps:/c/Users/marti/AppData/Roaming/npm:/c/Users/marti/.fly:/c/Users/m arti/AppData/Local/Programs/Hyper/resources/bin:/c/Users/marti/AppData/Loc al/GitHubDesktop/bin:/us/bin/vendor_perl:/usr/bin/core_perl:/c/Program Files/PostgreSQL/16/bin)
where adb was also not helpful:
martin@DESKTOP-UJBONIT MINGW64 ~
$ where adb
INFO: Could not find files for the given pattern(s) .
Support for adb in the PATH location $HOME/AppData/Local/Android/Sdk/platform-tools was added by @Josehower in this PR:
- Add adb path instructions to windows setup #18
@ProchaLu will:
- Find a Windows machine and remove any existing Android Studio things /
PATHconfiguration - Try the System Setup Android Studio steps on Windows
- Including the System Setup step to check whether
adbruns
- Including the System Setup step to check whether
- Document the results in this issue
- If
adbdoesn’t run, debug the problem and create a PR fixing it
ADB and fastboot tool are some of the most powerful tools for Android devices, when it comes to rooting, unlocking bootloader or if you want to flash firmware, everything can be done in one single place that is ADB and fastboot. However, it is not easy to use ADB and fastboot commands, often people end up with a lot of different types of errors. Sometimes it says ADB is not recognized or ADB command not found, there are a lot of different errors similar to these. So here is some easy fix through which you might be able to fix your ADB command error.
Below is a list of some errors and their fixes that might help in fixing your error which you are facing during the ADB commands.
Reasons why you get an ADB Error
There could be several different reasons for the error you are getting while executing the ADB command.
Sometimes drivers are missing while at times permission access are missing. Below we have quoted some of the error messages that often appear while executing ADB commands.
‘adb’ is not recognized as an internal or external command, operable program or batch file.
‘adb’ is not recognized as an internal or external command react-native.
The command a.exe was not found, but does exist in the current location.
or
The command adb was not found, but does exist in the current location.
‘adb’ is not recognized as an internal or external command android studio.
In case you are using Powershell instead of Command Prompt to execute ADB Commands then you might go through the following errors.
ADB : The term ‘adb’ is not recognized as the name of a cmdlet, function, script file, or operable program.
‘adb’ command not found
‘fastboot’ command not found
‘fastboot’ is not recognized as an internal or external command, operable program or batch file.
Let’s begin with the very first and most common error that most of the users have which is “adb is not recognized as an internal or external command “. This error could occur due to the following reasons.
- For starters, ADB and fastboot tools is an external software tool which you need to download and install it manually on your PC. it doesn’t come pre-installed on your computer on any of the OS be it Windows, Mac or Linux.
- You may also face errors like the ‘ADB command not found error, this happens mostly because of an outdated version of ADB and the fastboot tool, so always make sure that you have the latest version of SDK and Platform tools.
- Make sure that you are executing the ADB commands from a location where ‘adb.exe’ and ‘fastboot.exe’ file is present otherwise it will show errors while executing the commands.
- If you are trying to flash an OTA zip file, a factory image or a custom recovery then you must make sure that the file which you are flashing is located in the same folder where the ADB is installed or inside the platform-tools folder along with ‘adb.exe’ and ‘fastboot.exe’
Fix for ‘ADB is not Recognized’ Error
There are several different solutions that can work and solve the error ADB is not recognized, so below we have listed a few of the solutions that you can check and try to solve your issue with ADB and fastboot.
There are several different versions of ADB and fastboot tools lying around the internet, many of them are outdated versions as well. For instance, if you are using the ADB and fastboot tools of Koush’s Universal ADB drivers or Minimal ADB and Fastboot, 15 seconds ADB Installer chances are that you are running an older version of the ADB and Fastboot tools. This means that the driver of the Adb is also outdated on your Windows PC. Not to mention, these older versions and installers from third-party sources can also contain some kind of malware that can harm your PC as well.
You must try to remove the tool as soon as possible. The safest and the most reliable way to download and install the ADB and Fastboot tool driver is by downloading it directly from Google’s own website. Thus, we would recommend you to download the latest version of Android SDK Platform Tools zip For Windows directly from the development website of Google.
As we all know that the original ADB and fastboot tool drivers are not the installer files and we just extract it and start using it by opening the command Prompt on that location of the Platform-tools folder, so there are 3 ways to open cmd.
- Open the Platform-tools folder that contains the ADB and fastboot files. Now, in the address bar of that folder type cmd and press the Enter key on your keyboard.
- Open the Platform-tools folder. Next, click on the file tab which should be somewhere at the top left of the screen, now select open Windows Powershell from the context menu.
- Navigate into the Platform-tools folder, now in the empty area of the folder press and hold shift and then press the right click of your mouse. now from the context menu select open Command prompt/ Windows Power Shell.
So if you have saved the ADB and Fastboot drivers in the C drive and you are trying to run an ADB command from the desktop screen, you will get an error as ‘adb is not recognized as an internal or external command error’.
To fix this, all you have to do is
- Open the platform-tools folder now from that folder click on the address bar and copy the whole path.
- Go back to the command prompt and then type cd <Space> paste the path and then press enter.
- That’s it now you can try executing the ADB commands and it should not show the error.
Fix 4: Add a User or System variable path For ADB And Fastboot
The method we used above in which we wrote the path of the platform-tools folder using the cd command works pretty well but could be a bit complex and lengthy if you use ADB and fastboot very frequently. So in that case we can use the system variable path method, using it will be very easy to access ADB and fastboot tool universally from any screen or location on your Windows PC. All we have to do is set up the ADB system-wide.
To add System or User Variables for the path of the platform-tools folder follow the tutorial written below.
- Open Advanced System Settings on your Windows PC.
- to go to advanced settings simply click on the windows button and then type Advanced system settings.
- Now Click on Environment Variables as shown below.
- Now, click on the new button under system variables, for reference look at the screenshot below.
- Now, in the new dialogue box that opened, type Path in the Variable name box, and inside the variable box you need to enter the path of the Platform-tools folder, simply copy and paste it from the address bar when inside the platform-tools folder. for reference, you can check the screenshot.
- Finally, click on Ok to add the path variable.
- Also, click on Ok in the previous screen which is Environment variables otherwise it won’t work.
That’s it you have successfully set up the variable path for ADB and fastboot tool and now you can access ADB commands from anywhere inside the PC be it any location.
Fix ‘adb.exe:no device/emulators found’ Error
Whenever ADB daemon is not able to detect your device due to some of the other reasons it will always show an error saying ‘adb.exe no devices/emulators found. So to fix the error follow the tutorial written below.
- One of the reasons could be that the phone or tablet is not connected to your Pc, you might need to check the cable or the quality of the cable, make sure you are using an original cable, some of the devices causes conflicts when using any other cable.
- Cross-check once whether USB-Debugging on your Android device is enabled.
- Try restarting your device and disconnect the cable and connect it again.
Bonus Tip: Allow USB-Debugging Permission
Whenever you use the USB-Debugging first time on your PC and phone you have to give authorization from your phone which allows your PC to use USB-Debugging, otherwise, none of the ADB commands would work.
So as soon as you run your first ADB command, you will see a pop-up on your phone asking to ‘Allow USB-Debugging’ click on Allow button and that’s it you have successfully given the USB-Debugging permission.
We have a whole guide for this issue: Allow USB Debugging | Authorize ADB Commands on Android
Fix ‘Fastboot is not Recognized’ Error
So all of the above-mentioned solutions were to fix the errors with ADB or ADB commands not recognized error. The above solutions might also fix the error of fastboot commands as well. otherwise, if you are still getting the ‘fastboot not recognized error then you can try the below method which might fix your error. Fastboot commands are those commands which you execute on the ADB platform when your phone is in Recovery or bootloader or fastboot mode. Mostly this is used to flash a custom recovery such as TWRP or to unlock the bootloader of your device.
- Make sure you have downloaded the latest version of platform-tools SDK from the links provided above.
- Now, open the Platform-tools folder
- First of all, copy the files you want to flash on your Android device, and paste them inside the platform-tools folder, the same folder which should also have files like ‘fastboot.exe and adb.exe’
- Now, reboot your Android device into fastboot mode. to do so simply execute the ADB command by writing
adb reboot fastboot. - Make sure your phone is connected to your Pc with a proper compatible cable.
- Now launch the Command Prompt from the platform-tools folder, the same way we do for ADB commands.
- Now type and execute
fastboot devicesthe command will show the list of devices connected to your PC. - If you cannot see any device in the list that means the device isn’t connected properly or there is some issue. You can try disconnecting the USB cable and connecting again to your PC if it doesn’t help then you can try to reboot your phone and check if USB-Debugging is enabled or not.
To Conclude
ADB and fastboot tool is used a lot of time in everyday life of rooting or unlocking the bootloader or if you are a pro-Android user, so having these solutions to fix the errors of ADB can be handy. Above ae have covered how to fix the error ADB device not recognized along with fastboot is not recognized error as well. So make sure you go through all of the solutions provided to you to minimize the chances of error and if you are having any error you might fix it with the help of the abovementioned solutions.
ADB not recognized found error, the ADB and Fast boot are amazing command line tools for your computer that lets you communicate with your Android device and monitor the changes you’ve made to your phone.
ADB and Fast boot have saved the day countless times, ADB not recognized found error making it possible to quickly access our phones whenever we locked them or connect a whole host of accessories through OTG cables to create exciting new experiences.
Having said that, sometimes it can get a little tricky when trying to use ADB or Fast boot on devices as they aren’t always easily detected by the commands without some easy fixes.
Below is a list of just a few of the ADB commands that can be used to accomplish a number of functions.
- Change Android device name
- Uninstall system apps without root
- Turn Safe Mode On or Off
- Unlock Android bootloader
Possible Reasons behind ADB Error
When you are trying to access your Android device using the Windows Command Prompt in order to install apps or run other technical operations, and you get the “ADB is not recognized” error message, you may be wondering:
What could possibly have gone wrong? Below is a screenshot that demonstrates the “ADB is not recognized” error on my Windows 10 computer.
‘ADB’ is actually a command line tool that you can use for Android Studio. To read more about the utility and its different functions, click here .
‘ADB’ is not recognized as an internal or external command. ADB not recognized found error If you are getting this error while using ‘react-native’ on a Mac computer then make sure you have the Android SDK with platform tools installed (also, updated).
Otherwise, check to see if it may be an issue with your computer’s security setting.
The command “a.exe” could not be found. It exists in the current location.
The command “ADB” does not exist in the folder, but it exists at the root of the directory.
It’s not immediately clear how the term “ADB” relates to the most common computer-related activities that we do everyday.
When you try to create a file in Windows PowerShell, you can’t and will get this message:
ADB: The term ‘ADB’ is not recognized as the name of a cmdlet, function, script file, or operable program.
‘ADB’ command not found
‘fast boot’ command not found
Fast boot is not recognized as an internal or external command, operable program or batch file.
If you’re getting the “ADB is not recognized as an internal or external command” error when attempting to use the command prompt to access your device, there could be a few reasons why it isn’t working.
- Many people think that ADB and Fast boot are present on their Windows PC by default. The reality is, you must download and set up the ADB and Fast boot drivers additionally.
- You may also get the “ADB command not found” error if you have an outdated version of ADB and Fast boot drivers. Installing the latest Android SDK Platform-tools on your PC might fix the problem.
- If you are trying to run ADB command from a location where ‘adb.exe’ and ‘fastboot.exe’ are not present.
- You haven’t set up system-wide ADB and Fast boot on your Windows 10 PC. That’s to say, you haven’t set the correct path under User variables or System variables.
- In case you are trying to flash an OTA update.zip, a factory image, or a custom recovery image (twrp.img, for instance), make sure you have saved the files to flash in the ‘platform-tools‘ folder along with ‘adb.exe’, ‘fastboot.exe’, etc.
If you are receiving the ‘ADB or fast boot command not found error’ on Mac, do not despair! ADB not recognized found error Do a web search for an effective fix and it will appear.
Fixing ‘ADB is not Recognized…’ Error
Now that we know what could be the reason behind the “ADB is not recognized as an internal or external command” error, let’s try to solve it.
Fix 1: Download Latest SDK Platform Tools
There is now a new tool for ADB & Fast boot called “Fast boot Mode” that works very similar to the following tools.
This makes it easy to check if your drivers are up-to-date or not, and you can use this app to update the latest one if they aren’t already.
It also lets you restore a stock image on your device in case anything ever goes wrong. Having this extremely simple yet powerful tool around can be very handy in case something goes wrong.
You must remove any existing third-party drivers for this device. To do that, go to ‘Settings’ > ‘About Phone’. There you will see your device’s build number.
After you’ve found it, ADB not recognized found error go to Google developers’ site and download the latest version of ADB and Fast boot Drivers (right click on the link in your browser and select “Save link as…” option).
This is one of the best sources because it’s provided directly by Google itself. The latest available platform tools can be found here . In case you are out of date, I’d suggest updating them.
Fix 2: Execute ADB Command from the ‘platform-tools’ Folder
Since the ADB driver doesn’t have an installer for it and it is downloaded as a .zip file, you’ve got to manually direct your command prompt to the proper location. You can do this by altering your system variables or changing registry keys.
- Open the ‘platform-tools‘ or the folder that contains the ADB and Fast boot files. Click in the folder address bar, type “CMD” and press the Enter key.
- Open the ‘platform-tools‘ folder. Click on the file explorer’s File tab and select Open Windows PowerShell.
- While in the ‘platform-tools‘ folder, hold the Shift key and right-click at an empty or white space (highlighted with yellow) in the folder window. ADB not recognized found error Select the Open PowerShell window here option from the context menu. If you want, you can add a permanent option to launch the command prompt to the Windows context menu.
Fix 3: Use ‘platform-tools’ Folder Path in CMD
Suppose you have saved the ADB and Fast boot drivers in the C Drive (which most people will when they are setting up their environment for Android Development) for convenience and you use Windows as an OS.
And you decide to launch a Command Prompt as Administrator on your C Drive, but give it an argument of “ADB” to boot up the device… except that you won’t see it. Instead, you’ll get this error:
As simple as the ADB command may be, ADB not recognized found error some of the users have reported errors related to this particular command.
To solve this problem and make debug configurations working properly without causing any issues, you should use a reliable solution.
By using Change Directory (cd) or Chdir command, you can make all mentioned functionalities working without any issues.
This easy-to-use command will allow you to get rid of the problems with ADB . Simply open Command Prompt and type cd followed by platform-tools folder path; for example:
cd c:\technastic\platform-tools
When you want to know what the path is for a particular file or folder, these are the 7 ways that you can find out. In this example, we show how to find the path for an android device such as when using ADB.
‘ADB’ is not recognized as an internal or external command, operable program or batch file.
When I tried to execute a command like “cd c:\technastic\platform-tools” and it didn’t work, which caused an error message (at least in my case) something along the lines of “ADB is not found.
But when I simply changed the location directly by typing exactly what it said and hit return, ADB started working again.
Fix 4: Add a User or System Variable Path for ADB and Fast boot
Although the CD method works well, I find it to be a bit inconvenient because you need to type the folder path every single time you use ADB or ADB Shell commands.
The easiest way to access ADB and Fast boot universally from any screen on your Windows-powered machine is to set up system-wide android debugging tools. ADB not recognized found error Claim your free Ultimate Guides Checklist.
An Android SDK Manager is a program that developers can use to update their Android SDK in case of a new release.
The Android Software Development Kit (SDK) is the package you need to install on your computer in order to develop an application for an android device.
The software comes with: user friendly interfaces, ADB not recognized found error documentation and samples, emulator images, tools and other developer aids.
- Open Advanced system settings on your Windows PC. You can go to those settings in 3 ways.
Done! You have successfully set up system-wide ADB and Fast boot on your Windows PC. ADB not recognized found error Now, you are all set to execute ADB or Fast boot commands from any screen without navigating to the ‘platform-tools’ folder. The best way to utilize these benefits is by using a launcher app like Launch By Fayce .
Fix ‘adb.exe: no devices/emulators found’ Error
If you are getting an error about not being able to detect a device or emulator, then it’s likely because the ADB daemon is failing to initialize as necessary.
There are many possible causes for this – such as having a firewall switched on, or not being able to connect because your IP address isn’t visible in order to be reached.
ADB not recognized found error, the best way to get around this is by making sure the appropriate ports are forwarded and that the IP address on the system is visible so that ADB can communicate with it properly.
- Your Android phone or tablet is not connected to the computer.
- You haven’t turned on USB debugging from the Developer options on your device.
Take care to make sure you have the above things done, then reconnect your device and try again. This should permanently resolve the error points.
Bonus Tip
In order to help your Windows computer communicate with your Android device, ADB not recognized found error you must keep USB debugging enabled on your device.
Also don’t forget to extend the screen timeout duration. As soon as you run the first ADB command, you’ll be prompted to Allow USB debugging on your device. You must select “Allow” to authorize ADB.
If the ADB was already installed, re-install it by installing SDK Platform Tools. ADB not recognized found error You will find this in Platform-Tools folder in your Android SDK installation directory.
If after that you still have issues with Windows, try installing Google USB Driver for Windows.
ADB
ADB devices
ADB version
Fix Fast boot is not Recognized Error
The ADB or ADB command not recognized errors can be fixed using the following recommendations.
‘fast boot’ is not recognized as an internal or external command, ADB not recognized found error operable program or batch file.
Although, if you’re still getting the Fast boot is not recognized error after flashing TWRP.img file, ADB not recognized found error or installing a factory image, or rooting your android device, here’s how to fix it.
The solution should also work if fast boot isn’t detecting a connected device.
- First of all, make sure you have downloaded the SDK Platform tools from above and extracted the downloaded zip file.
- Open the ‘platform-tools‘ folder.
- Now, copy or move the files you want to flash to your Android device to the same folder where ‘exe‘ and ‘fastboot.exe‘ files are present.
- Reboot your Android device into the Fast boot Mode using the following command
adb reboot fast boot
- While your device is in Fast boot Mode, use a compatible USB cable to connect it to the PC.
- Then launch a command window from the ‘platform-tools‘ folder. I have already described 3 ways to do that above.
- It’s time now to execute the following command.
Fast boot devices
- If you get the list of attached devices in the command window, it means everything is fine. However, if encounter any of the following issues, try plugging out the USB cable and insert it again. If it still doesn’t help, try to reboot your phone and PC and try again.
- Fast boot not detecting device
- Fast boot devices not showing in CMD
- Fast boot waiting for device
The Fast boot is not recognized error should be gone. ADB not recognized found error (with a period and no txt file)
If you are still experiencing issues related to ADB and Fast boot, ADB not recognized found error then please let us know.
Hello, My name is Shari & I am a writer for the ‘Outlook AppIns’ blog. I’m a CSIT graduate & I’ve been working in the IT industry for 3 years.
Android Debug Bridge allows us to debug Android devices and modify the system from a command window. However, if you have not set up Android SDK platform-tools on your computer properly and enabled USB debugging on your device, they can’t recognize and communicate with each other. We have shared some solutions to fix the “ADB is not recognized as an internal or external command” error on Windows 10 and 11.
Possible Reasons for ADB and Fastboot Errors
There may be various reasons you are encountering the “adb is not recognized…” error in the Command Prompt. Depending on the scenario, the error message you get may differ. Below is a screenshot of the error I recreated on my Windows 10 PC.
'adb' is not recognized as an internal or external command, operable program or batch file.
So, if you’re getting the “adb is not recognized as an internal or external command” error in the CMD or PowerShell, it could be due to one of the following reasons.
- Windows PCs don’t come with ADB and Fastboot drivers pre-installed. You must download and set up the Android SDK platform tools separately.
- You may get the “ADB command not found” error if you have an outdated version of ADB and Fastboot drivers. Installing the latest SDK platform tools on your PC might fix the problem.
- Running the ADB command from a location where ‘adb.exe’ is not present might also cause errors.
- You haven’t set the correct path under User variables or System variables while setting up system-wide ADB on your PC.
- In case you are trying to flash an OTA update.zip, a factory image, or a custom recovery image, make sure you have saved the files to flash in the ‘platform-tools‘ folder along with ‘adb.exe’, ‘fastboot.exe’, etc.
- Ensure your Android phone is connected to the computer in file transfer mode. ADB won’t recognize the connected device in the Charging mode.
- If you’re a Samsung user, navigate to Settings > Security and Privacy and ensure Auto Blocker is disabled.
Fixing ‘ADB is not Recognized…’ Error
ADB and Fastboot commands won’t work on your Windows PC unless you open the PowerShell or Command Prompt with the path of the folder containing the files from the SDK platform tools. The fixes suggested below will solve the ADB and Fastboot errors.
Fix 1: Download Latest SDK Platform Tools
Remove and uninstall any 3rd-party ADB client if you have it installed. Download the latest version of Android SDK platform tools for Windows directly from Google servers. Always ensure to have the latest ADB drivers on your PC.
Fix 2: Execute Commands with the Path to ADB
Since the official ADB and Fastboot drivers are not installer files, you must direct the Command Prompt to the exact path or location of the ‘platform-tools‘ directory. Now, there are 3 ways to do that.
- Open the ‘platform-tools‘ or the folder where you saved the ADB and Fastboot files. Click the folder address bar, type “powershell” or “cmd” and press Enter.
- Open the ‘platform-tools‘ folder. Click the File tab in the file explorer window and select Open Windows PowerShell.
- With the ‘platform-tools‘ folder in focus, hold the Shift key and right-click at an empty area in the folder window. Select Open PowerShell window here or Open in Terminal from the context menu. You can add a permanent option to launch the command prompt to the Windows 10 context menu.
Fix 3: Use the ‘platform-tools’ Folder Path
Another way to add the path to the ‘platform-tools’ folder in the command window is using the cd or chdir (change directory) command. This command tells PowerShell to trigger ADB or Fastboot from a given path. Just launch the command window and type cd followed by the platform-tools folder path and hit Enter.
cd c:\technastic\platform-tools
Fix 4: Add a User or System Variable Path for ADB
Although the CD method gives the expected result, it’s time-consuming as you need to type the folder path every time you use ADB. The easiest way to access ADB and Fastboot universally from any screen on your Windows PC is to set up system-wide ADB and Fastboot.
This method involves adding System or User Variables for the path of the ‘platform-tools‘ folder and below we’ll see how to do that.
- Open Advanced system settings on your Windows PC. You can go to those settings in 3 ways.
- Type ‘Advanced system settings‘ in the Windows search bar and launch it.
- Right-click This PC on the right pane in the File Explorer window and click on Properties> Advanced system settings.
- Open the Control panel and navigate to System and Security> System> Advanced system settings.
- Once you get to the System Properties pop-up window, click Environment Variables.
- A new pop-up window named Environment Variables will appear. Click on any item under User variables or System variables and click on New.
- When the New User/System Variable pop-up appears, type “Path” under the Variable name, then click on Browse Directory. Navigate to the ‘platform-tools‘ folder and click on the OK button.
- Finally, click OK to add the path variable.
- Next, click OK in the Environment Variables window to save it.
Done! You have successfully set up system-wide ADB and Fastboot on your Windows PC. Now, you can execute ADB or Fastboot commands from any screen without navigating to the ‘platform-tools’ folder.
Fix ‘adb.exe: no devices/emulators found’ Error
If you are getting adb.exe: no devices/emulators found error it means that the ADB daemon is unable to detect your device. It might be due to the following reasons.
- Your Android phone or tablet is not connected to the computer.
- You haven’t turned on USB debugging from the Developer options on your device.
Take care of the above things, reconnect your device, and try again. The error should have gone away.
Bonus Tip
So that your Windows computer can communicate with your Android device, you must keep USB debugging enabled on your device. Not just that, don’t forget to extend the screen timeout duration. As soon as you run the first ADB command, you’ll be prompted to Allow USB debugging on your device. You must select ‘Allow‘ to authorize ADB.
Launch the Command Prompt or Windows PowerShell again to check whether the ADB is not recognized… error is fixed. Try any of the following commands:
adb
adb devices
adb version
Fix Fastboot is not Recognized Error
The fixes I suggested above to solve ADB or ADB command not recognized error will also fix the following issue.
'fastboot' is not recognized as an internal or external command, operable program or batch file.
However, if you’re still getting the Fastboot is not recognized error while flashing the TWRP.img file, a factory image, or root your Android device, here’s how to fix it. The solution should also work if Fastboot is not detecting a connected device.
- Download the SDK platform-tools and extract the zip file.
- Open the ‘platform-tools‘ folder.
- Now, copy or move the files you want to flash to your Android device to the same folder where ‘adb.exe‘ and ‘fastboot.exe‘ files are present.
- Reboot your Android device into the Fastboot Mode using the following command.
adb reboot fastboot
- While your device is in Fastboot Mode, connect it to the PC via USB.
- Then launch a command window from the ‘platform-tools‘ folder.
- It’s time now to execute the following command.
fastboot devices
- If you get the list of attached devices in the command window, it means everything is fine. However, if you encounter any of the following issues, try plugging out the USB cable and inserting it again. If it still doesn’t help, try to reboot your phone and PC and try again.
- Fastboot does not detect the device
- Fastboot devices not showing in cmd
- Fastboot waiting for the device
The Fastboot is not recognized error should be gone.
If you are still getting any ADB or Fastboot-related issues, ping us so we can assist you in fixing them.
Was this Article helpful?
YesNo
% adb devices
zsh: command not found: adbIf you are trying to run a adb command on the Mac Terminal and you get the error «zsh command not found adb» then the most common issue reasons for this is as follows.
Reasons for the error
- You are not running the adb command-line tool from the directory its located in.
- The adb path is not set in the .zshrc profile file.
Fix/Solution
Make sure you are inside the location where adb tool is located.
Example:
% cd ~/Library/Android/sdk/platform-tools
% ./adb version
Android Debug Bridge version 1.0.41
Version 34.0.4-10411341
Installed as /Users/c2ctechtv/Library/Android/sdk/platform-tools/adb
Running on Darwin 23.0.0 (arm64)Its better to add this path to the .zshrc file.
- Open .zshrc file.
nano ~/.zshrc - Add the below line to the zshrc file.
export PATH="$HOME/Library/Android/sdk/platform-tools:$PATH" - Control + X and Y followed by Enter to save changes to the file (if using Nano)
- Run source ~/.zshrc to apply changes
You can download this article in various formats for your convenience. Choose from the options below:
Facing issues? Have Questions? Post them here! I am happy to answer!
Provide Feedback For This Article
We take your feedback seriously and use it to improve our content. Thank you for helping us serve you better!