[HOW_TO] get 'init.d' Support on Tablet S

[SWFlyerUK]

I've changed the build.prop value before and rebooted with no issues.

 

[kryddan]

rescue-guide

Maybe I'm jumping the gun here, but perhaps one of you gents (obicom and/or condi) could post a "rescue-guide" in dev for us less fortunate in the knowledge appartment when it comes to Android/Linux

Then maybe we can eliminate some of the casualties of our tablets with "bricked" (boot-loops).

I have read most of the post here in development-section, but I am still not 100% sure of how to go about with this "rescue-part".

just my two cents

my apologies if I'm out of line here.

 

[obicom]

You are right and I agree...

I did it here in our German Community ->
http://www.android-hilfe.de/root-ha...ck-protection-bitte-vor-dem-rooten-lesen.html

and Condi describes it here on xda ->
http://forum.xda-developers.com/showpost.php?p=22400765&postcount=20

Maybe we can create a special thread who describes it more clear.

 

[kryddan]

unfortunatlly I'm not that good with german and google-translate/yahoo bablefish isn't really that good translating, if you know what I mean hehe.

condi's guide is nice, but a bit short and missing a lot of newbie-steps.

I know many more would love to see a nice guide like the one you did for the init.d
It would save many happy tablet-s owners a lot of aggravation and hassle

Looking forward to a neat guide.

I'm not that green when it comes to Linux, but that is mostly on computers. They I can manage when they f**k's with me. They usually don't give me boot-loops or bricks

 

[rimsilva]

Why?

1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'


Now finished .... it should work !

After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.

Have fun with the new 'init.d' support and apologize for my weak English !!

Special thanks to DooMLord for the idea and first implementation.

Source: http://forum.xda-developers.com/show....php?t=1431134

I have all the steps indicated here, but I don't know how to "now you can put there your own scripts under 'init.d'"

Can someone help?

Thanks

 

[obicom]

What kind of script do you want to autostart?
Create a new script file or change the '99test file' to your requirements.

For example:
create a file into '/system/etc/init.d/' with the name '10myfirstscript'
put some stuff inside like:

#!/system/bin/sh
sleep 75
mount -o bind /mnt/sdcard2/Music /mnt/sdcard/Music

 

[rimsilva]

What kind of script do you want to autostart?
Create a new script file or change the '99test file' to your requirements.

For example:
create a file into '/system/etc/init.d/' with the name '10myfirstscript'
put some stuff inside like:

Thank you obicom for the answer!

This was what was missing... What I want to do is have access to a folder Music in sdcard2.

I've write in the 99test file the same information that you suggested, but In google music I only see files that are inside sdcard\music, not in sdcard2.

If I want to have access to videos and photo, I need to add a new line in file "99test"? As you suggest for music?

 

[sengeddy]

how to write script for a game,e.g mount -o bind /mnt/sdcard2/...?? thx

 

[Tikki Pon]

The AIO tool have the option to enable the init.d support,not? Or what is the difference ?

Sent from my Sony Tablet S using xda app-developers app