sodcalculator

10 Tech How-To

Run ADB Commands on Android Without a Computer

Guide 10-54094 · Updated · Step by step

This guide shows you how to execute ADB (Android Debug Bridge) commands directly on your Android device, eliminating the need for a PC. You’ll learn to set up a local ADB environment, use it for tasks like package management and file operations, and troubleshoot common issues.

What You’ll Need

  • An Android device (phone or tablet) running Android 5.0 or later.
  • USB debugging enabled in Developer Options (Settings > About phone > Tap ‘Build number’ 7 times, then Settings > Developer options > USB debugging).
  • A file manager app that can access the device’s internal storage (most pre-installed file managers work).
  • An internet connection to download the necessary APK files.

Step-by-Step

  1. Install a terminal emulator. Open the Google Play Store and install a terminal app like “Termux” or “Terminal Emulator”. Termux is recommended because it includes a package manager and is actively maintained.
  2. Download the ADB binaries. On your device, open a browser and search for “ADB Android ARM APK” or visit a trusted source like the official Android developer site (though you’ll need the ARM build). Download the ADB binary package (often a ZIP file) that matches your device’s architecture (ARM, ARM64, or x86).
  3. Extract the ADB files. Use a file manager to navigate to your Downloads folder. Tap the ZIP file and extract it to a folder you can easily access, e.g., /sdcard/adb.
  4. Open the terminal app. Launch Termux (or your chosen terminal). Grant storage permission if prompted (in Termux, run termux-setup-storage).
  5. Navigate to the ADB folder. In the terminal, type cd /sdcard/adb (or wherever you extracted the files) and press Enter. Use ls to list files and confirm you see adb and fastboot binaries.
  6. Make ADB executable. Run chmod +x adb fastboot to ensure the binaries can run.
  7. Start the ADB server. Type ./adb start-server and press Enter. This starts the ADB daemon on your device.
  8. Connect to the local device. Run ./adb devices. You should see a device listed as “unauthorized” or “offline”. To authorize, check your device screen for a prompt asking to allow USB debugging – tap “Allow” (if you don’t see it, try ./adb kill-server then ./adb start-server again).
  9. Test a command. Run ./adb shell to enter the device’s shell. You’ll see a prompt like shell@device:/ $. Type exit to leave the shell.
  10. Use ADB commands. Now you can run commands like ./adb install app.apk (to install an app), ./adb shell pm list packages (to list installed packages), or ./adb pull /sdcard/Download/file.txt . (to copy a file to the current directory).

Common Mistakes

  • Wrong architecture: Downloading an x86 version of ADB on an ARM device will cause a “cannot execute binary file” error. Check your device’s CPU type (Settings > About phone > Hardware info) and download the matching build.
  • Forgetting to authorize: If you skip the authorization prompt, ADB will show the device as “unauthorized”. Always accept the prompt on your device.
  • Using the wrong path: If you type adb instead of ./adb, the terminal will say “command not found”. The ./ prefix tells the shell to look in the current directory.
  • Not making binaries executable: Without chmod +x, you’ll get a “Permission denied” error.

Tips

  • Create a shortcut: In Termux, you can create a bash alias by editing ~/.bashrc and adding alias adb='./adb' to avoid typing ./ every time.
  • Use a local server: If you plan to use ADB frequently, you can run ./adb start-server once and leave it running. The server will automatically restart if needed.
  • Backup your data: Before running any command that modifies system settings or uninstalls apps, make a backup of important data using ./adb backup.
  • Learn common commands: Familiarize yourself with adb install, adb uninstall, adb shell, adb pull, and adb push – these cover most everyday tasks.

Troubleshooting

  • “command not found”: Ensure you’re in the correct directory and using ./adb. If the binary is corrupted, re-download it.
  • “device unauthorized”: Disconnect and reconnect the ADB server (./adb kill-server then ./adb start-server), then watch for the authorization prompt on your device and accept it.
  • “device offline”: This often happens if the ADB version is incompatible. Try a newer or older version of the ADB binaries. Also, ensure USB debugging is still enabled.
  • “permission denied”: Run chmod +x adb fastboot again. If the filesystem is mounted read-only, remount it with mount -o remount,rw / (requires root).
  • ADB server won’t start: Check if another process is using port 5037. In Termux, run pkill -f adb to kill any existing ADB processes, then try again.

Frequently Asked Questions

Do I need root access to run ADB commands on my device?

No, root is not required for most ADB commands like installing apps, copying files, or viewing logs. However, some advanced commands (like modifying system files) may require root.

Can I use this method to connect to another device wirelessly?

Yes, you can use adb connect <IP>:<port> to connect to a remote device over Wi-Fi, but both devices must have ADB configured and be on the same network.

What if my device doesn’t have a terminal emulator installed?

You can install one from the Play Store, but if you can’t, you can use a web-based terminal or a file manager with a built-in terminal (like Solid Explorer).

Is it safe to run ADB commands on my own device?

Generally yes, but be careful with commands that uninstall system apps or modify system settings. Always double-check the command before executing it.

Can I use this method to backup my entire device?

Yes, adb backup creates a full backup of your apps and data to a file on your device, which you can then copy to a safe location.

Why does my device show as “offline” in ADB?

This usually indicates a version mismatch between the ADB client and the device’s ADB daemon. Update your ADB binaries to the latest version and try again.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →