TC on rooted KitKat can write to / but not delete!

[ghisler(Author)]

This is just for test purposes! I need to find out what's the problem on your device. I do not have this problem on my Nexus 7 with Android 4.4.2. and SuperSU.

[TheByteSmasher]

Fyi, I get a funky toast also. I'll try the 'make a button' today, but just the normal way I get this:Image: http://i1374.photobucket.com/albums/ag435/TheByteSmasher/Screenshot_2014-06-29-12-32-08_zpsxwx0goco.png

[TheByteSmasher]

Doesn't work... maybe I did something wrong...[img]http://i1374.photobucket.com/albums/ag435/TheByteSmasher/Mobile%20Uploads/2014-06/Screenshot_2014-06-29-16-52-37_zpsclcub8yk.png[/img]

[ghisler(Author)]

Hmm, that's a funny error message "Not enough memory". It usually comes when the /system partition is full and you try to write something to it. Maybe it's a journaling file system like EX4 and the journal cannot be written for the deletion...

[TheByteSmasher]

Yeah, the toast is weird. CMFileManager doesn't get it and deletes stuff fine.. also, I have 4 GB free on internal storage but yeah, my system partition is full...

[NoSubstitute]

Yes, that toast is the same as I get.
Shouldn't really matter if the /system partition is full (or, even if it does, it shouldn't be relevant), since it works fine running the command manually in terminal.

[TheByteSmasher]

So... any ideas?

[ghisler(Author)]

No, unfortunately not, sorry. I have never seen this error on other devices.

[NoSubstitute]

Creating a button like you described, with the following content, worked.

Function: Send shell command
Command: su
Parametre line 1: mount -o remount,rw -t rootf rootfs /
Parametre line 2: rmdir /root/write-test

So it seems when it is done "automatically" the commands aren't chained/connected correctly. It says it does the remount, but it doesn't allow the rmdir.

This is on my Nexus 7 with 4.4.4 and my Sony Xperia Z with 4.4.2, both fully rooted.

[ghisler(Author)]

Can you try something else too, please? Create two separate buttons, one with
mount -o remount,rw -t rootf rootfs /
and the other with
rmdir /root/write-test

Then press the first and then the second button. Does this work too?

[NoSubstitute]

Can you try something else too, please? Create two separate buttons, one with
mount -o remount,rw -t rootf rootfs /
and the other with
rmdir /root/write-test

Then press the first and then the second button. Does this work too?

Yes, this works. Both commands have to be SU, with the action as parameter.

It seems that the internal mkdir command requests and processes the remount to rw and also correctly requests SU permissions, but the internal rm/dir does not.

When I create both mkdir and rmdir as SU commands it works fine.
IF I first manually remount as rw with your button.
Same if I do a SU copy and then an SU rm of that file.

So, basically, it seems to create or remove things from / one has to first remount it, with your remount-button. After that, it varies whether you are creating or removing.

For creating one can use the internal commands and buttons just fine.
For removing, only manually created buttons, with SU works.

[ghisler(Author)]

OK, I will try to find out what is different. Can you check what command the remount button sends? Maybe there is a small difference to the command you entered manually...

[NoSubstitute]

I don't know where to find the internal commands, but it uses "119 Mount".

[ghisler(Author)]

No, I mean when you press the 119 Mount button in that directory, TC will offer to mount the drive with write rights. In this dialog box, it shows the exact command which it will send. Please check whether it is 100% the same as your own, or if there are additional or missing parameters.

[NoSubstitute]

It's exactly the same as mine, as it is _that_ command I have been using, when I do it manually.