This guide will outline the steps to fix numerous types of ADB and Fastboot errors. If you are planning to step into the custom development, then ADB and Fastboot Commands are perhaps the two most useful tools that you could or rather should have in your collection. Whether it’s for executing the basic ADB shell commands to booting your device to Fastboot or Recovery modes or even flashing tons of custom binaries [such as the likes of custom ROMs or TWR], these commands will come in handy at every step of your journey.
However, you might come across quite a few roadblocks during this journey as well. Thse include the likes of the PC being unable to identify the connected device, refusing to accept the commands even though you have typed them correctly, failing to identify a particular partition of your device, well this list could go on and on.
While the inability to correctly execute these commands is a cause of infuriation, however, there’s a bigger concern looming around- in some instances, issues and errors with ADB and Fastboot Commands might even lead to the device being in a bootloop or bricked state. So to avoid all that from happening, it’s of paramount importance to address these issues at the earliest. Without further ado, let’s get started with the fixes.
Different Types of ADB and Fastboot Errors
You might come across quite a few types of ADB and Fastboot errors, with the below-listed issues being the most common and prominent ones. Fortunately, the fixes that we have listed in this guide will be more than enough to resolve all these problems.
- Waiting for Device Error in ADB or Fastboot Commands
- Android Device Stuck in Fastboot Mode
- adb server version doesn’t match this client; killing.
- ADB Device not found [List of Devices Attached is blank]
- adb is not recognized
- Unauthorized Device with ADB Commands [3 methods]
- Device Stuck in No Command Screen
- Failed (remote: ‘flashing is not allowed for critical partitions)
- FAILED (remote: Partition should be flashed in fastbootd)
- fastboot: error: Couldn’t parse partition size ‘0x’
- FAILED (remote: Command not allowed)
- FAILED (remote: Check device console)
- Fastboot Erase System Command Not Working.
How to Fix Various Types of ADB and Fastboot Errors
Given hereby are some nifty workarounds that should help you rectify various types of ADB and Fastboot errors. Try out all of them and see which works out in your favor.
FIX 1: Try USB Tweaks
The first course of action should be to use the USB 2.0 ports on your PC instead of the 3.0 ports [the blue one]. While the latter is the faster one, however, sometimes it might end up conflicting with the command execution process. Therefore, use the 2.0 Port on your PC, and on top of that, also consider switching over to a different USB cable.
Talking about cables, while it is always recommended to use the one that came with your device, however, in some cases, using one from a different OEM might also get the job done. So carry out these USB tweaks and then check out the results.
FIX 2: Toggle USB Debugging
Next up, consider disabling and then re-enabling USB Debugging on your device. This will refresh the debugging settings on the device and might rectify the issue that we are currently dealing with. So let’s give it a try using the below-listed steps and then check out the result. [NOTE: If you haven’t yet enabled Debugging, then do it first using our guide on How to Enable USB Debugging on Android Devices]
- Head over to Settings > System > Developer Options.
- Then disable USB Debugging and unplug your device.
- Now replug your device and re-enable USB Debugging.
FIX 3: Update Android SDK Platform Tools
Using an older version of Android SDK Platform Tools might also result in various types of ADB and Fastboot errors. Therefore, it is recommended that you should be on the latest version, which could be done using our detailed guide on Download and Install Android SDK Platform Tools.
FIX 4: Open CMD inside Platform Tools
It is always recommended to open the Command Prompt window inside the platform-tools folder directory. In this regard, there are two different approaches that you could opt for:
- Head over to the platform-tools folder, type in CMD in its address bar, and hit Enter.
- Head over to the platform-tools folder and copy its path from its address bar. Then launch CMD from the Start menu and type in cd <paste the path here>.
FIX 5: Re-Authorize USB Debugging
Next up, consider removing the USB Debugging authorization from your PC and then re-authorizing it from scratch. Here’s how it could be done:
- Head over to Settings > System > Developer Options.
- Then tap on Revoke USB Debugging Authorizations > OK.
- Now open the Command Prompt inside platform tools.
- Then type in the below command in the CMD window:
adb devices
- An authorization request will pop-up, tap Allow/Grant/OK.
- Now try executing the command and check out the results.
FIX 6: Restart ADB Server
In some cases, the ADB server might not be able to function along the expected lines. Therefore, you should consider stopping and then restarting the server, as explained below.
- Launch Command Prompt inside the platform tools.
- Then type in the below command to stop the server:
adb kill-server
- Now type in the below command to restart the server:
adb start-server
- Check whether it fixes the ADB Fastboot errors or not.
FIX 7: Add ADB to Path
If the platform-tools directory is not added to the system path, then the OS will not be able to identify the location of the platform-tools folder. Therefore it is advised that you add Android SDK to the system path using the instructions given below:
- First off, copy the path where you have the Android SDK Platform Tools.
- Head over to the Start menu and search View Advanced System Settings.
- Then go to the Advanced tab and click on Environmental Variables.
- Now select Path under System variables and click on Edit.
- Now click on New, paste the copied path, and hit OK > OK.
That’s it. These were the various methods that should fix the various types of ADB and Fastboot errors and issues. All the queries regarding the same are welcomed in the comments section below.
