[TOOL][ARM/x86]Init.d support enabler v1.0

[chandarakk]

This way we can only check if INIT command works or not, it doesn't prove that init.d support has been properly enabled

To check if init.d works or not you need to put any custom script in /system/etc/init.d (with correct permissions, at least r-xr-xr-x, recommended rwxrwxrwx), then reboot device and then check script's intended effect.

Below is an example "00test" script:

#!/system/bin/sh
# Init.d test
echo "Init.d is working !!!" > /data/initd_test.log
echo "excecuted on $(date +"%d-%m-%Y %r" )" >> /data/initd_test.log

If you reboot device with such script present in /system/etc/init.d - its intended effect is to create /data/initd_test.log file during boot with following content:

Init.d is working !!!
excecuted on 29-03-2016 03:28:29 PM

please help to check my 00test file it right or or not ? if right copy this 00test to system/etc/init.d folder ? thanks for my bad end

 

[_alexndr]

please help to check my 00test file it right or or not ? if right copy this 00test to system/etc/init.d folder ? thanks for my bad end

At first look it seems to be OK, but it has wrong text format - CRLF (Windows) instead of LF (Linux).

Please use attached file - extract ZIP, put 00test file into /system/etc/init.d folder, set correct permissions (see attached screenshot) and then reboot the phone.

... then check if init.d is working (see if exists /data/initd_test.log file)

 

[chandarakk]

At first look it seems to be OK, but it has wrong text format - CRLF (Windows) instead of LF (Linux).

Please use attached file - extract ZIP, put 00test file into /system/etc/init.d folder, set correct permissions (see attached screenshot) and then reboot the phone.

... then check if init.d is working (see if exists /data/initd_test.log file)

there no exists /data/initd_test.log file so mean not work ? i do all ur step but no luck

 

[_alexndr]

there no exists /data/initd_test.log file so mean not work ? i do all ur step but no luck

Maybe try another init.d enabler... First uninstall init.d from this thread (or revert all steps described here in post #1) and then flash this:

http://forum.xda-developers.com/and...ript-zip-init-d-enabler-stock-kernel-t3347724

 

[chandarakk]

Maybe try another init.d enabler... First uninstall init.d from this thread (or revert all steps described here in post #1) and then flash this:

http://forum.xda-developers.com/and...ript-zip-init-d-enabler-stock-kernel-t3347724

thanks bro work with this link test on LG f180 and Note 5 N920T

 

[rony raj]

cool for tweaks in droid

 

[brismatiq]

thank you

I truly appreciate your work

 

[HemanthJabalpuri]

Sir @Paget96
Your init.d enabler is placing sysinit file in xbin instead of bin....
So i have to move sysinit to bin or change the command in install-recovery-2.sh or init.d.sh file from /system/bin/sysinit to /system/xbin/sysinit.....
I think this is the reason people are stating not working....

So at last for working init.d we have to change 82, 83, 84, 133, 134, 135, 149 lines xbin to bin....
below is the modified working file to flash.... and follow instructions in first post

 

[Paget96]

Sir @Paget96
Your init.d enabler is placing sysinit file in xbin instead of bin....
So i have to move sysinit to bin or change the command in install-recovery-2.sh or init.d.sh file from /system/bin/sysinit to /system/xbin/sysinit.....
I think this is the reason people are stating not working....

So at last for working init.d we have to change 82, 83, 84, 133, 134, 135, 149 lines xbin to bin....
below is the modified working file to flash.... and follow instructions in first post

Thanks for sharing this ^^
Add your credits inside, and send me a screenshot of them. Also provide me .zip file so i can upload it on first page.

 

[HemanthJabalpuri]

Working init.d enabler v2.0 for ARM/x86

Changes
-Changed from xbin to bin in 82, 83, 84, 133, 134, 135, 149 lines of INIT file
-Added 00test in init.d folder to check working of init.d
through /data/init_test.log
-Now it deletes /system/su.d/init_d.sh file too
-Signed with test-key so that it will verify successfully in recovery

 

[Paget96]

Thanks
Changes
-Changed from xbin to bin in 82, 83, 84, 133, 134, 135, 149 lines of INIT file
-Added 00test in init.d folder to check working or init.d
-Now it deletes /system/su.d/init_d.sh folder too
-Signed with test-key so that it will verify successfully in recovery

Editing the first post after 3 years

Good ^^

Sent from my WAS-LX1 using Tapatalk

 

[HemanthJabalpuri]

@Paget96
Sir any exceptions for following lines to use instead of busybox run-parts..?

for FILE in /system/etc/init.d/*; do
   sh $FILE >/dev/null
done;

 

[Paget96]

@Paget96
Sir any exceptions for following lines to use instead of busybox run-parts..?

for FILE in /system/etc/init.d/*; do
   sh $FILE >/dev/null
done;

Why not busybox?

 

[HemanthJabalpuri]

Why not busybox?

Not for me..
But for people who dont use busybox...
What about above command sir?

Thanks for reply..