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

OOOOPS, Just bricked a WRT54Gv2

Discussion in 'Tomato Firmware' started by PGalati, Mar 12, 2013.

  1. PGalati

    PGalati Network Guru Member

    In the process of configuring a Shibby test install of 108, I wanted to increase the clock speed. this is done via the tools area since shibby does not provide a overclock GUI. I had my stuff written down but for whatever reason I had written:

    nvram set clkfreq=225
    nvram commit

    Apparently this version was no too keen on 225. Previously running Toastman, selecting 250 would result in a 252MHz clock speed while maintaining stable. After entering the above commands, the router rebooted to a never ending blinking power button. The router does not recognize the reset button anymore, so a 30 30 30 does not help.

    I opened the router to reveal that the JTAG connector is soldered in, no holes. I soldered a header connector to the board and fired up EJTAG 3.0. When I perform a jtag -probeonly command, I get some good responses but the program stops at "Probing Flash at (Flash Window: 0x1fc00000) and stops.


    This link leads me to believe that all I really need to do is erase the nvram and let the router rebuild one, but I can't seem to get that far. the firmware is/was good but the nvram is probably corrupted/

    Any suggestions?
  2. GhaladReam

    GhaladReam Network Guru Member

    You did it wrong, unfortunately. When overclocking, there are 3 values you need to enter, not just CPU speed. See the link below (I know it's a DD-WRT page, but the same works on Tomato)


    Also, you're going to get very little performance improvement from overclocking an older router like that one. You'll likely end up getting crashes unless you add additional cooling. I would recommend getting a new router (Asus RT-N66U) if you need more horsepower.

Share This Page