Root on Android 10: a complete guide from unlocking the bootloader to installing Magisk

Obtaining root access to Android 10 is a task that requires not only technical skills, but also an understanding of the consequences. Unlike earlier versions, the tenth version of the operating system introduced additional protection mechanisms, such as Android Verified Boot and enhanced verification of the integrity of the system partition. This means that classic methods like flashing Google has introduced additional protection mechanisms, such as AVB 2.0 (Android Verified Boot) and enhanced verification of the integrity of the system partition. This means that classic methods like flashing SuperSU through TWRP often lead to looped loading (bootloop) or complete loss of data.

In this guide we will look at current methods of obtaining root access to Android 10, taking into account the characteristics of different manufacturers - from Google Pixel to Xiaomi i Samsung. You will learn how to correctly unlock the bootloader, bypass DM-Verity, install Magisk (the only reliable solution for modern devices) and avoid common mistakes. We will also analyze the risks: from loss of warranty to problems with Google Pay and banking applications.

Before you begin, answer yourself two key questions: Why do you need root (removing the blaster, custom firmware, backing up system data?) and Are you ready for possible consequences (factory reset, blocking OTA updates, security problems). If the answers are yes, let's get started.

1. Preparing the device: what needs to be done before unlocking

The first and most important stage is preparing the smartphone. Neglecting these steps may lead to data lossiring the device or the inability to restore functionality. Start by checking the following parameters:

• 📱 Device model and Android version: Make sure that you have the same one Android 10 (API 29) and not a newer version. To check, go to Settings → About phone → Android version. Some manufacturers (for example Samsung) modify the kernel, which requires a special approach.
• 🔓 Bootloader status: Most devices come with a locked bootloader. Unlocking erases all data, so make a backup copy in advance.
• 🔋 Battery charge: The level must be at least 70%. The unlocking and flashing process can take up to 30 minutes, and interruption due to low battery is almost always fatal.
• 💻 Having a PC: You will need a computer with Windows, macOS or Linux to work with ADB i Fastboot. Install the latest versions Platform Tools from Google.

Pay special attention data backup. Use Google Account to synchronize contacts and applications, and for media files and documents - an external drive or the cloud. When unlocking the bootloader on most devices, factory resetis performed, and some manufacturers (for example, Huawei) can block access to the internal memory after modifications.

2. Unlocking the bootloader: official and unofficial methods

Unlocking the bootloader is a mandatory step before obtaining root access. The process differs depending on the manufacturer. Below are instructions for the most common brands:

Manufacturer	Unlock method	Features
Google Pixel	Official team fastboot flashing unlock	Requires inclusion OEM Unlock in developer settings. After unlocking, DRM keys are reset (problems with Widevine L1).
Xiaomi	After Mi Unlock Tool linked to your Mi account	You must wait 72-168 hours after linking the device to your account. Some models require unlocking Anti-Rollback.
Samsung	Through Odin with patched firmware BL (bootloader)	On devices with Exynos unlocking is possible, on Snapdragon (for example, Galaxy S10 USA) - no. Trigger risk KNOX (0x1).
OnePlus	Official team fastboot oem unlock	On new models (for example, OnePlus 8T), you may need to disable OEM Lock in the service menu (*#808#).

For most devices, the unlocking algorithm looks like this:

1. Enable Developer mode 7 times: go to Settings → About phone and click on Number assembly.
2. Activate USB debugging i OEM unlocking in the developer menu.
3. Connect the device to the PC and execute the command:

   adb reboot bootloader

4. In mode fastboot enter the unlock command (for example, for Pixel):

   fastboot flashing unlock

   A warning will appear on the device screen - confirm unlocking with the volume button.

Developer mode enabled|USB debugging activated|Unlocking enabled OEM|The device is connected to the PC in file transfer mode|A backup of all important data has been made-->

⚠️ Attention: On some devices (for example, Huawei or Motorola), unlocking the bootloader can lead to loss of access to encrypted partitions. If after the procedure the smartphone does not boot or requires a password that is not suitable, a full reset will be required. via fastboot:

fastboot erase userdata
fastboot reboot

3. Installing custom recovery (TWRP) on Android 10

For firmware Magisk or SuperSU you will need custom recovery. TWRP (Team Win Recovery Project) is the most popular solution, but Android 10 its installation is complicated due to dynamic partitions (dynamic partitions) and A/B systems (dual-slot firmware).

Before installation TWRP check whether your device supports unofficial assemblies. The official list of compatible models is available on the website twrp.me. c A/B-sections (for example, Pixel 3, OnePlus 7) you will need a patched image TWRP, which is temporarily flashed in boot or recovery_ramdisk.

Instructions for installation TWRP:

1. Download the current version TWRP for your model (for example, twrp-3.7.0_9-0-pixel3.img).
2. Reboot the device in fastboot:

   adb reboot bootloader

3. Temporary firmware (for A/B devices):

   fastboot boot twrp-3.7.0_9-0-pixel3.img

   Or permanent (for devices with one slot):

   fastboot flash recovery twrp-3.7.0_9-0-pixel3.img

4. After loading into TWRP do not allow an automatic reboot - first flash Magisk or disable forced encryption.

What to do if TWRP does not see the internal memory?

If after booting into TWRP the internal memory is displayed as 0 MB, this means that the recovery cannot decrypt the partition /data. Solution:

1. Go to Wipe → Format Data (this will delete all data!).

2. Enter yes to confirm.

3. Reboot into TWRP and check memory availability.

If the problem persists, try using OrangeFox Recovery —it works better with encryption on Android 10.

⚠️ Attention: On devices with SAR (System-as-Root), such as Pixel 3/4 or OnePlus 7/8, firmware TWRP to the partition recovery may lead to its replacement with the original one when the system is first booted. In this case, use the temporary download command (fastboot boot) or patched boot.img.

4. Installing Magisk: the only reliable way to get root on Android 10

Magisk from the developer topjohnwu is not just an alternative SuperSU, but a full-fledged system for modifying Android without violating the integrity of the system partition. On Android 10 this is the only solution that:

• 🔄 Bypasses SafetyNet (allows you to use Google Pay and banking applications).
• 🛡️ Supports AVB 2.0 i DM-Verity.
• 📦 Works with dynamic partitions (for example, super.img on Pixel 4).
• 🔧 Allows you to install modules (for example ViPER4Android or EdXposed).

The installation process Magisk depends on the type of device:

Method 1: Firmware via TWRP (for devices without A/B)

1. Download last Magisk.zip s GitHub.
2. Reboot into TWRP.
3. Click Install → select Magisk.zip → swipe to confirm.
4. Reboot device.

Method 2: Patching boot.img (for A/B devices)

1. Extract boot.img from the firmware for your model (can be downloaded from the manufacturer's website or extracted via payload-dumper for .img-firmware).
2. Copy boot.img to the device.
3. Install Magisk Manager (APK) and select in it Install → Select and Patch a File.
4. After patching, copy received magisk_patched.img on the PC and flash it through fastboot:

   fastboot flash boot magisk_patched.img

fastboot flash boot_b magisk_patched.img
fastboot reboot

Otherwise, after updating the system, root will disappear.-->

⚠️ Attention: If after installation Magisk the device boots into bootloop, most likely you used the wrong boot.img or did not disable forced encryption. Solution:

1. Reboot into TWRP.
2. Run Wipe → Format Data (this will delete all data!).
3. Repeat flash Magisk or patched boot.img.

5. Checking root functionality and bypassing SafetyNet

After successful installation Magisk you need to check:

1. Availability of root access: Install the application Root Checker from Google Play and run the scan.
2. SafetyNet Status: Open Magisk Manager → click Check SafetyNet. data-i="236">, banking applications and FAIL, banking applications and Google Pay will not work.

If SafetyNet does not work, follow these steps:

• 🔧 Install module MagiskHide Props Config via Magisk Manager (section Modules).
• 📱 Enable MagiskHide in settings Magisk Manager and add applications that check root to the hide list (for example, SberBank Online or Google Pay).
• 🔄 Restart the device and check again SafetyNet.

If the problem persists, try:

• Update Magisk to the latest version.
• Remove conflicting ones modules (for example Xposed or EdXposed).
• Reset settings Magisk Manager (Wipe Dalvik/Cache in TWRP).

6. Typical errors and their solutions

Even if you follow the instructions exactly, failures are possible. Below are the most common problems and ways to fix them:

Error	Cause	Solution
Bootloop after firmware Magisk	Incompatible boot.img or encryption not disabled	Flash the original boot.img, format /data to TWRP, repeat patching
fastboot: error: cannot load 'magisk_patched.img'	Damaged file or incorrect path	Check the integrity of the file, use the full path (for example, fastboot flash boot C:\magisk_patched.img)
Magisk Manager does not see root	Wrongly flashed Magisk or module conflict	Reflash Magisk.zip via TWRP, remove all modules
Does not work Google Pay after passing SafetyNet	Modules are modified /system or enabled MagiskHide not for all applications	Disable all modules, add Google Play Services to MagiskHide
The device does not boot after unlocking the bootloader	DRM keys have been reset or damaged vendor	Flash the full stock firmware via fastboot or Odin

⚠️ Attention: If after manipulating with Magisk the device stops booting and TWRP is unavailable, try booting into fastboot and flashing the original boot.img:

fastboot flash boot boot_original.img
fastboot reboot

If this does not help, you will need to completely flash the stock software using the manufacturer's official utilities.

7. Alternative ways to get root (if Magisk is not suitable)

In rare cases Magisk may do not work (for example, on some devices MediaTek or Huawei c Kirin). Consider the alternatives:

• 🔧 SuperSU: Outdated solution, but may work on some devices. data-i="304">and dm-verity And forceencrypt manually via editing fstab.
• 📦 KernelSU: A new project integrated into the kernel. Supports Android 10–14, but requires a custom kernel.
• 🔄 Temporary root via ADB: For some tasks (for example, removing a blower), a temporary root is sufficient. can be obtained via adb shell with rights su.

Installation example SuperSU (only for experienced users!):

1. Download SuperSU.zip and no-verity-opt-encrypt.zip.
2. Flash both archives through TWRP (first no-verity, then SuperSU).
3. Edit /vendor/etc/fstab, replacing forceencrypt on encryptable.

Risks of using SuperSU on Android 10

SuperSU does not support systemless modetherefore:

- Will not work SafetyNet (banking applications will not work).

- Possible problems with OTA updates.

- High risk of bootloop due to conflict with DM-Verity.

Recommended to use only if Magisk impossible install.

8. Restoring the device after unsuccessful manipulations

If something goes wrong and the device does not boot or is unstable, use one of the recovery methods:

Method 1: Flashing stock software via fastboot

For most devices (except Samsung and LG):

1. Download the official firmware from the manufacturer's website (for example, for Pixel or XDA Developers for other brands).
2. Unpack the archive and go to the folder with the firmware.
3. Run the command (for Pixel):

   flash-all.sh

   Or manually (for other devices):

   fastboot flash boot boot.img
   fastboot flash system system.img
   fastboot flash vendor vendor.img
   fastboot reboot

Method 2: Recovery via EFS/IMEI (for Samsung)

If after the firmware it disappeared IMEI or the mobile network:

1. Download the original EFS backup for your model.
2. Flash it through Odin to the section EFS.
3. Perform a reset via *#2767*3855# (carefully - it will delete all data!).

⚠️ Attention: On devices Samsung with a processor Exynos after flashing custom software, the flag may be triggered KNOX (0x1), which leads to loss of functions Samsung Pay, Secure Folder and warranty. Check the status KNOX via *#06# or application Phone INFO.

1. (must match the model and region).

2. Integrity of the bootloader (fastboot flash bootloader bootloader.img).

3. The presence of critical errors in fastboot (for example, FAILED (remote: 'Partition not found') indicates an incorrect partition).-->

FAQ: Frequently asked questions about root on Android 10

Is it possible to get root without unlocking the bootloader?

No. On Android 10 all methods of obtaining root require an unlocked bootloader. The exception is temporary root through vulnerabilities (for example, DirtyCow), but they are closed in current versions of the kernel. Unlocking the bootloader is a mandatory step, which also resets the device to factory settings.

Will Google Pay work after getting root?

Yes, if you configure it correctly MagiskHide and pass the verification SafetyNet. To do this:

1. Enable MagiskHide in the settings Magisk Manager.
2. Add Google Play Services and Google Pay to the list of hidden applications.
3. Install module MagiskHide Props Config and select the certificate Pixel 3.
4. Reboot the device and check the status SafetyNet.

If SafetyNet does not work, remove all modules that modify system partitions.

How to update Android after receiving root?

Updating via OTA after getting root is impossible - the system will detect changes in the partitions and refuse to install the update. Options:

• 🔄 Manual firmware: Download the full OTA image, extract boot.img, patch it via Magisk Manager, then flash the update manually via TWRP or fastboot.
• 📱 Temporary removal of root: Flash the original boot.img, install OTA, then re-patch boot.img via Magisk.
• 🚫 Refusal of updates: If root is critical, stay on the current version or use custom firmware (for example, LineageOS).

Is it possible to return the warranty after getting root?

Formally, no, since unlocking the bootloader and modifying system partitions will void the warranty. However, in practice:

• 🔧 Return the device to stock: flash the original firmware, lock the bootloader (fastboot flashing lock), reset the counter KNOX (if possible).
• 📱 On some devices (for example Xiaomi) you can re-lock the bootloader, but this does not always reset modification flags.
• ⚠️ Manufacturers (for example, Samsung or Huawei) can track changes to hardware flags (for example, KNOX or eFuse), which are reset impossible.

If the device is under warranty, but requires repair due to the fault of the manufacturer (for example, a faulty display), some service centers may turn a blind eye to root if you return the stock firmware. However, this is not guaranteed.

How to remove root and return everything as it was?

To completely remove root and return the device to its original state. status:

1. Download the stock firmware for your model.
2. Flash it through fastboot or the official utility (for example, Odin for Samsung).
3. For devices with Magisk enough to flash the original boot.img:

   fastboot flash boot boot_original.img

4. Lock the bootloader (if required):

   fastboot flashing lock

   ⚠️ This will delete all data!

5. Reset via Settings → System → Reset settings.