Receiving root access on Android opens access to hidden system functions, allows you to remove built-in applications, overclock the processor or install custom firmware. However, this process is fraught with risks: from loss of warranty to complete โ€œbrickingโ€ of the device. In this article, we will look at how to properly flash the root, what tools to use for different versions Android (including Android 14), and how to minimize possible problems.

It is important to understand that the methods for obtaining root access differ depending on the smartphone model, firmware version and even the region of sale. For example, devices Samsung require the use of Odin, and for Xiaomi you will need to unlock the bootloader via Mi Unlock Tool. We will look at universal steps, but some nuances will have to be clarified for your specific model.

What are root access and why you need them?

root access (or superuser rights) are complete control over the operating system Android. With them you can:

  • ๐Ÿ”ง Uninstall pre-installed applications (bloatware) that cannot be uninstalled using standard methods.
  • โšก Overclock the processor or change GPU frequencies to improve performance (but this reduces battery life).
  • ๐Ÿ“ฑ Install custom firmware (LineageOS, Pixel Experience) with advanced functions.
  • ๐Ÿ”’ Block advertising at the system level using AdAway or Blokada.
  • ๐Ÿ“ Gain access to hidden system files and folders, for example, /data or /system.

However, along with opportunities come risks:

  • โš ๏ธ Loss of warranty - most manufacturers (including Samsung, Google, OnePlus) will void the warranty if root access is detected.
  • ๐Ÿ›ก๏ธ Vulnerability to malware - some viruses use root access to steal data.
  • ๐Ÿ’ฅ Possibility of "bricking" the device - incorrect actions can make the smartphone inoperable.
  • ๐Ÿ”„ Problems with OTA updates - after receiving root access, automatic system updates may stop work.
โš ๏ธ Attention: On some devices (for example, Huawei or Oppo), unlocking the bootloader leads to resetting IMEI or blocking network modules. Before you begin, check the forums XDA Developers or 4PDA for specific problems with your model.

Preparing the device before flashing root access

Before you begin to obtain root access, you need to complete several critical steps. Skipping any of them may result in data loss or device inoperability.

First, create a full backup all data. Use for this:

  • ๐Ÿ“ฒ Google Account (contacts, photos, applications).
  • ๐Ÿ’พ Local backup via adb backup or applications like Titanium Backup (requires root access, but can be used on another device).
  • ๐Ÿ–ฅ๏ธ Copying files to PC via MTP or ADB.

Secondly, check bootloader and firmware version:

  1. Go to Settings โ†’ About phone โ†’ Build number and click on it 7 times to activate Developer mode.
  2. Return to Settings โ†’ System โ†’ For Developers and enable USB Debugging i OEM Unlock.
  3. Connect the device to the PC and run command:
    adb devices

    to make sure that the computer recognizes the smartphone.

Also charge the battery at least to 70% - this will prevent sudden shutdown during the process. Keep in mind that on some devices (for example Samsung Galaxy S23), unlocking the bootloader resets all data, even if you made a backup.

Back up your data|Charge the battery to 70%+|Enable USB debugging|Unlock OEM in developer options|Install ADB/Fastboot drivers on PC|Download the correct version of Magisk or SuperSU-->

Selecting a method for obtaining root access: Magisk vs SuperSU

Today, there are two main ways to obtain root access: through Magisk or SuperSU. Despite the fact that SuperSU was popular several years ago, now not all devices support it. Magisk has become a de facto standard thanks to its support Magisk Modules and the ability to hide root access from applications (for example, banking or games).

Criterion Magisk SuperSU
Support for new versions of Android Yes (including Android 14) Limited (up to Android 10)
Hide root access (MagiskHide) Yes No
Modules for expanding functions Yes (Magisk Modules) No
Compatible with OTA updates Yes (if correct setup) No
Installation via custom recovery Yes (TWRP, OrangeFox) Yes

For most modern devices it is recommended to use Magisk, since it supports AVB 2.0 (Android Verified Boot), which is critical for smartphones on Android 11+. In addition, Magisk allows you to pass SafetyNet, which is important for work Google Pay, Netflix and banking applications.

If you still decide to use SuperSU, please note that:

  • ๐Ÿšซ It has not been updated since 2018 and may contain vulnerabilities.
  • ๐Ÿ”„ On new devices, its installation often leads to a loading loop (bootloop).
  • ๐Ÿ“ฑ Some custom firmware (for example, LineageOS 20+) does not work at all support SuperSU.
๐Ÿ“Š Which root method do you prefer?
Magisk
SuperSU
Other (specify in the comments)
Haven't tried it yet

Bootloader Unlock

Before installing root access on most devices, you need to unlock the bootloader. This process deletes all data from the device and may void the warranty. The procedure differs depending on the manufacturer:

  • ๐Ÿ“ฑ Google Pixel: use the command fastboot flashing unlock.
  • ๐Ÿ“ฑ Xiaomi: requires official permission via Mi Unlock Tool (may take up to 720 hours of waiting).
  • ๐Ÿ“ฑ Samsung: unlocking via Odin with mode enabled OEM Unlock in settings.
  • ๐Ÿ“ฑ OnePlus: command fastboot oem unlock, but on new models an additional key is required.

General instructions for unlocking via fastboot:

  1. Turn off the device and hold down the button combination to enter Fastboot Mode (usually Power + Volume Down).
  2. Connect your smartphone to the PC and run the command:
    fastboot devices

    to make sure the connection.

  3. Unlock the bootloader with the command:
    fastboot oem unlock

    or fastboot flashing unlock for Pixel.

  4. Confirm unlocking on the device screen (volume and power buttons).

On devices with a processor MediaTek (for example, Redmi Note 12), unlocking the bootloader can lead to blocking IMEIIn this case, additional recovery via SP Flash Tool or MTK Auth Bypass.

โš ๏ธ Attention: On some devices Samsung (series Galaxy S22/S23), unlocking the bootloader leads to activation Knox, which permanently blocks access to Samsung Pay i Secure Folder, even after rolling back changes.

Installing custom recovery (TWRP or OrangeFox)

For firmware Magisk or SuperSU required on most devices custom recovery, such as TWRP or OrangeFox. It replaces the standard recovery and allows you to install unofficial firmware and modifications.

Installation instructions TWRP:

  1. Download the official version TWRP for your model from the website twrp.me (for example, twrp-3.7.0_9-0-redfin.img for Google Pixel 5).
  2. Reboot the device in Fastboot Mode and connect to the PC.
  3. Flash recovery with the command:
    fastboot flash recovery twrp.img

    For devices with a partition recovery_ramdisk (for example, OnePlus 9) use:

    fastboot flash boot twrp.img
  4. Immediately after the firmware, reboot into recovery, holding Power + Volume Up, otherwise the standard firmware may overwrite TWRP.

Important nuances:

  • ๐Ÿ”ง On devices with Dynamic Partition (for example, Xiaomi Mi 11) is required patched image boot.img instead of the standard one TWRP.
  • ๐Ÿ“ฑ Some smartphones (Realme, Oppo) block the installation of custom recovery without additional manipulations VBMeta.
  • ๐Ÿ”„ After installation TWRP you may need to disable the check signatures in the recovery settings (Install โ†’ Settings โ†’ Disable DM-Verity).
What to do if TWRP is not installed?

If when you try to flash TWRP you get an error FAILED (remote: 'Not allowed in Lock State'), this means that the bootloader is not unlocked. Return to the previous step and repeat the unlocking. If error Invalid sparse file format at header โ€”download another version TWRP or use fastboot boot twrp.img for temporary download.

Magisk firmware and obtaining root access

After installing custom recovery, you can start flashing the firmware Magisk. This process consists of two stages: patching boot.img (for devices with Android 10+) or installing a ZIP archive via recovery.

Method 1: Installation via TWRP (for older devices)

  1. Download latest Magisk-v26.4.zip from the official repository GitHub.
  2. Move the archive to your device or SD card.
  3. Reboot into TWRP and select Install โ†’ Select Magisk.zip โ†’ Swipe to Confirm Flash.
  4. After installation, reboot the device. It may take 5-10 minutes when you first start.

Method 2: Patching boot.img (for new devices)

  1. Download the original boot.img for your firmware (can be extracted from the factory firmware or downloaded from XDA).
  2. Install Magisk Manager on the device and select Install โ†’ Select and Patch a File.
  3. Select downloaded boot.img โ€” Magisk will create a patched file magisk_patched.img.
  4. Flash patched boot via fastboot:
    fastboot flash boot magisk_patched.img

After successful firmware, check for root access using the application Root Checker or command in ADB:

adb shell su

If the command returns # instead $, root access is installed correctly.

๐Ÿ’ก

If after flashing Magisk the device gets stuck on the logo, try flashing the original boot.img back, and then repeat the process with the module disabled DM-Verity settings Magisk.

Solving common problems after obtaining root access

Even with the correct installation of root access, problems may arise. Let's consider the most common of them and ways to solve them:

Problem Possible cause Solution
The device does not turn on (bootloop) Incompatible version Magisk or damaged boot.img Flash original boot.img via fastboot
Does not work Google Pay or banking applications SafetyNet failed Enable MagiskHide and install the module Universal SafetyNet Fix
No network after unlocking the bootloader Reset IMEI or Baseband Restore IMEI via Maui Meta or flash the original modem.img
OTA updates are not installed Changed system partition Remove root access before updating or flash manually via TWRP
Applications crash with an error SELinux Incorrect status SELinux (Permissive instead Enforcing) Install the module MagiskSELinuxSwitcher or flash the kernel with the correct policies

If, after receiving root access, they stopped working Widevine L1 (no Full HD v Netflix), try:

  1. Remove all modules Magiskassociated with DRM.
  2. Flash original vendor.img or dtbo.img.
  3. Install module Widevine L1 for Magisk (does not work on all devices).
โš ๏ธ Attention: On devices Samsung with a processor Exynos (for example, Galaxy S22), installing root access may lead to blocking the camera in some applications (for example, Snapchat or TikTok).This is due to a trigger Knoxthat cannot be reset.

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

If you need to return the device to stock condition (for example, for sale or repair under warranty), you must completely remove root access and restore the original firmware. The process depends on what changes were made:

Method 1: Removal via Magisk (if recovery has not been changed)

  1. Open Magisk Manager and select Uninstall โ†’ Complete Uninstall.
  2. Reboot the device. root access remain, flash the original boot.img:
  3. fastboot flash boot stock_boot.img

Method 2: Full rollback to stock firmware

  • ๐Ÿ“ฑ For Samsung: flash the official firmware via Odin with checkmarks BL, AP, CP, CSC (use HOME_CSCto not reset data).
  • ๐Ÿ“ฑ For Xiaomi: use Mi Flash Tool with option clean all and lock.
  • ๐Ÿ“ฑ For Google Pixel: flash the factory image via fastboot with the flag --force.

After restoring the stock firmware:

  1. Reset to factory settings (Settings โ†’ System โ†’ Reset).
  2. Check the status SafetyNet via the app SafetyNet Test.
  3. If the bootloader has been unlocked, lock it back with the command:
    fastboot oem lock
    On some devices (for example, OnePlus 8T) re-locking the bootloader may lead to data loss or error Invalid partition. Before blocking, make sure that the firmware is completely stock.
๐Ÿ’ก

To ensure you return the device to its original state, use the manufacturerโ€™s official tools (Odin for Samsung, Mi Flash for Xiaomi). Firmware via custom recovery may leave traces of modifications.

FAQ: Frequently asked questions about root access. Android

Is it possible to get root access without unlocking the bootloader?

On most modern devices, no. Exceptions include some models with vulnerabilities (for example, DirtyCOW on older versions Android), but such methods are unreliable and often lead to unstable operation of the system. For a reliable root, unlocking the bootloader is required.

Will Google Pay work after receiving root access?

Yes, if you configure it correctly MagiskHide and install the module Universal SafetyNet FixHowever, some banking applications. (for example, SberBank Online or Tinkoff) can block work even with a hidden root. In this case, the module MagiskHide Props Config for replacing device fingerprints will help.

Is it possible to update Android via OTA with root access?

Technically yes, but this is fraught with problems. Usually, after an OTA update, root access disappear, and the device may freeze. It is recommended:

  1. Delete. root access via Magisk.
  2. Install the update.
  3. Repeat the process of obtaining root access for the new firmware.

For devices with Dynamic Partition (for example, Pixel 6) a manual update may be required via fastboot.

How to check if the bootloader is unlocked?

Turn off the device and hold down the combination to enter Fastboot Mode. If at the bottom of the screen you see the message Unlocked or Device State: Unlocked โ€”the bootloader is also unlocked. you can check this with the command:

fastboot getvar unlocked

If the answer is unlocked: yes โ€”the bootloader is unlocked.

What to do if the device does not boot after Magisk firmware?

Most likely, you flashed an incompatible version Magisk or damaged boot.img. Solutions:

  1. Flash the original boot.img via fastboot.
  2. If the device boots into TWRP, try flashing a different version. Magisk (for example, Magisk-canary for new devices).
  3. For devices with AVB 2.0 you may need to disable signature verification (dm-verity) through the command:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img