Are you sure that will not just make it load from the 2nd partition on the next boot and soft brick it right away?
Does that apply only to custom builds from the firmware selector? I just downloaded the default build. No customization.
This is how my AX3200 works for a very long time.
That's correct. Another post above:
But FYI - the issue appears fixed.
I see the kmods listed in the recipe again.
Thank you for the confirmation.
Can you please check if these 2 fields are set to the same:
boot_fw0=run boot_rd_img;bootm
boot_fw1=run boot_rd_img;bootm
If those are set to load the same image, then the counter doesn't seem to matter as much.
root@router:~# fw_printenv | grep "boot_rd_img;"
boot_fw0=run boot_rd_img;bootm
boot_fw1=run boot_rd_img;bootm
root@router:~# fw_printenv | grep "flag_try_sys"
flag_try_sys1_failed=48
flag_try_sys2_failed=8
Thank you so much for checking and for the info.
It's very likely that your setup works because both fw0 and fw1 are set to load the same boot image.
If possible, I would recommend to edit the comment about changing the counter above 6, as someone might have fw1 set to another boot image by default and it might soft brick their AX3200 on the very next boot (unless you're sure that it doesn't affect it)
I tried that already quite some time ago. Soft-brick doesn't depend on boot_fw1 being the same as boot_fw0.
1 Like
Thank you so much for the info and for the confirmation.
Good to know that it doesn't depend on it
If I remember correctly from the AX3200 thread the soft brick happens only on devices with newer bootloader. I have a AX3200 with older BL and those counters always stay at 0.
1 Like
Updated xiaomi 4a gigabit v1 and working perfectly thanks
1 Like
Could be, that's a good point that it might depend on the hardware revision. Thank you for the reply and the info, I appreciate it
1 Like
Unforunately Comfast CF-E395AX did not make it into the build and the CF-393AX shows that it is not compatible if you try to load the sysupgrade. even though it should be the same h/w, i didn't want to try the force option until someone comfirms you can do that and it works
Check this:
It seems my router has older u-boot:
root@OpenWrt-AP:~# grep ^U-Boot /dev/mtd2
U-Boot
U-Boot console
U-Boot
U-Boot BUG at %s:%d!
U-Boot 2014.04-rc1 (Sep 28 2021 - 10:42:26)
root@OpenWrt-AP:~# grep mtd2 /proc/mtd
mtd2: 00080000 00020000 "u-boot"
1 Like
Runs fine on my Netgear WNDR3700 v4. Thank you to everyone who worked on this!
Attended Sysupgrade from 23.05.4 to .5 went ok for RPi CM4 (with DFRobot Routerboard)
Hi.
Updated to 23.05.5 today on my Ubiquiti UniFi U6 Long-Range v2.
Unfortunately the downstream is as bad as with v 23.05.4. My Mobile tells me 6 mbit. Did a speed test and had 4,3 Mbps. Thats pretty bad.
So I do confirm at least for the Ubiquiti, that the fix did not work.
I'll rollback to .3 again.
Let me know if I can provide any additional information to track this issue down and fix it finally.
Can you elaborate?
In which regard?
Via my Smartphone I had a sync with 6mbit. Same issue I had with .4. Testing the download speed to the internet showed 4.3MBit. I rolled back to .3 and the sync was again up to 1200++MBit. Also the speedtest was back to normal with ~100MBit down, the max of my internet link.
Right now the network manager of my Android shows:
Freq: 5GHz
Up: 1729 Mbit/s
Down: 1200 Mbit/s
Like mentioned, with .4 or .5 it only shows 6mbit down and in fact its horrible slow. No matter if WAN or LAN.So this is not just cosmetics
1 Like
Upgraded Xiaomi Redmi AX6000 (Mediatek mt7986a) from 23.05.3 to 23.05.5 2 days ago - took only 2 minutes using attended sysupgrade, kept all settings and appears to be working well so far. Thanks all Devs.
1 Like