Rev Pi Core S Boot Mode/RPI Boot Issues

[ShiboW]

Hi all,

My RevPi one day had issues booting. Per the boot sequence, it was unable to detect the emmc and jumped to next boot mode (SD Card), resulting in inability to boot.

I have been trying to connect through rpiboot with the following response:

Code: Select all

"C:\Program Files\Raspberry Pi\rpiboot.exe" -d "C:\Program Files\Raspberry Pi\mass-storage-gadget64"
RPIBOOT: build-date 2026/01/22 pkg-version local 7f7e6eb2

Please fit the EMMC_DISABLE / nRPIBOOT jumper before connecting the power and USB cables to the target device.
If the device fails to connect then please see https://rpltd.co/rpiboot for debugging tips.

Loading: C:\Program Files\Raspberry Pi\mass-storage-gadget64/bootfiles.bin
Using C:\Program Files\Raspberry Pi\mass-storage-gadget64/bootfiles.bin
Waiting for BCM2835/6/7/2711/2712...

Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711/2712...

Second stage boot server
File read: mcb.bin
File read: memsys00.bin
File read: memsys01.bin
File read: memsys02.bin
File read: memsys03.bin
File read: memsys04.bin
File read: memsys05.bin
File read: memsys06.bin
File read: memsys07.bin
File read: memsys08.bin
File read: bootmain
Loading: C:\Program Files\Raspberry Pi\mass-storage-gadget64/config.txt
File read: config.txt
Loading: C:\Program Files\Raspberry Pi\mass-storage-gadget64/boot.img
File read: boot.img
Second stage boot server done

To this extent the handshake from rpiboot detects the device, but it is unable to read it I get a windows pop-up error that "The USB device was not able to connect".

I am wondering where I should be troubleshooting. Whether it is an issue with the boot mode, or something from rpiboot not being read the emmc.

Thank you in advance.

Shibo

[RamiGspo]

Hi Shibo,

The rpiboot output you shared looks good... it confirms the device is being detected and the second-stage boot is completing successfully. The Windows pop-up error ("USB device was not able to connect") sometimes appears at that stage and doesn't necessarily mean something went wrong.

Before going further, it would help to know what you're trying to do next: are you looking to reflash the RevPi, or do you need to recover data from the eMMC first?

If you want to reflash, you can find the full process documented here: https://revolutionpi.com/en/knowledge/r ... ling-image.
Once rpiboot has completed, you can use **Raspberry Pi Imager** to write a fresh image directly to the eMMC. I recommend our latest release, **RevPi Bookworm 64-Bit 11/2025**.

[ShiboW]

Hi Shibo,

The rpiboot output you shared looks good... it confirms the device is being detected and the second-stage boot is completing successfully. The Windows pop-up error ("USB device was not able to connect") sometimes appears at that stage and doesn't necessarily mean something went wrong.

Before going further, it would help to know what you're trying to do next: are you looking to reflash the RevPi, or do you need to recover data from the eMMC first?

If you want to reflash, you can find the full process documented here: https://revolutionpi.com/en/knowledge/r ... ling-image.
Once rpiboot has completed, you can use **Raspberry Pi Imager** to write a fresh image directly to the eMMC. I recommend our latest release, **RevPi Bookworm 64-Bit 11/2025**.

Hi. Thanks you for your reply. I am trying to first recover certain data from eMMC before re-flashing.

My device appears when running lsdblk, however and further attempts to mount it result in no partitions being read on the device.

Thanks in advance!