[Q] Custom Firmware - Running SH scripts on boot - Android Q&A, Help & Troubleshooting

Hey there,
I am around 85% complete on a custom firmware I am developing on the amlogic platform for a new device I am working on.
The base firmware I have used runs sh scripts during boot - and upon shell launch. I have added what sh I want to run into the same directory with the same permissions as existing but mine won't run.
The sh files I need to run either during boot or as soon as boot has completed - simply unpack an tar archive files to a specific location.
Can anyone assist?
Thanks in advance
DA

Related

[Q] replacing ADB daeamon to correct zombie issue in screenCap service

Hi,
I a looking at flashing nexus S (or any other device actually) with a PATCHED version of ADB daemon
[
So I was looking at ADBD location in any .IMG factory files, in order to unpack then pack new IMG file to flash again (System.img I was thinking)
does anyone know the location of ADB DAEMON in IMG files (under /sbin in the device I guess)
Please note : I tried to push ADBD with ADB push being root, but after rebooting, the system just replaced with the OLD one !
Thanks for help

[Q] create initrd with hello world

Hello!
I've got a gt-i9100 (glalaxy SII) with android 4.0.4( No CWM, no Root)
I want to make a recovery image, that when it start running a simple HelloWorld application (printf("Hello World\n") on the screen for example).
1) Samsung Stock recovery image running init(which initializes fs, mount partitions. etc.), then running recovery binary file, which doesn't contains exec (so, I can't add "exec /sbin/HelloWorld" in recovery.rc file).
Is there a way to run the application, modifying rc files in initrd? (I can compile stock kernel from sources, pack/unpack an initrd)
2) I make my own initrd, which contains busybox+udev+some initial scripts. But after flash, phone is going into reboot loop
Maybe someone managed to create "own little" initrd?
3) I think than I can use update.zip file for my goal. So, I downloaded an example of update.zip and make my own update.zip file with HelloWorld application. I've install ZipSigner and "sign" my update.zip with all keys. But for every key stock recovery says that update.zip is not verified.
I don't know how to work with zipsigner and update.zip or ZipSigner doesn't support 4.0.4 android?
Maybe someone was trying to do the same work?
any ideas?
Thanks!

[Q] Extract Compressed File to SD Card Director on First Boot

Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting

Run sh-script on boot

I have rooted smartphone Lenovo A Plus (A1010A20) with Android 5.1. I want to schedule some script to be execute on boot. I did not find any "init.d" directory, so I added the script call to "/system/etc/mkshrc" file. But in this case the script executes only after I enter the terminal as a super user. So I installed Busybox and tried to use cron. But I can not make crond service run automatically. I even create folder "/system/etc/init.d/" and put file with script to run crond. But it does not working.
How to make crond service run automatically on Android?
yurybx said:
I have rooted smartphone Lenovo A Plus (A1010A20) with Android 5.1. I want to schedule some script to be execute on boot. I did not find any "init.d" directory, so I added the script call to "/system/etc/mkshrc" file. But in this case the script executes only after I enter the terminal as a super user. So I installed Busybox and tried to use cron. But I can not make crond service run automatically. I even create folder "/system/etc/init.d/" and put file with script to run crond. But it does not working.
How to make crond service run automatically on Android?
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/an...ript-zip-init-d-enabler-stock-kernel-t3347724

How to add library to /system/bin without editing system.img ?

Basically, in the rom I am using the dev did not include for the some reason a file called "logd" always present in /system/bin, this file is responsible for making logcat work. I already extracted the file from my original rom but every time I copy it to /system/bin and then I reboot it gets deleted and nothing changes. This is very frustrating because logcat is very important for me.
So how can I move the file to my /system/bin without reflashing a modified system image which I don't want to take the risk of nor I have time to do so ? Even a workaround won't matter.
device: xiaomi note 10s
rom: LiteE (android 11)
additional info: device rooted with magisk v23 and xposed framework installed
Please tell me if you think I should i include any other info.

Categories

Resources