Essential ADB Commands for Android Power Users: Debloating, Backups, and Screen Recording

The Android operating system is built on top of a modified Linux kernel, providing an extensive command-line subsystem beneath its graphical user interface. While everyday smartphone interaction occurs via touchscreen gestures, genuine system ownership and granular administrative control are unlocked through the Android Debug Bridge (ADB). ADB bridges your desktop workstation and your mobile device, providing direct shell access with elevated system permissions that bypass standard user-space restrictions without requiring root.

Whether you want to purge non-removable OEM carrier bloatware, extract clean local application backups, capture crystal-clear high-bitrate screen recordings, or modify hidden system display flags, ADB is the most powerful tool in the Android enthusiast arsenal. This comprehensive guide details essential ADB commands, safe debloating protocols, and real-world shell scripts every power user should master.

1. The Architecture of the Android Debug Bridge

The Android Debug Bridge operates as a client-server architecture composed of three distinct components:

• The Client: The command-line executable (adb) running on your computer. When you issue a command like adb devices, you are invoking the client.
• The Server: A background process running on your workstation that manages communications between the ADB client and the background daemon on your smartphone. The server listens on TCP port 5037.
• The Daemon (adbd): A lightweight background service running on your Android device. When Developer Options and USB Debugging are activated, the kernel spawns adbd with elevated shell user privileges (UID 2000), allowing it to execute privileged shell commands and file transfers on behalf of authenticated clients.

2. Setting Up Platform-Tools and Establishing Connections

Never download outdated third-party ADB installers. Always use the official, standalone Android SDK Platform-Tools package maintained directly by Google:

1. Download the Platform-Tools ZIP archive for Windows, macOS, or Linux from the official Android developer portal.
2. Extract the folder to a permanent path (such as C:platform-tools on Windows).
3. Add this directory to your system PATH environment variable so you can launch adb from any terminal prompt.
4. On your phone, navigate to Settings > About Phone and tap Build Number seven times consecutively to activate Developer Options.
5. Open Settings > System > Developer Options and toggle on USB Debugging.
6. Connect your phone to your PC via a USB cable. Open your command terminal and verify the connection:

adb devices

Your phone will display a prompt: “Allow USB debugging?” displaying your computer’s RSA public key fingerprint. Check “Always allow from this computer” and tap Allow. Your terminal will now show your device serial number followed by the state device.

3. Pairing Wireless ADB on Modern Android (No Cables Required)

Starting with Android 11, Google introduced native Wireless Debugging using secure TLS authentication, eliminating the need to connect a physical USB cable:

1. Ensure your computer and smartphone are connected to the exact same local Wi-Fi network.
2. In Developer Options, toggle on Wireless Debugging and tap the menu item to view its configuration screen.
3. Select Pair device with pairing code. A dialog displays a 6-digit Wi-Fi pairing code and an IP address with a random pairing port (e.g., 192.168.1.45:38472).
4. In your computer terminal, execute the pairing command:

adb pair 192.168.1.45:38472
# Enter the 6-digit pairing code when prompted

Once paired, look at the main Wireless Debugging screen for your regular connection port (e.g., 192.168.1.45:41295) and connect:

adb connect 192.168.1.45:41295
# Output: connected to 192.168.1.45:41295

4. Safe OEM and Carrier Debloating Without Root

Manufacturers (like Samsung, Xiaomi, and OnePlus) and cellular carriers bundle dozens of unremovable pre-installed applications: redundant app stores, tracking analytics, commercial partner bloatware, and duplicate browsers. In standard settings, the “Uninstall” button is greyed out.

Using ADB package manager commands, you can completely uninstall these applications for the current primary user (User 0). The application binary remains intact in the read-only system partition (so system integrity is preserved), but it is completely removed from memory, app drawers, background services, and storage for your profile.

Step 1: Listing Installed Packages:

# List all third-party and OEM packages
adb shell pm list packages

# Filter packages by specific keyword (e.g., samsung or facebook)
adb shell pm list packages | grep -i "facebook"
# Output example:
# package:com.facebook.katana
# package:com.facebook.system
# package:com.facebook.appmanager
# package:com.facebook.services

Step 2: Uninstalling Bloatware for User 0:

# Uninstall Facebook background trackers cleanly
adb shell pm uninstall -k --user 0 com.facebook.katana
adb shell pm uninstall -k --user 0 com.facebook.system
adb shell pm uninstall -k --user 0 com.facebook.appmanager
adb shell pm uninstall -k --user 0 com.facebook.services

The flag --user 0 tells the system package manager to remove the application only for your primary profile, while -k keeps the app data cache folder if you ever decide to reinstall. Android immediately returns Success. The package stops running instantly and never loads in the background again.

5. Reinstalling and Restoring Debloated Packages

If you accidentally uninstall a system component that breaks a feature you need (such as an OEM camera app or ambient display service), you do not need to factory reset your smartphone. Because the underlying APK binary is preserved in the read-only system image, you can restore it in two seconds with a single command:

adb shell cmd package install-existing com.example.accidentally_removed_app

The operating system re-registers the package for User 0 instantly with its original system permissions restored.

6. High-Bitrate Screen Recording and Raw Framebuffer Capture

While native Android screen recording tools often compress videos aggressively or restrict recording parameters, ADB provides direct hardware-accelerated screen capture via the screenrecord shell binary:

Capturing High-Quality 60fps Video:

# Record video at custom resolution, 24 Mbps bitrate, and 180s duration
adb shell screenrecord --size 1920x1080 --bit-rate 24000000 --time-limit 180 /sdcard/gameplay.mp4

# Pull the recorded video directly to your desktop computer
adb pull /sdcard/gameplay.mp4 C:UsersUserVideos

Capturing Lossless Screenshots:

# Capture direct framebuffer PNG and pull immediately
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png .

7. Data Backups, File Pushing, and APK Sideloading

ADB accelerates file operations, moving multi-gigabyte archives across USB 3.0 interfaces far faster than traditional MTP (Media Transfer Protocol) file browsing:

Fast Batch Sideloading:

# Sideload APK with reinstall (-r) and grant all permissions (-g) flags
adb install -r -g my_application.apk

# Sideload multiple split APKs (APKS container) simultaneously
adb install-multiple base.apk split_config.arm64_v8a.apk split_config.xxhdpi.apk

Pushing and Pulling Files:

# Push an entire local folder to device internal storage
adb push C:ROMsPlayStation /sdcard/Emulation/PSX/

# Pull custom photos or backup folders to your computer
adb pull /sdcard/DCIM/Camera/ C:BackupsPhotos

8. Master ADB Command Reference Matrix

Command Syntax	Operational Purpose	Risk Level
adb devices -l	Lists connected hardware devices with detailed product model and USB port info	Zero
adb shell pm uninstall -k –user 0 <pkg>	Uninstalls bloatware or system package for current user without root	Low (Reversible)
adb shell cmd package install-existing <pkg>	Instantly restores and reinstalls a previously debloated system application	Zero
adb reboot recovery / bootloader	Reboots the device directly into Recovery partition or Fastboot mode	Low
adb shell dumpsys battery set level <N>	Simulates custom battery percentage levels for thermal and throttling testing	Zero
adb shell logcat -c && adb logcat *:E	Clears previous log ring-buffer and streams system errors in real time	Zero

9. Advanced Display and Power Tweaks via ADB Shell

ADB provides access to the wm (Window Manager) and settings commands, allowing you to configure parameters hidden by manufacturer UI skins:

Custom Display Scaling (DPI Tuning):

# View current display density
adb shell wm density
# Output: Physical density: 440

# Increase workspace screen real estate by lowering DPI
adb shell wm density 380

# Reset back to manufacturer default
adb shell wm density reset

Permanently Granting Special Permissions:

Certain powerful utilities (such as Shizuku, BetterBatteryStats, or Tasker) require elevated Android permissions that cannot be enabled via normal permission dialogs:

# Grant Write Secure Settings permission to automation apps
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS

# Grant DUMP permission for battery profiling
adb shell pm grant com.asksven.betterbatterystats android.permission.DUMP

10. Frequently Asked Questions

Can debloating an app via ADB void my device warranty or break OTA updates?

No. Because pm uninstall --user 0 only removes the application from the user space profile without modifying the read-only system partitions (dm-verity hash remains 100% intact), it does not trip Knox, does not unlock your bootloader, and does not block official Over-The-Air (OTA) system updates.

Why does my computer show “device unauthorized” when running adb devices?

This occurs when the smartphone has not accepted your desktop RSA public key. Unlock your phone screen, check the prompt for “Allow USB Debugging”, and accept it. If the prompt does not appear, toggle USB Debugging off and on in Developer Options, or revoke USB debugging authorizations in settings.

Can I use ADB commands directly from my phone without a computer?

Yes. On Android 11 and newer, you can install apps like LADB or Shizuku. These apps pair directly to your phone’s own Wireless Debugging port over local loopback (127.0.0.1), giving you a full on-device ADB shell without needing a PC or root privileges.