--------------------------------------------------------------------------------------------------------------------------------------------------------
Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.
The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.
I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.
Any thoughts???
------------------------------------------------------------------------
Anyway, I discovered the solution to my dilemma mentioned above by searching thru forums and Youtube. This may be helpful to those who have flashed the latest ROM update for their phone, then flashed the Magisk patched boot.img and now the phone is unable to boot to the OS.
It appears that the bootloop caused by flashing the 'Magisk_v22.0_Patched_boot.img' was due to installed Magisk modules. This is what worked for me:
1. Boot into TWRP from fastboot.
2. Using the File Manager in TWRP navigate to the '/data/adb/modules/' folder where the Magisk modules reside as folders. Delete all of them.
3. If Magisk is NOT installed then flash 'Magisk_v22.0_Patched_boot.img' as Boot or 'Magisk_v22.0.zip' in TWRP and boot phone to the OS.
4. Open the Magisk app to configure Magisk and install the Magisk modules.
5. Reboot.
The phone is now running the latest ROM, rooted with Magisk v22.0, passes safety net all without erasing user data...