The era of Android 5.0 Lollipop and 5.1 was a turning point in the history of Google's mobile operating system. It was then that a new permissions management system was introduced, which made it much more difficult to gain full control of the device compared to previous versions of KitKat and Jelly Bean. Many users still use budget smartphones or tablets on this platform, wanting to expand their functionality, remove pre-installed junk or install specialized modules.
The procedure rooting on this version of the OS requires not just pressing one button, but an understanding of the security architecture SELinuxwhich by default operates in Enforcing mode. This means that even having a superuser does not guarantee full access to all system partitions without additional manipulations. Before taking active steps, you must clearly understand that you are going to interfere with the operation of the system kernel, which is always associated with certain risks.
In this material we will analyze in detail all the available methods for obtaining superuser privileges for devices based on Android 5. We will consider both software solutions that work without a PC, and a more reliable method through custom recovery. We will also pay attention to the specifics of unlocking the bootloader, which is a mandatory step for most modern procedures.
Preparation of the device and risk assessment
The first step before starting any system modification is to create a full backup copy of the data. Getting root access on Android 5 often requires a factory reset, which will result in permanent loss of contacts, messages and photos unless they are saved separately. Use cloud services or connect the device to a computer to copy important files to the internal memory or card microSD.
⚠️ Attention: The rooting procedure will void the official warranty on the device. In the event of software failures, service centers may refuse free repairs, citing a violation of the integrity of the software.
A critically important parameter is the battery charge level. The process of flashing or setting access rights should not be interrupted due to a low battery, as this can lead to the smartphone turning into a “brick”. Make sure the charge is at least 60-70%. You also need to enable USB debugging mode in the developer menu.
To activate the hidden menu, go to Settings → About phone and quickly click 7 times on the item Build number. After a notification appears that you have become a developer, return to the main settings menu, find the new section For developers and activate the switch USB debugging. This will allow the computer to interact with the device at a deep system level.
☑️ Ready for rooting
Unlocking the bootloader
Most modern devices released with Android 5 have a locked bootloader. This is a security mechanism that prevents the installation of software that is not signed by the manufacturer, including custom recoveries and rooted images. Without unlocking Bootloader installation TWRP Recovery will be impossible.
The unlocking process varies depending on the manufacturer. For devices Nexus i Pixel this is done through a simple command in Fastboot mode. For brands like Sony, Motorola or Xiaomi often you need to obtain a special unlock code on the manufacturer's official website linked to the IMEI of the device.
Run the command to check the status of the bootloader by connecting the phone to the PC in Fastboot mode:
fastboot oem device-infoIf you receive a response Device unlocked: false, this means the blocking is active. The unlock command usually looks like fastboot oem unlock or fastboot flashing unlock. Remember that this action initiates a complete data reset (Wipe Data).
What to do if the bootloader is not unlocked?
Some telecom operators or regional versions of smartphones have a permanently locked bootloader. In this case, software unlocking is impossible, and you will have to look for vulnerabilities in a specific firmware version or accept the lack of root access.
After successful unlocking, the status will change to true, and you can reboot into the system or immediately proceed to installing a modified recovery. Ignoring this step will make all further attempts to install a superuser through recovery useless.
Installation method through custom recovery TWRP
The most reliable and clean way to obtain superuser rights is to install the package SuperSU or Magisk (if the version supports Android 5) through a modified recovery. TWRP (Team Win Recovery Project) provides a convenient graphical interface for working with system partitions and installing zip archives.
First you need to find a recovery image that is compatible with your device model and version of Android. Universal images may not work due to differences in partition layout or display drivers. The downloaded file twrp.img needs to be flashed through the computer while in Fastboot mode:
fastboot flash recovery twrp.imgImmediately after flashing, it is important not to boot into a normal system, but to go into recovery mode. On many devices, this requires holding down the volume and power buttons immediately after the screen goes dark after the firmware command.
| Stage | Action | Risk of error |
|---|---|---|
| Image search | Download TWRP for a specific model | High (incorrect image) |
| Firmware | Fastboot flash recovery command | Medium (cable error) |
| Installing root | Flash zip archive in the TWRP menu | Low |
| Reboot | Reboot System | Low |
In the TWRP menu, select item Install, find the downloaded archive with access rights (for example SuperSU-v2.79-SR5.zip) and slide your finger along the slider to confirm the installation. After completing the procedure, click Reboot System. If everything went well, a superuser control icon will appear in the application menu.
Using TWRP is the safest method, as it allows you to easily remove root access by simply restoring the original recovery image or deleting the zip file through a file manager.
One-click utilities for rooting without a PC
For users who do not want to bother with drivers, the command line and unlocking the bootloader, there are applications that promise to obtain rights in one click. On Android 5, utilities such as KingoRoot, iRoot or Framarootcan still be effective by exploiting kernel vulnerabilities that have not been patched by budget device manufacturers.
These applications work by matching a known exploit to the specific version of the Linux kernel on which Android is based. They do not require unlocking the bootloader in the classical sense, since they use security holes to temporarily increase privileges and pin the binary file su to the system partition.
- 📱 Download the APK file of the utility (for example, KingoRoot) directly to the device, since there are no such applications on Google Play.
- 🔌 Allow installation from unknown sources in the security settings before running the installer.
- ⚡ Launch the application and click the "Get Root" button, trusting the automatic script to select the method.
- 🔄 The device may reboot several times while exploiting the vulnerability.
It is worth noting that the effectiveness of such methods on Android 5 is lower than on older versions due to improved protection SELinux. If the utility reports an error or freezes at the 50% stage, most likely the exploit did not work, and repeated attempts are pointless.
Problems with SELinux and system access
Even after successfully installing the binary file su Android 5 users may encounter a situation where applications do not receive full access or the system is unstable. The reason for this is often the operating mode SELinux, which in Lollipop by default blocks many system calls, even on behalf of the superuser.
For the full operation of some modules and tweaks, you need to switch SELinux from Enforcing mode to Permissive. This can be done using special applications from the Play Market, such as SELinux Mode Changer, which require root access to operate.
⚠️ Attention: Switching SELinux to Permissive mode reduces the overall level of system security, making it more vulnerable to malware. Do this only if it is critically necessary for the operation of specific applications.
You can check the current status through the terminal by entering the command getenforce. If the answer is Enforcing, then the protection is active. The change to Permissive will allow you to bypass many access restrictions to files and processes, which is often required for the operation of advanced backup utilities like Titanium Backup.
Possible errors and ways to eliminate them
When rooting Android 5, you may encounter a cyclic reboot (bootloop), when the device constantly shows the manufacturer's logo and does not loads further. This often happens when installing an incompatible version of SuperSU or the system partition is damaged during recording.
If the device is in a bootloop, try going into recovery mode (Stock Recovery or TWRP, if it was installed). In the recovery menu, select Wipe Cache Partition. This will clear temporary files that could conflict with the new access rights, but will not affect your personal data.
In more serious cases, when clearing the cache does not help, you will need a full reset (Factory Reset) or flashing the stock system image via a computer using utilities like Odin (for Samsung) or SP Flash Tool (for MediaTek). Always have the stock firmware for your model on hand before starting experiments.
If after rooting the Internet is lost or calls do not work, check the APN settings and make sure that you have not deleted the system applications responsible for the operation of the radio module.
Frequently asked questions (FAQ)
Is it safe to root Android 5 in 2026?
From a data security point of view, no. Android 5 no longer receives security updates, and root access opens up additional attack vectors. Use this only on devices that do not contain critical information.
Is it possible to get root without unlocking the bootloader?
Only using one-click utilities that use exploits. However, on Android 5 this method is unstable and depends on the specific processor model and kernel version. The reliable method via TWRP requires unlocking.
How to completely remove root access?
If you used SuperSU, go to the application settings and select "Full removal". If you used Magisk or manual installation, the easiest way is to reflash the stock system image or boot.img file.
Will banking applications stop working?
With a high degree of probability, yes. Banking applications and payment systems (Google Pay) detect the presence of root access and a locked bootloader, refusing to launch. It is extremely difficult to hide root on the old version of Android 5.