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

WRT54G v1.1 dead

Discussion in 'Cisco/Linksys Wireless Routers' started by dll2002dll, Aug 3, 2009.

  1. dll2002dll

    dll2002dll LI Guru Member

    Hi Guys,

    I was running Tomato 1.25 on my router and it was working fine until one day I wanted to login to it to make some changes, I realized I couldn't login to it anymore via http or ssh. I then tried resetting the router with the reset button and I ended up with the router being not responding to pings.

    I then tried to upload the firmware using the tftp right after the reboot, which worked and successfully updaloaded the firmware, but when I rebooted the router and tried to ping, I got a weird ping response, the response time varies too much and still no http/ssh access:

    Reply from 192.168.1.1: bytes=32 time=84ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=326ms TTL=128
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=189ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=432ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=53ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=295ms TTL=128
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=158ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=401ms TTL=128
    Reply from 192.168.1.1: bytes=32 time=22ms TTL=128

    I then tried to upload the firmware by shorting pin's 15/16 method, it successfully uploaded the firmware but the same ping response time and no http/ssh access.

    Since then I tried to upload almost all firmwares (openwrt/dd-wrt/tomato/linksys official), but all gave me the same ping response time and no http/ssh access.

    I also tried 30-30-30 reset routine, but still the same results.

    Anybody can help?

    Thanks.
     
  2. mstombs

    mstombs Network Guru Member

    The variable ping suggests it is stuck in a reboot cycle booting and crashing. Assuming it has not been damaged by pin-shorting etc likely the only way to recover is to build a JTAG interface and erase the nvram.
     
  3. dll2002dll

    dll2002dll LI Guru Member

    Thanks mstombs, can you point me to a link to build the JTAG for v1.1?
     
  4. dll2002dll

    dll2002dll LI Guru Member

    Issue has been fixed, no need to JTAG.

    After I came to know that the only way to recover my router is to do a JTAG, I said lets look at the router board closely, so I grabbed a halogen lamp and a magnifying glass, examining the board closely I realized that the pins 15/16 are distorted and looks like touching each other (must have happened when I was trying to recover it by shorting pins 15/16), I picked up a needle and scratched the space b/w pins 15/16, so that it no longer touches each other.

    After that I turned the router on, and bingo, everything is fine.

    Thanks everybody.
     

Share This Page