[MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!

Vagelis1608 · Feb 3, 2015

HdSht said:
Hello guys . I'd like to know which method should I use on lollipop. Ty in advance .

Term-init

Sent from my D620r [Stock 4.4.2]

amarc78 · Feb 6, 2015

I just wanted to throw this out there in case anyone hadn't noticed. If you use the Universal Init.d apk, and you change an init.d script and a .bak file is created you need to delete it because the app will still run the script.

thdervenis · Feb 13, 2015

Crashes on Moto G 2014

Crashes on app startup on rooted Moto G 2014.
Error report submited.

lucky_515 · Feb 15, 2015

thanks for this mod..very nice..im useing the pre installed init app on the rom xnote ported to sprint users on the note 3....i know the op says we can apply mods and scripts that apply on every boot..but can you give us more sripts to add?..how do we add more,i read can add scripts for battery tweaks and ect...how do we add more scripts?..do you have a few mods you can send me? so i can add them..interested in battery consumtion and performance..im useing stock kernal on the x note rom version 16,the latest version ported to sprint users

ehsanotaku · Feb 23, 2015

lucky_515 said:
thanks for this mod..very nice..im useing the pre installed init app on the rom xnote ported to sprint users on the note 3....i know the op says we can apply mods and scripts that apply on every boot..but can you give us more sripts to add?..how do we add more,i read can add scripts for battery tweaks and ect...how do we add more scripts?..do you have a few mods you can send me? so i can add them..interested in battery consumtion and performance..im useing stock kernal on the x note rom version 16,the latest version ported to sprint users

+1 yes this is caused some major concerns ,, Does "term-init" cause any problem with universal CronMod ( INTEXT + for instance , after Re-partitioning sd card , which is required for increasing the internal storage ) ?

lucky_515 · Feb 24, 2015

thank you for this..i used the apk on my note 3..im now useing note 4 edge..all stco,rooted..ive got cwm recovery installed..thinking best way for this phone is your cwm zip..looks to me after reading the several diff.ways to do this..the cwm may be my best bet..im not neer as talanted as you..some of your instructions actually scare me a little bit..but im determined to get this done..i want to know what scripts come preinstalled with this zip file,or do we need to add scripts ourself?...gues to put more simple,im not good enough to really understand all this,or tpo add scripts and get the most out my note edge,but i do know i want this on my phone..so im hopeing scripts are jus added by default,like on the xnote rom where i first saw this app ,it had several scripts..im hopeing all i got to do is flash the zip,and check to see if init.d is in fact installed..thank you for this..great work

alanthehat · Mar 2, 2015

The script checks for
root
busybox
grep

Then modifies (or creates)
/system/bin/sysinit
/system/etc/install-recovery.sh
/system/etc/install-recovery-2.sh
to include instructions to run init scripts
(Only one of these is likely to work, but if more than one work you should clean up the others)

Then creates
/etc/init.d/

Then puts 2 scripts into /etc/init.d/
test script
script to set permissions & ownership of init scripts

Any further scripts you will have to find or write for yourself

---------- Post added at 10:06 AM ---------- Previous post was at 09:26 AM ----------

It seems that the master Busybox at http://busybox.net conains the 'runit' init system that is the default 'init' for some Linuxes.

So some Android builds of 'busybox' also have it.

In my mind there are 2 advantages over 'run_parts'
1) it can be controlled with signals (kill <signal> <pid>)
2) it has a watchdog that restarts crashed scripts

There is one directory per function which contains scripts for 'start', 'stop' etc

See http://smarden.org/runit/ for the full implementation of which this is a viable subset

tonyafc · Mar 11, 2015

Can someone help im on lollipop rooted busybox stock kernel no matter what i do i cant get testlog in data i get both recoverysh and sysinit but no test log thanks in advance

el.quechon · Apr 24, 2015

tonyafc said:
Can someone help im on lollipop rooted busybox stock kernel no matter what i do i cant get testlog in data i get both recoverysh and sysinit but no test log thanks in advance

go to system/etc then find install-recovery.sh open it and delete everything in there paste this then:

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.

/system/etc/install-recovery-2.sh

After that safe and reboot and look for the test.log file in /data

Make sure to give proper permission before rebooting you can find that in op first post

bombadier · Jun 8, 2015

scripts in my init.d folder are not starting, those in su.d work fine, I have installed uni-init to test and everything looks good,anyone any ideas ?

Example
The script 00test which will create a log in /data, put the script in init.d it does not work, move it to su.d and rename it 00test.sh and it runs and generates a log in /data
I am on slimsaber which has init.d support and the app reports that everything is working, scripts in init.d do not work but manually running them does
Correct permissions etc
latest busybox 1.23.2
Also going to /system/etc/init.d and running the script manually works,just not at startup like it meant to.

Perseus · Jun 8, 2015

bombadier said:
scripts in my init.d folder are not starting, those in su.d work fine, I have installed uni-init to test and everything looks good,anyone any ideas ?

Example
The script 00test which will create a log in /data, put the script in init.d it does not work, move it to su.d and rename it 00test.sh and it runs and generates a log in /data
I am on slimsaber which has init.d support and the app reports that everything is working, scripts in init.d do not work but manually running them does
Correct permissions etc
latest busybox 1.23.2
Also going to /system/etc/init.d and running the script manually works,just not at startup like it meant to.

Can you please use System Manager to see if Scripts do get executed at Boot ? Alternatively Script Manager is also a good test.

If one or both fail then there's a chance your kernel does not look in init.d and you'd need to look into some sort of insmod option or continue Script manager.

bombadier · Jun 8, 2015

Perseus said:
Can you please use System Manager to see if Scripts do get executed at Boot ? Alternatively Script Manager is also a good test.

If one or both fail then there's a chance your kernel does not look in init.d and you'd need to look into some sort of insmod option or continue Script manager.

Thanks for the pointers,sorry dont understand how to check with system manager? is that an app ? Am using slimsaber and ak's kernel which is meant to have support, it seems like the init.d folder is definitely not being allowed to run at boot, odd that su.d is working, as I said I can run the script and it works, just not at startup

Perseus · Jun 8, 2015

bombadier said:
Thanks for the pointers,sorry dont understand how to check with system manager? is that an app ? Am using slimsaber and ak's kernel which is meant to have support, it seems like the init.d folder is definitely not being allowed to run at boot, odd that su.d is working, as I said I can run the script and it works, just not at startup

Can you Try SManager AKA Script Manager ?

Meant to say [APP 2.1+] System Tuner not Manager.

bombadier · Jun 8, 2015

Perseus said:
Can you Try SManager AKA Script Manager ?

Meant to say [APP 2.1+] System Tuner not Manager. [emoji14]

Now I found the app but still not sure how to use it to show what got ran on boot,although I suspect that it will show the scripts not being ran,will ask in ak's thread to see if its something with the kernel,
The same script with a .sh added execute on startup from the su.d folder,hope that makes sense?
Ok asked in ak's thread and he says known limitation with lollipop,that will be that then

tapatyping fae the bacon

alanthehat · Jun 16, 2015

Code:

su
mkdir /data/logs
chmod 0777 /data/logs
touch /data/logs/startup.log

Then, in every startup script:

Code:

echo $(date) $0 >> /data/logs/startup.log

will tell you what has run & when (you can substitute the name of the script for '$0')

Code:

cat /data/logs/startup.log

viaimpedita · Jun 21, 2015

Some one can help me?
I don't nave log in data after reboot.
I try run script install-recovery.sh an install-recovery-2.sh with script manager bit i have this error :

Only position indipendent executables (PIE) are supported
I have fonetab 8 with lollipop

EDIT : i solved get runparts file from my samsung s4 mini

:crying::crying::crying::crying::crying:
EDIT 2 : Also for me the script do't run at boot, why??
If i run script with script manager i have testlog i data

Thanks all

Sent from my GT-I9195 using XDA Free mobile app

Ulf3000 · Sep 17, 2015

working on z3c kitkat stock ! thanx so much ^^

kiaheyrati038 · Sep 19, 2015

Ryuinferno said:
**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:

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: View 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:
- 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:

term-init.sh v3

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

tnx man.it worked great on Xperia V lt25i 4.3 rooted stock ROM.:good:

famewolf · Oct 7, 2015

Is there a way to apply init.d to a flashable zip of the stock rom?

kos25k · Oct 30, 2015

hello guys!can anyone please tell me how to make this https://github.com/poliva/random-scripts/blob/master/wifi/hotspot-bypass-android.sh an executable script?

[MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!

Senior Member

amarc78

Guest

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Senior Moderator / Recognized Developer

Senior Member

Retired Senior Moderator / Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Similar threads

Top Liked Posts