Permissions Issues for New Files

[ccccoisini]

Hello, I attempted to create a new file: /system/bin/myscript.sh, then ran chmod 755 system/bin/myscript.sh

After rebooting, the result is:
-rw-r--r-- 1 root shell 975 2025-10-09 02:20 /system/bin/myscript.sh

I hope to get your help.

[ravindu644]

Hello, I attempted to create a new file: /system/bin/myscript.sh, then ran chmod 755 system/bin/myscript.sh

After rebooting, the result is: -rw-r--r-- 1 root shell 975 2025-10-09 02:20 /system/bin/myscript.sh

I hope to get your help.

Hey,

Just add your custom file to the .repack-info/fs-config.txt with proper permissions.

The script automatically applies the SE context using the parent folder's context, but uses the default 644 permissions for any new files.

The only way to fix this is by manually adding the entry in fs-config.txt until I add an option to set executable permissions for .sh files and any files added to the bin/ folders.

[ravindu644]

Hello, I attempted to create a new file: /system/bin/myscript.sh, then ran chmod 755 system/bin/myscript.sh

After rebooting, the result is: -rw-r--r-- 1 root shell 975 2025-10-09 02:20 /system/bin/myscript.sh

I hope to get your help.

As an example, the .repack_info folder is located in the root of the unpacked image’s directory.

It contains several text files that you can edit according to your needs:

If you want to add an executable file, you can specify the path along with the owner and permissions.
For the root user, it would look like this:

/path/to/binary 0 0 755

You can also define your own custom contexts like this:

That’s it!

[ccccoisini]

thank you very much