After rooting your Samsung Galaxy S5, you will need a root management app that organizes the root access granting process. The most powerful, user friendly and easiest app of these apps is SuperUser. The app is responsible of giving you the control over apps that require root access. It prompts you whenever an app tries to access root files, and asks you whether to grant the app this permission or to deny it from gaining the access. It works as a doorman; no one gets in my root unless I am told first and agree.
Is it safe?
Well, it is as safe as it can get. The app literally works as a guard; no root access is given to any app without your permission. You can also deny the root access to any app, even if you have granted it to it before. SuperUser is your net when you walk on the ropes, rooting is somehow dangerous due to all malicious apps out there, so if any app got installed with a bundle or something and it ties to gain root access, SuperUser will alert you that a certain app is trying to access root. Then it is up to you to do it or not.
How it works?
When you learn how to root S5, almost every rooting method installs the SuperUser app by default. Without it; there will be no way for you to control which app gets the root access. SuperUser is like the su in Linux operating systems, as android OS is based on Linux kernel. The su –stands for super user-, is the account or the privilege that the administrator use to access the core files of the OS. On android, it consists of 2 parts; the SuperUser apk file and the su binary. The SuperUser apk file is installed on your Galaxy S5 like any other app, and it gives you the ability to have a friendly interface to manage your root apps. Use the SuperUser app to grand or deny root access to whatever app you want, also you’ll find a log section to track apps’ su usage. The su binary is what apps itself use whenever they need SuperUser permissions. The su binary then checks with the SuperUser app’s database, to see if you have already granted the root access to the app. If you haven’t, then it prompts the SuperUser app to display a message on behalf of the root app to ask for the permission.
Why would I need it?
As we mentioned, you need the SuperUser to grant root access to the apps that need to go deep into the core files to operate. But the question is, if my phone is already rooted and any app can get the root access whenever it wants; why would I want to bother knowing? Actually it is a good question, sometimes apps get installed by mistake or as a bundle with other apps. Some of these apps may be malicious or malware or even a virus, it can use your information or hack into whatever account you are using on your phone; including finances of course. Here is what SuperUser is all about; just letting you know that a certain app needs root access. If you have installed the app yourself then no problem, grant the access no questions asked. If you haven’t installed the app and you know nothing about it, then you are indirectly alerted and you can uninstall it.
What apps would need root access?
Now to the fun part, knowing which apps need your root access is just another way to learn how to root Samsung Galaxy S5. Whenever an app asks for root access, it uses it to be able to reach system’s core files or to control any hardware of your device. For example, some battery saver apps ask for root access so they can reduce the clock speed of your device’s processor when the screen is off. Non-rooted devices can’t give such permission to the app, affecting your ability to save more juice. Another example is backup apps, without root access; the app can only backup the apk file of your application. What if you want to backup the data as well?? If this app is a game, then you don’t want to lose your progress when you transfer the application to another device. You can do this if your device is rooted and of course have the SuperUser installed.
To make a long story short, rooting Galaxy S5 and having SuperUser are inseparable. To survive having root access with minimal risk and problems; make sure to have SuperUser on the device.