OpenWrt Forum Archive

Topic: Unable to flash firmware

The content of this topic has been archived on 19 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I have a problem with my WRT54GS (no model number specified, so I suspect it's a version 1.0). I had a previous version of WhiteRussian running on this and decided to flash 0.9. I used the tftp way to flash the firmware. After seemingly successfully flashing the firmware the power led lit up and the dmz led flashed. The ping responses from 192.168.1.1 turned into destination unreachable. The first time I rebooted the router after a couple of minutes and then it just went back in the corrupt firmware state (power led flashing, dmz led slowly turning on and off).

So now, no matter what firmware I am seemingly able to flash, just turns the router into the same state. I've tried Kamikaze, Whiterussian and the stock firmware for WRT54GS 1.0. Nothing brings back my router.

I have of course also tried failsafe mode, but I don't see how this can help me when the router clearly reports of a bad firmware.

So what are my options? What can I do to revive my router?

Are you tftping the firmware in 'binary' mode instead of 'ascii'?  Sounds like you're tftping the images up in ascii mode.

Oh, I'm definitely transferring in binary mode. I've done this multiple times, but the same happens:

marius@bounty:~$ tftp 192.168.1.1
tftp> binary
tftp> rexmt 1
tftp> timeout 60
tftp> trace
Packet tracing on.
tftp> status
Connected to 192.168.1.1.
Mode: octet Verbose: off Tracing: on
Rexmt-interval: 1 seconds, Max-timeout: 60 seconds
tftp> put openwrt-wrt54gs-squashfs.bin
sent WRQ <file=openwrt-wrt54gs-squashfs.bin, mode=octet>
received ACK <block=0>
sent DATA <block=1, 512 bytes>
....
sent DATA <block=3027, 0 bytes>
received ACK <block=3027>
Sent 1549312 bytes in 2.2 seconds

Then the leds change to a blinking power led and a lit dmz led. I leave the router in this position for a while (I've waited up to 30 minutes) and then cycle the power, and I end up back into the aforementioned state (blinking power led and dmz led going on and off).

The discussion might have continued from here.