[koumkouat]

SuperSU v2.81 Final
Requirements: 2.1+
Overview: SuperSU is the Superuser access management tool of the future.


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

WHAT'S NEW

V2.80 Bug Fix on installation error and root loss

This app has no advertisements

More Info:

Code: Select allhttps://play.google.com/store/apps/details?id=eu.chainfire.supersu

Download Instructions:
SuperSU v2.81 Final:
https://dailyuploads.net/uhflrp7oetx9

Mirror:
https://drop.download/pebf82nr29dk
(Closed Filehost) https://ul.to/nyuiiw52

SuperSU v2.81 Final Pro key:
https://dailyuploads.net/wo41ry5cdiy8

Mirror:
https://drop.download/xdv5bd12fi1t
(Closed Filehost) http://uploadocean.com/fpn6rjlyiw6d

Recovery Flashable Zip:
https://dailyuploads.net/82m5jbk54m10

Mirror:
https://drop.download/e578qrlxy1mh
(Closed Filehost) https://ul.to/gnjt0qmh

[koumkouat]

Recovery Flashable Zip Ready!

[Shardz]

There have been many reports about v2.80 not installing the binaries properly, and users are saying that root access is lost after attempting to install them. This also happened with v2.79, though with that version they simply would not install, so I ended up flashing the binaries manually through TWRP to get it to work. This current version of v2.81, which is an emergency fix, is also reported to fail with updating the binaries.

The forums at Chainfire are actually down due to excessive traffic from this problem. From what I understand, installing their binaries will not allow you to root your device again in the case this process fails. I purchased SuperSU Pro, and I have not updated the app or the key because of what happened last time with v2.79. It was a real mess, and took some research to fit it. Currently, there doesn't appear to be any fix other than waiting to see how they will deal with this problem. I am personally waiting several days before updating through Google Play because I'm not going through that hassle ever again!

One user in the Google Play reviews said this today regarding v2.81:

"This app used to work like magic but seems the latest update has taken everyone back. Highly irresponsible to release an update without proper testing. Even the latest fix doesn't work. Not able to root again and not able to update binaries as well. Kind of stuck in a deep hole like everyone else. Hours of research and couldn't find anything to fix this. I hope you guys fix the mess you have created ASAP!"

Install this at your own risk, and make sure you have a NANDROID backup in place before you attempt to do so!

Thank you for your support, the same happened to me. I have a S4 mini rooted with SuperSu v2.79 installed. I updated to v2.80 and I lost the root permissions. I had to restart the rooting again (Odin, Rootkit, recovery-clockwork etc).

After that Google PlayStore informed me that a new update was available (v2.80). I gave the OK (with a little pain in the…) and strangely enough everything worked!

[Shardz]

Thank you for your support, the same happened to me. I have a S4 mini rooted with SuperSu v2.79 installed. I updated to v2.80 and I lost the root permissions. I had to restart the rooting again (Odin, Rootkit, recovery-clockwork etc).

After that Google PlayStore informed me that a new update was available (v2.80). I gave the OK (with a little pain in the…) and strangely enough everything worked!

There is now a large amount of reviews on Google Play that are complaining that root is broken with v2.80 - v2.81, and with no way to fix it currently. Out of those reviews, probably three said it was successful, so you are one of the lucky ones. I read that cold booting the device might bring it out of a bootloop and into Android with root after the binary update, but it's not clear if they checked their device with Root Checker or not.

I'm going to steer clear of my retail update until something changes 'cause it's way too scary for my taste. Chainfire was bought out by a third party corporate company, and the problems with this app started about the same time before v2.79. It's really too bad these things happen, but it's a learning experience. I'm glad to hear you got things running okay.

Thank you for your support, the same happened to me. I have a S4 mini rooted with SuperSu v2.79 installed. I updated to v2.80 and I lost the root permissions. I had to restart the rooting again (Odin, Rootkit, recovery-clockwork etc).

After that Google PlayStore informed me that a new update was available (v2.80). I gave the OK (with a little pain in the…) and strangely enough everything worked!

There is now a large amount of reviews on Google Play that are complaining that root is broken with v2.80 - v2.81, and with no way to fix it currently. Out of those reviews, probably three said it was successful, so you are one of the lucky ones. I read that cold booting the device might bring it out of a bootloop and into Android with root after the binary update, but it's not clear if they checked their device with Root Checker or not.

I'm going to steer clear of my retail update until something changes 'cause it's way too scary for my taste. Chainfire was bought out by a third party corporate company, and the problems with this app started about the same time before v2.79. It's really too bad these things happen, but it's a learning experience. I'm glad to hear you got things running okay.

Just follow my guide and all will be fine!
http://forum.mobilism.org/viewtopic.php?p=4498297#4498297

[Shardz]

Just follow my guide and all will be fine!
http://forum.mobilism.org/viewtopic.php?p=4498297#4498297

Thanks for the guide, though those who already updated their binaries will be likely screwed unless they use ADB commands via USB (I could be wrong, however). The only part I'm not clear about is resigning the APK - no clue how to do this.

I wish like hell that Google would allow you to hide specific app updates, but they are obviously more worried about how to make the Play Store UI more white.

[betamaster]

Just follow my guide and all will be fine!
http://forum.mobilism.org/viewtopic.php?p=4498297#4498297

Thanks for the guide, though those who already updated their binaries will be likely screwed unless they use ADB commands via USB (I could be wrong, however). The only part I'm not clear about is resigning the APK - no clue how to do this.

I wish like hell that Google would allow you to hide specific app updates, but they are obviously more worried about how to make the Play Store UI more white.

+1

The only part I'm not clear about is resigning the APK - no clue how to do this.

Install ZipSigner. It can sign zip/apk/jar.

Glad I didn't update

I just installed 2.80 and 81 too. Nothing hpnd all fine

permissions in v2.81 :
wake_lock
receive_boot_completed
get_tasks
system_alert_window
reboot
internet
read_phone_state
access_fine_location
access_wifi_state
access_network_state
write_external_storage
read_external_storage

compared to v2.79 :
wake_lock
receive_boot_completed
get_tasks
system_alert_window
reboot

[Shardz]

Install ZipSigner. It can sign zip/apk/jar.

Hey, thanks for the tip! This is great to know.

Glad I didn't update

Me, too! Normally I would have updated without thinking, but I got smart after the v2.79 fiasco.

permissions in v2.81 :
wake_lock
receive_boot_completed
get_tasks
system_alert_window
reboot
internet
read_phone_state
access_fine_location
access_wifi_state
access_network_state
write_external_storage
read_external_storage

compared to v2.79 :
wake_lock
receive_boot_completed
get_tasks
system_alert_window
reboot

Yes, I read complaints about users freaking out over the new expanded access. That's a really crazy list there once you think about it. One user mentioned on Google that this company actually sends your information to China through these routines. I'm really sorry that I just didn't install the Clockwork manager and stayed away from this thing altogether. Now this app is acting like Kingroot or something similar with privacy issues. :/

[betamaster]

The only part I'm not clear about is resigning the APK - no clue how to do this.

Install ZipSigner. It can sign zip/apk/jar.

Any Windows Commandline version as I m skeptical to trust APK's after Fiasco of SuperSu..

Any Windows Commandline version as I m skeptical to trust APK's after Fiasco of SuperSu..

Here is some guide for that:

https://stackoverflow.com/questions/10930331/how-to-sign-an-already-compiled-apk