I've used Greenify for a long time on my android 4.4.4 nexus 5 phone. Recently, greenify 2.5.1 has been unable to obtain SU privileged. (see attached screenshot from SuperSU).
Greenify doesn’t ask me to grant privileges. I just get an occasional popup notifying me that :
"Greenify silently denied... "
How do I correct this?
I can't find anything in SuperSU that would allow me to add Greenify. What to do?
Please ignore. Problem solved on reboot.
Related
I'm sure the answer to this question is somewhere there, but I cannot find it. There is plenty of information on how to root your phone or tablet, but not on how the root works on Android.
When I work on my Linux box I usually use a "normal", limited user. Only when I need to install something, I switch to superuser, or root, using "su" or "sudo".What happens on a rooted Android? Do all apps run with root privileges all the time? Or rather some sort of "su" command is unlocked, and an app can access it when required. Can I give and revoke superuser powers to an app?
It is always safer to run all programs or apps with limited privileges, so when they misbehave, the risk to system integrity is minimal. If everything runs in root mode, it might just spectacularly crash one day.
In this context, how does adaway work? Does it start with the system, sitting in the background and using its root privileges to intercept and filter incoming HTTP packages? If I understand this correctly, it should then work with any browser?
Sorry for asking several questions in one topic, but I'd appreciate if someone could briefly explain the whole thing.
There is a superuser app, which seems to be doing the same job as gksu does on a linux desktop. Apps can request root, you can allow/deny. If you use the shell, su works as normal (just no password) - but connectbot needs to be given root privileges in order for this to succeed.
Hi XDA Community,
Your forums have helped me in the past and I spent some time scouring the posts before posting this one as I couldn't find anything that was specific to my issue. Since this is my first post, I thought that I would save a ping pong of responses, by being fairly expansive on what the problem is and what I have tried; thus hoping to pinpoint my issue a little quicker.
Device Details:
---------------------
Model Number: GT-I9100
Android Version: 4.0.3
Kernel Version: [email protected] #3
Build Number: IML74K.XWLP3
ROM Firmware: Samsung-Updates.com-GT-I9100_O2U_1_20120326173406_jiut50pyip.zip (via Samsung Kies)
Rooting Method / Kernel: Odin3v185 / CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Summary
--------------
Since the beginning of July 2012, I successfully upgraded from Gingerbread v2.3.6 to ICS v4.0.3 using Samsung Kies then initiated root privileges by using the CF-Root Kernel via Odin (versions shown above) - All has been working fine 100%.....
However, it appears that I seem to have lost my SU permissions and may have disabled my root access, even though my device was rooted and I would appreciate any assistance from anyone who might have time to shed some light on the situation.
Behaviour of Apps I have tried that require root
-------------------------------------------------------------------
SuperSU
SuperSU Pro v0.96 lists in the 'Apps' tab (denoted by a green # symbol) that I have granted all relevant Apps that require SU privileges. This includes AdFree, BusyBox Pro, Root Checker Basic, Root Explorer, SetCPU, Terminal Emulator, Titanium Backup, Triangle Away.
Terminal Emulator
Terminal Emulator displays the following and when I enter the su command at the prompt, I just see a carriage return with a grey block. In other words, I do not see the # symbol denoting I have su privileges.
a/local/bin:$PATH
[email protected]:/ $su
Root Explorer
Root Explorer no longer displays a directory listing and simply displays a pop up from SuperSU after tapping on Root Explorer, "Root Explorer has been granted superuser permission for an interactive shell." then the following message from Root Explorer itself:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on."
Root Checker Basic
Apart from the App stating "Please wait for Root Check to be complete. Systems appears to be running very slow" after tapping on the [Verify Root Access] button. It never seems to provide an output after a few minutes waiting. My conclusion is that it cannot get su permissions.
BusyBox Pro
SuperSU displays the message that Titanium Backup has been given root access, however I get the following message:
"Asking for root rights..."
Then after a few minutes I receive this most enlightening output:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox and try again.
This attempt was made using the "/system/xbin/su" command."
I read somewhere that Titanium Backup uses it's own BusyBox installation and not the system wide BusyBox package so I went in to the Titanium Backup preferences and selected 'Troubleshooting settings' then chose 'Force system BusyBox' to see if my issue was a BusyBox specific problem. Again, it failed so not sure if it is BusyBox or my SU permissions that have somehow got corrupted or been disabled.
Additional Information
-------------------------------
Using 'ES File Explorer', I can confirm that the following file's exist at the appropriate location paths:
/system/xbin/su
/system/xbin/busybox
Conclusion so far
-------------------------
It appears that on the face of it that I have lost my root permissions, so I removed apps from SuperSU, then uninstalled the App (e.g. Root Explorer, Terminal Emulator et al.); then performed the rooting procedure again via ODIN and the CF-Root kernel. The process itself worked flawlessly and so after it rebooted, I installed the Apps in question from the Google Play Store again and they prompted to be granted SuperSU privileges. Unfortunately, the same issues arose where it appears that it cannot communicate with either the su command or BusyBox to do what it requires.
Does anyone have any ideas as the phone is fine apart from this and although performing a Titanium Backup backup around two weeks ago, I would sooner not have to wipe everything if I can help it. I wonder if it is an update that somehow confused things...Either way, I cannot use Titanium Backup to backup/restore due to it requiring SU/root permissions, of which I do not seemingly have anymore.
Any ideas please as I am scratching my head and have gone blurry eyed at spending hours viewing various forums and posts?
follow this steps:
1. Unroot your phone with the unroot method here
2. To be sure, unroot again with the method here
3. ROOT your phone again using Any of the Rooting methods in the links provided in step 1 or 2.
Good luck
ICS 4.0.3 Lost su permissions even though device was rooted - Resolved
:good: Issue Resolved :good:
Many thanks for contributing to my issue. I had come across the post before in your links and although the directions were not completely related, there was a section pertaining to a zip file that I must have missed.
Conclusion
----------------
As can be read in the post, I was unsure if my issue related to losing root, a possible corrupt su file itself or BusyBox. As you will see on the link below, Busy Box actually creates hundreds of symbolic links (symlinks) and due to my perhaps overzelous approach to wanting a quick fix; I must have inadvertently created too many links with different versions of Busy Box and therefore when an App that was correctly added and granted SU permissions within SuperSU, when it then communicated with Busy Box / su to authenticate; I can only imagine it got confused and was lost with all the dead symlinks. The net result was that although SuperSU stated that it had granted permissions to the Apps requiring root, it never got to communicate with the su file contained within /system/xbin. I hope that makes sense, well at least I am pretty sure that is what happened.
Solution
------------
Firstly, I cleared all entries contained within SuperSU and therefore removing all Apps from being granted with root access (they didn't have it anyway at the moment).
I saved the zip file contained at the following link on to my external SD card and choosing to 'install zip from sd card' within the CWM Recovery (Volume Up + Power + Home button); effectively this uninstalls Busy Box completely from your device, including hundreds of symlink files - including many which in my instance was causing issues with Apps that required root to function correctly.
Busy Box Uninstaller v1.0 here
I restarted my device and downloaded Busy Box from Google Play Store and when I opened Root Explorer and the other aforementioned Apps shown in this post, they prompted to be granted root permissions (SuperSU) and voila....it worked ! :good:
I hope this may help other droid users experiencing similar symptoms.
Conflicts? LG P769 rooted V18. Binary update fails, su reports "The ap su (processom.noshufou.android.su has stopped unexpectedly)" then crashes. Until resolved and certain that su will preserve root would like to prevent ph from forcing update. Have read several methods one is to freeze a couple of scripts w/Titanium, another to delete 24MB ip folder 10e>10g in cache and alter Google Framework. Not sure which is the safest or easiest with apps I already have. That's two requests which will be greatly appreciated: One to resolve su binary fail w/possible app conflicts the other to simply stop OTA until I understand Andoid and the apps better.
Installed: SuperSU (non-pro- no survival mode) , Superuser Elite(over vs from Bin4ry), Smanager Elite, OTA Root Keeper, Titanium BU Pro
btw- No response from ph running Bin4ry? Go to redmondpie com "how-to-set-up-android-adb-and-fastboot-on-windows-tutorial" Only way it worked for me. Followed the directions and was able to view my device in command box prior to executing v18.
note: When editing the string as described, redmondpie, +be sure not to wipe out any part of existing script+ (hit end , blue box turns white). Copied and pasted extracted bin4ry "stuf' in a folder labled Andoid-adb set up in adb environment. Root executed from there first try after dozens of failures w/other methods.
>>not sure if I have valid root restore tools should OTA (already in cache) executes<< >>Meanwhile, which method to prevent OTA execution<<
notes from apps
root checker basic verifies root; voodoo all boxes checked, protected su copy available but note "using both su and SupersSU take care keeping app and su bu consistent" (should not be issue since not the pro vs of SuperSU - no ota survival). edit just started to rept "sys running very slow-pls wait for r-ckr to cmplete.
Superuser elite v3.1.3(46) (downloaded over Bin4ry incl vs) shows no apps, no log, o entries Binary updater fails, "The ap su (processom.noshufou.android.su has stopped unexpectedly" then crashes. "bu written to sd card"black box flashes to say su has been granted superuser permission interactive shell access; access timeout aps not remembered set to 0; auto response set to prompt; ghost mode off; ...
SU updater reports "sigs ok"
SuperSU v0.96: all green # today (but not yesterday); superuser enabled; surv mode not avail (not pro);
Titanium BU Pro root ccess ok, busybox 1.19.4-titanium from ap ; sqlite- yes 3.7.6.-titan incl; All green checks on overview pg; has quite a few red line entries, probably hven't left ph on long enough for bu to complete
; active data pofile- sys rom 1.03gb ; internal 1.93/1.46 free note down from 1.7 when new.
Smanager reports root access Can this app delete cached ota update zip?
Did I err in downloading elite vs of Superuser over the copy already inserted by Binr4y? Thanks.
I'm pretty sure this is the latest version of SuperSU, but every time I reboot my phone I get a message that reads: "The SU binary needs to be updated!", and when I click on the prompt to update it, it always fails and asks me to reboot.
Has anyone else run into this issue, or know how to resolve it? Thanks.
SuperSU APK and the SU binary are two different things :
SU is a binary executable, it's used by Android and other *nix based systems to allow a process to change the user it is run by and therefore what the process has the rights to do (as it inherit the user permissions). In the rooting case, processes invoke SU to switch to the root user therefore acquiring root permissions.
SuperSU is an Android application (.apk is an Android application package), it works as a sort of "gatekeeper" to the SU binary. Applications which attempt to invoke SU will be forced to route through SuperSU, which will then prompt the user with the options of approving or denying the access to SU (and optionally having SuperSU remember their decision and automatically apply it for subsequent calls by that app).
So what happens to you is, every time you boot, SuperSU v2.78 (which is the latest version of the SuperSU APK) checks the SU binary version and tells you that there is a newer version of it and that you should update it.
Then for SuperSU failing to update the SU binary I can't help as for me it always worked till now. But maybe there is a way to manually do it (by finding the binary in a flashable zip that you can flash in recovery)?
bafforosso said:
SuperSU APK and the SU binary are two different things :
SU is a binary executable, it's used by Android and other *nix based systems to allow a process to change the user it is run by and therefore what the process has the rights to do (as it inherit the user permissions). In the rooting case, processes invoke SU to switch to the root user therefore acquiring root permissions.
SuperSU is an Android application (.apk is an Android application package), it works as a sort of "gatekeeper" to the SU binary. Applications which attempt to invoke SU will be forced to route through SuperSU, which will then prompt the user with the options of approving or denying the access to SU (and optionally having SuperSU remember their decision and automatically apply it for subsequent calls by that app).
So what happens to you is, every time you boot, SuperSU v2.78 (which is the latest version of the SuperSU APK) checks the SU binary version and tells you that there is a newer version of it and that you should update it.
Then for SuperSU failing to update the SU binary I can't help as for me it always worked till now. But maybe there is a way to manually do it (by finding the binary in a flashable zip that you can flash in recovery)?
Click to expand...
Click to collapse
Thank you for explaining the difference for me. I went ahead and downloaded the .zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/page8
And then used the installation instruction found here: http://androiding.how/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
And I don't seem to be getting the prompt that SuperSU needs to be updated anymore.
Huh. Never mind. Seemed to work for about 12 hours, but now it's asking me to update again, and I can't. Looks like I need step-by-step instructions on how to clear this message, cause whatever I'm doing isn't doing the trick.
Did you disable Sony RIC and dm-verity when you modified the kernel? I'm not sure if it has anything to do with or whether it will solve your problem, but one time I patched my kernel leaving one of the options enabled and ran into all sorts of problems with apps that required root, so after that horrible experience I decided to just disable everything. During that horrid experience, I think I also had SuperSU (or was it busybox?) complain about not being able to update binaries.
I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?