ADB and Fastboot are essential tools for every Android user. It’s easy to launch a command window inside the ‘platform-tools’ folder. However, if you set up system-wide ADB and Fastboot drivers on your Windows 10 PC, you can launch and execute commands on your Android device from any screen on your computer. The good thing is you can do this without installing any 3rd-party software.
Gone are days when Android users had to download either the full Android SDK or Studio suite or 3rd-party utilities like Minimal ADB and Fastboot, and 15 Seconds ADB Installer. Google now provides the latest Android SDK Platform-tools for Windows, macOS, and Linux as a ZIP that contains all required ADB and Fastboot drivers. Below, I will be sharing a simple tip to help you set up system-wide ADB and Fastboot.
If you have used ADB and fastboot commands, you must be aware that every time we have to perform a task, we must navigate to the ‘platform-tools’ directory and launch the Command Prompt in the folder path to run commands. Having set up system-wide ADB and Fastboot on Windows 10, you’ll be able to access these tools even from your desktop screen. This is not only convenient but also saves time while executing ADB Shell commands or Fastboot commands.
Setting up System-wide ADB and Fastboot
Don’t Miss: How to Set up Global ADB on macOS
All you need to set up universal ADB and Fastboot on your Windows 10 computer is the Android SDK Platform-tools and 2-3 minutes. Let’s see how we can do it.
- Download the latest SDK Platform-tools.zip for Windows. If you have downloaded it already, you can skip this step.
- Extract the downloaded Zip and save it in a safe place. In my case, I have kept it on the root of the C drive fn my PC.
- Open Control Panel on your Windows PC. If you don’t find it, just click the Search icon on the taskbar and type “control panel”.
- In the Control Panel window, click on System and Security and then on System.
- On the next screen select Advanced system settings.
- Doing so will open the System Properties window. Click on the Environment Variables button.
- Now, click on any item under System variables pane and then click on New.
- Another pop-up with 2 input fields will appear.
- Type “Path” in the Variable name field and then click on the Browse Directory button. Navigate to the “platform-tools” folder and select it. Alternatively, you can also type or paste the folder path in the Variable value input area.
- Anyway, click on the OK button to save the newly-created system variable.
- Now, close all windows. You have successfully set up system-wide ADB and Fastboot on your Windows 10 PC.
That’s it! It’s time now test if system-wide ADB and Fastboot is working properly on your PC or not.
Testing System-wide ADB
- Launch a Windows Command Prompt or open a PowerShell window on your desktop or any other screen. To do so perform a right-click on the mouse while holding the Shift key and select Open PowerShell window here from the right-click Context Menu. You can also use the Windows search feature to quickly access the Command Prompt.
- Now, connect your Android device to your PC. Don’t forget to enable USB debugging on your device otherwise, the ADB daemon won’t recognize or detect your phone.
- One more thing, as soon as you issue the ADB command, your Android device will prompt you to authorize ADB. Keep an eye on your phone’s screen and select Allow when asked.
- Type the following ADB command in the command window and press the Enter key. Allow USB debugging if prompted.
- You’ll get a string of alphanumeric values representing the ID of the connected Android device as shown below.
Now that you can run ADB and Fastboot commands from any screen of your Windows PC, why don’t you start with uninstalling system apps on your Android device via ADB without root?
If you get the ‘ADB is not recognized error‘, it means you haven’t set up system-wide ADB and Fastboot on your Windows PC properly.
You might have made a mistake while following the steps to create the ADB and Fastboot directory path as a system variable. To fix the issue, follow this tutorial more carefully. If you still get the same error, let me know via comments.