By default, root permissions are managed by Kingroot’s own su binary, which some apps (like Titanium Backup) can misinterpret. You will see "Kinguser" instead of "Superuser."
Some users report random reboots or the "root lost after reboot" problem. This is due to the temporary nature of certain exploits.
Note: This version will not work on Android 7.0 Nougat or later due to SELinux enforcements.
Alternative: Use the app "Super-Sume" (no longer on Play Store, but APKs exist) to automate the replacement. Kingroot 3.3.1
Type: Android Rooting Tool / Privilege Escalation Exploit Chain Release Era: ~2015 Developer: Kingroot Studio ( subsidiaries: KingoRoot, Root Genius)
KingRoot 3.3.1 is a "one-click" Android rooting application. Unlike traditional rooting methods (which require a connected PC, an unlocked bootloader, and manual flashing of a custom recovery like TWRP), KingRoot 3.3.1 was designed to root devices directly from the Android UI.
It achieved this by utilizing a library of local privilege escalation exploits. The application would fingerprint the device's kernel and Android version, then deploy a specific exploit to gain root access, subsequently installing the kingroot binary (a modified version of su) and a management application. By default, root permissions are managed by Kingroot’s
The operation of KingRoot 3.3.1 can be broken down into three phases:
A. Reconnaissance (Fingerprinting) Upon launch, the APK collected system metadata:
This data was often sent to Kingroot's servers to determine if a rooting strategy existed for that specific combination. This data was often sent to Kingroot's servers
B. Privilege Escalation (The Exploit) Version 3.3.1 was active during the transition from Android 4.x (KitKat) to 5.x (Lollipop). It utilized a "vulnerability database" contained within the APK assets. Common exploits leveraged during this era included:
C. Persistence (Installation) Once the exploit provided a temporary root shell, KingRoot executed a script to: