How to fall back to the old version uboot
Get a copy from someone, and dd (or ubi write ?) it to the correct mtd, I guess.
I have one flashed to OpenWrt before v231.
I can try to copy out the required partition.
Please tell me what and how to do.
replacing the uboot will be at your own risk ... very high danger area ... it is not just the uboot partition that one will need to replace ... there will be code elsewhere checking versions etc
Thank you for the reminder.
Isn't mtd14 the u-boot environment?
What are the mtd14_appsblenv.img differences from old to new FW?
Here is my mtd14 from old FW:
(I edited my MAC XX:XX:XX, also note that jlbaurate, got jl prefix from the bin, looks like jl is not part of that string)
$ strings mtd14_appsblenv.img
jlbaudrate=115200
bootcmd=bootipq
bootdelay=2
eth1addr=a4:97:33:XX:XX:XX
eth2addr=a4:97:33:XX:XX:XX
eth3addr=a4:97:33:XX:XX:XX
eth4addr=a4:97:33:XX:XX:XX
ethact=eth0
ethaddr=a4:97:33:XX:XX:XX
fdt_high=0x4A400000
fdtcontroladdr=4a971480
flash_type=2
machid=8850105
mtdids=nand0=nand0
mtdparts=mtdparts=nand0:0x6100000@0x7a00000(fs)
oobd=2022-11-21T09:06:21Z
soc_version_major=2
soc_version_minor=0
stderr=serial@78B3000
stdin=serial@78B3000
stdout=serial@78B3000
Same partition, but after I flashed openwrt:
$ strings OpenWrt.mtd14_appsblenv.bin
T\Obaudrate=115200
bootdelay=2
eth1addr=a4:97:33:XX:XX:XX
eth2addr=a4:97:33:XX:XX:XX
eth3addr=a4:97:33:XX:XX:XX
eth4addr=a4:97:33:XX:XX:XX
ethact=eth0
ethaddr=a4:97:33:XX:XX:XX
fdt_high=0x4A400000
fdtcontroladdr=4a971480
flash_type=2
machid=8850105
mtdids=nand0=nand0
mtdparts=mtdparts=nand0:0x6100000@0x7a00000(fs)
oobd=2022-11-21T09:06:21Z
soc_version_major=2
soc_version_minor=0
stderr=serial@78B3000
stdin=serial@78B3000
stdout=serial@78B3000
bootcmd=setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs
root=mtd:rootfs rootfstype=squashfs rootwait; ubi part fs;
ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0
fw_printenv from dynalink fw only shows this small env.?:
https://forum.openwrt.org/t/dynalink-dl-wrx36-askey-rt5010w-ipq8072a-technical-discussion/110454/762
Could you please try to backup and show the mtd14 partition from the new FW?
You need to SSH to the dynalink FW and run:
cat /dev/mtd14 > /tmp/tmp/mtd14_appsblenv.img
If you wish you can backup all your partitions this way, just use SCP to copy the partitions img.
Source: https://forum.openwrt.org/t/dynalink-dl-wrx36-askey-rt5010w-ipq8072a-technical-discussion/110454/11
EDIT: Now I see you already tried the most obvious differences here:
https://forum.openwrt.org/t/dynalink-dl-wrx36-askey-rt5010w-ipq8072a-technical-discussion/110454/776
In case you want to compare old partitions crc32 with new ones:
177e59ce mtd0_sbl1.img
151b7dc6 mtd1_mibib.img
e22f7d27 mtd2_bootconfig.img
e22f7d27 mtd3_bootconfig1.img
02239b21 mtd4_qsee.img
02239b21 mtd5_qsee_1.img
d0dc8a29 mtd6_devcfg.img
d0dc8a29 mtd7_devcfg_1.img
504bf849 mtd8_apdp.img
504bf849 mtd9_apdp_1.img
3c5754e7 mtd10_rpm.img
3c5754e7 mtd11_rpm_1.img
b5bafe32 mtd12_cdt.img
b5bafe32 mtd13_cdt_1.img
323570c6 mtd14_appsblenv.img
73c8a660 mtd15_appsbl.img
73c8a660 mtd16_appsbl_1.img
ea4f7544 mtd17_art.img
b5d6cd09 mtd18_rootfs.img
eef63c9f mtd19_wififw.img
53e198b4 mtd20_rootfs_1.img
5d3855bc mtd21_wififw_1.img
3d29cced mtd22_ubifs.img
504bf849 mtd23_ethphyfw.img
529738d1 mtd24_certificate.img
1 Like
Thank you very much for the instructions!
I got resource busy for mtd27, mtd28 & mtd29 .
cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "0:SBL1"
mtd1: 00100000 00020000 "0:MIBIB"
mtd2: 00080000 00020000 "0:BOOTCONFIG"
mtd3: 00080000 00020000 "0:BOOTCONFIG1"
mtd4: 00300000 00020000 "0:QSEE_1"
mtd5: 00300000 00020000 "0:QSEE"
mtd6: 00080000 00020000 "0:DEVCFG_1"
mtd7: 00080000 00020000 "0:DEVCFG"
mtd8: 00080000 00020000 "0:APDP"
mtd9: 00080000 00020000 "0:APDP_1"
mtd10: 00080000 00020000 "0:RPM_1"
mtd11: 00080000 00020000 "0:RPM"
mtd12: 00080000 00020000 "0:CDT_1"
mtd13: 00080000 00020000 "0:CDT"
mtd14: 00080000 00020000 "0:APPSBLENV"
mtd15: 00100000 00020000 "0:APPSBL_1"
mtd16: 00100000 00020000 "0:APPSBL"
mtd17: 00080000 00020000 "0:ART"
mtd18: 06100000 00020000 "rootfs"
mtd19: 00900000 00020000 "0:WIFIFW"
mtd20: 06100000 00020000 "rootfs_1"
mtd21: 00900000 00020000 "0:WIFIFW_1"
mtd22: 01600000 00020000 "ubifs"
mtd23: 00080000 00020000 "0:ETHPHYFW"
mtd24: 00280000 00020000 "certificate"
mtd25: 003ff000 0001f000 "kernel"
mtd26: 0218b000 0001f000 "ubi_rootfs"
mtd27: 0331a000 0001f000 "rootfs_data"
mtd28: 00f04000 0001f000 "log"
mtd29: 00516000 0001f000 "vendor"
mtd30: 0001f000 0001f000 "user_data"
mtd31: 0020f000 0001f000 "wifi_fw"
Could you calculate the crc32 for the partitions you backup?
This way we could see if any partition in new router/FW is exactly the same as the old router/FW.
Since there's a new u-boot, maybe also investigate if now there is any recovery implemented using the reset button? Power on while pressing reset button produces any effect?
Sorry for the delay!
Changed:
sbl1
bootconfig
bootconfig_1
qsee
qsee_1
devcfg
devcfg_1
rpm
rpm_1
cdt_1
appsblenv
appsbl
art
rootfs
wififw
rootfs_1
wififw_1
ubifs
# CRC32
aaeaf2a8 mtd0_SBL1.img
406d7a55 mtd10_RPM_1.img
3bc8bb50 mtd11_RPM.img
bafd7ae4 mtd12_CDT_1.img
b5bafe32 mtd13_CDT.img
9966e152 mtd14_APPSBLENV.img
4b05d5c4 mtd15_APPSBL_1.img
55d27bf2 mtd16_APPSBL.img
e7c384a1 mtd17_ART.img
fc14f36c mtd18_rootfs.img
57584f95 mtd19_WIFIFW.img
151b7dc6 mtd1_MIBIB.img
4df054d7 mtd20_rootfs_1.img
52515620 mtd21_WIFIFW_1.img
353de595 mtd22_ubifs.img
504bf849 mtd23_ETHPHYFW.img
dc7f591b mtd24_certificate.img
c6ae5333 mtd25_kernel.img
c455600f mtd26_ubi_rootfs.img
00000000 mtd27_rootfs_data.img
00000000 mtd28_log.img
00000000 mtd29_vendor.img
3460922b mtd2_BOOTCONFIG.img
ae228dc0 mtd30_user_data.img
12630005 mtd31_wifi_fw.img
3460922b mtd3_BOOTCONFIG1.img
b49811ed mtd4_QSEE_1.img
de0c22ff mtd5_QSEE.img
3f6c8ff9 mtd6_DEVCFG_1.img
7605b920 mtd7_DEVCFG.img
504bf849 mtd8_APDP.img
504bf849 mtd9_APDP_1.img
Received my second unit today, came with stock firmware 1.10.01.201 just like my first. Standard flashing steps worked like a charm just like the first. Are others receiving units with the newer firmware brand new? Or are they updating stock firmware prior to flashing?
1 Like
Anyone else having stability issues with the latest snapshots? Seems like the radios work for a few minutes after restarting the radio device and then drop out to the point where only a reboot brings them back. Could it be issues with the IPQ8074 drivers? Tested snapshots 21900, 22036 and 22040 with no luck.
I’m using 22020 without issue since first flashing earlier this week.
DFS channel ?
1 Like
Channels 100 and 6, both were working a few snapshots ago.
Channel 100 is a DFS channel in the US. Have you tried getting out of the DFS range of channels? Try 44 if you want to go low, or 157 if you want to go high… test and see if it helps?
Set 157 and performed a reboot to get the radio transmitting again. Saw the network show up on a Network Analyzer app for a few seconds then gone. Radio device is labeled as "not active" in luci and reboots are the only thing to bring it back (at least temporarily).
1 Like
When I initially tried with 160MHz for 5GHz channels, I got some issues.
After chaning to 80MHz for 5GHz and 40MHz for 2.4GHz, the WIFI are relatively stable.
And what do the kernel log and system log say, when the radio is in error condition?
What does iwinfo say?
Etc.
Is this about both radios? Both 2.4 and 5 GHz ?
If it would be just about 5 GHz, it might be a DFS issue, like already speculated.
With DFS channels it is possible that the radio remains silent if there is no fallback channel defined.
You might read