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

Search This thread
By:
Advanced…
M

Mr_Biggles

Member
Aug 3, 2012
31
1
The Big Smoke
Worked like a million bucks for me. Using an LG C800G running stock GB. One reboot and the Test.log was there. Also confirmed through V6 Supercharger and KAK. Thanks.
 
J

josefaquinojr

Member
Nov 13, 2010
21
1
Pasig
no errors but empty /data/

title says it all.

followed the instructions to the letter, console window says successful install.

restarted 4 times. /data/ folder is still empty.

cherry mobile w100.
 
bruce16878

bruce16878

Senior Member
Aug 31, 2012
161
23
test.log found in /DATE but init.d folder isn't created on Galaxy tab 7.7, is that ok?

Sent from my GT-P6800 using xda app-developers app
 
Ryuinferno

Ryuinferno

Senior Member
Apr 3, 2012
3,548
7,113
ryuinferno.github.io
josefaquinojr said:
title says it all.

followed the instructions to the letter, console window says successful install.

restarted 4 times. /data/ folder is still empty.

cherry mobile w100.
Click to expand...
Click to collapse

Ok...have you installed busybox with all the applets especially run-parts? Refer to the discussion before this, a user can't get it working because he was lack of run-parts...:)





bruce16878 said:
test.log found in /DATE but init.d folder isn't created on Galaxy tab 7.7, is that ok?

Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse

Hmm...init.d folder is in /system/etc...could you find it? :) If you have Test.log, means that the folder should be present..
 
J

josefaquinojr

Member
Nov 13, 2010
21
1
Pasig
Ryuinferno said:
Ok...have you installed busybox with all the applets especially run-parts? Refer to the discussion before this, a user can't get it working because he was lack of run-parts...:)


Thanks for replying. I used Busybox installer (stephen erickson) smart install function. after installation, applet manager says run-parts is symlinked to: /system/bin/busybox.

is this right or do i have to do something else?
Click to expand...
Click to collapse
 
Ryuinferno

Ryuinferno

Senior Member
Apr 3, 2012
3,548
7,113
ryuinferno.github.io
Ok...use the normal install method...as stated there, it is safer and much more effective...:)...and reboot after installing before running the script...
 
Last edited:
J

josefaquinojr

Member
Nov 13, 2010
21
1
Pasig
Ryuinferno said:
Ok...use the normal install method...as stated there, it is safer and much more effective...:)...and reboot after installing before running the script...
Click to expand...
Click to collapse

damn! im terribly sorry about missing the "normal" install mode note.

i am trying it now and will update asap.

---------- Post added at 04:00 AM ---------- Previous post was at 03:26 AM ----------

after installing in "normal mode", rebooted once, run script, rebooted thrice.

there is still nothing in /data/ folder. can you help me out?

---------- Post added at 04:40 AM ---------- Previous post was at 04:00 AM ----------

how do i check if my device kernel supports install-recovery.sh on startup?

My device is a Cherry Mobile W100
Successfully rooted via POOT
 
Last edited:
J

josefaquinojr

Member
Nov 13, 2010
21
1
Pasig
Ryuinferno said:
Ok...can you run the script and screenshot the output? And check whether is there any init.d folder in /system/etc, a file named sysint in /system/bin and a file named install-recovery.sh in /system/etc? :)
Click to expand...
Click to collapse

yes there is a /system/etc/init.d folder with two files inside.
yes there is a /system/bin/sysinit file
yes there is a /system/etc/install-recovery.sh

run-parts is also installed:
ScreenShot-2.jpg


here is the script output:
ScreenShot-1.jpg
 
J

josefaquinojr

Member
Nov 13, 2010
21
1
Pasig
ok so this is weird, I was playing around with the terminal, executing run-parts /system/etc/init.d -- it looks like it was executing, but going back to ES Explorer and browsing /data/ folder, it was still empty.

But when i tried to execute

sh /system/etc/init.d/00test

and going back to the /data/ folder, all of these other folders and files(probably created by link2sd) along with the test.log were created right in front of my eyes. am not sure what triggered this but after deleting the test.log and restarting, lo and behold it was re-created.

am trying to delete the test.log again and restart but i am confident that its going to be there when i do.

thank you so much Ryuinferno!
 
  • Like
Reactions: sethgreen
Ryuinferno

Ryuinferno

Senior Member
Apr 3, 2012
3,548
7,113
ryuinferno.github.io
josefaquinojr said:
ok so this is weird, I was playing around with the terminal, executing run-parts /system/etc/init.d -- it looks like it was executing, but going back to ES Explorer and browsing /data/ folder, it was still empty.

But when i tried to execute

sh /system/etc/init.d/00test

and going back to the /data/ folder, all of these other folders and files(probably created by link2sd) along with the test.log were created right in front of my eyes. am not sure what triggered this but after deleting the test.log and restarting, lo and behold it was re-created.

am trying to delete the test.log again and restart but i am confident that its going to be there when i do.

thank you so much Ryuinferno!
Click to expand...
Click to collapse

No prob...just hit the thanks button next time...saves space...:D...actually, since you mentioned that you are using Link2SD, I remembered something...try to view what is inside install-recovery.sh...check whether are these lines present or not:
Code: 
# init.d support
run-parts /system/etc/init.d/

If no, add them in manually...remember to leave an empty line at the end (press enter after the last line)...then reboot...everything should work fine then...:)...Link2SD is install-recovery.sh dependent, so your case is a bit hard...although my script won't mess it up, but maybe Link2SD will mess up mine...XD...you excecuted 00test manually, of course there will Test.log in /data...the script was supposed to run at boot...:p
 
  • Like
Reactions: subnoize soulja
You must log in or register to reply here.

Similar threads

Snoop05
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
Replies
2K
Views
7M
McAsia
McAsia
Androguide.fr
☠ [APK][Tweaks & Mods] █ PIMP MY ROM █ BETA v1.0 {Any Device // Any Rom} ☠
Replies
5K
Views
2M
amman74
amman74
amarullz
[CWM-APP][2.00] AROMA Filemanager + TERMINAL :: 15022810 :: Open Source
Replies
1K
Views
2M
I
ivergad13
L
[APK] Seeder 2.0.0 entropy generator to provide significant lag reduction
Replies
4K
Views
3M
ravingrabbid_
ravingrabbid_
osm0sis
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Replies
4K
Views
1M
Vision
Vision

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 463
    Ryuinferno
    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...:D


    2OgMJ.png
    v1.0
    init.d support through an app!!!​


    What is init.d:
    the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
    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.
    Click to expand...
    Click to collapse

    But how? :confused:
    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!!! :D 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! :D


    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:
    - 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...:p

    - 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:
    83qRd.png
    rfpyz.png


    **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! :D


    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...;)​
    View
    149
    Ryuinferno
    Ryuinferno
    **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!!! :D

    **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...:D


    WdW7A.png

    init.d support through terminal emulator!!!​


    What is init.d:
    the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
    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.
    Click to expand...
    Click to collapse

    But how? :confused:
    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!!! :D 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 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...:p

    - 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! :D 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​
    View
    59
    Ryuinferno
    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...:D

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

    kKjNl.png

    init.d support through CWM!!!     ​


    What is init.d:
    the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
    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.
    Click to expand...
    Click to collapse


    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...:p

    - 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! :D

    **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...;)​
    View
    37
    Ryuinferno
    Ryuinferno
    Troubleshooting

    Troubleshooting:
    **CWM might warn something about disable recovery flash when using this mod, it is just a false positive, please DO NOT select yes or else it won't work anymore**

    If you have already applied the script but there is no /data/Test.log, please refer the steps below:
    1. Check whether have you installed busybox properly, especially run-parts. REBOOT after installing, then only apply this script.
    2. If you are using the busybox installer by Stericson, please use "normal installation method", NOT "smart installation method".
    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)]
    - /system/etc/install-recovery-2.sh (rwxr-xr-x) [owner: root (0), group: root (0)] (may or may not be present)
    4. Check whether you have run-parts installed. Go to /system/xbin, you should be able to find a fine named "run-parts"
    5. Check whether you have these lines in /system/etc/install-recovery.sh (if not, please add them in manually (using Root Explorer or keep the EOL in Unix format...Google about it), remember to leave an EMPTY line at the end of the file)
    Code: 
     # init.d support
busybox run-parts /system/etc/init.d/
    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.
    7. Still fails? Check your /init.rc for any lines containing "install-recovery"...if there are none, this method won't work...so use the Script Manager method.
    8. 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).
    9. If all the above are not working, and the "install-recovery" line is present, then please paste the contents of your /etc/install-recovery.sh and /etc/install-recovery-2.sh if present somewhere (like http://pastebin.com and after applying the mod of course) here for me to debug. Take a screenshot of the output after running Term-init and post here, along with your ROM version, android version and name of device.
    View
    7
    Androguide.fr
    Androguide.fr
    @Ryuinferno Hey bro!
    While working on Pimp my Rom's bew beta, I came up with a way to grant init.d support to any device, which happens all on the app side, no need for install-recovery.sh (or any other file) modifications.

    The concept is very simple but it's what makes it powerful and truly universal :

    Using Android's BroadcastReceivers mechanism, the app detects whenever the device is rebooted, and when it does, after the boot is completed, it will execute all the scripts inside /system/etc/init.d automatically.
    I also refined the kernel init.d support testing, it now requires a reboot but will really detect if the user's kernel has init.d support by creating a simple init.d script that creates a file on the sdcard, and after the reboot, the app will check if the file has indeed been generated, if it does, the kernel has init.d support so the app is useless, otherwise, it doesn't.

    Finally, I added options to manage the init.d scripts (edit/delete/run), and will probably soon add an option to select your "init.d" folder (i.e make it so that /sdcard/newinitd is considered as /system/etc/init.d and the app will execute all the scripts in it instead of in the real init.d folder).

    The standalone app is fully open-source, so if you want to fork it/add it here/modify it to your needs, go ahead, it's yours : http://github.com/Androguide/Universal-init.d
    I attached a signed apk to this post.

    Here are a few screenshots :

    framed-initd1.jpg
    framed-initd2.jpg
    framed_initd3.jpg
    framed-initd4.jpg
    framed-initd5.jpg
    framed-initd6.jpg


    Also, I wanted to ask you some help ;
    I could definitely use your bash knowledge for a new project I started, which allows to flash zips without using a recovery, if you got time, please go take a look and tell me if you see any mistake or better bash translations of updater-script commands. (thread here)



    -
    View

New posts