The problem of pre-installed software, or so-called bloatware, is familiar to almost every owner of an Android smartphone. Device manufacturers and telecom operators often include a set of applications in the firmware that cannot be removed using standard means through the settings menu. These apps take up precious memory space, consume RAM in the background, and sometimes even drain battery power, slowing down your gadget.
Fortunately, there is an effective way to turn an uninstallable system application into a regular user application that can be deactivated or completely removed. This does not require obtaining root access, which preserves the warranty on the device and the integrity of the system partitions. The method is based on the use of a tool Android Debug Bridge (ADB)that allows you to send commands directly to the operating system through the computer.
In this article we will analyze in detail the process of preparing equipment, setting up debugging and executing commands to clean the system. You will learn how to safely manage system components, which packages can be touched, and which are critical for stable operation Android. The right approach will allow you to personalize the device to suit your needs, getting rid of unnecessary digital noise.
Preparing equipment and setting up debugging
The first step towards freeing your smartphone from unnecessary software is preparing the workplace. You will need a computer running Windows, macOS or Linux, as well as a working USB cable, preferably an original one, to ensure a stable connection. Without a reliable physical connection, the process of transmitting commands may be interrupted, which will lead to script execution errors.
On the smartphone itself, you must activate the hidden menu for developers. Go to Settings → About phone and find the item Build number. Click on it seven times in a row until a notification appears indicating that you have become a developer. After this, a new section will appear in the main settings menu For developers.
Inside this section, find the switch USB Debugging and activate it. The system will issue a warning about potential risks, which you must agree to. It is this mode that allows the computer to send debugging commands to the device, which is the foundation for further manipulation of system packages.
⚠️ Attention: Never leave USB debugging enabled all the time, especially when using public charging stations. This may create a vulnerability for unauthorized access to your device data.
Use a short, high-quality cable for connection. Long, cheap cables often cause a loss of connection at the most critical moment of command execution.
Installing drivers and the ADB platform
To interact with a smartphone, the computer requires special drivers and a set of platform tools. If you are using Windows, you will most likely need to install generic Google USB Drivers or specific drivers from your device manufacturer, such as Samsung, Xiaomi or Huawei. Without the correct drivers, the computer will see the phone only as a drive, but not as a debugging device.
You can download the minimum set of tools Platform Tools from the official Android developers website. This archive contains executable files adb and fastboot. Unpack the contents of the archive into a convenient folder, for example, to the root of drive C or to the desktop, so that the path to the files does not contain Cyrillic characters, which sometimes causes errors in the command line.
After unpacking, open a terminal or command line in this folder. Connect your smartphone and enter the command adb devices. A window should appear on your phone screen asking you to allow debugging from this computer. Be sure to check the box Always allow from this computer and click OK. If the terminal displays the serial number of the device with status device, then the connection has been established successfully.
What to do if the device is displayed as unauthorized?
If the device status is unauthorized, try disconnecting and reconnecting the cable. Also check if your smartphone screen is locked. In rare cases, revoking debug permissions in the developer menu and re-confirming it helps.
Finding package names to remove
Before deleting anything, you need to know exactly the internal package names of the applications that you want to deactivate. System applications often have names that differ from those that are visible to the user on the desktop. For example, a popular browser may be hidden under the name com.google.chrome, and Google services - under the prefix com.google.android.gms.
The easiest way to find out the list of all installed packages is to run the command in the terminal:
adb shell pm list packagesThis command will display a huge list of all applications. You can use a filter to find something specific. For example, to search for all applications from Samsung enter adb shell pm list packages | findstr samsung (for Windows) or adb shell pm list packages | grep samsung (for macOS/Linux).
There are also specialized GUI utilities such as Universal Android Debloater or ADB AppControl. They automatically scan your device, show a list of apps with descriptions, and allow you to remove them in one click, making the process much easier for newbies. However, using console commands gives you greater control over the situation.
It is recommended to make a list of packages that you plan to remove in advance and check their purpose on the Internet. Removing critical system components may cause the phone to stop booting or lose connection.
- 📱 com.android.camera — standard camera application.
- 📺 com.google.android.youtube — YouTube video hosting client.
- 🛒 com.amazon.mShop.android.shopping — Amazon store application (often pre-installed).
- 🎮 com.facebook.katana — main social network application Facebook.
The process of deactivating and deleting applications
The main command for turning a system application into a user one (in fact, deleting it for the current user) is as follows. It does not permanently erase the application files from the system partition, but makes it invisible and inactive for the main user (User 0).
adb shell pm uninstall -k --user 0Instead substitute the full name of the application that you found in the previous step. The key -k means that the application data and cache will be preserved in case of recovery, although they will become inaccessible to the user.
If the command is successful, the terminal will return a message Success. The application will instantly disappear from the menu and list of installed apps. It is important to understand that this operation is reversible only until the first factory reset. After a full reset (Factory Reset), all system applications deleted in this way will return to their places.
⚠️ Attention: Do not try to remove packages associated with
com.android.systemui,com.android.phoneor Google Play services (com.google.android.gms) if you are not 100% sure of the consequences. This can lead to an endless reboot of the device.
For some users, it is important not just to hide the application, but to completely clear the device of its traces. In this case, you can use the command adb shell pm clear before deleting to erase all accumulated data, but the deletion itself occurs only through the command uninstall with the user flag.
☑️ Check before deletion
Restoring deleted system applications
What to do if you deleted unnecessary ones, and then realized that this application was needed? Since the APK files remain on the system partition, there is no need to download them again. It is enough to send a command to restore the package for the main user. This will return the application icon to the menu and restore its functionality.
The command for recovery looks like this:
adb shell cmd package install-existingIn older versions of Android (before 10-11), the command could be used adb shell pm install-existing, but in modern versions Android it is preferable to use the subcommand via cmd package. After execution, you will see the message again Success, and the application will become available.
If you used third-party utilities like ADB AppControl, there is usually a "Recovery" or "Trash" tab, where a list of deleted packages is stored. Recovery through such an interface occurs automatically without the need to manually enter commands, which is very convenient in case of a massive error.
In the event that the removal of a critical component caused the phone to become stuck on the logo upon boot, recovery through ADB may not be possible, since the system will not boot until the debugging stage is enabled. In such a situation, only entering Recovery mode and performing a factory reset (Wipe Data/Factory Reset) will help.
Removing via ADB does not erase the APK file from the system partition forever, but only disables it for the current user. This makes the method safe and reversible.
Comparison of application management methods
There are several approaches to managing pre-installed software, and the choice depends on your goals and level of training. Simply disabling it through settings is the safest but least effective method as the app continues to take up space. Using ADB is a happy medium that requires minimal technical skills. Obtaining root access gives maximum control, but carries high risks.
The table below compares the main characteristics of different methods for removing system applications on Android:
| Method | root access required | Frees up space | Risk of breakage | Reversibility |
|---|---|---|---|---|
| Disable in settings | No | No (data only) | Minimum | Full |
| Removal via ADB | No | Yes (for user) | Medium | Before reset |
| Removal from Root (System App Remover) | Yes | Yes (full) | High | Only with backup |
For most users, the method using ADB is the optimal balance between safety and efficiency. It allows you to get rid of the visual presence of the application and stop its background processes without violating the integrity of the system partition.
However, it is worth considering that interfaces and capabilities may change with the release of new versions of the operating system. What worked for Android 11may have other limitations for Android 14. Always check the relevance of the commands with the documentation for your specific firmware version before performing critical actions.
Frequently asked questions (FAQ)
Is it safe to remove Google applications via ADB?
Removing basic Google services (com.google.android.gms) will cause most applications that depend on them to not work (maps, Play store, push notifications). You can only uninstall client applications such as YouTube, Google TV or Google News if you don't use them.
Do you need to enable USB debugging every time?
If you selected the "Always allow from this computer" option when you first connected, then when you connect to the same PC, debugging will be activated automatically. However, the switch itself in the developer settings must remain enabled.
Will deleted applications return after a system update?
Usually no, the deletion status is retained. However, when you receive a major update to the Android version (for example, from 13 to 14) or when you reset to factory settings, all system applications will be restored to their original state.
Is it possible to delete an application that does not have an icon in the menu?
Yes, many system services run in the background and do not have an icon. They can be found and removed only by knowing the exact name of the package through the command pm list packages or using specialized software for analysis.
What is User 0 in the removal command?
In Android there is the concept of multi-user mode. User 0 is the primary owner of the device. The command removes the application only for this profile, leaving its files on the system in case you create a second user or decide to restore the application.