How to install root access on Android 10: safe methods and pitfalls

Android 10 is one of the most stable versions of the mobile OS from Google, but even it limits users in managing system files. Obtaining root access (or root access) opens up opportunities for deep customization: from removing built-in software to installing modified firmware. However, the process is fraught with risks - from loss of warranty to “bricking” the device.

In this guide we will examine Current ways to get root on Android 10 (including security patches 2026-2026), features for popular brands (Samsung, Xiaomi, Google Pixel, OnePlus), as well as legal alternatives if you don’t need root. Important: the procedure is different for devices with a locked and unlocked bootloader - we will consider both scenarios.

Before you start, check: 1) Android version (in Settings → About phone). 2) Processor model (via application CPU-Z). 3) Bootloader status (command fastboot oem device-info in ADB).

Without this information, you risk choosing the wrong method and damaging the system.

1. Preparing the device: what needs to be done BEFORE getting root

An unprepared device is the main source of problems when getting root. On Android 10 it is critical to perform a backup via ADB (not only cloud services!), since after unlocking the bootloader the data will be erased. Here is a checklist of required actions:

Create a backup via adb backup (including applications and data)

Download the original firmware for your model

Install drivers ADB and Fastboot

Charge the phone to at least 70%. In some devices (for example

Disable OEM Lock in developer settings

Check your model's compatibility with Magisk on the forum XDA Developers-->

Pay special attention to the point about OEM Unlock. On some devices (for example, Samsung Galaxy S10 or Xiaomi Redmi Note 8 Pro) this option may disappear after a reboot. Solution: activate it, connect to the Internet, reboot the phone and immediately check the status using the command:

adb shell getprop ro.oem_unlock_supported

If the answer is 1 —the bootloader can be unlocked. If 0 —you will need a workaround (about it in the about Samsungsection. Also note that some operators (for example, Verizon in the USA) block unlocking at the firmware level.

⚠️ Attention: On devices with Exynos (For example, Samsung Galaxy S20) after unlocking the bootloader, hardware protection Knoxis triggered, which makes it impossible to use Samsung Pay, Secure Folder this is irreversible!

2. Methods for obtaining root on Android 10: which one to choose?

The method of obtaining root depends on three factors: 1) Bootloader status (locked/unlocked). 2) Availability of custom recovery (TWRP). 3) Processor model (Qualcomm, Mediatek, Exynos).

Below is a comparison table of methods:

For 90% of modern devices the method with Magisk via patch is optimal boot.img. It retains the possibility of OTA updates (if properly configured) and supports SafetyNet (important for banking applications). modern devices DirtyCow work only on firmware with vulnerabilities that have long been closed in security patches 2023+.

Magisk|SuperSU|Exploit (for example, DirtyCow)|OneClick tools (KingRoot, etc.)|Never tried-->

Why Magisk is the best choice for Android 10?

Magisk (developer topjohnwu) solves the key problems of the classic root:

• 🔹 The system partition remains untouched — changes are made only to boot, which simplifies rollback.
• 🔹 SafetyNet support — you can use Google Pay, Netflix banking applications (when hiding the root via MagiskHide).
• 🔹 Modular system — installation of modifications (for example, ViPER4Android or AdAway) without editing system files.

⚠️ Attention: Starting from Magisk v26.0 (2023), the module MagiskHide was removed due to stricter checks Google. Instead, use the module Universal SafetyNet Fix + Shamiko to hide the root.

3. Step-by-step guide: root via Magisk on Android 10

This method is suitable for devices with unlocked bootloader. If your bootloader is locked, first complete section 4, then return here.

Step 1: Download the necessary files

You will need:

• 📱 Original firmware for your model (download from the manufacturer's official website or XDA).
• 🖥️ Platform Tools (includes adb and fastboot) — official link.
• 🛠️ Magisk Manager (latest version) - GitHub repository.
• 🔧 7-Zip or WinRAR to extract boot.img from the firmware.

Step 2: Extract and patch boot.img

1. Unpack the downloaded firmware (usually this is a file .zip or .tar).

2. Find the file boot.img (may be called boot.img.lz4 —then unpack it via LZ4 Tool).

3. Copy boot.img to your phone.

4. Open Magisk Manager, click Install → Select and Patch a File and select boot.img.

5. After patching, the file will be saved as magisk_patched.img in the folder Download.

Step 3: Flash patched boot.img

1 Connect the phone to the PC in fastboot (turn off the device, then press Power + Volume Down).

2. In the command line (in the folder with platform-tools) run:

fastboot flash boot magisk_patched.img

3. For devices with a partition boot_a/boot_b (for example, OnePlus 7T) use:

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

4. Reboot the phone:

fastboot reboot

Step 4: Check the root and configure Magisk

After downloading:

• 🔍 Install Root Checker from Play Market and check the status of the root.
• 🛡️ In Magisk Manager activate the modules Universal SafetyNet Fix i Shamiko (to hide the root from banking applications).
• 🔄 If the root does not work, repeat the firmware boot.img with the option disabled AVB (add --disable-verity --disable-verification to the command fastboot).

4. Unlocking the bootloader: instructions for different brands

The process of unlocking the bootloader varies depending on the manufacturer Below are the current methods for popular brands for 2026. year.

📱 Samsung (Exynos/Mediatek)

On devices Samsung with processors Exynos (for example, Galaxy S21, Note 20) unlocking is possible, but with reservations:

• 🔓 Turn on OEM Unlock in Settings → Phone information → Software information → Build number (tap 7 times to activate developer mode).
• 🔧 Use the utility Odin (version 3.14.4+) for firmware TWRP or patched boot.img.
• ⚠️ After unlocking it will work Knox (check the status via *#06# - if Knox: 0x1, the warranty has expired).

📱 Xiaomi (Mediatek/Qualcomm)

Xiaomi blocks bootloader unlocking via account linking Mi. Algorithm of actions:

1. Link the device to your account Mi to Settings → Xiaomi Account.
2. Go to Settings → Advanced → For developers → Mi Unlock status and link the device.
3. Download Mi Unlock Tool (latest version) and log in.
4. Connect your phone in mode fastboot and follow app instructions. Typically, a wait of 7–14 days is required (on new devices).

⚠️ Attention: On devices Xiaomi with a processor Mediatek (for example, Redmi 9A) after unlocking, you may need to update the firmware VBmeta with disabled check AVB:

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

Without this, the phone will freeze on the logo.

📱 Google Pixel

Google I have simplified the process as much as possible for my devices:

1. Activate OEM Unlock in the settings developer.
2. Connect your phone to the PC and do:

   fastboot flashing unlock

   Confirm unlocking on the phone screen (volume buttons).

3. Flash magisk_patched.img as described in section 3.

On Pixel 4a and newer, after unlocking, all data (including internal memory) is automatically reset.

📱 OnePlus

On OnePlus 7/8/9 series, unlocking takes 5 minutes:

fastboot oem unlock

But please note:

• 🔋 On OnePlus 9 Pro s OxygenOS 12+ you need to disable Critical Unlock in the developer settings (otherwise it will be blocked Widevine L1and Netflix will show in low resolution).
• 🔄 After unlocking, flash fastboot flash boot magisk_patched.img immediately fastboot flash dtbo dtbo.img (otherwise the camera will stop working).

5. Alternatives to root access: when they can be avoided

root access is not always necessary to solve problems. In many cases, alternative methods are sufficient:

adb shell pm uninstall -k --user 0 com.android.bloatware

If your goal is remove bloat or backup, try to do without root. For example, to disable unnecessary services Google use the command:

adb shell pm disable-user --user 0 com.google.android.apps.magazines

This safer than rooting and does not affect SafetyNet.

6. Risks and how to minimize them

Obtaining root access entails not only opportunities, but also threats. Here are the key risks and ways to avoid them:

• 💀 "Brick" devices - happens when the firmware is incorrect boot.img or the process is interrupted. Solution: always check the hash sum (MD5) of the downloaded files and. use Fastboot Enhance to control the process.
• 🛡️ Loss of SafetyNet - without root, many banking applications and games (Pokémon GO) refuse to work. Solution: modules Universal SafetyNet Fix + MagiskHide Props Config.
• 🔄 Problems with OTA updates - after rooting, system updates can break the bootloader. Solution: Before updating, remove the root via Magisk (Uninstall → Complete Uninstall).
• 🕵️ Data leak —root applications can access passwords and tokens Solution: use AFWall+ to block network access. suspicious applications.

⚠️ Attention: On devices with Dynamic Partition (entered in Android 10), incorrect resizing of partitions (for example, through TWRP) leads to data loss without the possibility of recovery. create a full backup in sections via:

adb backup -apk -obb -shared -all -f backup.ab

If after rooting the phone stops booting:

1. Try to boot into fastboot and flash the original boot.img.
2. If the screen is black - connect the phone to the PC and check the command output:

   fastboot devices

   If the device is not detected, you will need EDL mode (for Qualcomm) or SP Flash Tool (for Mediatek).

7. Common errors and their solutions

Even if you follow the instructions, errors may occur. Here are the most common ones and how to correct them:

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

If Magisk Manager does not see the root after successful firmware:

• 🔄 Reinstall Magisk Manager (download the latest version from GitHub).
• 📱 Check that in Settings → System → About phone the root status is displayed as Magisk.
• 🔧 If there is a root, but applications do not see it, activate MagiskHide (in Magisk v24+ this is called Enforce DenyList).

8. FAQ: answers to frequently asked questions