I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.
Related
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.
Hi, when cwm SuperUser done a update to app and binaries the root not work in my device, can someone give me SuperUser cwm.apk v0.9 or some work please, i searched but I didnt found
fernan2001 said:
Hi, when cwm supersu done a update to app and binaries the root not work in my device, can someone give me supersu cwm.apk v0.9 or some work please, i searched but I didnt found
Click to expand...
Click to collapse
http://download.chainfire.eu/204
r
Very thanks for answer, but the link is a .zip and I want an apk or can I put it (.zip) with default recovery and not have problems?
Extract that zip, apk is in there
Tapped from my RazR
DumbleCore said:
Extract that zip, apk is in there
Tapped from my RazR
Click to expand...
Click to collapse
thanks now I understand I dont knew that...but the apk is not that, I tested that app and not worked because I dont have root chainfire installed , the super user that I have is SuperUser of ClockworkMod, I need a previous version.
fernan2001 said:
thanks now I understand I dont knew that...but the apk is not that, I tested that app and not worked because I dont have root chainfire installed , the super user that I have is SuperUser of ClockworkMod, I need a previous version.
Click to expand...
Click to collapse
Look man, superuser is ROOT. Either your phone is rooted or it is not. A rooted phone can run apps that require it like ClockworkMod ROM Manager, Titanium Backup, Greenify, Wireless Tether for Root Users, File managers like Root Explorer or ES File Manager if you want to be able to access the system areas of the phone. So far as I know, there is no "SuperUser of ClockworkMod". If your phone is rooted (You will see superuser or "Super SU" in your app drawer. Here is a free app from the playstore that will tell you if your phone is rooted or not.
Root Checker
Install it and use it to see if your phone is still rooted or if you lost root somehow. If you still have root, then when CWM starts, it will ask for root privileges and the first time it asks, you will be prompted to grant it, once, for a certain time period, or forever. For stuff like CWM, root file managers, and Titanium Backup, you always grant root forever and you will not be asked again until the app updates and requires you to okay granting root privileged or not, then you grand forever and leave it alone.
If you find out you do not have root or lost your root, then you have to root the phone and the procedure is different for different devices, versions, and ROMS. For that kind of help, you have to search for rooting <your particular device and android version number>
Ohmster said:
Look man, superuser is ROOT. Either your phone is rooted or it is not. A rooted phone can run apps that require it like ClockworkMod ROM Manager, Titanium Backup, Greenify, Wireless Tether for Root Users, File managers like Root Explorer or ES File Manager if you want to be able to access the system areas of the phone. So far as I know, there is no "SuperUser of ClockworkMod". If your phone is rooted (You will see superuser or "Super SU" in your app drawer. Here is a free app from the playstore that will tell you if your phone is rooted or not.
Install it and use it to see if your phone is still rooted or if you lost root somehow. If you still have root, then when CWM starts, it will ask for root privileges and the first time it asks, you will be prompted to grant it, once, for a certain time period, or forever. For stuff like CWM, root file managers, and Titanium Backup, you always grant root forever and you will not be asked again until the app updates and requires you to okay granting root privileged or not, then you grand forever and leave it alone.
If you find out you do not have root or lost your root, then you have to root the phone and the procedure is different for different devices, versions, and ROMS. For that kind of help, you have to search for rooting <your particular device and android version number>
Click to expand...
Click to collapse
Thanks for answer, well I thinked that too, because my phone cant use root privileges if the aplication superuser isnt installed, however with te superuser aplication my phone have root privileges but with the previous version, with actual version my phond dont have root, even the people in google play say the same "with the new version my phone losed root" and similars comments...
maybe the root version (clockWorkMod) work in this way and need the app for work.
maybe this one??? http://d-h.st/l91
DumbleCore said:
maybe this one???
Click to expand...
Click to collapse
Thanks DumbleCore! I have root again
fernan2001 said:
Thanks DumbleCore! I have root again
Click to expand...
Click to collapse
Solved it? No problem
Hey, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and there's no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I don't know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
brewsterj98 said:
Hey, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and there's no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I don't know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
Click to expand...
Click to collapse
i have never used this phone even never shown but i am trying to help you
i think you should change the superuser app that you are using
download the latest version of super user
Vaibhav Chauhan said:
i have never used this phone even never shown but i am trying to help you
i think you should change the superuser app that you are using
download the latest version of super user
Click to expand...
Click to collapse
thank u! u are the only one out of 50 people who's viewed this that's even attempted to help.
I am currently on the latest superuser app and i've also tried Super su as well and both do not do anything.
brewsterj98 said:
thank u! u are the only one out of 50 people who's viewed this that's even attempted to help.
I am currently on the latest superuser app and i've also tried Super su as well and both do not do anything.
Click to expand...
Click to collapse
why don't you try too reroot your phone
Vaibhav Chauhan said:
why don't you try too reroot your phone
Click to expand...
Click to collapse
I just rebooted and it didnt change anything
brewsterj98 said:
I just rebooted and it didnt change anything
Click to expand...
Click to collapse
lol..
i'm not saying to reboot
i'm saying to root it again(reroot)
Vaibhav Chauhan said:
lol..
i'm not saying to reboot
i'm saying to root it again(reroot)
Click to expand...
Click to collapse
oh xD well i tried that and it still wont give anything permissions. when i try to go into root explorer it says " cannot obtain root" then it gives me a error saying "char* ttyname(int)(3) is not implemented on android". i couldn't find anything on google about the error either.
brewsterj98 said:
oh xD well i tried that and it still wont give anything permissions. when i try to go into root explorer it says " cannot obtain root" then it gives me a error saying "char* ttyname(int)(3) is not implemented on android". i couldn't find anything on google about the error either.
Click to expand...
Click to collapse
sorry i don't know about the rooting method of this device
Vaibhav Chauhan said:
sorry i don't know about the rooting method of this device
Click to expand...
Click to collapse
i rooted by SRSroot first then first got the error then i unrooted and re-rooted by using the kingo root method but still received the same error. they are both windows programs u can run for root on multiple devices. They use USB debugging to root then device reboots and bam your rooted.
i used those methods because i tried to just flash the binary files through cwm recovery and it never actually installed into system. The two methods above installed binary and rooted my device but i cant give root access to any apps including superuser or supersu.
If anyone can help me with this it would be appreciated because i hit a wall and don't know what to do. No apps can get root permissions and i cant fix my play store, WiFi, speakers or theme chooser until the root is properly working because the methods to fix those bugs need root to function. so please if anyone has knowledge or any idea why i have root but cant get access please help me out.
brewsterj98 said:
If anyone can help me with this it would be appreciated because i hit a wall and don't know what to do. No apps can get root permissions and i cant fix my play store, WiFi, speakers or theme chooser until the root is properly working because the methods to fix those bugs need root to function. so please if anyone has knowledge or any idea why i have root but cant get access please help me out.
Click to expand...
Click to collapse
If there is a custom recovery available for your device I would recommend flashing that and then flashing the latest SuperSU.zip package in recovery. Part of the problem is the orginal Superuser (by ChainsDD) while excellent at the time is now extremely outdated and no longer really be maintained, as a result make sure you flash a Superuser package compatible with Android 4.4.2 such as the latest version of SuperSU.
shimp208 said:
If there is a custom recovery available for your device I would recommend flashing that and then flashing the latest SuperSU.zip package in recovery. Part of the problem is the orginal Superuser (by ChainsDD) while excellent at the time is now extremely outdated and no longer really be maintained, as a result make sure you flash a Superuser package compatible with Android 4.4.2 such as the latest version of SuperSU.
Click to expand...
Click to collapse
Where can i find it at? I have recovery on here but i cant seem to find the file. At this point i'll try anything.
Ok so i found the SuperSU.zip v1.99 via another XDA Forum(http://forum.xda-developers.com/showthread.php?t=1538053) and i flashed it then rebooted. Now my device says there is no binary and i am not rooted. I tried reflashing but the .zip does nothing. what should i try next?
Rooted again with SRSroot and still cannot get root access.........please help me out.
brewsterj98 said:
Rooted again with SRSroot and still cannot get root access.........please help me out.
Click to expand...
Click to collapse
You can try flashing Koush's Superuser in recovery, after please run root checker and tell me what is says it the status of your device.
I cant install root checker pro for some reason. I have the basic version installed, is that good enough?
brewsterj98 said:
I cant install root checker pro for some reason. I have the basic version installed, is that good enough?
Click to expand...
Click to collapse
The basic version will work just fine for our needs.
shimp208 said:
The basic version will work just fine for our needs.
Click to expand...
Click to collapse
OK so root checker says i have root access but i still cant access root permissions in apps. I took some screenshots of Link2sd, Terminal Emulator and root explorer so you can see what exactly is going on. I get some weird error in link2sd and root explorer that i have no clue what it is.
Anyone got any knowledge of this error?
brewsterj98 said:
Anyone got any knowledge of this error?
Click to expand...
Click to collapse
try root after factory reset
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've been trying to root my Sparrow without much luck. Followed the instructions and keep getting the following error.
Updater process ended with ERROR : 2
Error installing zip file '/sdcard/SuperSU-2.79-wear.zip
Downloaded SuperSu from here
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
Tried installing with System mounted
You are on AW2.0, right? If so, that's why.
O wait, I didn't realize the 1.5 in your title. Sorry for the confusion.
Got it sorted
https://forum.xda-developers.com/showpost.php?p=73165371&postcount=66
SuperSu appears to install, but still Not Rooted (?)
GTDarthYoda said:
Got it sorted
https://forum.xda-developers.com/showpost.php?p=73165371&postcount=66
Click to expand...
Click to collapse
I used this ^^ SuperSU without BusyBox, and one time it worked, but now trying to use it after a complete wipe and re-install of 1.5, SuperSU appears to install, but Wear Root Checker says Not Rooted. I can't figure out what I am doing wrong/different. I have tried with and without wiping dalvik cache, I have tried with and without mounting system. Can't get it to stick!
Anyone have any ideas?
cushcalc said:
I used this ^^ SuperSU without BusyBox, and one time it worked, but now trying to use it after a complete wipe and re-install of 1.5, SuperSU appears to install, but Wear Root Checker says Not Rooted. I can't figure out what I am doing wrong/different. I have tried with and without wiping dalvik cache, I have tried with and without mounting system. Can't get it to stick!
Anyone have any ideas?
Click to expand...
Click to collapse
Are you using this app?
If so it doesn't work anymore.
Easiest way to see if you're rooted is to use this app. It doesn't open if you're not rooted.
If you really want to test it, use that app to uninstall a system app. Like that useless activity tracker they include.
GTDarthYoda said:
Are you using this app?
If so it doesn't work anymore.
Easiest way to see if you're rooted is to use this app. It doesn't open if you're not rooted.
If you really want to test it, use that app to uninstall a system app. Like that useless activity tracker they include.
Click to expand...
Click to collapse
Thanks!
I uninstalled Wear Root Checker, and installed Advanced Settings, and it opened but said Screen Overlay detected and wouldn't proceed. After reading up on Screen Overlay problems, I found that Wear Mini Launcher was mentioned as a culprit - I uninstalled it, and now Advanced Settings works!
What activity tracker are you talking about? Fit? iFit? Activity Stub?
cushcalc said:
Thanks!
I uninstalled Wear Root Checker, and installed Advanced Settings, and it opened but said Screen Overlay detected and wouldn't proceed. After reading up on Screen Overlay problems, I found that Wear Mini Launcher was mentioned as a culprit - I uninstalled it, and now Advanced Settings works!
What activity tracker are you talking about? Fit? iFit? Activity Stub?
Click to expand...
Click to collapse
I think it's called wellness or something
GTDarthYoda said:
I think it's called wellness or something
Click to expand...
Click to collapse
Ah, I see it. Similar to Fit, but has a sleep tracker.
Have you figured out a way to disable OTA update?