My Traffic Statistic are all completely wrong like
vnstat -l -i wan or br-lan
and doing a Speedtest doesnt show up at all just a few kbps.
Is that because of HW-Offloading ?
When i do a Speedtest with Iperf3 directly from OpenWRT i see the Traffic on the wan interface.
If i do it from lan i cant see no matter which interface is choose wan/br-lan/Radios.
I bought a new memory because the old one stopped responding to the programmer during the recovery process, I'm looking for a full backup of the firmware with all the partitions.
I have a backup of the bdata bl2 factory fip kf nvram ubi partitions, maybe I can somehow collect them into one binary file?
Now my router does not respond at all, I tried to flash the uboot bootloader, but I have some unreadable garbage in an endless stream in my uart
I noticed that the Pull Request for adding support for the Winbound W25N01KV chip has been committed to the OpenWrt repository and is ready to be processed. I hope it will be merged into the Release 23.05.x branch soon.
@andi-at-1, based on your clarification here, does this mean that you tested and confirmed the patch for the Winbound W25N01KV chip in the regular OpenWrt Snapshot version? (So, support for the Winbound chip in the AX3000T router is now included in each new OpenWrt Snapshot build?).
As it is a "sysupgrade" file, it will have already installed LUCI webui, won't it?
About Change to OpenWrt U-Boot. I have read all post here, I think that the diferent with "default boot" is about the less space it needs.
Default boot and u-boot both have recovery mode (default boot with TFTP, isn' it)
It is a bit risky to change default boot. For newbies, better to let it as it is.
If I don't change the default boot, I can recover my devide (back to stock) with "Go Back to stock from default layout Openwrt: ubiformat /dev/mtd8 -y -f /tmp/ubi.bin" or with MIWIFIRepairTool.x86
Could you help me with these almost yes/no/ok/better/... questions?
Step 0: check what flash chip you have, otherwise it will brick. If you are not sure take the immortalwrt build (mabe tomorrow snapshot will also work)
The firmware selector will give you the right named files like you see in the howto
Stock bootloader needs more time to boot and won't give you any infos over serial. The good side is that you can essily recover any wrong firmware with the repairtools. Tftp on openwrt bootloader is a bit of a pita for me...
@alexq I think the winbond chip patch was committed today, i will check if snapshot work tomorrow and post if so
Thanks a lot for your answer, yes I have already checked my flash chip. It is ESMT.
So after reading you...
Ok, this is the file (rename or change command)
Ok, this is the file (rename or change command)
pending As it is a "sysupgrade" file, it will have already installed LUCI webui, won't it?
Ok, also speed and more info over serial
you dont like it, but i think that you are saying "yes" to this anser, aren't you?
pending what is your opinion?
pending 1. If I don't change the default boot, I can recover my devide (back to stock) with "Go Back to stock from default layout Openwrt: ubiformat /dev/mtd8 -y -f /tmp/ubi.bin" or with MIWIFIRepairTool.x86
At this moment I have stopped process because I am not able to make a full backup with xmir-patcher (I have commented some issues). Meanwhile I hope got more information about you guys by replying my 7 questions, thanks
Xmir patcher has a timeout issue, you can just use the manual commands from the wiki
3 On the firmware selector page you see in the dropdown what packages are installed, it includes lucy for the stable build in my list
6 stay on stock if you dont want to mess around witj the serial/tftp boot stuff. Stock recovery with xiaomi tool is easier on windows. (Recovery is possible regardless what you kill due to the ability to send a new boot loader over serial.)
7 if you stay on stock bootloader use the xiaomi tool. hold reset, plug in power, flash the stock firmware from the wiki page with the tool
Yes,I have seen the issues. I have already changed python files code with timeout, but still not working.
And I have to use
mount -o remount,rw /
as first command before doing full backup with Wiki commands.
Is this normal? why is this command to be able to write not being showed in the wiki?
These things make me go carrefully with the steps. I prefer to make it througt xmir patcher (just in case), but now it is not working for me. Who knows!!!
Hello, I have tested today's SNAPSHOT build (r27137-f51cb74473) and the patch for winbond NAND works well. This build comes with NO LUCI web interface.
Thanks, yes, I finally make the backup after mount command, but just in case I am writting here because of I am not seeing anyone speaking about the need of the r/w re-mount. May be I am too newbie
But just in case and before the last flash of openwrt, I want to ensure everything, that is why I want also to do it with xmir-patcher but even changing in several python files the timeout... I am still getting timeout error (https://github.com/openwrt-xiaomi/xmir-patcher/issues/15#issuecomment-2284228444)
I have finally go on with wiki commands, and now I have openwrt installed. Thanks a lot for your help guys !!!
My only great doubt now is to flash o not to flahs uboot. I will get 15Mb more of free space (I dont want to loose recovery so 85Mb option is not an option for me).
"Default available space is 60Mb . OpenWrt U-Boot provide faster boot loading and more space: 75Mb (with recovery) or 85Mb (without recovery)."
The backup commands are:
nanddump -f /tmp/BL2.bin /dev/mtd1
So this reads raw nand and writes it to temp, wich is mounted as tempfs=in ram and already readwrite:
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
So making / writeable makes no sense cause you dont write to it and you also can't write to it thanks to being squashfs.
My best guess is that you are missing the leading / for squashfs, but otherwise i habe no idea... but whats happening there will mess up xmir-patcher too.
I never used OpenWRT in the past and plan on trying out on Xiaomi AX3000T by following the Easy method but after I installed " openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi" I can not progress any further.
There is no GUI to perform other steps and this router does not have internet access.
I tried "opkg update" and opkg install luci through SSH but it was not useful because a router without internet can not get the packages. Hence, I copied all the Luci packages around 4000 files and installed them. however, I can not able to access the GUI or update openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin
What are the options I have?
Is it possible to revert to the stock firmware and try the "Difficult" method?
. Easy method
Download XMiR-Patcher and unpack into any directory - Done
Copy UBInized image openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi into directory firmware - Done
Execute !START.bat (or run.sh on *nix machine) - Done
Execute 2 - Done
Execute 7 - Done
Wait 40...70 seconds - Done
Browse 192.168.1.1 - I am stuck at this point and can not browse until router has "LuCi" installed.
Using LuCI flash sysupgrade image openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin - I tried this through SSH but it fails.
All good Guys, I managed to connect the router to the existing network to access the internet and was able to install the Luci packages. I should have done this yesterday and wasted 8 hours trying so many things and reading through forums
I managed to install Luci but somehow after rebooting, It is not showing Luci packages and I can not access it through the browser.
Please let me know if I am missing any steps.
It is looping at these steps.
Browse 192.168.1.1 - ** * Browse 192.168.1.1 - I am stuck at this point and can not browse until the router has "LuCi" installed. It reverted after I rebooted and needed to install Luci again.
Using LuCI flash sysupgrade image openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin - I tried this through SSH and GUI. It seems to fail as It is reverting to the original firmware with no Luci and web access
Wait 40...70 seconds - Reboots and reverting to previous firmware.