GL-AR300M-LITE Booting Mystery

Yeah. I found this description somewhere else.
I must say I really have no idea about what I am doing here… :grin::man_facepalming:
So I found two files for the LITE version both *.bin.
Am I right I am dealing with NOR then?

I couldn’t connect to the IP. According to what I found this problem is specific to the damn LITE version. :frowning:

More or less accidentally I found that when I connect to TTL and start the DHCP service it works and I can access the router from the browser for a short time. It was possible to start the upgrade as described but I don’t think it finished successfully.

Still no WiFi and neigher of the IPs accessible.
Should I have flashed the kernel.bin instead of sysupgrade.bin?

Spent nealy two days on it and could finally flash OEM-SW.
Seems totally random available.
Could find some oxidized patches around where the PCIE would go on the non-LITE.

I don’t know why it worked for a while back then, but now I tried to use it again after a long time: not accessible.
The LITE is not accessible in the recovery process.
Left LED on and the middle one indicating network traffic (WAN).

Maybe you can try change uboot itself first. http://192.168.1.1/uboot.html

If uboot cannot be accessed totally, you may try another pc.

Didn’t work. Not this link and not from another PC.

Network connection to router seems to be successfully established.

What is the waiting time to release the reset button for the LITE model?

One LED will flash 5 times and another LED light up. Release finger then.

Yes, that is what I did. No connection to uboot. :pensive:

  1. Only connect one cable from your pc to the router. Do not connect multiple cables.
  2. Press and hold reset button, then power on router.
  3. Wait for one LED flashes. When it flashes several times and another LED will light up.
  4. Release your finger now
  5. Change pc IP to 192.168.1.2

Then, try to access 192.168.1.1 using your browser. Pls post what is displaying.

Yes, that is what I tried. → Browser is running into timeout. :man_shrugging:

If everything is done correctly, and still timeout, maybe just try a different pc and cable.

I tried all that Mr Zhao :frowning:

Sure WAN port works like LAN in the other routers?

Maybe there’s something wrong on the HW level?

In uboot wan or lan does not matter.

Maybe the only thing can do now is sending the unit back to me in HK to investigate.

Oh dear. I guess that is too expensive.