Removing root applications on Android: a complete guide with risks and solutions

System applications on Android take up precious space in memory, consume resources in the background and often remain unnecessary after purchase smartphone. But removing them is not an easy task: manufacturers block such actions without superuser rights (root). Even with root access, careless manipulations can lead to "brick" devices - complete loss of functionality.

This article will help you figure out how to properly remove root applications, what tools exist for this, and what to do, if after cleaning the phone stops working. We will consider both manual methods through ADB and Terminal Emulator, as well as specialized apps like Titanium Backup or System App Remover. We will pay special attention list of system packages safe to remove to the list of system packages safe to remove

Before you begin, answer yourself two key questions: do you really need to remove these applications (perhaps disabling them is enough?), and are you prepared for the possible consequences - from loss of warranty to the need to reflash the device. If in doubt, start with the least risky methods described at the end of the article.

What are root (system) applications and why can’t you just delete them

Root applications are apps installed by the manufacturer in the partition /system or /vendor at the stage of flashing the device. They are divided into three categories:

1. Critical services —responsible for the operation of the OS (for example, com.android.phone for phone calls).
2. Branded utilities —branded shells like One UI from Samsung or MIUI from Xiaomi.
3. Pre-installed blockware - games, social networks or services (for example, Facebook, Netflix), which the manufacturer added under a contract with partners.

Android by default blocks the removal of such applications through standard settings. Even the command adb uninstall will return an error Failure [DELETE_FAILED_INTERNAL_ERROR]if the package is in a protected section. This is done to prevent accidental damage to the system - for example, deleting com.android.settings will deprive you of access to the phone settings.

Manufacturers also use a mechanism OEM locks: even on an unlocked bootloader, some packages may be protected by a signature, and their modification will lead to triggering Knox (on Samsung) or DM-Verity (system integrity check at boot).

⚠️ Attention: On devices with Samsung Knox (Galaxy S series, Note, fold), deleting system applications can lead to a flag trigger KNOX 0x1. This will irreversibly void the warranty and block access to Samsung Pay, Secure Folder and corporate features.

Preparing the device: rooting and backing up

Before deleting anything, you must obtain root access. The methods depend on the device model: Root access unlocking the bootloader via

• 🔧 Suitable for most smartphones Magisk (recommended method) - it allows you to get root without changing the system partition (systemless root).
• 📱 On devices Xiaomi Unlocking the bootloader via Mi Unlock Tool, then flashing custom recovery (TWRP) and installing Magisk.
• 🤖 To Google Pixel enough to unlock the bootloader with the command fastboot flashing unlock and flash Magisk via fastboot.

After getting root, be sure to create full backup of the system. For this, the following are suitable:

• 💾 TWRP (if custom recovery is installed) - creates an image of the partition /system.
• 📦 Swift Backup (requires root) - saves applications and data to the cloud or to a memory card.
• 🖥️ Command adb backup is an outdated method, but suitable for backing up user data.

Important: backup via Titanium Backup does not save the system data itself applications - only their data. To fully restore after an unsuccessful deletion, you will need a partition image /system.

Get root access (Magisk/TWRP)

Create a backup via TWRP or Swift Backup

Check the list of packages safe to delete

Temporarily disable antivirus (may block ADB)

Charge the phone at least 50%-->

Ways to remove root applications: from simple to complex

There are three main methods for removing system packages. The choice depends on your experience and device model:

1. Through specialized applications (the easiest way)

apps like System App Remover or Debloater provide a graphical interface for removing packages. Algorithm of actions:

1. Install the application from Google Play or F-Droid.
2. Give root access when prompted.
3. In the list, mark unnecessary applications (for example, com.sec.android.app.launcher for the standard launcher Samsung).
4. Click Uninstall and restart the device.

2. Via ADB (without full root, but with USB debugging)

This method works even without permanent root, but requires USB debugging to be enabled (Settings → For developers → USB debugging). Commands for removal:

adb shell
pm uninstall -k --user 0 com.package.name

Here --user 0 means removal only for the current user (does not affect system files). Disadvantage of the method: after resetting the settings or updating the OS, the applications will return.

3. Manually via Terminal Emulator or ADB Shell (for experienced ones)

To completely remove the package from the system, use:

su
mount -o rw,remount /system
rm -rf /system/app/PackageName
rm -rf /system/priv-app/PackageName
mount -o ro,remount /system

Where PackageName is the folder with the application (for example, BasicDream for standard wallpapers on Samsung). An error in the path will lead to the deletion of critical files!

List of system packages safe to remove (by brand)

The following are packages that can be deleted without critical consequences on most devices. However, even here there are nuances - for example, deleting com.google.android.gm (Gmail) can disrupt the operation of other Google services.

Universal packages (for all Android):

For Samsung devices (One UI):

• com.sec.android.app.launcher —standard launcher (replace with Nova Launcher before deleting).
• com.samsung.android.app.spage — Bixby Home (left panel on the main screen).
• com.samsung.android.bixby.agent — Bixby voice assistant.
• com.sec.android.app.sbrowser — Samsung Internet browser.

For Xiaomi devices (MIUI):

• com.miui.analytics — statistics collection (safe to delete).
• com.xiaomi.mipicks — theme and wallpaper store.
• com.miui.hybrid —part Quick Apps (mini-applications).
• com.miui.player —standard music player.

⚠️ Attention: On some firmware MIUI deleting packages com.miui.* may lead to a reboot loop. Before cleaning, disable the function MIUI Optimization in the developer settings with the command:

adb shell settings put global miui_optimization_disabled 1

What to do if after removal the phone does not turn on or is unstable

If the device hangs on the logo or goes to bootloop (cyclic reboot), first of all try to boot into Safe Mode (hold the power button → long tap on “Turn off” → “Safe Mode”). In this mode, system applications are disabled, and you can roll back changes.

If Safe Mode is not available:

1. Recovery via TWRP:
   • Boot into recovery (Power + Volume Up).
   • Select Restore and restore the backup /system.
   • If there is no backup, flash the original firmware via Odin (Samsung) or Fastboot (Pixel/Xiaomi).

adb push com.package.name.apk /system/priv-app/
adb shell chmod 644 /system/priv-app/com.package.name.apk

If the device turns on, but not all functions work (for example, the mobile network or Wi-Fi has disappeared), check whether you have deleted packages like:

• com.android.phone - phone calls;
• com.android.providers.telephony - databases network;
• com.android.bluetooth —Bluetooth module.

Alternatives to deletion: disabling and freezing applications

If the risks of deleting system packages seem too high, consider safer alternatives:

1. Disabling through Android settings

Go to Settings → Applications → Show system ones, select an unnecessary application and click Disable. This will stop it from working and hide it from the menu, but will not free up disk space.

2. Freezing via Titanium Backup or App Quarantine

apps like Titanium Backup allow you to “freeze” an application - it will remain in the system, but will not start. Advantage: you can quickly defrost if something goes wrong.

3. Using ADB to deactivate without uninstalling

The command below will disable the package for the current user, but will not affect system files:

adb shell pm disable-user --user 0 com.package.name

To return the application, replace disable-user with enable.

4. Installing custom firmware

Firmwares like LineageOS or Pixel Experience are initially devoid of bloatware and offer “pure” Android. Disadvantage: requires an unlocked bootloader and experience with fastboot.

Risks and how to minimize them: advice from experts

Even experienced users sometimes encounter problems after cleaning system applications. Here real cases and ways to prevent them:

1. Loss of the mobile network after removal com.qualcomm.qti.telephonyservice

This package is responsible for the operation of the modem on devices with chipsets Qualcomm. Solution: restore it from a backup or flash the firmware via QFil (for Qualcomm).

2. Cyclic reboot after deletion com.android.systemui

SystemUI is the interface of notifications, taskbar and lock. Without it, the phone will not boot. Restore the package via TWRP or reflash system.img.

3. Error "Android is not running" after cleaning /data/dalvik-cache

This folder contains optimized versions of applications. If you accidentally deleted it, run the TWRP command Wipe → Advanced Wipe → Dalvik Cache, then reboot.

To minimize risks:

• 🔍 Before deleting, check the package on sites like Android Package Names or forums XDA Developers.
• 📌 Uninstall one application at a time and reboot the device to check stability.
• 🛡️ Use Magisk instead of classic root - it allows you to roll back changes through modules.
• 📱 On devices with A/B-partitions (Pixel, new Samsung) flash changes to both slots (fastboot --set-active=a and fastboot --set-active=b).

adb shell getprop ro.boot.slot_suffix

FAQ: Frequently asked questions about deleting system applications