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:
Related
Copying a font in /system/fonts resulted in a 'read only file system' error.
Googling around looks that the /system folder is mounted read only.
How can I (temporarily) set this folder to read/write ?
By using a rooted file explorer or Super Manager .
jje
Thanks, this works.
When I set /shystem to r/w I can manipulate files / copy files to this folder even from an SSH terminal from my Mac.
Worked extremely well!
Thanks for the help guys. I had installed Beans Stock Rom and lost my VVM support. The market even said my device was not compatible. Tried all prior versions of VVM and none worked until I got this file and used Root Explorer to install it and set permissions as described. Thanks heavens.
Hey there?
I've got a question which I can't seem to find anywhere else and YES I have searched this forum and google. However, I may miss it.
Anyway, I've mapped my android phone as a network drive using Samba and changed the smb.conf file to show the System Root directory as well. However, system root is default set as R/O so to mange files USING my computer I need to change the permission to R/W using a file manager (such as root explorer). This is annoying, as I have to keep doing this in order to write to certail directories.
What I wish to do is create a massive guide on all of this to help out the community, however I need one little bit of information.
I would like the / directory (root) to be mounted as R/W as default so that I can quickly edit files on my PC without having to constantly change it to R/O.
If this has been answered before, I do apologize.
Thanks in advance.
Regards,
xxSHABSxx
EDIT:
To make things a bit clearer.
I want something that will automatically mount my phone's root dir into rw upon boot, without custom apps/having to manually mount as rw everytime it reboots. And yes I understand there are apps that do this.
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it'll stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
kuisma said:
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it's stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
Click to expand...
Click to collapse
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Anyway thanks for the reply!
xxshabsxx said:
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Click to expand...
Click to collapse
Or do like I did, move the root to a real ext3 non-volatile file system instead.
Hey guys,
I'm having a problem with ES file explorer. After several days I managed to root my HUawei U8800 Ideos X5 (Android 2.3.5) and obviously one of the next steps is installing CWMR. Unfortunately I'm failing here too. I tried to copy the recovery.img to the .cust_backup/image, but it keeps to say copy failed. Root access was given and I checked all four boxes in root settings. Someone in a german forum told me to update the binarys in SU, which failed too (it says sth like copy su to /system -> failed!). I'm not even sure ES FE would work if the binarys would be current.
Is there someone who can help me? Any ideas?
I already tried the app Mount /system (rw / ro). It didn't work with this too.
Thanks a lot.
no ideas?
You must have the /system folder mounted for read and write, default is read-only.
Different folders in the file structure could be located on different file systems, the easiest way to be sure that you have read and write access were you want to put files, imho, is by using root explorer.
If you are rooted and ES have root permissions then the problem is that the folder is non-writable. I don't know the app you tried to use to mount the /system as r/w but it's easy to do in root explorer or through adb shell with a little bit of *nix knowledge (su and mount -o remount,rw).
Should work from terminal emulator app as well.
C:\Users\...>adb push C:\recovery.img /.cust_backup/image/
failed to copy 'C:\recovery.img' to '/.cust_backup/image//recovery.img': Read-on
ly file system
before I typed
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Doesn't work. adb etc. is installed.
I'm really desperate about this now, I think something is really wrong with my system partiture or something like that. I consider formatting it, the problem I obviously have is that without CWMR I have no clue how to do that and how to flash an OS after it. Does someone have ideas about the whole issue? Interesting facts about my device: Often I'm not able to flash a stock ROM, it stops somewhere in the middle of the process. Rooting works often, but not always with SuperOneClick or zergrush. At the moment my superuser app says "root app_63" in a red font instead of "root root" in a green font, at least I have current binaries at the moment, but this doesn't work always as well. Seems like I am pretty alone with all these problems, that's why I want to format /system...
Please help me! Thanks
Give root explorer a try!
Sent from my OC ed mind.!
Why would you think that would work? ES File Explorer does basically the same...
Dont EVER try to format /system or u r gonna end up completely bricked. Just take your phone to a service centre and see what can be done. If you are under warranty, replace the mobile.
Hope i helped .
Sent from my GT-S5360 using XDA-Developers App.
How can Install the Camera apk on the rooted stock with writable kernel DNA? I replaced this apk with the original stock camera apk, changed the permissions to rw--r--r--. Then, rebooted. But, I don't get the new camera options.
thanks.
Did you mount the /system partition as read/write? This is in addition to the writable kernel, and must be done each time you want to change /system while booted. Most root capable file explorers (i.e. ES explorer) have an option to do this, or you could use this adb command
Code:
adb remount
CastleBravo said:
Did you mount the /system partition as read/write? This is in addition to the writable kernel, and must be done each time you want to change /system while booted. Most root capable file explorers (i.e. ES explorer) have an option to do this, or you could use this adb command
Code:
adb remount
Click to expand...
Click to collapse
It worked. Thanks.:good:
Hi,
I tried to rename root's .ogg files on my Samsung Note 9(Oreo) and unable to do it. I found limited information here. I can rename the .ogg files in the older Android though.. What I have tried so far from these app and failed;
1. ES explorer
2. root explorer
3. mixplorer
4. total commander
Permission for "RW" only can set on "mixploer", and "root explorer" but after tried to copy over the root folder, it prompted failed to copy. Although I can set ES exploere to "RW" mode but it fools you to believe it has rename the file but in reality it was unable to, what a screw up.. Anyone has successfully rename files in root folders?
I did not try this in "safe mode" though..
If you had Magisk rooted phone, try ExSDcardEnable module. Or can you move file to internal storage for rename?
adeii said:
If you had Magisk rooted phone, try ExSDcardEnable module. Or can you move file to internal storage for rename?
Click to expand...
Click to collapse
I was tried to rename the files at internal storage but not able to. I can copied files out to ext memory card or pen drive. After that I was not able to move back to override the current file/files.
Magisk is installed but can't find "ExSDcardEnable module".. Is it in the Magisk manager?
This file ".ogg" is at "system\media\audio\xxxx.ogg" and unable to edit. Looks like the ownership of Oreo harder to make change now..
user109 said:
Magisk is installed but can't find "ExSDcardEnable module".. Is it in the Magisk manager?
This file ".ogg" is at "system\media\audio\xxxx.ogg" and unable to edit. Looks like the ownership of Oreo harder to make change now..
Click to expand...
Click to collapse
Well, at least you have remount /systen as read/write with "mount -o rw,remount /system" or in TotalCommander is easier.
Yes, it is downloadable module in Magisk Man. Latest is ExSDCard Write Access Enabler v3.5 (Sorry for bad name). The new access path for our externals SDCards: /mnt/media_rw/SDCARDNUMBER/
adeii said:
Well, at least you have remount /systen as read/write with "mount -o rw,remount /system" or in TotalCommander is easier.
Yes, it is downloadable module in Magisk Man. Latest is ExSDCard Write Access Enabler v3.5 (Sorry for bad name). The new access path for our externals SDCards: /mnt/media_rw/SDCARDNUMBER/
Click to expand...
Click to collapse
@adeii,
May I know if I need to install it from TWRP? Or run by Magisk manager will do?
user109 said:
@adeii,
May I know if I need to install it from TWRP? Or run by Magisk manager will do?
Click to expand...
Click to collapse
By running from Magisk Manager -> Plugins -> sign "+" -> choose *.zip plugin, after automatic install, reboot phone.
Or MM -> Downloads -> search for ExSDcard -> Click on ExSDcard write access enabler -> Install then reboot.
@Hi adeii,
I installed the "ExSDCard Write Access Enabler" by download through the Mgisk manager's download and wonder if correct. I attached a screenshot here.
I tried to use the total commander to rename the ".ogg" files but failed after I have re-mount the R/W. I wonder if I did correctly by adding the folder as shown in the screenshot.
Did anyone successfully overwrite the files in Oreo? I run out of lucks... Not much information about this issues also.. From Jelly Bean to Marshmallow I have no problem to overwrite files(I did not try on Nougat). But Oreo, until now I still have no way to overwrite a simple file like .ogg.. :crying: