{"id":8940,"date":"2026-03-18T11:29:51","date_gmt":"2026-03-18T08:29:51","guid":{"rendered":"https:\/\/computingforgeeks.com\/?p=8940"},"modified":"2026-03-24T11:52:23","modified_gmt":"2026-03-24T08:52:23","slug":"install-adb-fastboot-ubuntu-debian","status":"publish","type":"post","link":"https:\/\/computingforgeeks.com\/install-adb-fastboot-ubuntu-debian\/","title":{"rendered":"Install ADB and Fastboot on Ubuntu 24.04 \/ Linux Mint 22 \/ Debian 13"},"content":{"rendered":"\n<p>ADB (Android Debug Bridge) and Fastboot are command-line tools that let you communicate with Android devices from a Linux workstation. ADB handles tasks like installing apps, copying files, capturing logs, and running shell commands on a connected device. Fastboot operates at the bootloader level, useful for flashing firmware images, unlocking bootloaders, and recovering bricked devices.<\/p>\n\n\n\n<p>This guide walks through installing ADB and Fastboot on <strong>Ubuntu 24.04<\/strong>, <strong>Linux Mint 22<\/strong>, and <strong>Debian 13<\/strong> using two methods: the distribution package manager and a manual install from Google&#8217;s official release.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<p>Before you start, confirm the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A running Ubuntu 24.04, Linux Mint 22, or Debian 13 system<\/li>\n\n\n\n<li>A user account with sudo privileges<\/li>\n\n\n\n<li>An Android device with a USB cable (for testing the connection)<\/li>\n\n\n\n<li>Internet connectivity to download packages<\/li>\n<\/ul>\n\n\n\n<p>Update your package index before proceeding:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 1 &#8211; Install ADB and Fastboot from APT (Recommended)<\/h2>\n\n\n\n<p>The simplest approach is to install the <code>android-sdk-platform-tools<\/code> package directly from the distribution repositories. This method handles dependencies automatically and integrates with the system package manager for updates.<\/p>\n\n\n\n<p>Run the following command to install ADB and Fastboot:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install -y android-sdk-platform-tools<\/code><\/pre>\n\n\n\n<p>After installation completes, verify that both tools are available:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>adb version<\/code><\/pre>\n\n\n\n<p>Expected output will show the ADB version and build information:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Android Debug Bridge version 1.0.41\nVersion 34.0.x-xxxxxxx<\/code><\/pre>\n\n\n\n<p>Check Fastboot as well:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fastboot --version<\/code><\/pre>\n\n\n\n<p>You should see version details similar to:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fastboot version 34.0.x-xxxxxxx<\/code><\/pre>\n\n\n\n<p>If both commands return version strings without errors, the installation is complete. The repository version may lag behind Google&#8217;s latest release by a few versions. If you need the newest build, use Method 2 below.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 2 &#8211; Install ADB and Fastboot from Google&#8217;s Official Release<\/h2>\n\n\n\n<p>Google publishes standalone platform-tools packages that always contain the latest ADB and Fastboot binaries. This method gives you the most recent version without waiting for distribution repositories to update.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1 &#8211; Download Platform Tools<\/h3>\n\n\n\n<p>Download the latest Linux platform-tools archive from Google:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/tmp\nwget https:\/\/dl.google.com\/android\/repository\/platform-tools-latest-linux.zip<\/code><\/pre>\n\n\n\n<p>Verify the download completed successfully by checking the file size:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -lh \/tmp\/platform-tools-latest-linux.zip<\/code><\/pre>\n\n\n\n<p>The file should be several megabytes in size. If it shows 0 bytes or the download failed, retry the wget command.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2 &#8211; Extract the Archive<\/h3>\n\n\n\n<p>Install <code>unzip<\/code> if it is not already present, then extract the archive:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install -y unzip\nunzip \/tmp\/platform-tools-latest-linux.zip -d \/opt\/<\/code><\/pre>\n\n\n\n<p>This extracts the tools to <code>\/opt\/platform-tools\/<\/code>. Confirm the binaries are in place:<\/p>\n\n<!-- \/wp:post-content -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>ls -l \/opt\/platform-tools\/adb \/opt\/platform-tools\/fastboot<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Both files should appear as executable binaries.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Step 3 &#8211; Add Platform Tools to PATH<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>To run <code>adb<\/code> and <code>fastboot<\/code> from any directory, add the platform-tools folder to your shell PATH. Append the following line to your <code>~\/.bashrc<\/code> file (or <code>~\/.zshrc<\/code> if you use Zsh):<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>echo 'export PATH=\"$PATH:\/opt\/platform-tools\"' >> ~\/.bashrc<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Reload the shell configuration to apply the change immediately:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>source ~\/.bashrc<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Step 4 &#8211; Verify the Installation<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Check that the system picks up the correct binary path and version:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>which adb\nadb version<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>The <code>which<\/code> command should return <code>\/opt\/platform-tools\/adb<\/code>. Then verify Fastboot:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>which fastboot\nfastboot --version<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Both tools should report their version numbers. If <code>which<\/code> returns a different path, you may have the APT version installed as well. Remove it with <code>sudo apt remove android-sdk-platform-tools<\/code> to avoid conflicts.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Configure udev Rules for Device Permissions<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>On Linux, regular users typically cannot access USB devices without proper udev rules. Without these rules, ADB will either fail to detect your device or require running as root, which is not recommended.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>The <code>android-sdk-platform-tools<\/code> package from APT usually installs udev rules automatically. If you used Method 2, or your device is not detected, set up the rules manually.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>Install the community-maintained Android udev rules package:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>sudo apt install -y android-sdk-platform-tools-common<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>This installs udev rules to <code>\/lib\/udev\/rules.d\/51-android.rules<\/code> covering most Android device vendors.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>If you prefer to create rules manually or need to add a specific vendor, create a custom rules file:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/udev\/rules.d\/51-android.rules &lt;&lt;'EOF'\n# Google\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"18d1\", MODE=\"0666\", GROUP=\"plugdev\"\n# Samsung\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"04e8\", MODE=\"0666\", GROUP=\"plugdev\"\n# OnePlus\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"2a70\", MODE=\"0666\", GROUP=\"plugdev\"\n# Xiaomi\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"2717\", MODE=\"0666\", GROUP=\"plugdev\"\n# Huawei\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"12d1\", MODE=\"0666\", GROUP=\"plugdev\"\n# Motorola\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"22b8\", MODE=\"0666\", GROUP=\"plugdev\"\n# Sony\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"0fce\", MODE=\"0666\", GROUP=\"plugdev\"\n# LG\nSUBSYSTEM==\"usb\", ATTR{idVendor}==\"1004\", MODE=\"0666\", GROUP=\"plugdev\"\nEOF<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Reload udev rules and add your user to the <code>plugdev<\/code> group:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>sudo udevadm control --reload-rules\nsudo udevadm trigger\nsudo usermod -aG plugdev $USER<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Log out and back in (or reboot) for the group membership change to take effect. Verify your user is in the plugdev group:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>groups $USER<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Enable USB Debugging on Your Android Device<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>ADB cannot communicate with your device unless USB debugging is turned on. Follow these steps on the Android device:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:list {\"ordered\":true} -->\n<ol class=\"wp-block-list\"><!-- wp:list-item -->\n<li>Open <strong>Settings<\/strong> and go to <strong>About phone<\/strong><\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Tap <strong>Build number<\/strong> seven times until you see &#8220;You are now a developer&#8221;<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Go back to <strong>Settings<\/strong> and open <strong>Developer options<\/strong> (may be under System or Additional settings depending on your device)<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Toggle <strong>USB debugging<\/strong> to ON<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Connect the device to your Linux machine via USB<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>When prompted on the device, tap <strong>Allow<\/strong> to authorize the computer for USB debugging &#8211; check &#8220;Always allow from this computer&#8221; if you want to skip this prompt in the future<\/li>\n<!-- \/wp:list-item --><\/ol>\n<!-- \/wp:list -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Test the ADB Connection<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>With USB debugging enabled and the device connected, start the ADB server and list connected devices:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>You should see output listing your device with a serial number and the word <code>device<\/code> next to it:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>List of devices attached\nXXXXXXXXXXXXXXX\tdevice<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>If the status column shows <code>unauthorized<\/code>, check the device screen for the authorization prompt and tap Allow. If it shows <code>no permissions<\/code>, revisit the udev rules section above.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Common ADB Commands<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Here is a reference of ADB commands you will use regularly.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Open a shell session on the device:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb shell<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Push a file from your computer to the device:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb push \/path\/to\/local\/file \/sdcard\/Download\/<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Pull a file from the device to your computer:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb pull \/sdcard\/Download\/file.txt \/tmp\/<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Install an APK on the device:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb install application.apk<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Use the <code>-r<\/code> flag to reinstall an existing app while keeping its data:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb install -r application.apk<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>View real-time device logs:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb logcat<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Filter logcat output by tag for targeted debugging:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb logcat -s \"ActivityManager\"<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Reboot the device:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb reboot<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Reboot into recovery or bootloader mode:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb reboot recovery\nadb reboot bootloader<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Common Fastboot Commands<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Fastboot works when the device is in bootloader (fastboot) mode. Boot into fastboot mode from ADB:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb reboot bootloader<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Or power off the device and hold the appropriate hardware button combination (varies by manufacturer).<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>List connected devices in fastboot mode:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>fastboot devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Unlock the bootloader<\/strong> (this wipes all data on the device):<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>fastboot flashing unlock<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Flash a partition image:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>fastboot flash boot boot.img\nfastboot flash recovery recovery.img<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><strong>Reboot the device from fastboot mode:<\/strong><\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>fastboot reboot<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Device Not Detected by ADB<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>If <code>adb devices<\/code> returns an empty list:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:list -->\n<ul class=\"wp-block-list\"><!-- wp:list-item -->\n<li>Confirm USB debugging is enabled on the device<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Try a different USB cable &#8211; some cables are charge-only and do not support data transfer<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Try a different USB port, preferably a USB 2.0 port on the back of the machine<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>On the device, change the USB mode from &#8220;Charging&#8221; to &#8220;File Transfer&#8221; (MTP)<\/li>\n<!-- \/wp:list-item -->\n\n<!-- wp:list-item -->\n<li>Kill and restart the ADB server:<\/li>\n<!-- \/wp:list-item --><\/ul>\n<!-- \/wp:list -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb kill-server\nadb start-server\nadb devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Permission Denied or &#8220;no permissions&#8221; Error<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>This indicates missing or incorrect udev rules. Follow the udev rules section above to set them up. After creating the rules file, reload udev and restart ADB:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>sudo udevadm control --reload-rules\nsudo udevadm trigger\nadb kill-server\nadb devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Make sure your user is a member of the <code>plugdev<\/code> group. If you just added yourself, log out and back in for the change to take effect.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Device Shows &#8220;unauthorized&#8221;<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>The device is detected but has not authorized your computer. Disconnect the USB cable, reconnect it, and look for the RSA key fingerprint prompt on the device screen. Tap <strong>Allow<\/strong> to authorize the connection.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>If the prompt does not appear, revoke existing USB debugging authorizations on the device under <strong>Developer options<\/strong> and reconnect.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">ADB Version Mismatch Between Client and Server<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>If you see a warning about mismatched ADB client and server versions, it usually means you have two ADB installations. Kill the server and let the correct binary start it fresh:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>adb kill-server\nwhich adb\nadb devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>If <code>which adb<\/code> points to the wrong binary, adjust your PATH so the preferred installation appears first, or remove the version you do not need.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading {\"level\":3} -->\n<h3 class=\"wp-block-heading\">Fastboot Cannot Detect the Device<\/h3>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Fastboot detection issues are almost always a udev rules problem. Verify the device is in fastboot mode (the screen should show a fastboot or bootloader menu), then run:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>sudo fastboot devices<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>If the device appears with <code>sudo<\/code> but not without it, your udev rules are not configured correctly. Fix the rules as described in the udev section and try again without sudo.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading -->\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>You now have ADB and Fastboot installed and working on your Ubuntu 24.04, Linux Mint 22, or Debian 13 system. Method 1 using the APT package is the straightforward option for most users, while Method 2 gives you the latest binaries directly from Google. With udev rules in place and USB debugging enabled, you can manage Android devices directly from the command line, whether that means transferring files, debugging applications, or flashing firmware images.<\/p>\n<!-- \/wp:paragraph -->\n","protected":false},"excerpt":{"rendered":"<p>ADB (Android Debug Bridge) and Fastboot are command-line tools that let you communicate with Android devices from a Linux workstation. ADB handles tasks like installing apps, copying files, capturing logs, and running shell commands on a connected device. Fastboot operates at the bootloader level, useful for flashing firmware images, unlocking bootloaders, and recovering bricked devices. &#8230; <a title=\"Install ADB and Fastboot on Ubuntu 24.04 \/ Linux Mint 22 \/ Debian 13\" class=\"read-more\" href=\"https:\/\/computingforgeeks.com\/install-adb-fastboot-ubuntu-debian\/\" aria-label=\"Read more about Install ADB and Fastboot on Ubuntu 24.04 \/ Linux Mint 22 \/ Debian 13\">Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":8971,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26,690,299,50,81],"tags":[3725,3726],"class_list":["post-8940","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-debian","category-dev","category-how-to","category-linux-tutorials","category-ubuntu","tag-adb","tag-fastboot"],"_links":{"self":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/8940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/comments?post=8940"}],"version-history":[{"count":2,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/8940\/revisions"}],"predecessor-version":[{"id":164079,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/8940\/revisions\/164079"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media\/8971"}],"wp:attachment":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media?parent=8940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/categories?post=8940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/tags?post=8940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}