Getting root access on Android opens access to the hidden capabilities of the system: from removing built-in applications to fine-tuning performance. However, this process is fraught with risks - from loss of warranty to “brick” of the device (complete failure). In this article, we will look at all the current methods for obtaining root access, their pros and cons, as well as alternative solutions for those who are not ready to sacrifice stability.

It is important to understand: methods for obtaining root access depend on the smartphone model, version Android and even the firmware region. For example, devices Samsung s Knox require a special approach, and on Xiaomi often it is enough to unlock the bootloader through an official tool. We will consider universal steps, but some models (for example, Google Pixel or OnePlus) may have unique nuances that should be clarified on specialized forums.

What are root access and why you need them

root access (or rights superuser) is complete control over the operating system Android, similar to administrator rights in Windows or Linux. With them you can:

  • 🔧 Remove pre-installed system applications (bloatware) that cannot be uninstalled using standard methods.
  • ⚡ Optimize performance: overclock the processor, change kernel parameters or disable unnecessary ones services.
  • 📱 Install modified firmware (custom ROMs) with advanced functions.
  • 🔒 Bypass manufacturer restrictions, for example, blocking downloading files to an external memory card.
  • 🛠️ Use specialized utilities like Titanium Backup for backup or Greenify for "freezing" applications.

However, with opportunities come also risks:

  • ⚠️ Loss of warranty: most manufacturers will void the warranty if root access is detected.
  • 🛡️ Security vulnerabilities: malware with superuser rights can cause irreparable harm to the system.
  • 💥 "Brick" devices: incorrect actions can lead to damage to the smartphone, requiring flashing through Fastboot or ODIN.
  • 📵 Problems with OTA updates: many devices stop receiving over-the-air updates after rooting.
⚠️ Attention: On some devices (for example, Samsung Galaxy c Knox) obtaining root access activates a flag KNOX 0x1that cannot be reset. This may block access to the secure folder Samsung Pay and other services.

Preparing the device: what you need to do before rooting

Before you begin to obtain root access, you need to complete several critical steps. Neglecting them can lead to data loss or the inability to restore the functionality of the smartphone.

First, create a full backup all data. root access can damage system files, and resetting to factory settings after an unsuccessful attempt will delete all information. Use:

  • 📲 Google Account to synchronize contacts, photos and documents.
  • 💾 Local backup via adb backup or applications like Swift Backup (requires root for full backup).
  • 🖥️ Copying files to a PC via MTP or cloud services.

Secondly, unlock the bootloader (bootloader). This is a required step for most rooting methods. The process is different on different devices:

Manufacturer Unlock method Features
Google Pixel, OnePlus Command fastboot flashing unlock Requires enabled OEM Unlock in the developer settings.
Xiaomi, Redmi, POCO Official tool Mi Unlock Tool You need to link your account Mi and wait 7-15 days for unlocking.
Samsung Mode Download Mode + Odin Activates KNOX, may block some functions.
Huawei, Honor Unlock code through the official website Since 2018, Huawei has stopped providing codes for new models.

Thirdly, make sure the battery is at least 70% charged. Interruption of the process due to discharge can lead to serious failures. Also check what you have:

ADB and Fastboot drivers are installed on your PC|

Developer mode is enabled (7 taps on the build number in "About phone")|

The "USB Debugging" and "OEM Unlock" options are enabled in the developer settings|

The official firmware image for your model has been downloaded (in case of recovery)|

A USB cable has been prepared (preferably original)-->

⚠️ Attention: On some devices (for example, Sony Xperia) unlocking the bootloader erases the keys DRM, which leads to loss of camera quality and lack of support 4K HDR in video.

Ways to obtain root access: from simple to complex

There are several methods for obtaining root access, differing in complexity and compatibility. The choice depends on your model, version Android and willingness to take risks. Let's look at them from the simplest to the most complex.

1. One-click rooting applications (KingRoot, iRoot, etc.)

These utilities promise to get root access without unlocking the bootloader and using the PC. However, they have serious disadvantages:

  • ✅ They work on older versions Android (up to 7.0).
  • ❌ They often install malware or advertising.
  • ⚠️ They do not provide full root, but only temporary access.
  • 🔄 After a reboot, rights may disappear.

Usage example KingRoot:

  1. Download APK from the official website (not from Google Play).
  2. Enable installation from unknown sources in the security settings.
  3. Launch the application and click Try to Root.
  4. Wait for the process to complete (may take 5-10 minutes).

If the device is supported, you will see a success message. However this method is not possible. recommended due to the high risk of installing malware.

2. Magisk - a modern and safe way

Magisk is the most popular tool for obtaining root access on modern devices. It works through modification of the boot image (boot.img) and supports:

  • 📱 Android 5.0 and newer (including Android 14).
  • 🔄 Ability to hide root from applications (for example, for banking services).
  • 🔧 Support for modules to expand functionality.

The installation process Magisk includes several stages:

  1. Download the latest version Magisk from the official repository to GitHub (file Magisk-vXX.X.zip).
  2. Extract boot.img from the firmware of your device. For this you can use Payload Dumper (for Pixel) or Firmware Extractor.
  3. Send boot.img to a smartphone and edit it via Magisk Manager (option Patch Boot Image).
  4. Flash the modified boot.img via fastboot: 
    fastboot flash boot magisk_patched.img

    fastboot reboot

After the reboot you will have Magisk Manager with the ability to manage root access and modules. To check the success, install the application Root Checker.

💡

If after the firmware Magisk the device is stuck in a boot loop, try disabling forced encryption in the kernel settings or flash it disable_forceencrypt.zip via TWRP.

3. Installing custom recovery (TWRP) + SuperSU

This method is suitable for older devices or those where Magisk does not work. TWRP (Team Win Recovery Project) is an alternative recovery that allows you to flash ZIP files with modifications.

Steps:

  1. Download the official image TWRP for your model with site twrp.me.
  2. Sew it through fastboot: 
    fastboot flash recovery twrp-3.7.0_9-0-yourdevice.img

    fastboot reboot recovery

  3. B TWRP select Install and flash SuperSU.zip or Magisk.zip.
  4. Reboot into the system.

The advantage of this method is the ability to create full system backups (Nandroid backup) and restore them in case of failures.

⚠️ Attention: On devices with Android 10+ and dynamic partitions (dynamic_partitions), the standard TWRP may not work. In this case, you need a patched image or an alternative recovery like OrangeFox.

root access without unlocking the bootloader: myth or reality?

Many users are looking for ways to get root access without unlocking the bootloaderin order to maintain a guarantee or avoid risks. Unfortunately, this is not possible on most modern devices for the following reasons:

  • 🔒 Protection dm-verity: Android checks the integrity of the system partition at every boot. Any changes without unlocking the bootloader will result in an error.
  • 🛡️ SAR (System-as-Root): Starting from Android 9, the system partition is mounted as the root partition, which complicates the modification.
  • 📱 Manufacturers block exploits: Vulnerabilities that made it possible to bypass protection (for example, DirtyCOW), have been closed for a long time.

However, there are partial solutions:

  • 🔧 ADB commands with temporary root: On some devices (for example, Sony Xperia with an unlocked bootloader) you can get temporary root through: 
    adb shell

    su

    But the rights will disappear after a reboot.

  • 📦 Modules Magisk without root: Some functions (for example, change build.prop) work without full rights superuser.

If your goal is to simply remove system applications or change settings, consider alternatives:

  • 🔄 ADB AppControl: Allows you to disable built-in applications without root.
  • 📱 Island or Shelter: Create isolated profiles for working with sensitive data.
  • 🔧 Shizuku + App Ops: Manage application permissions via ADB.

Magisk|TWRP + SuperSU|One-click applications (KingRoot, etc.)|Not rooted and not planning to|Other method-->

How to hide root access from applications (MagiskHide and alternatives)

One of the main problems after obtaining root access is inoperability of banking applications, games and services (for example, Google Pay, Netflix, Pokémon GO). They check for the presence of root through SafetyNet or their own mechanisms.

Magisk offers a built-in solution - MagiskHide, but with the release Android 12+ and tightening SafetyNet its effectiveness has decreased. Here are the current workarounds:

1. MagiskHide (built into Magisk)

Steps:

  1. Open Magisk Manager and go to Settings.
  2. Enable the option MagiskHide.
  3. In the section MagiskHide mark applications that need to hide root (for example, SberBank or Google Play Services).
  4. Reboot the device.

To check functionality, use:

  • SafetyNet Test (application or command adb shell su -c "snet check").
  • YASNAC (Yet Another SafetyNet Attestation Checker).

2. Modules for bypassing SafetyNet

If MagiskHide does not work, install additional modules via Magisk:

  • 🔒 Universal SafetyNet Fix (universal-safetynet-fix.zip) - corrects certification errors.
  • 📱 MagiskHide Props Config - allows you to replace device fingerprints (fingerprint) to deceive services.
  • 🔧 Riru - Core + Riru - HideLibs — hides root from specific libraries.

Installation:

  1. Download the module (file .zip) from GitHub or via Magisk Manager.
  2. In Magisk Manager select Modules → Install from storage.
  3. Reboot the device.

3. solutions

If all else fails:

  • 📱 Use the second user space (Work Profile) through Island or Shelter.
  • 🔄 Roll back to an older version of the applicationwhere check SafetyNet less strict.
  • 📦 Install a modified version of the application (for example, Google Pay with a patch for working on rooted devices).
Why does SafetyNet block rooted devices?

SafetyNet is a mechanism for checking the integrity of the device from Google. It is used by banks and other services to ensure that the system has not been modified. If root access, an unlocked bootloader or uncertified firmware are detected, SafetyNet returns the status ctsProfile: false, which leads to application blocking. You can read more about the operation of the mechanism in the documentation Google Play Protect.

Frequent problems after rooting and their solutions

Even if the process was successful, you may encounter problems. Let's look at typical scenarios and ways to eliminate them.

1. The device does not turn on (soft brick)

Symptoms: the smartphone vibrates when the power button is pressed, but the screen remains black or frozen on the logo.

Solutions:

  • 🔄 Hard reboot: press Power + Volume Down to 10-15 seconds.
  • 📱 Firmware via Fastboot: 
    fastboot flash boot stock_boot.img

    fastboot reboot

  • 🔧 Recovery via TWRP: flash backup or official firmware.

2. Constant reboots (bootloop)

Causes: incompatible module Magisk, damaged boot.img or modification conflict.

Solutions:

  • 🛠️ Remove the problematic module via TWRP (go to /data/adb/modules and delete the module folder).
  • 🔄 Flash the original boot.img:
  • 📦 Roll back to stock firmware via Odin (for Samsung) or Fastboot.

3. The mobile network or Wi-Fi does not work

A common problem after flashing a custom recovery or a modified kernel.

Solutions:

  • 📶 Check IMEI (dial *#06#). If it is Null or Unknown, restore it via QCNfile.
  • 🔧 Reflash the modules modem and vendor from stock firmware.
  • 📱 Reset the network settings in Settings → System → Reset → Reset network settings.

4. Applications do not see root access

If Root Checker shows that there are no rights, although Magisk is installed:

  • 🔄 Restart the device.
  • 📦 Check if it is enabled whether Magisk in the settings (Settings → Magisk → Enable Magisk).
  • 🔧 Reinstall Magisk via TWRP or fastboot.
⚠️ Attention: On devices with Android 13+ and kernels supporting dm-verity in enforcingmode, you may need to disable the integrity check via the command adb shell su -c "setenforce 0" (temporary solution).

How to remove root access and return the warranty

If you decide to return the device to the store or sell it, you must completely remove traces of rootingSimple removal Magisk is not enough - you need to roll back all changes.

1. Removing Magisk

The easiest way:

  1. Open Magisk Manager.
  2. Go to Settings → Complete removal.
  3. Confirm the action and reboot the device.

If Magisk Manager does not start:

  • Download Magisk-uninstaller.zip from GitHub.
  • Flash it via TWRP or fastboot.

2. Restoring stock firmware

For a complete reset:

  1. Download the official firmware for your model (for example, from websites XDA Developers or SamMobile for Samsung).
  2. Flash it through:
    • Fastboot (for Google Pixel, OnePlus): fastboot flash all stock_image.zip
    • Odin (for Samsung).
    • SP Flash Tool (for Mediatek).
  • Reset to factory settings (Wipe Data/Factory Reset in TWRP or through stock recovery).

    • 3. Resetting the Knox flag (only for Samsung)

    On devices Samsung flag KNOX (0x1) is reset only through the official service center. However, you can try:

    • 🔧 Flash the stock firmware via Odin with a checkmark Re-Partition.
    • 📱 Use utilities like Triangle Away (does not work for everyone) models).

    Please note: flag KNOX cannot be reset programmatically on new devices (starting from Samsung Galaxy S7).

    4. Checking for traces of rooting

    Before returning the device, check:

    • 🔍 Run Root Checker —should show no rights.
    • 📱 Check the status SafetyNet via Magisk Manager or adb shell su (should return Permission denied).
    • 🔧 Make sure that the bootloader is locked (fastboot oem lock for some devices).
    💡

    Even after removing root access, some services (for example, Samsung Pay or Google Pay) may retain information about modifications. The only reliable way to return full functionality. firmware of official software through the service center.

    FAQ: answers to frequently asked questions

    ❓ Is it possible to get root access on Android 14?

    Yes, but the process is more complicated than on older versions of Na Android 14 required:

    1. Unlocking the bootloader (on some devices this blocks data encryption).
    2. Using the latest version Magisk (26.0+) with support for new integrity checking mechanisms.
    3. Manual fix boot.img or init_boot.img (on some devices).

    The list of supported devices can be found at XDA Developers or in the repository Magisk at GitHub.

    ❓ How to update a rooted device?

    Over-the-air update (OTA) on rooted devices is usually impossible due to modified system files. Alternatives:

    • 📱 Manual flashing via TWRP: Download the full OTA package, remove from it boot.img, flash the rest through recovery, then update Magisk.
    • 🔧 Use Magisk Delta: fork Magisk with support OTA updates.
    • 📦 Full rollback to stock firmware, update, then re-rooting.

    Important: before updating make a backup via TWRP or adb backup.

    ❓ Do Google Pay and banking applications work after rooting?

    Most banking applications block work on rooted devices due to Google Pay block work on rooted devices due to SafetyNet. Solutions:

    • 🔒 Use MagiskHide + module Universal SafetyNet Fix.
    • 📱 Install a modified version Google Pay (for example, GPay SQL).
    • 🔧 Create an isolated profile via Island or Shelter.

    On Android 12+ the effectiveness of these methods is reduced due to stricter checks.

    ❓ Is it possible to root a device without a computer?

    Yes, but with reservations:

    • 📱 On some devices (for example, Xiaomi), you can unlock the bootloader and flash Magisk via TWRP, using only a smartphone.
    • 🔧 Applications like KingRoot or iRoot promise rooting without a PC, but they are unreliable and often contain malicious code.