File manager CX Explorer has long become one of the most powerful tools for working with the file system Android —but its key advantage (access to system partitions) is often blocked by OS restrictions. You try to open a folder /data, /system or even /Android/obb, but you see the message "Refused in Android accesswhich has evolved with each new version - from Marshmallow 6.0 to Android 15.

In this article we will examine all current methods access unlocking - from basic settings in the interface CX File Explorer to advanced methods using ADB and modified firmware. Important: starting with Android 11, Google has tightened its access policy /data and /system partitions even for root usersso some methods will require workarounds. We'll also explain why simply granting "superuser permissions" through Magisk stopped working in 2023 and what to do about it.

Why CX Explorer does not see Android system folders

The reason lies in the security architecture Android, which divides the file system into three types of divisions:

  • 📁 User folders (/storage/emulated/0/, /sdcard/) - accessible to any application with permissions READ_EXTERNAL_STORAGE.
  • 🔒 Protected system partitions (/data, /system) - blocked SELinux and by the mechanism App Sandbox.
  • 🛡️ Kernel and boot partitions (/dev, /boot) - accessible only through fastboot or custom recovery.

Starting with Android 10, Google introduced a concept Scoped Storagethat restricts even root applications from accessing other people's data. For example, CX Explorer with superuser rights will not be able to read the files of another application in /data/data/com.example.app/unless explicitly granted permission through ADB or modification SELinux.

⚠️ Attention: On devices with Android 13+ and Dynamic Partitioning (for example, Pixel 6/7, Samsung Galaxy S23) an attempt to mount /system in recording mode can lead to soft-brick (the device boots, but is unstable). Before experiments, check the model via adb shell getprop ro.boot.dynamic_partitions.
Android version Main limitation Workaround
5.0–9.0 None Scoped Storage, but required root for /data Rights su via SuperSU/Magisk
10–11 Scoped Storage, blocking /Android/data/ for third-party applications ADB command pm grant + patch Magisk
12–14 Storage Access Framework (SAF), SELinux in mode enforcing Modification platform.xml or Shizuku

Method 1: Basic settings of CX Explorer (without root)

Before resorting to radical measures, check the settings yourself CX Explorer. Often the problem lies in disabled options:

  1. Open CX Explorer and tap on the three-dot menu (⋮) → Settings.
  2. Go to section Access to the root directory (Root access).
  3. Activate the switch Enable root access (if it is gray, you do not have rights su).
  4. In the section Display hidden files enable the option Show system files.

If after these manipulations folders /data or /system are still not displayed, which means that restrictions are imposed at the level Android, and additional actions will be required. Pay attention to the status bar at the bottom of the screen CX Explorer: if it says "Read only", then the partition is mounted in mode ro (read-only).

Developer mode activated (Settings → About phone → Build number ×7)

USB debugging enabled (Settings → System → For developers)

ADB drivers installed on PC (for Windows - via SDK Platform Tools)

Downloaded the latest APK of CX Explorer from the official website (not from Google Play)

-->

Method 2: Permissions via ADB (without root, for Android 10+)

Starting with Android 10, Google added a mechanism pm grantthat allows you to manually assign extended permissions to applications via ADBThis works even without root, but requires a connection to computer.

Follow the instructions:

  1. Connect the phone to the PC via USB and confirm debugging (the request “Allow debugging?»).
  2. Open the command line (Windows) or terminal (macOS/Linux) in the folder with platform-tools.
  3. Run the command to check the connection: 
    adb devices

    The serial number of your device should be displayed.

  4. Give CX Explorer permission to access protected folders: 
    adb shell pm grant com.cxinventor.file.explorer android.permission.MANAGE_EXTERNAL_STORAGE
  5. To access /Android/data/ add one more permission: 
    adb shell pm grant com.cxinventor.file.explorer android.permission.READ_EXTERNAL_STORAGE

After executing the commands, restart CX ExplorerNow it should display previously hidden folders, including /Android/obb/ And /Android/data/. Please note: Android 13+ this method may not work for /data/data/ —you will need root or Shizuku.

💡

If the command pm grant returns an error Operation not allowedtry first revoking all permissions for CX Explorer via adb shell pm revoke com.cxinventor.file.explorer android.permission.MANAGE_EXTERNAL_STORAGEthen grant them again.

Method 3: Using Shizuku (root alternative for new Android

Shizuku is a utility that allows applications to obtain rights close to rootthrough ADB without actually rooting. It is especially useful for Android 12+where traditional methods have stopped working.

Instructions for use. setup:

  1. Download Shizuku (official website) and install the APK on your phone.
  2. Connect the device to the PC and do: 
    adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
  3. In the application Shizuku click "Start" - the status should change to "Running».
  4. In CX Explorer go to Settings → Root access and select Shizuku (ADB).

Shizuku allows you to bypass Scoped Storage, but does not give full access to /data/data/ —this will still require rootBut the method works on Samsung Knox and other devices that are locked. bootloader.

⚠️ Attention: On some firmware (for example, MIUI 14+ or ColorOS 13+) Shizuku may be disabled after reboot. To avoid this, add a launch command to init.d or use Tasker to automatically execution adb script.

Method 4: Obtaining root access (Magisk or SuperSU)

If the previous methods did not work, the most reliable (but also the most risky) method remains - obtaining root access. On modern devices, this requires unlocking the bootloader, which leads to data reset and loss of warranty.

Step-by-step guide for Magisk:

  1. Unlock the bootloader via fastboot oem unlock (for Xiaomi — fastboot oem unlock-go).
  2. Flash custom recovery (TWRP or OrangeFox).
  3. Download the latest Magisk (APK) and flash it through recovery as a ZIP.
  4. Install Magisk Manager and check the status root.
  5. In CX Explorer enable the option Use root to mount.

On Android 11+ even with root Additional configuration may be required Magisk:

  • 🔧 Open Magisk → Settings → enable Zygisk.
  • 📋 Install the module Riru - Core i Riru - LSPosed.
  • 🔄 Reboot the device and check access in CX Explorer.
What to do if Magisk does not give root?

If after flashing Magisk in CX Explorer still no access, check:

1. Status SELinux via adb shell getenforce —if Enforcing, change to Permissive by command setenforce 0 (temporarily).

2. Availability of a module MagiskHide Props Config —it can block root for individual applications.

3. Kernel version: on some devices (for example Samsung Exynosa patch is required dm-verity via displax.

Method 5: Manually mounting partitions (for advanced)

If CX Explorer sees folders, but cannot open them (error “Mount failed”), the problem may be in the mount parameters. On devices with root you can manually remount the partition into recording mode:

su

mount -o rw,remount /system


mount -o rw,remount /data

For automatic mounting at startup CX Explorer:

  1. Create file /data/local/tmp/cx_mount.sh with the following contents: 
    #!/system/bin/sh

    mount -o rw,remount /data
    

    mount -o rw,remount /system

  2. Give execution rights: 
    chmod 755 /data/local/tmp/cx_mount.sh
  3. B CX Explorer go to Settings → Scripts → Add script and specify the path to the file.

On Android 12+ this method may not work due to AVB 2.0 (Android Verified Boot). In this case, you will need to disable signature verification via fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img.

ADB (pm grant)

Shizuku

Root (Magisk/SuperSU)

Manual mounting

Nothing helps

-->

Frequent errors and their solutions

Even after all the manipulations, you may encounter errors. Here are the most common ones and how to fix them:

Error Cause Solution
Permission denied when accessing /data SELinux in mode Enforcing or absence rights su Run setenforce 0 or check operation Magisk
CX Explorer freezes when opening /system Damaged file system or broken symlinks Execute fsck via recovery or remount the partition
Folders /Android/obb/ empty Scoped Storage or manufacturer restrictions (for example, Huawei) Use ADB or Shizuku to bypass restrictions

If you see the error “Failed to mount: Invalid argument", most likely the partition is mounted in erofs mode (read-only file system, used in Android 13+). Only flashing to custom software with support will help. On devices with ext4.

💡

On devices with Dynamic Partitioning (for example, Google Pixel, Samsung Galaxy S22+), an attempt to write data to /system will lead to automatic restoration of the original files the next time you boot. For permanent changes, you need to disable dm-verity And avb.

Is it possible to access /data without root?

On Android 10–12 partially - via ADB or Shizuku, but only to your data (/data/data/your.package/). Full access to other people's data (/data/data/com.whatsapp/) requires root.

Why after the update. Android access stopped working?

Most likely, the update reset Magisk or changed the policies SELinux. Try:

  1. Reflash Magisk in the same slot (without deleting).
  2. Check the status root via adb shell su.
  3. Update modules Riru and LSPosed.
How to regain access after resetting the settings?

Reset to factory settings deletes Magisk and all modifications. You will have to:

  • Unlock the bootloader again.
  • Flash Magisk via recovery.
  • Restore the backup copy of the data (if you made a backup via TWRP).

On some devices (for example, Samsung s Knox), a reset may block the ability to receive root forever.

Is it safe to use these methods?

Any intervention in system partitions carries risks:

  • 🔴 Soft-brick (the device does not boot, but is restored through the firmware).
  • 🔴 Loss of warranty (unlocking the bootloader is fixed in efuse).
  • 🔴 Blocking of banking applications (due to Magisk or modified build.prop).

We recommend creating full backups via TWRP before experiments.

Are there alternatives to CX Explorer?

If CX Explorer not copes, try:

  • 📁 Mixplorer - supports Shizuku and has a built-in FTP server.
  • 📁 Solid Explorer - works with root and SAF.
  • 📁 FX File Explorer - has plugin for ADB access.

On Android 14 the best results are shown Mixplorer with the module Mixplorer Silver.