Before you just delete this post I want to say what I EXACTLY want to know:
What does it need that the ROM signs me in as root? I don't want to know how to flash one of these ROMs like Cyanogen or something, but I want to know what I have to change in my ROM that it logs in as ROOT!
So if there is a post already, just tell me WHERE. Because when I search for "how to root" or something like that I get those flashing guides.
I hope you can help me.
Best regards,
b!rust
http://forum.xda-developers.com/showthread.php?t=581819
Hi, you said you flashed your phone with the ION rom, correct? Well, download the SDK and follow the instructions in dferreira's first post detailing how to obtain root
Yeah! That's right. But I wanted to know, how I can do that in general.
And I'm a bit confused, because after I did it like it was said in the thread you mentioned and I type
Code:
su
id
in the console (Terminalemulator.apk and also via adb) it doesn't say I'm root.
//edit: in Terminal Emulator it says I am user "app_38" in the group "app_38". In the adb shell it says that I'm user "shell" in group "shell"...
What does it say in the terminal? Because as far as I know, root uid is 0, and mine isn't listed as such. I'm not 100% sure, because I'm also new to this, but I think that regardless of whether it shows or not you are indeed root.
For example, to test root on my phone I took a few screenshots of my phone using the app "drocap2" which requires root. I also was able to flash a new bootscreen image etc
Yeah that's right uid 0 is root and that's what confused me. But when you say that you can run apps that require root... I will test it in a sec.
How did it go?
Edit: I think actually you need to enable local root for using a terminal and such (instead of going through the recovery/adb shell).
http://android-dls.com/wiki/index.php?title=Magic_Root_Access
But don't quote me, just picking it up as I go
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
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
Hello All,
I am trying to figure out some way to manually start an app as root. It seems that apps which "require" root privileges are coded to elevate to root using su. However, what I would like to do is manually start *any* app as root - even an app that does not "require" root privileges. For anyone familiar with Linux or Unix, this would be similar to running 'su -c /usr/bin/myapp' (or less so, but also similar to running 'sudo /usr/bin/myapp'). In Windows this would be like using 'runas /user:Administrator myapp.exe'. Specifically, what I would like to do is open my text editor as root, so I can modify my hosts file. I needed to change this today, but was not near a computer, and therefore I could not use ADB. I finally gave up trying to figure it out and simply used Vi from the terminal, which is fine when using ADB, but quite difficult when actually using the phone. I could not find many questions (or answers) about doing this, and the few posts I could find, I get the impression that those who replied did not fully understand what the OP was asking. If my question does not seem clear, please let me know and I will try to rephrase it. I very much appreciate any insight. Thank you.
Hello! So this should be an interesting first post. First, a little background:
I'm relatively new to this, and I've been trying to root my NEC Terrain for a little while now. I've followed the instructions on numerous pages in order to understand how to do things. And now I have been able to rip any partition from the phone. I've looked through everything I could in both the boot and recovery partitions but I haven't found anything I can use (I also explored /system but there doesn't seem to be anything in there either). Also, I tried to do everything on this page: http://forum.xda-developers.com/showthread.php?t=2337642 but I can't get SuperSU or TiBu to work. (As an aside, if anybody can point me in the right direction for the most recent su binary, that would be awesome). SuperSU wants to update the binary but fails. I would assume it's because it tries to install it directly into /system/bin, which isn't writable. If I could make it install it into /data/sbin, it might work, but that's off topic right now.
I would like to explore more of the partitions to understand what they are and what they do (I can't seem to find much information about them anywhere). I'm hoping to find something in the code to give a hint as to how to get into the bootloader. So, I have things like "aboot", "firmware", "MM", and "GROW", among others. Is there any way to decode or decompile those images so I can see what coding goes into them? Am I going about this the wrong way?
Thanks in advance to anyone that can help!
Maybe this will help you
In this post by E:V:A you can find some information about partitions and links to more!
I think latest SuperSU should be with latest SU binary (I can be wrong about this), so you could download "CWM / TWRP / MobileODIN installable ZIP" from this post and take one from "x86" folder.
Good luck.
Thanks for the links! Some of these may be very helpful. However, the su binary I got from that link was much older than the other most recent I had. It's a version 2.0 and they're up to at least 3.2 (I'll check the link again to see if I missed something). Also, for these phones, if anybody is wondering, they are ARM, not x86.
There seems to be only one direction I can go with this: Find an exploit that can run at boot that will interrupt it at the right time and allow editing of the /system partition. I can get a root shell with that script and a bind mount, but it's not enough to get anything else to work (ro.secure is still active, so there's no way to change it after the system is booted). Root is granted to root, and that's all. Any app requesting root does not get it.
The guys on that other thread said they got SuperSU and TiBu to work, but they provided very limited information and I can't seem to make them work. I wonder though, if that would matter as long as ro.secure is still enabled.