[Balatan]

SuperSU v2.62.3 beta (Flash)
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

2015.12.11 v2.62-3 BETA:
--- (systemless) ZIP: Fix calling wrong script name for custom patcher script
--- (systemless) ZIP: Improve APK overwrite
--- (systemless) ZIP: Do not move backups from /cache to /data, just copy them
(there are no changes to SuperSU itself compared to v2.62, just minor script changes in the ZIP)


IMPORTANT NOTICE:

Continuing on the previous post, here is SuperSU v2.62 BETA, with automated boot image patching. It's been tested by myself on various Samsung's running anything from 4.3 to 5.1, and all of the recent Nexus devices on 6.0. Even on CM13. Other users have tested it with success on various other devices.

If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.

If you are coming from a SuperSU 2.56 system-less install, you must re-flash the stock boot image prior to installing this.

If you are coming from a SuperSU 2.60 system-less install, or were not rooted at all, then you can just flash the ZIP without any special prior instructions.

If TWRP offers you to keep /system read-only, indeed keep it read-only.

If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!

If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image. The boot image patcher currently only supports gzip compressed ramdisks and the standard Android boot image format. Some devices do not use the standard format, and many custom kernels use a compression other than gzip. A backup is made (/data/stock_boot_<sha>.img.gz) of the original boot image before patching it.

Further implementation details (including an updated list of changes to the ramdisk) are explained in the installer script itself, as usual.

Some things of note with 2.62:

A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system. Removing /su/xbin_bind and rebooting will disable this feature, or "echo BINDSYSTEMXBIN=false>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash.
If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not.

Dont ask for supersu PRO Version it has nothing to do with you.
Only need app which grants root permission thats all ,it has no ads at all so NEVER ask for supersu pro either purchase it and also there is option in the to enable pro features without paying so this is unnecessary

This app has no advertisements

More Info:

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

Download Instructions:
Flash Recovery zip:
https://revclouds.com/2q8tu14pk5z5

Mirrors:
(Closed Filehost) http://uploads.to/1bjtto3ixx7o
https://dailyuploads.net/hjxmmjfmubrw
(Closed Filehost) https://unlimitzone.com/9evson3ewf5q
(Closed Filehost) https://ul.to/zsget4g2