Getting root access on Android allows access to system files, hidden settings and advanced device management options. However, this process is fraught with risks - from loss of warranty to complete โ€œbrickingโ€ of the smartphone. Root Explorer (or any other file manager with root support) becomes a powerful tool for editing system partitions, backing up applications with data, and even removing firmware.

In this article we will figure out how to safely get root access on modern versions of Android (including Android 13/14), what tools are needed for this, and how to configure Root Explorer or its analogues (FX File Explorer, Solid Explorer) to work with root access. We will pay special attention alternative methods for devices with a locked bootloader and workarounds without full rooting.

We warn you right away: the procedure requires technical training. If you have never worked with ADB, Fastboot or custom firmware, it is better to practice on an old device. And for most tasks (clearing cache, transferring applications to an SD card) there are legal alternatives without rooting.

๐Ÿ“Š Why do you need Root Explorer?
Removing built-in applications
Backup system data
Changing system files (hosts, build.prop)
CPU overclocking/modding
Other

1. What are root access and why you need them for Root Explorer

root access (or superuser rights) on Android, similar to administrator rights in Windows. They allow you to:

  • ๐Ÿ“ edit system files in folders /system, /data, /vendor;
  • ๐Ÿ”ง delete pre-installed applications (bloatware) that cannot be uninstalled using standard methods;
  • ๐Ÿ”„ create full backup copies of applications along with their data (including game saves);
  • ๐Ÿ› ๏ธ modify system settings (for example, change build.prop to cheat applications or overclock the CPU).

Root Explorer is a file manager that can work with root access. Without them, it is no different from the standard Explorer. With root access you can:

  • ๐Ÿ” view hidden system folders;
  • ๐Ÿ“ edit files with rights rw-r--r-- (read only);
  • ๐Ÿ—‘๏ธ delete protected files, including remnants of viruses or undeletable updates;
  • ๐Ÿ”„ mount partitions in write mode (mount -o rw,remount /system).

However starting with Android 10 Google has tightened its security policy: many system partitions are now mounted read-only (ro), and their modification requires additional tricks (for example, using Magisk or patching boot.img).

โš ๏ธ Attention: On devices with Samsung Knox (Galactic smartphones and tablets) obtaining root access the Knox flag is irreversibly triggered (0x1), which voids the warranty and blocks access to Samsung Pay, Secure Folder and some banking applications.

2. Preparing the device: what needs to be done before rooting

Before you start obtaining root access, complete the required steps steps:

Unlock OEM unlocking in developer settings

Back up important data (photos, contacts, messages)

Charge the device at least 70%

Install ADB/Fastboot drivers on PC

Download the official firmware for your model (in case of recovery)-->

First of all, activate developer mode:

  1. Go to Settings โ†’ About phone.
  2. Find the item Build number and tap on it 7 times.
  3. Return to the main settings menu - a new section will appear For developers.

Inside enable it:

  • ๐Ÿ”“ OEM unlocking (allows bootloader unlocking);
  • ๐Ÿ–ฅ๏ธ USB debugging (to work with ADB);
  • ๐Ÿ”„ Unlocking the bootloader (on some devices, for example Xiaomi).

On devices Huawei, Honor and some models Sony may be required unlock code, which is available on the manufacturer's official website. For Samsung a patch is often needed. via Odion or Magisk.

โš ๏ธ Attention: Unlocking the bootloader on most devices erases all data (including internal memory) Do not rely on Google backups - they do not save SMS, calls and some settings. applications.

3. Methods for obtaining root access in 2026

Rooting methods depend on the Android version, device model and bootloader status:

Method Suitable for Pros Cons
Magisk (Patched Boot) Android 9โ€“14, most devices Secure (systemless), support for OTA updates Requires an unlocked bootloader, patching boot.img
SuperSU (outdated) Android 5โ€“8, older devices Easy to install Does not support new versions of Android, conflicts with SafetyNet
OneClick-root (KingRoot, iRoot) Devices with vulnerabilities in the kernel No PC needed, works on some Chinese smartphones High risk of malware, unstable operation
Custom recovery (TWRP) Device with TWRP support Full control over the firmware, Nandroid backups Difficult to install on new devices (A/B partitions)

The most universal and safe method is Magisk. It works on the principle of systemless-root, that is, it does not modify the system partition, but replaces boot.img. This allows you to pass verification SafetyNet (needed for banking applications) and receive. OTA updates.

To install Magisk:

  1. Download the latest version Magisk from official repository (file Magisk-vXX.X.zip).
  2. Extract boot.img from the firmware of your device (you can via Payload Dumper to .ozip/.payload.bin).
  3. Open Magisk Manager (or patch manually via ADB):
    adb push boot.img /sdcard/
    

    adb shell

    su

    magisk --patch /sdcard/boot.img

  4. Flash patched magisk_patched.img via fastboot:
    fastboot flash boot magisk_patched.img
    

    fastboot reboot

What to do if Magisk is not flashed?

If after flashing the patched boot.img the device boots into bootloop (cyclic reboot), try:

1. Flash the original boot.img. back.

2. Use an alternative method (for example, flash Magisk via custom recovery, if it is available for your model).

3. For devices with dynamic partitions (Android 10+), you may need to patch init_boot.img instead of boot.img.

4. (for example, Samsung) you need to disable AVB (Android Verified Boot) through the command:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

4. Setting up Root Explorer after getting root

After successful rooting, install Root Explorer (or alternatives: FX File Explorer, MiXplorer, Solid Explorer) from Google Play or APKMirrorWhen you first start:

  1. Give the application root access (a request will appear from Magisk or SuperSU).
  2. In the settings, enable:
    • ๐Ÿ”’ Mount File System (mount how R/W);
    • ๐Ÿ‘๏ธ Show Hidden Files (show hidden files);
    • ๐Ÿ”„ Root Access Mode (access mode - select Superuser or Magisk).
  • To edit system files (for example /system/build.prop) first mount the partition in write mode:
    mount -o rw,remount /system
  • Important folders in Root Explorer:

    • ๐Ÿ“ฑ /data/app โ€” user applications;
    • ๐Ÿ”ง /system/app and /system/priv-app โ€” system applications;
    • ๐Ÿ“„ /data/data โ€” application data (saves, cache);
    • ๐Ÿ”’ /system/etc โ€” configuration files (hosts, permissions).
    ๐Ÿ’ก

    Before editing system files, always make a backup copy of them! For example, copy /system/build.prop to /sdcard/build.prop.bak. This will help restore the device's functionality in case of an error.

    To remove built-in applications (bloatware):

    1. Go to /system/app or /system/priv-app.
    2. Find the folder with the name of the unnecessary application (for example, Facebook, GooglePlayMovies).
    3. Delete the folder or rename it (add .bak at the end).
    4. Reboot the device.
    โš ๏ธ Attention: Removing critical system applications (for example, Settings, TelephonyProvider) may lead to device failure. Before deleting, check the package name through ADB:
    adb shell pm list packages | grep "keyword"

    5. Alternatives to Root Explorer without full rooting

    If rooting is not possible (locked bootloader, corporate device) or is too risky, consider alternatives:

    • ๐Ÿ”ง ADB commands without root: some operations (uninstalling applications, changing settings) can be performed through ADB with user rights. For example, disabling an application:
      adb shell pm disable-user --user 0 com.package.name
    • ๐Ÿ“ Shizuku + AppOps: tool Shizuku allows you to manage application permissions without root (required ADB).
    • ๐Ÿ”„ Custom firmware without root: some firmwares (for example, LineageOS) offer advanced settings without the need for rooting.
    • ๐Ÿ—‘๏ธ Debloater tools: Universal Android Debloater (GUI for PC) removes pre-installed applications via ADB.

    To backup data without root, use:

    • ๐Ÿ“ฑ Swift Backup (works via ADB backup);
    • ๐Ÿ”ง Titanium Backup (requires root, but there are workarounds for some functions);
    • โ˜๏ธ Cloud services (Google Drive, Syncthing) to synchronize files.
    ๐Ÿ’ก

    If your goal is to simply remove unnecessary applications or free up space, try methods without rooting first. Obtaining root access is only justified for deep modification of the system.

    6. Risks and how to minimize them

    Root access violates the integrity of the Android system, which entails. the following risks:

    • ๐Ÿšจ Loss of warranty: most manufacturers will void the warranty if a root is detected (checked through getprop ro.boot.verifiedbootstate).
    • ๐Ÿ›ก๏ธ Problems with SafetyNet: banking applications (Sberbank, Tinkoff), Google Pay and some games (for example, Pokรฉmon GO) can block operation on rooted devices.
    • ๐Ÿ› Vulnerabilities security: malware with root access can gain full control of the device.
    • ๐Ÿ’ฅ "Brick" devices: incorrect editing of system files or flashing the wrong firmware boot.img can make the smartphone inoperable.

    How to reduce risks:

    • ๐Ÿ”’ Use MagiskHide (or Universal SafetyNet Fix) to bypass SafetyNet checks.
    • ๐Ÿ“ฑ Regularly update Magisk and the device kernel.
    • ๐Ÿ”„ Make backups via TWRP or OrangeFox Recovery before any modifications.
    • ๐Ÿ› ๏ธ Install only verified Magisk modules (from the official repository).

    To check the SafetyNet status, use the command:

    adb shell su -c "magisk --safetynet-check"

    Or application YASNAC (Yet Another SafetyNet Attestation Checker).

    โš ๏ธ Attention: On devices with Android 12+ and kernel 5.10+ some Magisk modules may not work due to stricter policy SELinuxBefore installing the module, check its compatibility. forums XDA Developers.

    7. How to cancel root access and return the device to its original state

    If you need to return the warranty, sell the device or fix problems after rooting, follow these steps:

    1. Uninstall Magisk:
      • Open Magisk Manager.
      • Go to Settings โ†’ Delete Magisk deleted): Settings โ†’ Remove Magisk.
      • Select Complete removal (this will restore the original boot.img).
  • Flash the original boot.img (if Magisk is not uninstalled):
    fastboot flash boot stock_boot.img
    

    fastboot reboot

  • Return stock recovery (if you installed TWRP):
    fastboot flash recovery stock_recovery.img
  • Reset settings via Settings โ†’ System โ†’ Reset (or via recovery).
  • Close the bootloader (optional, but recommended for warranty):
    fastboot oem lock
    โš ๏ธ Attention: Locking the bootloader erases all data! Do this only after a complete reset.
  • For devices Samsung you may additionally need to reset the flag Knox via Triangle Away (does not work on all models). through Xiaomi check unlock status via fastboot oem device-info โ€” if Device unlocked: false, the bootloader is successfully locked.

    After all manipulations, check the status of the device:

    • ๐Ÿ” Run adb shell su โ€”if an error appears Permission denied, root has been removed.
    • ๐Ÿ“ฑ Install Root Checker from Google Play - the application should show the lack of root access.

    FAQ: Frequently asked questions about Root Explorer and rooting

    Is it possible to get root on Samsung with Knox?

    Technically yes, but the Knox flag to work irreversibly. (the status will change from 0x0 to 0x1This will cause:

    • Loss of warranty;
    • Blocking Samsung Pay, Secure Folder, Samsung Health;
    • Problems with some banking applications.

    On new devices (for example, Galaxy S22+it is impossible to bypass Knox For older models (before Galaxy S10) sometimes resetting through Triangle Awayhelps, but there are no guarantees.

    How to edit the hosts file without root?

    It is impossible to edit without root, but there are workarounds: /system/etc/hosts You can't, but there are workarounds:

    1. Via ADB (temporary solution, resets after reboot):
      adb shell
      

      su

      mount -o rw,remount /system

      echo "127.0.0.1 example.com" >> /system/etc/hosts

      mount -o ro,remount /system

    2. Blocking applications: Blokada, AdGuard or NextDNS can block domains at the VPN level without changing hosts.
    3. Magisk modules: if there is root, install the module Systemless Hosts from the Magisk repository.
    Why does Root Explorer not see system folders?

    Possible reasons and solutions:

    • ๐Ÿ”Œ No root access: check whether rights are granted in Magisk or SuperSU.
    • ๐Ÿ”’ SELinux in Enforcing mode: run setenforce 0 (temporary solution) or install the module Magisk to change the policy.
    • ๐Ÿ“ Folders are hidden: in the Root Explorer settings, enable Show Hidden Files.
    • ๐Ÿ”„ System partition in read-only mode: mount it in writing mode:
      mount -o rw,remount /system
    How to transfer applications to an SD card without root?

    Starting from Android 6.0, Google has limited the ability to transfer applications to SD Alternatives:

    • ๐Ÿ“ฑ Adoptable Storage: format the SD card as. internal memory (all data on it will be encrypted and linked to the device). Settings โ†’ Storage โ†’ SD card โ†’ Format as internal storage.
    • ๐Ÿ”ง Applications with SD support: some applications (for example, Spotify, Netflix) allow you to save data to the card without root.
    • ๐Ÿ“ Manually moving files: via Files by Google or Total Commander you can manually transfer media files, but not APK.
    • ๐Ÿ› ๏ธ ADB commands: works for some applications command:
      adb shell pm set-install-location 2

      (but most modern applications ignore this).

    On Android 11+ even Adoptable Storage may not work - manufacturers often block this function.

    Is it possible to update the firmware with root access?

    Yes, but with reservations:

    • ๐Ÿ”„ Via OTA: if you have Magiskinstalled, temporarily remove it (there is an option in Magisk settings Uninstall โ†’ Restore Images), accept update, then flash Magisk again.
    • ๐Ÿ“ฑ Through custom recovery: download the full firmware package (payload.bin or OZIP) and flash it via TWRP/OrangeFox, then reinstall Magisk.
    • โš ๏ธ Risks: the update can block the bootloader or reset the settings. Always make a backup via recovery before updating!

    On devices Samsung OTA updates with root often lead to bootloop. In this case, you will have to flash the full firmware via Odion.