Impossible to get the init.d support in ramdisk

kalo86 said:

Hello guys!

I am not new in the Android and Nexus world but at this time I need some help.
I am used to root any Nexus phone in this way:

1. Put su, daemonsu, busybox on /system/xbin/ path;
2. Create the init.d folder in /system/etc/ path;
3. Add a script file to start the superuser daemon at the boot;
4. Edit the kernel ramdisk adding the sysinit script to add the init.d support at the boot;
5. Edit the updated-script for the right permissions to the new init.d folder (and its content) and to the su binary file.

I never had problems with Galaxy Nexus and LG Nexus 4 but today I am having troubles with the Nexus 5.
Is this a common issue?

I hope to get answers,
regards,

kalo86

Click to expand...

Click to collapse

kalo86 said:

Of course I have unlocked the bootloder but the init.d script does not work.
Neither a test script works...

This is the test script that I am using to verify if the init.d support is working. The file 00test is placed in /system/etc/init.d/.

Code:

#!/system/bin/sh
#Init.d Test

busybox mount -o remount,rw -t auto /system

if [ -e /system/Test.log ]; then
rm /system/Test.log
fi

echo "kalo86 @ XDA 2014" > /system/Test.log
echo "Init.d is working !!!" >> /system/Test.log

Click to expand...

Click to collapse