GL-MT300N-V2 restore to factory firmware?

Hello. Basically I was attempting to install a firmware update tonight, device went unresponsive for an extended period of time (10+ mins) tried to reset it, done nothing, so I pulled the power, then powered it back on again, still nothing. I have managed to flash LEDE Reboot 17.01-SNAPSHOT r3657-45566fb / LuCI lede-17.01 branch (git-17.298.45605-07e7ff0) via uboot, it’s currently running pretty happy on that, I was wondering how I would be able to go back to the factory standard firmware, because I like the simplicity of it, I’m not really a networking specialist :confused:

I am able to access LEDE - LuCi UI on 192.168.1.1 but not standard UI via 192.168.8.1.

thanks in advance

Stephen

The stuck firmware is available in GL.iNet download center. And the latest is available in GL.iNet download center.

Thanks for the reply :slight_smile: I have already installed GL.iNet download center. Unfortunately I am unable to get to the factory UI, just the LEDE - LuCi on 192.168.1.1. I wish to access the stock UI.

Did you´ve flashed with uboot? After disabling the static ip you should get a IP with DHCP and you can reach the router with the ip 192.168.8.1

Sigh, I flashed the device via uboot, as written in the initial post, I did unbind ip to auto, and also checked with various computers, it will not access 192.168.8.1, just the advanced options under 192.168.1.1.

First, seems you reserved the setting while flashing back. So you have 1.1 as IP address, not 8.1. You need to reset the firmware by pressing and hold the reset button for 10 seconds.

Seconds, you can only go to advanced settings because the browser cache. You can clear the cache of your browser or try another browser.

Or a trick, add ? at the end of the url

try 192.168.8.1/index.html?

thanks for reply, I did flush cache of the browsers of 2 computers, then reset the router (10 second button press) it done the same thing, I flashed another firmware (2.27 testing) to the device this time it’s working, must have just been a bug in the system :slight_smile: