Hi all,
As a noob, I try to learn about rooting.
But, I am a little bit more geeky than the average user. So I want to understand in bigger depth what is going on when "you root" the phone.
I have made my search around and I have a certain question:
Does rooting include (in all cases) the change of rights on the /system directory, no matter what the phone is?
Is this the 'heart" of the rooting process or am I missing something (or a lot) here?
this is as far as I know.
your phone is a mini PC running a flavor of linux. In each linux PC, there's the system admin, "root". When you root, what you do is to unlock that root user in order to execute stuff as "root". not as a regular user.
The unlocking is done via exploits in the phone / model. Thats why the process differ in phones and models.
Hope you got it. ( and hope I got it )
Hello there, thanks for the answer.
I know about Unix-oid OSes, because I have been working for a long time with them.
I wanted to understand if the ultimate goal for "rooting" is the permissions' change of the /system directory (or there is something that I didn't know). The vulnerabilities that the techies exploit is something that comes first. When they exploit these vulns, then they are ready to chmod. And then, voilà.
This is what I want to be sure about.
Related
Hi all,
First post here, be gentle.
I am a linux user (pretty noob but learning) and I'm a bit confused about what I've been reading on rooting android. I'm looking at getting a Droid X and I'm just trying to understand things before I dive in (already running 1.6 as a VM to play with it).
As far as I can tell--my bash skills not being quite good enough to completely understand everything in the rooting wikis--the methods employed to gain root access to a phone (from: wiki link) use an external OS to push image files onto the phone, then remove the native rights management files (mid.txt?) and replace them with something else in the pushed files. (Please correct me if I'm wrong, cause I probably am)
When completed, this presumably allows you to run su and changes the root password or removes it (though I have no idea how that would work). If this is the case, and I root my phone does this mean that my default login to new sessions will be as root, or will I have to run su to gain privileges? And if I have to run su, what's the password?
One of the first things I learned when getting into linux was that root can be dangerous--you can kill your computer etc.--so, what does this mean for my phone? Can I just login as an admin and then sudo for the apps that need it? (Yes, I realize that I would have to install sudo and edit the list of sudoers etc.) Is it not dangerous to run as root or it it dangerous but easily ignored?
I'm just curious about this because it seems funny to me that a lot of joe shmos who have no idea what they're unleashing by running as root might suddenly hear that it's a great idea to go into a terminal and run
Code:
#rm -rf /
and I have this desperate hope that it's not as simple as that and there is some kind of rights management still in effect once a phone is "rooted." If not, and rooting a phone really does log you in as root for every session then it's much more dangerous than I had thought.
Thanks,
Bob
Is there really no one here who can answer this?
My phone is coming on Wednesday and I'd love some help with this and I can't believe that one of the brilliant people here can't answer this.
Sorry nobody replied yet. When you root there is usually a one click root app that does everything for you. After you are rooted you can install superuser from the market and it lets you choose what apps are allowed to have root access. You can search the droid forums for more info since I have an epic. If this helped please hit the thanks button below
Sent from my Epic that craves frozen yogurt
Hi everybody.
I bought recently (mid-November 2012) a Polaroid easy2 tablet. It is an MIDR477 model, made in China by Baolaili and based on a MIPS 74Kc processor. It is the "low-end" resistive model but I cared little for it is supposed to become a "smart terminal" in a data acquisition system. I needed to break into the system (I am a Linux person and prefer to do Perl and C programming) to make it suitable for my application.
It turned out to be easy to get the root shell, I rooted it successfully with the help in this forum, thanks to the contributors.
The file system, accessible through the /dev/block/actX devices is actually easy to mount and modify and after a short while I managed to modify permanently the init scripts. The one of interest was init.rc that changes the path and libraries default. I still have a problem due to the non-standard paths (and my limited knowledge in Linux administration), while changing successfully the paths and other variables, I cannot get any external program to run. As an example, when I try to do a simple 'ln -s /<original path> /<link>', it is never executed from the init.rc. Can someone tell me what I am doing wrong ?
Additionally, if there is in the Android boot sequence a better way to gain control, I would be very grateful to know it (my goal is to be able to set-up the system to run unattended).
Edit: My assumption was that init.rc was a script that executed, it seems to be a file parsed by init. No wonder why it did not work properly. Still looking for an entry point that is not a java component ...
re-Edit: (I'll make a thread on my own ) ... I finally dug the answer in this forum, if anybody is interested in the boot process :
3w.androidenea.com under /search?updated-max=2009-10-16T13:47:00%2B02:00&max-results=7&start=21&by-date=false
sorry for the restriction ...
the answer I was looking for is in the "The init process and init.rc" section.
Best regards.
Hi,
I've got the same tablet, but I can't find a way to root this device.
Can you help me find a thread where this is explained.
Ty,
Dimitri
doorknob314 said:
Hi,
I've got the same tablet, but I can't find a way to root this device.
Can you help me find a thread where this is explained.
Ty,
Dimitri
Click to expand...
Click to collapse
Hi Dimitri.
All this is from memory. I found on this forum a thread about a similar product that actually gives the password for the root shell (something like connect123, can't remember). After installing the adk and the adb shell (took me a while and it was under linux), I uploaded an unlocked busybox (be careful about the proc, it is not the usual type: MIPS 74Kc). I think that at that point the rooting app started functioning. I still have superuser installer but that was not the one originally used. Sorry not to be able to help more but as the tablet is unlocked, I quickly forgot about the process.
Regards.
Thank you, i hope i can find an answer with your information
Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.
Dreadful man said:
Has anyone created a method to root Acer a1-713 manually?
Those one click methods are really crude also I don't even know what's happening in there.
If anyone knows it please help me.
Click to expand...
Click to collapse
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573
JnFrks said:
Some said that Kingroot worked for them in this Q&A thread -> http://forum.xda-developers.com/chef-central/android/root-recovery-acer-iconia-tab-7-a1-713-t2851573
Click to expand...
Click to collapse
Well it didn't for me. Also I want to know what I am doing with my tab and not just know that tapping this button will root my tab.
Have you ever tried to look at this site -> http://www.oneclickroot.com/device/acer-iconia-a1-713/. They featured this one-click rooting and it seems they can be trusted. I've downloaded and installed their software so no worries. Well, I'm also using a one-click root utility and it's always working. (just sayin')
The process of rooting a device is too complicated for those who don't have knowledge in Linux (like me), so your question about manually is out.
http://www.oneclickroot.com/device/acer-iconia-a1-713/
Well this one click root website was also a waste of time and didn't work either .
I may have to wait a little bit more before dumping this thread.
Rooting an android device basically means (for me) granting You (as the user) to do whatever you want to your device's system, hardware, etc. But what does root will actually do to your device that will cause you to obtain that superuser access? It's because of the "su" (Switch User) file used by Android and other UNIX-based systems that allows a process of switching of a user to be the superuser (or root user) that has access to the commands and file system, meaning those processes that requires root permission (root access or superuser access) need to invoke su. So basically the process of rooting will just push this su, a binary executable file, to the file system so that you can switch to the root user to give root permissions... And the Superuser application is just optional, but really required for some reasons, it serves as the "gatekeeper" of the su binary so when a certain command or application that invokes su will prompt the user by the Superuser app first before granting the root permission since becoming the root user can do whatever to the system which means it can cause the device to malfunction, etc... So what do you mean by manually?
Sorry for what I'd just suggest you that OneClickRoot waste your time...
Oh, there's a bad news after spending time searching how to root your device, read the news here -> [GUIDE] Firmwares, ROMs, CWM, Root - Acer Iconia (MTK) Tablets [ⒶⒸⒺⓇ ⒹⒺⓋⒾⓁⓈ]
Can't find a best way to root your Acer.
Well thanks for enlightening me on the topic, I hadn't really understood what really is su..
By manually I meant by using computer and tinkering with the files hands on.
Oh, and you needn't to be sorry since everything I tried didn't work. Sometimes I had root till the app was open while sometimes it existed until the next reboot.
Also looked at the link you gave and well, what can I say, it really is bad news and there sure is the risk of bricking my device.
Well thanks for taking your time.
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
joy.julep said:
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
Click to expand...
Click to collapse
Hello,
Please post your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal
hi guys,
first, i m all time thankful to these developer guys, you make mobile world so genius, yeah it was never genius,
second, something i learn and something i want to learn more is about android always, but here is my question below that is really important. i don't know if it really make sense or not but i would like to know your opinion.
question :- i see there is a way to push files into device without rooting it. is it secure? it is safe? i guess yes. than how can i push titanium backup(data only) of particular app into my device?
example : - i myself after learning lot about apk tool and all that, modded "whatsapp" successfully and which is out of this world according to me, lately i cam to know there is already one called whatsapp GB, but mine is mine. (right now i don't have rooted device so couldn't send screenshot), but what i am trying to figure out is, i can install my modded apk on my non-rooted device and can run it either, problem comes when it is about registering number, what i really thought that if i can push titanium backup of my modded whatsapp.apk (data only - taken perviously when i had rooted device) to this non rooted device via ADB, than i didn't need to root my device ever, and so for any other app that is modded by me or any developers can be executed on non rooted device.
pros - if this is possible than i guess People won't need to root device, will not loose warranties, will not loose device by bricking it, will get out of a procedure of root methods, no one will ask more about root method, soft brick, hard brick, boot loader issues and many more questions like that i guess.
there will left only one tutorial than if this is possible and it will be like this - how to use adb?(step by step : beginner to black hat).
if this is possible than what we need? proper method of how to use adb, most of people easily can learn how to use adb but most of tutorial misses some points like how to push file by changing r/w permission, and where to put new data backup or files in device like some tutorial i have seen gives only command line but people actually don't know where to put the file like /data/data and than what?
Developers and Rooted device owner will become God in fact in this case because they can lead the rest in right path.
is this possible? or am i ridiculously making no sense?
This is not the right place.
You were already advised to post in the Ask any Query Newbie Friendly thread last month.
Please post there with all relevant details.
Thanks and thread closed