Where system applications are stored in Android: a complete guide on paths and access methods

Have you ever wondered where exactly those applications that cannot be deleted using standard methods are hidden in your smartphone? We are talking about system APKs - from Google Play Services to proprietary utilities of the manufacturer like MiUI or One UI. These files take up disk space, are updated in the background, and sometimes conflict with user apps. But where to look for them?

Unlike regular applications, which are stored in a folder /data/app, system APKs are distributed across several protected sections of Android. Their location depends on the OS version, device model, and even the type of firmware (stock or custom). In this article, we'll look at system apps, how to view them (including non-root methods), and the risks associated with tampering with these files. If you plan to delete or modify system APKs, be sure to read to the warning section! all possible ways to system applications, ways to view them (including non-root methods), and the risks associated with tampering with these files. If you plan to delete or modify system APKs, be sure to read the warning section!

1. Main folders with system applications in Android

System APK files are distributed across three key sections of the Android file system. Their location is standardized, but may vary slightly depending on the manufacturer (for example, Samsung or Xiaomi add their own subfolders). Here are the basic paths:

• 📁 /system/app —standard Google and manufacturer applications integrated into the firmware. Examples: Calendar, Contacts, Samsung Knox.
• 📁 /system/priv-app —privileged system APKs with extended rights (for example, Services Framework or Telephony Provider). These applications are launched on behalf of the system.
• 📁 /vendor/app - applications specific to the hardware platform (camera drivers, communication modules, etc.). Often there are proprietary utilities like Mi Camera or Huawei Mobile Services.

On devices with dynamic partitions (Android 10+), part of the system APK can be stored in virtual volumes super.img. In this case, the physical paths will look like /system/system_ext/app or /product/app. You can check this through the command:

adb shell ls -la /system/ | grep "app"

⚠️ Attention: Starting from Android 11, Google has tightened control over system partitions. Even with root access, modifying files in /system can lead to soft-brick (the device boots, but is unstable) due to the dm-veritymechanism. Before making any changes, create a full backup via TWRP or OrangeFox.

2. How to View System APKs Without Root

If you don't have root access, your options for viewing system apps are limited, but they are there. Here are the working methods:

Method 1: Via ADB (Android Debug Bridge)

Connect the device to a PC with installed Platform Tools and execute:

adb shell pm list packages -s

This command will display a list all system packages (flag -s). To find the path to a specific APK, use:

adb shell pm path com.android.vending

Example output: package:/system/priv-app/Phonesky/Phonesky.apk. Please note that some paths may point to files (new package format in Android 10+). Method 2: Through a file manager with ADB access. Apps like .apex-files (new package format in Android 10+).

Method 2: Through a file manager with ADB access

Applications like Mixplorer or view system folders via FX File Explorer allow you to view system folders via FTP via ADB:

1. Enable USB debugging in the developer settings.
2. In the file manager, select ADB connection (usually in the side menu).
3. Go to /system/app or /system/priv-app.

⚠️ Attention: Some manufacturers (for example, Huawei or Oppo) block access to system folders even through ADB. In this case, only root or custom recovery will help.

3. Searching for system APKs on rooted devices

With root access, the possibilities expand. You can not only view, but also edit system files. Here's how to do it safely:

Method 1: Through Root Explorer

Install a file manager with root support (for example, Solid Explorer or Root Browser) and:

1. Give the application root access when request.
2. Go to /system and open the folders app, priv-app or vendor/app.
3. Pay attention to files with the extension .apk i .odex (optimized Dalvik cache).

Method 2: Through Terminal Emulator

Open a terminal on the device (for example, Termux) and do:

su
ls -R /system/app /system/priv-app /vendor/app

To find a specific application (for example, Google Play Market), use:

find /system -name "Phonesky"

Create a backup via TWRP|Check package dependencies (dumpsys package)|Disable automatic recovery (pm uninstall -k --user 0)|Make sure that the APK is not critical for the operation of the system-->

4. Features of storing system APKs in different versions of Android

With each new version of Android, Google changes its approach to storing system applications. Here are the key differences:

Android 9 Pie and older

Up to Android 10 system APKs were stored as separate files in /system. They could be easily modified or replaced via recovery. However, even then there was an integrity check mechanism (SELinux) that could block changes.

Android 10–12: dynamic partitions and APEX

C Android 10 Google has implemented dynamic sections (super.imgthat combine several traditional sections (system, vendor, product) into one virtual volume. This made accessing system files more difficult. In addition, .apexpackages have appeared - a new format for critical components (for example, com.android.art or com.android.tzdata).

Android 13+ and Project Mainline

In the latest versions of Android, some of the system components updated via Google Play System Updates (Project Mainline). These modules are stored in /apex and cannot be deleted or changed without breaking the system. Examples:

• 🔄 com.android.permission (permission management)
• 🔒 com.android.tethering (modem and access point)
• 📡 com.android.wifi (Wi-Fi drivers)

5. Risks and consequences of interfering with system APKs

Deleting or modifying system applications can lead to a variety of consequences - from harmless ones. glitches until the device is completely inoperable. Here's what you need to know:

Frequent problems after deleting system APK

• ⚠️ Bootloop (cyclic reboot) - if a critical component is deleted like com.android.phone.
• 📵 Loss of connection - deletion TelephonyProvider or ImsService will turn off calls and SMS.
• 🔋 Rapid battery drain - some system services are responsible for optimizing energy consumption.
• 🛑 Blocking OTA updates - a modified system may not pass integrity checks.

How to minimize risks

If you still decide to remove the system application:

1. First disable it via pm disable-user and check the stability of the work.
2. Use pm uninstall -k --user 0 instead of completely deleting it - this will keep the APK on the system, but will hide it from the user.
3. Before making any changes, study the dependencies of the package command:

   dumpsys package com.android.example | grep "dependencies"

⚠️ Attention: On devices with Samsung Knox or Huawei EMUI modification of system files may trigger the flag KNOX 0x1 or Tamper Detectedwhich will void the warranty and block some functions (for example Samsung Pay or Secure Folder).

6. Alternatives to deletion: how to disable system apps

If the goal is to free up space or get rid of annoying notifications, deletion is not always the best option. Here are safer ways:

Method 1: Disabling via ADB (without root)

Connect the device to the PC and do:

adb shell pm disable-user --user 0 com.android.bloatware

Replace com.android.bloatware with the package name (you can find it through pm list packages). This method hides the application from the system, but does not delete its files.

Method 2: Using Magisk and the Universal Android Debloater module

If you have root and installed Magisk, you can use modules to “neutralize” system applications:

1. Install Universal Android Debloater via Magisk.
2. Select applications to disable in the module interface.
3. Reboot the device.

The advantage of this method is the ability to restore disabled packages in one click.

Method 3: Replacing system APKs with dummies

For experienced users: you can replace the original APK with a modified one (for example, with removed services). To do this:

1. Download a “cleaned” APK (for example, from the forum XDA Developers).
2. Rename the original file to Name.apk.bak.
3. Place the new APK in the same folder and set the rights 644.

adb shell pm enable com.android.package

If the package was completely deleted, it can only be restored through flashing or backup.-->

7. How to restore deleted system applications

If after deleting the system APK the device becomes unstable, there are several ways to get everything back:

Method 1: Through TWRP backup

If you have system backup:

1. Boot into TWRP or OrangeFox.
2. Select Restore and mark the section System.
3. Confirm the restoration.

Method 2: Manual APK copy

If there is no backup, but there is another smartphone with the same firmware:

1. Copy the missing APK from another device (for example, /system/priv-app/Settings/Settings.apk).
2. Place the file in the appropriate folder on your device.
3. Install the correct ones rights:

   chmod 644 /system/priv-app/Settings/Settings.apk

4. Reboot the device.

Method 3: Flashing via Fastboot

If the system does not boot:

1. Download the official firmware for your model from the manufacturer's website.
2. Unpack the archive and find the file system.img.
3. Flash it via fastboot:

   fastboot flash system system.img

⚠️ Attention: When restoring system APKs via fastboot or TWRP, anti-rollback protection may work (for example, on devices Xiaomi or Oppo). This will block the bootloader. Always check the firmware version before restoring!

FAQ: Frequently asked questions about system applications in Android

adb shell dumpsys batterystats --charged