Very bad decision. And you didn't see the full scale of the problem.
This issue is not limited to one device.
There is already a device from Asus on the market that has the bootloader version 2022.10 installed (the specified patch is already included):
Proof: ASUS AX-1800S V2 (not RT-AX54) cant't flash with bootloader ver 2.0.0
I have already compiled OpenWrt 23.05.4 for RT-AX57M, but on the snapshot I will encounter the same problem.
And every day there will be more and more devices in which Uboot is installed with the specified fix (commit 36fee2f) and the presence of a common UBI partition.
At the moment, the issue is related to the following devices:
ASUS RT-AX52
ASUS RT-AX57M
ASUS RT-AX59U
ASUS TUF-AX4200
ASUS TUF-AX6000
The issue reported will likely affect the following devices:
ASUS RT-AX89X
OpenWrt One (of course there is a custom bootloader here)
mercusys,mr90x-v1
tplink,re6000xd
cellc,rtl30vw
teltonika,rutx10
teltonika,rutx50
zte,mf18a
zte,mf282plus
zte,mf286d
zte,mf287
zte,mf287plus
zte,mf287pro
zte,mf289f
platform bcm4908
There is a similar problem on the qcom platform (ipq80xx) and it is also solved by deceiving the logic of Uboot.
Example:
And here all hope is that the logic of the Uboot operation will remain the same (and there is a flaw in the logic).
Personally, I really don’t like such decisions (which are based on hope).