I'm posting this so it might help others who may find themselves in the same situation. Assuming you have root access, the system is set to read/write permissions and you are using SuperSU yet you are still experiencing one or more of the following issues: Root Browser, Root Spy or another file manager will not let you move files or change permissions, particularly in the system or system/app directory and you are getting "Permission Denied", "Operation Failed" and other errors or Titanium Backup will not restore system apps and hangs at the beginning never starting or completing the restore process and other similarly mysterious permission issues with root.
The answer I discovered was to go into the settings in SuperSU and disable "Mount namespace separation" by unchecking the box and rebooting the device.
Hopefully someone finds this useful.
Related
SU problem... need help
Looks like I accidentally fu.... up my Superuser settings...
When I start Titanium Backup I get an empty screen with the title "SU Request" without any
possibility to allow su access.
I remember I opened "Superuser Permissions" program.
Just for curiosity I tapped the text line, and then this line disappeared.
From this on I can not use Titanium Backup for restoring my old programs.
Now when I start "Superuser Permissions" app I also just get an empty screen,
without any way to change settings...
Any idea how to get my SU rights?
I im attempting to install this bootanimation with sound. With the direct instructions from the op here
When i type "su" in terminal emulator permission is denied.
I am setting the system folder as read/write using root explorer.
I tried it with just root set as read/write
I tries it with both as read/write
Still no go -permission denied
Superuser does not have any apk listed as being denied root access. Superuser has never prompted me to allow or deny terminal emulator root access.
Inspire (obviously) running CM7.0.3
Am I doing something wrong? or missing something? or could this be a error with terminal emulator and/or the ROM?
Thanks for any insight or ideas.
you should be getting a pop-up from super user right after you type su in the term emulator and hit enter.
i have this problem too
I had a similar problem like this when I first started out.......I ended up downloading root checker...which not only checks for root...but makes sure you have a recent version of busybox installed....in my case I didn't. I downloaded and installed busy box and it fixed everything.
Not sure if this will help you, but thought I would try.
Thanks S.Reno9. I installed root checker and I did have busybox installed and still no dice. I dont know what the deal is.
I really hope we can get some more help on this.
Reading this post confirmed the issue came from using Root Tools. What I did was move the cache back to data and SU started working again.
I also have this problem. How did you "move cache back to data." (sorry for the noob question)
same here
after type "su" dont get any pop window only permission denied
what to do now?
A couple things to try -
1 - Clear data from Terminal and Superuser and try again
2 - Uninstall and Reinstall Terminal and Superuser
I have had success with both of these suggestions and different times with this issue
Whoa - just noticed how old this thread was before you posted. Guess it's better than opening a new one.
Solved!
I tried installing busybox but no luck.
I copied the executable (in your case sh script) to root, and now it works fine
It's Super User issue
For me it was because of Super User updates and the problem solved after I had uninstalled the last updates for Super User
recommended from Google Play.
Thanks for the tips.
First problem, I can't access Play Store so I tried to clear cache, clear data, remove google account and then re-adding it (fail because of Authentication failed message). After done some researching, I have to remove or rename accounts.db on my tablet that means I have to root my tablet.
Because my tablet is practically already cluttered, I factory reset and everything.
I tried to root it and it seems to succeed but problem arise when I need to open Root Browser / Root Explorer. It appears that I have to install either SuperSU or Superuser to grant permission to those apps but I can't access Play Store so I download Root Browser, SuperSU and Superuser apk manually and install them on my tablet.
More problems arise. I can't install binary in SuperSU and Superuser or they're not updating and I have no idea why. Now because SuperSU / Superuser not updated, I can't open Root Browser and because I can't open Root Browser, I can't delete or rename accounts.db and finally I can't delete or rename accounts.db, I can't access Play Store (not even sure accounts.db is the problem but I still can't access Play Store after factory reset)
Sorry for the long post, I tried to explain in the most simplest way possible.
I'm trying to install the 4.4.1 update from today, but in TWRP it's complaining that calculator is missing (I deleted it after I rooted). I've tried reinstalling it as a normal user app, but it still complained, so I guess it has to be a system app.
I've tried dropping the calculator.apk into system/app using ES File Explorer but it says "permission denied". I then tried to push it using ADB but when I go to do "adb remount" (as it says to do here: http://www.androidauthority.com/install-user-app-as-system-app-how-to-93522/) I just get "remount failed: permission denied".
Any help please? I'm kinda lost.
Has es been set with root permissions? Does it mount system as r/w? Does it show in supersu app? Does /system/bin/su exist? What about /system/etc/install-recovery.sh? Does the .sh start the su daemon (read commands)?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Thanks for taking a look at it.
ES was set for root permissions, but did not seem to be utilising them correctly or mounting /system properly. I looked around and apparently quite a few people on KitKat are having issues with it, so I assume it needs an update. Root Explorer also would not mount /system.
I did find one file manager that would correctly mount /system as read / write, and that was AntTek Explorer Ex. I was able to put Calculator back and try to update the OTA again, but this time it found other system apps that I had forgotten I had removed. At this point I think I'm just going to wait for someone to modify the OTA update and strip out all of the checks, since that will probably be easier.
Thanks for taking a stab at it though.
I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
pennywaltz said:
I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
Click to expand...
Click to collapse
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted?
2) you have Magisk root manager installed?
3) you have the latest version of busybox installed and have granted it root permission.
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting)
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?)
6) your bootloader is unlocked? (this may or may not be necessary)
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary)
8) have you checked to see if there are any Magisk modules that you might need?
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option?
Sent from my LGL84VL using Tapatalk
REsponses below
Droidriven said:
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted? Based Root Checker I am rooted
2) you have Magisk root manager installed? Yes I have Magisk Manager installed, safetynet passed
3) you have the latest version of busybox installed and have granted it root permission. Yes, installed to /system/sbin
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting) Not an option
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?) Yes, FX has roots right based on Supersu and i have mounted R/W prior to pasting it into the director
6) your bootloader is unlocked? (this may or may not be necessary) It is unlocked
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary) Base on App Systemizer, SE Enabled is False, therefore I assume it is off
8) have you checked to see if there are any Magisk modules that you might need? Not that I know of, I have moved this app as system without it on my Nexus 7 before without any other modules and also have done it on my Pixel 1 phone without it
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option? Yup tried it, it just hangs there, nothing happens
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Sounds like I covered all my bases... so I am puzzled