Rooting (getting root access) on Android allows access to the hidden capabilities of the system, but requires caution. With its help, you can remove built-in applications, overclock the processor, install custom firmware, and even restore deleted files. However, incorrect actions can turn a smartphone into a “brick” or void the warranty.

In this article you will find current rooting methods for modern devices (including models with Android 13/14), you will understand the differences between Magisk and SuperSU, and also learn how to get around common mistakes. We will not convince you that you need to root - instead, we will honestly tell you the pros and cons so that you can make an informed decision.

We warn you right away: the procedure is different for each manufacturer (Samsung, Xiaomi, Google Pixel etc.), so it is important to follow the instructions adapted to your model. If you are a beginner, start with the “Preparation” section - there are critical conditions without which rooting will result in problems.

📊 Why do you need root on Android?
Removing built-in software
Installing custom firmware
Overclocking the processor/GPU
Recovering deleted data
Other

What are root access and why you need them

root access (from English root — “root”) give the user full control over the Android operating system, similar to rights administrator on Windows. With their help you can:

  • 📱 Remove system applications (for example, unnecessary services Google or bloatware from the manufacturer).
  • ⚡ Overclock processor/GPU to improve performance in games (through kernels like FrancoKernel).
  • 🔧 Install modified firmware (for example, LineageOS or Pixel Experience).
  • 🗃️ Recover deleted files using tools like DiskDigger.
  • 🔒 Block advertising at the system level (via AdAway or Blokada).

However, with opportunities come also risks:

  • ⚠️ Loss of warranty - most manufacturers will void the warranty if detected root.
  • 🛡️ Security vulnerabilities —malware with root access can cause more harm.
  • 💥 "Brick" devices —wrong actions can make the smartphone inoperable.
  • 🚫 Problems with banking applications —many apps (for example, SberBank Online or Google Pay) refuse to work on rooted devices.
⚠️ Attention: On some devices (for example, Samsung c Knox), rooting activates a flag KNOX 0x1that cannot be reset. This permanently makes it impossible to use Samsung Pay, Secure Folder and other functions tied to Knox.

Preparing the device for rooting

Before starting the procedure, you must complete several critical steps. Skipping any of them can lead to data loss or inoperability of the smartphone.

☑️ Checklist before rooting

Done: 0 / 5

1. Backup

Rooting can erase all data on the device. Use:

  • 📲 Local copy - through adb backup or applications like Swift Backup (requires root, but you can make a copy before rooting on another device).
  • ☁️ Cloud storage —sync contacts, photos and documents with Google Drive or Dropbox.
  • 💾 Copy of the EFS partition (for Samsung) - contains IMEI and serial numbers. Use EFS Professional or QPST.

2. Unlocking the bootloader (Bootloader)

On most devices, the bootloader is locked by default. To unlock it:

  1. Activate Developer mode: go to Settings → About phone → Build number and tap on it 7 times.
  2. Enable USB debugging i OEM unlocking in the developer menu.
  3. Connect the device to the PC and run the command: 
    fastboot flashing unlock

    On some devices (Xiaomi, Huawei) you need to get an unlock code on the manufacturer's website.

⚠️ Attention: Unlocking the bootloader on Samsung c One UI 5.0+ can lead to data reset even without rooting. Make sure that a backup is created before this step.

3. Installing the necessary tools

You will need:

  • 🖥️ PC with Windows/Linux (for ADB/Fastboot).
  • 🔌 USB cable (preferably original).
  • 📦 Android SDK platform package (or Minimal ADB and Fastboot).
  • 📱 Firmware file for your model (for example, factory image for Google Pixel or ODIN-firmware for Samsung).
  • 🔧 Magisk (latest version with GitHub).
💡

If you are using MacOSinstall homebrew and run the command brew install android-platform-tools to install ADB/Fastboot.

Rooting methods: which one to choose

The method of obtaining root depends on the device model, Android version and bootloader type. Below are the current methods for 2026.

Method Suitable devices Complexity Pros Cons
Magisk (patch boot.img) Most devices (except Samsung Exynos and some MediaTek) Average Hide root from applications, supports modules Requires an unlocked bootloader
OneClick tools (KingRoot, iRoot) Old devices (Android 5-8) Low No PC required, simple process High risk of malware, unstable operation
Custom recovery (TWRP) Supported devices TWRP High Full control over the firmware, backups Difficult to install on new models
Exploit methods (DirtyCOW, CVE-2023-XXXX) Devices with kernel vulnerabilities Very high Works without unlocking the bootloader Unstable, can break the system

The recommended method for most users is MagiskIt supports hiding root from applications. (via MagiskHide) and allows you to install modules to expand functionality. Below we will discuss this method in detail.

⚠️ Attention: On devices with Android 12+ i Dynamic Partition (for example Google Pixel 6/7) an additional step is required - extraction boot.img from the full firmware using payload-dumper-go.

Step-by-step guide: rooting via Magisk

This method is suitable for most modern devices. The example was performed on Google Pixel 7 c Android 14, but the steps are similar for other models (adjusted for firmware).

Step 1: Download the firmware and extract boot.img

  1. Download full firmware for your model from the manufacturer's official website (for example, Google Factory Images for Pixel or SamFW for Samsung).
  2. Unpack the archive. If the firmware is in format .zip c payload.bin, extract boot.img using: 
    python3 payload-dumper-go payload.bin
  3. Copy boot.img to a smartphone (for example, to a folder Download).

Step 2: Patching boot.img via Magisk

  1. Install Magisk APK on a smartphone (do not run!).
  2. Rename Magisk-vXX.X.apk to Magisk-vXX.X.zip and copy to the device.
  3. To Magisk click Install → Select and Patch a File, select boot.img.
  4. After patching, the file magisk_patched.img will appear in the folder Download.

Step 3: Firmware patched boot.img

  1. Connect the smartphone to the PC in mode Fastboot (turn off the device, then hold Power + Volume Down).
  2. Run the command: 
    fastboot flash boot magisk_patched.img
  3. Reboot the device: 
    fastboot reboot

Step 4: Check root access

After reboot:

  1. Open Magisk —if the installation was successful, you will see the status Installed.
  2. Install Root Checker from Google Play and run the test.
  3. If root is not detected, repeat steps 2-3 or check firmware compatibility.
What to do if Magisk is not installed?

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

1. Flash the original boot.img back.

2. Use an alternative method (for example, fastboot boot magisk_patched.img instead of flash).

3. Check the compatibility of the Magisk version with your kernel.

Solving common problems

Even if you follow the instructions exactly, errors occur. Here are the most common ones and how to fix them.

1. The device is not detected in Fastboot/ADB

  • 🔌 Check the cable —use the original USB cable (cheap cables may not transmit data).
  • 🖥️ Update the drivers —download the latest ones version Google USB Driver or drivers for your model (for example, Samsung USB Driver).
  • 🔄 Try a different USB port —ports on the front panel of the PC are sometimes unstable.
  • 🐧 For Linux —add a rule udev: 
    sudo nano /etc/udev/rules.d/51-android.rules

    Add the line:

    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"

    (replace 18d1 with your manufacturer ID).

2. Error "Invalid sparse file format at header". magick"

This error occurs when you try to flash an incompatible one boot.img. Solutions:

  • 📥 Download the correct firmware — make sure that the firmware version matches your model and region.
  • 🔧 Use another tool — for Samsung try Odin instead fastboot.
  • 🔄 Convert the format - if the firmware is in .lz4, unpack it using: 
    lz4 -d boot.img.lz4 boot.img

3. Detect root applications (banking, games)

Many applications (for example, Pokémon GO or SberBank) block work on rooted devices. To get around this:

  • 🔍 Activate MagiskHide:
    1. Open Magisk → Settings → enable MagiskHide.
    2. Add the problematic application to the list hiding.
    3. Reboot the device.
  • 🔄 Use modules:
    • Install the module Universal SafetyNet Fix to pass SafetyNet.
    • For Netflix and other streaming try MagiskHide Props Config.
    • 📱 Try alternative builds of Magisk services - for example, Magisk Delta (with support for new versions of Android).
      • ⚠️ Attention: Starting with Android 13, Google tightened the check SafetyNet. Even with MagiskHide some applications can detect root. In this case, only rolling back to the stock firmware will help.

      How to remove root and return the device to its original state

      If you need to return the warranty, sell smartphone or fix errors after rooting, you should completely remove root and restore the stock firmware.

      Method 1: Through Magisk (if the system boots)

      1. Open Magisk → Uninstall → Complete Uninstall.
      2. Reboot the device.
      3. If you need to lock the bootloader, do: 
        fastboot flashing lock
        Attention: on some devices (Xiaomi, OnePlus), locking the bootloader erases all data, including internal memory!

      Method 2: Flashing stock firmware

      If Magisk is not installed or the system is not loading:

      1. Download full stock firmware for your model.
      2. For Google Pixel: 
        flash-all.bat
        (from the archive with the firmware).
      3. For Samsung:
        1. Open Odin.
        2. Add firmware files to the appropriate fields (BL, AP, CP, CSC).
        3. Click Start.
      4. For Xiaomi use Mi Flash Tool in mode clean all.

      Method 3: Through custom recovery (TWRP)

      If you have installed TWRP:

      1. Boot into TWRP (usually Power + Volume Up).
      2. Select Wipe → Format Data (erases all data!).
      3. Flash the stock firmware via Install.
      💡

      After removing root, be sure to check the status SafetyNet in the application Magisk or via command adb shell su --check. If the test fails, some functions (for example, Google Pay) may not work.

      Alternatives to root: what you can do without rooting

      If you are worried about the risks of rooting, consider alternative ways to achieve similar goals. without loss of warranty.

      Purpose Solution without root Limitations
      Removing built-in applications Disable via Settings → Applications or ADB: 
      adb shell pm uninstall -k --user 0 com.package.name
      		 Applications remain in the system, taking up space
      Ad blocking Applications like Blokada (without root) or DNS66 Does not block ads in some games
      Backup Swift Backup (with Shizuku) or Titanium Backup (via ADB) Not all data is saved (for example, SMS)
      Changing system fonts/icons Themes in Substratum or Lawnchair Launcher Limited selection of modifications

      ADB commands for advanced users

      With ADB you can perform many actions that usually require root:

      • 📵 Disable system applications: 
        adb shell pm disable-user --user 0 com.android.bloatware
      • 📡 Change network settings: 
        adb shell settings put global captive_portal_detection_enabled 0
      • 🔋 Limit background activity: 
        adb shell cmd appops set com.package.name RUN_ANY_IN_BACKGROUND ignore

      To work with ADB you do not need root, but you need activated USB debugging.

      FAQ: Frequently asked questions about rooting Android

      Is it possible to get root without unlocking the bootloader?

      On most modern devices (Android 10+) there were exploits before (for example, DirtyCOW), but they are closed in new versions. Exceptions:

      • Some devices on MediaTek (for example, Redmi Note 8 Pro) can be rooted via MTK-su.
      • Devices with vulnerabilities in the kernel (but this is unstable and dangerous).

      For other models, unlocking the bootloader is required.

      Will Google Pay work after rooting?

      Officially - no, since Google Pay checks the integrity of the system through SafetyNet. However, there are workarounds:

      1. Install the module Universal SafetyNet Fix in Magisk.
      2. Activate MagiskHide and add Google Pay to the hide list.
      3. Use alternative payment systems (for example, Samsung Pay works on some devices even with root).

      If nothing else helps, you will have to choose: either root or Google Pay.

      How to update Android after rooting?

      OTA updates (over the air) on rooted devices usually do not work. Options:

      • 📥 Manual firmware: Download the full update image and flash it via fastboot or TWRP, then reinstall Magisk.
      • 🔄 Temporary root removal:
        1. B Magisk select Uninstall → Restore Images.
        2. Install the update.
        3. Reflash magisk_patched.img.
    • 🚫 Refusing updates: If you are happy with the current version of Android, you can disable checking for updates via ADB: 
      adb shell pm disable-user --user 0 com.google.android.gsf.update
      • Is it possible to root a smartphone with an Exynos processor (Samsung)?

      Yes, but the process is more complicated than on devices with Snapdragon. Features:

      • 🔧 Use Odin instead of fastboot.
      • 📦 The firmware must be in the format .tar.md5.
      • 🚨 On devices with Knox rooting works trigger KNOX 0x1, which makes it impossible to use Samsung Pay i Secure Folder.
      • 🔄 For Android 12+ on Exynos you need to patch init_boot.img instead boot.img.

        • We recommend following the instructions on the forums XDA Developers for your model.

      How to check if my device supports rooting?

      Check the following parameters:

      1. Availability of bootloader unlocking: If there is no option in the developer menu OEM Unlock, rooting is not possible without exploits.
      2. Support TWRP: Check if there is a custom recovery for your model at TWRP official website.
      3. Magisk compatibility: Make sure your version of Android is supported (for example, Magisk 26.0+ works with Android 14).
      4. XDA Forum: Search for a topic based on your model (for example, root [model]). If there is no theme or it has not been updated for more than a year, the chances of successful rooting are low.

      For a quick check, you can use the application Root Checker (it will show whether there is already root and provide information about the bootloader).