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
Related
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
spanner44 said:
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
Click to expand...
Click to collapse
You have to mount the system as ReadWrite and there was no need for a new thread. You should've posted in the rooting thread
Sorry, for not putting it in the rooting thread, but didn't want to clog a general rooting thread with a specific problem.
I have solved this now thanks, but not with Astro File manager as I still cannot seem to change the permissions with that app, but used advanced tools app instead.
Thanks again anyway.
Yes i had same problem trying do root operations with file expert. I used root file explorer instead. Weird thing being that even with rooting permissions ticked file explorer failed.
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
ChicoKiri said:
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
Click to expand...
Click to collapse
It's mainly dependant on the kernel, all custom kernels automatically mount system as RW and all stock kernels mount it as RO
At least root explorer tells you that it's read only if you attempt to modify it without remounting, I havnt used ASTRO in a long time so I cant comment on that
Root explorer better for me
Sent from my PC36100 using xda premium
Hey guys so Im trying to edit my vold.fstab file to switch my emmc and sdcard interfaces around but everytime I try and edit the file it is denied due to permissions, if I try and set the permissions to 66 (rw-rw-rw) it gets denied and I get an error saying certain filesystems protect these types of files. Does anyone have any idea how to change the permissions for this file because ive tried using terminal and root explorer but neither are working and I really would like to get my internal sd card active again. Thx guys
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:
I'm trying to use Link2SD, so I created the 2nd partition with ext3 format, while the first is FAT32 both are primary.
It did gives me the error "script cannot be created. Invalid argument". I did some research and for what i could understand, I need to enable Init.d, so link2sd scripts can be executed.
So i got Universal Init.d, it says my kernel doesn't support it. Tryed some scripts, but no deal.
The "init.d" folder is there with the script, but it's ignored.
Even if I try to execute the command manually (mount -o rw -t ext3 /dev/block/mmcblk1p2 /data/sdext2) i get the same error using "su" privileges (invalid argument)....
My phone is Xperia Z2 rooted on Lollipop 5.1.1 with SuperSU and XZRecovery (TWRP & CWM).
Thanks for any help
@dthknt ,
XZDR does support init.d but you need to enable it yourself. edit XZDR.prop on your sd card and enable / add:
dr.initd.active=true
dr.keep.byeselinux=true
this last one disables SElinux permanently on your device, if you don't want that install SElinux mode changer app and disable when you want.
SElinux probably needs to be disabled for everything to work correctly.
ptmaniac said:
@dthknt ,
XZDR does support init.d but you need to enable it yourself. edit XZDR.prop on your sd card and enable / add:
dr.initd.active=true
dr.keep.byeselinux=true
this last one disables SElinux permanently on your device, if you don't want that install SElinux mode changer app and disable when you want.
SElinux probably needs to be disabled for everything to work correctly.
Click to expand...
Click to collapse
Thanks @ptmaniac, init.d is working !!!!
But the error remains....invalid argument, even on link2sd log files !
Any ideas ?
Thanks
@dthknt , no problem glad init.d is working, i can't really help you with links2sd as i never used it... try setting selinux to permissive if you didn't do that already.
I personally use obb on sd xposed module to move my obb files to external sd card. Just moving obb's to the sd card is enough for me, i have about 20gb of apps installed right now
It looks like that didn't work, init.d is not enabled.
The XZDR.prop file got corrupted, editing through root explorer or notepad++ from PC.
Any help, @ptmaniac ?
Hello everyone!
since some time ago I was customizing the ROM of Android 5.0. Everything was in order while I didn't try to change the system files. Obviously after flashing device refuse the normal boot and stacked on boot screen.. The reason was selinux context which I've never applied.
The process is:
1. Mount the ROM as EXT4
2. Add/Change files
3. Change the permissions
4. Unmount and flash...The question is:
How to label and chcon the newly added files with Android's default context in a mounted EXT4 image?
PS: Not sure is the right forum. Please suggest a solution.
Thanks!
dFrem said:
Hello everyone!
since some time ago I was customizing the ROM of Android 5.0. Everything was in order while I didn't try to change the system files. Obviously after flashing device refuse the normal boot and stacked on boot screen.. The reason was selinux context which I've never applied.
The process is:
1. Mount the ROM as EXT4
2. Add/Change files
3. Change the permissions
4. Unmount and flash...
The question is:
How to label and chcon the newly added files with Android's default context in a mounted EXT4 image?
PS: Not sure is the right forum. Please suggest a solution.
Thanks!
Click to expand...
Click to collapse
What do u mean u mounted the ROM ext4? The file system should have been defined upon install. If u changed the file system of your system partition I would assume you wiped you accidently wiped the installed os . Selinux status could affect boot but only if you did something that requires permissive status (a custom kernel is a good ready example of the type of flAsh that would need selinux on permissive). Ok so let's assume u didn't mean ROM . You meAnt system partition and you naturraly mounted that (system) as R/W . What permissions did you set on file . 644 is the correct answer if you were trying to install as system file. Wht was it you flashed? It's probably an easy fix bud . Just need more info
mojoswagger1980 said:
What do u mean u mounted the ROM ext4? The file system should have been defined upon install. If u changed the file system of your system partition I would assume you wiped you accidently wiped the installed os . Selinux status could affect boot but only if you did something that requires permissive status (a custom kernel is a good ready example of the type of flAsh that would need selinux on permissive). Ok so let's assume u didn't mean ROM . You meAnt system partition and you naturraly mounted that (system) as R/W . What permissions did you set on file . 644 is the correct answer if you were trying to install as system file. Wht was it you flashed? It's probably an easy fix bud . Just need more info
Click to expand...
Click to collapse
@mojoswagger1980 Thanks for answering. My bad, of course meaning is to mount "system.img" and not the ROM. Will explain.
The image is mounted, adding busybox into system/xbin, chmod 644, (automatically set owner root:root). As expected ls -Z is showing "?" for system/xbin/busybox...
Not changing anything more, flashing this image. File is not accessible or doesn't exists.
No doubts that if I am doing "chcon ubject_r:system_file:s0 system/xbin/busybox" it says first relabel the file... Relabel says there is no such type, user, etc...
What can I do in this case?
PS: Setting permissive 1 with inject-sepolicy doesn't help. May be I am doing something wrong here. Please suggestions.