Obtaining root access on Android 5.1 Lollipop

Operating system version Android 5.1 Lollipop, despite its age, is still installed on millions of budget smartphones and tablets that continue to perform their functions properly. However, standard Google restrictions often prevent users from realizing the full potential of these devices by blocking access to system files and settings. Obtaining root access (superuser rights) becomes the only legal way to bypass these prohibitions, allowing you to remove pre-installed software, overclock the processor and install specialized modules.

The rooting process on this version of the OS has its own unique features that differ from modern methods on Android 10-14. In particular, Lollipop's security architecture is less restrictive, which opens the door to simple, single-command applications that don't require a computer connection. However, interfering with the operation of the system kernel is always fraught with risks, and before starting the procedure, it is necessary to clearly understand the responsibility for the possible consequences.

In this guide, we will examine in detail the most effective and time-tested methods of activating privileged access. We will consider both software methods through special utilities, as well as more advanced options using ADB and custom recovery.

Preparation of the device and risk assessment

Before taking active steps, it is critically important to prepare the smartphone for system modification. The first step should be to create a complete backup of all important data, including contacts, messages and photos. The process of obtaining administrator rights often requires a reboot or reset, which can lead to permanent loss of information if you do not take care of its safety in advance.

The second mandatory point is to ensure a stable battery level. It is recommended to charge the device to at least 70-80%to eliminate the possibility of a power outage at the most critical moment of recording system partitions. A sudden shutdown of the smartphone while flashing the firmware or modifying the bootloader can turn the device into a “brick,” the restoration of which will require complex hardware repairs.

⚠️ Attention: Obtaining root access will automatically void the factory warranty for the device in most service centers. Manufacturers consider any interference with the system partition as a violation of operating conditions.

You must also activate the USB debugging mode in the developer settings. To do this, go to the menu Settings → About phone and quickly click on the build number seven times to unlock the hidden menu. After that, in the section that appears For developers find the item USB debugging and activate it with the switch.

Using universal applications for rooting

The simplest and most accessible method for Android 5.1 users is to use specialized APK files that automate the process of exploiting system vulnerabilities. apps like KingRoot, KingoRoot or Framaroot were especially effective on Lollipop versions, since the exploits they used had not yet been closed by Google security updates of that period.

To get started, you will need to download the installation file of the selected utility from the official website of the developer or a verified archive. Installing applications from unknown sources must be allowed in your smartphone's security settings. After launch, the app will automatically analyze compatibility and offer a button to start the procedure, which usually you just need to press and wait for completion.

• 📲 KingRoot - the most popular solution with a high base of supported devices, often works without the need for a reboot.
• 🚀 Framaroot - great for older MediaTek and Qualcomm processors, uses Borromean Rings and Gandalf exploits.
• 💻 KingoRoot —has both a mobile version and a desktop client for PC, which increases the chances of success if the phone fails.

It is important to note that not all devices are supported equally well by these utilities. Success depends on the specific firmware build and security patches installed by the manufacturer. If one application was unable to gain access, you should try an alternative option by first deleting the unsuccessful attempt and rebooting the smartphone.

Rooting method via computer and ADB

If mobile applications did not cope with the task, a more reliable way would be to use a computer and tools Android Debug Bridge (ADB). This method requires drivers for your device and the Platform Tools package installed on your PC. It gives greater control over the process and allows you to manually send commands to exploit vulnerabilities.

Connect your smartphone to your computer via a high-quality USB cable and make sure that the system sees the device. In the command line or terminal on your PC, enter the command adb devices to test the connection. If the device is displayed in the list with status device, you can start downloading temporary recovery or binary executable files su directly to the system partition.

adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su

This approach is often used in conjunction with a utility SuperSUthat requires installing a special ZIP archive via recovery mode. In the case of Android 5.1, sometimes it is enough to simply send a command to temporarily obtain rights in order to then install the privilege manager. However, to permanently secure the result, you often need to unlock the bootloader, which can erase all data.

⚠️ Attention: Using ADB requires care when entering commands. An error in the file path or partition name can lead to damage to the file system and the inability to boot the OS.

Installing custom TWRP recovery

For advanced users, installing a modified recovery mode such as TWRP (Team Win Recovery Project). The presence of custom recovery allows you to install not only superuser rights, but also any other system modifications, including custom firmware and kernels. On Android 5.1, this process usually runs reliably on most popular models of that time.

The procedure begins by searching for an image .imgspecifically compiled for your specific smartphone model. Universal images may not be suitable due to differences in disk layout or display drivers. After downloading the file, you need to rename it to recovery.img and place it in the ADB tools folder on your computer.

Next, the device is switched to Fastboot mode (usually by holding down the volume and power keys when the phone is turned off). The command for flashing the recovery is as follows:

fastboot flash recovery recovery.img
fastboot boot recovery.img

After successful recording, a new recovery menu with touch controls will appear in the device memory. It is through this interface that the archive with access rights is subsequently installed. This is the most reliable method that minimizes the risk of getting a “bootloop” (cyclic reboot) compared to directly editing system files.

What to do if Fastboot does not see the phone?

If the fastboot devices command does not return the serial number, check the installed ADB/Fastboot drivers on the computer. Try using a different USB port, preferably USB 2.0, and the original cable. Also make sure that the device's bootloader is not permanently locked by the manufacturer (which often happens with carrier versions of smartphones).

Installing the rights manager SuperSU or Magisk

After you have access to recovery mode or temporary rights, you need to install a manager that will control application requests for privileges. For Android 5.1, historically, SuperSU is the most stable and lightweight solution, although the project Magisk also supports this version, offering the function of hiding the root from banking applications.

If you use TWRP, download the ZIP archive with the manager firmware and place it in the internal memory of the phone. In the recovery menu, select Install, find the downloaded archive and swipe the slider to confirm the installation. The system will automatically insert binary files into the required directories and configure initialization scripts.

Manager	Compatibility with Android 5.1	Installation complexity	Hide ability
SuperSU	Excellent (Native)	Low	No (Requires additions)
Magisk	Good (Requires old version)	Average	Yes (Built-in)
KingUser	Medium	Low (Auto)	Partial

After installation and reboot, a new manager icon will appear in the application menu. When you first launch the application, you may be prompted to update the binaries or perform a full setup. Agree with the recommendations to ensure that all security and access control functions work correctly.

Checking for root access and troubleshooting problems

The final stage is verification of the success of the operation. There are many applications on Google Play, such as Root Checker, which in one click determine whether you have superuser rights. Run this utility, click the check button and wait for the result. If you see a green checkmark and a message that access has been granted, the procedure was successful.

However, sometimes there is a situation when the rights manager is installed, but applications cannot gain access. In this case, go to the settings of the manager itself (SuperSU or Magisk) and check whether the “Give access” or “Allow ROOT” switch is turned on. Also make sure that SELinux is not in Strict mode, which can block some operations, although this is less critical for Android 5.1 than for newer versions.

• 🛠 Check the event log in the rights manager to see if requests from specific applications are blocked.
• 🔄 Try reinstalling the binaries through the app settings, selecting the "Normal" option installation.
• 📱 Make sure that the antivirus does not block the operation of system utilities by adding the rights manager to the exceptions.

If all else fails, perhaps your firmware version has specific protections that were not bypassed by the selected method. In this case, you should look for specialized topics on forums dedicated specifically to your device model, where users share unique scripts or modified recovery images.

⚠️ Attention: Having root access makes the device vulnerable to malware. Do not provide superuser access to applications from unverified sources, as they can gain complete control over your system and data.

Frequently asked questions (FAQ)

Is it safe to root on old Android 5.1?

Security depends on your actions. The procedure itself is technically safe if you follow the instructions, but having superuser rights reduces the overall level of system security. On an outdated version of Android, which no longer receives security patches from Google, the risk of virus infection is higher, so you need to be extremely careful with application sources.

Is it possible to remove root access after receiving them?

Yes, this is possible. If you used SuperSU, there is a “Full Unroot” function in the application settings that restores the original system files. If you used Magisk, you can use the complete uninstall function. In extreme cases, flashing the stock firmware via a computer will help.

Will banking applications stop working after rooting?

Most likely, yes. Banking applications and services like Google Pay (at that time) detect the presence of superuser rights and refuse to work. To get around this, you need to use the root hiding features available in Magisk, or look for special modules that mask the status of the device.

What is “bricked” and how to avoid it when rooting?

“Bricked” is the state of a device when it stops turning on or loading the operating system due to a critical error in the software. To avoid this, strictly follow the instructions for your specific model, do not interrupt the process of writing files, and always have the original firmware on hand for recovery.

Do you need a computer to get rights to Android 5.1?

Not always. For many devices, it is enough to install the APK file of a utility like KingRoot directly on the phone. However, using a computer with ADB and Fastboot gives a greater chance of success in difficult cases and allows you to restore the device if something goes wrong.