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 has stopped booting is usually recoverable in under an hour if you work in a fixed order: identify the exact board, read what the board reports, check power, decide whether the existing card is worth keeping, and only then touch firmware. Most failures sit in the first three steps. Reflashing the bootloader is a last resort for specific models, not a first move.
This guide is written for a team trying to get an existing project running again, often close to a deadline. It assumes nothing about your board, operating system, or event rules, so each step names the condition that makes it apply.
Start with the board model and what it reports
Before changing anything, write down four things: the exact board model and revision, the current boot medium (microSD card, USB drive, or SSD), the power supply in use, and whether the project’s files need to be kept. Those answers decide which of the steps below apply to you.
Identify the board and its revision
The model name is printed on the board and on the packaging. Some boards also carry a revision code. Record both. Model support matters because power requirements, boot options, and bootloader recovery all differ between families.
#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
Read the green LED
The green activity LED flashes a pattern while the bootloader runs. Raspberry Pi’s official documentation maps long and short flashes to specific failures. Examples from that table:
- 0 long, 3 short: generic failure to boot.
- 0 long, 7 short: kernel image not found.
- 2 long, 2 short: failed to read from partition.
- 4 long, 6 short and 4 long, 7 short: power failure, types A and B.
Use the official table for the full set and for your model, rather than working from memory. Count the flashes slowly and note the pattern before you power-cycle again.
Read the HDMI boot diagnostics on Raspberry Pi 4 and later flagship models
On Raspberry Pi 4 and later flagship boards, bootloader diagnostics can appear on an HDMI display. Raspberry Pi’s documentation says this screen can show when the bootloader cannot boot from any boot media or network. Named causes include absent or defective media and incorrect network boot parameters. A diagnostic screen is more useful than a generic black screen, so connect a monitor before you assume the board is dead.
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
Check power before anything else
Undervoltage is one of the most common reasons a project that worked last month fails after a move, a battery swap, or a new USB peripheral. Raspberry Pi publishes recommended power modes per model. Do not substitute a supply that is merely “5V” without checking the current rating.
| Board family | Recommended power mode (Raspberry Pi table) |
|---|---|
| Raspberry Pi 5 | 5V/5A |
| Raspberry Pi 4 Model B | 5V/3A |
| Raspberry Pi 3 and earlier families | 5V/2.5A |
These are the ratings listed in Raspberry Pi’s documentation as reviewed for this guide, which carries no publication date. Confirm them against the current page for your board before you buy a replacement supply.
Attached hardware counts toward the total. Disks and SSDs can draw more current than a bare board, and several drives together can push a marginal supply into a brownout. If the LED shows a power-failure pattern, test with a known-good supply rated for your model before you touch the card.
Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
Decide whether to keep or replace the boot card
The boot medium is where project data most often gets lost, so this step comes before any write operation. The decision is simple: if the card still contains the only copy of your project, preserve it first.
Preserve the existing card
- Power the Pi down and remove the card with the board unpowered.
- Read the card on a computer with a card reader, and copy the whole card to a file or a second drive. A disk image is safer than copying files one by one, because it keeps the boot partition intact.
- Check that the copy opens and that your source code, data, and configuration files are present.
- Only after the copy is verified, decide whether to repair the original card or write a new one.
Writing a recovery image to a card erases what was on it. Do not skip the copy.
Prepare a fresh card for Raspberry Pi OS
If the card is absent, defective, or has no bootable image, write a fresh one with Raspberry Pi Imager. Raspberry Pi’s storage guidance is at least 32GB for Raspberry Pi OS and at least 16GB for Raspberry Pi OS Lite. A 32GB microSD card is the simplest choice that fits the full desktop image. Supported models can also boot from other media, but microSD is the most common route.
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
- Install Raspberry Pi Imager on a computer and insert the new card.
- Choose the board and the operating system you need.
- Choose the storage device. Double-check it, because the selected device will be overwritten.
- Write the image and wait for verification to finish before you move the card to the Pi.
Raspberry Pi Imager writes the image to the chosen storage device, so the selected card is erased. Re-check the device name before you confirm.
Confirm the board supports your boot route
A new card will not help if the board cannot boot from it. Verify the board’s supported boot media in the official documentation before you assume a card or a USB drive is the problem.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTry USB boot only with its constraints in mind
USB mass-storage boot is supported on specific device families, and older models have known problems with some USB devices. If you plan to move the operating system to a USB drive or SSD, check three things: that your board supports USB boot, that the boot configuration is set up for it, and that the drive’s power draw is covered by your supply. Do not assume a drive that works on a laptop will work on every Pi.
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)
Reflash the bootloader only when the model and symptoms justify it
Bootloader recovery is model-specific. Raspberry Pi documents EEPROM bootloaders on flagship models from the Raspberry Pi 4 Model B onward, on Compute Modules from CM4 onward, and on keyboard models from Pi 400 onward. Its Imager-based recovery sequence applies to those families. It is not a general fix for older boards.
Consider it only after the power and boot-media checks have failed to explain the symptoms, and only if your model is in one of those families. Follow the current model-specific procedure from Raspberry Pi’s documentation, and do not improvise steps from older forum posts.
Compare recovery options before you commit
| Action | Board support | Data risk | Power compatibility | Time and complexity |
|---|---|---|---|---|
| Read LED pattern or HDMI diagnostics | LED on all models; HDMI diagnostics on Raspberry Pi 4 and later flagship models | None; read-only observation | Confirms whether power is a suspect | Minutes |
| Check and replace power supply | Requires the model’s recommended mode (see table above) | None | Core check | Minutes, plus purchase time if needed |
| Copy existing card | Any model | Preserves data; reads the card | Not applicable | Depends on card size |
| Write fresh Raspberry Pi OS card | Any model that boots from the chosen medium | Erases the selected card | Not applicable | Tens of minutes for a full write and verify |
| USB boot | Specific device families only; older models have known USB issues | Depends on whether the drive is new or already holds project data | Drives can need extra current | Moderate; requires configuration |
| Bootloader (EEPROM) reflash | Flagship models from Raspberry Pi 4 Model B, Compute Modules from CM4, keyboard models from Pi 400 | Changes firmware; keep the card safe | Stable power is essential during the update | Most involved; last resort |
Work down the table in order. Each step that reads or preserves data should come before a step that overwrites it.
Free tools Windows power users keep installed
One-click scans. No signup required.
A hackathon fallback that gets something running
If the original project will not come back before the deadline, aim for a smaller goal. This is editorial advice, not an official Raspberry Pi procedure, and it has not been tested as a recovery method.
- Keep the original card untouched in a labelled, verified copy.
- Bring up a minimal, known-good operating system on a separate card, such as Raspberry Pi OS Lite on a 16GB card or larger.
- Demonstrate one essential function of the project, such as reading a sensor or driving the main output.
- Restore optional features only after that core function works on the new setup.
Reviving the original build is worth pursuing after the demo is safe, because a working fallback protects your team if the original hardware cannot be recovered.
What this guide does not cover
This guide does not identify your board, operating system, project, or event rules, so it cannot give exact pin, firmware, or storage settings for your setup. Hackathon-specific requirements, judging criteria, and schedules are outside its scope. Raspberry Pi’s documentation can change, especially model support, power recommendations, and Imager steps, so check the current official pages for your board before you rely on a figure or procedure.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
