Removing applications via the Android command line: a complete guide with ADB

Removing unnecessary applications through the standard Android interface is often limited: the system does not allow you to get rid of pre-installed apps, and some "junk" files remain even after uninstallation. Command line via ADB (Android Debug Bridge) opens up advanced options - from complete erasure user applications before deleting system components that are usually blocked.

This method is especially relevant for owners of devices with limited memory or custom firmware, where every megabyte counts. However, working with ADB requires caution: the wrong command can lead to a system crash or loss of functionality (for example, deleting Google services will make it impossible to work with the Play Market). This article provides step-by-step guide for beginners and experienced users, including backup and recovery methods.

Before you begin, make sure that your device USB debugging is enabled (path: Settings → About phone → Build number — tap 7 times to activate developer mode, then return to Settings → System → For developers). Without this, connecting to ADB is impossible.

1. Preparation: installing ADB and drivers

To manage Android via the command line, you will need ADB tool from Google, which is included Android SDK Platform-Tools. Download the archive from the official website of Android developers (link) and unpack it into a convenient folder (for example, C:\platform-tools).

For Windows, you will additionally need drivers USB: Suitable for most devices (download from the same SDK). their sites.:

• 🔌 Universal drivers: Suitable for most devices (download Google USB Driver from the same SDK).
• 📱 Manufacturer drivers: For brands like Samsung, Xiaomi or Huawei It's better to use official drivers from their websites.
• 🔍 Checking the connection: After installing the drivers, connect the phone to the PC and make sure that Manager devices there are no exclamation marks next to the name of your device.

For macOS or Linux installation is simpler - just unzip platform-tools and add the folder path to the environment variable PATH. For example, in the Mac terminal, run:

echo 'export PATH=$PATH:~/platform-tools' >> ~/.bash_profile
source ~/.bash_profile

⚠️ Attention: On devices with MIUI (Xiaomi) or EMUI (Huawei) may require additional debugging permission in the security settings. Without this, ADB will not see the device.

2. Connecting the device and checking the connection

Open a command line (Windows) or terminal (macOS/Linux) and go to the folder with platform-tools. To do this, enter:

cd path_to_folder\platform-tools

For example, for Windows:

cd C:\platform-tools

Now connect the phone via USB and run the command:

adb devices

If the connection is established, you will see the serial number of the device. If not, check:

• 🔄 Data transfer mode: On the phone, select File transfer (MTP), not "Charging".
• 🔒 Debugging permission: A window asking for permission should appear on the phone screen - confirm it.
• 🔌 Cable and port: Use the original USB 2.0 cable and port (USB 3.0 sometimes causes problems).

Original USB cable connected|

Enabled USB debugging|

Drivers for your model are installed|

Phone is unlocked (not in sleep mode)|

The `adb devices` command shows the serial number-->

3. Finding application packages to remove

Before deleting anything, you need to know package name the target application. To do this, use the command:

adb shell pm list packages

This command will list all installed packages. To narrow your search, add a filter. For example, to search for applications from Facebook:

adb shell pm list packages | grep facebook

For Windows, replace grep with findstr:

adb shell pm list packages | findstr facebook

Some popular system application packages:

⚠️ Attention: Removing packages with names containing android, google or systemmay result k device malfunction. Always check the purpose of the package before deleting!

4. Commands for uninstalling applications

There are two main methods for uninstalling via ADB:

1. For custom applications (installed by you):

adb shell pm uninstall -k --user 0 package_name

Flag -k saves data and application cache (useful if you plan to restore it later). Without this flag, complete removal.

2. For system applications (pre-installed):

adb shell pm uninstall --user 0 package_name

This command does not delete the apk file from the system, but only hides it from the current user. For complete removal you need rights root.

Examples:

• 📱 Removal Facebook:

adb shell pm uninstall -k --user 0 com.facebook.katana

• 🎵 Removal Google Music:

adb shell pm uninstall --user 0 com.google.android.music

This will help restore deleted applications, if something goes wrong.-->

5. Uninstalling with root access: risks and opportunities

If your device unlocked (has rights root), you can remove system applications completely, and not just for the current user. To do this, use the command:

adb shell
su
mount -o rw,remount /system
rm -rf /system/app/package_name
rm -rf /system/priv-app/package_name

However, this method is extremely risky:

• 💥 Loss of functionality: Removing critical packages (for example, com.android.phone) will make the phone inoperable.
• 🔄 Problems with updates: System updates can restore deleted files or cause conflicts.
• 🛡️ Security violation: Some applications (for example, Samsung Knox) are related to encryption data.

⚠️ Attention: On devices with Samsung Knox or Google Pixel obtaining root access, the flag may be triggered KNOX 0x1 or blocked Google Pay. Before taking action, check the consequences for your model!

6. Recovering deleted applications

If you deleted an application by mistake, you can restore it in several ways:

1. Through the Play Market: Simply find the application and install it again (works only for user apps).
2. Via ADB: If you have a backup copy of the APK, use:

adb install file_name.apk

3. Via TWRP: If you have a custom recovery, you can restore the system image from a backup.

For system applications removed by the command --user 0, just run:

adb shell cmd package install-existing package_name

If this method does not work, try resetting the application settings:

adb shell pm clear package_name

7. Alternative methods: without the command line

If working with ADB seems difficult, consider alternatives:

• 📱 Debloater applications: Universal Android Debloater (GUI for ADB) or Package Disabler (for Samsung) allow you to disable applications without commands.
• ⚙️ Custom firmware: Firmwares like LineageOS or Pixel Experience come without pre-installed garbage.
• 🔧 ADB AppControl: A utility with a graphical interface for managing packages (available on GitHub).

However, even these methods require unlocking the bootloader or superuser rightswhich will void the warranty on most devices. Always weigh the risks!

FAQ: Frequently asked questions

adb shell pm uninstall -k --user 0 com.google.android.gms

adb shell dumpsys package package_name