I think the answer is mistaken: “the kernel” never calls anything from any init.d directory. There needs to be explicit support from the startup scripts for that. I’d need to look at an actual Android device boot process to say how/where, though, can’t do that right now.
– mirabilosMar 6 '14 at 10:18

If you have stock ROM you probably don't have init.d support.
Permissions of file located in init.d folder should be 755 or 777.
If you don't have init.d support you can use kernel adiutor which have init.d emulator