iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Raspberry Pi that will not boot usually has one of three faults: inadequate or unstable power, unreadable boot media, or a display path that is blank even though the computer is running. Diagnose them in that order. Identify the exact Pi model, reduce the hardware to the board and a known-good power supply, read the repeating ACT LED pattern, re-image and verify the microSD card, then use the HDMI bootloader diagnostics available on Pi 4 and later. Only after the boot process is shown to work should you troubleshoot the display cable, connector, panel power and configuration.
The fastest diagnostic order
Do not replace parts at random. Follow this sequence so that a display problem does not send you back to reformat a healthy card, and a weak power supply does not masquerade as a storage failure.
- Identify the exact model and match its power requirement.
- Disconnect USB accessories, HATs, GPIO devices and displays. Leave only the board, boot medium and power connected.
- Watch the status LEDs for a repeating long-and-short flash pattern.
- If the card is suspect, write a fresh operating-system image with Raspberry Pi Imager and let verification finish.
- On Pi 4 and later, power up once with boot media removed to display the bootloader diagnostic screen.
- If the bootloader or operating system is alive but the screen is blank, isolate the HDMI or DSI path instead of treating the board as dead.
Raspberry Pi’s documentation says that a device that has not booted within five minutes should be checked through its status LED. A few minutes of observation matters: some faults are reported only after the bootloader has attempted the card several times.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteMatch the power supply to the exact Raspberry Pi model
Power is the first check because a supply can light the board while still collapsing under the processor, storage and USB load. The current recommendations are model-specific.
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
| Raspberry Pi family | Recommended supply at the board | What to verify |
|---|---|---|
| Raspberry Pi 5 and Raspberry Pi 500 | 5 V/5 A | Use a good-quality supply and cable with enough current headroom for the board and peripherals. |
| Raspberry Pi 4 and Raspberry Pi 400 | 5 V/3 A | Confirm that the supply can sustain the current at the Pi’s power-in connector, not merely advertise a high value at the wall plug. |
| Raspberry Pi 1, 2, 3 and Zero models | 5 V/2.5 A | Older boards still need a stable 5 V source; a phone charger or thin cable can produce a voltage drop under load. |
Pi 5’s minimum boot figure versus the recommendation
Raspberry Pi documentation states that a Pi 5 needs a good-quality USB-C supply capable of delivering 3 A at +5 V (15 W) to boot. The current model table recommends 5 V/5 A for Pi 5 and Pi 500. Treat these as different limits: 3 A is the stated boot capability, while the 5 A recommendation provides the margin expected for normal operation and attached peripherals. A supply that barely reaches the minimum can still trigger instability when USB devices or other loads are added.
Check voltage at the connector, not just the label
On most models since Raspberry Pi B+, the low-voltage detector trips below 4.63 V ±5 percent; the Zero range is excluded from that statement. The detector responds to the voltage the board receives. A long, damaged or undersized cable can therefore cause the same symptom as an under-rated adapter even when the adapter’s label looks correct. Re-seat both ends, use the designated power-in connector, and substitute a known-good cable before blaming the SD card.
Remove load while testing
Disconnect powered USB drives, Wi-Fi adapters, cameras, HATs, fans, GPIO circuits and displays for the first boot attempt. A board that boots in this bare configuration has not “fixed itself”; it has identified a load, cable or accessory that needs to be added back one item at a time. If it fails even when bare, continue with the LED and boot-media checks below.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Read the ACT LED as a diagnostic code
The green ACT LED is not random decoration. Raspberry Pi documents repeating patterns in which long flashes come first, short flashes follow, and the sequence normally pauses before repeating. Count one complete cycle rather than reacting to a single blink.
Rank #2
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (4GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- CanaKit Mega Heat Sink - Black Anodized
| Pattern | Official interpretation | Practical next check |
|---|---|---|
| 0 long / 3 short | Generic boot failure | Check power, then re-image or replace the boot medium. |
| 0 long / 4 short | start*.elf not found |
The boot partition is missing required firmware files; write a complete, verified image. |
| 0 long / 7 short | Kernel image not found | Re-image the card and verify that the write completed. |
| 1 long / 2 short | SD-card overcurrent | Power down and test another known-good card; also recheck the supply and connector. |
| 2 long / 1 short | Partition is not FAT | Recreate the card with Raspberry Pi Imager rather than manually copying files. |
| 2 long / 2 short | Failed to read a partition | Suspect card corruption, a failing card or an incomplete image write. |
| 2 long / 3 short | Extended partition is not FAT | Replace the partition layout by writing a fresh supported image. |
| 2 long / 4 short | File signature or hash mismatch on Pi 4 and Pi 5 | Re-image with verification; a damaged or altered file is not being accepted. |
| 3 long / 1 short | SPI EEPROM error | Investigate bootloader or EEPROM state after power and card checks. |
| 4 long / 6 short | One power-failure diagnostic type | Return to the supply, cable and connector; test with the board stripped to essentials. |
| 4 long / 7 short | Another power-failure diagnostic type | Use a correctly rated supply and remove all peripheral load before retesting. |
The notation is literal: “2 long / 2 short” means two long flashes followed by two short flashes. If the pattern changes after you replace the supply or card, record the new code; the latest code describes the current failure, not necessarily the original one.
When the red LED is on but the green LED never flashes
A red power light alone proves only that some voltage reaches the board. It does not prove that the processor has read the bootloader or accessed the card. First test the correct model-specific supply and cable with every accessory removed. Then inspect the card and watch for an ACT pattern. No ACT activity after several minutes, with known-good power, points you toward bootloader, card or board-level investigation rather than the monitor.
Repair or eliminate the SD card as a variable
A card can be electrically present yet contain a damaged partition, an incomplete image or files that fail the bootloader’s signature check. The most reliable first repair is a clean write, not a manual deletion of a few files.
Recommended Free Tools
Write a fresh image with Raspberry Pi Imager
- Install and open Raspberry Pi Imager on a computer.
- Choose the operating system intended for the Pi model and the correct removable storage device. Double-check the destination because writing erases that device.
- Start the write and allow the application to complete its verification step. Do not remove the card when the progress bar reaches 100 percent; verification is a separate operation.
- Eject the card safely, insert it in the Pi, reconnect only the known-good power supply, and allow several minutes for the first boot.
Verification is important because a write that appears complete can still contain unreadable data. If verification fails, do not keep retrying the same card and reader indefinitely: try another known-good microSD card and, if the model supports it, an alternate boot medium.
Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
What the LED code tells you about the card
The partition and file errors in the LED table are stronger evidence of a boot-media problem than a blank HDMI screen. A “partition not FAT,” “failed to read partition,” missing start*.elf or missing kernel message means the bootloader reached the storage device but could not find a usable layout or file. A Pi 4 or Pi 5 signature/hash mismatch similarly calls for a verified re-image before any display troubleshooting.
Update the bootloader when the first image still fails
Official setup guidance recommends updating the bootloader and re-imaging when the initial attempt does not work. This is especially relevant after changing boot media or when a board has been stored for a long time. Perform the update using Raspberry Pi’s supported procedure for the exact model, then write and verify the operating-system image again. If two verified cards fail with the same code while the power supply is known good, the problem is less likely to be ordinary file corruption.
Use HDMI boot diagnostics on Pi 4 and later
Pi 4 and later models can show a bootloader diagnostic screen over HDMI even when no operating-system medium is installed. This is a powerful way to separate “the board never starts” from “the OS or display configuration is wrong.”
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors- Power the Pi down completely.
- Remove the microSD card or other boot medium.
- Connect a display to the correct HDMI connector and select that input on the display.
- Power the Pi with the correctly rated supply.
- Read the diagnostic screen for the detected model, bootloader information, boot order and the reason no usable medium was found.
A visible diagnostic screen proves that the processor, bootloader and at least one display path are functioning. It does not prove that the operating-system image is healthy; reinstall the image after recording the bootloader information. If the screen remains blank in this test, return to cable, connector, display power and supply checks before concluding that the SD card is at fault.
Rank #4
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
Separate a boot failure from a blank display
A Pi can finish booting while showing nothing. Treat “no picture” as a different branch whenever the LEDs and bootloader evidence indicate progress.
Check the physical display path
- Use the HDMI connector intended for the model and the cable type that matches it. On boards with more than one HDMI output, test the other output as well.
- Push each plug fully home and inspect for a cable that is bent, loose or damaged. A micro-HDMI plug that is not fully inserted can provide power negotiation without a usable video signal.
- Turn on the display and select the input actually connected to the Pi. Test the cable and display with another known-good source if possible.
- If the project uses a DSI panel, verify the ribbon cable’s orientation at both ends, its seating in the latch and the panel’s separate power connection.
- Disconnect GPIO wiring and HATs temporarily. A miswired GPIO circuit can interfere with boot or with a display accessory even when the Pi itself is healthy.
Check software and EEPROM state
After the physical checks, update the operating system and, where applicable, the Pi’s EEPROM or bootloader using the supported tools for that model. Review the display-related configuration for the operating system and panel you are using. A configuration copied from a different Pi generation, an obsolete overlay or a forced resolution can leave the system running with an unsupported mode.
Use the bootloader screen as the dividing line
If HDMI diagnostics appear with the boot medium removed, the cable, connector and display are capable of showing at least the bootloader. If diagnostics appear but the normal image does not, focus on the operating-system image and display configuration. If diagnostics never appear, test another cable, another display input and the other HDMI connector before replacing storage.
Symptom-based recovery paths
Red power LED, no green activity
- Confirm the model and use the matching 5 V/current recommendation.
- Replace the cable with a short, known-good one and connect it to the power-in port.
- Remove every accessory and boot with a verified card.
- Observe the ACT LED for a repeating code.
- On Pi 4 or later, remove the card and try the HDMI bootloader screen.
If there is still no ACT activity or diagnostic screen with known-good power, storage and display equipment, the remaining possibilities include a bootloader or board fault; document the exact model, power setup and LED behavior before seeking hardware service.
Best Value
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 32GB EVO+ Micro SD Card pre-loaded with 64-bit Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit 45W PD Power Supply for the Raspberry Pi 5
- Display Cable - 6 foot (Supports up to 4K 60p)
Repeating ACT code for a partition or file
Do not spend time adjusting HDMI settings first. Write a fresh image with Raspberry Pi Imager, complete verification, and try a second card if the first write fails. Codes for a non-FAT partition, unreadable partition, missing firmware or missing kernel are all storage-path failures until a verified alternate medium proves otherwise.
Power-failure code or unexpected shutdown
Strip the Pi to the board, boot medium and supply. Substitute the correct current-rated supply and cable, then add peripherals back one at a time. A board that is stable bare but fails when a drive, display or HAT is connected needs either a better power path or a lower-load accessory arrangement.
Bootloader screen appears, operating system does not
Record the boot order and the reason shown on the diagnostic screen. Check that the intended medium is in that order, then re-image and verify it. If two verified media fail, update the bootloader as recommended by Raspberry Pi and repeat the test before investigating the display configuration.
The operating system is likely running but HDMI is blank
Work only on the display branch: check the selected input, cable seating, correct HDMI or DSI connector, panel power, GPIO wiring and display configuration. Do not repeatedly rewrite a card that has already passed verification unless the LED code or bootloader screen identifies a storage error.
A compact decision checklist
- Model identified: Pi 5/500, Pi 4/400 or Pi 1–3/Zero.
- Power matched: 5 V/5 A, 5 V/3 A or 5 V/2.5 A as appropriate.
- Load removed: no USB accessories, HATs, GPIO circuits or display hardware during the first test.
- LED pattern recorded: count long flashes, then short flashes, through a complete repeat.
- Boot medium verified: Raspberry Pi Imager completed both writing and verification.
- Alternate medium tried: use a known-good card or supported boot medium if the first verified attempt fails.
- Bootloader separated from OS: Pi 4 and later tested with the medium removed and HDMI diagnostics observed.
- Display path isolated: correct connector, sound cable, powered display, correct input, secure DSI ribbon and no interfering GPIO wiring.
What to remember
Power must match the Pi generation, and voltage at the board matters more than the adapter label. A repeating ACT pattern identifies where the boot process stopped. Raspberry Pi Imager’s verified re-image is the first repair for suspected card corruption. On Pi 4 and later, the HDMI bootloader screen can prove that the board is alive without an operating-system card. Finally, a blank display is not proof of a failed boot: check the connector, cable, display power and configuration as a separate diagnostic branch.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
