-
Notifications
You must be signed in to change notification settings - Fork 454
init.d
- Description
- Do I have init.d support?
- What should I know?
- Check if BusyBox run-parts are present
- How to remove init.d?
- Useful links
Originally Posted by the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer)
Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks. It essentially opens the door to a world of mods only possible through the Init.d process, which in turn is usually only available on custom kernels.
Only "init.d" is responsible for loading up stuff at startup. Sometimes kernels don't make "init.d" folder and you have to create them manually.
Please check if you have such folder:
/system/etc/init.d (permission -> 755/rwxr-xr-x)
If it is there you are good to go!
A other method is:
- Download the file from here: test_initd.zip | XDA - it's from the XDA Member Inside 4ndroid.
- Extract the file, you will get a file named 00test. DO NOT flash!
- Paste it into /etc/init.d. If there is no init.d folder, most probably you DO NOT have init.d support. However, if you still wanna try, just create the folder named "init.d"
- Change the permissions of the init.d folder and 00test into rwxrwxrwx.
- Reboot.
- If you see a file named Test.log in /data, you have init.d support. If not, you will have to run Uni-init, Term-init or Zip-init.
Quick and dirty:
- You need a rooted device!
- To enable init.d scripts (BusyBox is required!) Some kernel use an inbuild BusyBox version and some not, but if you don't have BusyBox don't worry, install a kernel with it (example Kernel, or simply install the BusyBox from Google Play Store.
- Install-recovery is placed in init.rc, so in some ROM's it's maybe on a different place.
Type "busybox run-parts" (without quotes) in a terminal emulator and press enter. If you get an output similar to what's shown below you're all set. It means that BusyBoxs installed and the command is present.
BusyBox v1.20.2-jb static (2014-07-21 00:00 +0100) multi-call binary. Usage: run-parts [-t] [-l] [-a ARG] [-u MASK] DIRECTORY Run a bunch of scripts in DIRECTORY -t Print what would be run, but don't actually run anything -a ARG Pass ARG as argument for every program -u MASK Set the umask to MASK before running every program -l Print names of all matching files even if they are not executable
Install your ROM again or simply delete all files and of course the init.d folder.
- [MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!! | XDA
- How to modify initialization scripts or startup routines in Android | androidquestions.org
- Init.d Toggler | Android Apps on Google Play
- Script Manager - SManager | Android Apps on Google Play
- Universal Init.d | Android Apps on Google Play - (init.d at app level)
Footer