Total Commander

Hello, I'm not able to mount /system r/w anymore since the update to 4.3. Root is available (I'm sure). SuperSU is at version 1.51. No one else with this problem?

This is a known problem with 4.3. What happens is that the remount DOES work, but only inside the program which requests it (in this case, "su"). Total Commander itself still sees the partition as not writable when looking at /proc/mounts. I'm currently working on a new version which will read /proc/mounts via "su" command instead of reading it directly.

Please contact me by e-mail (support at ghisler dot com) if you want to test a pre-release version.

ghisler(Author) wrote:...

Please contact me by e-mail (support at ghisler dot com) if you want to test a pre-release version.

Christian, you got my mail this time?

Yes, I already sent you the link a while ago. Please check the spam folder of your mail provider.

ghisler(Author) wrote:Yes, I already sent you the link a while ago. Please check the spam folder of your mail provider.

It's not my spam filter that's acting worse. I got both of your mails and answered them. That's why I asked if you got my last mail.

However, what I wanted to tell you is that the test-version you sent me works without any errors. Many thanks.

Thanks for your feedback! Could you please test the following, one user reported a problem with it which I could not reproduce:
1. Make sure /system is mounted as "read only"
2. Copy a small text file to /system
3. Tap on it to open it with the internal TC editor
4. Edit and save the file
-> the user reported that he could not save it.

True, it does no work. But I can not even open the file. When tapping the file I get the error: open failed: EACCES (Permission denied). After that I can delete the file without problems.

This means that you only give read rights to the owner of the file. Please use long tap - properties - rw button to set the rights to at least
-rw-r--r--

OK, this time I was able to open, edit and save the text file in /system.

Great! I still wonder why the file didn't have read rights initially. It may be a configuration of your system (umask setting).

It was always like this. All files copied to /system just get -rw-------. Where should this be changed?

I don't think that you can change this yourself.

I have the same problem on my nexus 4 and android 4.3
I was previously on 4.2 and everthing was ok. Right now it a big problem for me.

Please use the beta version available here:
http://www.ghisler.com/android.htm#download

Beta solved my problems! Many thanks!