Yeah, about that... I'm changing the layout YET AGAAAAAAIN.
So don't sysupgrade from new images you build, if you're following my branch.
I really need to stop waffling between partition layouts. If you're on an older image built after I push yet another indecisive partition/image change (4mb kernel and a ubifs straight after), you'll probably have to mtd write the factory.bin in order not to soft-brick. Or better yet just go back to stock and start from the beginning.
The problem being that depending on that old beta image is a bit , since Xiaomi could in theory go around waving the takedowns, in true hypocritical manner.
Bit of an oopsie for that image to leak though. They probably shouldn't have signed it with the same key, but then they wouldn't be able to upgrade their test users to full version.
Feels bad for the AX3200 buyers though. I don't think anyone would be looking too hard for a way in on their images anymore.
Anyway, how do we feel about these installation instructions for the AX6S? I avoided linking directly to the whole password calculator and leaked image though, as it would be pretty hard to guarantee keeping those both up somewhere.
I did however do a run-through from the stock image with these instructions and it worked, so it should be the last time... Probably...
Installation:
1. Flash stock Xiaomi "closed beta" image labelled
'miwifi_rb03_firmware_stable_1.2.7_closedbeta.bin'.
(MD5: 5eedf1632ac97bb5a6bb072c08603ed7)
2. Calculate telnet password from serial number and login
3. Execute commands to prepare device
nvram set ssh_en=1
nvram set uart_en=1
nvram set boot_wait=on
nvram set flag_boot_success=1
nvram set flag_try_sys1_failed=0
nvram set flag_try_sys2_failed=0
nvram commit
4. Download and flash image
On computer:
python -m http.server
On router:
cd /tmp
wget http://<IP>:8000/factory.bin
mtd -r write factory.bin firmware
Device should reboot at this point.
It's probably a bit presumptive with only putting the python3 http.server in there, but on the other hand it is 2022...
You can set it via nvram set "boot_fw1=run boot_rd_img;bootm" && nvram commit
or via uboot
That was was the piece I was concerned about, the ability to set it from OpenWRT. I didn't want to get into a situation where I needed to crack the case and go back to UART to change something in uboot.
Feels bad for the AX3200 buyers though. I don't think anyone would be looking too hard for a way in on their images anymore.
It makes me wonder if the availability of the test was deliberate. Keeping people from looking too hard sounds like a great way to keep known issues from being found. I'm thinking of the ~2013 backdoor debacle with Cisco Linksys D-Link + + +.
Hmm. I've just flashed latest @namidairo ax6s branch (mtd factory.bin via previous OpenWRT firmware).
It looks like configuration is persistent now, I did several config changes and reboots.
Could you describe the patch in detail? So others can easily write and apply similar patch on some third party sources like lede for extra plugins needed.
Respect.
That means the Wifi speed is limited by the 1 Gbits uplink. Probably it won't help to aggregate multiple links since the internal switch is 1 Gbits only, right?
I have still the 2 images version. I would like to know if writing single image will corrupt my router.
also, what is the procedure to flash stock firmware?
@mikeeq, it did not work for me. I thought it was just me because I've been all over the map with images and builds in the pat 24 hours.
I went back to using @panton GD5F1GQ5xExxG-sysupgrade image.
@cenzor, I have the 2 image RB03. After a lot exploration & attempts trying different images, sequences, partitions, and recovery to stock, I would say it is very hard to permanently corrupt your router by following the most common instructions floating around. Recovery always seems possible but there is no such thing as zero risk. That being said, I would say UART access is a must. A change is required to boot from the first image, not the second (which is default). Recovery does not appear to change this back when reverting to stock. (Meaning if your first image/openwrt is bad, recovery will still not work as it will never boot into the recovered xiaomi image.) Having UART access solves this by allowing you to boot the right image and/or change the boot settings back to original.
, since Xiaomi could in theory go around waving the takedowns, in true hypocritical manner.
