DEV Community

Hedy
Hedy

Posted on

What to do if Raspberry Pi won’t boot?

If your Raspberry Pi isn’t booting, follow these steps to diagnose and fix the issue:

1. Check Power Supply Issues (Most Common Cause)
Symptoms

  • No LED lights (or only a red LED).
  • Random reboots or instability.

Solutions
✅ Use a high-quality power supply (5V, ≥2.5A for Pi 3/4, ≥3A for Pi 5).
✅ Try a different USB-C/micro-USB cable (some cables don’t deliver enough power).
✅ Check the red LED:

  • Solid red = Power is good.
  • Flickering/blinking red = Under-voltage (use a better power supply). ✅ Disconnect power-hungry peripherals (HDDs, USB devices) and retry.

2. Verify the SD Card (Second Most Common Issue)
Symptoms

  • Green LED flashes briefly but no boot.
  • Corrupted OS or failed writes.

Solutions
✅ Reinsert the SD card (poor contact can prevent booting).
✅ Test with a known-working SD card (another Pi’s card or a fresh install).
✅ Reformat & Reinstall Raspberry Pi OS:

  • Use Raspberry Pi Imager (Download) to flash a fresh OS.
  • Select the correct model (Pi 3/4/5, Zero, etc.).
    ✅ Check for SD card corruption:

  • If the Pi was improperly shut down, the file system may be corrupted.

  • Try fsck on another Linux PC:

bash
sudo fsck /dev/sdX  # Replace sdX with your SD card (e.g., sdb1)
Enter fullscreen mode Exit fullscreen mode

3. Check HDMI & Display Issues
Symptoms
Red LED on, but no display output.

Solutions
✅ Try a different HDMI cable/port (some Pis need HDMI0 for initial boot).
✅ Force HDMI detection (edit config.txt on the SD card):

  • Mount the SD card on another PC.
  • Add these lines to config.txt:
text
hdmi_force_hotplug=1  
hdmi_group=2  
hdmi_mode=82  # For 1080p)
Enter fullscreen mode Exit fullscreen mode

✅ Test with a different monitor/TV (some displays don’t support the Pi’s default resolution).

4. Diagnose Bootloader/Firmware Issues
Symptoms

  • Solid red + green LED = Bootloader issue.
  • No green LED activity = Firmware corruption.

Solutions
✅ Reinstall the bootloader (Pi 4/5):

Download the latest EEPROM firmware:

bash
sudo rpi-eeprom-update -a
Enter fullscreen mode Exit fullscreen mode

Flash via another Pi or USB recovery.
✅ Check for start*.elf missing errors (corrupt firmware files on SD card).

5. Test Without Peripherals (Minimal Boot)
Disconnect all USB devices, GPIO accessories, and cameras.

Boot with just:

If it boots, reconnect devices one by one to find the faulty component.

6. Advanced Debugging (Serial Console/UART)
If the Pi still won’t boot, check kernel logs via UART:

  1. Connect a USB-to-TTL adapter (e.g., CP2102) to GPIO pins:
  • TX (Pi) → RX (USB adapter)
  • RX (Pi) → TX (USB adapter)
  • GND → GND
  1. Use a terminal (PuTTY, screen) at 115200 baud to see boot logs.

  2. Look for errors like:

  • Failed to start Linux kernel → SD card or firmware issue.
  • Under-voltage detected → Power supply problem.

7. Check for Hardware Damage
Symptoms

  • Burnt smell, bulging capacitors, or physical damage.
  • No LEDs at all (dead board).

Solutions
🔹 Inspect for burnt components (replace if damaged).
🔹 Try a different Pi (if available).

Quick Troubleshooting Checklist

Final Steps

  1. Reinstall Raspberry Pi OS using Raspberry Pi Imager.
  2. Test with a different SD card and power supply.
  3. Check UART logs if still unresolved.

If the Pi still won’t boot, it may be faulty and need replacement.

Top comments (1)

Collapse
 
nalin_amarasekaraa_226e8f profile image
Nalin Amarasekaraa

Hi @carolineee, you have any succession to this issue ?

forums.raspberrypi.com/viewtopic.p...