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

Bricked my router linksys WRT54GL v1.1

Discussion in 'Tomato Firmware' started by Hungry Man, Oct 9, 2010.

  1. Hungry Man

    Hungry Man Networkin' Nut Member

    I did a bad overclock on my Tomato WRT54GL and now it's not working.

    Power light blinks constantly (doesn't seem to end)

    All ethernet lights and "internet" are on.

    DMZ doesn't flash even for a moment on bootup.


    Am I totally boned here? Outside of opening the router up what are my options?
     
  2. FattysGoneWild

    FattysGoneWild LI Guru Member

    Did you try a hard reset? 30-30-30? What MHz did you set it at that caused the brick?
     
  3. Hungry Man

    Hungry Man Networkin' Nut Member

    216mhz using telnet to the VRAM. I think it might be an invalid speed for the kernel =\ I should have checked first.

    Er, hard reset? I've tried unplugging it and plugging it back in. I've tried the 30-30-30 a few times as well.
     
  4. FattysGoneWild

    FattysGoneWild LI Guru Member

    Gah. Yeah that sucks man. There is a chart floating around that shows what clocks are safe that the router will read. Like you said. You probably picked 1 that is not supported. Wish I could help you further. But be patient and they will help you out to try and unbrick it.
     
  5. Hungry Man

    Hungry Man Networkin' Nut Member

    If someone could post that it would be great.
     
  6. Hungry Man

    Hungry Man Networkin' Nut Member

    216 is supposed to be supported but apparently 215 is a killer value. I don't think I typo'd but maybe for some reason it clocked lower? =\ Gonna short it.
     
  7. FattysGoneWild

    FattysGoneWild LI Guru Member

  8. WRobertE

    WRobertE Addicted to LI Member

    216 is a valid overclock value for the GL - I've used it on several GL's without issues.

    Also the recommendation is NOT to enter a backplane frequency, like nvram set clkfreq=216,108. Instead, just use 216 by itself and the firmware will use the correct backplane frequency.

    Here's info on valid frequencies:

    WRT54GL Overclock Frequencies

    Try the 30-30-30 procedure a few times. Another option is to try a JTAG cable and TFTP the firmware to the router.


    Go here for more info:

    Recover from a Bad Flash

    UPDATE: FattysGoneWild beat me to it...
     
  9. Hungry Man

    Hungry Man Networkin' Nut Member

    Thanks for the chart. I'm not going to bother OCing next time I don't think.
     
  10. Hungry Man

    Hungry Man Networkin' Nut Member

    I put it
    nvram set clkfreq=216

    I maybe put in 215 by accident.
     
  11. Hungry Man

    Hungry Man Networkin' Nut Member

    =\ Well these guides are all for XP and I'm on 7.


    Windows 2000/XP:
    1. Go to Start click on Run and type in control ncpa.cpl .
    2. Double click on the Local Area Connection that controls your network card.
    3. Click Properties under Local Area connection status.
    4. Click the Configure button. Then, click on the Advanced Tab.
    5. Click Connection Type (this may also appear as Media Type, Connection Speed, Mode, Link Speed, etc).
    The current default value should be set to "Auto sense" or "Auto".
    6. Change the value of this option to 10Base-t, half duplex mode (usually the lowest possible option).
    The wording of this value may also vary, depending upon the make and model of the Network Adapter.
    Other possibilities include 10T half, 10Mb half duplex, 10Mbps half, etc.
    7. Click OK after you made the change then click Close.


    I can't find the " Connection Type" under advanced.
     
  12. Hungry Man

    Hungry Man Networkin' Nut Member

    Nevermind found it. Is it ok if I just type out step by step what I do? It'll help me keep track/ I would appreciate the input. I'm going to short it.
     
  13. Hungry Man

    Hungry Man Networkin' Nut Member

    Ok I don't know how to set my card with a static IP on windows 7... I'm so used to xp.
     
  14. Hungry Man

    Hungry Man Networkin' Nut Member

    Ok so I can ping 192.168.1.2 and get a response but I can't telnet. I've been trying to ping 192.168.1.1.
     
  15. WRobertE

    WRobertE Addicted to LI Member

    From the FAQ on the polarcloud.com website:

    If you have a Buffalo router or a Linksys with a pushable Cisco logo, push the AOSS/Cisco button for at least 20 seconds, then telnet into the router on port 233.

    This should start the telnet daemon if it's not running so you can telnet into the router.
     
  16. Hungry Man

    Hungry Man Networkin' Nut Member

    How do I choose what port I use?

    I never realized I could push that... thank you lol
     
  17. Hungry Man

    Hungry Man Networkin' Nut Member

    "could not open connection to the host on port 23" =\

    Should my router be connected to my cable box? Or just my computer/ power outlet?
     
  18. WRobertE

    WRobertE Addicted to LI Member

    telnet 192.168.1.2 233

    Just put the desired port number after the host address, separated by space(s).
     
  19. Hungry Man

    Hungry Man Networkin' Nut Member

    Didn't work. I also can no longer ping it. When I ping 192.168.1.2 it gives me

    "reply from 192.168.1.101: destination host unreachable" before it worked and didn't give me this .101 part at the end, just .2.
     
  20. Hungry Man

    Hungry Man Networkin' Nut Member

    Trying to open up my router.... that thing does not want to budge...
     
  21. WRobertE

    WRobertE Addicted to LI Member

    DO NOT use the pin shorting method to attempt to recover your router. This will most likely permanently damage your router.
     
  22. Porter

    Porter LI Guru Member

  23. TexasFlood

    TexasFlood Network Guru Member

    See this thread for valid WRT54GL clock rates and the danger of the evil 215MHz clock rate. Near as I can tell it's time to invest in a JTAG cable. But check with Toastman, he's got the first hand experience.
     

Share This Page