Dear friends,
I read about rooting. It means that I as the user of the phone will get super user rights, that is I can view system files ..etc. Please correct me if I am wrong.
I am about to install madmack 1.4 KE7 which will enable Arabic read/write on SGS2. Now madmack said that the ROM is rooted. This means that after flashing this ROM I will have super user rights, right?
If this is correct then will the applications that I have or that I will download from market later, will they use my permissions as a super user or they will use what permissions they have? i.e. because I have super user rights will they have the same rights?
Also, lets say I am happy with the new ROM but I don't want to be a super user. Is it possible to get the ROM and disable super user and use the phone as a 'normal' user?
Kind regards,
Sul
Yes, you will have superuser rights after rooting
Sent from my GT-I9100 using XDA Premium App
anything that accesses super user access will need to be granted by you with a pop up from the superuser app. so its pretty hard for anything to get by you.
Related
Is there a way to install an apk as a system app? I want to 'unroot' a device but still run an app that requires root access. I'm unsure of how this can be done, any advise would be very much appreciated!
Thanks
I know that the Z4 root app has an option for temp root functions which goes back to an unrooted state once you reboot.
My guess is that you can run that, place your apk in the appropriate system folder, install the apk from there & then reboot.
But again I'm not to sure if temp root functions work on our G-Tabs & if it does if it's as simple as I explained. Worth a try I guess.
Again I'm assuming that your not already in a permanent root state. If so then you'll have to unroot completely first & then try what I mentioned above.
Unless someone has an easier method?
convert user apps to system apps
nikt said:
Is there a way to install an apk as a system app? I want to 'unroot' a device but still run an app that requires root access. I'm unsure of how this can be done, any advise would be very much appreciated!
Thanks
Click to expand...
Click to collapse
Titanium Backup Pro (paid version 3.8.1 and higher) has a function that allows one to convert user apps-->system apps (as well as system app-->user app ... though this sometimes causes initial FCs, which generally disappear with reboot).
Not sure if the effect will remain after unrooting.
Just to clear up a bit, not because an app its on /system it will have root access. If you want to run an app that needs root, you need root, thats it. You cant unroot and use the app after that.
So, no you cant do that. Its 2 different things installing an app on /system than having root for an app.
pmcnano said:
Just to clear up a bit, not because an app its on /system it will have root access. If you want to run an app that needs root, you need root, thats it. You cant unroot and use the app after that.
So, no you cant do that. Its 2 different things installing an app on /system than having root for an app.
Click to expand...
Click to collapse
So then how do proprietary apps like Sprint Nascar (as an example) run on an unrooted phone?
Why would Sprint Nascar need root permision?
pmcnano said:
Why would Sprint Nascar need root permision?
Click to expand...
Click to collapse
It probably doesn't or it might I have no idea. The op never pointed out which apps he wants to use.
However & this is a big however, as I have no idea which apps require root access, one has to assume that any of the preinstalled apps that come on our G-Tabs do in fact need root access, yet they can run on an unrooted device. Again I could be wrong.
That being said, how does one go about determining which apps require root access?
Thanks for the replies guys. The issue is supporting proxy servers on unrooted devices. There are several proxy apps that require root access as well as a kernel that supports proxy. If the proxy app were installed as a system app, would this have enough rights to access the kernel as required? I don't know enough about this but was led to believe this might work if it was running as system. Same for apps that use CIFS, like mount manager. I guess I'll give it a try and see what happens...!
Like I said, being installed on System doesnt have anything to do with having root or not.
Im 95% sure about what I am saying.
edit: I confirmed it..so 100% sure, if the app needs root, you will need root no matter where the app is installed.
In the past I read a thread from someone claiming that he had
Appbrain App Market installed on his phone which is a Non-Root app the last time I checked, Well anyways he said that he was Receiving Popups from the app to Grant it Superuser Permissions.
I really Didn't think much about it until now when I Received a Popup of my own, After I Installed whatever Stupid Basketball 3D game from the Market myself...
I checked and it Wasn't a Root app, and it Didn't even show up in the Superuser app Log, even though I Didn't Grant it Permission. I just UnInstalled it as soon as I saw the Popup!
So my Question is...
What the Hells up with that? Is that some type of Virus app or some ****?
Thanx in Advance!
PMGRANDS said:
In the past I read a thread from someone claiming that he had
Appbrain App Market installed on his phone which is a Non-Root app the last time I checked, Well anyways he said that he was Receiving Popups from the app to Grant it Superuser Permissions.
I really Didn't think much about it until now when I Received a Popup of my own, After I Installed whatever Stupid Basketball 3D game from the Market myself...
I checked and it Wasn't a Root app, and it Didn't even show up in the Superuser app Log, even though I Didn't Grant it Permission. I just UnInstalled it as soon as I saw the Popup!
So my Question is...
What the Hells up with that? Is that some type of Virus app or some ****?
Thanx in Advance!
Click to expand...
Click to collapse
i'm not familiar with random apps from the market asking for superuser permission but i am familiar with the superuser app and how the permission structure/process works.
essentially, the superuser.apk file replaces your /system/bin/su binary with its own binary. the superuser custom binary, whenever any user or application executes a command using the su binary (executing a command as root) the superuser su binary redirects to the superuser application then prompting the user to accept or deny the request.
i know i have seen it is possible to spoof these requests, but it was done by a very knowledgable friend and i don't think the spoofing of superuser requests is common place or well known (might have been patched recently too).
without knowing the application's source code that requested superuser access, i personally would not trust the application unless the application stated it would need root access and performed functions which required root access. example, if the application were a game, i don't see any reason it would need superuser access.
once an application has been granted superuser access on an s-off evo 3d, it essentially has write/read access to the majority of the android partitions including the kernel, system, data, cache, etc.
from what you've described, i think you're correct in not granting an unknown application superuser access. as a developer with applications in the market, i would appreciate an email from a user who experienced such a situation and a screenshot attached would be even more helpful. might be worthwhile reaching out to the developer to confirm or ask them to explain.
thanks for posting this information. always good to know. hope some of the information i provided helps!
joeykrim said:
i'm not familiar with random apps from the market asking for superuser permission but i am familiar with the superuser app and how the permission structure/process works.
essentially, the superuser.apk file replaces your /system/bin/su binary with its own binary. the superuser custom binary, whenever any user or application executes a command using the su binary (executing a command as root) the superuser su binary redirects to the superuser application then prompting the user to accept or deny the request.
i know i have seen it is possible to spoof these requests, but it was done by a very knowledgable friend and i don't think the spoofing of superuser requests is common place or well known (might have been patched recently too).
without knowing the application's source code that requested superuser access, i personally would not trust the application unless the application stated it would need root access and performed functions which required root access. example, if the application were a game, i don't see any reason it would need superuser access.
once an application has been granted superuser access on an s-off evo 3d, it essentially has write/read access to the majority of the android partitions including the kernel, system, data, cache, etc.
from what you've described, i think you're correct in not granting an unknown application superuser access. as a developer with applications in the market, i would appreciate an email from a user who experienced such a situation and a screenshot attached would be even more helpful. might be worthwhile reaching out to the developer to confirm or ask them to explain.
thanks for posting this information. always good to know. hope some of the information i provided helps!
Click to expand...
Click to collapse
Yeah man I Never really Experienced a App Requesting Superuser Permission, that Wasn't even a Root App... Just Didn't seem right to me either... A Game Shouldn't need Root Access!!
Thanx for your Reply!
I recently had the same op-ups from Tasker. But since I had been using Tasker even before rooting, I denied the request.
Are there any more precautions we need to take with regards to this.
odyssseus said:
I recently had the same op-ups from Tasker. But since I had been using Tasker even before rooting, I denied the request.
Are there any more precautions we need to take with regards to this.
Click to expand...
Click to collapse
Great question. If anybody else has experience/knowledge feel free to chime in.
Regarding precautions, there are a few basic steps which I think we're all fairly familiar with as being general computer precautions. These are a few which come to mind:
1) Don't load software you don't trust.
2) Always thorougly check the permissions being granted to an application. Example, once you grant an application permission to load at startup, it now has the potential to always be running in the background. Potential bad situation: the application *could* be gathering user/system data and if it has network access, sending this data back.
3) Superuser provides a great basic level of security to protect root access. Without superuser, any application can execute the su binary now running with root priviledges and there will be no required notification to the end user. This could all happen in the background w/o a log, audit trail or notification to the user. Root priviledges, as I mentioned above on an S-OFF EVO 3D will give write access to /system, /data, boot (kernel), recovery, etc. This is potentially very dangerous and important to protect the su binary.
Important to realize, once an application has been granted superuser access, it has the potential to destroy the device or grab extensive system/personal information and send it out. This makes it essential to trust the application.
As with any type of security, there are always ways to bypass. Essentially, these three steps should help avoid the majority of issues.
On a brighter note, there really aren't many Android viruses or malicious applications in circulation. For the most part, people who post on XDA and android application developers/posters in the market have are trustworthy. The comments on Market applications are usually fairly helpful. Might be worth skimming thru a page or 2, maybe 3 or 4 of market comments on a suspicious application or emailing the developer.
I know as a developer I'm more than happy to explain any function or question regarding my applications, especially if it raises a security/privacy concern to a user.
Hope that helps round out some simple precautions!
Hello, i just installed galaxy task 14 rom but i have a root problem and i'm unable to use applications which need to be rooted.
Have any solutions please ?
Thanks
doesn't sound like you are rooted. Do you see Super User in your app drawer?
I don't see super user in app drawer.
Then your not rooted. I would check for a guide to root. Once you are rooted you will see Super User in the app drawer. You can also get an app called root check to ensure that you are completely rooted and have full access, but I haven't seen a time where Super User was available and the device wasn't fully rooted. Hope that helps
I'm aware what rooting is and I'm benefiting from it on daily basis on my GT-I9100. However, what exactly happens during the rooting process? As I understand, (often) custom recovery(for example Clockworkmod recovery) is installed, an application for managing programs which might need root access(for example SuperSU) is installed, su utility for switching to root user is installed, but what else happens? Are there some file permissions changed during the rooting process?
All I know is I had to install supersu from playstore after rooting and then downloaded rom manager to get clockworkmod but idea I got was the rooting itself strips security from phone so that you can gain full access that samsung otherwise blocked. I havent looked in depth to see anything that the root itself installed but hey im a newbie with this sort of stuff
Sent from my GT-P3110 using xda app-developers app
m4rtin86 said:
I'm aware what rooting is and I'm benefiting from it on daily basis on my GT-I9100. However, what exactly happens during the rooting process? As I understand, (often) custom recovery(for example Clockworkmod recovery) is installed, an application for managing programs which might need root access(for example SuperSU) is installed, su utility for switching to root user is installed, but what else happens? Are there some file permissions changed during the rooting process?
Click to expand...
Click to collapse
You can install all these great programs from the Play Store that require root, also you have manual access (through file explorer) to your system files like frameworks, stock sounds, built-in apps and more. You can disable the annoying ads in the games, you can backup your app data (like progress in games, so you don't have to start over and over again), you can backup settings, change the system look (icons, sounds etc.) and much more. Otherwise you won't see any interface changes or unlock some hidden options. :laugh: Everything is done through the programs.
^The guy knows what you can do with root, he's asking what the details of the rooting process are.
I don't know either but I think you basically unlock the boot loader, then install SU.
Sent from my LG-P920 using xda app-developers app
LeighR said:
^The guy knows what you can do with root, he's asking what the details of the rooting process are.
I don't know either but I think you basically unlock the boot loader, then install SU.
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry, at second reading I understood him. My bad.
italcrwd are
m4rtin86 said:
I'm aware what rooting is and I'm benefiting from it on daily basis on my GT-I9100. However, what exactly happens during the rooting process? As I understand, (often) custom recovery(for example Clockworkmod recovery) is installed, an application for managing programs which might need root access(for example SuperSU) is installed, su utility for switching to root user is installed, but what else happens? Are there some file permissions changed during the rooting process?
Click to expand...
Click to collapse
At a high level the following changes (and a few more I cant think of) are made to the device:
Access to previously read-only areas of memory are changed to read-write
A binary called busybox is pushed to the handset (the location varies depending on rooting method used)
Busybox is a set to linux like tools compiled spercifically for the CPU of the device (usually ARM)
The SuperUser or other 'Gate Keeper' application is installed to allow and monitor access to the busybox binary (this is optional but is normally done by default and is required for most root apps to function.)
In essence, your original post is almost spot on.
Well, hello. I'm most certainly a noob, although I do have experience with developing for android and using Linux on a PC system. I haven't done any rooting/unrooting/custom-firmware-flashing before, however.
I believe this question to be about Android devices in general and so I'm posting it here instead of a device-specific forum.
The short version of my question is:
Is it possible to install a custom firmware on my phone, but prevent apps installed in it from having root access?
The long version:
Having read about how the Android OS works, I understand that each app installed in a system basically has its own user account, and that's how privileges work: The OS simply doesn't allow this specific user/app to access other apps or hardware.
Unless I'm mistaken, rooting a phone makes all apps run under the same user account: root. Which means that all apps have access to every other app and all hardware on the device.
I found many web pages that explained that this is a security risk as malicious code could then use anything at all on the phone. This makes sense of course, that's why most applications on a Linux system don't run as root.
I understand why rooting the device is necessary to install a custom firmware on it, but what I haven't understood is why the device has to stay rooted afterwards. Isn't installing a custom firmware basically replacing the OS on the device? If so, couldn't I replace it with an OS that doesn't run everything as root but instead runs every app as its own user, like unrooted devices do?
I've searched this website and others for information on this but I haven't been able to find something that answers this question.
I found explanations for why unrooting is needed to install a custom firmware, but they didn't include why the resulting system can't be rooted.
I found guides on how to restore the original firmware on a device, which isn't what I'm looking for, although this process is called "unrooting" (the word seems to be misused here, but maybe that's just me).
I also found guides on how to trick certain applications, which won't run on a rooted device, into thinking that the device isn't rooted. However, the reason I'd prefer my device not to be rooted isn't to trick any applications but for security reasons.
What I'd basically like to do, is install custom firmware but, once that's done, ensure that applications I download from the Market or install directly don't have any more privileges than they've been developed to ask for. Is that not possible? I don't understand why not...
Gaining root access to your phone will not give a single app root privileges, for the most part you will use an app called superuser or supersu to allow or deny any app root access. (Sometimes baked into ROM)
But you have no worries, any app that you download from the market will not have root unless you give it
Sent from my Nexus 4 using xda premium
demkantor said:
Gaining root access to your phone will not give a single app root privileges, for the most part you will use an app called superuser or supersu to allow or deny any app root access. (Sometimes baked into ROM)
But you have no worries, any app that you download from the market will not have root unless you give it
Click to expand...
Click to collapse
Is that so? Thanks. It seems I was wrong at the very beginning of my logical process.
So, if I understand correctly, the lack of security isn't that anything installed has root access, but that it can have root access. Is that right?
Correct, even whatever custom ROM you are running has a built in app for lets say messaging, this will not have root access.
You just bow have the ability to do anything (mostly) to your device, but you don't have to
Sent from my Nexus 4 using xda premium