I have galaxy M31 device and managed to install goodlock. But when running modules, modules are installing but keeps crashing it doesn't even opens. So using warden I noticed that many permissions are not granted which maybe the reason for force stopping. So using adb when I execute the command to grant permission, it's showing: " Permission is a changeable permission type" error. Please how to solve this issue?
An error would be if you get "Permission is not a changeable permission type"
Related
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
I've had an automatic reboot enabled on my phone for well over a year now that has worked perfectly using the process described here:
http://tasker.wikidot.com/devicereboot
This morning I had a notification that my SU binary was outdated asking if I wanted to update to. I updated, and now I can't get a prompt for the Tasker/Locale Execute Plug In action to give it root privleages. I get a SuperUser prompt for other apps, Titanium, Voltage Control, Root Explorer, etc, but for some reason the Locale Execute Plug In get's automatically denied without any prompt whenever it requests root privileages. This is confirmed by viewing the log.
Any ideas?
Ok, more info..
Manually rebooting the phone seems to partially downgrade the SU binary.
I get the notice that a new version of su binary is found.
Code:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0
Checking installed version = 2.3.1-ef
Fixing database... okay!
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... okay!
Checking md5sum... okay!
Moving su to it's final location... okay!
Checking md5sum... okay!
Changing su file mode to 06755... okay!
Remounting /system as ro... okay!
Checking installed version = 3.0
Cleaning up... okay!
It seems to be stuck in this endless loop now.
Every time I reboot the phone it reverts back to the older (working) SU binary and tells me a newer version is available. If I upgrade the SU binary, then my Tasker reboot is broken AND any reboot reverts the SU binary version back to the old one.
I'd be fine leaving the older SU binary on there and just ignoring the notification to update, but when it notifies of an update/newer SU binary it disables the ability to remember your SuperUser choices (Allow/Deny) for apps so either I have to manually allow any root apps every time they need access or change my Super User settings to always allow instead of prompt which isn't exactly ideal or safe.
Any thoughts or ideas?
Cross-posting for visibility...
Looks like others (Epic users) are having the problem as well with the SU binary update.
http://forum.xda-developers.com/showthread.php?t=1279238
In that other thread, the person get a message, that his su binary is installed in /sbin. That means it is in the ramdisk of his boot image.
su should be in /system/xbin, then it can be replaced. if placed in the ramdisk, you need to replace/modify the boot image, to change it.
Per
I don't have the problem with updating the binary, but I do have the same problem with the updated binary.
I've emailed the developer to ask him if there is a fix. I think what he's done is limit it to run only with the exact command you first grant.
So if you're using the Locale execute plugin to try running more than one command only the original command you allow is allowed and all others are denied.
Even setting the default to Allow doesn't help.
Hopefully he'll have a fix.
I'm noticing the same behavior with new Superuser. It no longer prompts to allow Locale Execute Plugin, just waits until the request times out and flashes that the permissions were denied.
I can't figure out how to execute Locale Execute Plugin in a manner that the new Superuser will prompt the request, nor haw to manually add it as allowed.
And this is a single line Tasker Execute, so it's not related to hastarin's comment.
Yes, it does seem to be a bug caused with the new su.
For anyone still stuggling, I managed to get my commands to run with this instead of the Locale Execute Plugin:
http://forum.xda-developers.com/showthread.php?t=1217767
Not sure if this is still relevant however I registered to post anyway.
Ran into this problem and couldn't find any answers so I fiddled around on my own.
By checking the "Advanced Prompt" option in Superuser's preferences I managed to get a prompt to appear and allow the locale execute plugin su permissions.
[FIXED]
Thank you all for the support! I was facing the same issue which Tasker had no root access.
The solution for me was checking the "Enable Permission Warning" option in SuperSU as in the attachment...
I've used Greenify for a long time on my android 4.4.4 nexus 5 phone. Recently, greenify 2.5.1 has been unable to obtain SU privileged. (see attached screenshot from SuperSU).
Greenify doesn’t ask me to grant privileges. I just get an occasional popup notifying me that :
"Greenify silently denied... "
How do I correct this?
I can't find anything in SuperSU that would allow me to add Greenify. What to do?
Please ignore. Problem solved on reboot.
"This operation requires elevated permission.try changing into root access mode"
I'm running a cm 14.1 on moto g2. i have installed supersu given it superuser permissions and even in the file manager i have changed it into root access mode but still every time when i try to access my external card in the file manager it prompts me this. any suggestions ?? coz i have tried mostly everything
Hey!
I have a Galaxy S8 running Renovate ICE rom on android 8.0
There is this app called Screen Stream mirroring (https://play.google.com/store/apps/details?id=com.mobzapp.screenstream.trial)
It should ask for root priviliges, i even see the window "waiting for root priviliges" but the toast where i can grant it, just doesnt come up.
I even tried to grant the app the permission from adb / terminal (android.permission.ACCESS_SUPERUSER) but it results as unknown permission.
Would like to sort this problem out, help please!
Hi try to root your device with kingroot and then it should pop up permission when you open Screen Steam.
https://kingroot.en.uptodown.com/android
Good Luck