On the road to debricking a v4...

Discussion in 'Cisco/Linksys Wireless Routers' started by jay_t, Aug 10, 2006.

  1. jay_t

    jay_t Guest


    I have a WRT54G v4 that I attempted to install HyperWRT on (to use WDS in my house along with my v2). However, I foolishly went ahead and installed the standard 2.1b1 HyperWRT, unaware of the Thibor version. Since v4 does not work with 2.1b1, I continually got "Upgrade are failed" messages. In my ignorance, I continued by installing dd-wrt (v23 I think) and installing HyperWRT 2.1b1 from there. Then my router was bricked. Wouldn't respond to pings, wouldn't reset, nothing. As a last ditch, I shorted some pins (which is a very divisive issue apparently - some people are for it, and some are madly against it). By shorting pins 16 and 17, I was able to receive pings again. Using the Linksys TFTP GUI (or just using the Linksys 4.30.5 Auto Upgrade Utility), I am able to send the router new firmware. However, it doesn't seem to work. Once the GUI successfully completes the transfer, the router doesn't respond to pings for a minute (presumably while it is loading and rebooting the new firmware image) and then doesn't do anything different. The Power LED continues to blink and the LED of the port connected to my machine stays illuminated, flickering off every second or so.

    Reset doesn't seem to do anything - I have held down reset in a variety of ways for many different durations, yet I never get any response from the router's LEDs. The only response I get is a couple of missed ping packets. Also, when I power cycle, the router is able to return pings (unlike before when I had to short the pins to get the router to even respond to pings). This tells me that at least some different firmware is loaded - which one, I do not know. Either way, I have tried a variety of firmwares through the Linksys TFTP GUI, including the stock Linksys firmware, HyperWRT G Thibor15c, and dd-wrt micro, with no luck. Perhaps the loading of HyperWRT 2.1b1 put the router in a strange state?

    I followed all the directions for changing the NIC and TCP/IP settings on my machine (which is a WinXP box, and I have a Powerbook at my disposal as well), but I think that the issue is unrelated to that since the image is able to correctly send to the router.

    I have scoured WRT54G forums as well as WRT54GL forums (since the L version is simply v4 hardware if I understand correctly), but have not been able to find an appropriate solution.

    My apologies if this doesn't fit in this forum - I was unable to post to the HyperWRT website forum for some reason. Anyone have any ideas? Thanks.

  2. RonWessels

    RonWessels Network Guru Member

    As I recall from when I had to de-brick my WRT, you have to wait a very long time between when the image is uploaded and the router reboots itself with the new firmware. It's very easy to believe that "it didn't work" and interrupt the process.
  3. Toxic

    Toxic Administrator Staff Member

    you could try TFTPing the micro version of dd-wrt (generic) to the WRT and see if that helps, it is much smaller and would take less time to transfer.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice