Database Info

[Q] Q: Perm/Temp roor & S-OFF - security concerns.

I spent much time searching, but fail to find answer to these questions:
1.- In an device with S-OFF: - can other than SuperUser apps touch any system data ?
2.- if an device is temp-rooted, then only SU-apps* can touch S-OFF'ed data areas ?
(by "su-apps" i mean apps that got granted "superuser" rights by "superuser" app)
3.- Visionary can temp root on each boot, or perm root - what's the difference ?
4.- does perm-root grant full rights to every application ? (so that any app can read any part of data it wants anytime ?)
5.-provided that I use S-OFF and temproot, - what secutity risks did I enable, provided that I trust the few applications that I allow to run as superuser ?
Thanks.

bump - anyone knows ?

AlCapone said:
I spent much time searching, but fail to find answer to these questions:
1.- In an device with S-OFF: - can other than SuperUser apps touch any system data ?
2.- if an device is temp-rooted, then only SU-apps* can touch S-OFF'ed data areas ?
(by "su-apps" i mean apps that got granted "superuser" rights by "superuser" app)
3.- Visionary can temp root on each boot, or perm root - what's the difference ?
4.- does perm-root grant full rights to every application ? (so that any app can read any part of data it wants anytime ?)
5.-provided that I use S-OFF and temproot, - what secutity risks did I enable, provided that I trust the few applications that I allow to run as superuser ?
Thanks.
Click to expand...
Click to collapse
Perm.Root, Basically Only Allows You To Have Root Access After A Reboot, Compared To Temp.Root, Which Requires The User To ReRoot After Every Reboot!!
No Matter Temp.Root or Perm.Root, You Still Have To Grant Which Ever App SU Permissions, For It To Run!!
Install "Lookout Security" If Your Sceptical Of A Certain App!!
Hope This Helps!!
Sent from my HERO200 using XDA App

Thanks.
PMGRANDS said:
Perm.Root, Basically Only Allows You To Have Root Access After A Reboot, Compared To Temp.Root, Which Requires The User To ReRoot After Every Reboot!!
Click to expand...
Click to collapse
Makes sense, but why does f.eks visionary have option to "temp root on each boot" ? - something is supposed to be different.

[Q] Do all applications get root priviliges on a rooted android phone?

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.

Giving su rights to an app on a not rooted device

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.

[Q] Looking for a way to make an app think a device is not rooted

I have a certain app that I need to use that will not run on a rooted device. My root app is SuperSU, and by disabling superuser in the settings the app will run, but I can't make it work without disabling it. It doesn't even give me a prompt to ask for root permission - the app must just be looking somewhere for the su binary or something.
Is there a way to make an app think that a device is unrooted without disabling root access?

mewmew! said:
I have a certain app that I need to use that will not run on a rooted device. My root app is SuperSU, and by disabling superuser in the settings the app will run, but I can't make it work without disabling it. It doesn't even give me a prompt to ask for root permission - the app must just be looking somewhere for the su binary or something.
Is there a way to make an app think that a device is unrooted without disabling root access?
Click to expand...
Click to collapse
Xposed framework with Root Cloak module. It doesn't always work, but it often does, so give that a try.

Can you give permissions (via adb) to a terminal app?

Hey all, long time no see. Anyways, I'd like to be able to do quite a few adb commands without actually using adb here locally on the device. So I was curious and started thinking, could you use adb to grant a terminal emulator app (i.e. Termux, the one I use) permissions such as DUMP and WRITE_SECURE_SETTINGS, or whatever else it may need to perform certain commands like clear cache and install apps. I obviously don't have root (Dag on US Carriers). Maybe I don't have a great understanding of what these permissions do? Any help is appreciated.
Unfortunately you cannot just pop into adb and try to give the app the permission, as termux doesn't request it. Termux:API does not as well. I saw somewhere over on Github some guy edited the source of Termux:API and added more APIs to use, I just don't know how to compile an app from source)
Thanks,
Gavin

Craz Basics said:
Hey all, long time no see. Anyways, I'd like to be able to do quite a few adb commands without actually using adb here locally on the device. So I was curious and started thinking, could you use adb to grant a terminal emulator app (i.e. Termux, the one I use) permissions such as DUMP and WRITE_SECURE_SETTINGS, or whatever else it may need to perform certain commands like clear cache and install apps. I obviously don't have root (Dag on US Carriers). Maybe I don't have a great understanding of what these permissions do? Any help is appreciated.
Unfortunately you cannot just pop into adb and try to give the app the permission, as termux doesn't request it. Termux:API does not as well. I saw somewhere over on Github some guy edited the source of Termux:API and added more APIs to use, I just don't know how to compile an app from source)
Thanks,
Gavin
Click to expand...
Click to collapse
Terminal Emulator is the same thing as ADB shell(adb shell, not the normal adb), anything that can be done from PC using ADB shell can also be done using Terminal Emulator app, the commands are the same except the "adb" or "adb shell" part is removed from the command.
For example "adb reboot recovery" would instead be "reboot recovery" or "adb shell dumpstate" would instead be "dumpstate".
Some commands might not work or might need other protocols, parameters or switches added to the command.
But, unfortunately, you can't set Termux or any other app to have access to change or pull anything from system without root, if you don't have root, you're wasting your time. You cant change anything about the system without root unless you have TWRP, it can do whatever it wants to do and the device can't stop it.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Terminal Emulator is the same thing as ADB shell(adb shell, not the normal adb), anything that can be done from PC using ADB shell can also be done using Terminal Emulator app, the commands are the same except the "adb" or "adb shell" part is removed from the command.
For example "adb reboot recovery" would instead be "reboot recovery" or "adb shell dumpstate" would instead be "dumpstate".
Some commands might not work or might need other protocols, parameters or switches added to the command.
But, unfortunately, you can't set Termux or any other app to have access to change or pull anything from system without root, if you don't have root, you're wasting your time. You cant change anything about the system without root unless you have TWRP, it can do whatever it wants to do and the device can't stop it.
Click to expand...
Click to collapse
I understand it's the same thing, and I'm not wanting to change anything related to the system. I'm wanting to do commands such as install apps and clear data. It gives me errors when I try and do this, because I don't have permission. If I am understanding correctly, you can decompile an app, add in the appropriate APIs for the permission, and recompile it. This way you won't get an error when you try to give it a permission (adb shell pm grant com.termux android.permission.WRITE_SECURE_SETTINGS). It tells me the app doesn't request this permission.

Craz Basics said:
I understand it's the same thing, and I'm not wanting to change anything related to the system. I'm wanting to do commands such as install apps and clear data. It gives me errors when I try and do this, because I don't have permission. If I am understanding correctly, you can decompile an app, add in the appropriate APIs for the permission, and recompile it. This way you won't get an error when you try to give it a permission (adb shell pm grant com.termux android.permission.WRITE_SECURE_SETTINGS). It tells me the app doesn't request this permission.
Click to expand...
Click to collapse
If you want the app to be able to access those permissions then you need to push the app to /system to make it a system app, apps outside of system can't access those permissions.
After moving the app to system, boot to recovery and wipe only the cache partition(if you have custom recovery, wipe dalvik cache also), then reboot the device.
But, unfortunately, you aren't rooted so it isn't an option for you, you need to root your device.
But even that won't help, see here:
https://stackoverflow.com/questions...-permission-error-even-when-added-in-manifest
Sent from my LGL84VL using Tapatalk

Droidriven said:
If you want the app to be able to access those permissions then you need to push the app to /system to make it a system app, apps outside of system can't access those permissions.
After moving the app to system, boot to recovery and wipe only the cache partition(if you have custom recovery, wipe dalvik cache also), then reboot the device.
But, unfortunately, you aren't rooted so it isn't an option for you, you need to root your device.
Click to expand...
Click to collapse
Take SystemUI Tuner from the Play Store for example, it requires those permissions to do its thing. It does NOT need to be a system app to utilize them, they just need to be granted manually via adb. Greenify does this as well.
As for root, I would if I could. Verizon Note 9 is locked down like Fort Knox.

Craz Basics said:
Take SystemUI Tuner from the Play Store for example, it requires those permissions to do its thing. It does NOT need to be a system app to utilize them, they just need to be granted manually via adb. Greenify does this as well.
Click to expand...
Click to collapse
Yes, some apps can access that permission, but it's built into the app, it isn't just granted via adb or terminal. Read some of the link that I posted above. As far as I knew, accessing secured settings/permissions required root and/or unlocked bootloader, but, things always change. Granted, over the years, things change and trickier things have to be done get mods and apps to do certain things without root, but it's not quite changing/accessing the system.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Yes, some apps can access that permission, but it's built into the app, it isn't just granted via adb or terminal. Read some of the link that I posted above. As far as I knew, accessing secured settings/permissions required root and/or unlocked bootloader, but, things always change. Granted, over the years, things change and trickier things have to be done get mods and apps to do certain things without root, but it's not quite changing/accessing the system.
Click to expand...
Click to collapse
Just took a look, strange. Greenify and SystemUI Tuner are considered 3rd party, correct? Maybe it's it's something with their signature? (I don't know much about signatures either)
And yes I'm aware you have to add it into the app, the app requests it and you can grant it via adb.
Think my question is answered now anyway, no lol. Thanks for your responses man.