Originally Posted by kurotsugi

ah...thats it. you don't have system folder in working_xxx folder. if you have cwm, make a backup of your rom, copy system.rfs.tar to your computer, extract the file, then put whole system folder into working_xxx.

I tried your method and that's probably the best way to make it work.

But I found a way around. What I did is extract my boot.img with the 'a' option (no need for system folder), rename the folder where boot.img has been extracted to BOOT-EXTRACTED, modify init.rc and build a new boot.img with 'b' option. Maybe not as clean as your method, but it's a newbie way .

I then installed the new boot.img and I checked that the init.rc file in my root was the modified one (which was the case). However, it seems that init.d support is not working as the scripts installed in the init.d folder didn't execute. Is it due to my noob method? Should I try your method instead?

Thanks a lot for helping me in my first steps in the Android world.

how did you test the init.d script? a simple way to test init.d script is by make a file in init.d contain

#!/system/bin/sh
touch /data/kurotsugi.txt

make sure that you have installed busybox and set the file permission to 777 (rwxrwxrwx). if the init.d script is working you'll find kurotsugi.txt in /data

Originally Posted by kurotsugi

how did you test the init.d script? a simple way to test init.d script is by make a file in init.d contain

#!/system/bin/sh
touch /data/kurotsugi.txt

make sure that you have installed busybox and set the file permission to 777 (rwxrwxrwx). if the init.d script is working you'll find kurotsugi.txt in /data

I set the permission to 777 and your test file (called 03test) in init.d but nothing happens.
What I did in fact is to put the following command line in the updater-script of my update.zip file (used to transfer the 03test file to init.d):

set_perm(0, 0, 0777, "/system/etc/init.d/03test");

Any idea why this doesn't work?

have you install the busybox?
if that method didn't work you can try the other method that I've given to you.

I have busybox installed. But when I want to

chmod 777 03test

I get the following error message:
Unable to chmod 03test: Read-only file system

That's why I have to go through the update.zip method.

I also reinstalled the new boot.img created with your method but nothing changes. The scripts in init.d don't run at startup.

Originally Posted by JohnNAVI

I think I have found the reason why it doesn't work. I have installed Busybox v1.18.14 and it looks like run-parts is not supported in this version. I will install a new version of Busybox and I will keep you posted.

It was a problem with the old Busybox version that did not support run-parts. I installed v1.19.4 and everything is working fine now.

Thank you so much for helping me kurotsugi. Have a nice day.