Related
I've got an app that is listed as 'disabled' in application manager list, but when I select it to try and re-enable the button is grayed out and says 'disable' on it as if it was never disabled to start with.
How do I un-stick this app? TIA
What app is it?
You should be able to use any app or file manager to uninstall it.
Do you have root access?
440bro said:
What app is it?
You should be able to use any app or file manager to uninstall it.
Do you have root access?
Click to expand...
Click to collapse
The basic 'email' app. I had originally disabled that and 'exchange services' way back at the beginning (root required) because I wasn't using anything but gmail and was paring down on apps as much as possible. Now I have a reason to use it, and while I was able to enable 'exchange services' again, the other one just seems stuck. After the update to ICS and then JB I never installed root, and with the OTA updates it seems this particular app has gotten into a bit of a mangled state.
tigerknight said:
The basic 'email' app. I had originally disabled that and 'exchange services' way back at the beginning (root required) because I wasn't using anything but gmail and was paring down on apps as much as possible. Now I have a reason to use it, and while I was able to enable 'exchange services' again, the other one just seems stuck. After the update to ICS and then JB I never installed root, and with the OTA updates it seems this particular app has gotten into a bit of a mangled state.
Click to expand...
Click to collapse
Well you can try installing them again. I'm going to assume you're on the latest 4.1.2 version. So here is the email apk and here is the exchange apk just in case you want to reinstall both.
Or you could gain root access and use an app to unfreeze them that way.
To root the stock 4.1.2 rom
1. Use Odin 1.85 in Admin Mode for Windows users.
2. Install TWRP 2.5 via PDA settings.
3. Reboot phone into Recovery.
4. Install SuperSU via the Zip.
5. Reboot phone and viola You're rooted!. SuperSU is there and works.
440bro said:
Well you can try installing them again. I'm going to assume you're on the latest 4.1.2 version. So here is the email apk and here is the exchange apk just in case you want to reinstall both.
Or you could gain root access and use an app to unfreeze them that way.
To root the stock 4.1.2 rom
1. Use Odin 1.85 in Admin Mode for Windows users.
2. Install TWRP 2.5 via PDA settings.
3. Reboot phone into Recovery.
4. Install SuperSU via the Zip.
5. Reboot phone and viola You're rooted!. SuperSU is there and works.
Click to expand...
Click to collapse
Grr. I downloaded the email apk and tried to run it, and it just failed with 'application not installed'. Apparently I buggered myself up good - I'll have to go the root option, any tips/tricks to keep in mind before I do that?
After installing SlimROM 4.3 Build 2, I lost root?
I was originally rooted on the stock 2.1 and had the SuperUser app as well. However, after upgrading, Root Checker says I'm not rooted anymore?
try opening up SU if its not installed and update the binaries if that doesnt work flash the SU zip if your still having errors try going into your settings and grant SU rights to whats needed
krazierokz said:
try opening up SU if its not installed and update the binaries if that doesnt work flash the SU zip if your still having errors try going into your settings and grant SU rights to whats needed
Click to expand...
Click to collapse
I tried installing superUser from this:
http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
But Root Checker and other apps still say I don't have root?
Neo3D said:
I tried installing superUser from this:
http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
But Root Checker and other apps still say I don't have root?
Click to expand...
Click to collapse
Then I tried to install this:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
and it installed but when I open the app, it says:
- I have to update the binaries but updating them fails
- I have to uninstall superUser, but I can't do that anymore because I flashed zip?
Try dirty flashing the rom flash again and wipe dalvik and cache a d reboot then open rom manager and click fix permission from within the app. If that doesn't work download busy box installer that should update your binaries it's weird issue your having
EDIT: i found this for you didn't realize earlier that 4.3 SU is different than before Root access works in another way in 4.3 then it was before. It is disabled by default. If you want to have root access go into your Superuser application or in Settings->Developer options and enable it. Please note as well that currently some third party kernels are around which may break root.
sent from my t mobile S4
Neo3D said:
After installing SlimROM 4.3 Build 2, I lost root?
I was originally rooted on the stock 2.1 and had the SuperUser app as well. However, after upgrading, Root Checker says I'm not rooted anymore?
Click to expand...
Click to collapse
In slim rom go to
System settings-> advanced options -> Super User ->top right key for settings
then change super user access for your APPS
and choose declared permission
rigzin said:
In slim rom go to
System settings-> advanced options -> Super User ->top right key for settings
then change super user access for your APPS
and choose declared permission
Click to expand...
Click to collapse
This worked like a charm. Thank you.
Just in case, if anyone makes these changes to their Super User settings, and Super SU bypasses and deny's access automatically, just go back to the settings again and Long Press whatever was denied and "Allow" it.
Another tip, I personally just went ahead and clicked on Auto-Allow so I don't have to go back to the settings so much.
Currently on: Galaxy S3/T999, SlimRom4.4.4, Stock Kernel
I recently installed Hyperdrive RLS19 on a a I545 NC5 using Safestrap 3.75 KitKat A01. Everything works fine including wifi. I did have to restore the Android Device ID, which got changed somehow. I have rebooted several times into SS and used it to flash other stuff, etc. However, I decided to update the pre-installed version of SafeStrap, which was an older version. I first attempted to uninstall SS using System App Remover. The SS app appears to be gone; but then, when I tried to reinstall SafeStrap a message asked if I wanted to update this built-in app. The update then failed. I have two questions. If this has been explained elsewhere, please just point me in the right direction.
1. How can I reinstall SafeStrap 3.75, so that it matches the version of the installed recovery?
2. Is there any need to keep the SafeStrap app installed, after the recovery is installed and working? Does it do anything besides install and uninstall the recovery?
(I think I should be able to uninstall the recovery, if needed, by switching back to the stock ROM slot and uninstalling it from there.)
Thanks in advance for any help or explanations.
Also, kudos to the developers of Hyperdrive for an outstanding product.
VirtualX1 said:
I recently installed Hyperdrive RLS19 on a a I545 NC5 using Safestrap 3.75 KitKat A01. Everything works fine including wifi. I did have to restore the Android Device ID, which got changed somehow. I have rebooted several times into SS and used it to flash other stuff, etc. However, I decided to update the pre-installed version of SafeStrap, which was an older version. I first attempted to uninstall SS using System App Remover. The SS app appears to be gone; but then, when I tried to reinstall SafeStrap a message asked if I wanted to update this built-in app. The update then failed. I have two questions. If this has been explained elsewhere, please just point me in the right direction.
1. How can I reinstall SafeStrap 3.75, so that it matches the version of the installed recovery?
2. Is there any need to keep the SafeStrap app installed, after the recovery is installed and working? Does it do anything besides install and uninstall the recovery?
(I think I should be able to uninstall the recovery, if needed, by switching back to the stock ROM slot and uninstalling it from there.)
Thanks in advance for any help or explanations.
Also, kudos to the developers of Hyperdrive for an outstanding product.
Click to expand...
Click to collapse
Download the Safestrap 3.75 apk. Go into your old version of Safestrap and "uninstall recovery". Then from your app drawer, drag the Safestrap app to "uninstall app". Uninstall Busybox also. From the Play Store, download Selinux and Busybox. Reboot your phone. Go into Selinux and set Linux to "permissive". Go into the Busybox app and "install Busybox". Go to wherever the Safestrap 3.75 APK is and install it. Go into your Safestrap app and "install recovery" reboot. Profit.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
liljoe727 said:
Download the Safestrap 3.75 apk. Go into your old version of Safestrap and "uninstall recovery". Then from your app drawer, drag the Safestrap app to "uninstall app". Uninstall Busybox also. From the Play Store, download Selinux and Busybox. Reboot your phone. Go into Selinux and set Linux to "permissive". Go into the Busybox app and "install Busybox". Go to wherever the Safestrap 3.75 APK is and install it. Go into your Safestrap app and "install recovery" reboot. Profit.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
Click to expand...
Click to collapse
The Safestrap app was removed. Usually, System App Remover makes a backup of apps removed, but in this case it did not make the backup; not sure why.
If you reboot after removing the recovery, does it automatically go into the last used ROM slot? Or does it default back to the stock slot?
Thank you for the assistance.
VirtualX1 said:
The Safestrap app was removed. Usually, System App Remover makes a backup of apps removed, but in this case it did not make the backup; not sure why.
If you reboot after removing the recovery, does it automatically go into the last used ROM slot? Or does it default back to the stock slot?
Thank you for the assistance.
Click to expand...
Click to collapse
I reckon it should boot into whatever partition you were in before you removed Safestrap. You could just hotboot the phone and you wouldn't need to worry about that.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
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.
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