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

kaizokan · Jul 27, 2017

remi13014 said:
Yo, I installed Uni-unit but when I click on activate/verify It wants open store to install Superuser but i'm already rooted ( I got SuperSU2.79, busybox etc....)
I got a Honor 8 with stock rom Nougat

~~Did you manage to get it working? and how?~~
EDIT: never mind. I now used the terminal method. no test.log yet.

landcruser · Oct 24, 2017

i have huawei mate9 with Android version 7.0，try every method and not working also follow the advices so i have to post the screenshot..
and the contents of /etc/install-recovery.sh as follow
#!/system/bin/sh
# init.d support

/system/bin/sysinit

any ideas?thanks

通过我的 MHA-AL00 上的 Tapatalk发言

post-mortem · Oct 24, 2017

landcruser said:
i have huawei mate9 with Android version 7.0，try every method and not working also follow the advices so i have to post the screenshot..
and the contents of /etc/install-recovery.sh as follow
#!/system/bin/sh
# init.d support

/system/bin/sysinit

any ideas?thanks

If you're running Android 7.0, you don't need this. As the first 2 lines of the output in your screenshot show, you should already have native init.d support.

landcruser · Oct 24, 2017

post-mortem said:
If you're running Android 7.0, you don't need this. As the first 2 lines of the output in your screenshot show, you should already have native init.d support.

the question is the init.d seems not work .scripts not execut at boot

Medeon · Feb 5, 2018

Ryuinferno; said:
- /system/etc/install-recovery.sh (rwxr-xr-x) [owner: root (0), group: root (0)]

Initially my Sony Xperia m5 smartphone running android 6.0 didn't suport init.d so I had to manually add the folder in the /etc folder. Followed all the nessecery steps including chance file permissions. I have got a recent version of busybox by Osm0sis installed which includes the run-parts applet (for a full overview of applets see screenshot I added). Finally got init.d support by installing the app and when I verified wheter it was installed correctly it confirmed me Init.d now was supported on my device. However when checking the test.log file I didn't find it in the /data folder (nor anywhere). So I decided to check the troubleshooting guide and finally found out that al the files are there with the right permissions, except from the install-recovery.sh Where did it go wrong? Could you help me out? I'd really appreciate that.

Medeon · Feb 5, 2018

Actually I overlooked the install-recovery.sh file (I was looking for it in the init.d folder

). I added 'busybox' to the lines since it was the only missing word in the program file. Still no test.log file in the /data folder.

However something strange occured to me when I second checked all the files. The sysint file in the system/bin folder would temporarily be present whenever I (re)activate init.d support trough the app. Then after rebooting the device it completely dissapeared as if it never existed inside the system/bin folder (this time I double checked

). Do you have idea how this could be?

Saswata Chakraborty · Mar 19, 2018

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

So, after placing the file in the root of sdcard directory, I typed sh /sdcard/term-init.sh and guess what, it said no file or directory found. Then i used my brain and typed sh /root/term-init.sh and it worked. But when I rebooted my device twice and checked /data, no Test.log found. Does it mean my device doesn't support init.d? And if not, will there be any problem since ran the term-init.sh file through terminal emulator? By the way I am using Xiaomi Mi A1 (Nougat 7.1.2) with Magisk root.

jagster936 · Apr 7, 2018

Does this work on android 5.0.1? Verizon s4 PL1 firmware. I’m looking to disable ipv6 permanently by running startup script.

alecxs · May 22, 2018

does not work on Lollipop. because install-recovery.sh is executed with very restrictive selinux context.
– Source: Chainfire Google+
Try to set selinux permissive with SELinuxModeChanger first. Then try to install init.d

edit: app is no longer available on google play, is this project discontinued? May I suggest flashable Kernel init.d Support Injector - the author @osm0sis claims this zip is also signed, so could potentially be used with stock recovery on a locked bootloader.

osm0sis · May 22, 2018

aIecxs said:
does not work on Lollipop. because install-recovery.sh is executed with very restrictive selinux context.
– Source: Chainfire Google+
Try to set selinux permissive with SELinuxModeChanger first. Then try to install init.d

edit: app is no longer available on google play, is this project discontinued? May I suggest flashable Kernel init.d Support Injector - the author @osm0sis claims this zip is also signed, so could potentially be used with stock recovery on a locked bootloader.

You're better off using su.d (SuperSU) or post-fs-data.d (Magisk) than trying to get init.d to work.

xXCoolGuYXx · Jun 1, 2018

Will this work on a LG V20 H91810q T-Mobile on magisk 16.0v root ?

kblade29m · Sep 1, 2018

Getting error "Read-only file system" when the script try to copy the sysinit and install-recovery.sh. For some unknown reason, the script failed to mount /system as rewritable due to "Device is busy".
Manually run -- "mount -o rw,remount /system" in adb shell.
Re-run the script "sh term-init.sh"
All executed properly.
The script seem to work fine.
Thanks.

ranchu-panchu · Sep 7, 2018

Hello,
Is there a way to start the init script a bit earlier ? I see that UI starts before my scripts, but I need the script to start before UI.

Is there a way I can make it earlier ? Or do I need to find other method ?

Thank you very much for the init.d tool, it's very good.

ranran

HemanthJabalpuri · Sep 26, 2018

hi..

My device successfully supports init.d...
Android v4.4.2 Device SamsungGalaxy S4 Mini GT-I9192(serranodsdd) ..ROM stock touchwiz...

I have a doubt..
When i enabled init.d through app the sysinit script is

Code:

#!/system/bin/sh
# Init.d support
# Ryuinferno @ XDA 2012

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper run-parts /system/etc/init.d

and when I use term init script then the sysinit script is

Code:

#!/system/bin/sh
# init.d support

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
run-parts /system/etc/init.d

Which is better?
What is the additional use of that /system/bin/logwrapper ?

站住那逗比 · Feb 21, 2019

Hello.

My Android TV box(GF-WM28H, Android 4.4.2) successfully supports init.d through your script file, thanks!

(This box is a deep customization Android, can just use system app, but leave a usb cable can use adb directly connect. Use this script to auto open network adb connection port ((which dropped default

That's all, thanks again!

Henry Markle · Feb 21, 2019

The download page is somewhat broken.
Could you uodate the download site?

clickmeplz · Aug 11, 2019

It works with script manager app or if i run sh /etc/install-recovery.sh at emulator.
But i have to run the command in each reboot or keep script manager app and i can not uninstall it.
Is there a better solution?
Device: Mi 4
Rom: Xiaomi eu
Kernel: ZeurionX

edzamber · Aug 11, 2019

clickmeplz said:
It works with script manager app or if i run sh /etc/install-recovery.sh at emulator.

But i have to run the command in each reboot or keep script manager app and i can not uninstall it.

Is there a better solution?

Device: Mi 4

Rom: Xiaomi eu

Kernel: ZeurionX

Hi

Yes

You need to add init.d support in your Kernel directly.

Ask to your Kernel dev to do it or edit your Kernel ramdisk.

https://mega.nz/#!7lFkjCoL!qliHaAMzFWv2ZT-PNwF9PgyU0U5OG-0NjXpcd-T9sAM

alecxs · Aug 11, 2019

for systemless root solution /su/su.d or /data/adb/post-fs-data.d and /data/adb/service.d

Deleted member 1890170 · Nov 4, 2019

For me Universal Init.d Support doesn't work on Android emulator named MEmu App Player: The message Success.!You have init.d support! simply is a fake.

It's not wondering me because neither init.rc and/or init.<machine_name>.rc - the files that are processed by Android's init at boot - nor any other hereby imported .rc file triggers sysinit.sh and/or install-recovery.sh script.

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

Senior Member

Member

Senior Member

Member

Senior Member

Attachments

Senior Member

Senior Member

Member

Forum Moderator

Senior Recognized Developer / Contributor

Senior Member

Member

Senior Member

Recognized Contributor

New member

Senior Member

Member

Senior Member

Forum Moderator

Deleted member 1890170

Guest

Similar threads

Top Liked Posts