Version: 2.72 (272)
Package: eu.chainfire.supersu
6,231 downloads
6.02 MB (6,311,718 bytes)
Min: Android 2.1 (Eclair, API 7)
Target: Android 5.0 (Lollipop, API 21)
nodpi
Uploaded May 10, 2016 at 7:57PM UTC by Displax
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.72 BETA released

This is a relatively minor update. Support for the patching ChromeOS-wrapped Android boot images has been added (Pixel C), some logcat and fsck issues were fixed in the SELinux policy, and some flags have been added to the ZIP installer.

Force encrypt

Some recent devices do not get a signal - for reasons yet unknown - unless /data is encrypted. The SuperSU ZIP installer by default removes the forceencrypt flag from fstab, so you can run your device unencrypted if you want to. In some cases this may cause you to run unencrypted while you want to be running encrypted, such as on these recent devices. That is what the KEEPFORCEENCRYPT flag is for.

I am open to debate (in the BETA thread on XDA) as to whether the situation should be switched around, keeping the forceencrypt flag enabled by default, and have removing it be the case that requires extra action. It seems to me like those who want to run decrypted may be the more advanced users as well as the minority.

To clarify: the situation right now is still the same as in 2.71, there is now just the option to change the behavior. The point of discussion is whether that option should become the default in the future.

Compatibility

Not a day goes by since the release of 2.69 - sometimes not even an hour, or a full page in the thread - that somebody doesn't complain or ask about ES File Explorer or Secure Settings or whatever root app not getting root.

I want to emphasize again that these are bad apps that are hardcoding the path to the su binary. This has always been a bad idea and I have been warning against it since 2012.

In the early days of systemless root a compatibility mode hack was enabled by default, but this has been disabled since 2.69. It will not come back, because it's a bit of a dirty hack, and I'm not going to keep forcing millions upon millions of users running that hack just for a handful of outdated apps to work.

You can manually re-enable that compatibility mode by setting the BINDSYSTEMXBIN flag before re-flashing SuperSU, see forum.xda-developers.com/showpost.php?p=66140836&postcount=5493

I suggest writing the authors of these apps to inform them that their apps will no longer work with SuperSU on Marshmallow by default, and ask them to fix their code. Said fix is generally one line or less, so there really isn't much of an excuse to not just fix it.

Links

ZIP: download.chainfire.eu/supersu-beta

SuperSU BETA thread on XDA: forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

SuperSU subforum on XDA: forum.xda-developers.com/apps/supersu

Changelogs
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
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:

http://forum.xda-developers.com/showthread.php?t=1538053


SUPERUSER
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.


NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.

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.


TRANSLATIONS
Want to help translate SuperSU ? See http://www.getlocalization.com/supersu/ !

IN-APP PURCHASES
These are completely optional and more like donations. They do not unlock any functionality.
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
Comments