OxygenOS fix

[blxckhundred]

Hi! I am interested in your module, but judging by the description, I understood that it most likely will not work on OOS15. I assume that the animation file in this system is not in
/system/product/media/bootanimation.zip
but in
/my_product/media/bootanimation/bootanimation.zip

You can add this to your module, I think it should work.

[blxckhundred]

This is what it looks like.
(rbootanitation - animation of turning off the phone)

[rhythmcache]

I have already tried this, but it didn't work. On 1+, the boot animation is located at /my_product/media/bootanimation/bootanimation.zip ... ok.... but afaik Magisk/KSU/Apatch only support replacing files in /system. If /my_product is not inside or linked to /system, perhaps it won't work.
also the desc.txt format on 1+ devices differs from the AOSP ig. btw I don’t have a 1+ device to test this ... but you can try it manually, and if it works for you, I'll add it.

[blxckhundred]

I have already tried this, but it didn't work. On 1+, the boot animation is located at /my_product/media/bootanimation/bootanimation.zip ... ok.... but afaik Magisk/KSU/Apatch only support replacing files in /system. If /my_product is not inside or linked to /system, perhaps it won't work. esc.txt format on 1+ devices differs from the AOSP ig. btw I don’t have a 1+ device to test this ... but you can try it manually, and if it works for you, I'll add it.

I parsed the contents of these .zip archives and asked ChatGPT to decipher for me what was written in desc.txt. All in all, nothing complicated.
All animations are just .png pictures (1 picture = 1 frame), and desc.txt is how they should behave.
So, hypothetically, even if Magisk can't replace these files automatically, it can be done manually. The main thing is that there should be an automated software that would divide animations into frames and crop them

Attached is the archive and what ChatGPT said.

bootanimation.zip

[rhythmcache]

well the structure of your device desc.txt is

g 1080 280 0 661 30

And structure of the desc txt used by my rom (also by most of the roms and devices) is

1080 1920 30

Here 1080x1920 is the resolution, and 30 is the FPS, which is quite simple. However, your desc.txt has extra fields (such as global , offsets, as chatGPT mentioned) which differ from the standard format. I'm not sure how these fields affect the boot animation's behavior.

If you just need something to convert videos into boot animations, you can use this Termux script:

https://github.com/rhythmcache/Video-to-BootAnimation-Creator-Script

.. though you will need to manually modify the desc.txt file in the generated bootanimation.zip to match your original boot animation format.

Ps : I put your oneplus bootanimation.zip in my ROM, but my ROM didn't support it. It booted with a black screen.

[ChiquitoDiego]

Hi! I am interested in your module, but judging by the description, I understood that it most likely will not work on OOS15. I assume that the animation file in this system is not in /system/product/media/bootanimation.zip but in /my_product/media/bootanimation/bootanimation.zip

You can add this to your module, I think it should work.

Greetings,
I also have huge difficulties to replace the /system/media/product/bootanimation.zip on a OnePlus 7T with rooted Android 11. Even after installing RO2RW, I am able to have R/W access for /system/ and /system/media/ but not /system/media/product/ which remains Read Only whatever I try. I am blocked here.
Thanks by now for any hint.
Dav

[blxckhundred]

Yoooo! I found a Magisk module that runs on OOS15 with no problems! It turns out that Magisk has access to the new directory just like all the others. And the archive just has the same frame-by-frame images as the original.
So the only difficulty in replacing boot animation on OOS15 is to make a frame-by-frame video and write the necessary desc numbers to it, but I think this task is doable.

OPPOFindX8UNewbootAnimation_2.zip

[blxckhundred]

ChatGPT explained
The module doesn't seem to replace the animation directly, but only substitutes it early in the loading process

[rhythmcache]

could you run this in termux of your device and tell the ouput ?

su -c zcat /proc/config.gz | grep OVERLAY_FS

module.zip

Also could you test this module on your device and tell if it works ?

I have tried to fix it for oxygen os using overlayfs

d02ebf1

[blxckhundred]

could you run this in termux of your device and tell the ouput ?

su -c zcat /proc/config.gz | grep OVERLAY_FS

module.zip

Also could you test this module on your device and tell if it works ?

I have tried to fix it for oxygen os using overlayfs

d02ebf1

Here is the output of that command:

~ $ su -c zcat /proc/config.gz | grep OVERLAY_FS
CONFIG_OVERLAY_FS=y
                   # CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
             CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
      # CONFIG_OVERLAY_FS_INDEX is not set
                                          # CONFIG_OVERLAY_FS_XINO_AUTO is not set
                                 # CONFIG_OVERLAY_FS_METACOPY is not set

But for some reason the module doesn't change anything - after installing it, the standard power-on animation is still running

[rhythmcache]

Weird.
I created a similar folder, like oos, in my root directory /my_product/media/bootanimation, and the module is correctly placing the bootanimation file there.

also could you run

mount | grep overlay

(Module should be installed while running)

[rhythmcache]

video-to-bootanimation-main-test.zip

This is modified video to bootanimation module which writes oos style desc.txt if it detects bootanimation is in /my_product . You can also test this btw..

[ChiquitoDiego]

Greetings,
In fact, I have been able to put standard boot animation using this post:
https://xdaforums.com/t/guide-how-to-change-any-file-or-directory-using-magisk.4543103/
I am happy now :-)
I hope this helps.
Dav

[eyeblech]

even your shows cfg undetectable> video-to-bootanimation-main-test.zip

This is modified video to bootanimation module which writes oos style desc.txt if it detects bootanimation is in /my_product . You can also test this btw..