So I plugged my boot usb into my chromebook, and then went into the mx-linux systemd. I installed it there and when I reboot I get this message:
Booting from ‘MX Linux’ failed: Not Found
Verify it contains/points to a valid 64-bit UEFI OS.
Press any key to continue
Probably should have booted to MX-Linux?
This error usually means the Chromebook’s UEFI firmware can’t find a valid bootloader after installation, which often happens if MX Linux wasn’t installed with the correct EFI settings or the boot entry wasn’t created properly. To fix it, boot back into your MX Linux USB, open a terminal, and make sure the system was installed in UEFI mode (not legacy/BIOS). Then reinstall or repair the bootloader by mounting your installed system and running a GRUB reinstall (e.g., using grub-install targeting the EFI directory and update-grub). Also verify that an EFI System Partition (ESP) exists and is formatted as FAT32 with the correct flags (boot and esp). If the boot entry is missing, you can recreate it using efibootmgr or MX’s Boot Repair tool. On Chromebooks with custom firmware, it’s also important to ensure your firmware supports full UEFI booting and that secure boot (if present) is disabled. Once the EFI entry correctly points to the MX Linux bootloader, the system should boot normally instead of showing the “Not Found” error.
Thanks for your response, I will try this and update. Also, I am using the UEFI full rom mrchomebox firmware, so I think it does fully support it.
Ok so I tried your steps, and I saw that there are 2 partitions of my main drive, one is fat32 formatted and has the flags boot and esp. the other partition is bigger and is ext4 formatted. Via the Boot Repair tool in MX, I changed the bootloader from the main drive to the first partition. After I rebooted, it looked like it created a new boot entry called “MX25” and it said this message while trying to boot:
Booting from ‘MX25’ failed: Not Found
Verify it contains/points to a valid 64-bit UEFI OS.
Press any key to continue
It then proceeded to try booting into MX Linux and provided with the same aforementioned error:
Booting from ‘MX Linux’ failed: Not Found
Verify it contains/points to a valid 64-bit UEFI OS.
Press any key to continue
I also checked that my secure boot was disabled and I was in UEFI mode.
there was an issue with the original release firmware on Stoneyridge devices, re-run the update and booting from internal storage should be fixed
no, it means that the drive with the bootloader on it can’t be found / file pointed to by the bootloader entry doesn’t exist.
Thanks for your reply @MrChromebox, what exactly do you mean by re-running the update? I am pretty sure I am on the latest version of the firmware, 2603.0. Also if there is a newer update, then how would i download it?
just run the script and update again, I was lazy and didn’t change the date
I just did this and thanks a lot. It actually worked! 
