SuperSU requires a rooted device!!! SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. In bestimmten Fällen kann es sinnvoll sein, den Zustand des gerooteten Smartphones vor diversen Apps zu verstecken. Ich persönlich hatte. allsportsreplaygunnison.com › Anleitungen › Firmware & OS.
Root-Zugriff unter Android mit Hide-Superuser von Chainfire versteckenViel Spaß mit Millionen aktueller Android-Apps, Spielen, Musik, Filmen, Serien, Büchern und Zeitschriften – jederzeit, überall und auf allen deinen Geräten. Der für die Entwicklung zahlreicher Root-Apps wie SuperSU verantwortliche Programmierer Chainfire zieht sich zurück. Die App für die Vergabe. Einerseits versteht Chainfire darunter, dass das su-Binary nicht in die Partition /system installiert werden muss. Andererseits ist die neue Methode.
Superuser Chainfire SuperSU App 2.82 Update Video How To Fix: \ Kennwort vergessen? IN-APP PURCHASES These are completely optional and more like donations. Elektroauto von Apple: Hyundai ist Fauda Besetzung in Mobilität.
Threaded instance you manage, retrieve an instance from the pool, proxies the call to that instance's run Sound complex? Maybe, but it all comes together so you can sprinkle Shell.
All of this without you ever having to worry about managing the instances, and only having to catch a single Shell. It is assumed all the code following is run from a background thread, such as Thread , AsyncTask , or Job IntentService.
When running multiple commands in quick succession, it is slightly cheaper to get an instance and close it when done, and using the returned instance.
But keep in mind if there is a longer period between your calls, and another thread wants to call su, the shell you have not close 'd yet cannot be reused by that thread:.
Threaded::ac , which casts the instance to a Shell. ThreadedAutoCloseable :. Please note that all methods that may be problematic on the UI thread have been marked as WorkerThread.
Some of these methods can be called from the UI thread without issue in specific conditions. If so, those conditions should be noted in the method's javadoc.
Skip to content. Example code for "How-To SU" su. Code Issues Pull requests Actions Projects Wiki Security Insights.
HTTPS GitHub CLI. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again.
Go back. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio If nothing happens, download the GitHub extension for Visual Studio and try again.
Latest commit. Chainfire Update README. Update README. Git stats commits. Failed to load latest commit information.
Enable basic GitHub Actions CI. Apr 10, Update Gradle Wrapper to 5. Feb 28, Do not fail with no local. Remove Eclipse leftover.
Add Apache LICENSE file. Oct 29, Dec 23, Update gradle plugin again. Update Gradle build files. Oct 24, View code.
Deprecated This library is not under active development right now, as I've mostly moved away from the Android world. Upgrading from v1. Example project The example project is very old, and does not follow current best practises.
Basics This page is not intended as a full reference, just to get you started off. Some of the below may seem out-of-order, you might want to read this entire section twice.
Blocking, threads, and ShellOnMainThreadException Running subprocesses is expensive and timings cannot be predicted. Didn't make sense? Don't worry about it, and just follow the advice and examples below Shell.
Interactive vs Shell. Threaded Shell. Common methods Examples follow further below, which make use of pooling.
Common methods: addCommand Common methods: run Pooling The Shell. Examples It is assumed all the code following is run from a background thread, such as Thread , AsyncTask , or Job IntentService.
Annotations Nullity and thread annotations have recently been added. About Example code for "How-To SU" su.
Releases 2 tags. Packages 0 No packages published. Contributors Terms Privacy Security Status Docs Contact GitHub Pricing API Training Blog About.
In this case, you might just want to add all permissions of class dir and as you would later discover, file as well. But how do you find these?
In the end, these are the policies being applied by StickMount :. All parameters may be collections, aside from the permission-class parameter.
It is highly unlikely you will ever need any statement other than allow for anything other than testing purposes. That being said, should you come up with a valid reason to use any of these, then it is still advised to only use the statements that relax security allow , permissive , attradd rather than further enforce it deny , enforcing , attrdel.
With the latter, you may inadvertently break other root apps running on the device. SELinux denies by default, and only allow s what you explicitly state should be allowed.
Many of the source statements use collections that are ultimately expanded to a large set of rules. The neverallow statement just makes sure that if a certain allow statement exists, it is removed.
The neverallow statement is not stored or applied in the resulting policy file. There's no need to counter these other than allow ing whatever your app needs.
All the files you need are in the latest SuperSU flashable ZIP. The latest 'stable' build can always be retrieved from my server , for the latest 'beta' release you need to check the beta thread in the SuperSU forums.
This is not a binary as the name suggests, but a shell script, and the standard update ZIP's updater-script file is just a dummy. This script has comments which document which files go where on which API level, and what their file permissions, ownerhips, and security labels must be.
If you have done this exactly right, SuperSU will not complain when you open the app after booting. It is non-trivial to include SuperSU exactly right on your own.
It is therefore often easiest to include the latest SuperSU ZIP inside your own flashable ZIP, and chain its installation. An example ZIP can be downloaded here , which installs SuperSU v2.
Additionally, you should see the section about the supolicy tool , as it describes which properties are set and which scripts are called after SuperSU is done patching policies, and root calls are from the unrestricted init context.
Over the past years, many exploits have installed SuperSU as their means of persistent root. Often the exploit leaves the system in an unstable state, and a proper and lengthy installation may not be possible.
The APK can fix a partial install as long as basic root works. At the time of this writing, that means at least these files need to be present, and for the right architecture and amount of bits for the firmware see the ZIP script for permissions and API levels :.
Furthermore, daemonsu --auto-daemon needs to be launched somehow on boot. This is generally done via install-recovery. Alternatively, you can include the ZIP and run SuperSU's installation script.
For this to work, at the time of this writing, the following commands need to be available on the PATH:.
Additionally, sh needs test support [ ] square brackets work in if statements. Aside from unzip , all of these should be present on a fully booted 4.
If not, you can provide a SELinux capable toolbox or busybox and symlink these commands somewhere on the PATH.
If all of these dependencies are met, you can install the ZIP as follows:. Due to the script trying things in various ways to support different systems and recovery versions, it will throw errors at you regardless of if the installation is succesfull or not.
Just ignore those, reboot, and see if the SuperSU GUI complains when you open it. On December 17 , [libsuperuser GitHub] has been updated with Gobblers to consume STDOUT and STDERR.
These are nothing more than background threads that consume STDOUT and STDERR output as fast as possible.
The exact how and why is a long story if interested, read [When Runtime. If you are using my library please make sure you are running the latest version.
If you're not running my library it may be wise to read the linked article and see if there is a problem with your code.
SuperSU has a feature to log all su command content. While this works fine for most apps, some apps can run into unexpected problems when this feature is used.
One example is terminal emulators - these will not show the command prompt if a su shell is started. SuperSU v0. If you use this method, SuperSU will not enable full content logging for your app if SuperSU has only been configured to log by default.
If the user goes into app-specific configuration, the user can still enable full content logging for your app manually.
The user will in that case be presented with a warning. To let SuperSU know your app is not fully compatible with full content logging, add the following to an Activity , Service , or BroadcastReceiver :.
Adding it to a single Activity , Service , or BroadcastReceiver , is enough to get the entire package excluded from full content logging.
There is no need to add it multiple times. Please note that I will not tolerate abuse of this feature. Full content logging is there for the end-user, and it should not be disabled this way without good reason.
I may resort to blacklisting your package from root access altogether if you purposely abuse this. As far as I know, since SuperSU v1.
As such, this section may be obsolete. SuperSU originally took its parameter parsing from ChainsDD's Superuser's su binary.
On January 11 modifications regarding parameter parsing were pushed to ChainsDD's GitHub [fcfab2 GitHub]. SuperSU has virtually identical updated parameter parsing from v1.
While this does allow for some interesting constructs in calling su , you must be aware that not all constructs possible with the original parameter parsing will be interpreted in the same way with the new parameter parsing.
I would also like to point out specifically that 1 the command to execute, following the -c or --command parameter, should be a single parameter , 2 that parameter is not even supported by all su variants available in the wild, and 3 the most reliable way to execute commands as root still remains starting su as a shell and piping commands and output.
Some su variants on some devices do not support anything else than being started as an interactive shell. Exact parameter parsing of the more functional su binaries differs by author and by version, sometimes very subtly.
The older the version of Android your app can run on, the higher the chance of running into an exotic or incompatible su binary.
You'd be surprised what your app can run into in the wild. As such, in my personal opinion, it is always wisest and most compatible to simply run su as an interactive shell and pipe commands and output.
If you must deviate from this, you should at least thoroughly test your app with 1 the most recent Superuser, 2 a Superuser and binary from , 3 SuperSU v0.
Due to changes in Android 5. From SuperSU version 1. All root apps should from now on declare this permission in their AndroidManifest.
If this permission is not present, SuperSU will present a warning in its superuser request popup this is configurable in SuperSU settings.
At the time of this writing this permission is not enforced, but it is expected that sometime in the future it will be, and apps requesting root that do not have this permission set will be silently denied.
If this permission is declared, the user will be able to see in the app permissions list that the app requests superuser access. SuperSU v2. This protection is used in many security-related dialogs in Android.
What it comes down to is that the popup will not react to input of it is obscured by any other activity, view, overlay, etc.
This prevents a malicious app from displaying a touch-transparent image on top of the popup that would for example switch around the accept and deny buttons.
There are however some legitimate uses for overlays, a common use for them is to adjust display colors. An app displaying such overlays should hide the overlay when the SuperSU popup becomes visible, and show it again.
To facilitate this, SuperSU will send a broadcast to apps that have previously been granted root access. The following BroadcastReceiver can be used to receive information on when to hide overlays.
See [libsuperuser :: HideOverlaysReceiver. Both the directories and the containing scripts and binaries should be chmod As the scripts are run serially, if your script does not need to delay the boot process, the script itself should make sure its actions are run asynchronously.
For example:. The parenthesis cause a sub-process to be created that runs the commands inside them. This allows all the other scripts in su.
How-To SU Guidelines for problem-free su usage for Android Developers. Introduction Since I started writing SuperSU, I have run into a lot of implementation problems.
How to call su 3. Common pitfalls Runtime. Making the call A common method to call su that avoids the known issues listed above is by creating an interactive shell and piping commands to it.
Checking for su availability There are many ways to check whether or not superuser access is available. Checking for su version While this is not something most root apps need to do, and not all su binaries even support this, this might be something you want to do.
Mount namespaces When SuperSU versions 1. When to call su 4. When not to call su The main thread Do not call su when running on the main application thread.
Detecting the main thread Detecting if your code is running on the main thread is generally done as follows: if Looper. Using AsyncTask The AsyncTask class is often used to perform quick and easy background processing for relatively short operations.
Using IntentService While AsyncTask is a very useful class you will no doubt often employ, sometimes it's just not the right tool for the job. What this means for you As a root app developer, you need to learn how to deal with SELinux.
Detecting SELinux While it is probably wise to make sure your code runs regardless of SELinux presence or mode, sometimes you will need to detect if SELinux is present and set to enforcing.
Contexts 5. Basics The current SELinux context defines which security policies apply to your process. Why switch contexts? How to switch contexts There are several ways to switch contexts.
When to switch contexts Context switching is a complicated process, and I advise to use it sparingly. This is only needed in select circumstances: when you are piping commands to the su shell, and you send the next command before waiting for the result of the previous command.
Filesystem and socket contexts Previous mentions of context switching have applied to processes. By far most root app developers should never need to access any of these manually.
Ok I Agree Learn More. Download APK 5. Using APKPure App to upgrade SuperSU , fast, free and save your internet data. The description of SuperSU App 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.
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.
IN-APP PURCHASES These are completely optional and more like donations.
Nie Genug - SuperSU 2.82 AktualisierenDu kannst auch als Gast kommentieren Anleitung. The central CF-Auto-Root thread can be found here on allsportsreplaygunnison.com that thread for requests for new roots and generic discussion. Most device models have their own dedicated threads on XDA, please keep discussion about those specific models in that dedicated thread, and don't litter the central thread with them. Example code for "How-To SU". Contribute to Chainfire/libsuperuser development by creating an account on GitHub. Live wallpaper and daydream displaying the latest and greatest imagery from allsportsreplaygunnison.com, highly configurable. SuperSU Zip gives you complete access and control on your Android device. you can keep the track of all the rooted granted apps from SuperSu Zip. SuperSU comes into existence by chainfire. Developers launched the apps that manage all the action of the Superuser that access has complete right on the apps of your device. Hi! I'm a software developer and amateur photographer. I'm best known for the Android apps I've released over the years under the Chainfire name, but I've been involved with many other projects as well. Random thoughts can be found on Twitter, probably the place where I'm most active these days. Technische Details. Paketname. allsportsreplaygunnison.comu. Lizenz. Kostenlos. Betriebssystem. Android. Anforderungen. Android oder höher notwendig. Kategorie. Viel Spaß mit Millionen aktueller Android-Apps, Spielen, Musik, Filmen, Serien, Büchern und Zeitschriften – jederzeit, überall und auf allen deinen Geräten. SuperSU requires a rooted device!!! SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. Der für die Entwicklung zahlreicher Root-Apps wie SuperSU verantwortliche Programmierer Chainfire zieht sich zurück. Die App für die Vergabe.