[Magisk] vladin79:
Thank you very much for your reply.

I have patched the boot image with "Preserve dm-verity" enabled, but again it is stuck on the boot animation.

This is the log from Magisk Manager when patching the boot image:

- Copying image locally
- Target image: /data/data/com.topjohnwu.magisk/install/boot.img
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_21f9cec6deb5897d8707666e6b64e5c29055ed76.img.gz]
- Patching ramdisk
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Save SHA1: [21f9cec6deb5897d8707666e6b64e5c29055ed76] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
- Repacking boot image
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
KERNEL [7094175]
RAMDISK [668173]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [91065cd3c70eaa74d173a4806f64db3b07f2b3c9]
DTB [23079]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [7094175]
RAMDISK [928008]
SECOND [0]
EXTRA [0]
PAGESIZE [2048]
NAME [1465011659]
CMDLINE [bootopt=64S3,32S1,32S1]
CHECKSUM [8dd621ec0dbb737eeedadbf8b8681f6a04b6409b]
MagiskBoot v16.7(1671) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...

****************************
Patched image is placed in
/storage/sdcard0/MagiskManager/patched_boot.img
****************************
- All done!

This is the /cache/magisk.log

08-09 12:30:31.285 203 203 I Magisk : ** Initializing Magisk
08-09 12:30:31.286 203 203 I Magisk : * Creating /sbin overlay
08-09 12:30:31.599 203 203 I Magisk : * Mounting mirrors
08-09 12:30:31.601 203 203 I Magisk : mount: /sbin/.core/mirror/system
08-09 12:30:31.601 203 203 I Magisk : link: /sbin/.core/mirror/vendor
08-09 12:30:31.601 203 203 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 12:30:31.601 203 203 I Magisk : * Setting up internal busybox
08-09 12:30:31.686 209 209 I Magisk : Magisk v16.7(1671) logger started
08-09 12:30:31.687 206 206 I Magisk : Magisk v16.7(1671) daemon started
08-09 12:30:31.695 206 211 I Magisk : ** post-fs-data mode running
08-09 12:30:31.696 206 211 I Magisk : * Mounting /data/adb/magisk.img
08-09 12:30:31.912 206 211 I Magisk : * Running post-fs-data.d scripts
08-09 12:30:31.912 206 211 I Magisk : * Running module post-fs-data scripts
08-09 12:30:31.912 206 211 I Magisk : * Loading modules
08-09 12:30:31.913 206 222 I Magisk : * Starting MagiskHide
08-09 12:30:31.913 206 222 I Magisk : hide_utils: Hiding sensitive props
08-09 12:30:31.914 206 222 I Magisk : hide_list: [com.google.android.gms.unstable]

I have attached the logcat via ADB during boot. It seems that there is a pattern that repeats forever. Any thoughts?