New HyperOS 2.0 fastboot installer fails for CN HyperOS 1.0

[Syncopated]

I observed that the xiaomi.eu HyperOS 2.0 fastboot clean installer (linux_install_and_format_data.sh from xiaomi.eu_AURORA_OS2.0.8.0.VNACNXM_15.zip) does not work when the phone is a Xiaomi 14 Ultra with official HyperOS 1.0 CN ROM. The detailed observations are as follows.

Initially, my phone was running official CN HyperOS 1.0 ROM. I tried to flash the xiaomi.eu HyperOS 2.0 fastboot ROM by running linux_install_and_format_data.sh in fastboot mode. At the end of the script when it rebooted, the normal boot screen flashed very briefly before the fastboot screen came back. I tried flashing again and the same thing happened, so the ROM was not working.

Through a hunch, I flashed the official CN HyperOS 2.0 ROM and debricked the phone; it booted normally. After that, I tried to flash the xiaomi.eu ROM again and it worked.

Thus, I suspect that the xiaomi.eu ROM fails when the original ROM is an official CN ROM with HyperOS 1.0. I speculate that partitions are not being prepared properly in linux_install_and_format_data.sh for the case where the phone was originally HyperOS 1.0.

 

[Igor Eisberg]

There's nothing special to prepare regardless of Android/HyperOS version.
I don't have the device to even try to reproduce what happened in your case.

 

[Syncopated]

There's nothing special to prepare regardless of Android/HyperOS version.
I don't have the device to even try to reproduce what happened in your case.

Is there anything simple I can do to assist with investigation using my own device? I can use adb & fastboot, but I don't know if you would need anything more complicated.

 

[Igor Eisberg]

Is there anything simple I can do to assist with investigation using my own device? I can use adb & fastboot, but I don't know if you would need anything more complicated.

There is no ADB during bootloader stage, and there is no logging with fastboot at all.
As far as we know from previous experience, the boot failure was caused because we don't include the stock recovery.img partition.
Android 14's recovery partition was likely rejected by the Android 15 bootloader.
We might have to keep stock recovery.img from now on, at least for more recent devices.