I have Root Explorer installed and it says that it has root access and that the mount is read/write yet I am unable to permanently delete or add files to the root/system directory.
I was hoping to replace the current system/media/video/shutdown directory with one of my own and add a bootanimation.zip file to system/media but although the delete/copy/move commands execute without error, no changes actually occur.
I'm so frustrated and have no idea what I'm doing wrong. Any insight will be greatly appreciated.
Thanks
I had the same problem...ended up downloading su file manager. Works perfectly for deleting stubborn system apps.
Sent from my SGH-T959 using XDA App
Have you tried pressing the Mount R/O button on the top right corner and then trying again?
Hi,
I tried changing file permission on one of the folders where I saved my photos to read-only using "Root Browser Lite".
The following error message came up: "Changing permission was not successful. Please note that some file systems do not allow permission changes".
I tried using ES file explorer but it also failed.
Could someone please tell me how I could change the file or folder permission. I wanted to prevent the photos from being accidentally deleted by my children when I let them browse their photos..
My phone I9300 was rooted using CF Auto Root.
Thanks
Get root explorer, it's much better.
Simply long press on a folder and the permissions option is there.
Sent from my GT-I9300 using xda premium
Don't forget to set to rw at the top of root explorer before attempting to change permissions
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
100% work
Try this.....
http://forum.xda-developers.com/showthread.php?t=2038243
this will help you 100%..
qwerty12 said:
If you're talking about the internal memory, you can do chattr +i /data/media/[name of folder] to set the immutable bit. EDIT: You need BusyBox installed for the chattr command
This works because /storage/sdcard0 (JB's usual mountpoint for the internal eMMC) is a fake FAT32 file system Google created for compatibility; the internal eMMC can really be found at /data/media, which is of the ext4 filesystem.
For the external memory, you can try SGS3 Easy UMS and set the read only property on the folder using your computer. (I can't find mattrib for Android.) There is no guarantee that Android/Linux programs will obey the RO attribute, however.
The reason why Root Browser Lite & ES File Explorer didn't work is because they work on UNIX file permissions, while a file system formatted using FAT obviously doesn't understand them - it would expect DOS/FAT attributes. That said, though, have you already backed up the data you consider to be important?
Click to expand...
Click to collapse
=============
Thank you all for your advice. The file system explanation betw FAT and ext4 fs makes sense. I have BusyBox installed.
Via Terminal Emulator, when I did "chattr -i /data/media/DCIM/Camera", I got a "permission denied".
Is there something that prevented me from this?
I'm running ICS.
Thanks
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
zoot1 said:
Did you type su before the command..
Just asking..
sent from here, there, somewhere!!
Click to expand...
Click to collapse
Thanks Zoot1.
I did that.
Image Gallary is still showing /mnt/sdcard/DCIM/Camera as "writeable".
What is the difference between two folders /data/media/DCIM/Camera and /mnt/sdcard/DCIM/Camera?
Thanks,
Note that I used +i in my example invocation of chattr. - removes the attribute; + sets it, which is what you want
Sent from my GT-I9300 using Tapatalk 2
Thanks qwerty12, after 'chattr +i folder name' , I return to root browser lite to change permission on mnt/sdcard/DCIM/Camera, I still get permission denied. What did I do wrong?
Sent from my GT-I9300 using xda app-developers app
Mount System RW
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Vanyna said:
The problem is that your system is currently in RO (Read-Only) mode.
Even if you are root, can't mess with system files if the setup is like that.
ES File Explorer works because it has an option (that DOES work) to mount the system in RW (Read-write) mode.
On my ES File Explorer Version 3.0.0 it goes like this:
Android menú button--->Tools---->Root Explorer--->Mount R/W.
Set: /system (or all of the options) to: RW----->OK.
Now, explore your files using the ES File Explorer interface on your phone and you should be able to erase every file and apk you want even if they are system files.
Click to expand...
Click to collapse
finally its worked for me thx very much dude:laugh::good:
Unhappy [Q] Problems with deleting files and replacing sounds
HI all! New use here.
I superuser'd my phone, routed my phone, installed CM11 and all is well. It was my understanding that with apps like RootBrowser and or SuperManager i could browse to files change permissions and delete and remove them or replace them.
I am unable to change my lock sound or boot animation.
Ive granted the permissions to the apps and am operating the root browsers in Root mode. (sorry if my terminology is wrong but im new to this) When i try to replace the files in system/media or system/media/audio/ui they simply dont work, "operation failed". I am able to change the permissions on the replacement files going into these directories to match those im overwriting but its still fails.
Ive even successfully deleted the default lock sound but when i paste the new one into the folder it fails and says stuff like "out of space" or "no room" and then when i shut app and go back in the original file is back!
Can anyone help with this as my lovely rooted phone is being very difficult.
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
Thank you. I now know what to do but not how to do it? Are you able to help or link me to a post on how to do that?
Many thanks
ngl_ro said:
Your partition is mounted as read-only, that`s why you get "operation failed".
Mount it as read / write and should be ok.
Click to expand...
Click to collapse
When i use the app SuperManager to browse the file system to "system" folder it asks me "If you want to modify the file in teh system, you have to mount the system image first. Please choose access mode: System IMage: R/O"
then
"Do nothing Read only R/W" so i chose R/W but that does not fix the problem?
My errors i get are "not enough free space" well there is plenty of that!
So confused....
Any thoughts
Just ignore the "not enough free space".
Cant help you with RootBrowser or SuperManager because I never used them. I use ES File Explorer, and mounting partitions with it always solved my problems with not being able to delete / modify system files / apps.
Hello. I wanna change a file's permission in sdcard/android/data but when i try this,root explorer gives "permissions change was not succesfull. Please note that some filesystems (e. G. Sd card) don't allow permission changes." I tried a lot of things to fix it. Tried fix permissions in android, add a line to platform.xml. It didin't work. I'm on cyanogenmod 12 with stock kernel. Shall i change my kernel or migrate my filesystem to f2fs? Thank u
Ive been able to decrypt adoptable storage and copy files over from my pc, however i had to chown the media folder to be able to write.
Now on android in a normal file manager the files are 0 bytes and not readable.
I can read them and open them normally with ghost browser as root but not in the stock file manager.
Ive tried to chown -R them back to media_rw:media_rw or system:media_rw but no avail
Somehow I was able to change one folder(including files) back in a test (cant remember how)
Does anyone know if I need to change the files in /mnt/expand/<uuid> or /sdcard ?
KenzooW said:
so does it works?
Click to expand...
Click to collapse
It didnt work for me, at least not yet because i gave up as it was taking to much time there are a few folders with sym links,
Code:
/mnt/expand/<uuid>
/sdcard/
/storage/emulated
/data/media
need to compare all the permissions sometime and replicate it.. It was taking to much time and i found another solution which was to move the folders to a writeable directory after mounting (no change in permissions)
Then on the phone moving it to the right place in ghost file manager. Android has separated the permissions for apps and what not.
Overall its easier just to copy via OTG.
One thing I forgot to mention, that if you're on Linux with the decrypted sd card mounted, you can copy files over directly to the media folder (as #root) without "chown"ing.
I didnt try this but i think that it may work that way since you're not altering existing permission settings