Xiaomi AX3600 install guide

Source https://www.right.com.cn/forum/thread-4040158-1-1.html

  1. download xiaomimtd12.bin and nand-ipq807x-single.img
    disconnects route wan network cable
    get ssh Adding OpenWrt support for Xiaomi AX3600

  2. login ssh, set uboot env

nvram set flag_last_success=0
nvram set flag_boot_rootfs=0
nvram set uart_en=1
nvram set boot_wait=on
nvram commit
  1. scp copy xiaomimtd12.bin to /tmp
    flash firmware mtd write /tmp/xiaomimtd12.bin rootfs
    after reboot now reboot to qsdk firmware (led broken :neutral_face:)

  2. login web 192.168.1.1 (no password)
    sysupgrade nand-ipq807x-single.img
    after reboot, sysupgrade again

  3. login ssh, set boot rootfs

fw_setenv flag_last_success 1
fw_setenv flag_boot_rootfs 1

Back to MiWiFi

  1. download ubi firmware (1.0.17 or 1.0.67) copy to /tmp
  2. login ssh, flash firmware
    ubiformat /dev/mtd12 -y -f /tmp/xiaomi1.0.67.ubi
  3. set ubootenv
fw_setenv flag_last_success 0
fw_setenv flag_boot_rootfs 0

Now reboot, if you back to qsdk, login ssh set boot rootfs

nvram set flag_last_success=1
nvram set flag_boot_rootfs=1
nvram commit

Note

  • 160MHz channel is 64
  • Please sysupgrade twice nand-ipq807x-single.img (not keep settings)

Credit

zhiping (thanks for build!) LonGDikE Gaojianli(SSH)



6 Likes

Thank you for your work. I installed this image yesterday and faced 2 problems:

  1. I can't save settings. They just disappear after reboot. (even those I made using ssh and config files)
  2. I can't go back to miwifi. Just sysupgrading over web doesn't work. Old .bin files don't valid for flashing and qsdktoxiaomi.img that I found on the internet doesn't change anything (but it is flashing).

Any suggestions would be appreciated. Thanks.

Sorry i don't speak english
Please update the firmware again
After sysupgrade twice, ssh set boot rootfs(step5)

1 Like

I have exactly the same problem

Settings doesn't getting saved - i already sysupgraded a few times - no change - and the fw_setenv doesn't help...

hmmm...

Try to reset to factory. That's something that happend to me in latest Master in 2 diferents devices.

Unfortunately it didn't help. Even the ssh-thumbprint is new after every restart... it's a complete "fresh" boot everytime...

This is a build from QSDK (qualcomm fork of OpenWRT chaos calmer).

I am not sure as to what actually works on that fork, its makes up some of the support package supplied to OEM's

I am also unsure what tag this used for QSDK (i am unable to get a working build myself)

1 Like

I'm happy to feed you with informations - if you need some outputs ... cause it seems I'm stuck with a "always-new-openwrt" for now...

Not sure what to look at, I get my device next week.

Maybe the original creator of this image can pass on some more information on the build (QSDK tag / added or changed files ect).

OK - i just got back to "stock" - with scp the original-firmware in /tmp and ssl in openwrt:

mtd write /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin rootfs

2 Likes

https://source.codeaurora.org/quic/qsdk/oss/system/openwrt/tree/?h=NHSS.QSDK.11.1.r3
QSDK11.1 R3

1 Like

Hi,
i don;t exacly how but i get working openwrt with keeping settings.
But - it its old build - v15 ?
And second - i can't back to stock

root@Openwrt:~# mtd write /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin rootfs
Unlocking rootfs ...

Writing from /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin to rootfs ...
root@Openwrt:~# mtd verify /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin rootfs
Verifying rootfs against /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin ...
a2bcc2c85eacfab2bcd2756a25daa5e8 - rootfs
a2bcc2c85eacfab2bcd2756a25daa5e8 - /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin
Success

after reboot always boot openwrt

BusyBox v1.28.3 () built-in shell (ash)

     MM           NM                    MMMMMMM          M       M
   $MMMMM        MMMMM                MMMMMMMMMMM      MMM     MMM
  MMMMMMMM     MM MMMMM.              MMMMM:MMMMMM:   MMMM   MMMMM
MMMM= MMMMMM  MMM   MMMM       MMMMM   MMMM  MMMMMM   MMMM  MMMMM'
MMMM=  MMMMM MMMM    MM       MMMMM    MMMM    MMMM   MMMMNMMMMM
MMMM=   MMMM  MMMMM          MMMMM     MMMM    MMMM   MMMMMMMM
MMMM=   MMMM   MMMMMM       MMMMM      MMMM    MMMM   MMMMMMMMM
MMMM=   MMMM     MMMMM,    NMMMMMMMM   MMMM    MMMM   MMMMMMMMMMM
MMMM=   MMMM      MMMMMM   MMMMMMMM    MMMM    MMMM   MMMM  MMMMMM
MMMM=   MMMM   MM    MMMM    MMMM      MMMM    MMMM   MMMM    MMMM
MMMM$ ,MMMMM  MMMMM  MMMM    MMM       MMMM   MMMMM   MMMM    MMMM
  MMMMMMM:      MMMMMMM     M         MMMMMMMMMMMM  MMMMMMM MMMMMMM
    MMMMMM       MMMMN     M           MMMMMMMMM      MMMM    MMMM
     MMMM          M                    MMMMMMM        M       M
       M
 ---------------------------------------------------------------
   For those about to rock... (Chaos Calmer, unknown)
 ---------------------------------------------------------------
root@Openwrt:~# mtd verify /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin rootfs
Verifying rootfs against /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin ...
a2bcc2c85eacfab2bcd2756a25daa5e8 - rootfs
a2bcc2c85eacfab2bcd2756a25daa5e8 - /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin
Success
root@Openwrt:~# fw_printenv  flag_try_sys2_failed
flag_try_sys2_failed=1

i don't know what this mean:
备注:附件里面的qsdktoxiami.img为qsdk固件刷回小米ax3600原版的固件,在备份升级里升级就行qsdktoxiami.img
i can't see that filename anywhere

and
this - "and ssl in openwrt:" here:

OK - i just got back to "stock" - with scp the original-firmware in /tmp and ssl in openwrt:

mtd write /tmp/miwifi_r3600_firmware_5da25_1.0.17.bin rootfs

qsdktoxiaomi.img uploaded
vendor sdk has been in the 15.05.1 chaos calme

1 Like

thx
i'm back on stock now

so, if vendor don't share new sdk it's not possible to get new openwrt ?
(i'm new in openwrt and don't know whats the difference between versions)
it's a stable and secure version to use ?

vendor sdk are all chaos calme or custom Linux

1 Like

The QCOM board support package / SDK is 15.05, that's why you see a lot (probably all) of vendor (Linksys ect) firmware for devices running QCOM SoC(s) is based on 15.05

Link : https://wiki.codeaurora.org/xwiki/bin/QSDK/

2 Likes

so in this version (15.05) functionality is the same as in stock firmware or there are some differences

1 Like

I uploaded some packages

3 Likes

Can you upload any modifications to QSDK needed to build this, I would assume its just adding firmware and DTS (And possibly fixing the NAND layout) ?

I trouble the author(zhiping) to modify to open qsdk10 , now public

3 Likes