A Raspberry Pi that will not boot after flashing is frustrating because the symptom tells you almost nothing on its own. A blank screen can mean a bad flash, a bad card, a weak power supply, a display problem, or a bootloader issue, and guessing at random wastes hours. The fastest fix is to work through the causes in order, from the most common and easiest to test to the rarer ones, and to change only one thing at a time.
This checklist is for anyone who has just flashed a card with Win32 Disk Imager, or any other tool, and now gets no boot, a rainbow screen that never moves, a kernel panic, or repeated reboots. It assumes you have a Windows computer for reflashing, a spare card if possible, and the official power supply or a known-good equivalent. Each step tells you what to check, what the result means, and what to try next.
Before you start, remember what a successful flash does and does not prove. Win32 Disk Imager reporting success proves the image was written to the card, not that the card is good, the image matches your Pi model, or the Pi is receiving enough power.
Before you start
- Do not reflash the same card repeatedly without changing anything else. If three reflashes give the same result, the problem is probably not the flash step.
- Write down what you see: LED behaviour, screen contents, and any error text. Those details are what separate a power problem from a card problem.
- Keep the original .img file. If you delete it and the download was the problem, you will have to download it again before you can test anything.
Work through the checklist in order, and stop as soon as the Pi boots. The order matters because power and card seating are faster to test than a full re-download and reflash, and because a display problem can look exactly like a boot failure. If you skip ahead to reflashing, you may fix nothing and conclude, wrongly, that the Pi itself is broken.
Step by step
1. Check power first
Use the official power supply for your Pi model, or a supply that meets its voltage and current requirements, and plug it directly into a wall outlet rather than a computer USB port or a cheap hub. A Pi that browns out under load can show a rainbow screen, reboot in a loop, or corrupt its card, and the low-voltage warning icon, a lightning bolt on newer models, is a direct sign of this problem. If you have another supply, swap it before you touch the card.
2. Reseat the card and check the slot
Power off, remove the microSD card, inspect it for dirt or damage, reinsert it firmly until it clicks or seats fully, and power on again. MicroSD slots are a common failure point, especially on Pis that have been handled often. If the card feels loose or the Pi only boots when you press the card, try a different card, because a worn slot or a slightly thin card can cause intermittent contact that looks like a software fault.
3. Try a different card with the same image
Flash the same .img file onto a different, known-good card and test it. If the second card boots, the first card is the problem, even if it worked in a camera or a phone. If the second card also fails, the image, the Pi, or the power supply is the problem, and you have saved yourself from buying cards at random.
4. Reflash carefully and verify the download
Re-download or re-decompress the image, check its size against the download page, and reflash with Win32 Disk Imager as administrator, double-checking the drive letter. A truncated download or a failed decompression can produce an image that writes without error but never boots. If Win32 Disk Imager offers a verify pass, run it, because a verify failure points directly at the card or reader rather than at the Pi.
5. Check the display and HDMI setup
Try a different HDMI cable, a different display or television, and, on models with two HDMI ports, the other port. If the green activity LED flickers normally but the screen stays blank, the Pi may actually be booting and the problem may be display detection, which is far easier to fix than a dead board.
6. Read the LEDs and any error text
Watch the LEDs during power-on. A steady red power LED with no green activity usually means the Pi cannot read the bootloader from the card. Green flicker followed by an error on screen, such as a kernel panic, means the bootloader ran but the system failed later, which points at the image or the card contents rather than at power or seating.
7. Consider the bootloader and model match
Confirm the image supports your Pi model. An image built for an older Pi may not boot on a Pi 5, and a very old image may lack the firmware a newer board needs. If you are using a Pi 4 or Pi 5 and an old image, download the current Raspberry Pi OS release and test it. For persistent bootloader problems, the Raspberry Pi documentation covers bootloader recovery, but that step is only worth taking after power, card, image, and display have been ruled out.
Frequently asked questions
My Pi shows a rainbow screen and stops. What does that mean?
A stuck rainbow screen usually means the Pi cannot proceed past the bootloader, often because of power, card seating, or a card the Pi cannot read. Work through power, reseating, and a different card before reflashing.
Win32 Disk Imager said the write succeeded, so why will the Pi not boot?
A successful write only proves the image was copied to the card. It does not prove the card is good, the image matches your Pi model, or the Pi has enough power. Test those separately.
Should I reflash first when a Pi will not boot?
No. Check power, reseat the card, and try a different display first, because those tests are faster and often reveal the cause. Reflash only after the quick checks, or with a different card.
For the full set of guides, see the Tutorials hub, and get the program from the download page. Related guides include: flash raspberry pi os win32 disk imager, how to use win32 disk imager, expand filesystem after flashing — each one covers one job in the same plain style as this guide.