Installed ExpressVPN Aircove firmware on AX1800. Everything worked perfectly well. After few months, I decided to go back to Flint’s original firmware. Followed the procedure (resetting, static ip etc) and I could and can see flashing LED few times and then solid white/grey. But I can not access 192.168.1.1 no matter what. Have I completely bricked the router? With no reset, I get a solid blue LED but completely dead otherwise. Can I uboot through serial? Any help is appreciated.
Did you make sure only 1 cable is connected to LAN or WAN port?
I do not work for and I do not have formal association with GL.iNet.
After restart your device in uboot mode and setting your computer’s network card to 192.168.1.2/24, have you tried pinging your AX1800 with 192.168.1.1?
Us a private browser window and flush DNS.
I saw this happen to me with chrome, the uboot http server code is very fragile, and chrome may do multiple requests and cause the response to hang, try with firefox. set static ip 192.168.1.2 with subnet mask 255.255.255.0. and plug in only 1 single cable into lan port.
Thanks for all the replies. I tried all the above but still not responding I am afraid:
- I had one cable connected to LAN port. Also tried WAN port. still no response.
- I tried 192.168.8.1 → no response
- I had already changed the DHCP to static, with 192.168.1.2/24. No ping response
- Private browser tab did not help either. I tried Edge instead of Chrome, that didn’t help either.
Any other suggestions?
Let’s try this
- Make sure the router is turned on.
- Hold the reset pin for about ten seconds.
- The LED will flash four times.
- Check if the issue is resolved.
Repeat this process three more times.
I tried that in two scenarios, and with neither I get LED flashing 4 times.
Scenario 1 → Turned the router on as is and I get solid blue LED.
Scenario 2-> Pressed the reset button, then power on with one ethernet cable connected to PC. LED flashes blue and white few times and then turns solid white. Then released the reset button. Then hold the reset button for 10s or more but no LED flashing.
Does solid white LED by definition suggests that uboot is loading but it’s just that I am not able to access it?
How about the ExpressVPN router page? Can access or not? 192.168.132.1
I tried that too, nothing! I also tried to ping sweep the whole ip range from 192.168.0.1 all the way to 192.168.255.255, no ping response.
Can the USB be used to do anything?
I’m not sure about the new routers, but the old ones had the ability to connect via the UART connector and use a tftp server for UBoot. I would like to contact GL-inet support for details.
I’ll keep that as my last resort 
Any crazy suggestions?
After you set your pc ip to 192.168.1.2/24 you access the uboot at 192.168.1.1 not 192.168.8.1
And disconnect wifi and any other lans with same ip range.
That’s what I did. I also tried 192.168.8.1 as someone suggested that previously. AirCove uses 192.168.8.1 or 192.168.132.1 as gateway ip.
OK believe it or not I have found the problem! I knew that AirCove firmware used 192.168.132.1 as the default gateway but I always thought by resetting, everything resets to 192.168.1.1. I changed the static ip to 192.168.132.10/24 and then changed default to 192.168.132.1 and ta-da I have the uboot page! Thanks for the all the help. It really helped to narrow down the problem.
2 Likes
You mean set the static ip to 192.168.132.10 instead of 192.168.1.2, then access 192.168.132.1 for uboot page instead of 192.168.1.1?
yes. ExpressVPN’s AirCove is to blame
They are trying to config the setting for uboot since got Aircove
That is wrong Uboot procedure is
- unplug from wall power
- have only one ethernet cable plugged in
- change computer to static ip of 192.168.1.x( anything up to 254 and not 1)
- holding the power button or reset button plug the power back into wall and keep holding power reset button till light goes solid.(if you let go it will not work)
- enter 192.168.1.1 into a private widow browser