Solved thanks to Reddit user liwindowsnux’s comment under a post by someone experiencing a similar problem on r/RockyLinux.
You’ll need a tool (such as Rufus) to burn the installer ISO into the USB stick in ISO mode (not dd mode) to get access to the /<USB_Stick>/EFI folder. I guess you can also use dd mode if you can get access to the EFI partition.
After the burning process, backup /<USB_Stick>/EFI to somewhere else just in case.
Get into /<USB_Stick>/EFI/BOOT, delete the original BOOTX64.EFI and BOOTIA32.EFI.
Rename grubx64.efi and grubia32.efi to BOOTX64.EFI and BOOTIA32.EFI respectively.
Boot your system with this USB stick in UEFI mode and you should be able to boot into the installer.
I am having the same issue both with the Fedora 37 live CD and Ventoy 1.0.82 (which uses the Fedora 37 shims). If I swap out BOOTX64.EFI and mmx64.efi with ones from either Ubuntu or Parted Magic, everything works great. I have also posted in Ventoy’s issues list here start_image returned Unsupported in v3.4 · Issue #18 · ValdikSS/Super-UEFIinSecureBoot-Disk · GitHub
and here is some of the hardware I have had trouble with Fedora 37 on:
MSI Z97A Krait Edition motherboard in custom build PC (BIOS version 2.0 and latest 2.3) with Secure Boot disabled error messages: Invalid image
Failed to read header: Unsupported
Failed to load image: Unsupported
start_image() returned Unsupported
then it reboots
Dell Latitude 7490 laptop (latest BIOS) with secure boot enabled error messages: Failed to open \EFI\BOOT\∎ - Invalid Parameter
Failed to load image ∎∎: Invalid Parameter
start_image() returned Invalid Parameter, falling back to default loader
but then continues to grub and works anyway
That’s an unnecessarily complicated way of doing it. All you need to do is write the ISO to a USB stick first, then just mount the relevant partition from the stick (the second one) and replace the files in a normal way - file manager, console cp, whatever. You don’t need to go to the trouble of modifying the ISO itself unless you need to write it to a DVD-R or something.
Unless I’m missing something, the partition is ISO9660 which is decidedly read only.
Believe me, I wanted it to be the case I could just copy a file over, but at least for a thumb drive made with dd, there was no way I could make that work. Even just replacing the shim on the ISO with xorriso before dd-ing wasn’t enough to make my board boot, the boot image jiggery pokery was required.
Perhaps Fedora media writer does something different? Perhaps I’m just dense. But believe me, I spent at least 3 hours trying to find a not complicated way.
The first partition on the stick is ISO9660. The second partition is FAT, and that’s where all the EFI bootloader files are - it’s an EFI system partition (it has to be, or else the stick wouldn’t boot). I just confirmed this with a stick I have here that’s written with dd.
I was sure the first thing I tried was replacing the shim on the second partition and it still refused to boot which was why I started down the road of ISO modification. But I just tried it, and it worked. Sorry for the noise!
I am also having a similar problem. My laptop is ACER s1001. The problem that I face is similar but it has a slightly different twist with regards to the shim. The processor on my laptop is 64bit but the EFI BIOS is 32bit. I tried after replacing the 32bit shim from the centos 32bit shim but it didn’t work.
Surprisingly Fedora 31 (64 bit) is able to boot with UEFI enabled as well as disabled.
As I explained in the bug report, we did (try to) maintain specific 64-on-32 support for those odd systems for a while. IIRC it didn’t require a 32-bit kernel, only a 32-bit shim and grub, they could boot a 64-bit kernel (the systems themselves run 64-bit code fine, they just shipped with a 32-bit firmware for some bizarre reason). This has likely been lost or just broken along the way as these systems are so uncommon; I used to have one, but got rid of it some time back, so I wouldn’t know if this broke.
We certainly have supported Secure Boot since way before F31.
Anyway, problems on those systems are very likely a different thing from the problem being discussed in this thread.