1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Router used to work with Thibor 15c and died

Discussion in 'HyperWRT Firmware' started by krzyspvfr, Sep 15, 2006.

  1. krzyspvfr

    krzyspvfr LI Guru Member


    I have a strange problem on my WRT54GL v 1.1. Just after buying it I reflashed the device with DD-WRT, but then I changed to Thibor 15c. Just after upgrade I did a reboot by holding the back reset button for 30 seconds, then configured the router to match my needs and it worked fine for a few days. Then suddenly I found out one morning that it has reset itself to defaults during the night... OK, so I left the device unplugged for a few days, then today I started configuring it. Initially, I did the 30-seconds back-panel-reset once again, afterfards I connected to the router with browser (no problems so far) and configured a few things (cloned MAC, changed wireless settings, disabled the Secure Easy Setup thing, etc), then after reboot the router died:
    - boots up fine,
    - I can get a local IP by DHCP,
    - after a few seconds it reboots.

    The time from power up to reboot is so small that I can't even log in the administration panel... it keeps rebooting every 15 seconds or so. I tried to ping it, ping goes fine for 3-4 seconds and then router reboots.... anyone can help? what can I do now?

  2. krzyspvfr

    krzyspvfr LI Guru Member

    Update: I managed to connect to it with tftp, got the "upgrade successful" message, but the router is dead now. After powering it up the power LED keeps blinking forever, I can't ping it... is it bricked?
  3. Thibor

    Thibor Super Moderator Staff Member Member

    you need to tftp again. leave it alone until it reboots by itself
  4. krzyspvfr

    krzyspvfr LI Guru Member

    Thanks for the hint :) I did it and I sucessfully reverted the firmware to the original Linksys. However, the main problem remains the same: I got reboot every 10-15 seconds. What's wrong? hardware failure?

  5. GhaladReam

    GhaladReam Network Guru Member

    Definately sounds like a hardware problem. I'd exchange it for a new one.

Share This Page