A Raspberry Pi that won't boot is usually trying to tell you exactly what failed, you just have to watch the right light. The steady red LED only confirms the board has 5V power. The diagnostic lives in the green activity LED, which flashes a pattern of long and short blinks that maps to a specific fault, from a missing firmware file to a card the Pi cannot read.

Quick Answer

Ignore the red LED beyond confirming power, and count the green activity LED flashes. Three flashes means the Pi cannot find start.elf, four means it found it but it is corrupt or the card is reading in 1-bit mode, seven means kernel.img is missing, and eight means the RAM was not detected. The flash count tells you whether to fix the card, reflash the firmware, or look at hardware.

What the red LED does and does not tell you

The red LED is a power indicator and nothing more. A steady red glow says the board is receiving its 5V supply and the power circuitry is alive. It says nothing about whether the Pi is booting successfully. People often stare at the solid red and assume the Pi is dead, when in fact the board is powered and waiting on a problem the green LED is reporting.

So the first move is always the same: watch the green activity LED through a power cycle and count the flashes in the repeating pattern. That count is the diagnostic.

Reading the green flash codes

The flashes come in groups that repeat, and the count in each group is the code. The common boot-failure patterns are:

  • Three flashes: the Pi cannot find start.elf on the card. This is the GPU firmware that kicks off the boot, and without it the board has nothing to run.
  • Four flashes: start.elf was found but is not launchable, usually corrupt. On a Pi 4 this can also signal a card-reader fault, where the card is only making contact on one data line and running in 1-bit mode, so a hardware issue masquerades as a corrupt file.
  • Seven flashes: kernel.img is missing. The firmware loaded but the operating system kernel it hands off to is not on the card.
  • Eight flashes: the system cannot detect the RAM, which points at the board rather than the card.

The pattern points you straight at the layer that failed: firmware, kernel, card, or hardware.

Fixing the common causes

Most flash-code failures trace back to the SD card, so start there. Reseat the card, then test it in another device to confirm it still reads. A corrupt or worn card causes a large share of three, four, and seven flash codes.

If the card is fine but the codes persist, reflash the operating system cleanly with the official imager, which restores start.elf, kernel.img, and the rest of the boot files in one step. That clears the missing-or-corrupt-firmware patterns directly. For a four-flash code that survives a fresh card and reflash, suspect the card slot or connector, particularly on a Pi that has seen heavy reseating. An eight-flash code that does not clear points at the board itself, at which point repair or replacement is the realistic path. If you are weighing a replacement or moving to a small always-on machine, the mini PCs range at Evetech covers the compact systems people often graduate to from a Pi.

Frequently Asked Questions

Why is only the red light on with no green flashing?

A steady red with no green activity means the board has power but is not getting far enough to report a code, or the card is not detected at all. Reseat the card, try a known-good card, and check the power supply delivers a stable 5V.

What does three green flashes mean?

Three flashes means the Pi cannot find start.elf, the firmware file that starts the boot process. The usual fix is reflashing the operating system to the card so the boot files are restored, or replacing a card that has failed.

Can the flash code lie about a corrupt file?

On a Pi 4 a four-flash code can come from a card-reader fault rather than a genuinely corrupt start.elf. If the card only contacts on one data line it reads in 1-bit mode and triggers the same code, so a four-flash that survives a fresh card points at the slot.

How do I fix a missing kernel.img (seven flashes)?

Reflash the operating system to the card with the official imager. The kernel image is written as part of a clean install, so a fresh flash restores it. If it recurs immediately, the card is likely failing and should be replaced.

What if I get eight flashes?

Eight flashes means the RAM was not detected, which is a board-level hardware fault rather than a card or firmware problem. Reflashing will not help, so this usually means repair or replacement of the board.

If the flash codes point to a board that has reached the end of the road, it may be time to step up. Browse the mini PCs range at Evetech for compact, always-on machines, and see what builders are choosing in the PC best sellers at Evetech.