Version: 2.78-SR1 (278)
Package: eu.chainfire.supersu
6.19 MB (6,487,102 bytes)
Min: Android 2.1 (Eclair, API 7)
Target: Android 5.0 (Lollipop, API 21)
Uploaded September 15, 2016 at 8:44PM UTC by Artem Russakovskii
Download APK
There's a newer version available below!

Whoa there!

It looks like you're using an ad blocker, so you'll have to wait 15 more seconds.
Please whitelist this site to skip the wait and help us pay for bandwidth, hosting, and other bills.

SuperSU v2.78 SR1 released

This update brings primarily bugfixes to the su binary (related to suhide and Magisk compatibility), but there is one supolicy update of particular note as well:

Due to an initialization bug, introduced in v2.68 BETA, some SELinux contexts (including shell and untrusted_app) could be granted sys_module capability. If this happens, and your kernel is compiled with module loading support (most modern stock kernels have this disabled) and an exploit is used to gain uid 0, this then allows for a complete SELinux bypass and kernel pwn.

The requirements are pretty extensive and your chances of being vulnerable are slim, but nevertheless I would recommend updating.

This fix requires SuperSU to be updated by flashing the ZIP. Updating by APK will not suffice.

SRx instead of BETA
We're moving from BETA to Service Release naming, so we can keep the version number for the next test release the same as the current stable release. So, v2.78 SR1 is what would have been v2.79 BETA before.

While this may be slightly more confusing, we need to keep the version numbers the same to reduce the effectiveness of people trying to upload the test releases to stores (many stores will not accept a version number already present). Surprisingly, this is a real problem on non-Play stores.

Discussion regarding CCMT has suddenly (about a year late) become prominent again. There will be some announcements regarding this probably next week.

SuperSU BETA thread:

FlashFire/TWRP Flashable ZIP:

- subinary: Adjust app_process detection with manipulated mount namespaces
- subinary: Adjust Zygote PID detection to prefer 64-bit
- subinary: Fix possible NPE in LD_PRELOAD sanitization
- subinary: In systemless mode, ensure PATH contains /su/bin and /su/xbin
- supolicy: Ensure zero-on-alloc for new rules
- supolicy: Fix parsing allowxperm with multiple sources/targets in a single definition
- ZIP/Systemless: Give su.d 60 seconds to execute (from 4 seconds)´╗┐
SuperSU is the Superuser access management tool of the future ;)

!!! SuperSU requires a rooted device !!!

SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. SuperSU has been built from the ground up to counter a number of problems with other Superuser access management tools.

Features include:

- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Always runs in ghost mode
- Wake on prompt
- Convert to /system app
- Complete unroot
- Backup script to survive CyanogenMod nightlies
- Icon selectable from 5 options + invisible
- Theme selectable from 4 options
- Launch from dialer: *#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*)
NOTE: Not all phones take both codes. On some phones you need to use single *# instead of double *#*#

The Pro version additionally offers:

- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- Grant/deny root to an app for a set amount of time
- PIN protection
- Per-app PIN protection
- Adjust auto-deny countdown

The discussion and support thread can be found on XDA-Developers here:

This is meant to replace Superuser (if installed), you use either one or the other. You cannot combine them. Statements that this breaks Superuser are therefore completely nonsensical.


Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU.

Want to help translate SuperSU ? See !

These are completely optional and more like donations. They do not unlock any functionality.

Contact us:
Website :
All versions
October 1, 2017
September 18, 2017
August 13, 2017
May 29, 2017
May 25, 2017
May 24, 2017
March 23, 2017
January 14, 2017