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

[obicom]

Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.

For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.

How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.

But now "Step-by-Step":

Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.

Step-by-Step Instructions:

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

 

[kryddan]

am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.

Thanx for a nice "how-to"

Seems simple and straightforward enough

 

[obicom]

Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)

Now you should find the zip on the end of first post.

 

[SWFlyerUK]

Sorry - how do you gve the 777 file permissions?

 

[Rumball]

Sorry - how do you gve the 777 file permissions?

Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.

 

[SWFlyerUK]

Whoops, my device is in a bootloop lol

 

[obicom]

I hope you are joking ...

@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.

4=read
2=write
1=execute

 

[SWFlyerUK]

I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.

 

[obicom]

What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?

 

[Rumball]

I hope you are joking ...

@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.

4=read
2=write
1=execute

Doh! Thanks

 

[Rumball]

I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.

Not permissions fault. Mine didn't bootloop

 

[condi]

Special thanks to DooMLord for the idea and first implementation.

yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.

 

[obicom]

That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...

with a special thx for Condi ;-)

 

[condi]

That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...

with a special thx for Condi ;-)

hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.

 

[SWFlyerUK]

I changed nothing in the build.prop.

All I did was follow the instructions to your post and change the permissions as said by the chap above.

I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...

 

[obicom]

Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.

I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"

If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.

 

[condi]

I changed nothing in the build.prop.

All I did was follow the instructions to your post and change the permissions as said by the chap above.

I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...

I wrote in many threads about 'rescue-backdoor', why havent you made it?

 

[SWFlyerUK]

I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.

 

[obicom]

That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!

-- Edit --

Rolled the build.prop increment value back

Does it mean now you have the original value or the lower value?

If first case , that was a fault.

 

[condi]

I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.

The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!