Hello...
My question is simple. Why I get permission denied on rooted phone?
When I type: adb shell, I get $. Then I type su and I get this message: Permission Denied.
I followed this how-to (http://forum.xda-developers.com/showthread.php?t=792016) to root my phone and everything was fine. I get root privilegies and installed Superuser.apk, su, busybox...
But now, when I try to get root privilegies, I get the message above. Why?
Thanks and sorry for my english.
Because your phone isn't rooted. Either you didn't do it right or it's unrooted somehow, perhaps you got an OTA.
I think my phone is rooted, because there are many apps that use root permissions installed and working normally.
Sent from my Nexus One using XDA App
Then su isn't set up properly, or isn't asking for superuser permissions, or has been denied superuser permissions? Look in your Superuser app, maybe clear settings in it and let su ask again.
So, I cleared the settings in Superuser.apk and tried open Adfree apps that needs su permissions... and it opened and got permissions normally. I really don't understand what is the problem...
Sent from my Nexus One using XDA App
You do have usb debugging enabled right?
I'm using official Omni 8.1. The issue I'm facing is that the Magisk Manager can't seem to remember the apps it has granted Superuser permission. Even in the Superuser tab it shows "No apps found". Result being I have to grant Superuser permission every time when I open an app like Root Explorer.
Please look into this issue.
Magisk Manager: v5.5.2
Magisk Root: v15.1 Stable
I don't have this issue on version 5.5.0 and 15.1 on the latest Omni 8.1 weekly on my Oneplus 3T.
Edit: You didn't mention what device, so I doubt anyone would be able to help you. But I guess you're running a Oneplus 3T or a Oneplus 5 since there are no 8.1 Omni weeklies for any other devices, yet. Maybe you could try to attach some logs.
For me Magisk v15.1 doesn't boot anymore, it just fails and goes back to recovery.
v14.6 works fine.
Omni 8.1 on Oneplus 5T
Same problem here. Any solution?
Look into this issue, doesn't boot, solutions?
Where are the logs?
How do you expect someone to help you without that?
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Jazavchar said:
For all the praise Magisk seems to get, it sure does have some issues. Lately, it's been kind of a lottery figuring out which version will work with which ROM... These things never happend to me on SuperSu
Click to expand...
Click to collapse
I'd say it has to do with the incredible speed that the Magisk development has been going at. Looking back over the past year, a lot has happened. This kind of speed can cause instabilities...
Now, it's most likely at a point where the focus will be on stability and compatibility development.
Having said that, though, all users experiencing issues can help with that by providing as much details as possible and relevant logs.
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
debichu said:
I can confirm this. It seems Magisk has a problem opening the sqlite3 database, on OmniROM 8.1 at least.
The Superuser request can be granted, and it goes through (as in the app gets its root access), however nothing is permitted "forever".
Superuser log in Magisk Manager is empty, so is the list of apps granted Superuser access.
From my log:
Code:
sqlite3 open failure: unable to open database file
Either the sqlite3 database is located somewhere else, or Magisk didn't get the correct writing rights during the install. Did something change regarding this in 8.1?
There is also a somewhat unrelated issue with Magisk Hide, where the hidelist-file doesn't exist/wasn't initially created upon installation:
Code:
fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
Full log attached.
Click to expand...
Click to collapse
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Didgeridoohan said:
Two things I'm curious about (at the moment):
What are the permissions for /data/adb/magisk.db?
Do you now have a hidelist file in /sbin/.core/img/.core?
Click to expand...
Click to collapse
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
debichu said:
There is no such file in that location. There is a magisk.img in that folder with -rw-r--r--, and a magisk/ folder but not containing any magisk.db file either.
Yes, there is now a hidelist file in /sbin/.core/img/.core with -rw-rw-rw-
Bonus info:
I did a complete wipe (I initially did that but I wanted to be certain), and I got this error while installing Magisk right after OmniROM (also see attached):
Code:
! System installed root detected, mount rw :(
Now, OmniROM doesn't ship with root built in - at least not to my knowledge. So I don't know what this "system installed root" Magisk is detecting.
Click to expand...
Click to collapse
Number 1 is an issue, because that's the su database... If there is none, it's no wonder why granted superuser requests aren't saved.
Hi, do you have a solution?
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
cpt.macp said:
@Didgeridoohan i am facing same issue like this . it keeps asking for superuser req .
Click to expand...
Click to collapse
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Didgeridoohan said:
As far as I know, so far the only known working solution is to reformat /data as ext4. Or stay on an old version of Magisk.
Click to expand...
Click to collapse
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
cpt.macp said:
which version you suggest also my /data is ext4 only .
also i would like to tell you one more thing after tinkering little bit and observed following things
as soon as i dont open the magsik app and using root by simple toast and granting the permission it works but as soon as i open the app , it starts misbehaving . i wonder why .
Click to expand...
Click to collapse
Let me guess: you're not using OmniROM...
Since you're posting in this thread, I kind of assumed you did, so my answer was given accordingly.
If you need help, post all possible details and lots of relevant logs.
I've had the same error. Magisk seems unstable on OmniROM 8.1 on OnePlus 5. Probably an issue with the ROM, but the developer seems like the kind of guy who will tell you to go f*ck yourself if you have a problem like this.
Sometimes it works sometimes it doesn't.
A temporary workaround with the permission issue on /data/adb/magisk.db, even after not working trying 0666 permissions, was to change ownership. None of many other solutions worked for me until I found the user for Magisk. You can use a shell as root or with apps like FX File Explorer with root capability to see which user owns files in "/data/adb/magisk/" . Then I applied that user as the owner of magisk.db. Verified that apps which ask for root permission get saved now. The user of Magisk will be different for you since it is marked as "app_##' which I suppose is up to the amount of apps you have installed.
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
saidmsb said:
I have a problem and think it caused by the same reason other users here.. My issue is after installing omni rom and gapps ONLY i can't use my banking apps because ( i guess) it thinks my device is rooted.
Device : oneplus 5
I wasn't planning to root my device to keep those kind of issues away
Click to expand...
Click to collapse
No... I don't think so. This thread is about an issue with Magisk and f2fs on Android 8.1 ROMs. Your issue could be that OmniROM sets some sensitive props to triggering values.
That can be taken care of by using Magisk and MagiskHide. Take a look here for more info:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Sensitive_props
If you decide to install Magisk, this part of the guide might also be useful (all of it is useful, really):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Like I said, if the default action is prompt, an app seeks root access and there is no prompt to grant it. If I change to grant as default, everything works. Root Checker, for instance, will fail to detect root in prompt mode but does so in grant mode. Same for Root Browser and, most importantly, Xposed.
I've tried reinstalling SuperSU. Didn't help. I have systemless root on a Moto X Pure and SuperSU 2.82.
I really don't want to leave it with grant as the default action. Not safe. I've been able to find a few other posts with a similar problem but they don't lead to solutions. This is a new behavior. Prompt used to work. About a week ago, I installed the latest version of Sensible Android Auto in Xposed. It worked twice and then stopped. My guess is that is the time when SuperSU stopped granting root. Everything that needs root can get root but ONLY if root is granted automatically to anything that asks for it.
Just rooted my Kyocera Event and deduced it to have the same problem. SuperSU 2.8.2 was not providing prompts and thus not granting root access, however changing to grant default did provide root. I tried installing SuperSU 2.7.9 rc4 but had the same result. I'm now just waiting for a definitive fix while looking for an alternative solution.
Hey! I have Magisk 23.0 installed on my Pixel 4 (Android 12). The phone is rooted (I can grant apps SuperUser privileges and I also checked that with Root Checker). However, if I try to run su from the adb shell I get Permission denied error and on the screen of my phone it appears Shell was denied Superuser rights. Tbh I have no clue how to fix this, I tried to reboot the phone, clear the cache of Magisk, and set the "Automatic Response" in Magisk to "Grant". Any idea? Thanks!
Hello!
I am on LOS GSI 19.1, S20 FE LTE Exynos (with TWRP) - when starting Magisk have this msg:
Abnormal State
A "su" binary not from Magisk has been
detected. Please remove any competing
root solution and/or reinstall Magisk.
What could be reason of that and how to fix it. :/ Maybe someone can help...
Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.
YoShake said:
Found your thread while searching for a solution of the same problem.
I thought I will share a solution as finding useful info novadays gets harder every day.
Not to get into detailed description, generally it's caused by su existing in /system/xbin path, and in most cases shell is started with su privileges due to an entry in /system/build.prop
Just rename the /system/xbin/su under adb shell or terminal to for example ssu/zu/subackup whatever the name is and after reboot magisk shouldn't yell with a popup.
btw. I haven't encountered any misbehaviour of magisk, but for the sake of not getting this popup I made the change by the way of working with shell on other things.
Click to expand...
Click to collapse
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
AirForceNBA said:
do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
if rom you use is complied with adb root capabilites, then just use linux mv command after connecting to shell
Code:
adb root
adb shell
mv /system/xbin/su /system/xbin/zu
if not, then maybe under twrp commandline it could be possible?
AirForceNBA said:
Hi I found that for some reason downgrading to android 12 PE works for some reason but when I update to android 13 EvolutionX it shows the popup do you mind sharing the command for adb on how to do this because it denied access for me when I tried remounting from r/o to r/w.
Click to expand...
Click to collapse
I solve this issue in my gsi evolution X android 13 after flash overlyfs.zip in my magisk manager ... Click Download System Rw in this site
Magisk Modules - some Daily use Magisk Mods in 2022 | Use these Modules Daily ! ยป Tech Karan
Magisk Modules are here !
techkaran.co.in
and then flash overlyfs.zip using magisk manager...
Need telegram apps and account to download the file...
Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?
Did
K_a_m_i said:
Any idea?
Click to expand...
Click to collapse
Did you set rw on /system or /system/xbin?
Set rw on the top dir, not nested one in which you want to make changes, or you won't get permissions to change anything in any nested directory you set rw on.
Try to copy the file somewhere else and then delete it from its original path. But I bet you won't succeed. Maybe changing the owner/group and all permissions to 777 would do.
I'd also try in safe mode, or in native recovery mode (not twrp, assuming you still have access to it) using ADB
For me it disapeard by reinstalling magisk by the TWRP.
K_a_m_i said:
Hi I have the same issue. I tried to rename su in xbin but I got permission denied. Root explorer granted root and system is rw. In abd with the command above also permission denied. Xbin folder is not visible in recovery. Overlayfs module is not working with my kernel. Galaxy S21+, TWRP, Lineage 19.1, Hari GSI kernel. Any idea?
Click to expand...
Click to collapse
Are you try to flash Overlyfs first without any module in your magisk...
After you flash magisk manager in your phone and installed already, open it and then restart your phone.. then
First: flash only Overlyfs.zip in your magisk without any module installed.. then restart your phone
Second: download root explorer and grant root
Third: find su in system/xbin and rename it in ZU and save and delete zu then restart your phone
I hope I helped you with this post