yochananmarqos
Inactive Recognized Contributor
@dr.bathman
Some info and critique:
Magisk cannot replace the bootanimation in /system directly since the Magisk image is not mounted until after it starts. See post #7 of the main Magisk post:
To add it to a module, you would set POSTFSDATA to true and add this to /common/post-fs-data.sh:
In all four of your modules, the MODID in config.sh is googledialercontactsmessages. The id in module.prop has the proper names.
Also, the permissions are already set in config.sh for 0755 for folders and 0644 for files. The line you added to set 0644 permissions for the bootanimation.zip is redundant and unnecessary.
Some info and critique:
Magisk cannot replace the bootanimation in /system directly since the Magisk image is not mounted until after it starts. See post #7 of the main Magisk post:
For example, you want to replace /system/media/bootanimation.zip, copy your new boot animation zip to /cache/magisk_mount/system/media/bootanimation.zip with any root explorer, Magisk will mount your files in the next reboot.
To add it to a module, you would set POSTFSDATA to true and add this to /common/post-fs-data.sh:
Code:
mkdir -p /cache/magisk_mount/system/media/
cp -f $MODDIR/system/media/bootanimation.zip /cache/magisk_mount/system/media/bootanimation.zip
In all four of your modules, the MODID in config.sh is googledialercontactsmessages. The id in module.prop has the proper names.
Also, the permissions are already set in config.sh for 0755 for folders and 0644 for files. The line you added to set 0644 permissions for the bootanimation.zip is redundant and unnecessary.
Last edited: