[Q] Rooting, bootloaders and custom ROMs? - Galaxy S II Q&A, Help & Troubleshooting

Hi, I would like to have root access to my phone, but not necessarily with a custom ROM. I would also prefer to not change my bootloader.
What exactly is rooting? Is it replacing the whole system image with an image that gives the user root access? Or is it just like enabling sudo for the user? Or is a smaller part replaced? (I am somewhat familiar with electronics, computers and Linux, but I find the Android hacking a bit confusing )
Also, is it possible to run stock Android, only with root access? Will the access be lost when upgrading?

c3c0l0n said:
Hi, I would like to have root access to my phone, but not necessarily with a custom ROM.
DEV section rooting post /
What exactly is rooting?
root is the user account in Linux with all privileges. The root user can edit anything on the system. For safety reasons, users do not have all those privileges. When you root your phone, you will gain write access to areas of the phone you couldn't previously access and are allowed to run more commands in the terminal. Because applications do not get a lot of privileges, some of them require you to root the device in order for them to function properly (or fully).
Also, is it possible to run stock Android, only with root access?
Yes and Yes lost root on upgrade usually .
jje
Click to expand...
Click to collapse

Thank you. How is the rooting performed? Is only an ACL modified, or is a more fundamental part of the system changed (like the kernel, bootloader etc)?
I know that a custom ROM might be unstable/experimental, but does the same apply for rooting, or is the modification so small that one could expect the exact same stability as in the stock ROM?

c3c0l0n said:
Thank you. How is the rooting performed? Is only an ACL modified, or is a more fundamental part of the system changed (like the kernel, bootloader etc)?
I know that a custom ROM might be unstable/experimental, but does the same apply for rooting, or is the modification so small that one could expect the exact same stability as in the stock ROM?
Click to expand...
Click to collapse
All your questions are explained in detail in the Development section

Sorry, I did not find it. However, I read this without getting smarter. This video suggests that rooting is a process that does something with your phone without replacing everything. An exact list of what the rooting tools do would be perfect

Not all tools do the same thing. To get a specific answer, you will have to ask the person that came up with whatever rooting tool you are referring to. Some phones take more to root than others.

Related

Will the HERO be a ROOTED phone?

I used to work with WM 5 & 6 phones, had plenty of them and enjoyed them all until I discovered the HTC Magic. What a giant leap forward!! Especially when using Google Apps as we do. I am however a bit reluctant to root the magic as it doesn’t seem like a walk in the park. I really miss being able to backup SMS messages and all the other apps that only run on rooted devices.
So my question is if the HERO is a rooted device or not.
Does anybody have an answer to this question? I’m so tempted to preorder one
the answer to the question should be probably yes seing how people have the system dump files. so its just a matter of time
In the meantime, you can back up SMS and MMS with GBackup from Market - backs up to Gmail automatically - can also back up call log and pics...
Dayzz
Apologies for my ignorance but what does rooting the phone mean? I've just come from using a Windows mobile phone - which I have been using since the original SPV!
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Ofcourse it's not 'rooted' when you unpack it from the box.
Eventually I'll guess the Hero will be rooted, but when and how... we'll just have to wait.
dipje said:
Ofcourse it's not 'rooted' when you unpack it from the box.
Click to expand...
Click to collapse
Easy son... He asked, I provided.
barryallott said:
Easy son... He asked, I provided.
Click to expand...
Click to collapse
wasn't ment to be offensive in any way ...
barryallott said:
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Click to expand...
Click to collapse
But as in Unix /Linux you use an ordinary login for normal day to operations and su to to use root. You have to consciously change your privelidges which is safer!!
Simon
Lots of useful info on allsorts, including rooting and other hacks here
http://forum.xda-developers.com/showthread.php?t=542452
Daisy xx

[Q] How does "Android Root" works ?

Hello XDA-Forum users,
I ask you a question: How does Android Root works ?
I mean, for example, How does it works in Nexus One ?
This would be an understanding question to know more about how I get root from my Phone (Nexus One, for example) from scratch, from sources.
upupupupupup
Rooting basics:
http://lifehacker.com/5342237/five-great-reasons-to-root-your-android-phone
For details on how to do it on your device, Google or use the forum search. Lots of rooting information that is device dependent out there.
It basically gives your phone permission to do almost anything. It is similar to giving a user in Windows Administrator rights. It is called super user. You can do many things such as removing unwanted apps and overclocking.
This is not what I mean, I asks for an explaining in which the question is "How the root is possible? What active the root ?" Probably a kernel exploit, or stuff like that, to understand the underground passage to take it, from an hack view.
So, How works a root utility (such SuperOneClick) to set gid to 0 ?
Valid question, I am also interested in learning this.
In other words, if I were to perform the rooting manually, where can I find such info?
And some of the question is why su must be in some diredctories, and can't be run from /data/local/tmp for example?
Someone can enlighten us?
diego.stamigni said:
Someone can enlighten us?
Click to expand...
Click to collapse
The general approach is taking advantage of bugs in the android OS
The process works something like this
User crafts some special data that contains a "payload" (the script/executable that we want to run)
User runs a system process that has root privileges and gets it to open the special data
The bug causes the system process to get confused by the data, and ends up running the embedded script
The embedded script runs with the same privileges as the system process, and thus can stuff that normal users aren't allowed to do (e.g. installs the SU app)
Commonly, things such as buffer overflows are used
So after gaining root access, which apps can run as root?
Or the user becomes root(as in desktop), and can run all types of apps?
Can root app(run as root) access everything?? Or app permission still applies?
Is it that system exploit is always used to run root apps?
can someone explain in technical details? not how to root.
are rooting programs open source??
What is the root procedure
Bayint Naung said:
So after gaining root access, which apps can run as root?
Or the user becomes root(as in desktop), and can run all types of apps?
Can root app(run as root) access everything?? Or app permission still applies?
Is it that system exploit is always used to run root apps?
can someone explain in technical details? not how to root.
are rooting programs open source??
Click to expand...
Click to collapse
Hi guys!
I have the same question and after searching and asking find this!
it is good!!
hope it works!
http://stackoverflow.com/questions/...hat-are-the-pre-requisites-for-it-to-work-wha
also look at the suggestedpages at the right of this page!

[Q] Rooting?!

Hello,
I'm considering rooting but I don't know what the meaning of having another kernel means, Do I lose TW4.0? Do I lose apps and data?
Thanks in advance
Rooting gives you user rights over a deeper level in Android OS.
Much as admin rights allowing modification of hidden system files in windows .
Its not another kernel just that using this method via a modified kernel is the only rooting method available yet .
Basic faqs SGS 1 applies also for most to SGS 2 but as SGS2 is new less development so far .
http://forum.xda-developers.com/showthread.php?t=723596
What is root/rooting?
root is the user account in Linux with all privileges. The root user can edit anything on the system. For safety reasons, users do not have all those privileges. When you root your phone, you will gain write access to areas of the phone you couldn't previously access and are allowed to run more commands in the terminal. Because applications do not get a lot of priviledges, some of them require you to root the device in order for them to function properly (or fully). T
If all of this means nothing to you then you are probably wise to NOT root your phone. Mistakes using root can break your phone very easily. (Usually, but not always, these can be solved with a reflash)
jje
Thank you for your reply, though you didnt answer the questions i had written. I already knew what rooting is
Sent from my GT-I9100 using XDA Premium App
+Answer is no no and no .
jje
Haha thanks dude, appreciate it!

semi noob question

alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
J35US said:
alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
Click to expand...
Click to collapse
Basically, the root section is blocked since it is set to r/o which normal user permissions cannot change. Rooting exploits change the system permissions and pushes the su binary in to give you superuser access which will then allow you full access to the system.
J35US said:
alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
Click to expand...
Click to collapse
as far as I know, Stock rom's don't have a root function implemented at all.
to get root access, people use exploits to change permissions of the folders to gain access to the System partition, and then the SU (superuser) binaries are put into /system/xbin , and then install the superuser.apk (to make use of the su binary)
EDIT:
Damn ninjas
so rooting is basically changing a few permisions of folders that i wont normally have access to in order to put the SU binary into the fore mentioned path
just re itarating to make sure i understand
additionally if i won't normally have access to these folders then how do they change the permissions <-- maybe pushing it but ask an you shall receive
J35US said:
so rooting is basically changing a few permisions of folders that i wont normally have access to in order to put the SU binary into the fore mentioned path
just re itarating to make sure i understand
additionally if i won't normally have access to these folders then how do they change the permissions <-- maybe pushing it but ask an you shall receive
Click to expand...
Click to collapse
You could say it like that but it grants you far more access and unlocks many possibilities making you the superuser. Rooting uses exploits which bypass these set permissions.

[Q] SGS2 Root / Rom questions (zergrush)

Alright, so I now have a new Samsung Galaxy S2 from Bell (GT-I9100M) and I want to play around with it. However, I'm pretty anal about getting the phone back to it's original state, just in case I'd like to.
I want to be able to backup everything from the phone in its current state so that I can restore it.
I'm currently getting the source for android and I'll be compiling zergrush from source in order to gain root access to the phone.
1st: Can this be undone?
2nd: Once you root your phone, does everything run as root? (that would be aweful)
3rd: Is root + Rom Manager + Titanium Backup all I really need to install custom roms easily? Or am I going to have to use Heimdall and such (I'm on Linux so no Odin for me unless I pop up a VM).
Correct my assumptions if I'm wrong:
It seems like zergrush exploits a bug that will give /data/local/tmp/sh uid of root. Is that how root access works? just a copy of the shell with root uid in that path. So if I delete this file, it unroots my phone?
If I zergrush my phone, gain access, use titanium backup to backup everything to the SD card or on my PC then I can use rom manager to get cyanogenmod and flash it straight through the phone's app. In case I want to revert to my good old stock rom and everything unrooted, I use rom manager to reflash the backup I made and then how do I revert what was done by zergrush?
Cheers!
Lewis
Is anyone familiar with what I'm asking?
as far i know zergrush was till 2.3.4 doesnt wored on 2.3.5 and 2.3.6 so not sure if it works on ICS.
try to search if the stock firmware is available for your phone model, unless you doesnt care for that in that case i assume ur phone is just a i9100 so you can flash a stock rom later using odin
now to gain root simplest method is http://forum.xda-developers.com/showthread.php?t=1103399
My phone is running 2.3.3 so zergrush should work.
As for the stock firmware, I'd want to extract it from my phone so that I get the exact same version when I revert.
the CF root method isn't suitable for me because I can't backup my kernel before flashing this.
I also can't use Odin as I am running linux. I can use a VM or Heimdall but it seems like zergrush is the best method for my situation. I already have the android sdk installed. My current issue is compiling zergrush from source... my environment doesn't seem to be completely setup correctly.
Why are you compiling it yourself? You can get a binary from the source, http://forum.xda-developers.com/showthread.php?t=1296916
There was a similar request a while back for what you're trying to accomplish, see http://forum.xda-developers.com/showthread.php?t=1409484
I compiled from source cause I like to know exactly what I'm running on the phone . Not such an issue when it's in user-space but when it comes to granting root access to anything...
Which is why I'm asking about what happens after rooting the phone. I suppose any app will have root access unrestricted... How does Cyanogenmod works for that? Can I explicitly grand root to applications, like on a linux desktop where you put your password when an app needs root.
So, can I undo zergrush's root by just deleting /data/local/tmp/sh ? (or just the setuid?)
ldiamond2 said:
I compiled from source cause I like to know exactly what I'm running on the phone .
Click to expand...
Click to collapse
So you've presumably peer-reviewed their code prior to compiling?
ldiamond2 said:
I suppose any app will have root access unrestricted... How does Cyanogenmod works for that? Can I explicitly grand root to applications, like on a linux desktop where you put your password when an app needs root.
Click to expand...
Click to collapse
There are currently two choices for managing root requests, SuperSU, and Superuser.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
https://play.google.com/store/apps/details?id=com.noshufou.android.su
AFAIK, neither of which publish their code publicly - so considering your earlier point, you won't be wanting them on your phone either.
oinkylicious said:
So you've presumably peer-reviewed their code prior to compiling?
Click to expand...
Click to collapse
Yep for sure.
oinkylicious said:
There are currently two choices for managing root requests, SuperSU, and Superuser.
Click to expand...
Click to collapse
At least having a single app that I can't see the code is safer than a bunch of them... I'll give it a shot.
But doesn't cyanogen mod offer superuser access management?
Found the source code for superuser
https://github.com/ChainsDD/Superuser

Categories

Resources