yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] jwyder:
I ran this from the zip-init.zip using CWM on my VZN Galaxy S3 SCH-I535 rooted stock rom

Ran successfully but no test log under /data

Verified init.d is in /system/etc/ as it was not there before.

Wondering how to test if this worked or not.

Thanks for all your hard work on this!!
[Android Software/Hacking General [Developers Only]] subnoize soulja:
Ooooo cool cause I have Acer iconia a500 rooted with the v6 supercharger already flashed and I tried flashing pimp my ROM before and it went through the whole process like it actually worked but when I rebooted there was no difference so it didn't stick but I'll give this a go and see what happens afterwards....Thanks for the reply +1
[Android Software/Hacking General [Developers Only]] gjnicholson:
Got it working on my Motorola Xoom 2 running stock ICS 4.0.4 Asia Retail.

There was an error in my install-recovery.sh which I discovered when I tried to run it in terminal emulator.

Thanks for this, you have made my day!:D:good:
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Hmmm...did you install busybox using the recommended method before this? If not, please do so...and if it still doesn't work, try the run-parts fix...it is all in my FAQ section...:)...to know whether is it working or not, just check for Test.log...

No prob...:)
[Android Software/Hacking General [Developers Only]] x_one:
AWESOME!

It's working on my Xperia Neo V FW Stock 4.0.4 with locked bootloader! :D

Thank you!
[Android Software/Hacking General [Developers Only]] psenseny:
CWM Flashable

I followed all instructions and FAQ.

I used the CWM flashable Zip. Everything seems to flash OK however after flash when I select to reboot the device, CWM recovery asks if I would like to disable the Rom potentially flashing a different custom recovery.

This only happens after flashing the zip as I guess it assumes that this flash will re-flash a different custom recovery.

If I select to disable the ROM overwriing the recovery, it does not look like the flash is completely sucessful and I have no Init.d support.

I assume I must not disable the "ROM from re-flashing a recovery"?

Using ATT Galaxy S3, stock ROM/kernel with CWM 6.0.1.2
[Android Software/Hacking General [Developers Only]] Ryuinferno:
:confused:...what the?! My zip will not change anything to your recovery...yours is the first case I met...hmm...maybe you should try term-init, much simpler and works for many...:)
[Android Software/Hacking General [Developers Only]] Pandemic:
work this on Jelly sandwich 7.1 by maxio on locked bl?

because he have already the new init.d tweaks, so thats why i asking ;)
[Android Software/Hacking General [Developers Only]] Daniel D.:
Strange... This script is nothing new compared to Doomlord's one. He developed the same effect long time ago - his script has problems with Link2SD, too. Both of them will destroy each other, you've to edit at least one file manually (install-recovery.sh) after installing Link2SD.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
That's the difference...my script does not intefere install-recovery.sh...it will only add lines and delete recurring lines...I didn't know about similar scripts or anything before this...the idea just popped out and so I made this...:)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
If init.d is already supported, you don't have to use this anymore...:)
[Android Software/Hacking General [Developers Only]] EdgaBimbam:
omg it is working, thx u vm :)

Btw im on galaxy note 2 stock odexed rooted firmware

Maybe i can add this tutorial at galaxy note 2 section with all credits to you?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Great to know that...:thumbup:...you can just quote my post in your thread over there...and add a link back here...you can add your comments later on if you like...but please don't mirror my work...:)
[Android Software/Hacking General [Developers Only]] EdgaBimbam:
lol ofcourse i wont mirror your work ;D i will pm you link of my created thread, to look if it is ok.
[Android Software/Hacking General [Developers Only]] Daniel D.:
Thank you for the answer!

Hmm, what if I integrate it into a ROM beside Link2SD? If I start Link2SD for the first time, it'll create the mount script(s) which destroy the installation of init.d support. Is there another way to get around this problem? Do I misunderstood anything?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Hmm...if so, you should run Link2SD first before using this script...after the install-recovery.sh is created by Link2SD, then run this script to modify the install-recovery.sh...you will only need my script once to enable permanent init.d support (provided you don't modify system files of course)...;)
[Android Software/Hacking General [Developers Only]] Daniel D.:
Ok, so i assumed right that there is no other way with a stock kernel to get both things working at the same time. Grrr... ;)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Nonono...you got me wrong...it will ADD lines to the install-recovery.sh by Link2SD..so if everything goes well, both will work at the same time...:)
[Android Software/Hacking General [Developers Only]] psenseny:
I took your suggestion and ran term-init. It was able to add init.d support after reboot, however since I ran this, I have lost CWM recovery and it is now replaced by Stock recovery.

I am no expert, but this seems to playing with the "override" on the stock ATT rom in Galaxy S3 where it disables the rom from re-flashing stock recovery.

I will reflash CWM recovery again, and see if I am still abel to run init.d scripts. However I have to wait until I am home since my company's filewall blocks downloading CWM from Rom Manager.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Hmm...so far you are the first person I know to face this problem...did you install the busybox recommended by me using the normal installation method? That is to ensure my script for adding lines instead of replacing them works fully...I guess that your CWM is dependent on install-recovery.sh...so my suggestion is to add the necessary lines in install-recovery.sh after you flash CWM:

Add this line after the last line in install-recovery.sh

run-parts /system/etc/init.d/

and leave an empty line after that...my hypothesis is that since you downloaded CWM from ROM Manager, it is not embedded in your kernel, so install-recovery.sh is required for it...:)
[Android Software/Hacking General [Developers Only]] Daniel D.:
I know, but Link2SD will overwrite everything! :mad: This is the problem with integrating the app into a ROM. I'll try to create all the files during installation, but I didn't succeed.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Hmm...means Link2SD actually rewrites install-recovery.sh after every reboot? Strange...it didn't happen before this...why not integrate other scripts such as DTa2sd etc into your ROM? To me, they are able to move more stuff when compared to Link2SD...:)...since now you have init.d support, using those custom scripts should not be a problem anymore...;)
[Android Software/Hacking General [Developers Only]] psenseny:
I installed busybox via Stericson's app as you instructed - the applets are there, etc. I will give this a try later and report back. THANKS FOR YOUR HELP!
[Android Software/Hacking General [Developers Only]] Daniel D.:
No, it overwrites only once after the first start, but this is once too much ;).
[Android Software/Hacking General [Developers Only]] Ryuinferno:
:confused:...hmm...then that should not be an issue...just launch Link2SD, reboot, then use my script...that's all...:)
[Android Software/Hacking General [Developers Only]] airbusecam:
re

i have a stock rom rooted note 2 and saw this thread in the note 2 forum thanks to the post there, once you have init.d support is then possible to run an app2sd script such as the dev made for the gs3 in the thread listed below.

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

if so what should i add, as this is my top mod for this phone, due to lack of install space.

cheers pj
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Then try to apply scripts such as DTa2sd or Amarulzz...both of them will work provided you have init.d support...:)
[Android Software/Hacking General [Developers Only]] Pandemic:
Alright thank you and thanks also for the reply, this is a good job btw:D
[Android Software/Hacking General [Developers Only]] Daniel D.:
Yes, but there is the custom ROM installation process. I'm trying to add Link2SD preconfigured and hope that I don't have to re-start and run another script.
[Android Software/Hacking General [Developers Only]] Vilo76:
Very convenient, and works on my Sola stock rooted ICS.

Thanks ;)
[Android Software/Hacking General [Developers Only]] spida_singh:
Thanks!

Worked great on my Xperia T. Stock kernel.
[Android Software/Hacking General [Developers Only]] :
Great stuff mate!! Time to test this on my Kindle Fire HD!
[Android Software/Hacking General [Developers Only]] yunolawliet:
not working

galaxy pocket.. still no init.d support :(
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Please describe your problem...read the troubleshooting section?:)
[Android Software/Hacking General [Developers Only]] ahmedelhofy:
Tried the terminal Emulator method on my Galaxy W with Stoch Rom

and it worked perfectly

Thanks Dude

you are awesome
[Android Software/Hacking General [Developers Only]] simplelife:
Model T889 work like charm. Thanks
[Android Software/Hacking General [Developers Only]] hiarc:
Just tried doing this on a Nexus 7 using RasBeanJelly and have not been able to get it to work. Prior to running the script I installed busybox using the normal installation through Stericson's app. I used the term-init.sh script via terminal (screenie is attached). After rebooting twice the log file did not appear. At first I found out that run-parts did not install in /system/xbin, so I used the one in the troubleshooting section; one reboot later and the log file still is not appearing. I went through all the troubleshooting steps again and still cannot get it to work. However, when I executed install-recovery.sh on its own it executed flawlessly. I do not know much about how the install-recovery.sh is executed but could it be that it does not or it executes differently on the Nexus 7? The thing is, the Nexus 7 is basically a Galaxy Nexus with a bigger screen so it should not matter since they both run almost the same, no? I did not have to use this on my GNex because Franco uses his own ramdisk on his kernels for the GNex so they run off the bat. Any other troubleshooting suggestions?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Ok...good effort in describing your problem...:)...you said run-parts was not installed right? Did you set the correct permissions and ownership for run-parts? And I can assume all the other files are present with correct permissions right?

P.s. Nexus 7 may not be the same as Gnex...every Android device have their differences in some parts...;)
[Android Software/Hacking General [Developers Only]] yunolawliet:
Done everything. By the way in my init.rc its just

run-parts not busybox run-parts.

nothing would happen even if I change it.

Even I cooked a custom ROM in kitchen with run-parts init.d supports,

still nothing.

even the ROMs that claim to have init.d supports,

still nothing.

GALAXY POCKET is KILLING me :)

HAHAHA. I should have got GALAXY Y if I want a low end small/handy phone!
[Android Software/Hacking General [Developers Only]] Camil0x:
Thanks !!!! I tried different methods but it is the only thing that worked for me. :victory:

My device is a Sony Ericsson Live with Walkman with stock firmware ics.587 and stock kernel with locked bootloader.
[Android Software/Hacking General [Developers Only]] hiarc:
Yes, after I wrote that I went into recovery to wipe /system partition, and I just re-flashed RasBean. I did a fresh normal install of BusyBox using Stericson's app, and then continued with running the term-init.sh off the terminal window. I found out that the normal installation does indeed install run-parts in /system/xbin. The problem might have been that I had already ran smart install in the prior flash of RasBean. Afterwards I ran through and checked all permissions and everything was right. My guess is something else needs to be done for it to work on the N7. I'll see if I can dig up something.
[Android Software/Hacking General [Developers Only]] deveshmanish:
Works on Motorola atrix2..

Thanks!!!!
[Android Software/Hacking General [Developers Only]] SammaelAkuma:
Haven't tried it, but looks extremely useful. Will keep it bookmarked incase anyone ever makes a new kernel for the SK4G that doesn't include init.d support.
[Android Software/Hacking General [Developers Only]] NEXUSBOY:
it worked on my device>htc explorer

thank you....:good:
[Android Software/Hacking General [Developers Only]] superman0509:
Can anybody help???

Ive tried this process many many times... several factory resets to try again and I can not get it to work... please help... my phone is a Raze Maxx xt912 6.16.215, 3.0.8 kernel version...
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Please describe what you did and attach a screenshot if possible...:)...factory resets won't do anything to help because this modifies the system directory, not data (factory reset clears data)...
[Android Software/Hacking General [Developers Only]] JediDru:
Using this on my Galaxy Nexus. Very impressive. Thank you very much.

Nexus Primed
[Android Software/Hacking General [Developers Only]] PANCHOMATASANO:
Work fine!!!

My device is TITAN 7010b

Rk2918

I will lead more people to your great work!!!

Thanks very much!!!!

Enviado desde mi 720F usando Tapatalk
[Android Software/Hacking General [Developers Only]] Ryuinferno:
No prob...just hit the thanks button...;)
[Android Software/Hacking General [Developers Only]] oldretiredman:
oldretiredman

:):):)

Thanks for writing this! Used term-init.sh on a ZTE Z990 Avail and it worked perfectly.:)
[Android Software/Hacking General [Developers Only]] janmae:
Samsung Galaxy Mini..stock XWKTN..

success in 1st attempt by 1st method... ;)
[Android Software/Hacking General [Developers Only]] SXUsr:
Worked a treat on stock 587 Xperia Kernel, and I just used Script Manager to run it.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Yeah...using script manager is another option...;)
[Android Software/Hacking General [Developers Only]] wale07online:
help

i mistakenly install busybox using d "smart install". what can i do to correct this please????
[Android Software/Hacking General [Developers Only]] wale07online:
i've done it!

thanks so much! you're a genius!
[Android Software/Hacking General [Developers Only]] CiscoX:
Run busybox and this time select normal install :)
[Android Software/Hacking General [Developers Only]] morrisx:
5830i does not work

Hi

I have a galaxy ace 5830i

with stock ROM

Here are the parameters of the ROM:

version of droid: 2.3.6 (it is a normal stock)

Baseband version S5830iXXLA2

Kernel: stock

Build number: GINGERBREAD.XXLA4

A few weeks ago i used your first method succesfully, but that time my kernel was flashed with a custom kernel (Rafael Baugis kernel).

All other parameters was the same.

Now (with stock kernel) does not works any of the methods, neither, with terminal, nor with zip).

Test.log doesn't appears in \data

I does not got any error status... With both of the methods it seems that everything is ok, but it doesn't work.

Can you help me?
[Android Software/Hacking General [Developers Only]] bongbongcong:
How do i know, if i have already init.d on my custom ROM?

:)Hi, excuse me. I have Note 2 international with custom ROM. My qustion is how can i check whether i currently(already) have init.d support or not in case i don't know/are not sure. Thank you very much, appreciate. :victory:
[Android Software/Hacking General [Developers Only]] CiscoX:
Hi.

You can try and see if you have init.d folder under ./system/etc/init.d (you need a root browser).

If you have init.d folder then i'm sure you have init.d support. Some custom Rom's add init.d support if not i'm sure Term-init & Zip-init would do the tricks :)
[Android Software/Hacking General [Developers Only]] SammaelAkuma:
Used this on SK4G's KJ2 DEODEXED ROOT rom with stock kernel. Works absolutely perfectly.
[Android Software/Hacking General [Developers Only]] bongbongcong:
Thanks a alot

:victory::victory::victory:Thank you very much for your answer/information.:good::good::good:
[Android Software/Hacking General [Developers Only]] PIRATA!:
Where do I get BusyBox and Run-Parts??

Play store or where???

In the troubleshooting I read that if I download the Stericson installer, must I select Normal Installation Method...right??

..but in what? Running Term-init.d.sh or installing his BusyBox??

Thank you
[Android Software/Hacking General [Developers Only]] CiscoX:
Hi.

Yes download BusyBox if you don't have it installed yet. And run "Normal Install" from BusyBox. The run-parts are included with BusyBox. After that you can run Term-init.d.sh

:)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Ok...here's a quick fix...get script manager from play store, then navigate to /etc/install-recovery.sh...select it and run as root and at boot (select the skull icon and the gear icon)...then reboot your phone...should do you fine...:)

The Init.d folder can be placed there but not necessarily it's working...I will include a test script soon but for the time being, googling for a script that tests init.d will be a better option...;)

Lol...when you download the installer from play store, you will get busybox and run-parts after selecting normal installation in the installer...:)
[Android Software/Hacking General [Developers Only]] CiscoX:
Hi. The term-init script have a test script that should run perfectly if everything are correct.

Test.log should be inside ./data/ if it run's ok :)
[Android Software/Hacking General [Developers Only]] morrisx:
Thanks for your answer. I made all you wrote, but i still can not find the file: test.log. Should i type once more the command in terminal?

By the way, i have init.d folder, just the log file is missing. Originally there wasn't this folder.
[Android Software/Hacking General [Developers Only]] CiscoX:
Hi.

Make sure that you have root access (install Superuser or SuperSU) and then installed BusyBox from the Play Store, and then start BusyBox and run "Normal Install" and after that run the term-init.d.sh file again... Then restart your phone.. and see if you have the Test.log inside ./data/
[Android Software/Hacking General [Developers Only]] morrisx:
Hi

Yes, the phone is rooted, su is present, busybox is installed (with normal install), i run the .sh file again, and nothing happened. The logfile is still not present. And i don't know, that init.d support is working, or not. As i wrote the folder is there. Does anybody know a method, how can i test it somehow else?
[Android Software/Hacking General [Developers Only]] PIRATA!:
Ok...so you both say to download the Play store version right?? Those linked in first post from Stericson are from there right??

Sent from my GT-i9300 using my XDA app
[Android Software/Hacking General [Developers Only]] CiscoX:
Hi.

Yes the link on first post for BusyBox are correct :)

https://play.google.com/store/apps/details?id=stericson.busybox
[Android Software/Hacking General [Developers Only]] morrisx:
It's working!!! First time i selected the icons you wrote, there was a popup message in script manager, what i ignored. That was the failure. I had to download SMExternalSD... after installation, i rrbooted, and there is the log file.

Thanks a lot!
[Android Software/Hacking General [Developers Only]] cegrade:
I am using 2.3.6 Galaxy GIO rooted

I tried the emulator method and went over troubleshooting and it doesn't work unluckily

I install the busybox here, and it said I have already installed(in root browser), and it reboot automatically after re installing(not sure if it is installed again). I checked that run parts is installed

Then, I tried CWM method

I face the status 0 error. And how to extract that from my recovery? I use this recovery. I just find a .img file inside and don't know how to extract

http://xdaforums.com/showpost.php?p=16980117&postcount=559
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Ok...here's a quick fix...run term-init and get script manager from play store, then navigate to /etc/install-recovery.sh...select it and run as root and at boot (select the skull icon and the gear icon)...then reboot your phone...should do you fine...:)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Thanks but that is no typo...it is working...and all phones require sdcards right (no matter internal or external), if not where will they download this script to? :p ...I have recoded my script and it will check for necessary parts automatically now...thanks anyway...;)
[Android Software/Hacking General [Developers Only]] Ryuinferno:
v2 for term-init is out...it has better functionality...check it out guys...by the way, I added a file to test whether you have init.d support before going anything...;)
[Android Software/Hacking General [Developers Only]] PIRATA!:
How to see inside .img files!!;)

http://xdaforums.com/showthread.php?t=1667081
[Android Software/Hacking General [Developers Only]] iamareebjamal:
Links not working

Please fix them
[Android Software/Hacking General [Developers Only]] Ryuinferno:
It's working now...just now the servers had an error...but it's fixed now...:)
[Android Software/Hacking General [Developers Only]] bpushpak:
Just perfect :) :victory:
[Android Software/Hacking General [Developers Only]] lelex45:
Finally It works now :good:
[Android Software/Hacking General [Developers Only]] eswawan:
Oh man, thankyou so much, you bring miracle to my WT19i stock kernel :thumbup:
[Android Software/Hacking General [Developers Only]] endre_dude:
Would this work on my Acer s500 which only has a "partial root", meaning that i have a (stock) secure kernel, and can't flash a custom one (can only boot it via fastboot), because the bootloader is locked ? I guess not, as not booting the insecure kernel anymore, upon restart..the init.d script would not have acces to my system partition anymore, right ?
[Android Software/Hacking General [Developers Only]] Ryuinferno:
It doesn't matter what kernel you have...as long as you have proper superuser access...:)
[Android Software/Hacking General [Developers Only]] rickryu:
ok thaks for this post...

i was using init.d before know its work or not for my hisense phone, and checking my data, there is no log text, then use the instruction above,

now i have the log text in data, so init.d working now... :D
[Android Software/Hacking General [Developers Only]] passlogin:
May I request that 00test write only once by default? Flash drives have a limited number of writes, and although this is a minimal write, it's not really necessary to perform every boot.
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Lol...it is there for debugging...I depend on it a lot as I need to see when the scripts are excecuted...but if you like, just remove 00test from /etc/init.d folder after you confirm that it is working...and remove /data/Test.log too...:)
[Android Software/Hacking General [Developers Only]] csantarcangelo:
Worked

Worked fine. Nexus 7, Stock, Unlocked/Rooted, 4.2.1.

Ran via terminal emulator in ROM Toolbox Pro.
[Android Software/Hacking General [Developers Only]] shoutokuyaki:
I can't run in script manager:(
[Android Software/Hacking General [Developers Only]] Ryuinferno:
Two possible causes: You did not install busybox or a bad download...but since the size is so small, most likely it's the first reason...:)

By the way, try running it using terminal emulator...and remember to place it at the root of sdcard...