The folder /system is the “heart” of the operating system Androidwhere critical files responsible for operation are stored devices: from the kernel and drivers to standard applications and fonts. However, finding it is not as easy as a regular folder with photos or music. Manufacturers hide the system partition from users by default - and for good reason.

Without special rights or tools, you will not see /system in a standard file manager. Even if you manage to detect it, any careless actions can lead to briku the device (complete inoperability). This article will help you figure out where the folder is physically located, how to access it in legal ways, and why 90% of users should never touch it unless absolutely necessary.

We will look at options for different scenarios: from simply viewing content to editing system files (only for experienced ones!). You will also find out what alternatives exist if you need to change system settings without the risk of damaging the device.

Why the System folder is hidden from the user

Android is built on the basis of Linuxwhere the partition /system is mounted in read-only mode (ro). This is done to protect against:

  • 🛡️ Accidental deletion critical files (for example, build.prop or framework-res.apk).
  • 🔒 Malwarethat could replace system libraries or services.
  • ⚙️ Incompatible modifications, leading to failures (for example, installing custom fonts without support).
  • 📱 Violations guarantees: most manufacturers (Samsung, Xiaomi, Google) will void the warranty if changes are detected in the system partition.

Starting from Android 10, Google has strengthened its security policy by introducing dynamic partitioning (Dynamic Partitions). Now /system can be part of a virtual volume super.img, which further complicates direct access.

⚠️ Attention: On devices with Android 12+ i Samsung Knox any changes to /system can activate the flag KNOX 0x1which blocks access to Samsung Pay, Secure Folder and encrypted data.

If you need to change system settings (for example, disable advertising in MIUI or change the boot animation), consider alternatives:

  • 🔧 Using ADB commands (without root).
  • 📱 Installation Magisk modules (requires unlocking bootloader).
  • 🖥️ Application custom firmware (for example, LineageOS).
📊 Why do you need access to the folder /system?
Remove bloatware (built-in applications)
Change system fonts/icons
Debug the device
Just wondering
Another option

Where is the System folder physically located on Android

The physical location of the partition depends on the device's memory architecture:

Device type Location /system Features
Old smartphones (up to Android 9) /dev/block/mmcblk0pX (where X is the partition number) Separate partition on flash memory (eMMC/UFS).
Android 10–11 (Dynamic Partitions) Inside super.img (virtual volume) Partition system mounted as a subvolume.
Android 12+ (with Virtual A/B) /dev/block/by-name/system or super Can be duplicated for trouble-free updates.
Devices Samsung (One UI) /system_root (symlink to /system) A mechanism dm-verity is used to check integrity.

You can see the real path through Terminal Emulator or ADBby running the command: 

ls -l /dev/block/by-name/ | grep system

At the output you will get something like: 

lrwxrwxrwx 1 root root 16 2023-01-01 12:00 system -> /dev/block/mmcblk0p42

However, even knowing the physical address, you cannot just mount it - you will need root access or special utilities like DiskInfo (available in Google Play).

💡

On devices with Medatekprocessors (for example, Redmi Note 8), the section /system can be called system_ext - this is normal and not an error.

How to find the System folder through a standard explorer

In 99% of cases, you are you won't see /system in a standard file manager (for example, Files by Google or Mi File Manager). Manufacturers limit access to the root directory / by default. data-i="122">you won’t see

Method 1: Use root-enabled explorer

  • 📁 Install Root Explorer, Solid Explorer or FX File Explorer.
  • 🔑 Give them root access (if the device is rooted).
  • 🔍 Go to the root folder / → find system.

Method 2: Connect to PC via ADB

  1. Enable USB debugging in Settings → About phone → Build number (tap 7 times).
  2. Connect your phone to the PC and run in ADB: 
    adb shell

    ls /system

  3. To view contents: 
    adb pull /system/

Method 3: Use Termux (without root)

  • 📱 Install Termux from F-Droid (version from Play Market is outdated).
  • 🔧 Run: 
    pkg install coreutils

    ls -la /system

    (there will be an access error, but you will see a list of files if the partition is mounted).

⚠️ Attention: On Android 13+ even with root some files c /system may be hidden due to the mechanism namespace isolationUse su -mm to bypass.

Make sure the battery charge is > 50%

Make a backup copy of your data (TWRP or Titanum Backup)

Disable antivirus (may block ADB)

Have stock firmware on hand for recovery-->

How to access the System folder without root (restricted mode)

If you do not have root access, you can still view (but not edit!) some files from /system using ADBHere are step-by-step guide:

Step 1: Install ADB on PC

  • 🖥️ Download Platform Tools from Google.
  • 📂 Unpack the archive and add the path to adb.exe to environment variables (or run from folder).

Step 2: Connect the device

  • 🔌 Turn on USB debugging and connect the phone.
  • 🔑 Confirm the trusted connection on the screen smartphone.
  • 📋 Check the connection: 
    adb devices

    (the serial number of the device should be displayed).

Step 3: View the contents of /system

  • 🔍 To see the files: 
    adb shell ls /system
  • 📄 To view a specific file (for example, build.prop): 
    adb shell cat /system/build.prop
  • 💾 To copy a file to a PC: 
    adb pull /system/build.prop C:\temp\

⚠️ Restrictions without root:

  • 🚫 Not possible edit or delete files.
  • 🔒 Some folders (for example, /system/priv-app) may be hidden.
  • 📵 On Samsung and Huawei may need to be disabled RMM/Knox.
What is build.prop and why look at it?

The file /system/build.prop contains key firmware parameters: device model (ro.product.model), Android version (ro.build.version.release), screen density (ro.sf.lcd_density), etc. It is often edited for:

- Unlocking hidden functions (for example, qemu.hw.mainkeys=0 to display soft buttons).

- Screen DPI changes (for example, ro.sf.lcd_density=420).

- Cheating applications (for example, ro.product.brand=Google for compatibility).

⚠️ Editing without knowledge can lead to a bootloop (loop loading)!

Full access to the System: unlocking the bootloader and root

If you need full control over the folder /system, you will need:

  1. Unlock bootloader (bootloader).
  2. Install custom recovery (for example, TWRP).
  3. Get root access via Magisk.

Step 1: Unlocking the bootloader

  • 🔓 For Google Pixel, OnePlus, Xiaomi: 
    fastboot flashing unlock
  • 🔧 For Samsung need Odin and file BL (bootloader).
  • ⚠️ On Huawei i Honor Unlocking is officially prohibited (you will need to bypass through DC-Unlocker).

Step 2: Installing TWRP

  • 📥 Download the image TWRP for your model from official website.
  • 🔄 Flash via fastboot: 
    fastboot flash recovery twrp-3.7.0_9-0-redfin.img
  • 🔄 Boot into recovery: fastboot reboot recovery.

Step 3: Getting root via Magisk

  • 📁 Download the latest version Magisk (.zip).
  • 🔧 In TWRP select Install → specify the file Magisk → Swipe to Confirm.
  • 🔄 Reboot: reboot system.

After that you can:

  • 📂 Mount /system in recording mode (mount -o rw,remount /system).
  • 🗑️ Delete built-in applications (bloatware).
  • 🎨 Modify system APKs (for example Settings.apk to add new functions).
⚠️ Attention: On devices with Android 11+ and AVB 2.0 (Android Verified Boot) after changes in /system you will need to disable signature verification (avbctl disable-verification), otherwise the phone will not boot.
💡

Unlocking bootloader erases all data on the device! Make a backup in advance via TWRP or Titanum Backup.

What you can do with the System folder (and what you can’t)

Even with root access not all operations. safeHere is what is allowed and prohibited:

✅ Allowed (with caution):

  • 🗑️ Removing bloatware (built-in applications, for example /system/priv-app/MiBrowser).
  • 🎨 Replacing system fonts (/system/fonts) or animations (/system/media).
  • 📱 Modification build.prop to unlock hidden functions (for example, persist.sys.ui.hwrot=0 to disable hardware screen rotation).
  • 🔊 Modification of sound files (/system/media/audio), for example, replacing the boot melody.

❌ Prohibited (high risk of bricking):

  • 🚫 Deleting or changing files in /system/bin or /system/lib (libraries and binaries).
  • 🚫 Editing /system/etc/permissions (Android permission settings).
  • 🚫 Changing files in /system/framework (for example, framework-res.apk).
  • 🚫 Deleting /system/vendor (drivers for hardware).

🔧 Alternatives to editing /system:

Purpose Safe way Requires root?
Uninstall built-in applications Use ADB AppControl or pm uninstall -k --user 0 ❌ No
Change DPI screen Application App Settings (Xposed) or wm density via ADB ✅ Yes (for Xposed)
Replace boot animation Use BootAnimations (Magisk module) ✅ Yes
Disable advertising in MIUI ADB commands (settings put global hidden_api_policy 1) ❌ No

Dangers and how to restore the system after errors

If after changes to /system device:

  • 🔄 Looped on loading (bootloop) → try booting into Safe Mode (hold Volume down when turned on).
  • 🚨 Does not turn on completely → flash the stock firmware via Odin (Samsung) or Fastboot (Pixel, OnePlus).
  • 📵 Lost network → check the files in /system/vendor/rfs/msm (modem data could be damaged).

Recovery methods:

  1. Rollback via TWRP:
    • Boot into recovery.
    • Select Mount → System.
    • Restore the backup (Restore).
  2. Stock firmware:
    • For Samsung: use Odin + file AP (firmware).
    • For Xiaomi: Mi Flash Tool + fastboot-firmware.
    • For Google Pixel: flash-all.bat from the factory image.
  • Recovery via ADB Sideload: 
    adb sideload update.zip

    (requires official OTA update package).

    • ⚠️ Attention: On devices with A/B partitions (for example Pixel, OnePlus) after unsuccessful modification /system slot switching may be required: 
    fastboot --set-active=_b

    fastboot reboot

    💡

    If after changes to /system the phone stops booting, first try resetting the settings via recovery (Wipe → Factory ResetThis often helps with damaged user settings). data, not system files.

    FAQ: Frequently asked questions about the System folder on Android

    Is it possible to access /system without root?

    Yes, but only for reading via ADB. edit or delete files. For example, you can view the content build.prop, but not change it.

    To write, you definitely need root access or custom recovery (TWRP).

    Why doesn’t the phone turn on after editing /system?

    Most likely, you:

    • Deleted a critical file (for example, /system/bin/sh).
    • Changed access rights (chmod) to system binaries.
    • Damaged build.prop (syntax error).

    Solution: flash the stock firmware or restore the backup via TWRP.

    How to copy files from /system to PC?

    Method 1: Via ADB (without root):

    adb pull /system/build.prop C:\android_backup\

    Method 2: Through TWRP (with root):

    • In recovery, select Mount → System.
    • Connect the phone to the PC and copy the files manually.
    Is it possible to increase the partition size /system?

    Technically yes, but it is extremely risky. The size /system is hardcoded in the partition table (partition tableTo change it you will need:

    1. Unlock bootloader.
    2. Change the partition table via gdisk or parted.
    3. Reflash the modified boot.img i super.img.

    ⚠️ An error will result to the loss of all data and possible loss of IMEI!

    Where is /system stored on Samsung with One UI?

    On devices Samsung (starting from Android 9) folder /system can be displayed like:

    • /system_root/system (symbolic link).
    • Part of a virtual volume super.img (inside system.img).

    To access use:

    adb shell

    su
    

    mount -o rw,remount /system_root