[HELP]Apps Are Granting Root Permission Without Superuser App!!!!!!!! - Galaxy Ace S5830i Q&A, Help & Troubleshooting

Hi! Guys i am facing a awkward problem
My Device-Samsung Galaxy Ace GT-S5830I aka Cooperve
ROM-ACEJB 2.0 BY BRIJESHP(Stock Based Custom Rom 2.3.6 GINGERBREAD XXLA1)
Kernel-Thunder Kernel 2.6.35.7(Custom Kernel already rooted with busybox)
I have SuperSu v.2.4.7 By Chainfire to manage my root access!
But the app crashes several times so i decided to use another superuser app!
I saw there is an option in supersu called "Switch to another superuser app"
I clicked on it after it is done! I rebooted and installed Superuser by chainsDD
and uninstalled supersu.
I opened root validator to check everything is ok or not.
It said everything is ok!
But suddenly strucks on my mind there is no prompt opened for granting superuser permission(ALLOW\DENY)then how could the app gets root permission!
I opened apps like nofrills cpu control,rom toolbox,link2sd,swapper for root and some other root apps they are working fine but there is no prompt to allow or deny showing up!
I opened superuser by chainsdd it said su binary found and showing its location in green colour!
But in apps sections no app is showing there and logs are also empty.
wHICH strucks me most!
I uninstalled superuser by chainsdd.Now i have no supersuser app but still root apps are working and getting root permission
HOW IS THIS POSSIBLE?
PLEASE HELP ME!
If i will not fix this my device will became vulnerable to threats!
(sorry for my english)

Related

Add SUperUser Permision Aplication SetCPU

Ok i installer SuperUser Aplication and now when i Run SetCPU i get a message |""setCPU could not obtain root access. Did you allow setCPU through Superuser permissions? If you checked Superuser permissions and SetCPU still cannot get root, there may be a permission problem with your ROM"
My ROm is Ex Launcher GO
The Superuser App alone is not enough, you need to actually have rooted your device (which also installs a different su that then uses the settings the Superuser App sets).
Grab one of the many root kernels (CF-Root, mine or w/e else) and you'll be set.

SGS3 re-rooting problem

Hi all,
I've rooted my SGS3 via ODIN with CF-Root-SGS3-v6.3. Everything went good and I had root in seconds. One thing I've noticed that this method is installing SuperSU app instead of SuperUser (which I was using on Motorola Defy). It didn't make any difference for me, however after some time I discovered that not all applications works with SuperSU. For instance xMissedCallPatch for exDialer don't even ask for admin permissions. Permission access window from SuperSU just don't POP UP so I can't give that app a root permissions. There was some more examples but can't remeber which one. TitaniumBackup and few other works good.
And here comes the problem:
I wanted to change from SuperSU to SuperUser, so I've installed SuperUser from market, however that does not make him as default app to handle root requests. So... I went to SuperSU settings and clicked "Switch Superuser application". That deleted SuperSU as default app to handle root, but again it didn't make SuperUser as default also. So, none of SuperSU or SuperUser were default apps to handle root
So, trying to make this out, I've uninstalled SuperUser and made ODIN again with CF-Root-SGS3-v6.3. All procedure went as expected but SuperSU still isn't default app to handle root. Now when I'm launching TitaniumBackup (for instance) it just says that it can't work because it has no root rights. As previously no Permission access window from SuperSU.
Do you have any ideas?
OK, my fault.
I've accidentaly used CF-Root-SGS3-v6.3 instead of v6.4. After ODIN with v6.4 everything works great. Even apps which hadn't popups from SuperSU previously now work. For example xMissedCallPath for exDialer now works somehow.
Sorry to bother you all, topic to close.

[Q] Have root. Superuser doesn't prompt

I just downloaded CM7.2 on my Galaxy551, using this thread
http://forum.xda-developers.com/showthread.php?t=1861186
The phone has root, but it gives root access to everything without superuser prompting.
I tryied to update the su binary but it stops at "Making sure new su works"
It just freezes there.
Any help?
Hi mtbrandao,
you could look into SuperSu settings. There you should see under "Access" the option "Default access". If it's on "Grant" that's the trigger for the problem.
s2+user said:
Hi mtbrandao,
you could look into SuperSu settings. There you should see under "Access" the option "Default access". If it's on "Grant" that's the trigger for the problem.
Click to expand...
Click to collapse
I downloaded SuperSu from Play store.
It works OK. Asks for permission and everything.
If I uninstall and install SuperUser, it doens't asks for permission.
SuperSu works (prompt), SuperUser doesn't (prompt).
I will using SuperSu until I can fix SuperUser

Is Superuser Working????

After a complex process to repair my bricked S3 (4.4.2), I rooted the phone with Towelroot (confirmed its rooted) and installed Superuser from the Play store.
I was of the understanding that when Superuser is installed from the Play Store that the binary upgrade is not necessary. However, I have seen no indication that Superuser is working. I explored the system/bin and system/app files with ESExplorer and I got no request from Superuser to allow root access. (there are not Superuser files either location)
I also explored the files with TitaniumBackup Pro and again not peep out of Superuser.
I went ahead and tried the binary update and it fails.
I thought I'd ask for help here before I uninstall Superuser and install SuperSU (I noticed Superuser has been updated since July 2012). At this point I believe uninstalling Superuser would be successful because it is a Play Store install.
Any help/recommendations would be appreciated. As you can tell I'm a novice at this.
NOTE: Just noticed that there are not entries in the Superuser log.
Try rooting with cf-root
dabyd64 said:
Try rooting with cf-root
Click to expand...
Click to collapse
Thank you for the recommendation, however, I just went ahead and uninstalled Superuser and installed SuperSU. SuperSU appears to work and is managing root access as it should.
I probably would not have gone the uninstall method with Superuser, however, I installed it from the Play Store and the Play Store installation is reportedly easy to uninstall because it does not put files in system/app or system/bin......at least I read that somewhere and I checked these locations and there were no Superuser files there.
Thanks again.
Superuser is located on /system/app
su is on /system/xbin

[Q] CleanMaster Root Access Failed

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.

Categories

Resources