Here we are again with a nice How-to Guide for the Android Lovers. This post is about the ADB and fastboot drivers and how to Install ADB on Windows, MAC, and Linux. ADB, Android Debug Bridge, is a command-line utility which helps you to run the ADB and fastboot commands on your android devices. In a simple way, we can say that ADB and FASBTOOT are the tools which allow you send terminal commands to your phone from your computer via USB. They both serve different functions, but they are must for the Android Phone users.
Disclaimer This instruction is only care how to install MacOS on WSL2, but not whether you have right permission to install MacOS on your device or not. (EULA) Steps prerequirements Setting WSL2 Enable KVM set QEMU VM create macOS-Simple-KVM on QEMU Launch prerequirements KVM supporting Intel CPU. To extract (unzip) a tar.gz file simply right-click on the file you want to extract and select “Extract”. Windows users will need a tool named 7zip to extract tar.gz files. The -v option will make the tar command more visible and print the names of the files being extracted on the terminal. Tar -xvf archive.tar.gz.
Suppose you want to customize your Android Devices like Install TWRP on the phone, Root the Android Phone to make changes in the system or Install Custom ROM on your Stock Android phone. Then you need to run some ADB and Fastboot commands. At that time you need these ADB and fastboot drivers on your Windows, MAC, and Linux.
There are so may tutorial are available on the internet to install the ADB setup files, but sometime they will not work or outdated. So here we are providing you the latest ADB drivers and that is direct from the Google Servers. Which means these ADB drivers are updated and work on any System and Android Devices. All you have to follow the below mention tutorial to setups the ADB and fastboot drivers on Windows, MAC, and Linux. So let’s get started and install ADB on your desktop.
Table of Contents
- 1 Guide To Install ADB and Fastboot
Guide To Install ADB and Fastboot
NOTE:- Install ADB on Your Desktop is a half process to complete the whole ADB setup you need to make some changes on your smartphone or tablet to accept the ADB commands.
Allows USB debugging On Android Devices
1. Open the Setting page on your device.
2. From here Tap on the About Phone option generally near the bottom of the list (this is hidden behind the “System” option in Google’s latest Android Oreo version).
3. In the about phone section of your phone, Tap the Build Number option 7 times to enable Developer Mode. And you will see a popup message on your screen “You are now a developer”.
4. Now go back to the Settings page and you should see a new Developer Options menu here.
5. Go in there and scroll down to USB debugging and turn the toggle on. This will enable the USB debugging On Android.
Now all you have to setup the ADB files on your desktop. Follow the rest of the instructions for your particular operating system.
Install ADB on Windows Desktop
1. Visit this Google page to Download the ADB ZIP file for Windows.
2. Unzip the folder on your Windows C Drive. (C:platform-tools).
3. Open the ADB Platform-Tools folder. Next, open a terminal window in the folder where you have ADB and fastboot installed. On Windows, you can right-click and click open command window here. (Some Windows 10 users may see “PowerShell” instead of “command prompt”.)
4. Now connect your phone to the Windows PC with the USB cable.
5. Now enter the following command in the command prompt window to check the connection between PC and Phone.
Your device’s serial number should appear in the command window.
6. Also on your phone’s screen, you should see a pop screen to allow or deny USB Debugging access. Grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).
That’s it! Now you can now run any ADB command on your device form your Windows PC.
How to Install ADB on MAC
1. Visit this Google page to Download the ADB ZIP file for MacOS.
2. Now extract the folder on your desktop.
3. Open Terminal on Your MAC.
4. Now to browse to the folder you extracted ADB into, enter the following command on Terminal window.
On my MAC the command looks like this cd /Users/Sid/Desktop/platform-tools/
5. Now connect your phone to the MAC with the USB cable.
6. Now enter the following command in the Terminal window to check the connection between MAC and Phone.
7. Now on your device, you’ll see an “Allow USB debugging” prompt. Allow the connection.
Voila! You successfully install the ADB on MAC OS.
How to Install ADB on Linux
1. Visit this Google page to Download the ADB ZIP file for MacOS.
2. Now extract the folder on your Linux desktop.
3. Open the Terminal app on your Linux machine to follow the next step to install ADB.
4. Now to browse to the folder you extracted ADB into, enter the following command on Terminal window.
On my MAC the command looks like this cd /Users/Sid/Desktop/platform-tools/
5. Now connect your Android Device to the Linux with the USB cable.
6. Now enter the following command in the Terminal window to check the connection between Linux and Android SmartPhone.
7. Now on your device, you’ll see an “Allow USB debugging” prompt. Allow the connection.
Voila! You successfully install the ADB on your Linux Desktop.
So with this way you easily install and setup ADB on your Windows, MAC, and Linux. You can also check some of the Other guides here to install ADB and fastboot, Fastest Method to Setup ADB and Fastboot on Windows and Install ADB and Fastboot on Mac, Linux, Chrome OS With Nexus Tool Script
The Beginners Guide has general help. Click here for the Beginners Guide
If you need Mac-specific help, you are at the right page.
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you.
Not all functionality is supported on all radios. See Model Support
As of MacOS 10.9, signed packages are required by default. Apple charges for this capability, and requires use of their tooling to do it. For the time being, MacOS users may need to disable signed package checking for CHIRP. Instructions provided by Jim, K2SON:
- Locate the app in Finder.
- Right click (control-click if you don't have a 2 button mouse) on the app and click Open.
- You will get a dialog box about it being an unsigned app, click the Open button.
- Enter an Administrator userid and password.
- The app will now be flagged to allow it to be opened normally in the future.
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Instructions for this provided by Tom, KD7LXL:
- Open your System Preferences
- Go to Security & Privacy, General tab.
- Click the lock
- Then choose Allow apps downloaded from: Anywhere.
As of 10.12 (Sierra) the UI for disabling app security was removed. The functionality is still there, but must be enabled from the command line.
To whitelist a single application (like an unzipped chirp-daily.app):- unzip chirp.zip
- control click on the unzipped application and select New Terminal at Folder. (Don't see that menu item? Instructions to enable it)
- run this command in the newly opened terminal window:
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Run this command in a terminal:
Macos Unzip Rar Terminal
references: single commandglobal
Unfortunately, Apple has made significant changes in 10.15 which cause major issues for independent software developers. CHIRP is significantly impacted and the future is unclear.
At the very least, Catalina users should use the 'unified' build of the app provided on the download page, which uses the system's 64-bit python runtime. Also note that there are significant limitations on what files unsigned applications can access which makes it very difficult to open, save, find, and otherwise organize image and CSV files with chirp. Please see issue #7147 for the current information about workarounds.
USB to serial cables are not merely wire, they contain small computer circuits at one end of the cable that respond as a USB device and convert the data to serial. These cables are not all the same, so the computer needs a software 'driver' so it can recognize the cable and speak to it correctly. You will need to install one of these 5 below.
FTDI cables¶
Note that with Mac OSX 10.9 'Mavericks', Apple provides their own driver for FTDI chipset. You may need to remove the OEM FTDI driver and use only the Apple FTDI driver, or you may need to disable the Apple FTDI driver and install the OEM FTDI drivers. YMMV.
http://www.ftdichip.com/Drivers/VCP.htm
Version 1.5.1 is available for Mac OS X on 64 bit, 32 bit and PPC machines.
Prolific PL-2303 cables - official drivers for the genuine Prolific cables¶
FYI: your cable, if using Prolific chipset, is more likely to be using a counterfeit chip than an original.
http://www.prolific.com.tw/US/CustomerLogin.aspx
Login as guest/ guest & look in the Support section. Specified to work with Mac OSX 10.6, 10.7, & 10.8.
Generic PL-2303 cables (counterfeit and/or “Generic”) If you aren't sure what kind of inexpensive cable you have, try this one first.¶
For Lion (10.7.x), Mountain Lion (10.8.x), and Mavericks (10.9.x):¶
You can try this one, which install open source pl2303 driver and remove any other driver versions:
http://1drv.ms/Nl68Ru At this web page you may need to right-click or control-click to link to get it to download. After downloading, you may need to control-right click, then open in order to bypass Mac Gatekeeper.
For earlier versions of Mac OS X up to 10.5 Leopard. Also some reports of success with Snow Leopard, Lion:¶
RTSystems cables¶
for OSX 10.9.x (aka Mavericks):¶
see RTSystemsCablesAndMavericks
Macos Unzip Terminal Free
for OSX < 10.9.x:¶
https://www.rtsystemsinc.com/kb_results.asp?ID=9
http://www.rtsystems.us/downloads/MacDrivers/RTSystemUSBSerialDrivers.pkg.mpkg.zip
Silicon Labs CP210x USB to UART Bridge VCP Drivers (including Kenwood TH-D72)¶
- http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
Macintosh OSX driver for the Intel and PowerPC Platforms versions 10.4, 10.5, 10.6, 10.7, 10.8, and 10.9.
WinChipHead CH340 series chipset¶
The WinChipHead CH340 series chipset is not compatible with the Prolific 2303 drivers. This chipset will report a Product ID of 0x7523 and a Vendor ID of 0x1a86. A signed driver compatible with Yosemite is available from http://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/ as the driver offered on the manufacturer's website (in Chinese) is not signed and requires allowing unsigned kernel extensions, which is a significant security risk on OS X.
- In many cases you need to connect the cable to the radio first, then power the radio on, while holding down some buttons. The exact procedure varies by radio.
- Some radios need to be put into a 'clone' mode to transfer to PC, some radios may need to be configured to use the mic/speaker jacks for PC transfer instead of for the speaker/mic. The exact procedure varies by radio.
- You will need to download from the radio to CHIRP first, before uploading anything to the radio. CHIRP creates a template from the radio download so it knows how to talk to the radio.
- If you want to download from one radio and upload those settings to another radio, first download from each radio to a separate “tab” of CHIRP. Then copy/paste from one tab to the other & upload back to the same radio that produced that tab. Do not try to upload to a radio directly from a tab that was not downloaded from that same radio.
- Many USB to serial cables include a counterfeit Prolific chip. This can cause connection problems because the official Prolific driver will ignore the counterfeit chip. Some people have reported success by using an older version of the Prolific driver, or a 3rd party driver.
- If you are using multiple USB cables, each will create a different “virtual port”, meaning that you will need to select the correct virtual port for your radio when connecting to your radio. CHIRP will give you this opportunity each time you download from the radio.
- If CHIRP won’t launch & won't run, you may have neglected to install the Python runtime. CHIRP needs that. Even though Mac OS X includes Python built-in, the runtime has to be installed is because it includes PyGTK and some other libraries that Chirp requires, in addition to Python itself: http://www.d-rats.com/download/OSX_Runtime/
- If your radio is not 'Supported', you can try downloading the newest Daily Build to see if support was recently added.
You can verify that the drivers are installed & working by connecting the USB cable to your Mac, then running “System Profiler”, or “System Information” (found in /Applications/Utilities ). When the USB cable is connected and drivers correctly installed, the cable will show up in the USB section of the System Profiler.
Another way to see that the driver is correctly installed is to open Terminal and type:
It will return a list of virtual serial ports including something similar to:
You may also type:
That will return a long list of kexts, including something similar to this at the bottom (most recently installed are listed last):
Look at the CHIRP log for clues.
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you.