You are trying to unlock superuser rights on your Android device, but every time you encounter errors: fastboot refuses to unlock the bootloader, Magisk is not installed, and then reboot the phone freezes on the logo? This problem is familiar to many who try to obtain root access on modern smartphones. Manufacturers are actively tightening protection, and algorithms for checking system integrity are becoming more and more complex.

In this article we will not just list typical errors like Failed to mount /system (Invalid argument) or DM-Verity corruption detected, but we will analyze hidden reasonswhich are rare mentioned in standard guides. For example, why on some models Samsung after updating to One UI 6.0 the method with the patch stops working AP after Odin, or why Xiaomi blocks unlocking the bootloader even after 7 days of waiting. You will also learn how to bypass restrictions on devices with hardware integrity check (for example, on chips Google Tensor or Exynos 2200)where standard methods no longer work.

Before moving on to solutions, make sure you understand the risks: loss of warranty, possible brick (turning the phone into a "brick"), problems with banking applications and SafetyNet. If you are ready, let's start diagnostics.

1. The bootloader is locked: why unlocking does not work

The first thing users encounter is locking the bootloaderEven if you have followed all the steps from the instructions, the command fastboot oem unlock may return an error FAILED (remote: 'Flashing is not allowed') or simply do nothing. The reasons lie deeper than it seems:

  • 🔒 The manufacturer prohibited unlocking for your model/region (for example, Samsung in the USA or Huawei after sanctions).
  • ⏳ The mandatory deadline was not met waiting (y Xiaomi — 7 days, y Realme — 168 hours).
  • 📱 The device is locked to the operator (for example, smartphones from Verizon or AT&T often have an “unlockable” bootloader).
  • 🔄 The firmware was updated over the air (OTA), and the bootloader is automatically locked again.

To check the status of the bootloader, run the fastboot command:

fastboot oem device-info

Look for the lines Device unlocked: false or Bootloader unlock allowed: noIf there. costs false/no, which means that software unlocking is prohibited. In this case, only bypassing through EDL mode (for Qualcomm) or searching for vulnerabilities in a specific firmware will help.

⚠️ Attention: On devices with chip Google Tensor (for example, Pixel 6/7/8) unlocking the bootloader resets all data, even if you used the command fastboot flashing unlock_critical. Backup via TWRP will not help here - storage encryption makes backups useless.
📊 What brand of smartphone are you trying to unlock?
Samsung
Xiaomi
Google Pixel
OnePlus
Realme/Oppo
Other

Let's say the bootloader is unlocked, but when you try to flash Magisk via TWRP or fastboot you get an error Installation failed: 1 or the phone goes into bootloop (infinite reboot). Here's what may be wrong:

  • 📦 Wrong version of Magisk. For example, Android 14 will not work Magisk 25.2 - you need at least 26.1+.
  • 🔗 Damaged boot image. If you manually patched boot.img via Magisk Manager, but forgot to disable compression (--compress), the file may not be flashed.
  • 🛡️ AVB 2.0 Active Protection. On new devices (for example Pixel 7 Pro), the integrity check blocks loading even with the patch Magisk.
  • 🔄 Conflict with custom recovery. Some versions TWRP are incompatible with Dynamic Partitions (used on Android 10+).

Solutions:

  1. Check the version Magisk on official GitHub (link to check relevance).
  2. If you use fastboot, flash boot.img with the flag --disable-verity --disable-verification:
fastboot flash boot magisk_patched.img --disable-verity --disable-verification
  1. For devices with Dynamic Partitions (for example, OnePlus 9 Pro) use fastboot flash boot_a i fastboot flash boot_b for both slots.

Download the latest version of Magisk (not beta!)

Check the device model for compatibility

Disable encryption (if possible)

Make a backup of data (even if unlocking does not erase them)

Check the boot.img version (must match the current firmware)

-->

If after flashing the phone is stuck on the logo, try:

  1. Press Power + Volume Down to go to fastboot and flash the original boot.img.
  2. Delete files /data/adb/* via ADB Sideload (sometimes it helps with bootloop due to Magisk).

3. Firmware compatibility: why 2020 methods do not work in 2026

Many guides on the Internet are outdated. For example, the method with firmware TWRP via Odin on Samsung Galaxy S22 will no longer work - the company has implemented VaultKeeperwhich blocks any changes in section /system. The same thing with Xiaomi: after updating to HyperOS old methods of unlocking the bootloader stopped working.

Manufacturer Model/Firmware What has changed Workaround
Samsung Galaxy S23+, One UI 6.1 Blocking OEM Unlock in the developer menu Use Shim to bypass VaultKeeper (requires EDL)
Xiaomi Redmi Note 12 Pro+, HyperOS Increased waiting time for unlocking to 168 hours Bypassing Mi Unlock Tool with modified fastboot
Google Pixel 8 Pro, Android 14 QPR2 AVB 3.0 blocks patches boot.img Firmware via fastbootd with disabling verification
OnePlus OnePlus 11, OxygenOS 14 Removed option OEM Unlock in settings Use MSM Tool for a complete reset and unlock

If your model is not listed in the table, check the current methods on the forums XDA Developers or 4PDA. Please note: for devices with Mediatek (for example, Realme 10 Pro+) you may need an authorized account to unlock via SP Flash Tool.

⚠️ Attention: On some devices Samsung (for example, Galaxy A54) after unlocking the bootloader, eFuse is triggered—a hardware flag that permanently marks the device as “jailbroken.” This may lead to problems with official updates and service.

4. Problems with SafetyNet and banking applications after root

Even if you managed to get root access, you may encounter that applications like Google Pay, SberBank Online or Tinkoff refuse to work, giving an error "The device is not certified" or "Detected root". This is due to the mechanism SafetyNetthat checks the integrity of the system.

Here's what you can do:

  • 🔧 Install the module MagiskHide Props Config and replace the device fingerprints (fingerprint) with certified ones.
  • 🛡️ Use Universal SafetyNet Fix (module for Magisk, bypasses verification ctsProfile).
  • 📱 For banking applications: enable MagiskHide and add the application to the list of hidden ones (DenyList).
  • 🔄 If all else fails - try Shamiko (alternative MagiskHide for new versions Magisk).

To check the status SafetyNet, use the application SafetyNet Test or the command:

adb shell su -c "snet check"

If ctsProfile: false, then your device has not passed the test. In this case:

  1. Update Magisk to the latest version.
  2. Remove all modules that may affect build.prop.
  3. Try changing the ROM to GSI (Generic System Image) from support SafetyNet.
💡

If the banking application still does not work, try installing it through Island (sandbox for cloning applications) or Shelter. This will isolate the application from root detection.

5. Hardware limitations: when root is not possible

On some devices it is root access impossible due to hardware limitations. Here are the most common cases:

  • 🔐 Chipset-level protection. For example, Google Pixel 6/7/8 uses Titan M2 a separate security chip that blocks any changes in boot and system.
  • 📱 Devices with eSIM and hardware encryption (for example, iPhone-like Android smartphones like Fairphone 4).
  • 🔄 Smartphones with Dynamic Partition i A/B slots, where the patch boot.img does not provide a full root.
  • 🚫 Devices for corporate use (for example, Samsung Knox-certified models).

In such cases, there are two left option:

  1. Use root without unlocking the bootloader through vulnerabilities (for example, DirtyPipe or CVE-2023-21036This is a temporary root that disappears after a reboot.
  2. Install custom firmware with pre-built root (for example, LineageOS for microG).

To check hardware limitations, use the command:

adb shell getprop ro.boot.verifiedbootstate

If the result is orange or yellow, then the bootloader is unlocked, but the hardware check is still the same active If green the device is completely blocked.

⚠️ Attention: On devices with Google Tensor (for example, Pixel 7 Pro) an attempt to flash uncertified firmware can lead to hardware blockingwhich can only be removed through an official service center (and then not always).

6. Alternatives to root: what to do if you can’t get root

If all attempts to get root access end in failure, do not despair. In many cases, the same problems can be solved without root:

Task Solution without root Limitations
Removing system applications ADB AppControl (disabling via pm disable) Does not delete completely, only hides
Backup applications with data Swift Backup (uses adb backup) Not all applications support adb backup
Change host file DNS66 or Blokada (VPN solutions) Does not block system requests
CPU overclocking Kernel Adiutor (on some devices) Works only with supported kernels
Access to hidden settings Codes ##4636## or Activity Launcher Not all settings are available

For advanced users there is another option — virtual root via Termux and proot. This allows you to run some root applications in an isolated environment, but without real access to the system. Example command for installation:

pkg install proot-distro

proot-distro install ubuntu


proot-distro login ubuntu

💡

If you need root only to remove the bloat or change the interface, try first ADBsolutions or custom launchers. In 80% of cases, they solve the problem without the risk of a brick.

7. Common errors and how to avoid them

Many problems with receiving root access arise due to typical user errors. Here are the most common:

  • 🔌 Wrong USB cable or port. Use the original cable and port USB 2.0 (on some PCs USB 3.0 causes errors fastboot).
  • 📋 Version mismatch. Flash boot.img from Android 12 to a device with Android 13.
  • 🔒 Forgot to unlock OEM Unlock in the developer settings (even if the bootloader is already unlocked).
  • 🔄 Did not clear the cache before flashingSometimes old data conflicts with new ones. modules.
  • 📱 Use an unofficial version of TWRP. Some assemblies contain errors leading to bootloop.

To minimize risks, always:

  1. Check MD5hashes of downloaded files (for example, through 7-Zip or md5sum in Termux).
  2. Use fastboot from the last one Android SDK Platform Tools (not old versions from archives).
  3. Disable Mi Account or Samsung Account before unlocking (on some devices they block the process).
What to do if after Magisk firmware the phone does not turn on?

1. Try holding Power + Volume Up for 10-15 seconds to force a reboot.

2. If it doesn’t help, flash the original boot.img via fastboot flash boot boot_original.img.

3. For devices with A/B slots flash both slots: fastboot flash boot_a and fastboot flash boot_b.

4. If the phone is not detected in fastboot, try the mode EDL (for Qualcomm) or Download Mode (for Samsung).

FAQ: Answers to frequently asked questions

You can Is it possible to get root on Samsung Galaxy S23 without Knox trigger?

No. On all devices Samsung s Knox 3.8+ (including Galaxy S22/S23), unlocking the bootloader inevitably works eFuse, which permanently marks the device as hacked. This leads to:

  • Blocking Samsung Pay and Secure Folder.
  • Inability to use official updates over the air (OTA).
  • Problems with warranty service.

The only workaround is use temporary root through vulnerabilities (for example, CVE-2023-21492), but it disappears after a reboot.

Why do you have to wait 7 days after unlocking the bootloader on Xiaomi?

Xiaomi implemented this delay to protect against theft and unauthorized access. The algorithm works like this:

  1. When an account is first linked Mi to the device, a timer starts.
  2. Every day, the servers Xiaomi check whether there has been a reset or change account.
  3. Only after 168 hours (7 days) unlocking becomes possible.

You can get around this:

  • Use Mi Unlock Tool with a modified fastboot (risk of blocking account).
  • Flash the device via EDL (requires an authorized account Qualcomm).
⚠️ Attention: If you reset the device before the end of 7 days, the timer will reset to zero and the countdown will start again.
How check if my device supports bootloader unlocking?

There are several ways:

  1. Enter the fastboot command: 
    fastboot oem get_unlock_data

    If the command returns data (and not an error), then unlocking is possible.

  2. Check for the option OEM Unlock in the developer menu (Settings → About phone → Build number - tap 7 times, then return to Settings → System → For developers).
  3. Look for your model on XDA Developers —there are usually topics with confirmed unlocking methods.

If your device does not support unlocking, but you need root, consider options with temporary root through vulnerabilities or installation GSI firmware.

Is it possible to get root on Android 14 without unlocking the bootloader?

Technically yes, but with serious limitations. Here are possible ways:

  • Kernel exploits (For example, DirtyPipe or CVE-2023-20938) They give a temporary root that disappears after a reboot.
  • ADB commands with elevated rights. Some manufacturers (for example, Sony) allow you to execute commands su through adb shell without full root.
  • Virtual environment (for example, UserLAnd or Termux s proot). Allows you to run root applications in an isolated space.

However, a full-fledged permanent root without unlocking the bootloader on Android 14 is impossible due to:

  • DM-Verity - checking the integrity of the system at each boot.
  • AVB 3.0 - improved verification system downloads.
  • Protection at the kernel level (for example, Kernel Lockdown v Linux 5.4+).
How to return everything back if after trying to root the phone does not turn on?

If the device does not respond or is stuck on the logo, proceed according to the algorithm:

  1. Try a forced reboot:
    • For Samsung: Power + Volume Down for 10 seconds.
    • For Xiaomi/Redmi: Power + Volume Up for 15 seconds.
    • For Google Pixel: Power for 30 seconds (until it vibrates).
  2. Flash the original firmware:
    • For Samsung: use Odin with proprietary firmware (download from samfw.com).
    • For Xiaomi: Mi Flash Tool in clean all.
    • For Qualcommdevices: QFil or EDL Tool.
  • If the phone is not detected:
    • Check the drivers (install Qualcomm HS-USB QDLoader 9008 for EDL).
    • Try another USB port or cable (the original one is better).
    • On some devices you need to close the test points (for example, to Redmi Note 10 Pro).

    If all else fails, contact the service center - there may have been hard brick (damage to the bootloader at the hardware level).