Developer help, extract and permissions?

[syztemlord]

Hi guys,

I'm trying to make some changes to an android 812 firmware. Ultimately what I'm trying to do is extract some files from a tar.gz into a folder on the root.

I have got as far as creating the directory on the root, and having a shell script run that extracts the files to the root folder. Problem is, the files aren't appearing in my folder.

This is what I've done so far:

1. Extracted the boot image in the firmware to edit "init.rc". I've made the changes so I can make my "test" folder with 777 permissions.
In the "on init" section of init.rc I have this:

mkdir /test 777

2. I've created the following script (test.h) that runs from init.amlogic.board.rc

#!/system/bin/sh

MARK=/data/local/test

if [ ! -e $MARK ]; then
echo "test script"

busybox tar -zxf /system/test.tar.gz -C /test/

touch $MARK
echo "OK, installation complete."
fi

This is the code in the init.amlogic.board.rc

service test_copy /system/bin/test.sh
            user root
            group root
            disabled
            oneshot

on property:sys.boot_completed=1
        start test_copy

Once the box has booted I can see the "test_copy" file but the tar.gz files are not in my root folder.
The last thing I need is the files from the tar.gz to be 777 permissions.

Obviously I'm a complete noob at this, hope that makes sense and someone can help?

[mo123]

Hi guys,

I'm trying to make some changes to an android 812 firmware. Ultimately what I'm trying to do is extract some files from a tar.gz into a folder on the root.

I have got as far as creating the directory on the root, and having a shell script run that extracts the files to the root folder. Problem is, the files aren't appearing in my folder.

This is what I've done so far:

1. Extracted the boot image in the firmware to edit "init.rc". I've made the changes so I can make my "test" folder with 777 permissions.
In the "on init" section of init.rc I have this:

mkdir /test 777

2. I've created the following script (test.h) that runs from init.amlogic.board.rc

#!/system/bin/sh

MARK=/data/local/test

if [ ! -e $MARK ]; then
echo "test script"

busybox tar -zxf /system/test.tar.gz -C /test/

touch $MARK
echo "OK, installation complete."
fi

This is the code in the init.amlogic.board.rc

service test_copy /system/bin/test.sh
user root
group root
disabled
oneshot

on property:sys.boot_completed=1
start test_copy

Once the box has booted I can see the "test_copy" file but the tar.gz files are not in my root folder.
The last thing I need is the files from the tar.gz to be 777 permissions.

Obviously I'm a complete noob at this, hope that makes sense and someone can help?

There might be file names in your tar file that is too long and stops the extraction command.
If you are trying to untar Kodi folders that is your problem as there are too many addons with strange file names.
Manually run all the commands in a terminal app to find the problem.

[prahjister]

Try to /sdcard/test also..

[syztemlord]

Thanks guys, the tar just contains 3 files, not kodi data related.

I was thinking it wouldn't extract because the file system would be set to read only?

[mo123]

Thanks guys, the tar just contains 3 files, not kodi data related.

I was thinking it wouldn't extract because the file system would be set to read only?

Does your firmware have the tar file in /system/bin and also busybox installed?

[syztemlord]

The tar file is in /system busybox is also installed.
I do have another tar file that extracts kodi data (as you mentioned before) and that works fine which makes me think it's a read only problem? both tar files, my test and kodi data are in /system. The scripts to extract are the same except for destination folder and ta name.

Can I set me test folder to read/write in the init.rc file?

[lewy20041]

Yor problem is that you dont remount system partition to rw before ectract,
Before "busybox tar -xzf" in your script place " mount -o remount,rw /system;" without quotas and after place " mount -o remount,ro /system;" to remount system back to read only.

[syztemlord]

Thanks for that Lewy, I now have this in the script:

mount -o remount,rw /system;

busybox tar -zxf /system/test.tar.gz -C /test/

mount -o remount,ro /system;

But unfortunatly it's still not working.

I was wondering if I made a "test" directory in the system folder on the firmware zip and copied the 3 files from the tar there, can I change permissions on the 3 files to 777 on boot? Would it be easier to do it that way?

I did previously try it and doing a chmod command in the init.rc but couldn't get it to work. Again, possibly a rights issue?

[prahjister]

What about permissions on the shell script itself

[lewy20041]

Your scripts needs to have 755 permisions, after the busybox also place "chmod 644 /system/test/ yourfile" also probably it would best for you to check if the script is working using android terminal first before making any changes to the ramdisk, its easer and faster. Just install android emulator type su and after giving root permisionss /path/to/yourscript it will show you whats wrong with the script this way.

[syztemlord]

Great thanks, I'll give that a go today.

[syztemlord]

YES!! All working now. Thank you so so much guys. Your help is extremely appreciated!

[lewy20041]

Glad you get it to work