Hello people.
I took it as this option is to make apps that are stored in /system/app gain root access without asking for confirmation. However, the apps that I have moved to /system/app folder still ask for root access nonetheless. Isn't it the system apps that is meant by "system user" in this description?
Its a mode that will always trust the superuser. this mode can be dangerous, since it hides all root privilege pop-ups and assumes an affirmative*
Related
Or what is the exact mechanism behind this in Android? I have been using GNU/Linux for many years so I understand the original concept and would not want every app to have root privileges.
The Superuser app allows you to accept & deny all root apps. You can also choose to always allow certain apps, but you don't have to.
I don't quite understand this. Who gives the apps the privileges. I suppose the Superuser app is only the frontend for some system service. And does it work as a white list or as a black list. Meaning: Does every app get root priviliges by default on a rooted phone or do I have to manually give root privileges to desired apps but the rest doesn't even realize it's on a rooted phone.
By default, apps are denied root privileges. If I restore an app that runs as root in the background -along with its data - the app won't work until I launch it & grant it superuser permissions. Droidwall is a good example of this. Droidwall works by denying or allowing 3g and/or wifi access to apps based on your input. It does this by changing the iptables. If I flash a new ROM & restore with Titanium Backup, I usually forget that Droidwall isn't doing its job until I notice ads in an app that isn't supposed to connect. Once the app is launched & I choose to apply the rules, Superuser prompts me to allow the changes. If I do not make a choice within 10 seconds, SU automatically denies the root request.
In short, an app will never run as root (aside from superuser itself, if that counts) without you first allowing it. Also be aware that most everyday apps will never ask for root access as they don't need it to run. Only apps that are making changes to the system (reading or writing) will need root access. As far as accessing your contact data & other stuff you may worry about, any app can do that if it has permission (not root) to do so. When you first install an app, you will see a list of permissions - usually an app needs those permissions to run and there's nothing to worry about.
OK, thanks I understand it more now. What would happen if I didn't install Superuser. Is there a built in daemon for superuser privileges?
Don't fight the powers that be. Install superuser. You need it.
I'm pretty sure you'll get error messages from most root apps. I could be wrong, though. Next time I'm about to flash a new ROM, I'll remove Superuser after I do my backup, just because I'm curious. I'm pretty sure that Superuser or an alternative - if one exists - is necessary. I know the ability is there in the os, but I would think that it would need some kind of vehicle (such as an app) to relay the information. I certainly hope apps wouldn't automatically be granted root privileges, but I'm not sure. It's an interesting question, though.
Roms come pre-loaded with Superuser, and any auto-root method does as well. You would only be without it if you root manually, stay on stock, and choose not to push the app. Or, I guess, if you choose to remove it.
Hey guys,
This is the wrong place forum, but I like you guys, so I will ask you a question
Say there is an app that requires root (in this case Cisco AnyConnect rooted version), but I do not want to have root access enabled from within Android OS. Is there a way to install the app with automatic root access? E.g. by flashing it from within the recovery?
Thanks,
Su
Do it need root access or system permissions ?
If it needs root, you must have "su" in android OS.
If it needs system permisssions, you could push it in /system/app/ or /system/priv-app/ (more access than /system/app/)
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Sumanji said:
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Click to expand...
Click to collapse
every app that wants SU permission should be prompting you the first time to allow or deny it.
if any app gets SU permission without you allowing it, something is wrong.
what i dont understand is, you said the phone is NOT rooted, then mentioned cm11. if you are running cm11, your phone is already rooted.
Hi
I recently rooted my phone and started using a few "root only" apps.
When I look at app permissions and let's say it example says that it can access "Phone" and "Other". By other it means root.
Does that actually gives it permission to anything? So if I accept the permissions "Phone" and "Other" it can actually access my camera too (just an example) or do I understand the root access wrong?
Thanks in advance
what i understand if an apps ask for a root permission, the apps will ask for the permission to read/write in a secure area, eg : /data, /etc
It is different from the permission of using camera, message, etc like when we install apps from playstore.
dubay.yabud said:
what i understand if an apps ask for a root permission, the apps will ask for the permission to read/write in a secure area, eg : /data, /etc
It is different from the permission of using camera, message, etc like when we install apps from playstore.
Click to expand...
Click to collapse
Thanks. Was what I was curious about. As I understood root, as the app could do whatever it wanted to.
No. It is not as you think. By allowing an app root permission, it means you're allowing it to do more than controlling limited applications. It can do more than that. And dont worry it wont damage your phone because everything has its limit but yeah be careful of what you're doing as sometimes you can risk your phone if you(not by allowing an app root permissions) but by using it after giving it root permission. So be careful and know what you're doing.
Please press the thanks button if you think I helped
In our project we "lock down" the device and let only our homescreen app running.
therefore we remove all unnecessary apps, and wondering if we can remove superuser or supersu.apk
of course we need root rights, but we dont need the controlling app
we have tested it on many devices, there are a lot where we could remove supersu.akp and our app kept the root right, but on many other devices we lost the root when we removed it
is there anything we have to handle before we remove it, or how does it work?
thanks,
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
ИΘΘK¡€ said:
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
Click to expand...
Click to collapse
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
oisiss said:
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
Click to expand...
Click to collapse
Please notice how I phrased it like this:
NOOKIE said:
...root is dependent on whether or not there are the su binaries existent in /system/bin (among other things).
Click to expand...
Click to collapse
I am fully aware that root is not as simple as su being in /system/bin. :silly:
oisiss said:
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
Click to expand...
Click to collapse
Yes, this sounds right. :good:
some apps have root detect,most of the checks can be disabled by Xprivacy.
but they still check for the /system/xbin folder to recognize if the device had been rooted or not.
so,as the title,i'd like to know if there is any solution to prevent the apps from accessing the folder.
(now i can use them by set the folder's permission to 0750 rwxr-x---,but i have to launch supersu to correct the permission again after using the apps that will check root)
any suggestion is welcome and thanks for the idea