Hello!
I was following the install guide but stuck after the ubiformat step
root@XiaoQiang:/tmp# ubiformat /dev/mtd9 -y -f /tmp/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi
ubiformat: mtd9 (nand), size 35651584 bytes (34.0 MiB), 272 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 271 -- 100 % complete
ubiformat: 180 eraseblocks have valid erase counter, mean value is 0
ubiformat: 90 eraseblocks are supposedly empty
ubiformat: warning!: 2 of 272 eraseblocks contain non-UBI data
ubiformat: warning!: only 180 of 272 eraseblocks have valid erase counter
ubiformat: mean erase counter 0 will be used for the rest of eraseblock
ubiformat: use erase counter 0 for all eraseblocks
ubiformat: flashing eraseblock 62 -- 100 % complete
ubiformat: formatting eraseblock 271 -- 100 % complete
root@XiaoQiang:/tmp# nvram set boot_wait=on
root@XiaoQiang:/tmp# nvram set uart_en=1
root@XiaoQiang:/tmp# nvram set flag_boot_rootfs=1
root@XiaoQiang:/tmp# nvram set flag_last_success=1
root@XiaoQiang:/tmp# nvram set flag_boot_success=1
root@XiaoQiang:/tmp# nvram set flag_try_sys1_failed=0
root@XiaoQiang:/tmp# nvram set flag_try_sys2_failed=0
root@XiaoQiang:/tmp# nvram commit
root@XiaoQiang:/tmp# reboot
root@XiaoQiang:/tmp# Connection to 192.168.31.1 closed by remote host.
I couldn't ssh back after the reboot. Connection was refused (also I could setup wired IP only statically, dynamic configuration didn't work). Yes, I've tried connecting to 192.168.1.1.
This is my firmware
root@XiaoQiang:~# cat /proc/cmdline
console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=0 mtd=ubi
What could be the problem? I've debricked it using a repair tool, but I'm wondering should I try again doing something differently?
EDIT:
Strangly, after debricking and accessing ssh again I have different info about firmware:
root@XiaoQiang:~# cat /proc/cmdline
console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=1 mtd=ubi1 uart_en=1
for the new offical openwrt fw, the IP is 192.168.1.1, no others.
When we use SSH, or WinSCP, always on 192.168.1.1, like:
ssh root@192.168.1.1 on ubuntu terminal to connect the router.
scp a file to /tmp:
$ scp -O sysupgrade.bin root@192.168.1.1:/tmp
ssh a file to /tmp:
$ ssh root@192.168.1.1 "cat > /tmp/openwrt.bin" < ~/Downloads/openwrt.bin
no need to login ssh.
I think you could do it again for the SSH access, and then, make sure the ubi code flash into mtd8 or mtd9.
try with window cmd i got same problem putty sometime get u access denied in ssh
i find the wget with a internet cable way to reinstall ubootmod sysupgreade firmware but it still not giving me ip after i plug back to my computer (no ip no gateway) what should i do now
normally, openwrt admin ip is 192.168.1.1, and your PC should be in auto-dhcp get an ip on 192.168.1.xxx. I did not meet a case like yours.
my router is not after debrick it not giving me any ip address
Ditti4
562
Have you tried a different Ethernet port on the router? Also, have you tried leaving the Ethernet cable unplugged for a minute and then plugging it back in? I've noticed before that Windows will sometimes not request a new IP address if it doesn't detect the connection as being down long enough (or maybe it's just been a coincidence in the past, but worth a shot at least).
tried but got random ip add again no gateway mask
i find out it not come from my router it come from the snapshot i download from openwrt download page i dowload another pork image (immortalwrt) it work perfect like it should be hope someone report n fix it soon (because i want to run pure openwrt not the chinese pork image
)
2 Likes
dnd
565
I think the snapshots were broken for the filogic target for a couple of days.
Same issue with the MT6000:
Hi, can someone help please
AX3000T, downgraded from from 64 to 47 successfully (had to use the MIWIFIRepairTool to do this)
Downloaded mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi into firmware folder
Launched XMIR-Patcher, pointed the IP to 192.168.31.1, then option 2 then 7
I then got the following log
device: "RD03"
img_write = True
Image files in directory "firmware/":
"firmware/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi"
Download file: "/tmp/dmesg.log" ....
Download file: "/tmp/mtd_list.txt" ....
Download file: "/tmp/mtd_info.txt" ....
Download file: "/tmp/mtd_fdt.txt" ....
Download file: "/tmp/kcmdline.log" ....
Parse all images...
UBI: filetype: b'UBI#'
UBI: Decoding UBIFS...
UBI: volume: "kernel" size: 7110656
parse_ubifs = 1
FIT size = 0x6C2B14 (6922 KiB)
FIT: name = "ARM64 OpenWrt FIT (Flattened Image Tree)"
FIT: def_cfg: "config-1"
FIT: def_cfg desc = "OpenWrt xiaomi_mi-router-ax3000t"
FIT: model = "xiaomi,mi-router-ax3000t"
FIT: def_fdt: "fdt-1"
FDT: desc = "ARM64 OpenWrt xiaomi_mi-router-ax3000t device tree blob"
FDT: type = "flat_dt"
FDT: arch = "arm64"
KRN: desc = "ARM64 OpenWrt Linux-6.6.32"
KRN: type = "kernel"
KRN: arch = "arm64"
KRN: compression = "lzma"
KRN: data = 4263111 bytes
FDT: compatible = ['xiaomi,mi-router-ax3000t', 'mediatek,mt7981']
FDT: model = "Xiaomi Mi Router AX3000T"
FDT: dt_part: ['/soc/spi@1100a000/flash@0/partitions']
FIT: Founded "initrd-1" node
FIT: initrd image name: "ARM64 OpenWrt xiaomi_mi-router-ax3000t initrd"
fw_img: 8064 KiB | kernel: 6922 KiB | rootfs: 2734 KiB
Download file: "/tmp/bl_BL2.bin" ....
Download file: "/tmp/bl_FIP.bin" ....
Download file: "/tmp/env_Nvram.bin" ....
Download file: "/tmp/env_Bdata.bin" ....
Download file: "/tmp/env_BL2.bin" ....
current flag_boot_rootfs = 1
install_method = 400
--------- prepare command lines -----------
fw_img: 8064 KiB | kernel: 6922 KiB | rootfs: 2734 KiB
------------- flash images -------------
Upload file: "tmp/fw/fw_img.bin" ....
Run scripts for change NVRAM params...
Boot from firmware [0] activated.
Writing firmware image to addr 0x00600000 ...
mtd -e "ubi" write "/tmp/fw_img.bin" "ubi"
The firmware has been successfully flashed!
Send command "reboot" via SSH/Telnet ...
ERROR: SSH execute command timed out! CMD: "reboot -f"
It seemed to install successful, but now I'm just getting a 169 address and can't seem to do anything anymore. Tried power cycling. For now I've gone back to direct to my main ISP router. Can anyone please help, or I have I bricked? Unsure if I need to also download any more files after this (if I can get it to run)
You can try 23.05 snapshot from https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/mediatek/filogic/
,but ax3000t-ubootmod-squashfs-sysupgrade.itb seems broken,today built is missing rootfs .
23.05-snapshot-r23898-d0620706f0 buildlog: https://buildbot.openwrt.org/images/api/v2/logs/2011823/raw
2 Likes
Hey, hadn't read your message til now.
But someone on another site suggested I was maybe in the WAN port (I originally wasnt and was in the 2nd and had tried that port 1 too thinking perhaps its that
However, thought I'd try port 4 from what he said, and got a 192.168.31 address again - and could see the router again as if nothing had happened, so I'd tried running the same flash, similar result, eventually got a 169 address on that port now - not sure if/when its going to want to give me access again to have another run but if it does I'll try that 23.05 one you gave
IF I get any further, where it says "Using LuCI flash" is LuCI just the name of the 192.168.1.1 page or an app? as yet to find it
edit: ah never mind that message wasn't directed at me
Someone? 
I see people are successful installing immortalwrt, I'd recommend that for the time being.
1 Like
Hey on here - ta - I'd be pulling hair out but I'm bald. If I can get another non 169 address then I'll give it a shout (will hunt the files out in the meantime)
edit - resolved and managed to get fixed, in case helps anyone else (tho its no doubt buried in the messages elsewhere too, couldn't get out of a 169 address no matter how many reboots or ports etc other than that random 1 time. So held the pin in the reset button for a while. That got me back, must be stuck in some mode or other.
Used ImmortalWRT, and still early days but looking good
1 Like
thanks, followed that and did exactly the same thing. Tried to install the broken openwrt snapshot like 4 or 5 times today....that really needs to be fixed!
2 Likes
Does anyone know how to config routing with the 23.x.x firmware i don't see it in luci like my old router
just tested my personal build on snapshot updated code (r26573-bac2f1bed6), it's all ok, no IP issues.
(I'm using ubootmod code)