[Q] What gives you root? - AT&T Samsung Galaxy S II Skyrocket SGH-I727

What part of rooting a phone gives you root?
Does installing CWM recovery enable root access?
Or does installing the superuser.zip file give it?
In other words, what is preventing you in a stock system from obtaining root?

daystrom said:
What part of rooting a phone gives you root?
Does installing CWM recovery enable root access?
Or does installing the superuser.zip file give it?
Just trying to have a basic understanding of the process and how it works.
Click to expand...
Click to collapse
CWM is just recovery, it is NOT root
rooting is simple. people think of it as some voodoo, but its not.
when you root, you are adding 2 files to your /system
/system/app/Superuser.apk
and
/system/bin/su
su is the binary that allows Superuser.apk to grant root permissions to you the user, or to an app that is requesting it (assuming you grant the permission when prompted)
rooting isnt some magical process, it actually has nothing to do with anything OUTSIDE of the OS.
if you use CWM to flash a rooted rom, then you have root in that rom.
if you use CWM to flash a non-rooted rom, then you will not have root, plain and simple. you will still have CWM, but no root.
the 2 items (cwm and superuser/root) are NOT equivalent

Great info!
What is stopping you however from adding those files to a stock system? CWM recovery has to be installed first to install the su files. Why?

daystrom said:
Great info!
What is stopping you however from adding those files to a stock system? CWM recovery has to be installed first to install the su files. Why?
Click to expand...
Click to collapse
if you are booted into CWM you have read/write access to /system which allows you to add the necessary files for you to gain root access.
if you are booted into the OS, /system is mounted as read-only and you would have to rely on an actual exploit of the OS in order to 'temp-root' so that the rooting tool can gain the read/write access it needs to inject the root files. since 2.3.6 fixed all the current exploits CWM is required for rooting, until someone finds an exploit in 2.3.6 that allows them to gain that temp access .
you can completely add those files to a stock system, assuming you install CWM or are on an android version < 2.3.6
on 2.3.5 you could use the zergrush exploit to get permanent root without having to flash anything in ODIN to gain CWM...in fact, on 2.3.5 you can root your stock system and never even install CWM or go any farther than rooting it.

Awesome, I appreciate your knowledge!

Pirateghost said:
if you are booted into CWM you have read/write access to /system which allows you to add the necessary files for you to gain root access.
if you are booted into the OS, /system is mounted as read-only and you would have to rely on an actual exploit of the OS in order to 'temp-root' so that the rooting tool can gain the read/write access it needs to inject the root files. since 2.3.6 fixed all the current exploits CWM is required for rooting, until someone finds an exploit in 2.3.6 that allows them to gain that temp access .
you can completely add those files to a stock system, assuming you install CWM or are on an android version < 2.3.6
on 2.3.5 you could use the zergrush exploit to get permanent root without having to flash anything in ODIN to gain CWM...in fact, on 2.3.5 you can root your stock system and never even install CWM or go any farther than rooting it.
Click to expand...
Click to collapse
OK sorry just to clarify if we used a oneclick method to root that utilizes the zergrush exploit on 2.3.5 then we will be able to get the ICS OTA update when it comes next year?
All I did was follow the instructions provided on this link:
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
which says that the root method i used is: "This is why, Shabbypenguin and the team at Android Creative Syndicate have brought us the Easy Root for the Skyrocket. The script, uses the brilliant zegrush exploit and will have your device rooted in no time."
After rooting I used bloat freezer to "freeze" bloatware because i've read elsewhere that completely uninstalling could prevent you from getting OTAs correctly.
Sorry I'm such a noob at this...

You need stock recovery and bloatware can be frozen but not deleted
---------- Post added at 03:36 PM ---------- Previous post was at 03:33 PM ----------
Thats all. You dont have to use the oneclick to be able to get an ota. You . can use the odin method then flash the stock recovery.tar. its so simple. You can root use cwm recovery then if theres an ota just odin the stock tar. And u can take the ota

Related

[Q] Can I get SU on a stock ROM?

I need root access via shell. I have seen su apps out there that require a rooted phone. I don't want to muck with my ROM other than to gain root access via shell.
Are there any free packages that I can install to do this?
unrevoked 3. Follow those steps to root. Very easy. Ounce u have s-off ur rooted on stock Rom. But trust me ounce u root your gonna wanna learn more than just using SU apps.
r0cky.Da.3v0.SU
Thanks, that got me what I wanted and more. I ran the backup from the recovery boot. Where did the backup get written to?
No problem. It was written to the SD clockworkmod folder.
r0cky.Da.3v0.SU

New How to Install Video!! Rooting with the OTA Gingerbread...

Just finished up posting a video on rooting with the new OTA updates of Gingerbread 2.3.6. Let me know if you need help. Read the show notes first and backup everything!
Dave
Video:
http://www.youtube.com/watch?v=zzJE...xt=C326a0c8UDOEgsToPDskJD2AQiktg6frnsdEWSNuJH
Channel:
www.youtube.com/kraisydave
Thank you for this Sir!
This will help for when I obtain root on my bro-in-law's D.C.
Sent from my Incredible 2 HD using XDA App
Technically speaking, you don't have to load an entire OS ROM via ODIN.
All you really have to do is download the SuperUser Pack, install CWM, flash the SuperUser Pack in CWM, and then you'd be rooted.
Then, once you're rooted you would then go into Root Explorer, find a file called "install_recovery.sh" in /system/etc and then change the permissions of the file so that it doesn't have Executable permissions, and then go back to install CWM (again) and you'll have permanent CWM.

[Q] How do I temporarily "unroot" device?

Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Questions belong in Q&A. Moved
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?
vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.
cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday
There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0
Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.
I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds

Need experienced dev help w/ adb root vs. flashing *.tar (/system) root through Odin

I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you
Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S

Just me or Voodoo Doesn't work?

I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.

Categories

Resources