Extract the files from the rpi-boot-eeprom-recovery zip file into a temporary folder. These files will be recovery.bin, pieeprom.bin and README.txt.
Now put those 3 files directly on the root of your blank FAT32 formatted SD card. Your recovery card is now prepped and ready!
Before powering up your device make sure that all USB devices are removed. Even keyboards have been known to cause issues so make sure absolutely everything is unplugged!
Now insert the SD card into the Pi and connect the power.
If the bootloader recovery is successful the green activity light will start blinking rapidly continuously (forever). In this case you have successfully recovered your bootloader! You may now insert a normal fully imaged SD card and it will boot normally again.
If anything other than a continuous rapidly blinking green light happens the recovery was not successful.
If Recovery Doesn’t Work
There is a known (and strange) issue with Raspberry Pi 4’s and 32 GB SD cards where the Pi will abort the boot. If this might apply to you then read this post.
Make sure you created your SD card correctly. A common pitfall is using cards above 32 GB and formatting them with ex-FAT instead of regular FAT/FAT32.
Make sure *all* USB devices are unplugged from the Pi
Try a different SD card if you have one available. SD cards do go bad all the time. If there’s any doubt here check out my Raspberry Pi storage benchmarks page to see the highest performing SD cards (you definitely want an A1 rated one).
Check your power cord. Make sure you are using a high quality USB-C power cord that is compatible with the Pi. Even if it was working before I have had several old Pi power supplies that worked for years die on me. If there’s any doubt grab a known reliable one like the Canakit USB-C Raspberry Pi 4 Power Supply
If you’ve gone through all the steps and are positive it’s not one of the above “gotcha” issues then it’s time to go deeper. You need to observe your Pi’s exact behavior when you plug it in (what the lights are doing). Here is a table of different blink patterns and what they mean:
Raspberry Pi 4 LED blink warning table
If your Pi’s LED behavior matches any of these codes then we now have much more to go on to diagnose why your Pi won’t boot. Some of them are very obvious but they’re all worth a quick web search once you have matched it to a code.
If your Pi’s behavior does not match one of these codes head to the official sticky post on the Raspberry Pi forums and scroll to the very bottom (post #4 specifically for Raspberry Pi). This tracks ongoing boot issues with the Pi 4 that may affect your Pi and a whole bunch of things to try. If you get through that post go all the way up to post #1 and start going down the list.
要将Raspberry Pi新安装的Raspberry Pi烧录到你的USB盘上，请使用Raspberry Pi Imager，就像平时设置Raspberry Pi时一样。
To remount the root filesystem as read/write, run the following command
#To remount the root filesystem as read/write, run the following command
#
sudo mount -o remount,rw /
#检查fstab
/etc/fstab
proc /proc proc defaults 0 0
PARTUUID=35786a18-01 /boot vfat defaults 0 2
PARTUUID=35786a18-02 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
#
#在里面更改
sudo nano /boot/cmdline.txt
#We are going to add the following entry into the very front of cmdline.txt:
#xxxx在lsusb中查，下面加在cmdline.txt最前面
usb-storage.quirks=XXXX:XXXX:u
#usb-storage.quirks=0781:5588:u console=serial0,115200 console=tty1 root=PARTUUID=35786a18-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
