How to get root access on Android 14: complete guide

Obtaining root access on devices running Android 14 has become much more difficult compared to previous versions of the OS. Tightening security policies, introducing Verified Boot 2.0 and changing the partition system to A/B complicate the process, but do not make it impossible. Owners of modern smartphones are looking for ways to bypass restrictions for installing specialized modules or removing system bloatware.

In this article we will analyze in detail the current rooting methods using Magisk and KSU (KernelSU). You will be faced with the need to unlock the bootloader, work with ADB and Fastboot, as well as the risk of completely losing the warranty. Preparation requires care, as one mistake can turn your gadget into a brick.

Before you begin, make sure you fully understand the consequences of your actions. Modern data protection systems can erase all information with the slightest intervention in the boot process. We will look at a step-by-step algorithm that minimizes risks, but there is no absolute guarantee of security in any method of system modification.

Device preparation and backup

The first critical step is to save all important data. The procedure for unlocking the bootloader on most manufacturers, including Xiaomi, OnePlus i Google Pixel, initiates a complete reset of the device to factory settings. This means that all photos, contacts and applications will be permanently deleted.

You must activate Developer mode to access USB debugging. Go to Settings → About phone and click 7 times on the build number. After this, a new item will appear in the menu where you need to enable USB debugging. Without this step, the computer will not be able to send commands to the smartphone.

Create a complete backup of the system using cloud services or a local connection to a PC. Some manufacturers block the ability to backup certain partitions without superuser rights, so save everything you can to an external drive.

⚠️ Attention: Unlocking the bootloader permanently resets Knox security flags on Samsung devices and similar protections on other brands. This may permanently disable banking applications and Samsung Pay even after returning to stock firmware.

You will need a high-quality USB cable, preferably an original one, since cheap analogues often only support charging and do not transfer data. A stable connection is critically important when flashing images, since a break in the connection will lead to a recording error.

Unlocking the bootloader

Without an unlocked Bootloader installation of a custom recovery or a modified kernel is impossible. Manufacturers use different methods: from a simple Fastboot command to obtaining a special code through the official website, as does Huawei (on older models) or Motorola.

For processor-based devices MediaTek i Qualcomm the procedure often comes down to executing the command in Fastboot mode. Connect your phone to the PC while holding the volume down button and enter the command fastboot flashing unlock. A warning about data loss will appear on the device screen.

Confirm the action using the volume buttons. The process may take from a few seconds to a minute. After rebooting, you will see a message that the bootloader is unlocked and the device will boot into a clean system without your data.

⚠️ Attention: On some carriers (especially in the US), the bootloader is locked at the hardware level. Check the status via the command fastboot oem device-info before starting work.

If the command does not work, the manufacturer may require preliminary registration of the device on its portal. Carefully study the forum XDA Developers specifically for your model, since the nuances may differ even within the same line of smartphones.

Selecting a tool for rooting: Magisk or KernelSU

On Android 14 the traditional method of installing Magisk through patching the boot image is still relevant, but a new alternative is emerging - KernelSU. This tool works directly at the kernel level, which makes it more secretive for security systems and banking applications.

Magisk remains the most popular solution due to its huge base of modules and ease of use. It injects itself into the boot partition and grants superuser rights through the app. However, the Detect Root system on Android 14 has become more aggressive, so additional hiding settings are required.

KernelSU requires a compatible kernel (GKI 5.10+), which limits its use only to recent devices. If your smartphone was released after 2022, the chances of support are high. Otherwise, you will have to be content with the classic Magisk.

Characteristics	Magisk	KernelSU	SuperSU (Outdated)
Working method	Patching boot.img	Module kernels	Replacing su binaries
Stealth	Requires Zygisk settings	High (default)	None
Android support 14	Full	Kernel GKI only	No
Installing modules	Via application	Via kernel modules	Limited

The choice of tool depends on your goals. To easily install an ad blocker or system tweakers, Magisk is suitable. If the operation of banking applications without dancing with a tambourine is critical to you, you should take a closer look at KernelSU if technically possible.

Extracting and patching the Boot image

The most difficult technical stage is obtaining the file boot.img from the official firmware. You need to download the full firmware image (Factory Image or OTA zip) corresponding to the current version of Android on your device. A version mismatch can lead to a bootlap.

Use an archiver to extract the firmware. In some cases, the boot file is located inside the file payload.bin. To extract it, you will need a special utility payload-dumper-go. Run it in the terminal, specifying the path to the archive.

Copy the extracted boot.img to your smartphone. Install the Magisk application, open it and click the "Install" button next to Magisk. Select the option "Select and patch a file" and specify the copied image.

adb push boot.img /sdcard/
adb shell
su
cd /sdcard
magisk --patch boot.img

After the process is completed, a file with the name of the type will appear in the downloads folder magisk_patched_[random].img. It is this file that will need to be returned to the computer and flashed via Fastboot. An error at this stage is often associated with insufficient memory space or a damaged firmware archive.

What to do if payload.bin does not unpack?

Sometimes the structure of the firmware changes. Try using online services to dump payload.bin or find an already unpacked boot.img on specialized forums for your model.

Flashing a modified image via Fastboot

Return the patched file to your computer. Put your smartphone into Fastboot mode (usually by holding the volume down button when turning it on). Make sure that the PC sees the device with the command fastboot devices.

For devices with A/B partitions (most modern phones), you need to flash both slots or the currently active one. The command for flashing the firmware looks like this: fastboot flash boot magisk_patched.img. If you have a device without A/B, the command is similar, but the process occurs instantly.

After successful recording, you must reboot. Do not try to immediately boot into the system if you see errors in the console. Give the device time to initialize the modified kernel for the first time; this may take up to 5 minutes.

⚠️ Attention: On devices with Dynamic Partitions, the firmware command may differ. Sometimes you need to use fastboot flash boot_a i fastboot flash boot_b separately.

If after a reboot the Magisk logo does not appear and the system boots as usual, then the patching was unsuccessful or the image was damaged. In this case, you will have to repeat the procedure from the very beginning, downloading the firmware again.

Setting up hiding Root and working with modules

After successfully obtaining root access, the system can still see the presence of root access. Banking applications and games with anti-cheat (for example, Pokemon GO) will refuse to work. To solve this problem, you need to activate Magisk Zygisk.

Go to Magisk settings, enable Zygisk and reboot your device. Next, go to the "Customize DenyList" section. Check all banking applications, Google Pay and games there. This will tell Magisk to hide root access for these processes.

Additionally, it is recommended to install the module Play Integrity Fix. It replaces the device's fingerprints, making Google services think that the bootloader is locked and the system has not been modified. Without this module on Android 14, many services may not function correctly.

Be careful when installing third-party modules. An incompatible module may cause a cyclic reboot. In safe mode (booting with the volume down button held down), Magisk automatically disables all modules, allowing you to restore system functionality.

Possible problems and solutions

The most common problem is Bootloop (cyclic reboot). If the device does not boot beyond the logo, try entering Recovery mode (if it is custom) or Fastboot and flashing the original one. This will return the phone to stock state. boot.img. This will return the phone to stock state.

The lack of Internet after rooting may be due to a module conflict or a change in iptables rules. Check your firewall settings and disable recently installed tweaks. Sometimes resetting the network settings helps.

The camera's performance may deteriorate due to loss of Google certification. In this case, installing the GCam (Google Camera) module with the correct configs often solves the problem of image quality, but does not always return all sensors to work.

Will the warranty expire after obtaining root access?

In most cases, yes, the fact of unlocking the bootloader is recorded on the manufacturer's servers. Even if you close the bootloader back, the physical flag (efuse) may remain switched, which the service center can easily detect during diagnostics.

Is it possible to get root without unlocking the bootloader?

On modern Android 14 devices this is almost impossible. Kernel-level vulnerabilities that allow this (like old exploits) are quickly fixed by security updates. The only legal way is the official BL unlock.

Is it safe to use banking applications with root?

Yes, if hidden access (DenyList) is correctly configured and disguise modules like Play Integrity Fix are installed. However, banks can update their detection methods at any time, so there is no 100% guarantee.

What are A/B partitions and how do they affect the firmware?

The A/B system uses two sets of partitions (slots) for seamless updating. When flashing firmware, it is important to understand which slot you are currently in, otherwise the modified image may be written to an inactive slot, and you will boot into a clean system without root.

Is it possible to update Android over the air after rooting?

A standard OTA update will not be installed on the modified boot partition. You will have to manually flash full firmware images or use special modules that temporarily restore the stock boot to install the update.