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
Related
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.
I installed Greenify on my HTC M7 with Cyanogenmod 12, but didn't get the 'Grant Root Access' question. Now Greenify can't hibernate.
I tried deleting and re-installing the app, but it didn't help a bit. Also tried using superuser apps, but still no root access question. For I think that's the cause why Greenify can't hibernate my apps in Root mode. Any ideas on how to fix this?
You could check your SuperUser/Super SU to ask for greenify root permission again. What probably happened was that you failed to respond in the short window of time to allow root access to greenify when the popup appeared for the first time & now it is denied unless you manually tell your SuperUser/SuperSU to ask again. Do check the log for permission allowed/denied in your SuperUser/SuperSU app. Hope it helps.
Salman Babri said:
You could check your SuperUser/Super SU to ask for greenify root permission again.
Click to expand...
Click to collapse
Have Useruser installed right now, but can't find this option? No apps in application list. Can you tell me how I should do the above?
Looks like a problem with root access on my phone
Greenify doesnt working with xposed module....not all xperimental features....i mean boost mode...running lollipop5.0.2
Did it work before? Have you donated? You have root and the correct Xposed framework installed? Is Greenify enabled in Xposed and have you rebooted? etc etc etc
tnsmani said:
Did it work before? Have you donated? You have root and the correct Xposed framework installed? Is Greenify enabled in Xposed and have you rebooted? etc etc etc
Click to expand...
Click to collapse
I download cracked apk
reeeju said:
I download cracked apk
Click to expand...
Click to collapse
You have some nerve, reporting it here.
Ok...working now...latest stable apk2.6.2
reeeju said:
I download cracked apk
Click to expand...
Click to collapse
Proud of yourself? Don't expect any help here.
Oh come on people ... Haven't you ever used a crack??
Sent from my SM-G920F using XDA Free mobile app
Its working nicely with all experimental features through xposed.....nd all donation package features...����������������??
?
A Couple Issues
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
I uninstalled it via TiBU and reinstalled the backup with the same result. I uninstalled via TiBU (could not uninstall via the Android App Mgr. It was grayed out. I reinstalled via the play store - had to do via PC because I can't install from the phone for some reason. I get the same result. Only can see the single screen. Also, Greenify is not asking for root and does not show as having root permission in SuperSU (2.49) . I have rebooted, wiped cache and dalvik, and still have the same issue.
Any help would be appreciated.
Thanks
Smithfolk4 said:
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
I uninstalled it via TiBU and reinstalled the backup with the same result. I uninstalled via TiBU (could not uninstall via the Android App Mgr. It was grayed out. I reinstalled via the play store - had to do via PC because I can't install from the phone for some reason. I get the same result. Only can see the single screen. Also, Greenify is not asking for root and does not show as having root permission in SuperSU (2.49) . I have rebooted, wiped cache and dalvik, and still have the same issue.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Which version of greenify r u using now...cos here all working fine in my moto g2
reeeju said:
Which version of greenify r u using now...cos here all working fine in my moto g2
Click to expand...
Click to collapse
I have version 2.6.2. It had been working in the past. It would sometimes get stuck on the same screen, but I could always get it to go to the main screen for hibernating by reopening.
I installed 2.7 Beta 2 and got the hibernate screen. Then when I rebooted it went back to the same problem.
I figured out that I had to remove administrative rights to uninstall, so I did that, uninstalled, reinstalled 2.7 beta 2 and it asked for admin rights and has them, but still I cannot access the hibernate screen after rebooting. So it seems to work okay until I reboot. I am running the latest Xposed for LP 5.0. I also uninstalled and reinstalled from the play store 2.6.2 (via PC) and I could not access it either through exposed or through the app drawer. I then enabled Greenify in Xposed and rebooted and still it is the same. I may have to remove and reinstall Xposed.
Smithfolk4 said:
I have version 2.6.2. It had been working in the past. It would sometimes get stuck on the same screen, but I could always get it to go to the main screen for hibernating by reopening.
I installed 2.7 Beta 2 and got the hibernate screen. Then when I rebooted it went back to the same problem.
I figured out that I had to remove administrative rights to uninstall, so I did that, uninstalled, reinstalled 2.7 beta 2 and it asked for admin rights and has them, but still I cannot access the hibernate screen after rebooting. So it seems to work okay until I reboot. I am running the latest Xposed for LP 5.0. I also uninstalled and reinstalled from the play store 2.6.2 (via PC) and I could not access it either through exposed or through the app drawer. I then enabled Greenify in Xposed and rebooted and still it is the same. I may have to remove and reinstall Xposed.
Click to expand...
Click to collapse
Download and install 2.6.2....tick in module list....reboot.....open greenify..select boost mode...selinux status permissive...do a soft reboot.....
Smithfolk4 said:
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Go to SETTINGS>Device Administrators and uncheck Greenify. Then to SETTINGS>Accessibility and switch off Greenify. Then uninstall Greenify the usual way, not through TiBu. Reboot.
Then try to install Greenify from Play Store or download the apk and install. Enable Greenify in Xposed. Enable Greenify in Device Administrators and Accessibility. Reboot, not soft reboot.
Then open Greenify and see whether you are able to access all the features.
You have root and Xposed, I hope.
Thanks
reeeju said:
Download and install 2.6.2....tick in module list....reboot.....open greenify..select boost mode...selinux status permissive...do a soft reboot.....
Click to expand...
Click to collapse
I decided to reflash the ROM. Will see how it goes.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
tnsmani said:
Go to SETTINGS>Device Administrators and uncheck Greenify. Then to SETTINGS>Accessibility and switch off Greenify. Then uninstall Greenify the usual way, not through TiBu. Reboot.
Then try to install Greenify from Play Store or download the apk and install. Enable Greenify in Xposed. Enable Greenify in Device Administrators and Accessibility. Reboot, not soft reboot.
Then open Greenify and see whether you are able to access all the features.
You have root and Xposed, I hope.
Click to expand...
Click to collapse
Reflashed the ROM. Had other strange stuff going on.
Until the latest release of Microsofts Intune Company Portal (5.0.3503.0) for android exposed module rootcloak has worked to hide that the phone is root'ed but since a week back or something like that the company portal is detecting that my CM13 phone is rooted, so I'm looked out from syncing mails.
Anyone here having the same issue and have a solution for this?
Have you tried Su hide by chainfire
Sent from my iPhone 4s using Tapatalk I also own a g900v
[email protected] said:
Have you tried Su hide by chainfire
Click to expand...
Click to collapse
yes I have, SuHide 0.55, no success
Sorry for your troubles [emoji53]
Sent from my iPhone 4s using Tapatalk I also own a g900v
---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------
Have you tried Uninstalling xposed and just using Su hide I've heard some apps can detect xposed framework
Sent from my iPhone 4s using Tapatalk I also own a g900v
Thanks for the tips! I tryied right away but still no luck!
ljon said:
Thanks for the tips! I tryied right away but still no luck!
Click to expand...
Click to collapse
is it possible to install a previous version of Intune where it still works, and how to get this version?
Try to find the apk on apkmirror or apkpure and install it manually if you find a significantly earlier version uninstallb the version on your device and install the old apk
[email protected] said:
Try to find the apk on apkmirror or apkpure and install it manually if you find a significantly earlier version uninstallb the version on your device and install the old apk
Click to expand...
Click to collapse
i found several older versions that do install but they obviously have an inbuilt check for that so they dont work and just tell me i have to upgrade. as a result it seems its currently not possible to use microsoft company tools on a rooted phone. An unrooted phone is more or less useless.
Are you using systemless supersu most recent version is 2.79 sr3
[email protected] said:
Are you using systemless supersu most recent version is 2.79 sr3
Click to expand...
Click to collapse
The info in the SuperSU app says 2.79 and I installed it systemless on my elephone P9000 stock rom. Also have xposed framework running. I tried a lot of tools but none works.
It does not seem to use safenet check, because I can pass the safenet check by using magisk, but still fails on app's compliance check, saying my phone is rooted.
Damn!
You could always turn off root in developer options and reboot then sync emaills then turn back on root in developer options
Hi,
I'm facing the same issue on my S7 Edge with a Superman Rom on Nougat. I have Magisk 12, Safetynet check Ok but Company Portal still detects root. May be it's because the app is registered as a Device Administrator. I guess with these permissions it can check root differently.
I found an Xposed module for that specific issue but Xposed on Nougat is still unavailable
Do you only have magisk super user installed or do you also have SuperSU installed if you have SuperSU installed remove it
I have just Magisk Super User installed. I never installed SuperSU. The Xposed module that I was talking about is "Security Bypass for Company Portal".
I think we need a Magisk Module doing the same thing if possible.
I recently installed outlook and had the same problem running MagiskSU. Safetynet passes, and Magisk hide was enabled, but no luck. I used Tasker to get around the root check with the with the following tasks:
Launch App (Outlook)
Run Shell command:
su
chmod 0754 /data/magisk
sleep 25
chmod 0755 /data/magisk
This launches the outlook app and changes the permissions of the magisk folder for 25 seconds so that when it does the root check after I input my pin everything checks out. After 25 seconds it restores the permissions to what they were. I exported this as an app (long hold on task, click menu in upper right and export as app) and it seems to work like a charm.
I've tried your solution, but it doesn't work for me. I still have the same message showing up ?
Nakah95 said:
I've tried your solution, but it doesn't work for me. I still have the same message showing up ?
Click to expand...
Click to collapse
It's still one of the strongest root detection apps I know, was there once an xposed framework app that allowed a rooted device to access Portal?
dizzybrow said:
I recently installed outlook and had the same problem running MagiskSU. Safetynet passes, and Magisk hide was enabled, but no luck. I used Tasker to get around the root check with the with the following tasks:
Launch App (Outlook)
Run Shell command:
su
chmod 0754 /data/magisk
sleep 25
chmod 0755 /data/magisk
This launches the outlook app and changes the permissions of the magisk folder for 25 seconds so that when it does the root check after I input my pin everything checks out. After 25 seconds it restores the permissions to what they were. I exported this as an app (long hold on task, click menu in upper right and export as app) and it seems to work like a charm.
Click to expand...
Click to collapse
For now only this method works... Thank you...
kpmohamedhussain said:
For now only this method works... Thank you...
Click to expand...
Click to collapse
Hi, can I ask you to help me get this to work? I am not sure if I am implementing it right..I installed tasker but not sure if I am setting it up correctly cause when I launch the task I still get the same root detection error. I use a galaxy s7 edge with superman rom 2.8 Nougat, magisk 15.3 and xposed.
Hi guys !
I have been using Greenify for quite some time now and finally decided to get the Donation Package in order to unlock some more advanced features.
There's no way to know (or so I think), but I guess deep hibernation, at least, works fine. However, even though "Greenify system apps" is ticked, the only change I noticed in the wizard is SuperSU, which appears when ticking the box in the right up corner menu. I did reboot several times, but with no luck.
As for my configuration, my device is a Honor 5C L51 on Android Marshmallow. I use the EMUI stock ROM (v4.1.2 at the moment) and Nova Launcher Prime.
Do one of you guys have any idea how I can greenify my system apps ? Or is it normal that only SuperSU appears on that list ? I do understand that these options are experimental, but if there is something I misunderstood to get this working, please let me know.
Thank you for your time.
Zarou said:
Hi guys !
I have been using Greenify for quite some time now and finally decided to get the Donation Package in order to unlock some more advanced features.
There's no way to know (or so I think), but I guess deep hibernation, at least, works fine. However, even though "Greenify system apps" is ticked, the only change I noticed in the wizard is SuperSU, which appears when ticking the box in the right up corner menu. I did reboot several times, but with no luck.
As for my configuration, my device is a Honor 5C L51 on Android Marshmallow. I use the EMUI stock ROM (v4.1.2 at the moment) and Nova Launcher Prime.
Do one of you guys have any idea how I can greenify my system apps ? Or is it normal that only SuperSU appears on that list ? I do understand that these options are experimental, but if there is something I misunderstood to get this working, please let me know.
Thank you for your time.
Click to expand...
Click to collapse
- is device rooted?; can't hibernate most system apps w/o root
- make sure working mode is set to 'root' in settings
- if still no joy consider making Greenify a 'system' app which gives Greenify some additional powers if not running Xposed
- that said there are few (often no) system apps that benefit from hibernation
Davey126 said:
- is device rooted?; can't hibernate most system apps w/o root
- make sure working mode is set to 'root' in settings
- if still no joy consider making Greenify a 'system' app which gives Greenify some additional powers if not running Xposed
- that said there are few (often no) system apps that benefit from hibernation
Click to expand...
Click to collapse
Thank you for your answer.
I am root and Greenify's working mode is "Root + Boost (Xposed). I'm confused about what you're saying though, how can one change an app priviledge from user to system ?
Zarou said:
Thank you for your answer.
I am root and Greenify's working mode is "Root + Boost (Xposed). I'm confused about what you're saying though, how can one change an app priviledge from user to system ?
Click to expand...
Click to collapse
If you have Xposed there is no benefit to migrating the Greenify apk to the system partition. Make sure Greenify actually has root permissions. Change the working mode to 'non-root' and then removed the related entry from SuperSU (or whatever root manager you are using). Return to Greenify and select boost mode [or whatever is need to return to "Root + Boost (Xposed)"]. You should get a SuperSU prompt ... either immediately or when attempting to manually hibernate an app.
Davey126 said:
If you have Xposed there is no benefit to migrating the Greenify apk to the system partition. Make sure Greenify actually has root permissions. Change the working mode to 'non-root' and then removed the related entry from SuperSU (or whatever root manager you are using). Return to Greenify and select boost mode [or whatever is need to return to "Root + Boost (Xposed)"]. You should get a SuperSU prompt ... either immediately or when attempting to manually hibernate an app.
Click to expand...
Click to collapse
Just did all that and nothing changed. I also tried to untick the "Greenify system apps" option box and tick it again with no luck. However, I noticed that I could actually make SuperSU appear and disappear from the list of greenifying apps like I mentioned in my first post even if the box is unticked.
Zarou said:
Just did all that and nothing changed. I also tried to untick the "Greenify system apps" option box and tick it again with no luck. However, I noticed that I could actually make SuperSU appear and disappear from the list of greenifying apps like I mentioned in my first post even if the box is unticked.
Click to expand...
Click to collapse
Not much more to say. Either: 1) you have no system apps running aside from SuperSU [seems unlikely]; or 2) Greenify does not have sufficient permissions to see and act upon system apps. Good luck chasing this one down.
SuperSU typically runs as a user app regardless of how Greenify characterizes it. You can check current status from within SuperSU.