I am at a loss. I have found a thousand people on the interwebs that seem to have this problem but I have been unable to find a single solution.
I have searched these forums and every other android forum I can find. Hopefully I'm not posting this in the completely wrong forum but at this point I'm so fed up I'm seeing spots.
I want to use File Expert. I like it, it's pretty, it SEEMS like it might be useful to a person who wants to copy/move files.
But, it just says "operation failed" when I try and copy files into a system directory. (I have some ringtones, alarms, etc that I want to be available even if I'm in usb storage mode so I like to move them into the system directory).
I can move the files from a terminal emulator (pain in the you know) but Root Explorer (ugly) is the only file manager I can find that actually works to move them.
Am I stuck with Root Explorer or is there something I can do to get other file managers to actually work?
Yes I have enabled the root exploring function in File Expert and every option that i believe is applicable. I also like Anttek (quite visually appealing to me) but it doesn't work either.
Try es file explorer you have to have root permissions to move system dir apps and so forth in the settings of es file go down and check root explorer and mount the system as writeable and all your issues will be solved
Sent from my SPH-D700 using xda premium
Thanks for the quick reply and I will be happy to try ES File Explorer, but why would that work if File Expert (which also claims to be able to mount r/w) doesn't?
Is there really only just ES and Root Explorer that properly get root privileges?
Not sure? I guess so :/
Sent from my SPH-D700 using xda premium
Oh well ES works and it looks pretty good so i suppose I'll use that. Thanks.
Maybe the other file managers did not obtain superuser permission properly, or don't like the new version of busybox, or just don't like Epics...but Biggie steered you the right way.
^^^^^^^^^ edit: you beat me^^^^^^^^
I know in es file explorer you have to go into the apps settings to give the app root permissions so it can get to /system and all that jazz. Maybe file expert has the same deal in the apps settings.
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
So root explorer doesn't let me delete system apps...anybody else?
Also I tried root tools with no success.... I'm on aokp jb with super su I updated binary and nothing . Root explorer let's me mount r/w but says delete failed...any suggestions?
sent from my aokpeed jellybeamed S2 & what?!
jaestreetss said:
So root explorer doesn't let me delete system apps...anybody else?
Also I tried root tools with no success.... I'm on aokp jb with super su I updated binary and nothing . Root explorer let's me mount r/w but says delete failed...any suggestions?
sent from my aokpeed jellybeamed S2 & what?!
Click to expand...
Click to collapse
Bad flash do it again... I had the same issue updated everything and nothing helped til I rebooted wiped and reflashed rom.
Or try to install superuser and see what happens
I was reading somewhere that if you restore a backup the permissions or something get screwy and the only known fix is to re-flash the rom. it sucks
Sent from my SGH-T989 using xda app-developers app
Thanxx guys....just got home gonna try to install su again being that super su gives me an option to clean up the binaries to install regular su.
If anything I'm downloading Aokp again just in case.
sent from my aokpeed jellybeamed S2 & what?!
Had the same issue. I had to reflash. This occured after a Nandroid backup for me.
Have to re-flash, I had the same issue, I did not realize I was on a Nandroid backup. Just do a fresh re-flash and you should be good to go. All of my probs with this are posted in the themes area, they are in the Android pissing on Apple boot animation thread =)
Hello,
I rooted my X10 mini and still can't delete stock apps from the system folder. The root explorer shows R/W but when I try to delete a .apk it says "Delete failed".
I'm not very confortable with flash or re-flash (stock ROM). Can you help me?
I had the same problem, I fixed it by going from CWM 5.x.x to CWM 6.x.x
Try using Titanium Backup.
Sent from my SGH-T989 using xda premium
Thank you for the replies.
I was able to uninstall stock apps (Neoreader, Office suite, ...) through Titanium Backup.
Refugado said:
Hello,
I rooted my X10 mini and still can't delete stock apps from the system folder. The root explorer shows R/W but when I try to delete a .apk it says "Delete failed".
I'm not very confortable with flash or re-flash (stock ROM). Can you help me?
Click to expand...
Click to collapse
Remember, you can't delete a file that is IN USE, ie; system files. You need to freeze/disable them first THEN delete them! Watch what you delete though, some files are needed, some files that you least suspect, and will cause problems if you delete them.
Bluntified said:
Remember, you can't delete a file that is IN USE, ie; system files. You need to freeze/disable them first THEN delete them! Watch what you delete though, some files are needed, some files that you least suspect, and will cause problems if you delete them.
Click to expand...
Click to collapse
I'm experiencing something similar.
I have root on stock os but recovered from nandroid.
I can create folders, files, rename, edit text etc on some directories, yet I am unable for others.
I am trying to undrestand if this is because of
1) Nandroid backup
2) files are in use and I cannot edit or create folders in those directories?
I am trying to create folders and edit files in the /sys directory.
mikoal said:
I'm experiencing something similar.
I have root on stock os but recovered from nandroid.
I can create folders, files, rename, edit text etc on some directories, yet I am unable for others.
I am trying to undrestand if this is because of
1) Nandroid backup
2) files are in use and I cannot edit or create folders in those directories?
I am trying to create folders and edit files in the /sys directory.
Click to expand...
Click to collapse
Are you using the 'Root Explorer' app to do this? If not, I suggest you get that from the Play store first. Secondly, make sure the "root privileges" are enabled in Superuser for the app.
If you have already done what I mentioned and still occur problems, may I ask what folders in the 'sys directory' you are trying to change? As majority of the files/folders you are seeing in that folder are there for a reason and named accordingly for your phone to utilize that directory and keep the phone working.
FineTalent said:
Are you using the 'Root Explorer' app to do this? If not, I suggest you get that from the Play store first. Secondly, make sure the "root privileges" are enabled in Superuser for the app.
If you have already done what I mentioned and still occur problems, may I ask what folders in the 'sys directory' you are trying to change? As majority of the files/folders you are seeing in that folder are there for a reason and named accordingly for your phone to utilize that directory and keep the phone working.
Click to expand...
Click to collapse
I am using root explorer app.
I have root privileges as well. The phone is rooted and permission is granted to RE
i was trying to change or create a new folder for the CPU states because my cpu spy wasn't reading any cpu states (which is another problem im facing).
1) With root privileges am I suppose to be able to create folders in any directory? I seem to be able to create/rename/edit files only in some directories. I seem to have the option to mount as r/o and r/w only on certain folders. The other folders defaulted to mount as r/w. I've also changed permission on the folders as well.
2) Why can't my BBS and CPU Spy read my cpu states, but can only read it when i enter in with my SetCPU app?
mikoal said:
I am using root explorer app.
I have root privileges as well. The phone is rooted and permission is granted to RE
i was trying to change or create a new folder for the CPU states because my cpu spy wasn't reading any cpu states (which is another problem im facing).
1) With root privileges am I suppose to be able to create folders in any directory? I seem to be able to create/rename/edit files only in some directories. I seem to have the option to mount as r/o and r/w only on certain folders. The other folders defaulted to mount as r/w. I've also changed permission on the folders as well.
2) Why can't my BBS and CPU Spy read my cpu states, but can only read it when i enter in with my SetCPU app?
Click to expand...
Click to collapse
Unless you know the exact name and which sub-directory to place the folders to link with the apps you have mentioned, I suggest you do not add or modify anything.
The apps such as CPU Spy utilizes your phones kernel to determine what your usage is. What kernel are you using for your phone? Maybe flashing a new one would help.
I'll look in to the issue more and post any other solutions if I find any. Good luck!
FineTalent said:
Unless you know the exact name and which sub-directory to place the folders to link with the apps you have mentioned, I suggest you do not add or modify anything.
The apps such as CPU Spy utilizes your phones kernel to determine what your usage is. What kernel are you using for your phone? Maybe flashing a new one would help.
I'll look in to the issue more and post any other solutions if I find any. Good luck!
Click to expand...
Click to collapse
1) I understand that its not too safe to mess around anyhting in that directory. But.....can regular rooted users with RE edit that folder? If so, its a problem I'm experiencing. If not, then probably because that folder is in use. When I enter /sys, its mounted as r/w but there is no option for me to change it to r/o.
2) Everything is stock. I understand that CPUSpy may not work on certain custom roms, but what about stock?
Kernel version:
3.0.8-20120814-user
[email protected]#1
SMP PREEMPT Tue Aug 14 10:16:58 KST 2012
Thanks again
mikoal said:
1) I understand that its not too safe to mess around anyhting in that directory. But.....can regular rooted users with RE edit that folder? If so, its a problem I'm experiencing. If not, then probably because that folder is in use. When I enter /sys, its mounted as r/w but there is no option for me to change it to r/o.
2) Everything is stock. I understand that CPUSpy may not work on certain custom roms, but what about stock?
Kernel version:
3.0.8-20120814-user
[email protected]#1
SMP PREEMPT Tue Aug 14 10:16:58 KST 2012
Thanks again
Click to expand...
Click to collapse
1) i think i figured it out. i dont think we have access to the /sys directory. its for kernels.
2) but i still dont know why the cpuspy isn't working
mikoal said:
1) i think i figured it out. i dont think we have access to the /sys directory. its for kernels.
2) but i still dont know why the cpuspy isn't working
Click to expand...
Click to collapse
The app may not be compatible with a stock ROM/kernel. Hopefully someone else on a stock ROM can help you confirm that.
That's a possibility.
However do you know why or how I can get cpu spy to work after I use set cpu?
mikoal said:
That's a possibility.
However do you know why or how I can get cpu spy to work after I use set cpu?
Click to expand...
Click to collapse
I've never needed to use CPU Spy as SetCPU is more than enough, so I apologize if for not being able to answer that question. It just seems like a compatibility issue with what you are currently using, nothing for you to be worried about.
I don't know how else to describe this issue I'm having:
Essentially sometimes I cannot create new folders, either in an explorer app (ES File Manager, Explorer (free, not Root Explorer), or other file manager) or when connected to my computers via USB. Sometimes I can do both. Similarly, sometimes I cannot move files from one directory to another, both using file manager or when connected to computer over USB. It seems random, I think?
An example of this is I downloaded a PDF file from SharePoint using Chrome. The file is downloaded to the /Downloads directory by default. I wanted to move this to a different directory (/Documents), but the cut+paste operation failed. ES File Manager says the operation can't be completed, Explorer just sits there and doesn't say anything. When trying to do the same thing over USB connection, Windows just sits there saying the device is busy, and it'll sit there indefinitely. But an OGG file I downloaded from Dropbox was free to be moved to and from several directories when I was testing file operations.
Basically it's like my device doesn't want to play nice with files and folders. I tried doing a factory reset, but that didn't seem to help. Do you think completely reformatting the phone (as in fastboot format userdata, and a fresh ROM + kernel install) would help? It seems drastic, but at the same time being unable to move files and folders is very strange and likely hard to pinpoint the culprit.
I'm rooted (using traditional SuperSU root) running Pure Nexus 12/01/2015 ROM and ElementalX 0.07 kernel (Enforcing disabled). I doubt any of those 3 factors are the cause of it, but every detail might help, right?
Update: It looks like a permissions issue. Please see post below.
OK an update to this, I discovered that some folders that I thought I had deleted using ES File Manager are still showing up in USB storage when I'm hooked up to a computer. That is to say that what I see using a file manager versus what I see while connected to a computer are different.
Further to this, I am now getting "Permission denied" by the file managers when I try to copy and paste anything from anywhere to any other place. I have booted into TWRP to run Fix Permissions already. It looks like everything now has rwxrwx---, which means to me 770? It should be 775, no?
Any ideas what might be causing this permissions issue?
daver68 said:
OK an update to this, I discovered that some folders that I thought I had deleted using ES File Manager are still showing up in USB storage when I'm hooked up to a computer. That is to say that what I see using a file manager versus what I see while connected to a computer are different.
Click to expand...
Click to collapse
For this, I read somewhere that the latest ES File app has a recycling bin for when you delete apps. So, that needs to be emptied too.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
For this, I read somewhere that the latest ES File app has a recycling bin for when you delete apps. So, that needs to be emptied too.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did indeed clean out the Recycle Bin (and subsequently disabled it), but the problem persists. But thanks for pointing that out!
OK, an interesting discovery:
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /data/media/0/* then I am able to do anything I damn well please.
Now this makes a bit of sense to me, given the permissions for each directory. For example, when viewing the permissions of a file or folder when in /sdcard or /storage/emulated/0, I can only see the permissions as "Readable: Yes, Writeable: Yes", but I cannot change said permissions. However, when I view the permissions for something when under /data/media/0 then not only can I see the explicit permissions "rw-rw-r--" I can also change it if I wanted to.
I suspect this might be more than just the ROM. Perhaps I did not flash the system.img correctly when I first went through the process? Is this possible?