Odroid XU4 flash related boot issue

[nang]

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

• DietPi version | 9.13
• Distro version | N/A
• Kernel version | N/A
• Architecture | Armv7, Armv8
• SBC model | Odroid XU4 & Odroid N2
• Power supply used | Official Hardkernel power supply
• SD card used | Hardkernel official eMMC module

Setup

I have 3 Odroid boards, two are XU4 and the other one is N2. I also also have 3 128G eMMC module (Let’s say eMMC-1, eMMC-2 and eMMC-3). Here is the situation

1. eMMC-1, eMMC-2 and eMMC-3 can all be recognized by Windows and can be flashed by balenaEtcher or Rufus
2. After flashing DietPi_OdroidN2-ARMv8-Bookworm.img.xz to eMMC-1, eMMC-2 and eMMC-3, my Odroid N2 boards can boot with all three eMMCs → So I think all eMMCs are functional
3. Then I leave eMMC-1 for Odroid N2. And flashed DietPi_OdroidXU4-ARMv7-Bookworm.img.xz into eMMC-2 and eMMC-3.
   • eMMC-2 can boot both Odroid XU4
   • Neither Odroid XU4 can be booted by eMMC-3 → no blue light

I’ve tried to flash eMMC-3 for multiple times with balenaEtcher or Rufus, but the behavior is very consistent. Comparing to eMMC-2, I did once deleted its partitions using Windows Disk Management. My questions:

1. Did I somehow damage the boot partition and it can never be recovered? Any help on how to recover/flash is appreciated.
2. I tried to use command dd to replicate all 3 partitions (mmcblk0, mmcblk0boot0, mmcblk0boot) of eMMC-2 to eMMC-3, but did not work either (first time doing that might have wrong operations)

Thank you again for this amazing piece of operating system!

[Jappe]

So all 3 eMMC modules are identical?

[nang]

Yes, bought in the same batch. I think I somehow messed up with the partitions but I’m not sure how

[nang]

TL;DR

I did corrupted the hidden bootloader partition on eMMC modules by doing manual volume deletion on Windows.

The solution is here, basically recover eMMC bootloader: https://wiki.odroid.com/odroid_go_ultra/getting_started/recovery_emmc