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
2 Likes
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
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) ?
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://mirrors.edge.kernel.org/caf_mirrored_source/quic/qsdk/qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2 [following]
--2020-07-19 08:59:30-- https://mirrors.edge.kernel.org/caf_mirrored_source/quic/qsdk/qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2
Resolving mirrors.edge.kernel.org (mirrors.edge.kernel.org)... 147.75.69.165, 2604:1380:1000:8100::1
Connecting to mirrors.edge.kernel.org (mirrors.edge.kernel.org)|147.75.69.165|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-07-19 08:59:30 ERROR 404: Not Found.
It seems qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2 had been removed from the website.
How can I find qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2?
By the way, thank you for sharing.
I extracted qca-IOT-CNSS.zip and recompressed to qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2 and put it in ./qsdk/dl It doesn't' work. I don't know the original folder structure of that file.
By the way, if you had succeeded in compiling the source code, it should still be in the directory of the source code like this ./qsdk/dl/qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2 or maybe in here ./chipcode/NHSS.QSDK.10.0/apss_proc/out/proprietary/QSDK-Base/qca-IOT/qca-IOT.tar.bz
Thank you for sharing.
Thank you but it didn't contain qca-IOT-CNSS_W.QZ.3.0-00104-QZHW4024-1.tar.bz2
Could you please share this folder ./NHSS.QSDK.10.0/apss_proc/out/proprietary/QSDK-Base/ ?
or
Use command line to find that file by
find . -name "qca-IOT*.tar.bz"
Could you please copy and run this command again because those above commands that my fault it missed .bz2?
find ~/ -name "qca-IOT*.tar.bz2"
Thank you for your reply.