Hi There, does rooting and unrooting affect phone's performance ? what if I root my S6 and unroot it (let's assume that I repeat this 4-5 times ) will it affect ? please let me know.
Bhargav Hegde said:
Hi There, does rooting and unrooting affect phone's performance ? what if I root my S6 and unroot it (let's assume that I repeat this 4-5 times ) will it affect ? please let me know.
Click to expand...
Click to collapse
No, it shouldn't affect the phone performance. However you can install apps with root that can affect your system (as root you will have and give your apps permission to change and even damage the phone OS), in any case a simple restore would fix any malicious app.
So while root is safe, make sure you just give root privileges to apps you trust, malicious software can use this privileges for bad purposes.
Root - A SuperUser with all rights and permissions (or an administrator)
Rooting - A process of getting those SuperUser (or administrative) rights and permissions
Unrooting - Giving up SuperUser rights and permissions
As you might have figured - rooting in itself will not affect performance or security of a device; what you do after acquiring those rights and permission will affect performance and security of the device.
You can root unroot a thousand times if it pleases you; the process itself will not damage the device; ofcourse, as long as you read and follow the process properly and as directed by the author.
Related
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.
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.
Hello,
I've seen alot of threads about the exynos exploit and also available fixes, but i have a question i couldnt find the answer to.
my device is not rooted yet, If I root my Note 10.1 (Jellybean 4.1.1 Stock UK rom) using anyone of the methods available, and get SuperSU or Superuser on my tablet, will the exploit still be there?
so if I have SuperSU or Superuser the exploit wont exist because any app trying to get root access will need my permission to do so?
so basically the question is, if I am rooted, is the exploit still a problem (do i still need to install the fix)
Regards to all,,,,,thanks
The exploit has nothing to do with a rooted/non-rooted device.
The exploit allows any app (without aquiring root permissions) to write into any part of the memory by the samsung camera driver and by that getting root permissions. The system will not notify that and thus, a request to allow it will not occur.
To fix this, the faulty memory driver used by the camera needs to be fixed. Chainfire published a fix which might turn the camera unuseable.
akxak said:
The exploit has nothing to do with a rooted/non-rooted device.
The exploit allows any app (without aquiring root permissions) to write into any part of the memory by the samsung camera driver and by that getting root permissions. The system will not notify that and thus, a request to allow it will not occur.
To fix this, the faulty memory driver used by the camera needs to be fixed. Chainfire published a fix which might turn the camera unuseable.
Click to expand...
Click to collapse
Clear Explanation, thanks :good:
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,
Is it possible that apps obtain root rights without you know it ?
Could you please answer for
1) rooted smartphones,
2) unrooted smartphones.
Sorry if my question seems too basic.
Amusons-nous avant tout !
iwanttoknow said:
Hi,
Is it possible that apps obtain root rights without you know it ?
Could you please answer for
1) rooted smartphones,
2) unrooted smartphones.
Sorry if my question seems too basic.
Amusons-nous avant tout !
Click to expand...
Click to collapse
System applications always have root regardless of whether your phone is rooted or not. Third party apps usually don't have root rights, but malicious ones may exploit processes and apps that have root. If your device is not rooted, you wouldn't notice anything. If you have root and root control app like Supersu, you can restrict many apps. If you have Xposed privacy module, you can restrict even system apps, but you have to know what you are doing, otherwise, you may break your system...
optimumpro said:
System applications always have root regardless of whether your phone is rooted or not. Third party apps usually don't have root rights, but malicious ones may exploit processes and apps that have root. If your device is not rooted, you wouldn't notice anything. If you have root and root control app like Supersu, you can restrict many apps. If you have Xposed privacy module, you can restrict even system apps, but you have to know what you are doing, otherwise, you may break your system...
Click to expand...
Click to collapse
My smartphone is rooted and SuperSU, Xposed framework and XPrivacy module installed.
I deactivate SU when I don't need it; I think it's a good IT practice.
After reading your answer, I have two other issues :
1) I understood that malicious apps may gain root rights by using security weaknessses of processes and apps that have root. Is it also possible if SU is deactivated ?
2) If SU is activated, is it possible that malicious apps may gain root rights without being warned by SuperSU ?
Thanks for your help.
iwanttoknow said:
My smartphone is rooted and SuperSU, Xposed framework and XPrivacy module installed.
I deactivate SU when I don't need it; I think it's a good IT practice.
After reading your answer, I have two other issues :
1) I understood that malicious apps may gain root rights by using security weaknessses of processes and apps that have root. Is it also possible if SU is deactivated ?
2) If SU is activated, is it possible that malicious apps may gain root rights without being warned by SuperSU ?
Thanks for your help.
Click to expand...
Click to collapse
You shouldn't deactivate Supersu, because it really helps you to have more control over apps. You can set it not to trust even system user; you can set it to deny root during boot. You can set a password which will prevent apps from having root without a prompt. So, if you deactivate it, you lose some protection. In addition, there are some very good open source apps that give you additional protection, such as Afwall, which requires root. If you disable root, it won't work. From a secuirty point of view, it is better to have Supersu on all the time, but it has to be properly configured...
Malicious apps may still get root from those processes that have root regardless of Supersu. No system for any device is guaranteed against exploits, which are not known until they are discovered. Deactivating Supersu or unrooting your device does NOT revoke root rights from system apps. They have it anyway. Your phone would simply not boot or function if the opposite were true...
Thanks for your advice and explanations.
You wrote :
From a secuirty point of view, it is better to have Supersu on all the time, but it has to be properly configured...
Could you please publish an example of a proper configuration for SuperSU ?
iwanttoknow said:
Thanks for your advice and explanations.
You wrote :
From a secuirty point of view, it is better to have Supersu on all the time, but it has to be properly configured...
Could you please publish an example of a proper configuration for SuperSU ?
Click to expand...
Click to collapse
Enable pro; enable su; reauthentication; default access - prompt; enable pin code; don't enable su during boot; enable mount namespace separation; enable tapjacking; don't trust system user. In developer section grant root to apps only.
Unless you use MM, don't upgrade Superuser above 2.65...
I don't know what is "enable tapjacking".
Could you explain please ?
Amusons-nous avant tout !
iwanttoknow said:
I don't know what is "enable tapjacking".
Could you explain please ?
Amusons-nous avant tout !
Click to expand...
Click to collapse
It is all in Supersu settings...
optimumpro said:
In developer section grant root to apps only.
Click to expand...
Click to collapse
Hi, where is developer section? All other options are present but except this one.
@optimumpro
Sorry, but I don't understand why it's better to have always SU activated.
From my point of view, if SU is only activated when I need it, it's not a hole of security.
What do you think about that ?
Amusons-nous avant tout !
scattey said:
Hi, where is developer section? All other options are present but except this one.
Click to expand...
Click to collapse
In your phone Settings...
iwanttoknow said:
@optimumpro
Sorry, but I don't understand why it's better to have always SU activated.
From my point of view, if SU is only activated when I need it, it's not a hole of security.
What do you think about that ?
Amusons-nous avant tout !
Click to expand...
Click to collapse
As I have already said, there are third party apps that can protect you and they require root. I will give you 2 examples: Afwall and Adaway. If you don't have afwall, your phone is exposed to the internet. Adaway takes care of ads/tracking/malware domains system wide. Both apps require permanent root.
@optimumpro
So, the logical conclusion if I have not installed third party apps requiring permanent root, is that in this case it's useless to let SU permanently activated.
But my initial question was about the fact to be warned or not if apps can gain root rights. So thanks to your first answer to my post, I conclude that if SU is permanently activated, I would be permanently warned after booting.
Am I right ?
Amusons-nous avant tout !