Does anyone know of the procedure to properly recover a device if the uboot procedure won't work.
I can reset the device, get to uboot, upload the firmware, hit update, but then I get a message saying "Update Failed".
So my router is bricked at the moment. I didn't do any recent updates, just rebooted it from the GUI, then it refused to come back online. It's a great little device, worked faultlessly for two years before this.
I'm actually going to buy another one now for redundancy.
Hello,
Is the firmware upgraded in uboot v4.7.4?
https://dl.gl-inet.com/router/x3000/beta
You can try to upgrade uboot first, and then try to flush the v4.7.4 firmware, to see if it restores to work (system boot).
Unzip first, then upgrade .bin at 192.168.1.1/uboot.html
X3000_uboot_fip.zip (283.2 KB)
Bruce,
I can’t upgrade uboot either, it throws the same error “Update failed”, I tried Safari & Firefox, not that it should matter.
The updates upload fine, checksums seem to pass, but immediately after I click on update it throws an error. Is the internal storage broken?
Why doe uBoot not work, also you might tell people they need to connect to the LAN port, as the WAN port does not work for uBoot.
Is there any other way to connect to it?
So just an update and a HUGE thank you to Bruce & John @GL.i tech support.
Bruce gave me a couple of links and suggested I upgraded the uBoot on the device. I tried and failed multiple times. What worked in the end?
Renaming the files from "X3000_uboot_fip.bin" to "uboot.bin" and uBoot updated.
Then from there I updated the firmware, again, I renamed it from "openwrt-x3000-4.7.4-0317-1742206344.1.bin" to "openwrt.bin", this took a couple of attempts (not sure if I was doing something wrong), but I realised once the firmware is updated, you need to log into 192.168.8.1
Now I have my Spitz AX up and running again (firmware v4.7.4 thanks to Bruce).
Just as a side note, this was a reminder of how I moved to GL.i tech.
When my Spitz had a wobble, I unboxed my previous Mikrotik Chateau12 (That's €500+ when I bought it, never worked properly). The interface horrified me, I literally couldn't log into it, even though I was 100% certain the password was correct (I use Enpass password manager). Eventually I did a factory reset on it, it was then a brick, I wasted 2 hours, it refused to recognise the SIM card and I ended up literally sending it at high speed toward the wall.
Mikrotik product are so full of themselves it's unreal. Now I remember my headspace had to be fully in that weird command line / tweaking hundreds of settings to get any form of decent performance out of it.
My next step, the TP Link Archer, the Mikrotic replaced.
Speeds were horrendous, even though the interface was pleasant again. It failed to get ANY signal, even though my phone had full signal held right beside it, in other words, it was searching for the most reliable 3G / 4G signal it could and giving up.
In all, I am extremely happy with GL.i products (I just bought another Puli AX for redundancy). Great products, great UI, great flexibility, GREAT support.
Thanks guys, you can mark this as solved, but be sure to tell people to try and simplify the file names, I think this might be a uBoot error and nothing to do with GL.i.
Now at least if something goes wrong, I will have a fresh Puli AX in a box waiting.
I spoke too soon. I switched it off to move it to another property this morning, when I set it up and turned it on it was broken again.
Solid green power light, flashing 2.4 light.
Just trying the process of updating again and it's throwing the same "update failed" errors every time. Annoying to say the least.
FYI, posting for future reference.
When putting device into uBoot mode, it is very important to hold the reset button down at least 1 second AFTER to 2.4 light comes on. During this process, once you turn on the device, holding down the reset button, the power led will flash 5 times, then the 2.4 led comes on, release the reset button at least a second after this happens.
Doing the above, I was able to successfully update the device, every time. There is no "Update complete" or even a progress indicator, I left it for 4-5 minutes after the upgrade process began before power cycling.
Remember to switch local machine IP back to DHCP from manual after upgrade completes.
Does anyone know how to export settings for easy recovery if this happens again?
