[2.3.1] FDE/Naked fails to boot NVME until reflashed with usboot recovery5 (Pi 5 flagship, Pi NVME HAT+)

[daniel-ambient]

FYI: From branch dev/tdewey/2.3.1, FDE and Naked provisioning results in a Pi 5 flagship that does not boot (LED stays red). Reflashing the EEPROM with usboot recover5, with boot.conf set to boot from NVME first results in a correctly booting device.

[tdewey-rpi]

Your report sounds like you had a bad BOOT_ORDER configured, or you booted an old bootloader.

The default boot order in rpi-sb-provisioner is 0xf2461, which translates to:

1. SD
2. NVMe
3. USB Mass Storage
4. Network Boot
   f. Restart

So in your described case, if you were using the default rpi-sb-provisioner bootloader configuration, your device will have attempted to boot from SD, failed, and then moved to NVMe.

This diagnosis is supported by your resolution step - re-writing your bootloader and configuration configuration got you operational again.

Can you confirm which firmware you wrote?

[daniel-ambient]

I write 2026-05-26, and also tried 2026-06-17. I also tried fixing the bootloader and then re-provisioning. The re-provisioning resulted in a not-booting Pi when previously the Pi was booting. It did not show any messages on the screen and the LED stayed red. Could it be not just bad boot order, but somehow a bad bootloader? I have not yet had a chance to hook up serial to check if there are any messages at all.

However, I just tried a moment ago, with a debug probe attached the serial and it booted properly. I will try again without the serial later today to see if the problem has resolved itself.

EDIT: I realize for this most recent test I was not writing the EEPROM (because of the issue, I had set that to persistent). Testing again...

[daniel-ambient]

With the Pi debug probe on the Pi JST serial port, no messages appear on the serial, either, if I do write the EEPROM. Using usbboot repo's rpiboot to restore the bootloader gets it working again. This is with the 2026-05-26 firmware.

[daniel-ambient]

I am sorry to report that with all dependencies updated, and the 2.3.1 tag on main the problem is still present.

EDIT: if there are logs that would help, I am happy to attach them.

EDIT: 2026-06-30T18:08:31.904Z + RPI_DEVICE_FIRMWARE_FILE=/usr/lib/firmware/raspberrypi/bootloader-2712/default/pieeprom-2026-05-26.bin