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

Firmware update failed? (can't connect at all)

Discussion in 'Tomato Firmware' started by JaeZTT, Jun 17, 2008.

  1. JaeZTT

    JaeZTT Addicted to LI Member

    Hi everyone,

    I tried updating my WRT54G v1.1 with DD-WRT to Tomato. I downloaded the firmware from polarcloud.com and unzipped it. I logged into and went to the update section and selected the WRT54G_WRT54GL.bin.

    It was updating fine for a few minutes, then something came up and told me to click next to continue. I clicked next, and then the page timed out. I thought it was already done so I just exited out.

    But now, I can't even connect to the internet or with the router connected. I tried resetting both the computer and the router. In network connections, it says "limited connectivity" and "You might not be able to access the Internet or some network resources. This problem occurred because the network did not assign a network address to the computer."

    Any recommendation on what I can do to get the router working right? I'm not sure if it's bricked or not. All the LED's look fine. I tried to read through the FAQ's but didn't really see anything.

  2. LLigetfa

    LLigetfa LI Guru Member

    Did you try a 30 second reset? You might be able to TFTP the image onto it if you hard code your IP.
  3. JaeZTT

    JaeZTT Addicted to LI Member

    I tried the 30 second reset. But I don't really know what you mean by the second part. I'll try searching for it...
  4. LLigetfa

    LLigetfa LI Guru Member

    Power off the router.
    Set your PC to and plug it into a LAN port.
    Go to Start > Run > CMD
    ping -t

    Start a second CMD prompt and arrange it so you can see the first one.
    Type the following but don't hit enter yet:
    tftp -i put WRT54G_WRT54GL.bin

    Power up the router and when you get a ping response, hit [enter]

    Hopefully you will see it transfer. After it is done leave it for a good 5 minutes.
  5. JaeZTT

    JaeZTT Addicted to LI Member

    I've read this before, but how do i set my pc to
  6. JaeZTT

    JaeZTT Addicted to LI Member

    I think I figured out how to set the PC to the IP, but it's not working.

    I went to the TCP/IP properties for my LAN card, set IP to and subnet mask to 255.255.0. Then I followed your instructions, and while I was getting ping response I put in that other code.

    Then it came up with this error:

    tftp: can't read from local file 'WRT54G_WRT54L.bin'

    Do I have to set the location of it first?

    ^ I answered my own question...

    I tried it, and first time, I saw that it timed out in the first 10 seconds. It said this in both command windows. But I left it on anyway, and it started pinging again in a bit. But no luck.

    Then I tried it again, just in case...this time, on the pinging command window, it kept on pinging but the tftp window still stopped in a minute and said Timed Out.

    So I'm not sure what to do now...
  7. JaeZTT

    JaeZTT Addicted to LI Member

  8. LLigetfa

    LLigetfa LI Guru Member

    The timing is critical. You need to start the TFTP transfer right after the first ping goes through. If time is lost with your NIC coming online, you might buy more time by putting a switch between the router and the PC.
  9. JaeZTT

    JaeZTT Addicted to LI Member

    Hmm..I just tried again, and it said transfer successful. But I still can't connect to anything. I tried rebooting it, and restarting the computer but it's the same thing...
  10. LLigetfa

    LLigetfa LI Guru Member

    Can you still ping by the same IP after the router boots? Can you telnet to it?
  11. JaeZTT

    JaeZTT Addicted to LI Member

    Hmm this is what's going on.

    If the tftp is sucessful, it won't ping anymore. But if the tftp is not successful and it says request timed out or something, it'll start pinging pretty consistently again.

    BTW, when it is successful it says "transfer successful: 2782208 bytes in 3 seconds, 927402 bytes/s".

    And if by telnet you mean logging into the router through, I can't get that to work at all.
  12. LLigetfa

    LLigetfa LI Guru Member

    After the TFTP completes, you need to leave the router alone to do its thing. This can take as long as five minutes.
  13. pharma

    pharma Network Guru Member

    This part is true. When I flashed my WRT54G v1.1 it was basically using the same procedure. One thing I also did was the first time I wanted to use Tomato, I flashed back to the original Linksys firmware before flashing to Tomato.

  14. TheGIZ

    TheGIZ Network Guru Member

    And when you still can't reach it via the ping?

    After 20 mins of trying the directions...

    I tired tftp2.exe and it fixed it!!!
  15. JaeZTT

    JaeZTT Addicted to LI Member

    Yeah, I've left it alone for like 10 minutes, and it still wouldn't work. Anything I'm doing wrong or should be doing?

    GIZ, what do you mean by tftp2.exe?
  16. mstombs

    mstombs Network Guru Member

    Also after successful flash try connecting your PC to all LAN ports and the WAN port, there's a chance Port 1 thinks its the WAN port till you have reset to tomato defaults.
  17. fyellin

    fyellin LI Guru Member

    I never did understand that. How does putting a switch between the router and the PC buy you more time?

    (I'm not disagreeing or arguing. I really don't understand why the switch helps.)
  18. LLigetfa

    LLigetfa LI Guru Member

    A switch or hub would hold the link status so time is not wasted on the NIC negotiating link speed and then the OS delaying in making the NIC available.
  19. mstombs

    mstombs Network Guru Member

    It helps because your PC doesn't see the Ethernet connection breaking. My PC is particularly slow at noticing when cable is put back which means it is impossible to hit the short tftp window on devices that need this (I haven't had to on my WRT54GS yet, but have done this plenty with modems I'm hacking). On an AG241 I had to hook up a serial console cable to find I was actually tftping the running router (which was about to crash) not the bootloader.

Share This Page