I'm getting permissions issues whenever I try to run any root apps. I get a message like this: "SetCPU could not obtain root access. Did you allow SetCPU through Superuser Permissions? Operating in read-only mode." Everything is set to "allow" in Superuser, and I have tried rebooting into recovery and clicking "fix permissions." It tells me that permissions were fixed, but when I reboot, the problem persists. I'm on the latest Synergy. What do I have to do to get my phone back to normal?
SamOliver said:
I'm getting permissions issues whenever I try to run any root apps. I get a message like this: "SetCPU could not obtain root access. Did you allow SetCPU through Superuser Permissions? Operating in read-only mode." Everything is set to "allow" in Superuser, and I have tried rebooting into recovery and clicking "fix permissions." It tells me that permissions were fixed, but when I reboot, the problem persists. I'm on the latest Synergy. What do I have to do to get my phone back to normal?
Click to expand...
Click to collapse
Sounds like maybe SuperUser is still denying these apps (although a user would have to tell super user whether or not to allow a root app). Run Super User and delete these apps from the list and re run the problem app and set allow again.
Sent from my brain.
baronmxc said:
Sounds like maybe SuperUser is still denying these apps (although a user would have to tell super user whether or not to allow a root app). Run Super User and delete these apps from the list and re run the problem app and set allow again.
Sent from my brain.
Click to expand...
Click to collapse
That didn't work, and when I try to update Superuser the last thing it says in the log is "Gaining root access... fail!"
I'm gonna re-install my ROM and see if that does the trick.
EDIT: I think it might have gotten messed up when I pulled the battery out when it was booting. In case anyone has the same issue in the future, I just flashed my ROM again (right on top of the old one) and it fixed the problem.
I've had that issue with shootme since superuser/su updated last, but haven't bothered to really look into it since cyanogen has screen shot built into it.
So I'm having a very strange issue. I'm on a rooted stock NC5 ROM (original) and every once in a while I get a superuser request for Android System (System_user_x) x as in a number. At that point my screen becomes unresponsive to touch for about 5 minutes. Any ideas what's going on?
Exleh said:
So I'm having a very strange issue. I'm on a rooted stock NC5 ROM (original) and every once in a while I get a superuser request for Android System (System_user_x) x as in a number. At that point my screen becomes unresponsive to touch for about 5 minutes. Any ideas what's going on?
Click to expand...
Click to collapse
I had the same problem. I performed a factory reset, and after a Titanium Backup I wasn't able to allow the Android Process Superuser permission. I wound up fixing this by deleting the superuser app from /system/apps disabling wanam xposed module (the long press back kill mod was what started the issue) and then re installed superuser. I had the pro edition, so I hope it won't make a difference on your end.
After I re-enabled the wanam xposed and didn't have a problem. (obviously this removed all the saved permissions like TiBackup and ES explorer, but they aren't hard to re-enable.
Hope this helps.
So after a new rom flash I ran into the same problem. A quicker solution would be to go into SU and set the default permission to "grant" access. After this, run the process which requires the access, and once access is granted, switch the setting back to "prompt".
Hello,
I have a Samsung Galaxy S6 Edge SM-G925W8 and had SuperSU root access and XPosed Framework installed. I am now attempting to remove all of it so that I can pass Google's safetynet helper test. I have tried numerous things, but the safetynet result is always:
SafetyNet Request: Success
Response Validation: Success
CTS Profile Match: False
I first attempted to remove Root by clicking "Completely remove root" within SuperSU. After doing this, Response Validation was false, which, after doing some research, I learned was caused by XPosed Framework. I then boot into TWRP recovery and flash the Xposed uninstaller. This causes my phone to boot loop, forcing me to restore a NAND backup to before I removed anything. I then try to flash the XPosed Uninstaller BEFORE removing root access and it runs successfully. After this, I use SuperSU to completely remove all root, which also runs successfully then give the phone a reboot removing the app entirely. This is when I receive the SafetyNet Helper response above stating CTS Profile match is false. I'm not sure how to fix this error.
Any suggestions would be very appreciated! Thank you
Edit: I have no idea why this thread appeared twice...sorry I can't seem to delete one of them
Er.. Any ideas?
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
vgplayer54 said:
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
Click to expand...
Click to collapse
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hello, I attempted to use ES File Explorer to search both the system/bin directory and the system/xbin directories. system/bin does not have the "busybox" or "su" files in them, so I assume they were removed when I uninstalled SuperSU. /system/xbin however does have these two files, but I am unable to delete them. I get the error "Cannot delete file". I'm guessing this is because I've already unrooted?
I then opened the terminal in my TWRP Recovery, however when changing directories into the system folder, the terminal shows that it is empty. when using ls -la, only two files are there, both called root and neither can be opened. rm -r /system/xbin/busybox does nothing either, it claims there's no such directory. Any suggestions? or just wipe?
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
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?