yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] ArtfulDodger:
I can now save you a lot of detective work. Turns out two scripts in NOS were taking over 2 minutes to execute which would be over the timeout limit, thus causing ANR issues. I removed both of the problem ones, and now it seems scripts are executing at boot. I tested Crossbreeder and it works at boot. The test script you asked me to use now executes at boot!

Congrats, app works perfectly after all. Thank you very much for this useful tool.
[Android Software/Hacking General [Developers Only]] ArtfulDodger:
V6, Crossbreeder and NOS.

Sent from my Baked Samsung Galaxy Exhibit with special ingredient NOS.
[Android Software/Hacking General [Developers Only]] detdett:
NOS
[Android Software/Hacking General [Developers Only]] detdett:
You can always try V6 SuperCharger
[Android Software/Hacking General [Developers Only]] detdett:
good, in that case, you don't need anymore scripts. How's your phone performance thus far?
[Android Software/Hacking General [Developers Only]] les02jen17:
Thanks to this app, I successfully got init.d support on my phone! My question is, would uninstalling this app and factory resetting the device (wipe /date and /cache) remove the init.d support? TIA!!!
[Android Software/Hacking General [Developers Only]] ArtfulDodger:
Yes, you need to just reinstall the app and you'll have it again.

Sent from my Baked Samsung Galaxy Exhibit with special ingredient NOS.
[Android Software/Hacking General [Developers Only]] mintume:
Hello Sniperkill,

i couldn't get this script to work at all with all these 3 methods.

can you please tell me where can i find busybox 1.17.2 file to install? current busybox version is 9.2 which only gives option to install 1.20.1 onwards.

I have rooted Galaxy S3 international version.

thanks
[Android Software/Hacking General [Developers Only]] ArtfulDodger:
Well I ran into more ANR issues, this time with V6 scripts. I'm going to have to revert to Script Manager to run scripts on boot for now. Something causes the Universal support app to hang and I've noticed it's usually scripts that have a lot of lines in them. Short ones run with no problem. Makes sense but that means the timeout factor will cause this app to shut down and not run any scripts on boot, long or short.
[Android Software/Hacking General [Developers Only]] the-bomber:
working :3

samsung Galaxy Mini 2 (GT-S6500D)

rom : stock rom (gingerbread 2.3.6)

kernel : OC's kernel (squadzone)
[Android Software/Hacking General [Developers Only]] dmourao:
Not working for me... Tried on two different roms and kernels, "Universal Init.d Support" says "Sucess", but still my scripts wont load.

Device: Galaxy Nexus, 4.2.2.
[Android Software/Hacking General [Developers Only]] bigknowz:
Losing init.d after flashing

Ever since I flashed CWM 6.0.3.1 on my GNex toro, it gives me the message asking to fix recovery because ROM might overwrite no matter what I flash. Choosing yes seems to blow out init.d support. Didn't notice this issue with 6.0.2.3. ROM developer says clicking No will not affect recovery. Will that leave init.d permissions alone?

Also, is there a reason why install-recovery.sh has

run-parts /system/etx/init.d

instead of

busybox run-parts /system/etc/init.d ?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Yea...it won't affect..it is just a false positive...there's no difference between busybox run-parts and run-parts if you have already installed busybox...

Read through the FAQ please...and check if you have the phrase "install-recovery.sh" in /init.rc...or else it won't work...
[Android Software/Hacking General [Developers Only]] mw86:
Ryuinferno, Team Kernelizers would like to have your apk or cwm method in our TKmod aroma installer amongst our other recommended apps (free on the market). Im not sure you ever published this. In anycase we would be honored to supply your apk as an option. We do not take credit for any apps we have in the aroma installer as an option. Our tkmodhas build.prop, sysctrl, file manager, egl mod and we are always looking to expand. We help people over in our threads whenever we can. Ill grab link to TK thread verizon and sprint as sprint is the main and verizon has the latest OP currently.

http://xdaforums.com/showthread.php?t=2032956

[Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks {Aroma TK MOD 1.0.1}

http://xdaforums.com/showthread.php?t=2144004

[Team Kernelizers][How To][VZW][TK Mod 1.0.2]KT747 Kernel Tweaks - Updated 4-15-13
[Android Software/Hacking General [Developers Only]] Ryuinferno:
[MENTION=4745870]mw86[/MENTION] Sure, go ahead...:)...the app was not published on the market as I felt that there was no need to do so...and lack of funds...:o
[Android Software/Hacking General [Developers Only]] mw86:
Thank you kindly Ryuinferno :) and I fully understand the lack if funds, i hope things get better :)
[Android Software/Hacking General [Developers Only]] neurosis130:
works on my huawei u9508 xpw rom based on stock b026 and stock kernel .its easy to be done with the app method .

thank u so much for ur effort.i ll share with my friends.
[Android Software/Hacking General [Developers Only]] Deathshock01:
Thanks for that, I'll give it a try later. Question: when I install init.d then I can now install mod for my rooted phone or any script ?
[Android Software/Hacking General [Developers Only]] BajoPrimate:
Hi Deathshock01,

Yes, that's the point, you could use your "new" init.d suport for whatever you need.

Good luck.
[Android Software/Hacking General [Developers Only]] mandar_ez:
hi i tried the above instructions but didnt work..

i am using xperia ion stock, rooted, busybox installed, deodexed..

tried all three methods.. while using terminal emulator .. sh/ext_card/term-init.sh

sh: sh/ext_card/term-init.sh: not found

any help would be really appreciated
[Android Software/Hacking General [Developers Only]] Ryuinferno:
There should be a space between sh and /, like this: "sh /ext_card/term-init.sh"...Or just use the app...
[Android Software/Hacking General [Developers Only]] mandar_ez:
thank you..

got it to work..
[Android Software/Hacking General [Developers Only]] bassilap:
Only some scripts running?

I'm having a strange problem.

I have three scripts in the init.d folder

1) 00test -- this one seems to work every time. When I boot, there's a new time stamp in the test file (/data/Test.log)

2)gpx -- Never works

#!/system/bin/sh
#links My Tracks gpx folder to the gps logs folder

su
busybox mount -o bind /sdcard/GPSLogger /sdcard/MyTracks/gpx

The permission for all of these scripts is 777

When I execute the commands through a terminal emulator, they do work.

For the second script, I thought this might have to do with the timing (as in maybe /sdcard isn't mounted before the script runs), but i changed it to:

su
sleep 1m
busybox mount -o bind /sdcard/GPSLogger /sdcard/MyTracks/gpx

and it still doesn't work.

any thoughts?

Thanks.

Edit: So I think the problem lies with me improperly using su in the script, not the timing. Anyone know how I can execute the script or the command within the script as root?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Sorry but my thread is on enabling init.d support, so if init.d is already working, the rest is caused by the scripts themselves...try excecuting the scripts manually using script manager and see if it works...there should be no errors if the scripts are correct...
[Android Software/Hacking General [Developers Only]] bassilap:
Thanks for the reply. Yeah, i figured that it had to do with my scripts since the test one works. As I mentioned in an update of my post, I think it has to do with how I'm using su. I'm not sure to get the command to run as root.
[Android Software/Hacking General [Developers Only]] Omegadrive:
Hi, I'm having an issue on my Motorola Razr XT910, I'm using latest official rom from O2 JB 4.1.2, fully rooted, but for the life of me I can't seem to enable init.d support. I used Pimp my Rom to add support and the folder is there, but the permissions of the folder are rwx --- --- and can't be changed, I use ES File Explorer with root permission and says the folder permissions can't be changed. Also tried deleting the folder to recreate it and it doesn't let me delete it. Please help. :(
[Android Software/Hacking General [Developers Only]] Omegadrive:
That's one of the problems and why I noticed init.d was not working, when I try to copy any file to that folder it won't let me, can't copy any scripts to the etc/init.d folder for some reason, so I guessed it was the permissions, but it won't let me change them.

Also, tried changing the permissions for the "run-parts" (size 0kb) and "/system/etc/install-recovery.sh" so I can edit them and it won't let me change either.

UPDATE:

Ignore all, found that ES File Explorer had problems with root access, had to switch to FX File Manager, now managed to set all permissions and fixed the init.d support problem, woot!
[Android Software/Hacking General [Developers Only]] s30ckf:
Hi Dev,

I have read though and follow all the steps you stated, but I failed to get the test.log in /data

I install uni init.apk (not the rest)

I would like to ask, Busybox install, is should install to /system/bin or /system/xbin...

and how I know whether I'm install using normal mode or smart mode, as I only saw Install , Uninstall , Restore....
[Android Software/Hacking General [Developers Only]] s30ckf:
Hi Ryu,

I have clean flashed latest slim bean weekly 6.9, found that there is no init.d support. Thus I try the step you provided but still no luck:

1. Check whether have you installed busybox properly, especially run-parts. REBOOT after installing, then only apply this script. YES

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)]

YES, all fulfilled

4. Check whether you have run-parts installed. Go to /system/xbin, you should be able to find a fine named "run-parts" YES

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/ YES

Please assist. Thanks.
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
Try without the busybox

like this

Code:

# init.d support

run-parts /system/etc/init.d/
[Android Software/Hacking General [Developers Only]] s30ckf:
Had try this, but no luck.... :(

Anyway, thanks for your kind suggestion....
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
Have you checked /data if it is there a file named Test.log? If it is there, you have init working.

other thing, which version did you use, the app installer or the flashable version?

If you used one, try the other

Or if that don't work

try this, install link2sd and select a partition file system, doesn't matter if you won't use link2sd, it's just so it can create a new install-recovery.sh and fix permissions.

After reboot edit that file and place the lines for init.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
1. Check your /init.rc and see whether you have the "install-recovery" phrase in it or not

2. Did you install busybox? in /system/bin or /system/xbin, it does not matter...if you used the installer recommended in the OP, you have the option to use smart installation or normal installation...use normal

3. AOSP ROMs like Slim should already have init.d built in...it is impossible that you do not have init.d...

It's the same thing...

There's no point of doing that...my installer does the same, if it doesn't work now, it won't work with link2sd either...
[Android Software/Hacking General [Developers Only]] s30ckf:
Thanks for your suggestion, I will try another 2 more method (via TE and CMW) again to see it can works either.....

---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------

Hi Ryu, great and thanks that you have responded. Please see below:

1. Check your /init.rc and see whether you have the "install-recovery" phrase in it or not Yes, I saw this phase

2. Did you install busybox? in /system/bin or /system/xbin, it does not matter...if you used the installer recommended in the OP, you have the option to use smart installation or normal installation...use normal I have installed the recommended busybox, but when first time install, it doesn't prompt out for me to choose smart or normal install, it just install by itself when I click install... first install is to /xbin, but init.d doesn't work, then I install again to /bin, and still same

3. AOSP ROMs like Slim should already have init.d built in...it is impossible that you do not have init.d... I have init.d folder in /etc, but the scripts inside is not execute when phone reboot, as I can't see test.log in /data, apart of this, scripts from Direct Inject also not working....

EDIT 1:

Flash via TE seem to be OK, but still can't see test.log.

EDIT 2:

Tried flash in recovery also can't make init.d support work.... :crying:

Appreciate your feedback.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
How do you know that it is not working? Is there a 00test script in /system/etc/init.d? Permissions set to rwxrwxrwx? Post your contents of install-recovery.sh at pastebin and share it here...my guess is you disabled it after you rebooted into CWM6... There will be a prompt to disable recovery flash, which you should choose no...
[Android Software/Hacking General [Developers Only]] s30ckf:
Because I didn't see test.log in /data.......Ya, there is the 00test script in init.d, with permission set to rwxrwxrwx

Below is the contents from install-recovery.sh:

#!/system/bin/sh

#======== Copyright (C) 2013 Jeffrey Gomez (Exit_Only) =========#

# This program is free software: you can redistribute it and/or modify

# it under the terms of the GNU General Public License as published by

# the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

# This program is distributed in the hope that it will be useful,

# but WITHOUT ANY WARRANTY; without even the implied warranty of

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

# GNU General Public License for more details.

# You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.

#===============================================================#

# init.d support

busybox run-parts /system/etc/init.d/
[Android Software/Hacking General [Developers Only]] Ryuinferno:
What's the permission of install-recovery.sh? I will not attend to things that are clearly not done by my scripts/work...What's the content of 00test? This will be the last support from me...you are using Exit_Only's work...there is already a test script by him...check his thread on how to check the functionality...
[Android Software/Hacking General [Developers Only]] s30ckf:
Permission of install-recovery.sh is rwxr-xr-x

Content of 00test as below:

#!/system/bin/sh

#Init.d Test

busybox mount -o remount,rw -t auto /system

busybox mount -o remount,rw -t auto /data

if [ -e /data/Test.log ]; then

rm /data/Test.log

fi

echo Ryuinferno @ XDA 2012 > /data/Test.log

echo Init.d is working !!! >> /data/Test.log

I really appreciate all your supports given. Right after I flashed Slimbean weekly 6.9 2 days ago (before flashing EO's MOD), I have use your uni-init app to check whether init.d support working or not, and its not working since then.... Please accept my apologies for asking support that not 100% pure from your work.
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
Try to execute install-recovery.sh using scriptmanager (right name?!) and see if test.log appears and other stuff is changed. This way we test the process after the install-recovery file.

The problem could be before that

A question, the rom didn't already had a sysinit in bin?

Btw, same thing? Yes. I know but some roms are picky
[Android Software/Hacking General [Developers Only]] s30ckf:
Hey NAZUnlimited & Ryu,

I double check on the scripts in /etc/init.d, I found that scripts from EO is executed in /data/direct_inject, but I can't see test.log in /data... this is what I miss out previously..... having said that, I think the init.d is supported after the final step (run with script manager).... thanks for both of you for the support...:good:
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
Probably one of the other init.d scripts is deleting the .log files, most devs include a cleaner in init.d scripts
[Android Software/Hacking General [Developers Only]] MrCabana:
I ran this apk to add init.d support to my phone and added a script to /etc/init.d/00tma.

It seems to be working just fine, the problem is: the line I added was to bind mount a folder in sdcard2 and I presume this folder isn't created yet by the time init.d is run.

I don't see any error messages added to the log file, but /mnt/sdcard/Android/data/com.ea.games.nfs13_na is empty after boot is complete.

Where could I put that command to make it run AFTER /mnt/sdcard2 is mounted?

Thank you.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
*Shrugs*... This thread is to give you init.d functionality...Since you have it then the rest depends on you...
[Android Software/Hacking General [Developers Only]] MrCabana:
Hehe, sorry if my previous question was too dumb.

I was wondering if maybe running scripts AFTER the processing of mounting scripts could perhaps be one of init.d functionalities.

But now I can see it isn't.

Thank you.
[Android Software/Hacking General [Developers Only]] AFN:
For test this is tooooooo hard , there is sth easier

Post#30 [Something Special :D ]

For the test :

1.Download attached file and put it in sdcard

2.Flash it into Recovery

3.Navigate to data/ if Test.log is available then you have init.d support if not then you don't have

4.Smash that Thanks button ;)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
What is this for? :confused: There's already one in the first post...
[Android Software/Hacking General [Developers Only]] AFN:
Man aren't you seeing the complex of the test this is 100+ times easier ;)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
==... What do you mean? It does the same... You zip will not be compatible with all devices (why? Update-binary problem...) or else why wouldn't I be doing that ages ago?
[Android Software/Hacking General [Developers Only]] pvinodnayak:
Hi I'm on MF9 complete stock rooted, I followed post no2 using terminal emulator. I can't see Test. Log under /data. All the permissions are correct. I did not find run parts under /system/xbin, I downloaded it from the op and set permissions and rebooted 3 times. No luck. I have installed busy box in normal method.

I even used script manager to run the script. Something is wrong. I'm attaching a pic. Please advice.
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
Try the app version of post 1
[Android Software/Hacking General [Developers Only]] famewolf:
I ran the app in post #1 and it enabled init.d for my device, verified by Test.log.

ICOO D70 Pro II (rk3066 dual core cheap chinese tablet) on Android 4.1.1 Custom rom due to fact author removed some chinese apps and did some minor tweaking/fix's but mostly stock.

I will add "Thanks" once I'm past my current "8 times a day" limit.
[Android Software/Hacking General [Developers Only]] mr.abdolian:
Thank you so much! It worked on my Xsola.

I have been looking for anything like this! Add init.d support to stock roms without Unlocking Bootloader!! It's very coool!!

just a question:"Does it work 100% on Locked Bootloaders just like Unlocked Ones?"
[Android Software/Hacking General [Developers Only]] NAZUnlimited:
this one has a locked bootloader and its working 100%, tweaks and every init.d customization i've added. His method is working flawless
[Android Software/Hacking General [Developers Only]] ReadReadz:
[MENTION=4576707]Ryuinferno[/MENTION]

I installed your apk and complete active !

After reboot, i found init.rc in /data/local/tmp

I try to put test script in system/etc/init.d

#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt

But after reboot, i dont see init.d_log_test.txt in /data/local/tmp/.

Is my phone initd supported ?:(
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Paste your /etc/install-recovery.sh somewhere and let me see...

Is there a Test.log in /data? If not, please refer to the updated self-help guide...

By the way guys, I have updated Term-init and Zip-init now...removed useless code and improved some code logic...corrected the mistakes done when I was inexperienced...;)
[Android Software/Hacking General [Developers Only]] mr.abdolian:
Not working :(

I used Uni-init app and Activated init.d support and then verified and everything was OK and I thought that init.d is Activated but I forgot to check "/data" folder for the "Test.log" file. Then I went to "/data" and I didn't find "Test.log".

Then, I tried 2 other ways (Term-init and Zip-init) but Again I didn't have init.d support.

My device is Xperia sola with locked bootloader, stock Rom and kernel, rooted, deodexed and busybox support.

Can anyone Help me please? If you want I can take a logcat.
[Android Software/Hacking General [Developers Only]] famewolf:
Do we need to update? If so, what are the update procedures? Version I used seems to be running my script fine on bootup.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
You did not read the full self help guide...read on to debug...

http://xdaforums.com/showpost.php?p=32734144&postcount=4

Nope...it's for new users...
[Android Software/Hacking General [Developers Only]] mr.abdolian:
It woorkeed!!

YEAH.......YEAH.........IT WORKED!!:victory::victory: THANKS!:good::good:

Yes I forgot to Read that carefully! I tried all of them but not worked,BUT The last resort WorKeD!!...:p

Now, Can I Uninstall the app (ScriptManager) or not?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
No...you need it for the scripts to run at startup...
[Android Software/Hacking General [Developers Only]] mr.abdolian:
OK, Thanks for your reply...... but if I unlock my bootloader, Is there any way that does it without any app?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
You didn't read the FAQ fully again...read 7 & 9...
[Android Software/Hacking General [Developers Only]] mr.abdolian:
Do you mean Troubleshooting ? I read all of that but there don't mentioned anything about BootLoader...
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Lol... What I meant was if you want the hack to work without script manager, do what step 7&9 says...
[Android Software/Hacking General [Developers Only]] mr.abdolian:
Oh...OK! I got it! thanks....

excuse me one another question: Do I have to run this program every time I want to restart? I think answer is yes because I lost Test.log again!

Does this file appear for one time?

And If I do the step 9, can u help me to do that without app?

[ Thanks for your answers. And excuse me for my many questions and poor English!! ]
[Android Software/Hacking General [Developers Only]] rocketero:
[MENTION=4576707]Ryuinferno[/MENTION], You did a great job at the command line, I used the "term-init.sh" script and it worked as a charm.

thanks .
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Nope...it appears on every boot...no, you just have to set Script Manager to run /etc/install-recovery.sh as root on every boot...