[MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!
- Thread starter Ryuinferno
- Start date
Check init.d settings
I wrote a script that allows you to check what settings (using echo command) are in your init.d vs. the actual settings on the phone. A file showsettings.txt is created in /sdcard with all the values. Link to the file is in my signature, just change the extension from .txt before you run it in smanager or terminal.
I wrote a script that allows you to check what settings (using echo command) are in your init.d vs. the actual settings on the phone. A file showsettings.txt is created in /sdcard with all the values. Link to the file is in my signature, just change the extension from .txt before you run it in smanager or terminal.
Me?
Was that comment directed to me?
It is kinda rude to pop in someone else's thread and advertise...
EDIT: Your link isn't working btw...
Was that comment directed to me?
Have you checked the first couple of posts by the OP?
Sent from my A500 using xda app-developers app
Custom Rom inclusion
First off, I wish to thank for such an outstanding mod. This is awesome.
The APK does the job very well. The test does establish that init.d is working successfully after the APK enables it.
I have a slightly different problem. I am trying to enable init.d support in a custom ROM I am building. Here's the steps I followed so far without success.
1. Add lines at the bottom of existing install-recovery script to execute init.d.
run-parts /system/etc/init.d
2. I added the init.d folder with the sample test script from this thread.
3. Set the permissions to 644 on the init.d as well as the test scripts inside. Also set 755 on the install-recovery.
4. Since those permissions did not work, I tried 755 on the init.d folder and scripts inside.
5. I did copy the run-parts binary to /system/xbin folder and made sure it had executable permissions. All objects have root as owner (0).
Yet I don't see the test log in /data folder.
Note I do see a successful test log upon using the Universal init.d app.
Can someone help me pin point the issue ?
First off, I wish to thank for such an outstanding mod. This is awesome.
The APK does the job very well. The test does establish that init.d is working successfully after the APK enables it.
I have a slightly different problem. I am trying to enable init.d support in a custom ROM I am building. Here's the steps I followed so far without success.
1. Add lines at the bottom of existing install-recovery script to execute init.d.
run-parts /system/etc/init.d
2. I added the init.d folder with the sample test script from this thread.
3. Set the permissions to 644 on the init.d as well as the test scripts inside. Also set 755 on the install-recovery.
4. Since those permissions did not work, I tried 755 on the init.d folder and scripts inside.
5. I did copy the run-parts binary to /system/xbin folder and made sure it had executable permissions. All objects have root as owner (0).
Yet I don't see the test log in /data folder.
Note I do see a successful test log upon using the Universal init.d app.
Can someone help me pin point the issue ?
Thanks Ryuinferno. Appreciate the advice. I will test and post back the result.
I have done everything according to your guide but I can't get in init.d support! I can't see testlog in /data, I have installed the mod using terminal emulator and even tried through app!
Sent from my LG P500 eating tastiest gingerbread ever!
Sent from my LG P500 eating tastiest gingerbread ever!
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?
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.
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.
Your busybox must be corrupted...I said, use normal installation right from the beginning...type this in terminal emulator and post the output:
Code:
which run-partsAlso look for any lines that contain "install-recovery" in /init.rc...if you can't find one, means this hack will not work for you...
I have done everything according to your guide but I can't get in init.d support! I can't see testlog in /data, I have installed the mod using terminal emulator and even tried through app!
Sent from my LG P500 eating tastiest gingerbread ever!
No details, no support...
I checked init.rc, there is line which contains install-recovery.
Here is output of 'which run-parts' on terminal: system/xbin/run-parts
No idea then...things should work...delete install-recovery.sh and start over...or just use a custom kernel...there are many for the s3 anyway...to me, it seems that your busybox is acting weirdly...cause the script manager trick always works...
every step i followed and its say done without any error message (i believe my eyes still good) using term-ini.sh
i've rebooted twice but, there is no test.log in my /data folder
i'm using samsung galaxy mini, gingerbread XWKT9
i've rebooted twice but, there is no test.log in my /data folder
i'm using samsung galaxy mini, gingerbread XWKT9
Last edited:
Post your /etc/install-recovery.sh here...and check whether /init.rc has the line "install-recovery" in it or not...my guess is that you are using Link2sd or something similar...So install-recovery.sh might be modified...
@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 :
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)
-
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 :
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)
-
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
463** 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:
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
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: 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...
- 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...149**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:
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
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 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-init59** 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:
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:
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...37Troubleshooting
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)
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.Code:# init.d support busybox run-parts /system/etc/init.d/
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.7@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 :
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)
-
