The USB sits there and the screen stays black
You plug in a freshly written Fedora USB, restart your machine, and press the boot menu key. The firmware scans the drive, pauses for a second, and either drops you straight into your old operating system or prints a cryptic No bootable device found message. You double-check the ISO download, verify the flash drive works in another computer, and try again. The result is identical. The problem is rarely the hardware. It is almost always a mismatch between the firmware expectations, the partition layout, and the bootloader chain.
What is actually blocking the boot
Modern computers do not execute ISO files directly. They look for a specific directory structure on a FAT32 partition marked with the EFI system partition flag. If you are using a legacy BIOS machine, the firmware expects a Master Boot Record with a bootable flag on the first partition. Fedora ships with a hybrid ISO that supports both paths, but the writing tool must preserve the exact byte layout. When the layout shifts, or when Secure Boot rejects an unsigned bootloader, the firmware refuses to hand control to the kernel. The USB is physically connected, but the boot chain is broken at the first link.
Think of the boot process like a relay race. The firmware hands the baton to the EFI system partition. That partition hands it to shimx64.efi. shim verifies the signature and passes it to grubx64.efi. GRUB loads the kernel and initramfs. If any runner drops the baton, the race stops. Your job is to make sure the track is set up correctly before the starting gun fires.
Check the firmware mode first. UEFI and Legacy BIOS do not share boot paths. A drive formatted for UEFI will be invisible to a Legacy BIOS. A drive formatted for Legacy will be ignored by a UEFI firmware with CSM disabled. Match the drive layout to the machine mode.
Verify the image before you write it
A corrupted download will never boot. The Fedora project signs every ISO with a SHA-256 checksum. Verify it before you waste time writing a bad image to disk. A single flipped bit in the bootloader section will cause a silent failure at the firmware level.
Here is how to check the checksum against the official value from the Fedora download page.
sha256sum fedora-43-x86_64-netinst.iso
# Compare the output string with the official checksum on getfedora.org
# A mismatch means the download was interrupted or modified
# Do not proceed until the strings match exactly
# The hash must be identical character for character
If the checksum matches, the archive is intact. If it does not, delete the file and download it again. Network drops and browser caching can silently truncate large files. Always verify the hash before touching the block device.
Run the checksum verification before every write. A fresh download is never a waste of time when the alternative is a dead boot screen.
Write the USB correctly
The writing method determines whether the partition table and boot flags survive the transfer. Graphical tools sometimes repartition the drive or convert the filesystem to ext4, which breaks UEFI compatibility. Stick to byte-level copying or dedicated Fedora tools. The hybrid ISO contains both a GPT and an MBR. You must write to the raw block device, not to a partition slice.
Here is how to write the ISO directly to the block device using dd.
sudo dd if=fedora-43-x86_64-netinst.iso of=/dev/sdX bs=4M status=progress oflag=sync
# if= specifies the input file path to the downloaded ISO
# of= specifies the raw block device, not a partition like /dev/sdX1
# bs=4M sets the block size for faster sequential writes
# oflag=sync forces each write to complete before returning to the shell
# status=progress shows a live transfer counter so you can track completion
Replace /dev/sdX with your actual device identifier. Run lsblk before and after plugging in the USB to identify the correct letter. Never guess the device path. Writing to the wrong block device will overwrite your internal drive.
Convention aside: dd does not verify the write by default. The oflag=sync flag mitigates cache-related corruption, but running sync immediately after dd is still a safe habit on older kernels. Modern dd with oflag=sync is sufficient. Fedora Media Writer handles the byte-level copy and verifies the write automatically. Ventoy lets you drop the ISO onto a pre-formatted FAT32 drive and boot it directly without rewriting. Both tools preserve the hybrid MBR/GPT layout that Fedora expects.
Verify the device path with lsblk before typing dd. One wrong letter wipes your system disk.
Configure the firmware to actually see it
The USB is ready. The firmware now needs to be told to look at it. UEFI systems ignore bootable USB drives if Secure Boot is enforcing a strict signature policy and the drive lacks the required Microsoft or Fedora keys. Legacy systems ignore UEFI-formatted drives entirely if CSM is disabled.
Enter the firmware setup utility. The key is usually F2, F12, Del, or Esc. Navigate to the boot configuration section. Disable Fast Boot. Fast Boot skips USB enumeration to save seconds, which guarantees your drive will be invisible. Enable UEFI mode. Disable Legacy/CSM unless you are installing on hardware older than 2012. Set the USB drive as the first boot option. Save and exit.
If Secure Boot is enabled, Fedora will boot normally because the installation media ships with signed shim and grub binaries. If you are using a third-party tool that strips signatures, or if you modified the ISO, Secure Boot will block the handoff. Disable Secure Boot temporarily for the installation. You can re-enable it after Fedora installs its own keys during the first boot.
Here is how to list the current UEFI boot entries from a live session or another Linux machine.
efibootmgr
# Shows the active boot order and registered EFI loaders
# Look for an entry pointing to /EFI/fedora/shimx64.efi
# If the entry is missing, the firmware did not register the drive
# Use efibootmgr -c -d /dev/sdX -p 1 -L "Fedora" -l \\EFI\\fedora\\shimx64.efi to add it manually
The efibootmgr output tells you exactly what the firmware sees. If your USB is absent from the list, the partition table is wrong or the boot flag is missing. Rewrite the drive with dd or Fedora Media Writer. Do not format the USB manually. The ISO contains the exact partition table it needs.
Save the firmware settings and reboot. The boot menu key is faster than digging through setup menus when you just need to test a drive.
Verify it worked
Reboot with the USB inserted. Watch the firmware output. You should see the drive name in the boot device list. If the screen goes black and returns to the firmware menu, the partition layout is wrong or the boot flag is missing. If you see a GRUB menu, the chain is intact.
Here is how to check the partition layout from a live session or another Linux machine.
sudo fdisk -l /dev/sdX
# Look for a partition with type EFI System and a bootable flag
# The filesystem should be FAT32
# The partition size should be around 600MB to 1GB
# The second partition should be ext4 or squashfs containing the live OS
# Any deviation from this layout means the write tool altered the ISO structure
If the EFI partition is missing, the writing tool converted the hybrid ISO into a standard ext4 disk image. Rewrite the drive using dd or Fedora Media Writer. Do not format the USB manually. The ISO contains the exact partition table it needs.
Boot into the live environment and run lsblk again. Confirm the device mounts correctly. If the live session loads, the USB is ready for installation.
Test the live environment before installing. A working live session guarantees the media is intact.
Common pitfalls and what the error looks like
Boot failures rarely say exactly what went wrong. They show symptoms that point to specific layers.
The firmware prints No bootable device found or Boot Device Not Found. The USB is not marked as bootable in the firmware, or the drive lacks an EFI system partition. Check the boot order and rewrite the ISO.
The screen shows Secure Boot violation or Invalid signature. The bootloader binaries are unsigned or corrupted. Disable Secure Boot in the firmware setup, or rewrite the USB with an official tool that preserves signatures.
GRUB loads but drops to a grub rescue> prompt. The filesystem on the USB is damaged or the partition table is inconsistent. Run ls at the rescue prompt to see if GRUB can read the drive. If it cannot, the write process failed. Reformat and rewrite.
The system hangs at Loading initial ramdisk... with no further output. The initramfs is missing or the kernel cannot find the root filesystem. This usually means the ISO was truncated during download. Verify the checksum again.
The firmware shows EFI stub: failed to load custom SBAT or SBAT level violation. Your firmware is too old to support the current Fedora bootloader signatures. Update the machine firmware with fwupdmgr or use a slightly older Fedora release that matches your hardware generation.
Read the exact error string before guessing. The firmware and GRUB tell you which layer failed.
When to use this vs alternatives
Use dd when you need a guaranteed byte-for-byte copy of the hybrid ISO and want zero external dependencies. Use Fedora Media Writer when you want automatic verification and a graphical interface that handles device detection safely. Use Ventoy when you maintain multiple ISOs and want to switch between them without rewriting the drive. Use a dedicated USB-to-SD adapter when your laptop lacks enough ports and you need to boot from a card reader. Stick to official Fedora media when you want to avoid signature mismatches and partition table corruption.