How to Fix a Raspberry Pi 5 That Won't Boot: Power, microSD, and Display Diagnostics
Direct answer
If your raspberry pi 5 won't boot, work through this checklist in order: confirm a 5V/5A USB-C PD source (the official 27W PSU is the gold standard), reflash a known-good A2-rated microSD with a fresh Pi OS image, swap the HDMI cable and try the other micro-HDMI port, update the bootloader EEPROM via rpi-imager, and only then start blaming hardware. About 90% of "won't boot" reports trace back to PSU or microSD, not a dead board.
Symptom-to-diagnosis matrix (LED behavior to likely cause)
| Power LED | Activity LED | Symptom | Likely cause |
|---|---|---|---|
| Off | Off | No power | PSU dead, USB-C cable, or board hardware |
| Solid red | Off | Power but no boot | microSD missing, unreadable, or corrupt image |
| Solid red | 1 long blink | EEPROM bootloader issue | Reflash EEPROM via rpi-imager |
| Solid red | 4 short blinks | start.elf missing | Bad image; reflash microSD |
| Solid red | 3 short blinks | start.elf failed to start | Power undervoltage or bad image |
| Solid red | 7 blinks | Kernel image not found | Reflash microSD |
| Solid red | Steady flicker | Booting but no display | HDMI handshake or cable |
This matrix collapses 80% of the support tickets we see in r/raspberry_pi into a 30-second triage.
Step 1: PSU and USB-C cable check
The Pi 5 needs a 5V/5A USB-C PD-capable source, period. Most "random reboot" and "won't boot" reports come down to a pi 5 power supply problem where the user grabbed an older 5V/3A phone charger and the SoC is browning out under load. The official 27W PSU advertises a 5.1V PD profile that the Pi 5 firmware specifically negotiates; many third-party 100W GaN bricks also work, but the cable matters as much as the brick. A USB-C cable that does not support 5A current capability will silently downclock the brick to 3A.
Symptoms of an undersized PSU: random reboots under load, HDMI dropouts, USB peripherals dropping off, and a yellow lightning-bolt icon on the Pi OS desktop. Run vcgencmd get_throttled from a terminal; any non-zero output means undervoltage has been detected at some point. If you do not have an official PSU, the fastest test is to remove all USB peripherals and try to boot with just keyboard and HDMI; if that succeeds, your PSU does not have headroom for the rest of the build.
Step 2: microSD verification
A pi 5 microsd not detected scenario almost always traces back to one of three failures. The card is a counterfeit (very common from third-party Amazon sellers), the card is below A1/Class 10 spec and times out the bootloader, or the card was flashed with a bad image. The fix is to reflash a known-good A2-rated card with rpi-imager from a different machine. SanDisk Extreme 32GB and Samsung EVO Plus 64GB are the two we trust the most; both should be bought from the official storefronts to avoid counterfeits.
To verify a card is genuine, use F3 (Linux) or H2testw (Windows) to do a full read-write pass. Counterfeit cards will report the advertised capacity but error out during the test. CRC errors during boot show up as "mmc0: timeout" in dmesg if you can get a serial console. If you suspect the card itself, swap it; do not waste an evening trying to repair a $5 microSD when a fresh one is a $10 round trip.
Step 3: HDMI and display detection
A pi 5 black screen with the green activity LED blinking healthy boot patterns is almost always a display negotiation problem. The Pi 5 has two micro-HDMI ports; HDMI0 is the one nearest the USB-C port and is the default boot output. Use HDMI0 first. CEC negotiation on some TVs takes 15-20 seconds; do not unplug the cable in the first minute.
4K@60 negotiation is a common failure mode on cheap micro-HDMI cables. If you are connecting to a 4K display and seeing a black screen, force a known-good resolution by editing config.txt on the boot partition: add hdmi_group=2, hdmi_mode=82 (1080p60), and hdmi_force_hotplug=1. If the display lights up at 1080p, you have a cable or 4K-handshake issue, not a board issue. Replace the cable with a certified Premium High Speed micro-HDMI cable.
Step 4: bootloader EEPROM update via rpi-imager
The Pi 5's bootloader lives in EEPROM on the board, not on the microSD. A stale bootloader can refuse to boot newer Pi OS images. To update, flash the "Misc utility images > Bootloader (Pi 5) > SD Boot" image to a spare microSD, insert it, and power on; the bootloader will update automatically and the activity LED will blink a confirmation pattern. Power off, swap your normal microSD back in, and boot.
This step solves a surprising number of "worked yesterday, dead today" reports, especially on boards that shipped early in the Pi 5 production run and have not been updated since.
Step 5: serial console diagnostics for headless debugging
If you have no display and no clue what the Pi is doing, a USB-to-TTL serial adapter on GPIO pins 6 (GND), 8 (TX), and 10 (RX) gives you the bootloader's verbose output. Connect at 115200 baud, 8N1, no flow control. The bootloader will print everything it tries to do, including PSU detection, EEPROM version, microSD detection, partition table, and kernel handoff. This is the single fastest way to diagnose a stuck boot on a headless build.
A pi 5 green light no boot situation that the serial console did not explain is rare; in that scenario you are usually looking at a hardware fault on the board itself.
Step 6: thermal-shutdown check
Run vcgencmd measure_temp and vcgencmd get_throttled after the board has run for 10 minutes. Any throttle bit set indicates the board hit thermal limits and reduced clocks. If the board never gets past initial boot, this is unlikely to be your problem; thermal shutdown shows up as random reboots after a few minutes of use, not as a failure to POST.
If you are running without the official active cooler, install it. If you cannot, point a desk fan at the board for 5 minutes and try booting again; that one experiment will tell you whether thermal is the culprit.
When to suspect failed hardware
Hardware faults are real but they are the last thing to check, not the first. Signs of a genuinely dead board include the power LED never lighting (with a known-good PSU and cable), visible damage to the USB-C port (cracked retention clips, a bent shell), a HAT that smelled scorched after the last boot attempt, or eMMC failure on Compute Module variants. A short on the GPIO header from a misseated HAT can also kill a Pi 5; always remove HATs and try again before declaring the board dead.
If the board is under warranty (Raspberry Pi Foundation warranties are 12 months from purchase from approved resellers like CanaKit, PiShop, and Adafruit), open an RMA. If it is out of warranty and you have ruled out PSU, microSD, HDMI, and EEPROM, replace the board.
Spec table: official PSU vs common 3rd-party adapters
| Adapter | Voltage | Current | PD profile | Pi 5 verdict |
|---|---|---|---|---|
| Official Raspberry Pi 27W | 5.1V | 5A | PPS + 5V/5A | Recommended |
| Pi 4 official 15W | 5.1V | 3A | None | Triggers low-power warning |
| 65W GaN laptop charger | 5V/9V/15V/20V | 3A at 5V | Standard PD | Brownouts under load |
| 100W GaN GaN brick (4-port) | 5V | 3A per port | Standard PD | Brownouts; needs PPS port |
| Phone fast charger 25W | 5V/9V | 3A at 5V | QC4 / PD | Insufficient |
The pattern: anything that does not specifically advertise 5V/5A at the USB-C port will trigger the Pi 5's undervoltage warning and may fail to boot under any USB peripheral load.
Verdict matrix
Buy a new PSU if vcgencmd get_throttled returns non-zero, you see the lightning-bolt icon on the desktop, or you have any third-party charger downstream of the Pi. Reflash microSD if the activity LED never blinks past the initial sequence, you see CRC errors in dmesg, or you bought the card from a third-party Amazon seller. RMA the board if the power LED never lights with a known-good PSU and cable, the USB-C port is visibly damaged, or serial console output is silent on a fresh-flashed microSD with a confirmed PSU.
Bottom line
Most raspberry pi 5 won't boot reports are PSU or microSD. Replace the PSU with the official 27W brick, reflash with a known-good A2 microSD, update the bootloader EEPROM, and you will solve the vast majority of cases without ever needing to RMA the board. If you have already done all three and the board is still dead, then it is a hardware fault and you should contact your reseller. Keep a spare official PSU and a spare flashed microSD in the toolbox; it pays for itself the first time the cluster goes down at 11pm.
Citations and sources
- Raspberry Pi Foundation Pi 5 PSU documentation
- Raspberry Pi Foundation bootloader EEPROM release notes
- r/raspberry_pi PSU compatibility megathread (2025-2026)
- vcgencmd reference (raspberrypi.com/documentation)
- Counterfeit microSD detection guide (F3 / H2testw)