[Android Software Development] oberworld:
Thanks to you for your work... it's a pleasure to help developers. Testing...

I think the file must be renamed to version... almost v56 :)

Here you have the log, seems the same than before:

********* 2016/06/10 01:49:19 **********
- Detecting busybox
- Mount system RW
- Mount again system RW
- Save permissions and ownerships
- Adjust permissions
chown: unknown user/group root:root
- Add permissions to apps
- Write changes back to file
- Remove temporary file
- Apply back permissions and ownership
chown: invalid option -- r
BusyBox v1.24.1-Stericson (2015-11-06 19:11:24 EST) multi-call binary.

Usage: chown [-RhLHPcvf]... OWNER[<.|:>[GROUP]] FILE...

Change the owner and/or group of each FILE to OWNER and/or GROUP

-R	Recurse
-h	Affect symlinks instead of symlink targets
-L	Traverse all symlinks to directories
-H	Traverse symlinks on command line only
-P	Don't traverse symlinks (default)
-c	List changed files
-v	List all files
-f	Hide errors
********* 2016/06/10 01:49:20 **********

Phone it's ok, no changes, no problems.

I'm going to bed, it's 3:52 AM here..

I'll glad to help you tomorrow.

Regards, good nights.

---------- Post added at 04:01 AM ---------- Previous post was at 03:47 AM ----------

@rufus.wilson

This tutorial is for android maybe can help you:

Understanding Android file permissions

Overview Of Permissions via ADB SHELL

Example = drwxrwxrwx

To Check Permission at anytime in ADB just Type:

ls -l

The First character defines the Directory, Link, Binary.

Below are some examples

Example = d---------

d = Directory

l = Link

b = Binary

The next 9 characters define the file permissions. These permissions are

given in groups of 3 each.

The first 3 characters are the permissions for the owner of the file or directory.

Example = -rwx------

The next 3 are permissions for the group that the file is owned by.

Example = ----rwx---

The final 3 characters define the access permissions for everyone not part of the group.

Example = -------rwx

There are 3 possible attributes that make up file access permissions.

r - Read permission. Whether the file may be read. In the case of a

directory, this would mean the ability to list the contents of the

directory.

w - Write permission. Whether the file may be written to or modified. For

a directory, this defines whether you can make any changes to the contents

of the directory. If write permission is not set then you will not be able

to delete, rename or create a file.

x - Execute permission. Whether the file may be executed. In the case of a

directory, this attribute decides whether you have permission to enter,

run a search through that directory or execute some program from that

directory

In addition to the file permission, you can also modify the owner and

group of the file. The chown program is used here and its syntax is very

simple. You need to be the owner of a file or root to do this.

Understanding Owner Permissions:

The first command is for owner ID, the Second Command is for Group ID.

exp. root.root ( First Root is owner, Second Root is Group ).

Chmod 644 some file, Like Build.prop For testing & then Veiw the Resulted Changes!

Refer to the table below as a quick reference.

Command Line for Both would look like this

chmod 644 build.prop = -rw-r--r--

\/

Chmod Guide

0 - ---

1 - --x

2 - -w-

3 - -wx

4 - r--

5 - r-x

6 - rw-

7 - rwx

Behold 2 SH Chown Guide

\/

chown root.root build.prop

root.root = Root

root.shell = Shell

Busybox SH Chown Guide

\/

chown 0.0 build.prop

0.0 = Root

0.2000 = Shell

Side Note:Always set owner ( chown ) before Setting Permissions ( Chmod )!

Hope this Clears up things & is Helpful to everyone

---------- Post added at 04:14 AM ---------- Previous post was at 04:01 AM ----------

I think you must use "chown root.root" instead of "chown root:root" or maybe "chown 0.0"

I'll test tomorrow, good nights.