Pre-installed system applications, which the manufacturer blocks for removal through the standard settings menu, continue to take up space in the internal memory, consume RAM and drain the battery even in a new smartphone, requiring to be completely removed by connecting the device to a computer and using special tools to bypass access rights.
The only effective way to get rid of unnecessary system garbage is to use a computer and special debugging tools. Connecting to a PC opens access to hidden sections of the file system, allowing you to forcefully uninstall even those components that are considered an integral part of the firmware. However, this process requires extreme care, since an error can lead to the phone not working.
In this material we will examine in detail safe methods for deleting system files using the command adb without obtaining root access, as well as more radical methods for advanced users. You will learn which packages can be deleted without fear, and which packages are strictly forbidden to touch, so as not to turn the device into a โbrick.โ
Preparing equipment and enabling debugging
Before you begin manipulating system files, you need to prepare the working environment. You will need a computer running Windows, macOS or Linux, a working USB cable and, of course, the smartphone itself Android. A critical step is to install the ADB (Android Debug Bridge) drivers, which enable communication between the PC and the phone in debug mode. Without these drivers, the computer simply will not see the device in the desired mode.
On the smartphone itself, you need to activate the hidden menu for developers. To do this, go to Settings โ About phone and quickly click 7-10 times on the item Build number. After the message โYou have become a developerโ appears, return to the main settings menu, find the new section For developers and turn on the switch Debugging by USB. When you connect the cable to the PC, a request to allow debugging will appear on the phone screen - be sure to confirm it by checking the โAlways allow from this computerโ checkbox.
โ ๏ธ Attention: Enabling USB debugging gives the computer full access to control the phone. Never connect your smartphone to strangers or suspicious PCs in this mode, as attackers can gain access to your data.
Make sure the battery level is at least 50%. The process of removing system components, especially if it affects many files, can be energy-consuming, and suddenly turning off the device during the operation can damage the file system.
โ๏ธ Ready to remove system files
Installing and configuring ADB tools
To work we need a package Platform Tools, which is officially distributed by Google. Download the archive from the Android developers website and unpack it into a convenient folder, for example, the root of the C: drive. Inside you will find executable files adb.exe and fastboot.exe. In order not to enter the full path to the file every time, it is better to add the tools folder to the system environment variables or simply open the command line directly in this folder.
Open a terminal or command prompt (CMD) and enter the command to test the connection:
adb devices
If everything is configured correctly, you will see a list of connected devices with a unique serial number and status device. If unauthorizedis displayed instead, check your smartphone screen and confirm the debugging prompt. Status offline usually indicates a problem with the drivers or cable. In this case, try replacing the cable or reinstalling the USB drivers from your phone manufacturer.
Use the original cable from the smartphone manufacturer. Cheap cables from supermarkets often only support charging and do not transmit data, which will make it impossible to connect in debugging mode.
After a successful connection, you can proceed to identifying the names of the packages that need to be removed. The standard Android interface does not show the technical names of applications, but the command adb shell allows you to access the device shell. Next, using the command pm list packages, you will get a complete list of all installed packages. To search for a specific application, you can use a filter, for example: adb shell pm list packages | findstr facebook (for Windows) or adb shell pm list packages | grep facebook (for macOS/Linux).
Searching and identifying system packages
The most difficult part of the process is understanding what exactly a particular package is. System files often have names that mean nothing to the average user, for example com.android.browser or com.samsung.android.bixby.agent. Removing a key system component such as SystemUI or com.android.phonewill result in an infinite reboot or loss of connection.
For safe navigation, it is recommended to use specialized GUI utilities such as Universal Android Debloater or ADB AppControl. These apps automatically scan your device, display application names in plain language, and assign them a security status (Safe, Unsafe, Expert). If you prefer to work manually via the console, be sure to check package names with trusted lists on the Internet before deleting.
| Package name | Description | Risk of deletion | Recommendation |
|---|---|---|---|
com.google.android.youtube |
Official YouTube application | Low | Can be deleted if not used |
com.android.systemui |
System interface (status bar, notifications) | Critical | โ Prohibited delete |
com.google.android.gms |
Google Play Services | High | Deleting will break most applications |
com.samsung.android.app.spage |
Samsung News Feed (Bixby Home) | Low | Safe to delete |
com.android.phone |
Phone and call application | Critical | โ Loss of ability to make calls |
โ ๏ธ Attention: Interfaces and names of system processes may vary depending on the version of Android and the manufacturer's shell (MIUI, OneUI, ColorOS). Always check that the information is up to date for your specific model before deleting.
The removal process via the command line
When you have decided on the list of unnecessary applications, the moment of truth comes. To remove a package without root access, use the command pm uninstall with flag --user 0. This flag tells the system to delete the application only for the current user (primary), effectively hiding it and freeing up space, but leaving the file on the system partition in case of a factory reset. This is the safest method.
The command syntax is as follows:
adb shell pm uninstall -k --user 0
Parameter -k saves the application data and cache in case you want to restore it later, although when deleting a system application for user 0 this often makes no practical sense. After entering the command and pressing Enter, the system should return a message Success. If you see a message Failure [not installed for 0], it means that the application has already been uninstalled or is not installed for the current user.
It is important to remove one package at a time, checking the stability of the system after each operation. Bulk deleting dozens of apps at once can cause dependency conflicts that can be difficult to diagnose. If, after removing a component, the phone begins to behave strangely (notifications disappear, Wi-Fi does not work), restore the application immediately.
Using the --user 0 flag allows you to delete an application for a user without physically erasing it from the system partition. This makes the process reversible and safe for the integrity of the firmware.
Restoring deleted system components
The main advantage of the flag method --user 0 is the possibility of easy recovery. Since the application file physically remains on the /system or /productpartition, you can return it to a working state with one command. This saves you from having to reflash the device in case of an error.
To restore a deleted package, use the following command:
adb shell cmd package install-existing
In older versions of Android (up to 11), the command could be used pm install-existing, but in modern builds it is preferable to use cmd package. After executing the command, the application will reappear in the menu and function as usual. Make sure that the package name is entered without typos, otherwise the system will generate an error.
If you used the complete removal method (requires Root access and mounting the partition in write mode), recovery is only possible by reinstalling the APK file or resetting the device to factory settings. This is why experts recommend starting with the method for user 0.
What to do if the phone goes into a cyclic reboot (bootloop)?
If, after deleting a critical system file, the phone stops booting, try entering Recovery mode (usually by holding the Volume Up + Power button). Perform a factory reset (Wipe Data/Factory Reset). This will restore the default set of system applications. In extreme cases, you will need to flash the device via Flash mode (Odin for Samsung, Fastboot for Pixel, etc.).
Alternative methods and working with root access
For users who have received root access (superuser rights), more radical opportunities open up. Using file managers with Root support, such as Root Explorer or Mixplorer, you can directly go into the system folders /system/app, /system/priv-app or /product/app and physically delete APK files. This method frees up space on the system partition, which cannot be done through ADB without Root.
However, physical deletion carries increased risks. A misspelled file name or removal of a dependency may cause Android to fail to complete the download. In addition, rooting will often void the device's warranty and prevent banking apps and Google Pay services from working (although this can be bypassed using Magisk Hide).
There is also a method of using custom recovery (TWRP) to delete system partitions or install debloater scripts. This method is only suitable for experienced enthusiasts who understand the partition structure of their device's memory. Beginners are strictly not recommended to experiment with formatting partitions through recovery.
โ ๏ธ Attention: Physically deleting files from the system partition makes standard rollback of changes impossible. Before any actions with root access, be sure to create a full backup (NANDroid backup) through custom recovery.
Frequently asked questions (FAQ)
Is it safe to delete Google Play Services (GMS)?
No, it is extremely risky. Google Play services provide notifications, contact synchronization, maps, and authorization in most third-party applications. Removing them will result in the Play Market store and many installed apps not working. Delete only visible Google user applications, such as YouTube, Google TV or Google News, if you do not need them.
Will the deleted application return after a system update?
Yes, when updating the firmware over the air (OTA), the system often checks the integrity of the system partition and can restore packages deleted via ADB, since they are in the list of required for this version software However, applications deleted using the method for user 0 often remain hidden after the update, but may require disabling again.
Is it possible to delete system files without a computer?
Without root access - no. It is impossible to remove a system application using standard Android tools. With root access, you can use special uninstaller applications directly on your smartphone, but this requires first unlocking the bootloader and obtaining superuser rights, which in itself is a complex procedure.
What is Package Name and where can you find it?
Package Name (package name) is a unique application identifier in the system, for example, com.instagram.android. You can find it through ADB commands, in the application store (often indicated in the URL of the application page) or using special utilities like App Inspector installed on the phone itself.
Will deleting system files speed up the phone?
Yes, deleting unused system applications (bloatware) can free up RAM and reduce the load on the processor, since the background processes of these applications will no longer launch. However, the performance increase will be noticeable mainly on budget devices with a small amount of RAM. On powerful flagships, the difference may not be obvious.