Rooting Android: a complete guide for beginners with step-by-step guide

Obtaining superuser rights (root access) on the Androiddevice opens access to hidden functions system, allows you to remove built-in applications, optimize performance and install specialized software. However, the rooting process requires care: incorrect actions can lead to lost warranty, locked bootloader or "bricked" device (turning into a “brick”). In this guide, we will look at current rooting methods suitable for most modern smartphones, including devices with Android 13/14.

It is important to understand that the procedure differs depending on the model, firmware version and bootloader type. For example, devices Samsung s Knox require a special approach, and smartphones Xiaomi often need to be unlocked via Mi Unlock Tool. We will look at universal steps, as well as nuances for popular brands. If you are a beginner, start by studying the theory and preparing a data backup.

What are root access and why you need them

root access (or superuser rights) give complete control over the operating system Android, similar to administrator rights in Windows or sudo v Linux. With their help you can:

• 🔧 Remove pre-installed system applications (bloatware), which occupy memory and consume battery power.
• ⚡ Optimize performance through the system kernel (for example, change the processor frequency from using Kernel Adiutor).
• 📱 Install custom firmware (LineageOS, Pixel Experience) to update outdated devices.
• 🔒 Block advertising at the system level using AdAway or Blokada.
• 📁 Get access to hidden memory sections, for example, for backup EFS (important for communication).

However, there is a downside: rooting voids the warranty (although it can often be restored by rolling back to stock firmware), increases the risk of malware infection (since applications receive extended rights) and can disrupt the operation of some functions. For example, banking applications. (SberBank Online, Tinkoff) and services with DRM-protection (Netflix, Disney+) often refuse to work on rooted devices.

⚠️ Attention: On devices with Samsung Knox (for example, Galaxy S23, Note 20), rooting will lead to irreversible activation of the flag Knox 0x1, which will block access to Samsung Pay, Secure Folder and some corporate functions.

Preparing the device for rooting

Before starting the procedure, you must complete several critical steps. Skipping any of them may lead to data loss or the inability to restore the system.

1. Create a backup copy all data (photos, contacts, messages) using Google Account, Titanium Backup (requires root, but can be used on another device) or via ADB pull.
2. Charge the battery at least to 70% - this will prevent a sudden shutdown during the process.
3. Unlock the bootloader (bootloader). On most devices, this requires:
   • Activate Developer options (click on Number assembly 7 times Settings → About phone).
   • Enable USB debugging and Unlock OEM in the developer menu.
   • Connect the device to the PC and run the command:

     fastboot oem unlock

For devices Xiaomi, Redmi or POCO you will additionally need to link your account Mi to the phone and wait 7-14 days (depending on company policy) before unlocking the bootloader via Mi Unlock Tool. The Samsung process is more complicated: you need to enable the OEM Unlock in Download Mode (combination Power + Vol Down + Bixby).

Battery charge ≥70%|

Data backup created|

Developer options activated|

USB debugging and OEM unlocking enabled|

ADB/Fastboot drivers installed on PC-->

Selecting rooting method: Magisk vs SuperSU

Today, there are two main tools for obtaining root access: Magisk and SuperSU. The latter is considered obsolete (development ceased in 2018), but is still used on older devices. Magisk is a modern solution with support Android 10–14, the ability to hide root from applications (MagiskHide) and a modular extension system.

For most users, Magisk is the optimal choice. It allows you to pass SafetyNet (Google security check), which is critical for the operation of banking applications. Installation is carried out through patching the boot image. (boot.img) or recovery (recovery). Popular custom recovery: TWRP (Team Win Recovery Project) and OrangeFox.

⚠️ Attention: On devices with dynamic partitions (Dynamic Partitions, entered into Android 10, the standard patching method boot.img may not work. In this case, you will need to patch init_boot.img (for Android 12+) or use specialized scripts.

Step-by-step guide: rooting via Magisk

Let's consider the universal method of rooting using Magisk i TWRP. This method is suitable for most devices, except for those where the bootloader is locked at the hardware level (for example, some models Huawei after 2019).

1. Download the necessary files:
   • 📱 Firmware for your model (stock or custom) from the manufacturer's website or XDA Developers.
   • 🔧 Magisk Manager (latest version with GitHub).
   • 🛠️ TWRP for your device (check compatibility by model and version of Android!).
   • 🖥️ Platform Tools (ADB and Fastboot) from Google.

fastboot flash boot magisk_patched.img

For devices with A/B-partitions (for example, Pixel, OnePlus) instead of boot you may need to flash both slots:

fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

Solving problems after rooting

Even with successful rooting, problems may occur. Here are the most common of them and how to fix them:

• 🔄 The device is stuck on bootloop:

  Cause: incompatible patch boot.img or error during firmware. Solution: reflash the stock one boot.img via fastboot or restore the backup to TWRP.

• 📵 The mobile network or Wi-Fi does not work:

  The partition may be damaged EFS (contains IMEI and modem settings). Restore it from a backup or use tools like EFS Professional.

• 🔒 SafetyNet does not pass the test:

  Activate MagiskHide in the settings Magisk, update Magisk to the latest version and install module Universal SafetyNet Fix.

• 💳 Banking applications do not work:

  Try to hide root using MagiskHide Props Config or use alternative versions of applications (for example, SberBank Online via Island for isolation).

If after rooting the device stops booting at all ("brick"), try the following steps:

1. Boot into Download Mode (for Samsung) or Fastboot and flash the stock firmware via Odin or Fastboot.
2. For devices with a locked bootloader (for example, Huawei), an official service center may be required.
3. If the problem is a damaged one section EFS, try to restore it via QPST or ChimeraTool (requires skills).

Install the application Root Checker from Google Play or run the command in the terminal:

su

If a superuser prompt appears (# instead of $), root is active.-->

Routing without a computer: possible risks

Some applications (for example KingRoot, Framaroot, iRoot) promise to get root access without a PC. However, such methods are highly not recommended for the following reasons:

• 🕵️‍♂️ Malicious code: many one-click routers contain spyware or adware.
• 🔧 Instability: root obtained through such applications often leads to system crashes.
• 🚫 Lack of updates: most of these tools do not support new versions of Android.

The only exception is Magisk in direct installation mode (Direct Install), but it requires an already unlocked bootloader and does not work on all devices. For reliable rooting, it is better to use the patching method boot.img via a PC.

Through Magisk and TWRP|

Through custom firmware (LineageOS, etc.)|

One-click applications (KingRoot, etc.)|

I haven’t tried it yet, but I plan to|

I don’t plan to root -->

How to hide root from applications (MagiskHide and alternatives)

Many applications (banking, games with protection Netflix) block work on rooted devices. To bypass this limitation, use the following methods:

1. MagiskHide (built into Magisk):

   Activate the option in settings Magisk and add problematic applications to the hide list. Android 10+ may require an additional module MagiskHide Props Config.

2. Island (Work Profile):

   Create an isolated profile via Island and install banking applications there. They will not see root in the main profile.

3. Shelter:

   Analog Island, but open source. Allows you to sandbox applications in a separate space.

4. Modules for Magisk:

   Install Universal SafetyNet Fix and Play Integrity Fix to pass Google checks.

For verification status SafetyNet use the application YASNAC (Yet Another SafetyNet Attestation Checker). If the test fails, update Magisk and modules, and also make sure that there are no other modifications in the system (for example, changed build.prop).

Rooting back and restoring the warranty

If you need to return the device to a service center or sell it, you need to completely remove traces of rooting. To do this:

1. Remove Magisk:

   B application Magisk Manager select Uninstall → Complete Uninstall. This will remove all modules and patches.

2. Flash the stock one boot.img:

   Download the original firmware for your model and flash the standard one boot.img via fastboot:

   fastboot flash boot stock_boot.img

3. Return stock recovery:

   If you have installed TWRP, flash the original recovery:

   fastboot flash recovery stock_recovery.img

4. Reset settings:

   Perform a full reset (Wipe Data/Factory Reset) through stock recovery or Android settings.

5. Check the Knox status (for Samsung):

   If the flag Knox triggered (checked through *#06# or KnoxGuard, it is impossible to restore the warranty - this is a hardware lock.

For devices Xiaomi you will additionally need to re-lock the bootloader via Mi Unlock Tool (the procedure may take up to 30 days on some). models Sony i LG to restore the warranty, you need to flash the official firmware through proprietary utilities (XperiFirm + Newflasher for Sony, LGUP for LG).

⚠️ Attention: On devices c AVB 2.0 (Android Verified Boot) simply removing Magisk may not work - you will need to disable bootloader signature verification through patching vbmeta.img:

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

FAQ: Frequently asked questions about rooting Android