The RA80 firmware has an additional check in the setSysTime function and therefore the vulnerability I found will only work on RA82.
You just need to put the device into mesh mode in advance (you need a second router).
Guys, I have flash dumps (otp stripped) of both devices (RA82 and RA80) if someone wants to have a look... Too busy to look into it, but can try stuff if you need.
Those are dumps of original flash…, you need to use a programmer to read/write stuff directly to spi-nand ICs. You can sure enable console and change things by manipulating those (both in bootloader and later on), just make sure to recalculate and add crc checksums after your changes and use you original mac addresses and radio calibration data.
Here's the RA82 Global version firmware version 1.4.21
I looked at the logs generated during the attempt of firmware upgrade and I found the link to the file so I was able to download the firmware with no issues.
I'm putting together all the information I can about AX3000, but I can't boot automatically at the moment, just manually.
Has somebody else had problems with the Xiaomi uboot, more specifically "bootmiwifi". I have built and flashed a qsdk version with kernel 5.4, I can boot it manually with u-boot, but it will refuse to boot it automatically because it's missing a secure boot signature over the kernel and rootfs. I have even set a bootcmd, but that seems to be ignored. Anybody managed to get over this error?
The device I'm working on is a RA82 which seems to have secure boot fuse burned, which is something new for Xiaomi I guess.
Seem that you need to disable secureboot in any place like a UEFI, i'm not a master of routeros hardware. However it's a good thing you got root access.
The secure boot configuration is enforced through some sort of e-fuse, which means that once burned it can't be changed back. Fortunately secure boot as implemented by Xiaomi is not 100%, It only covers their own bootmiwifi command, so it's possible to boot your own system in uboot if you have serial enabled, but I can't figure out how to do this automatically as uboot ignores bootcmd if set -> I can only boot own system manually.
How you managed to get the ttl working ? Mine is R80 connected ttl but noting come out, not sure because of broadcom need to wait for specified seconds before plugin the ttl ?