[Android Q&A, Help & Troubleshooting] btiu:
A5 Pro CC collection of random solutions:

The ff are 3 ways I found to get out of a bootloop. I recommend trying it in order so that you don't lose your data.

Spoiler content hidden.

Use Lite version of LiteGapps, not Micro​

I got into a bootloop because I installed the micro magisk module of the LiteGapps (600mb). You should install the Lite magisk version (60mb) for arm64 sdk29, it works on mine: MAKSU-LiteGapps-arm64-10.0-20240615-official.zip

Newer version of Magisk Patched/Signed boot.img​

I'm also uploading my patched (18mb) and patched-signed (35mb) boot image. This is based on Magisk 27.0 and the latest A5 pro cc multilang firmware (L1732.6.18). For people who just finished unlocking their Bootloaders, you can use the patched-signed.img.

Fix fastboot: error: boot partition is smaller than boot image​

After recovering from a bootloop through Methods 2, 3, and 4 above, I find that I still get this boot partition size error, and the only way I've been able to clear it is to trigger a factory reset from settings once I was out of bootloop! After this, I can once again flash the 35mb patched-signed version.

To leave download mode without erasing data​

Use this if you just went into download mode for whatever reason (to backup your boot.img after BL unlock, for example), and don't want to erase user data. Of course, you should still follow the original guide that wipes user data if you're still at the stage of unlocking your bootloader.

spd_dump fdl fdl1-dl.bin 0x5500 fdl uboot-mod.bin 0x9efffe00 exec write_part splloader u-boot-spl-16k-sign.bin reset

Boot into Safe Mode​

ONLY GO TO SAFE MODE IF YOU HAVEN'T ADDED A GOOGLE SYNC ITEM (calendar, gmail etc). This is only safe to do in the ff scenarios: installed the wrong gapps module but haven't added any google account and apps. Not sure about magisk upgrade, should be ok, but @ ferlanero suggested to reflash the patched-signed.img in that scenario.

Going into safe mode while you have google sync items will cause a bootloop again! Safe mode is not so safe after all (this is because it unloads magisk and gapps, which have already been added to the accounts database. Safe mode essentially unloads non system apps, which messes with the database, resulting in an unbootable state.

3 ways to enter safe mode

From power off

Make sure your phone is turned off first, and not bootlooping. (One way to check is if you plug it into a charger, it will show battery charging. Then unplug.)

Press power button for 2 seconds to turn on, then press and hold only VolDown key all the way until it finishes booting to safe mode.

Middle of rebooting

If you can't do steps 1 and 2 and it's just stuck trying to boot, Press power button around 7-10 seconds until you trigger another reboot

Immediately let go of the power button once it vibrates/buzzes, then Vol Down simultaneously until you see the backlight come on. You can then let go and let it boot to safe mode.

If you have authorized root for adb shell in the past:

adb shell su -c 'setprop persist.sys.safemode 1'
adb reboot

Once in, you will notice magisk is not loaded, that's why it was able to boot. Turn on USB debugging from developer options and go to Method 2 to remove all modules (recommended), remove magisk app, or if you don't have a PC, try uninstalling Magisk from the app manager if it shows up there.