Database Develop

Can't get R/W permission on system folder...?

I am in need of read/write access to my system folder. I am simply trying to copy some ringtones and add a boot animation.
I have SGS tools and ran the r/w script, which allowed me to VIEW the folder with Droid Explorer, however I am unable to actually copy TO the system folder or its subfolders.
Any ideas on what I'm doing wrong?
EDIT - I've also tried to push the files to the phone via ADB, but I get an error telling me "Failed: Operation Not Permitted".
EDIT x2 - I've also got Root Explorer installed on the phone and it showed R/W access, but again, I can't get any files pushed to the phone.

Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App

Did you try fixing permissions through cwm recovery?

try root explorer. and double check superuser permissions

goob1284 said:
Did you allow sgs tools to get a root permission?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yup.
Did you try fixing permissions through cwm recovery?
Click to expand...
Click to collapse
I noticed a section for both "mount /system" and also permissions... Both: DONE.
try root explorer. and double check superuser permissions
Click to expand...
Click to collapse
Done & Done...
I've still got no access to R/W in any of the system folders/subs. Any ideas?

I am having the same problem with root explorer..
I have fixed permissions in CWM
It had worked once but now it wont mount r/rw in system folder. Press the icon and it does nothing.
Superuser permission in SGS tools, Root exploer all show active
Any ideas?

Anyone else have any ideas? I'm totally puzzled at this point.

I have sort of fixed the problem..
I go into SGS tools and run the batch file to give r/rw permissions, then I can mount r/rw in system folder, but I loose this each time I reboot and I think when I connect USB..
but it works for the purpose I needed!

I think I've found a work around (or maybe the way it was SUPPOSED to work)...
I rebooted the phone in recovery. Then, selected "mount /system". Then I went to Advanced and "Fix Permissions" (don't know if I had do, just did).
THEN - I was able to FINALLY push the files to the correct folders! I tried it using ADB commands and also with Droid Explorer - Both worked great.
I don't know if the phone was always supposed to be in recovery to do it, but it worked!

Cannot edit build.prop anymore - read-only.

Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...

I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.

dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.

mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.

DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.

You might try fixing permissions under recovery.

have you tried the app: nook netflix fixer?

I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?

Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.

I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App

foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"

backup and restore fresh start....?

I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App

foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best

All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App

bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?

I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.

NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?

Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>

mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney

how to edit hosts file

I've been trying to work on this and still can't figure out how to do this can somebody give me a step by step
So far I've tried to inStall an ash server to go in and edit it but I cannot get it to work somebody to help

maxgohan said:
I've been trying to work on this and still can't figure out how to do this can somebody give me a step by step
So far I've tried to inStall an ash server to go in and edit it but I cannot get it to work somebody to help
Click to expand...
Click to collapse
two ways to change your hostname
1. open edit /system/etc/dhcpcd/dhcpcd.conf with your favorite text editor. under "interface eth0", type: hostname yourdesiredhostname
2. open your favorit terminal emulator, type: vi /system/etc/dhcpcd/dhcpcd.conf
make above mentioned changes.
-> reboot and it should be working. try to ping your device from another piece of hardware in your home network
if you want to change your hosts file - do the same with /etc/hosts ^^

I keep getting this line...
mv: can't remove '/etc/hosts': Read-only file system

is your device rooted? if yes, you have either so mount your root file system as writeable in your file explorer (if it supports root access, like ES File Explorer), or you have to type "su root" at the beginning of your terminal emulator operations.

same problem with a rooted and unlocked device
two_handed said:
is your device rooted? if yes, you have either so mount your root file system as writeable in your file explorer (if it supports root access, like ES File Explorer), or you have to type "su root" at the beginning of your terminal emulator operations.
Click to expand...
Click to collapse
my device is rooted with kingroot I have installed root explorer and ES file explorer too with giving them root permission as well , but when ever I tried to delete or edit hosts file nothing gets change (with root explorer) and with ES file explorer it says " read only file " I tried to change the permission in properties but failed to save the check boxes result. oh man I forget to mention my problem here my cell is infected by a "freedom" app when finally I found it useless I changed the freedom app setting to "freecore" my device got reboot after that I uninstalled the app , now I am unable to connect with google servers , can't use play store , I also tried hosts file Editor but got no result I know my problem is to delete the hosts file , but something is not letting me to take control over hosts file , my android is 5.1 and model is huawei honor 4c ?

Unable to delete or rename install-recovery.sh

Using Root Browser I am unable to delete or rename the install-recovery.sh file. Does anyone know why? Thank you. I also tried ES file explorer.

You need to have R/W privileges. Do you have root?

Mark Once Again said:
You need to have R/W privileges. Do you have root?
Click to expand...
Click to collapse
Yes root has been verified. Thanks for any help you can give Mark.

I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....

Mark Once Again said:
I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....
Click to expand...
Click to collapse
Thanks Bro. Good to go now.

I had the same problem, which is how I found this thread, and was not able to resolve it by remounting /system RW. However it turns out the file had the immutable attribute "i". I was able to remove the attribute and delete the file via:
Code:
su
chgattr -i /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh

recovery upgrade
how to upgrade the recovery. i have a old recovery. i want upgrade it to touch philz recovery plz help

[Fix] ES File Explorer root error

When you try and toggle the "Root Explorer" switch to enable root in ES File Explorer, you are met with and error
"Sorry, test failed. This feature cannot run on your device. Root Explorer"
Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/
Now try turning root explorer on in ES File Explorers Tools setting
It should now turn on and work fine
Credit: Youtube commenter "Daniel Velez"
Code:
https://www.youtube.com/watch?v=TlWoSlvhzI0

*Detection* said:
When you try and toggle the "Root Explorer" switch to enable root in ES File Explorer, you are met with and error
"Sorry, test failed. This feature cannot run on your device. Root Explorer"
Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/
Now try turning root explorer on in ES File Explorers Tools setting
It should now turn on and work fine
Credit: Youtube commenter "Daniel Velez"
Code:
https://www.youtube.com/watch?v=TlWoSlvhzI0
Click to expand...
Click to collapse
Thank you[emoji106]!!
It works fine on G900F Marshmallow rooted with SuperSU 2.72 systemless!
Inviato dal mio SM-G900F utilizzando Tapatalk

Thanks for the hint!
But this error made me change from ESFE to FX + Root Add On.
It's more comfortable in my opinion.

Perfect! Thanks!!!
[emoji106][emoji106]
[emoji122][emoji122][emoji122]

Thank you very much! Worked on my 900F as well!

Great
Thank you so much for a solution :highfive:

New ES File Explorer version now supports Systemless root. Works on my Note 5

If this happens after installing a new ROM you must enable developer options and then set route and then restart the phone or tablet and then that won't happen

Great, thank you.

ES File explorer root error
Thanks, works great!

Titanium Backup
Thanks for the hint (works also with secure settings)
Unfortunately Titanium Backup doesn't recognize root anymore
It got a problem with the /system/xbin/su command.

Still no success. I followed your steps still failed to get root access

Same here with jiayu s3 on Android 7.1 fom M.A.D.
Edit: Got Root Access with copying /su from rootdirectory to system/bin...

Hi!
I have es file explorer version 4.1.4.3 and I have root access without problems

This method works for me, though I'm running a Note Edge MM 6.0.1

I'm on the J7 and having this problem because of Samsung. Moving the files to xbin doesn't work with Root Explorer. Says Copy failed. So even after it's mounted RW I can't copy and paste files. Strangely I was able to rename a file. Don't know why.
Did this trick. But copy still failed even though ES File Explorer got root successfully.
(FYI: Trying to copy sound files into the system.)
Any other ideas?
I am fed up with Samsung!!!

FOR ANY SAMSUNG: Figured it out. All my folder access troubles are Knox's fault! But I had to do a command line trick along with disabling Knox.
You'll need: Root Package Disabler and Terminal Emulator
*So after rooting get either Titanium Backup Pro (not free) or Root Package Disabler (free) or Package Disabler Pro (not free). (They do the same thing.)
*Open the program you installed. Find anything with "knox" in the name and disable it. I, personally, disabled Lookout as well because it often doesn't like advanced root apps or modifications. But it shouldn't block ES File Explorer.
*Open Terminal Emulator. Put in the commands below, one-at-a-time. Hit Enter after each. REBOOT WHEN YOUR DONE. (Source here.)
Code:
su
Code:
mount -o remount,rw /system
Code:
touch /sbin/su /system/bin/su /system/xbin/su
Code:
mount -o remount,ro /system
Code:
exit
Reboot and Root ES File Explorer again.
Note: ES File Explorer won't copy files to the system or other sensitive folders. You still need "Root Explorer" or maybe "Solid Explorer" for that. This makes ES File Explorer useless to me. However, you still need the steps above to copy sensitive system files in the other root enabled file browsers. So do it anyway.

Hi guys! I know this is an old thread and Samsung Space, but i still use ES File Explorer Pro 1.1.4.1 because i like it. But somehow i lost root. Don't know how and why, everything worked fine on my rooted (with Magisk 23.0) Xiaomi Redmi Note 7 with Android 10 (Sorry for that, but i didn't find anything else in the www about this problem). Now i receive the same message "Sorry, test failed. This feature cannot run on your device." and don't know how to solve this. I uninstalled and reinstalled ESFX, deleted it from the list of rooted Apps in Magisk and it asked for the permissions again.... fine..... granted! But still i can't activate it's root explorer. This doesn't work :
" Use another root explorer app with root permissions, and copy the contents of /su/bin/ (about 7 files) and paste them inside /system/xbin/"
....because there is no "/su/bin" and therefore i can't copy anything.

sensei_fritz01 said:
I still use ES File Explorer Pro 1.1.4.1 because i like it.
....because there is no "/su/bin" and therefore i can't copy anything.
Click to expand...
Click to collapse
Same issue here. I ended up copying all files from any folder containing "bin" (sbin, xbin, bin) to /system/xbin to no avail.
Not sure if it is accurate, but it seems like it is, but old ES cannot work on devices that have systemless root.