Version: 2.82-SR2 (282)
Package: eu.chainfire.supersu
6.06 MB (6,352,734 bytes)
Min: Android 2.3 (Gingerbread, API 9)
Target: Android 5.0 (Lollipop, API 21)
Uploaded August 12, 2017 at 11:33PM UTC by Ricardo
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.

APK Notes:

SuperSU v2.82 SR2 released

This update to SuperSU brings SBIN mode (details below) and various fixes to Pixel support. The latter patches have been available as a test version on XDA ('PixelFix') for some time now.

SBIN mode
Traditionally, SuperSU's systemless mode used an ext4 image (/data/su.img) that was mounted to the /su path. It was done this way to bypass some root restrictions (mostly Samsung's).

SBIN mode stores its files directly on the /data partition, and makes su available through /sbin. The forementioned root protections have now been circumvented in other ways.

For most root apps, this really shouldn't make any difference. Some very specific ones (like FlashFire) will need to be updated to cope. Apps that need access to SuperSU specific files and paths should refer to /sbin/supersu and /sbin/supersu_link, rather than finding the files on /data manually.

SBIN mode is the default mode for Android O and newer, but is supported on Nougat and Marshmallow as well. To enable it on N and M, you need to execute the following command in ADB shell before (re-)flashing the SuperSU ZIP:

echo "BINDSBIN=true">/data/.supersu

Users are encouraged to try it on N and M as well as O, and report any issues they may encounter to the BETA thread on XDA. Upcoming SuperSU features will require SBIN mode.

As with all SR releases, you are supposed to update them by flashing the ZIP, not by installing the APK.

Flashable ZIP:

BETA discussion thread on XDA:

Pixel (XL) users, I advise to 'fastboot boot' this modded TWRP to flash the ZIP:

- ZIP: Support order-swapped /etc/recovery.fstab
- ZIP: Cope with /system being a symlink to /system_root/system
- suinit: Fix remount /system r/w issue on Pixel(XL)+OPreview
- sukernel: Fix pre-patched ramdisk detection for reduced system_root footprint
- ZIP+suinit: Fix recovery going to ramdump on Pixel(XL)
- Added "BIND SBIN" mode, mounts files in /sbin instead of /su, stores files directly in /data instead of su.img (new default for O+)
- Systemless: all file contexts are restored at boot, see /path/to/su/mount/file_contexts
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

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.

These are completely optional and more like donations. They do not unlock any functionality.
Contact us:
Website :
All versions
August 13, 2017
May 29, 2017
May 25, 2017
May 24, 2017
March 23, 2017
January 14, 2017
January 3, 2017
December 22, 2016