FORUMS
Remove All Ads from XDA
Post Reply Email Thread
** NOT Android 4.3 compatible!!! Term-init is recommended for now!!!

**Note...this is only for those who do not have init.d support...if you are using custom kernels (cyanogen mod original kernel etc.) that already supports init.d, you shouldn't run this......but if you accidentally ran this, it is ok...won't mess up anything...


v1.0
init.d support through an app!!!



What is init.d:
Quote:
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.

But how?
Concept:
I have recently learnt some linux scripting and was searching for a method to enable init.d scripts support for my phone which has a stock kernel. Inspired by this thread by iridaki, I finally managed to get init.d working in my phone!!! However, I thought of the other users who still do not have a proper custom recovery...how are they gonna flash zip packages? And if it has to be done manually, it requires a lot of typing, changing file permissions etc....a very tedious process...

Therefore, I've decided to come up with a script to automate this process!!! *Drum rolls*...lol

BUT now, with the aid of Androguide.fr (creator of Pimp My ROM), we managed to integrate the script into an app to save the hassle of typing commands in terminal emulator! With just a button click, the commands will be carried out! With just a button click, the app will verify whether is there init.d support or not!


Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: Attachment 1612958
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. 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"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. 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.



Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing (shows time of execution), another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors



Requirements:
- a rooted phone of course...

- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script......use "normal install" method, don't use "smart install"...



Instructions:
1. Download the apk.
2. Install the apk like any normal app.
3. Launch the app.
4. The rest are pretty self-explanatory...
5. You can uninstall the app after that...

Screenshots:


**To check whether init.d is really working or not, reboot your phone and navigate to /data...you should find a Test.log in there...If it is present, congrats, you have a WORKING init.d support!



Download:
If you have already read all the instructions and understand them, then click here to download:





Credits:
Thanks to:
Androguide.fr for the android app base!


Donators (big thank you! ):
@bigknowz


Feel free to posts questions below...I will try my best to help......By the way, those who used the app and found that it works, please leave a post here, stating you phone model, android version and ROM...thanks! but don't just leave comnents saying 'it doesn't work' etc...give more details if possible...


Please don't mirror / modify my work, ask for permissions first...
The Following 466 Users Say Thank You to Ryuinferno For This Useful Post: [ View ] Gift Ryuinferno Ad-Free
12th October 2012, 07:26 PM |#2  
Ryuinferno's Avatar
OP Senior Member
Thanks Meter: 7,229
 
Donate to Me
More
**UPDATE: v3 is out now! Android 4.3 compatible!

**Term-init is also used in Droid Manager!!!**

**Featured in the XDA News Portal: Init.d Support for Any Rooted Phone (Thanks to the_scotsman!)


Hi guys...as stated in the title above, I have created a script to be ran in terminal emulator so that it will enable the support of init.d scripts!!!

**Note...this is only for those who do not have init.d support...if you are using custom kernels (cyanogen mod original kernel etc.) that already supports init.d, you shouldn't run this......but if you accidentally ran this, it is ok...won't mess up anything...



init.d support through terminal emulator!!!



What is init.d:
Quote:
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.

But how?
Concept:
I have recently learnt some linux scripting and was searching for a method to enable init.d scripts support for my phone which has a stock kernel. Inspired by this thread by iridaki, I finally managed to get init.d working in my phone!!! However, I thought of the other users who still do not have a proper custom recovery...how are they gonna flash zip packages? And if it has to be done manually, it requires a lot of typing, changing file permissions etc....a very tedious process...

Therefore, I've decided to come up with a script to automate this process!!! *Drum rolls*...lol


Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: test_initd.zip
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. 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"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. 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.



Features:
- Auto checks for required files [v2]
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will move install-recovery.sh to install-recovery-2.sh if it already exists and call it from the main install-recovery.sh (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't [v3]
- If Superuser is using install-recovery.sh, will use install-recovery-2.sh instead [v3]
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing (shows time of execution [v2]), another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists. This is for utilising a similar method to enabling init.d in AOSP ROMs



Requirements:
- a rooted phone of course...

- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script......use "normal install" method, don't use "smart install"...

- terminal emulator such as this: Link



Instructions:
1. Download the file.
2. Place it in the root of your sdcard directory.
3. Launch terminal emulator.
4. Type: su
5. Grant SuperUser access if prompted
6. Type: sh /sdcard/term-init.sh
7. The script will run and follow the instructions! As simple as that...

**To check whether init.d is working or not, reboot your phone and navigate to /data...you should find a Test.log in there...If it is present, congrats, you have init.d support!



Download:
If you have already read all the instructions and understand them, then click here to download:




Feel free to posts questions below...I will try my best to help......By the way, those who used my script and found that it works, please leave a post here, stating you phone model, android version and ROM...thanks! but don't just leave comnents saying 'it doesn't work' etc...give more details and screenshots if possible...


Please don't mirror / modify my work, ask for permissions first...

Source code & changelog: https://github.com/Ryuinferno/Term-init
The Following 149 Users Say Thank You to Ryuinferno For This Useful Post: [ View ] Gift Ryuinferno Ad-Free
12th October 2012, 07:27 PM |#3  
Ryuinferno's Avatar
OP Senior Member
Thanks Meter: 7,229
 
Donate to Me
More
** NOT Android 4.3 compatible!!! Term-init is recommended for now!!!

**Note...this is only for those who do not have init.d support...if you are using custom kernels (cyanogen mod original kernel etc.) that already supports init.d, you shouldn't run this......but if you accidentally ran this, it is ok...won't mess up anything...

As Term-init does not work for certain people, I have came up with a CWM flashable zip:


init.d support through CWM!!!



What is init.d:
Quote:
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.


Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: test_initd.zip
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. 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"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. 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.



Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing, another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors



Requirements:
- a rooted phone of course...

- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script......use "normal install" method, don't use "smart install"...
- a working CWM custom recovery



Instructions:
1. Download the file.
2. Flash zip-init.zip thorough CWM.
3. Reboot and you are done!

**If you get a status 0 error in CWM, please replace the update-binary in zip-init.zip with a working update-binary of your phone (just extract it from any CWM zip meant for your phone)...

**To check whether init.d is working or not, reboot your phone and navigate to /data...you should find a Test.log in there...If it is present, congrats, you have init.d support!



Download:
If you have already read all the instructions and understand them, then click here to download:




Feel free to posts questions below...I will try my best to help......By the way, those who used my mod and found that it works, please leave a post here, stating you phone model, android version and ROM...thanks! but don't just leave comnents saying 'it doesn't work' etc...give more details and screenshots if possible...


Please don't mirror / modify my work, ask for permissions first...
The Following 59 Users Say Thank You to Ryuinferno For This Useful Post: [ View ] Gift Ryuinferno Ad-Free
23rd April 2013, 02:41 AM |#4  
ken_alpha24's Avatar
Senior Member
Thanks Meter: 235
 
More
i dont get it... what are you suppose to do in the update-binary? where do i get it? and how do i get it?
23rd April 2013, 02:02 PM |#5  
Member
Flag Pune
Thanks Meter: 28
 
More
not working for me.
here are the details:
i have Galaxy S3 International I9300 version on stock 4.1.2 firmware. it's rooted.
i installed busybox first. when i run it, it asked for superuser permissions which i granted. it automatically started smart install after i run it. then i waited this smart install to finish. then i clicked install and it asked for smart or normal install. i selected normal install. i install in xbin this time.
then i installed your v1 apk file and clicked activate. after it's success message i clicked verify. this time also got the message done.
then i rebooted 3 times but couldn't find test.log in /data.
then i moved to your troubleshoot steps:

1. Check whether have you installed busybox properly, especially run-parts. REBOOT after installing, then only apply this script.
done
2. If you are using the busybox installer by Stericson, please use "normal installation method", NOT "smart installation method".
done
3. Check whether are these files present with the correct permissions (please change if the permissions are wrong):
- /system/bin/sysint (rwxr-xr-x) [owner: root (0), group: shell (2000)]
- /system/etc/init.d (rwxrwxrwx) [owner: root (0), group: root (0)]
- /system/etc/init.d/00test (rwxrwxrwx) [owner: root (0), group: root (0)]
-/system/etc/init.d/08setperm (rwxrwxrwx) [owner: root (0), group: root (0)]
- /system/etc/install-recovery.sh (rwxr-xr-x) [owner: root (0), group: root (0)]

done - corrected the permissions of init.d folder and files inside it
4. Check whether you have run-parts installed. Go to /system/xbin, you should be able to find a fine named "run-parts"
i couldn't find run-parts in this folder so i downloaded and copied as per your instructions.
5. Check whether you have these lines in /system/etc/install-recovery.sh (if not, please add them in manually, remember to leave an EMPTY line at the end of the file)
Code:

# init.d support
busybox run-parts /system/etc/init.d/

corrected as per your instructions

6. If all the above are still not helping, please download this: run-parts.zip and extract it (DO NOT flash it). Place the file named "run-parts" in /system/xbin. Change permissions to rwxrwxrwx, owner to root (o) and group to shell (2000). Reboot and check /data again.

done. permissions are set


Now i repeated the process again with apk file after all these checks. but again couldn't find test.log

then i did step 7 also:
7. Use this as a last resort: Download Script Manager from Play Store: Link. Then navigate to /etc/install-recovery.sh, select it and run as root and at boot (select the skull and gear icon).
did it but no luck

then i tried term-init and zip-init methods also but no lock again.
term-init method: all the message were shown OK and done.

i can't understand what am i doing wrong.
The Following User Says Thank You to mintume For This Useful Post: [ View ] Gift mintume Ad-Free
30th April 2013, 09:24 AM |#6  
tjkingg's Avatar
Senior Member
Flag Mumbai
Thanks Meter: 67
 
More
Quote:
Originally Posted by Ryuinferno

**Note...this is only for those who do not have init.d support...if you are using custom kernels (cyanogen mod original kernel etc.) that already supports init.d, you shouldn't run this......but if you accidentally ran this, it is ok...won't mess up anything...

As Term-init does not work for certain people, I have came up with a CWM flashable zip:


init.d support through CWM!!!



What is init.d:



Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: test_initd.zip
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. 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"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. 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.



Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing, another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors



Requirements:
- a rooted phone of course...

- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script......use "normal install" method, don't use "smart install"...
- a working CWM custom recovery



Instructions:
1. Download the file.
2. Flash zip-init.zip thorough CWM.
3. Reboot and you are done!

**If you get a status 0 error in CWM, please replace the update-binary in zip-init.zip with a working update-binary of your phone (just extract it from any CWM zip meant for your phone)...

**To check whether init.d is working or not, reboot your phone and navigate to /data...you should find a Test.log in there...If it is present, congrats, you have init.d support!



Download:
If you have already read all the instructions and understand them, then click here to download:




Feel free to posts questions below...I will try my best to help......By the way, those who used my mod and found that it works, please leave a post here, stating you phone model, android version and ROM...thanks! but don't just leave comnents saying 'it doesn't work' etc...give more details and screenshots if possible...


Please don't mirror / modify my work, ask for permissions first...

worked!! thanks mate!
now since my Tab has the init.d support...can any1 tell me which are the helpful scripts that i can flash??
30th April 2013, 02:59 PM |#7  
ArtfulDodger's Avatar
Senior Member
Flag Louisville
Thanks Meter: 1,469
 
More
Quote:
Originally Posted by tjkingg

worked!! thanks mate!
now since my Tab has the init.d support...can any1 tell me which are the helpful scripts that i can flash??

V6, Crossbreeder and NOS.

Sent from my Baked Samsung Galaxy Exhibit with special ingredient NOS.
The Following User Says Thank You to ArtfulDodger For This Useful Post: [ View ] Gift ArtfulDodger Ad-Free
30th April 2013, 04:54 PM |#8  
tjkingg's Avatar
Senior Member
Flag Mumbai
Thanks Meter: 67
 
More
Quote:
Originally Posted by ArtfulDodger

V6, Crossbreeder and NOS.

Sent from my Baked Samsung Galaxy Exhibit with special ingredient NOS.

supercharged my device and m about to flash crossbreeder. can u provide the link for NOS??
wasnt able to find it.

Sent from my GT I9000 using xda premium
1st December 2013, 03:48 PM |#9  
Cyboy's Avatar
Senior Member
Thanks Meter: 54
 
More
Thumbs up Oh thank you
Quote:
Originally Posted by Ryuinferno

** NOT Android 4.3 compatible!!! Term-init is recommended for now!!!

**Note...this is only for those who do not have init.d support...if you are using custom kernels (cyanogen mod original kernel etc.) that already supports init.d, you shouldn't run this......but if you accidentally ran this, it is ok...won't mess up anything...

As Term-init does not work for certain people, I have came up with a CWM flashable zip:


init.d support through CWM!!!



What is init.d:



Do I have init.d support?:
Well, here is a way to test:
1. Download the file from here: test_initd.zip
2. Extract the file, you will get a file named 00test. DO NOT flash!
3. 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"
4. Change the permissions of the init.d folder and 00test into rwxrwxrwx.
5. Reboot.
6. 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.



Features:
- Utilises install-recovery.sh (if your kernel supports that, but of course, but most do...) to enable init.d scripts (busybox run-parts required)
- Will add lines in install-recovery.sh if it already exists (will not replace install-recovery.sh because certain apps such as Link2SD requires that to work), creates it if it doesn't
- Creates the init.d folder with correct permissions
- Adds 2 init.d scripts: one for testing, another to ensure that the scripts in init.d folder always have the correct permissions
- Adds sysinit in /system/bin, will add the required lines if it already exists
- Deletes duplicate files and lines to ensure the least of errors



Requirements:
- a rooted phone of course...

- busybox with required applets (especially run-parts), if not sure what is this, just install this by Stericson: Link and please reboot after installing before running this script......use "normal install" method, don't use "smart install"...
- a working CWM custom recovery



Instructions:
1. Download the file.
2. Flash zip-init.zip thorough CWM.
3. Reboot and you are done!

**If you get a status 0 error in CWM, please replace the update-binary in zip-init.zip with a working update-binary of your phone (just extract it from any CWM zip meant for your phone)...

**To check whether init.d is working or not, reboot your phone and navigate to /data...you should find a Test.log in there...If it is present, congrats, you have init.d support!



Download:
If you have already read all the instructions and understand them, then click here to download:




Feel free to posts questions below...I will try my best to help......By the way, those who used my mod and found that it works, please leave a post here, stating you phone model, android version and ROM...thanks! but don't just leave comnents saying 'it doesn't work' etc...give more details and screenshots if possible...


Please don't mirror / modify my work, ask for permissions first...

do all do the same?
so whats the diffrence ?
22nd November 2012, 05:02 PM |#10  
iamareebjamal's Avatar
Senior Member
Flag Batcave
Thanks Meter: 5,236
 
More
Links not working


Please fix them
Post Reply Subscribe to Thread

Tags
app, init.d, stock kernel, terminal emulator

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes