Hello all..
So, I'll try a different way. step by step.
Is there any advantage or disadvantage to keeping the U-boot on a RD03?
thanks
Do you happen to remember what they were complaining about?
I encountered a new problem, I noticed that the speed of wi fi does not correspond to the tariff, it was tearing in half.
I decided to switch the channel on 5ghz to other frequencies (channels 56-60). At some point after another switch it just stopped starting.
I have a backup of the initial settings, after I pour it, the network begins to see and connect to it, but as soon as I change the channel falls off.
If you run the scanner of networks around 5Ghz, it sees networks around and when you go to the wifi interface it shows the access point on the interface enabled, but devices do not see it.
Any guides or docs to use MiWifiRepairTool?
I have a r23 emst chip with 1.0.31 firmware
Do i have to upgrade it first to newer version or not
is tutorial page all firmware versions have a link to it's stock firmware but my version
why is that?
In the top box, you select the native firmware of Xiaomi AX3000T.
Press the button on the bottom right.
In the next menu you select your network interface where you have the router connected (in advance you write to this interface a static address 192.168.31.100 and a standard mask).
Press the button at the bottom right.
Then disconnect the power, press the reset button and reconnect the power by holding the reset button for about 15 seconds until it blinks orange several times (release the reset button). The program should start pouring the firmware.
1 Like
Which channel and country? Most countries have channels 52-144 as DFS channels, those require the device to scan for conflicting devices such as radar before the channel is made available. This can take several minutes.
Thanks, what is a trusted source to download the tool?
No, all versions can exploit a web API to do RCE. Just run https://github.com/openwrt-xiaomi/xmir-patcher and it will detect the appropriate API to exploit.
1 Like
Thank you , after writing , I set the country and it corrected the frequency )
Well, it's a closed source chinese proprietary software, I don't think you can use the word "trusted". But you can download it from official source here: http://bigota.miwifi.com/xiaoqiang/tools/MIWIFIRepairTool.x86.zip
Simple instructions with screenshots from another Xiaomi router can be found here.
Links to the stock firmware can be found on the Wiki (see "Stock Firmware URL").
because Xiaomi never published the 1.0.31 firmware.
Someone needs to submit a PR on GitHub and show that the patch has been tested. This needed to happen before 23.05.5 was branched and the submitter would have need to push for the back port.
That didnât occur = not included in 23.05.5.
The patch was accepted into master.
If you absolutely need to know why the submitter didnât work on a back port look up the commit for the winbond chip and contact them. The core openwrt team wonât know the submitterâs thought process
1 Like
The author of the patch is a core developer, @robimarko
I won't use github, but if there was actually any work needed, I would be happy to provide it for anyone wanting to send a PR, but here is the thing, there is nothing to do, other than maybe fix the diff offsets (which is just a matter of copying his patch into the older winbond.c and generating a new diff patch).
The patch itself is very small and very simple, and it follows the usual template for SPI NAND support in the Linux kernel.
Like I said, I think there are enough of us that can vouch for the stability of the patch, myself included.
Or we can just ignore it, and keep having people soft brick their devices when we already have a working patch that was submitted almost two months ago.
The patch was commited 12/August, so it is acceptable that it was not in 23.05.5, but the fact that it is still not backported to openwrt-23.05 feels like none of the core developers are aware of this thread and no one else is interested in doing a PR (myself included).
I just tagged him with my mention, maybe this will get his attention? If it does, know that I've such a device and I can be of assistance, if needed.
4 Likes
All development is done against Main. What is needed is the maintainer of the AX3000T to request the backport
If you read above in the thread I believe this was discussed and the maintainer was not interested as they donât have the impacted device and/or only work with main anyway
2 Likes
Is there any uboot and openwrt for AX3000T that supports AN8855 switch?
I've heard and installed immortalwrt but couldn't find uboot.
1 Like
ImmortalWrt doesn't support it either.
From the ToH: " OpenWrt U-Boot provides faster boot loading and more space: 75Mb (with recovery) or 85Mb (without recovery)."
Just received my RD23 INT AX3000T from Amazon Germany.
- I can see that it is the ESMT NAND (see OpenWrt support for Xiaomi AX3000T - #790 by andi-at-1)
- Firmware stock version 1.0.31
I could easily get ssh access:
- Save sh file https://openwrt.org/inbox/toh/xiaomi/ax3000t#flash_instructions
- Make it executable (sudo chmod +x xiaomi.sh)
- Copy stok ID from webinterface URL: http://192.168.31.1/cgi-bin/luci/;stok=**3xxx3**/web/home#router
- execute the script with stok ID: ./xiaomi.ssh 3xxx3
- connect to 192.168.31.1 by ssh with root as user
How do i get the NAND info without looking at the pysical router?
I did not get a result with ssh on the router using dmesg | grep NAND
Thank you. Next step i will flash Openwrt.
Which version do you recommend beside Openwrt? X-Wrt, oder ImmortalWrt? Stable Wifi is my priority. Thank you!
//edit:
After Reboot i get it:
root@XiaoQiang:~# dmesg | grep NAND
[ 0.074335] spi-nand spi0.0: GigaDevice SPI NAND was found.
1 Like
`dmesg | grep -i esmt does not show anything for me, just:
dmesg | grep NAND
[ 0.074335] spi-nand spi0.0: GigaDevice SPI NAND was found.