[MOD][SHARE][SCRIPT]Enable Init.D On Stock Kernel - Galaxy Y GT-S5360 Themes and Apps

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
v1.0
init.d support through an app!!!​
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.
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"...
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
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:
Download:
If you have already read all the instructions and understand them, then click here to download:
Uni-init v1.0.apk
Original Source
Credits: Ryuinferno​

---

nice !!! , fb later :thumbsup: :beer:

---

frooztreited said:
nice !!! , fb later :thumbsup: :beer:
Click to expand...
Click to collapse
nice,,,ill bm it.. :highfive::good::good:

---

why need app, if we have custom kernel?
no offence btw nice....

---

Reynaldi said:
why need app, if we have custom kernel?
no offence btw nice....
Click to expand...
Click to collapse
some people prefer stock sometimes for its stability
=========================================================================
For the OP, atleast make credits to original developer bigger? since u cant provide any updates to this app, can anyone consider this development? or app share?

---

ronnieryan said:
some people prefer stock sometimes for its stability
=========================================================================
For the OP, atleast make credits to original developer bigger? since u cant provide any updates to this app, can anyone consider this development? or app share?
Click to expand...
Click to collapse
app share.. make it move to proper section.. haha.. joke!
for the OP.. tq!
just found this days ago.. when i want enable init.d for my frend ace duos.. but no luck then use custom kernel..
i prefer stock kernel due to its stability.. since this app cant support his kernel thats y im using custom one..
btw.. did u try and did it work with our stock kernel? i meant did Test.log present in /data folder?
sent from my GT-S5360 via WeChat

---

init.d folder not showing on system/etc/ where find him ?
and when i press activate button then check for succesfully app say init.d not support why ?

---

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
Click to expand...
Click to collapse
as stated by OP, in order to make this trick work the kernel must support install-recovery.sh script. too bad that SGY is not one of them. a simple test will prove it. you can make a script in init.d contain.
Code:
#/system/bin/sh
echo "kucing meong" > /data/kucing_meong.txt
if the trick really work. you'll find kucing_meong.txt in /data. in the past there are a lot of script and tweak claimed to be able add init.d support in any stock kernel but none of them work since samsung have disabled all the possibilities to add init.d support for SGY. the only way to add init.d support is by install a custom kernel with modified init.rc script.

---

kurotsugi said:
as stated by OP, in order to make this trick work the kernel must support install-recovery.sh script. too bad that SGY is not one of them. a simple test will prove it. you can make a script in init.d contain.
Code:
#/system/bin/sh
echo "kucing meong" > /data/kucing_meong.txt
if the trick really work. you'll find kucing_meong.txt in /data. in the past there are a lot of script and tweak claimed to be able add init.d support in any stock kernel but none of them work since samsung have disabled all the possibilities to add init.d support for SGY. the only way to add init.d support is by install a custom kernel with modified init.rc script.
Click to expand...
Click to collapse
in short, this app share is useless

---

Yeah and no development just an app
"Hate Me Till You Can"

---

Don't post like app share... because the original thread was in development section...
Sent from my Nexus 4 Using Tapatalk 2 Xparent Blue

---

Lets state the obvious ok,
at first it was in development section since the creator and developer of the app was the thread starter, and sharing that app to SGY section doesnt mean you developed it and placed in development section?
BTW, what makes it different is that a developer can post in development section because he can, develop,update, fix and whatever it is that he sees fine, but a sharer like you cannot

---

mod not working for our sgy