I´m looking for the uboot update for AR300M16 as it is stuck in uboot and doesn’t load the firmwear.
Does the version for the AR300M also work for the NOR only devices?
Issue background: I tried to update the AR300M16 but didn’t know it was a “M16” version, so I forced the firmware for the AR300M on it. surprisingly this didn’t work ;-). Uboot does work, so I tried to push the firmware for the correct model (v4.3.7 and the formerly working v3.216) but it keeps booting into uboot. A vanilla WRT firmware didn’t work either. So I’m hoping its an issue with the older uboot version that is on the device
Hi, this is the URL for the U-Boot update: GitHub - gl-inet/uboot-for-qca95xx: ar300m uboot source. Open the link and go to the “bin” directory. From there, locate the file for the AR300M called “uboot-gl-ar300m-20220216-md5-97ff7bb80cbf129fa21f34ded1559ff8.bin”. Download this file and proceed with the update. Please test to see if it works.
Hi, you can try to input 192.168.1.1 directly without adding uboot.html and see if it can access the firmware update page. 通过 Uboot 进行 Debrick - GL.iNet 路由器文档 3 — Debrick via Uboot - GL.iNet Router Docs 3 (gl-inet.com)
Yes i can access the Uboot @ 192.168.1.1 but
I tried to push the firmware for the correct model (v4.3.7 and the formerly working v3.216) but it keeps booting into uboot. A vanilla WRT firmware didn’t work either.
So are you trying to update uboot or trying to update the device firmware?
Uboot updates requires, well as the name says, the update files for uboot itself.
The screenshot shows the uboot update screen. So you can’t use device firmware or vanilla WRT there.
I tried to update uboot with the “uboot-gl-ar300m-20220216-md5-97ff7bb80cbf129fa21f34ded1559ff8.bin” file.
Now it took the firmewear. But the process was not as described in the documentation for U-Boot update (GitHub - gl-inet/uboot-for-qca95xx: ar300m uboot source) after firmwear instalation it did not boot into the OpenWRT but back into uboot and needed a powercycle to boot normaly
Hi, is your device functioning properly now?
Hi yes the firmware is working now. I guess there is a discrepancy between the documentation and the actual behavior of the uboot update process.
But I would still like to know if there are different versions of uboot for the two versions of the Shadow? I could not update to the most recent uboot version. Might still be important to update uboot in the future