Database Info

S-OFF But not rooted?

Do I need to do something else? I used Alpha what ever its called, all wen't fine, S-OFF but tried Titanium back up and am told it needs root access, tried screenshot and it wont work?

Tried the process again but it won't let me, says I already have S-OFF

You need to root the phone first using Gingerbreak.

You need to use ginger break http://forum.xda-developers.com/showthread.php?t=1044765

det66 said:
You need to use ginger break http://forum.xda-developers.com/showthread.php?t=1044765
Click to expand...
Click to collapse
It all seems very complicated

slugger09 said:
It all seems very complicated
Click to expand...
Click to collapse
Not at all mate. Just download the gingerbreak .apk file to your sd card, open it & it will install gingerbreak on your phone. Then once this is done go to the gingerbreak app and run it. It will root phone but you will need to do a manual reboot afterwards. Don't worry if it says something along the lines of things went wrong, just go ahead and reboot.
Peace

All you do is download and install it then click root in the app then reboot the device you should get an error before you do a reboot then you should see super user then go to rom manager cwm
slugger09 said:
It all seems very complicated
Click to expand...
Click to collapse
Sent from my HTC Desire S using XDA App

S-OFF allows you to obtain root access. In Linux terminology, root is a user with total permission over the machine. In terms of Android, all you need to know is that it's the Superuser app and a binary (executable file) called su, that needs to be installed in the /system partition. S-ON disallows you from touching the /system partition. So even though you turned off security, you didn't actually install su and Superuser.
FYI: Su is not an application, it's a command.

All done now. Thanks for your help.
Sent from my HTC Desire S using XDA Premium App

[Q] Wrong SU Permissions Warning in TB

Hi,
I rotted my phone on 2.3.5 and followed manual upgrade process to get 2.3.6 and indeed it worked fine with keeping root.
Of late, when ever I run TitaniumBackup it give me warning as
"Your ROM is rooted but SU binary has non-optimal access rights, which may cause problems
Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed? "
When I say "Yes. do it", it gives me message as
"Access rights on "SU" binary was succesfully corrected from "0:0:[4755]" to "0:0:6755" " and asks to restart for apply changes.
Once it restarted it didn't seems to apply changes and asks me same question when I re-open TB.
I understand it has something with access rights files but not sure how to fix this. [we moved SU to diff path to keep root, is that causing issues?] Can someone help me.
Thank you.

Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?

Shaliuno said:
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Click to expand...
Click to collapse
I think so, used below method.
go to /system/bin/
open in text editor – mount_ext3.sh
add the 3 following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
I did used ES File explorer to perform this. I also read posts mentioning the problem because of ES, how ever I performed this earlier even before complaints and never had problem as it stayed Rooted, so left as it is.
I also installed SU updated from market as I had problems with updating SU binaries.

Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it

Shaliuno said:
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Click to expand...
Click to collapse
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.

sazhagianambi said:
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
Click to expand...
Click to collapse
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.

Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad

Thank you!
jimbridgman said:
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Click to expand...
Click to collapse
Thank you Jim for clearing up, may be I should setup ignore warning then.

Shaliuno said:
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Click to expand...
Click to collapse
TB can and has messed up backups, frozen apps come unfrozen at the worst times, it has a minimal busybox, it has broken root before, it is just more of a headache than anything else... there are several apps that will give much better results.
For freezing apps, try modaco's eazy freezy
For backups, use ROM manager, way more successfull, and VERY stable and tested, and the backups it uses are the same that most manufactures deliver in the fxz and updates, since they are saved in img files, and they can be restored from a default recovery if you really are stuck, and can not even get into it on boot...
For busybox, there are two really good ones, I personally use busybox installer from JRummy16, also the one from Stephen (stericson) is really good too, and I have used it, but had an issue with a version several versions ago, and switched.
I am not bashing TB in any way, so no flames, if you like it.... This is just my experience and I have been using android since 1.4-1.5 version, and I have seen a lot of things....

[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

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.

Can you get ad blocking to work?

I recently got a Mini, took the system update fresh out of the box since I knew there was a root method for it, and then rooted it.
None of the ad blocking apps work on this phone. I'm thinking that /system is read only, so they can't change whatever file they need to. I've tried rebooting into recovery- just seems to boot normally, but from what I've read, with the previous root method this would set /system to RW. No difference though. Any suggestions? Am I missing something basic?

jjlangen said:
I recently got a Mini, took the system update fresh out of the box since I knew there was a root method for it, and then rooted it.
None of the ad blocking apps work on this phone. I'm thinking that /system is read only, so they can't change whatever file they need to. I've tried rebooting into recovery- just seems to boot normally, but from what I've read, with the previous root method this would set /system to RW. No difference though. Any suggestions? Am I missing something basic?
Click to expand...
Click to collapse
I use adaway and droid mini. It works well. Maybe you didn't root a phone or reboot into recovery

Just ran the tool to disable the /system write protect, reinstalled, and it's working fine now.