If anyone is being prompted to update binaries and getting an error while attempting to update the binaries on Super SU like I did, here's a fix/workaround for now so your precious root apps (like WiFi Tether) keep working.
The reason you are having issues all of the sudden is because there was a recent update for Super SU that for some reason isn't working with our phones. If your Play Store app is set up to update apps automatically, then you likely already have the newest Super SU update installed. Because the new updated version will not update binaries properly when first opened, you are going to have issues with your root apps, and may not even be able to open the Super SU app anymore unfortunately.
Here's what worked for me:
1) Uninstall Super SU in settings (the older version is still there don't worry).
2) Turn off WiFi and data.
3) Go into the Play Store and turn off auto update apps in settings.
4) Reboot
5) Go into Super SU and make sure the update binaries prompt no longer appears. You should also be able to fully open Super SU again too.
6) Turn data and or WiFi back on.
7) Smile
Viola! All of your root apps should now work properly again after you grant permissions.
Enjoy
Sent from my EVO using xda app-developers app
I have CM10.2 with Googy max kernel and latest SuperSU. When I'm running some apps (restart camera, some tasker tasks, etc) Supersu automatically denied root permission without promoting. But some apps it work (ROM manager, ROM toolbox, root checker, triangle away, etc. ). Then I use its full unroot option and reboot and again flash supersu zip. But no luck.
I can't see root permission deny apps list. Supersu only show allow app list.
But if I use "grant" (in Access) then there's no issue. I face this issue only if I selected "promote" option with some apps.
How do I fix this issue?
Sent from my GT-I9300 using Tapatalk
Hi! Guys i am facing a awkward problem
My Device-Samsung Galaxy Ace GT-S5830I aka Cooperve
ROM-ACEJB 2.0 BY BRIJESHP(Stock Based Custom Rom 2.3.6 GINGERBREAD XXLA1)
Kernel-Thunder Kernel 2.6.35.7(Custom Kernel already rooted with busybox)
I have SuperSu v.2.4.7 By Chainfire to manage my root access!
But the app crashes several times so i decided to use another superuser app!
I saw there is an option in supersu called "Switch to another superuser app"
I clicked on it after it is done! I rebooted and installed Superuser by chainsDD
and uninstalled supersu.
I opened root validator to check everything is ok or not.
It said everything is ok!
But suddenly strucks on my mind there is no prompt opened for granting superuser permission(ALLOW\DENY)then how could the app gets root permission!
I opened apps like nofrills cpu control,rom toolbox,link2sd,swapper for root and some other root apps they are working fine but there is no prompt to allow or deny showing up!
I opened superuser by chainsdd it said su binary found and showing its location in green colour!
But in apps sections no app is showing there and logs are also empty.
wHICH strucks me most!
I uninstalled superuser by chainsdd.Now i have no supersuser app but still root apps are working and getting root permission
HOW IS THIS POSSIBLE?
PLEASE HELP ME!
If i will not fix this my device will became vulnerable to threats!
(sorry for my english)
Newest stable version works but doesn't ask for root privilege. Rooted using Chainfire's supersu.
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Sent from my Sony Xperia SP using XDA Labs
Which settings require root? I've toggled all the settings and none of them made it ask for root.
olliebean said:
Which settings require root? I've toggled all the settings and none of them made it ask for root.
Click to expand...
Click to collapse
For me it asked for root when I changed settings under "wake up tracking and cut off".
If nothing happens to you reboot your phone and try again, you could also check to see if there is any denied requests of greenery in super su app and manually grant it.
Sent from my Sony Xperia SP using XDA Labs
ghst7 said:
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Click to expand...
Click to collapse
Oh it works just fine. It's just not showing up in Supersu as having root access.
I have the same problem.
After I updated from the market today I can't get greenify to properly request root access.
When I run it I tell it I'll rooted, see it saying it's requesting root access but supersu doesn't prompt then says it can't get root. Same results with rebooting.
In supersu there are no request prompts from greenify. I deleted the greenify access to see if that would get it to reprompt but it still says can't get root and supersu shows no requests in logs.
Other apps still work fine in supersu.
Edit --
Interesting, I disabled the module in xposed and when it prompts for root supersu pops right up. So I gave it access that way but logs show that once the module is reenabled it never asks for root.
Weird
Can't get root privilege
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Got mine to work by deselecting Greenify module in Xposed and rebooting. Started Greenify app and it said to either to activate the Xposed module or select non-root mode. I clicked on Greenify settings and tried to change Xposed settings and a popup window asked if I wanted to activate Xposed module. I selected yes, Xposed started, I selected Greenify module and rebooted. During the bootup process, Greenify asked for root permissions.
A similar process worked for me: deactivated the Xposed module, rebooted, started the Greenify app, then I went into the Greenify settings and turned on the enhanced wake up tracker, which caused Greenify to request root. Granted permission, then reactivated the Xposed module and rebooted again. Checked in SuperSU that Greenify had permissions, then I just had to re-enable the Xposed based features in the Greenify settings.
Having done that, however, I see from the SuperSU logs that Greenify isn't actually requesting any root permissions since I re-enabled the Xposed module. I suspect the new version is using Xposed for all its root access and no longer needs root permissions for the app in Boost (Xposed) mode.
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
dreinulldrei said:
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
Click to expand...
Click to collapse
Read prior posts for further guidance. Seems others have got it to work. I had zero/nada/no problems on latest betas w/Xposed and SuperSU 2.76. YMMV.
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
dreinulldrei said:
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
Click to expand...
Click to collapse
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Davey126 said:
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:43 PM ----------
This page has a link to the SuperSU v2.76 zip on ChainFire's site, which can be flashed with TWRP, etc depending on your phone.
https://www.progeeksblog.com/download-supersu-for-android/
I have not tried to flash it myself.
divineBliss said:
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Click to expand...
Click to collapse
If life is good don't change anything! I'm not out to skewer SuperSU v2.78; the problems I and a few others experienced are likely outliers with various contributing factors. That said, SuperSU 2.76 has been rock solid on my devices as have most of ChainFire's previous releases. Sticking with what works for now.
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
craigevil said:
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
Click to expand...
Click to collapse
divineBliss said:
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
Click to expand...
Click to collapse
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
I don't think you can do anything to the SuperSU configuration to make it so apps in priv-app have to ask for SU permission. I have other apps in there and have never seen them ask and they are not in SuperSU log either.
I moved my Greenify apk into priv-app because it wasn't clear to me that there was nothing to gain by doing that as I already had Xposed installed and working. Have since moved it back to original folder in /data/app/.
Davey126 said:
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
Click to expand...
Click to collapse
- Android 6.0.1
- SuperSU 2.78 (systemless root)
- Xposed
- latest Greenify Beta from PlayStore (in Root+Boost mode)
- NOT installed as system app or anything.
Same problem here -- Greenify never asks for root, is not listed in SuperSU logs. Greenify initially had root access iirc, but one of the updates from PlayStore removed it.
Nevertheless Greenify seems to be working fine though.
EDIT: All other root apps on my phone (OnePlus 2, stock OxygenOS 3.1) don't have any issues with root access.
Sent from my OnePlus 2 using Tapatalk
Sometime I miss popup of Granting 'root access" for given app. Is it possible to grant root access outside this popup?
I think it might be after update of Magisk that I cannot save "Grant root" timeout option. There is something wrong with latest update I guess.
I've had the same problem with Magisk 22.0 on LineageOS 18.1. I missed the 10 second timeout whan starting aLogCat, and now it keeps reporting 'aLogCat ROOT was denied SuperUser rights'. Upgrading to Magisk 22.1 doesn't change things.
I understand 'New v22.0 update merges Magisk and Magisk Manager app' (https://www.androidpolice.com/2021/02/24/new-v22-0-update-merges-magisk-and-magisk-manager-app/). So how does one go about granting root access after the first prompt is missed?
EDIT: SOLVED: Doh, I just spotted the toolbar at the bottom of the Magisk screen! Strange that it doesn't seem to be mentioned in any documentation I found...