- Apr 9, 2011
- 39,233
- 76,819
Init.d Enabler + Busybox Installer
As name suggest it's simple tool to enable init.d support without custom kernel. Also this tool have option to install busybox.
Requirement : Rooted Note4 (may work on other device but not tested) + Knowledge - why you needs to enable init.d.
Installation :
- Download attached InitD enabler 1.1 apk and install as regular application.
- Before using it make sure you have busybox installed as init.d requires to have busybox. (many custom ROM haves busybox included but stock ROM won't have it.)
- Open application from drawer
- If your device doesn't have busybox then first select to install busybox and reboot.
- Select to enable init.d support and reboot.
Now device should have init.d support. This tool will inject small test script to check init.d is enabled or not.
- Select Test option from application, it will show you status of init.d as floating message. In case status = Working then look for time too, it should match to last boot time of device.
- If you are not sure about busybox and status doesn't show working, you can try Installing busybox and see.
If everything is fine then you can un install application. Also you can delete test script (system/etc/ini.t/ketan) too.
Credits & Thanks : Busybox developer. (If I am not wrong he is Erik Anderson)
As name suggest it's simple tool to enable init.d support without custom kernel. Also this tool have option to install busybox.
Requirement : Rooted Note4 (may work on other device but not tested) + Knowledge - why you needs to enable init.d.
Installation :
- Download attached InitD enabler 1.1 apk and install as regular application.
- Before using it make sure you have busybox installed as init.d requires to have busybox. (many custom ROM haves busybox included but stock ROM won't have it.)
- Open application from drawer
- If your device doesn't have busybox then first select to install busybox and reboot.
- Select to enable init.d support and reboot.
Now device should have init.d support. This tool will inject small test script to check init.d is enabled or not.
- Select Test option from application, it will show you status of init.d as floating message. In case status = Working then look for time too, it should match to last boot time of device.
- If you are not sure about busybox and status doesn't show working, you can try Installing busybox and see.
If everything is fine then you can un install application. Also you can delete test script (system/etc/ini.t/ketan) too.
Credits & Thanks : Busybox developer. (If I am not wrong he is Erik Anderson)
What is init.d ?
This is the traditional service management package for Linux, containing the init program (the first process that is run when the kernel has finished initializing¹) as well as some infrastructure to start and stop services and configure them. Specifically, files in /etc/init.d are shell scripts that respond to start, stop, restart, and (when supported) reload commands to manage a particular service.
Attachments
Last edited: