You could run the getvar command and compare partitions
Maybe try flashing "vendor_boot" or "abl" from the fastbootd.
Fastboot is stored on "abl" partition, so a bit of precaution
I would recommend backing them up before flashing over
When I use the MSM tool it flashes the "vendor_boot"
Do you know where I can get a copy of the abl partition? I am guessing it is not the abl.elf file found in the firmware ofp? And do I use dd to backup the file located in dev/block/by-name/abl_<a,b>?
I will try it but idk if it's going to allow me to flash the abl partition in fastbootd though. Ever since I tried doing a local install of A.20 then I MSM tool it back to A.17 and took the A.20 update ota (was trying various things to see if it would fix it) now it wont even flash the boot.img anymore. I get FAILED (remote: No such file or directory). Have already tried the MSM tool again to go back to A.17 but still can't flash a boot.img. So now I'm back to having an unlocked bootloader that I cannot relock and also cannot root the phone either lol.
Edit: "fastboot oem device-info" fails and "fastboot getvar all" gives me a completely different output from what you show. Not a single line is the same for me to be able to compare it to. And oh yeah I can't root the phone so I won't be able to backup the abl partition huh?
Edit again: okay so no idea why this worked but I tried "fastboot flash boot_b boot.img" and this worked and allowed me to root the phone. Last time I rooted I definitely used "fastboot flash boot boot.img" so idk why that stopped working but at least I am now rooted again. Also wanted to add that even after I flash the phone with MSM tool, USB debugging is enabled so something/some partitions are not being overwritten. I know MSM tool doesn't seem to overwrite the persist.img so could something in there be causing this? Or any other partitions not being overwritten that could potentially cause this?