doggedly 0 Posted September 15, 2021 In Asus Tinker board version one it was easy. It was enough to put the init.asus.sh file in the /system/etc/ directory and grant it permissions. Everything in this file was executed on boot (after the tinkerboard bootlog). Unfortunately, it doesn't work in Tinkerboard 2. There is a solution after installing the Magisk package. Daily Job Scheduler mod needs to be added. This is a pretty cool solution that looks like a Linux crontab. However, I would prefer a more system-level solution, ignoring these types of mods. Is there any autorun method similar to init.asus.sh / rc.local etc ?? Share this post Link to post Share on other sites
tooz 54 Posted September 16, 2021 hello @doggedly, it should be the same as the first gen (tinker baord/ tinker board s). may i know the steps of how you run the executable on boot? Share this post Link to post Share on other sites
doggedly 0 Posted September 20, 2021 it doesn't work i did a simple test. I created init.asus.sh in /system/etc/ (same as in generation 1) to do something simple: #!/system/bin/sh touch /sdcard/test.txt The file has chmod + x (see the attachment). Nothing happens, the file has not been created. Just like my scripts don't run, they run and run on startup in generation one. What they do doesn't matter. In my opinion, the asus.init.sh autostart routine does not work. So I repeat the question how to do autorun without the Magisk mod. Share this post Link to post Share on other sites
tooz 54 Posted September 23, 2021 hello @doggedly, the reason why the scripts weren't excuted is because it requires Init-launched services in Android 10: Writing SELinux Policy | Android Open Source Project you will have to build your image in order to have SELinux Access: TinkerBoard2-Android/manifest (github.com) Share this post Link to post Share on other sites