Skip to content

Event

RDK X5 self-compiled image flashing fails to boot: GPT partition table corruption troubleshooting and recovery

1 reports · 1 sources

After flashing the self-compiled emmc_disk.img on the RDK X5, boot fails; fastboot reports Writing 'boot' FAILED (remote: 'cannot find partition'), and boot partition size: 0. Guazai, posting on the D-Robotics Developer Community, points out that the cause is the board being unable to read a valid GPT partition table, and provides troubleshooting and recovery steps. Recovery key points: the image should be flashed in its entirety starting from address 0 (including the partition table); do not flash boot separately. If the board's current system is already incomplete, do not select pure Fastboot in download mode (it requires a non-empty board and an image that can boot normally); instead use dfu_fastboot or xmodem_fastboot blank-board flashing modes. When flashing eMMC, it is recommended to remove the SD card to avoid U-Boot entering the UMS process and interfering with flashing.

Report timeline

  1. RDK X5 fails to boot after flashing a self-compiled image: troubleshooting and recovery for a corrupted partition table

    After flashing a self-compiled emmc_disk.img to the RDK X5, boot fails, and fastboot reports Writing 'boot' FAILED (remote: 'cannot find partition'); the cause is that the board cannot read a valid GPT partition table.

    D-Robotics Developer Community ·

Related topics