Database Info

[Q] Conceptual Rooting question

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

Samsung Galaxy Indulge 4G nand lock

I just got one of the new Galaxy Indulge 4G phones and tried rooting it.
BusyBox installer is telling me that the phone is rooted however it is nand locked.
and ideas on how to unlock nand on this phone?

How did you root it?

Thaxx said:
How did you root it?
Click to expand...
Click to collapse
SuperOneClickRoot.

Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!

So basically I think this means we a need a custom recovery, flash image and stuff. Bah, that'll probably take like a month

K, also tried visionary rooting, which did some wierd ****. I rebooted and it seemed like i had root, but super user still didn't work. It fooled a couple programs into thinking i had root, but it would not let me "touch" the files on the phone. Even though it claimed I had r/w permission.

Silvist said:
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
Click to expand...
Click to collapse
The Samsung Epic 4G drivers worked for me, also tried the rooting process used on the Epic whoever busybox says im rooted but that nand is locked, i downloaded Terminal emulator and it says im not rooted, also installing superuser not possible, I was able to install root explorer but not any good if doesnt let me delete the bloatware only read.

Yeah, busybox says the phone is rooted but nand locked.
superuser app was added to system/apps. however im not able to mount system/apps with R/W from root explorer. The rooting process seems to gain access to r/w the files but the apps cant.

seems 4G still have far distance from us...

Supposedly there's a work around for Nand locked, but the first one didn't work for me.
With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can’t copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don’t need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.
Click to expand...
Click to collapse
This didn't work still for me. So the only other option was unrevoked, but when I went to the site, it listed only HTC. Kinda confused how using HTC roms is a work around for a samsung phone lol. Still need some master guru's help on this stuff.

I too have been trying and am unable to get nand unlocked, I would really love some other ideas. Anyone out there able to help?

I'm waiting 'till the $50 MIR on the 1st, then I'll jump in with both feet.

Some guy suggested to shell root > perm root > restart device. That doesn't work either. I also noticed something called "media scanner" that scans as the phone boots up, i wonder if that's preventing any modified files.

If anyone knows how NAND unlocking has worked for other phones (and im not just talking about what apps to run or what room to use) please contact me so that we can try a few things out and hopefully get a full root for everyone.

Supposedly Mr. Parker rooted:
http://forum.xda-developers.com/showthread.php?t=803682&page=260
I'm asking him through both post and through private message if he could elaborate. Apparently he had trouble with getting Win 7 x64 to work, but it worked with Win Xp. I'm still not sure what drivers he used, and he said he had it not in debug mode. I tried in non debug, and my phone wouldn't even register. So hopefully he'll expand on how he did it. If not, back to the drawing boards, at least till we get a real pro in here.

Got my hopes up that even though we dont have full root yet, I would be able to get rid of the bloatware.
The SuperOneClick is able to get read/write access and send commands to the phone so I opened Root Explorer on the phone and then rand the superoneclick. As soon as the program mounted the phone with Read/Write I started clicking on the Mount R/W button in root explorer until it showed the app as having read/write access to the system/app directory. I tried deleting the Iron Man app and it said it was deleted successfully.
but then I checked and the app was still there loading root explorer agian then showed that the file was still there and had not been deleted.

Wow you managed to get root explorer to work? Mine just tries to obtain root, and crashes everytime i start it up now. I've tried to unroot, and uninstall and reinstall it. I used Linda manager to view the files on the phone, but like you if i deleted they would return on boot. That's why I think metro or samsung has some kind of media scanner that scans at start up, and it somehow reinstalls files, or prevents root. Can't confirm this yet because super user fails ;/

I've been trying also to get root. Programs often will think i have root access. as far as adb is concerned i do have root access till i dont something that requires it. I've been able to install root manager and look through some files. Im under the impression metro or samsung did install something odd, though im not sure the media scanner is it. Also the phone does not require root in order to install other-market software.

What do you mean programs "think" you have root? You mean you have super user? And what "programs" are you referring to? You can install root manager without a root yes, but in order to put it into "r/w" mode and delete the files from the phone itself, such as bloatware, you need root and Super user access. Most people here I hope are aware that you don't need to root to install "MOST" apps. There "is" apps that require root, and you cannot run them without root access.
Such as:
Titanium backup
Set CPU
Why do I want to root is like everyone keeps saying, to delete all the metro apps, and have "full" manufacturer control over the phone. That's the whole point of rooting. So far no one has rooted this phone PERIOD, or at least shown proof they were even able to. So any info you find regarding rooting please post it here.

Alright, so I tried what Mr. Parker did, and no go. Whether I ran super one click on Win 7 x64 (which was all in admin) or win xp, it would not install super user. In fact I noticed a couple of the files copied from super one click were already on the phone, and weren't able to be overridden. Which may relate to nand lock.

[Q] How can I modify or edit system file in the Andriod System

Hi,
I posted a question in forum about how to connect my A500 tablet to an Ad-hoc networking but after I did some search in the forum I found some steps to solve the issue and it is starting from rooting the device and finalizing by modifying a file in the following path:
sdcard/system/bin/wpa_supplicant
The problem is I can't rename the file (wpa_supplicant) also I can't copy the modified (wpa_supplicant) to the system/bin folder and a message appearing told that this file is "read only" and can not be modified or edited. Note that I used Root Explorer and Root Browser to explore the systems folders.
Please any one can help??

You can't do this because your device is not rooted !
Use Root explorer don't give all super user privilege to your device

my device did not open what shall i do??

As the guy answered, you have to be rooted in order to do that.
Im not sure if you can root tablets, I have never had any interest in this direction because I dont have money to buy one.
But if you can you click on Root explorer, then click mount r/w , go to system/apps.
If it is mounting r/o you can delete system apps, I did that to my SGSII and my battery life lasts much longer.
You also have access to the files that created the applications, the ones you create in Eclipse.If you are a developer , you would know what I'm talkin about.
I dont know any other ways of doing this if you are not rooted and I'm almost sure its not possible, but good luck still.

Im not sure if you can root tablets,
Click to expand...
Click to collapse
You can root tablets, even the a500 as tough as it is to do so. I am running FlexReaper ROM on my Iconia a500 right now. It's flippin' awesome !
As far as editing the system files, the O.P. may need to actually mount the drive as r/w.
In ES File Explorer there is an option to actually mount the file system as 'writable'......(which will be rejected if the device is not rooted).
Do you see any similar option in the file explorer apps you are using ? If so, try to enable it. Just browsing 'up to root' is not enough......at least for ES.
I would use a root check type of app to verify you are up to a 'true root'.
As for custom ROM's the Iconia a500 tab requires flashing with a custom unlocked bootloader and custom recovery image like cwm, then installing/flashing the new custom or stock OTA ROM and any desired app/system packs if needed. The Iconia a500 is pretty tricky, but possible.
If you do go the way of custom ROM's, I HIGHLY recommend the FlexReaper RF-1_rv3 Custom ICS 4.0.3 ROM for users running the Acer Iconia a500 tablet.
Super smooth, and the only custom ROM that doesn't start with a funny snow screen when initially booting up. A couple other ROM's I tried would 'snow' like a bad hardware compatibility issue or something. Flexreaper seems like it is the perfect ROM for the a500, at least for me.

many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!

ahmedalbidhany said:
many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!
Click to expand...
Click to collapse
I actually used the same method so I am unsure as to what is going on here.
Will read back thru my research and see if I can figure something out. I am still new to this rooting/flashing thing, so I don't want to mislead you. I'd rather find my methods in tangible text online, rather than relying on my fuzzy memory.

I am not sure if this will help, but if you boot into recovery, check if there is an option to fix permissions. Run it then reboot normally.
Should be under the Advanced header.

IMOP,your Root explorer manybe havent get the right from super user.
Or,there is a problem with the root app.
My A500 rooted with the method instead of official Recovery.

@ Valkillmore : thank you for your support I'll try this method and comeback again and post the results

Root + SSH + remount
Here's how I do it.
1) Root your device.. lots of tips on this in the forums and the process depends on your specific phone model.
2) Install SU super user access.
3) SSHDroid - Install from market and allow root access (via SU)
4) Turn on SSHDroid and login to it via an SSH client from your computer (see putty for windows, Linux, Unix , and MAC should have it already).
> ssh [email protected] (for example)
5) remount the system drive (it is typically mounted as read-only
> mount -o remount,rw /system
Then you can go ahead and modify files under /system folder. Note: when you reboot, /system will be mounted normally (read-only).

i had the same issue
i had astro file manager, it doesnt have complete root access.
downlaod efs explorer
go to settings
allow "up to root" click allow when super user dialog box pops up
select "mount" right under "up to root"
then go to efs explorer main manu press the "up" tap
navigate to wherever you want. bne carefull with what you change.
i was changing the APN settings on my evo

[Completed] Need some help regarding manual rooting using ADB to place the files. ReRooting phone

Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?

Hi Mc Fow1er
Thank you for using XDA Assist
As we do not have an specific forum dedicated for your device yet, our experts at the below forum should be able to help you. Please be welcome to post over in there.
Android Q&A, Help & Troubleshooting
Nice regards and good luck.
.
Mc Fow1er said:
Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?
Click to expand...
Click to collapse

root on 6.0 and a known exploit... quadroot

Ok so theres this security exploit or 4 actually that mainly involve sideloading a specially designed apk called quadroot, i assume that you already have an idea what this is if you're reading this if not then google it. I read that alot of the time root access exploits are found by finding apps that have root access and exploiting them to install su to the system partition. In this case you could potentially create your own. So my question is why isn't this being persued as a viable option? Pleas let the people who know what their talking about speak and if you have no legitimate knowledge of your own (im talking google cut paste) then just syfm please.

that-squirrel said:
Ok so theres this security exploit or 4 actually that mainly involve sideloading a specially designed apk called quadroot, i assume that you already have an idea what this is if you're reading this if not then google it. I read that alot of the time root access exploits are found by finding apps that have root access and exploiting them to install su to the system partition. In this case you could potentially create your own. So my question is why isn't this being persued as a viable option? Pleas let the people who know what their talking about speak and if you have no legitimate knowledge of your own (im talking google cut paste) then just syfm please.
Click to expand...
Click to collapse
Interesting. Will look into it. Will update if I find anything.
*UPDATE*
Checked it out. Useless because we still have locked bootloader. We need SYSTEMLESS root. Anything besides that is useless.

I was under the impression that the bootloader being locked only pertains to trying to install unsigned images, the method used for rooting mm in the same manner as lp would require a modified boot.img and no one has a working system image dump for mm being the reason no one can modify the boot.img. if a app was designed to escalate root access to install super su to the system partition and gain root access that way even temporary we could copy the entire system and make a permanent solution.