android_recovery_motorola_g.../recovery/root/system/bin/runatboot.sh

#!/system/bin/sh

mount /vendor_dlkm
mount /vendor
modprobe -d /vendor/lib/modules /vendor/lib/modules/nova_0flash_mmi.ko
modprobe -d /vendor/lib/modules /vendor/lib/modules/ili9882_mmi.ko
sleep 1
if [ $(cat /sys/class/touchscreen/primary/productinfo) == "NT36672C" ]
then
echo 1 > /sys/class/touchscreen/primary/forcereflash
echo novatek_ts-csot-NT36672C-2302240D-605b-genevn.bin > /sys/class/touchscreen/primary/doreflash
echo "Reflashing firmware..."
echo 0 > /sys/class/touchscreen/primary/forcereflash
fi

is_fastboot=$(getprop init.svc.fastbootd)
if [ "$is_fastboot" != "running" ]; then
echo "Fastboot is running"
fi

mkdir /firmware
SLOT=$(getprop ro.boot.slot_suffix)
mount /dev/block/bootdevice/by-name/modem$SLOT /firmware -O ro
echo "1" > /proc/sys/kernel/firmware_config/force_sysfs_fallback
echo "1" > /sys/kernel/boot_adsp/boot
exit 0
hiphi: recovery/root: Load ADSP firmware * Required for USB to work properly Co-authored-by: Andrew Hexen <SyberHexen@gmail.com> Co-authored-by: Captain Throwback <captainthrowback@hotmail.com> Co-authored-by: nebrassy <nebras30@gmail.com> Signed-off-by: 7Soldier <reg.fm4@gmail.com> 2023-04-24 14:42:28 -04:00			`#!/system/bin/sh`
touchscreen: support ilitek touch panel variants Reworked the script logic to load both variants' touchscreen kernel modules. Only the nova_0flash_mmi.ko module needs a manual load of the firmware as the ili8992_mmi.ko module loads firmware automatically. The script runs a quick check for a known value and then loads firmware accordingly. Running both modules showed no issues. Change-Id: Ib38f3adf802c505eb5aae58441efba4fda0e4f91 2023-09-09 00:26:14 -04:00
eqs -> genevn 2023-09-03 08:36:21 -04:00			`mount /vendor_dlkm`
			`mount /vendor`
			`modprobe -d /vendor/lib/modules /vendor/lib/modules/nova_0flash_mmi.ko`
touchscreen: support ilitek touch panel variants Reworked the script logic to load both variants' touchscreen kernel modules. Only the nova_0flash_mmi.ko module needs a manual load of the firmware as the ili8992_mmi.ko module loads firmware automatically. The script runs a quick check for a known value and then loads firmware accordingly. Running both modules showed no issues. Change-Id: Ib38f3adf802c505eb5aae58441efba4fda0e4f91 2023-09-09 00:26:14 -04:00			`modprobe -d /vendor/lib/modules /vendor/lib/modules/ili9882_mmi.ko`
eqs -> genevn 2023-09-03 08:36:21 -04:00			`sleep 1`
touchscreen: support ilitek touch panel variants Reworked the script logic to load both variants' touchscreen kernel modules. Only the nova_0flash_mmi.ko module needs a manual load of the firmware as the ili8992_mmi.ko module loads firmware automatically. The script runs a quick check for a known value and then loads firmware accordingly. Running both modules showed no issues. Change-Id: Ib38f3adf802c505eb5aae58441efba4fda0e4f91 2023-09-09 00:26:14 -04:00			`if [ $(cat /sys/class/touchscreen/primary/productinfo) == "NT36672C" ]`
			`then`
eqs -> genevn 2023-09-03 08:36:21 -04:00			`echo 1 > /sys/class/touchscreen/primary/forcereflash`
			`echo novatek_ts-csot-NT36672C-2302240D-605b-genevn.bin > /sys/class/touchscreen/primary/doreflash`
touchscreen: support ilitek touch panel variants Reworked the script logic to load both variants' touchscreen kernel modules. Only the nova_0flash_mmi.ko module needs a manual load of the firmware as the ili8992_mmi.ko module loads firmware automatically. The script runs a quick check for a known value and then loads firmware accordingly. Running both modules showed no issues. Change-Id: Ib38f3adf802c505eb5aae58441efba4fda0e4f91 2023-09-09 00:26:14 -04:00			`echo "Reflashing firmware..."`
eqs -> genevn 2023-09-03 08:36:21 -04:00			`echo 0 > /sys/class/touchscreen/primary/forcereflash`
touchscreen: support ilitek touch panel variants Reworked the script logic to load both variants' touchscreen kernel modules. Only the nova_0flash_mmi.ko module needs a manual load of the firmware as the ili8992_mmi.ko module loads firmware automatically. The script runs a quick check for a known value and then loads firmware accordingly. Running both modules showed no issues. Change-Id: Ib38f3adf802c505eb5aae58441efba4fda0e4f91 2023-09-09 00:26:14 -04:00			`fi`
eqs -> genevn 2023-09-03 08:36:21 -04:00
[FIXME] hiphi: recovery/root: Implement proper modules loading * On different versions of ROM can be used different kernel modules, loading prebuilds can cause issues with battery, touchscreen and OTG for some users. * However, in fastbootd mode not possible to load kernel modules from current ROM, so we forced to use prebuilds for it. Of course, its not proper solution, but at least it keep situation in same state, and fixes issues for some users in normal recovery mode. Signed-off-by: 7Soldier <reg.fm4@gmail.com> 2023-06-18 15:18:34 -04:00			`is_fastboot=$(getprop init.svc.fastbootd)`
			`if [ "$is_fastboot" != "running" ]; then`
eqs -> genevn 2023-09-03 08:36:21 -04:00			`echo "Fastboot is running"`
[FIXME] hiphi: recovery/root: Implement proper modules loading * On different versions of ROM can be used different kernel modules, loading prebuilds can cause issues with battery, touchscreen and OTG for some users. * However, in fastbootd mode not possible to load kernel modules from current ROM, so we forced to use prebuilds for it. Of course, its not proper solution, but at least it keep situation in same state, and fixes issues for some users in normal recovery mode. Signed-off-by: 7Soldier <reg.fm4@gmail.com> 2023-06-18 15:18:34 -04:00			`fi`

hiphi: recovery/root: Load ADSP firmware * Required for USB to work properly Co-authored-by: Andrew Hexen <SyberHexen@gmail.com> Co-authored-by: Captain Throwback <captainthrowback@hotmail.com> Co-authored-by: nebrassy <nebras30@gmail.com> Signed-off-by: 7Soldier <reg.fm4@gmail.com> 2023-04-24 14:42:28 -04:00			`mkdir /firmware`
			`SLOT=$(getprop ro.boot.slot_suffix)`
			`mount /dev/block/bootdevice/by-name/modem$SLOT /firmware -O ro`
			`echo "1" > /proc/sys/kernel/firmware_config/force_sysfs_fallback`
			`echo "1" > /sys/kernel/boot_adsp/boot`
			`exit 0`