4 1/2 Ways to Unbrick Your (Gl.inet) Router!

So You’ve Bricked Your Router and You Feel Bad!

This tutorial might help.


Unbricking via GL.iNet Recovery Mode

  1. Insert the ethernet cable into the LAN port.
  2. While holding the reset button down, plug in the power cable.
  3. Go to 192.168.1.1 and re-flash your OpenWRT firmware.

Unbricking via TFTP

  1. Enable TFTP in:
    • Control Panel > Programs > Programs and Features > Turn Windows Features on or off
  2. It may be necessary to:
    • Disconnect from the internet and temporarily disable your firewall or permit TFTP operation.
  3. Rename your firmware to firmware.bin.
  4. Run Command Prompt as administrator.
    • Command Prompt Commands:
    • cd C:\[path]\[to]\[your]\firmware.bin
  5. Insert the ethernet cable into the LAN port.
  6. While holding the reset button down, plug in the power cable.
    • Command Prompt Commands:
    • tftp -i 192.168.1.1 put firmware.bin
  7. Wait for the router LEDs to stop blinking.
  8. WebUI should now be available at 192.168.1.1 or maybe 192.168.8.1. (This isn’t an exact science!)

Unbricking via USB to TTL Adapter

(Useful for when Pineapple installation hangs)

  1. Attach GND, RX, and TX lines to the header.
    • Note: Slate routers may require soldering the header on. RX goes to TX and vice-versa.
  2. PuTTY Parameters:
    • COM port is unique to your system (port info is available in Device Manager).
    • Baud rate: 115200.
  3. Plug a USB stick into the router with the 19.07.7 firmware renamed to [yourModel]OpenWrt.bin.
    • Commands in PuTTY:
    • firstboot
    • mount /dev/sda1 /mnt
    • cp /mnt/[yourModel]OpenWrt.bin /tmp
    • sysupgrade /tmp/[yourModel]OpenWrt.bin
  4. Get back in via PuTTY:
    • Open and edit network settings with:
    • vi /etc/config/network
    • Change any 172.x.x.x IPs to 192.168.8.1.
    • Learn how to save and exit in vim and be amazed.
  5. WebUI should now be available at 192.168.8.1!

Additional Notes

  • In each instance, it may be necessary to set a static IP of 192.168.1.2.
  • If there’s a hang-up, try re-leasing your PC’s IP dynamically using DHCP.
  • If you have a gateway router already at 192.168.1.1, you’ll need to disconnect from it before connecting to any GL.iNet routers in recovery mode.

Leave Comment

Your email address will not be published. Required fields are marked *