I'm fairly confident the problem here is the bootloader version. The file that worked to restore your phone has the V2 bootloader, and the XAA firmware is a V1 bootloader. I just tried the same on my up to date A32 5g and got the same results - the XAA load bombed out, and the error screen popped up on reboot. Loading the TMB firmware worked just fine.
I have two more A32 5g that should still be factory images with no updates. I'll try to find some time to do the same process to one of them tomorrow and verify if that's the difference. My limited research indicates that Samsung created some new hurdles to jump through with the updated bootloader in the last OTA update.