Hey, I had the same issue some time back, and I have the same board. Seems to be an issue with 2 boards I’ve seen now(at the very least). The way I fixed it was by downloading the (slightly) older 2503 firmware.
(Quick note to anybody coming across this: DO NOT follow these instructions if you don’t have a Marasov board and/or do not feel comfortable doing this. I am just giving instructions for Marasov users that need to boot their Chromebooks and are affected by this bug. I am not liable for any bricking that may have been caused by you not listening to this warning. You have been warned)
Start up Linux in a bootable USB and start up the MrChromebox firmware utility script(I recommend Ubuntu for this because their kernel is lax enough to allow the script to operate)
Backup your current firmware to a secondary storage medium. If you have a second USB, put it there. Cloud storage services such as Google drive or Proton Drive are also an option. There are advanced ways to recover from bricking and it’s better to be able to turn on your Chromebook and not boot to an operating system than to have a bricked Chromebook and not be able to do anything with it.
Select “Flash custom firmware” in the utility script and point it towards the firmware file exactly. The path you give should look like this: /home/[username of live environment]/Downloads/coreboot_edk2-marasov-mrchromebox_20250427.rom. Let the flashing process run its course
Reboot(through the utility script or Ubuntu, it doesn’t matter which). Whichever operating system you have on the internal storage should boot properly now.