[MOD] Enable init.d scripts support on stock kernel

Search This thread
By:
Advanced…
iridaki

iridaki

Retired Forum Moderator
Feb 21, 2007
4,532
5,190
37
Edinburgh, Scotland
Hello!

This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him :D) and his thread in the X10 section.

I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.

So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.

Requirements:

1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.

Instructions:

1. Download the zip and place it in a folder in your SD card.

2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code: 
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code: 
# init.d support
busybox run-parts /system/etc/init.d/

In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***

3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.

4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".

5. Now you can use your favorite init.d scripts on stock kernel! :)

If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.


*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.


Let me know if it worked for you! :)

attachment.php
attachment.php
attachment.php
 
  • Like
Reactions: zalmen hatotach, btiu, PankajKumar12 and 72 others
sgj1

sgj1

Senior Member
May 10, 2010
100
16
spain
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
 
aimcr7

aimcr7

Senior Member
Jun 14, 2010
2,001
889
Yogyakarta
sgj1 said:
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
Click to expand...
Click to collapse

This is working great on mine mate, just try it again maybe you left something, i tested it with init.d scripts from SE Tweaked and it works. :)

Sent from my MT15i using XDA App
 
O

onlavu

Senior Member
Jan 21, 2011
100
16
Opava
www.facebook.com
Confirmed, working:)

I tried this mod and it seems to be working. Before its application, Supercharger tells me that he cannot reach init.d or something like that. But with this mod it can use init.d without any problems, no more warning. So it is working. Thank you
 
Last edited:
Pandemic

Pandemic

Senior Member
Aug 30, 2010
24,259
23,234
Meppel
talk.sonymobile.com
Samsung Galaxy Tab A series
Xperia XZ2
iridaki said:
Hello!

This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him :D) and his thread in the X10 section.

I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.

So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.

Requirements:

1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.

Instructions:

1. Download the zip and place it in a folder in your SD card.

2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code: 
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code: 
# init.d support
busybox run-parts /system/etc/init.d/

In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***

3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.

4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".

5. Now you can use your favorite init.d scripts on stock kernel! :)

If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.


*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.


Let me know if it worked for you! :)

attachment.php
attachment.php
attachment.php
Click to expand...
Click to collapse

this is working for neo v?
 
Tenacious

Tenacious

Senior Member
Oct 2, 2011
957
541
With rootxplorer go to system mount read/write (see screenshot)
59ac7e51-70b8-a63e.jpg
long press build.prop open in text editor find vm heapsize change it to 48 save the change and reboot. Make buckup of build.prop just in case.

Taptalked
 
You must log in or register to reply here.

Similar threads

jerpelea
  • Poll
{NEO/NEO V}[DEVELOPMENT] - CM10 - FreeXperia Project
Replies
3K
Views
738K
D
datumdatzgr
N
[KERNEL][NEO] The Alliance kernel mod for ICS (V1.5) and CM9 (128)
Replies
578
Views
309K
T
teasolves
N
[KERNEL][NEO] NightElf Kernel mod for FXP Rom/AchotjanRom/MIUI Rom/Stock (042, 062)
Replies
603
Views
257K
B
Butcher696
kormatoes
  • Locked
  • Poll
mods please lock for me XPERIA/NEO/Rom&Kernel[4.1.2]-V8FINAL/UPLOAD OF AC 8-11
Replies
4K
Views
441K
poyensa
poyensa
jerpelea
  • Poll
{NEO/NEO V}[DEVELOPMENT] - CM9.1 - FreeXperia Project
Replies
3K
Views
609K
herumukti99
herumukti99

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 75
    iridaki
    iridaki
    Hello!

    This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him :D) and his thread in the X10 section.

    I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
    However, I use lots of init.d scripts (my favorite one being SuperCharger)
    and I just don't want to lose this feature when I'm on stock.

    So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.

    Requirements:

    1. Stock Kernel
    2. Root
    3. Busybox
    4. CMW Recovery for Stock Kernel by nAa.
    5. Root Explorer or any other similar app.

    Instructions:

    1. Download the zip and place it in a folder in your SD card.

    2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
    a. If the file install-recovery.sh is not there, then press Menu and create a New File.
    Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
    Paste this text in it:
    Code: 
    #!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
    Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
    OR
    b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
    Code: 
    # init.d support
busybox run-parts /system/etc/init.d/

    In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***

    3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.

    4. Reboot your phone and with Root Explorer go to /data/local/tmp.
    There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".

    5. Now you can use your favorite init.d scripts on stock kernel! :)

    If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.


    *** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.


    Let me know if it worked for you! :)

    attachment.php
    attachment.php
    attachment.php
    View
    1
    Tenacious
    Tenacious
    Pandemic said:
    i cant edit it when i open as text:S
    Click to expand...
    Click to collapse

    Not open as text, scroll down and open in text editor.

    Taptalked
    View
    1
    Madfysh
    Madfysh
    Pandemic said:
    and what are your permissions ?
    Click to expand...
    Click to collapse
    What permissions? Of the build.prop file? Just long press on build.prop and select permissions. Or you also don't have that option? :)
    Anw, mine are RW-R-R.
    View
    1
    Tenacious
    Tenacious
    I use rootxplorer 2.19. Ok copy your build.prop to SD card transfer it to PC use text editor of your choice to edit build.prop after you finish putt it back to SD card now use rootexplorer and copy it to system set permission to rw-r-r and reboot. That is it.

    Taptalked
    View
    1
    LenAsh
    LenAsh
    For what reason? This phone has rather limited RAM to start with and anything over 32 or 36M heap is probably overkill. With a larger heap size, there is more v.memory for programs and the garbage collector "may" run more efficiently. Therefore, it is possible to get better performance by setting a larger VM heap size.

    However, if you set it too high you could run out of free memory which can trigger swapping which will seriously degrade performance. Take care... and remember that if the manufacturer could gain "free" performance simply by changing this, then they would have done.
    View

New posts