Hi
Sorry for the newbie /long post but I've been struggling with this for 20+ hours and feel like breaking the damn router. I've got v1.0 WRT54GS. I was looking to install  the sveasoft firmware (have 6.0rc3 installed on another WRT54G and working fine).
1) I updated the router to 3.37 (Linksys firmware) (first flash had failed)
@) Then tried updating it to SveaSoft's 4.0 and 6.0 without any success.
3) Finally managed to install OpenWRT, the command line was a bit more then I had bargained for :oops: . I basically wanted to use OpenWRT to upgrade to Sveasoft since the Linksys firmware wasnt accepting the updates via the web interface and tftp was working but changes werent saved.

4) After OpenWRT was installed tftp died (timeouts... I ran ethereal and it was spitting out destination unreachable messages)
5)  I tried disabling iptables and trying again with no luck (but was able to ping now).
6) I tried the hard reset but somehow the reset button seems disabled, pressing it does nothing
7) According to the manual I used wget to pull a firmware to /tmp and then dd to strip off the first 32 bytes and an mtd write, unfortunately kept getting bad crc errors (on multiple firmwares)

Commands I used are

wget -O /tmp/WRT54GS_3.17.4_US_code.bin http://www.neduet.com/WRT54GS_3.17.4_US_code.bin

dd bs=16 skip=2 if=WRT54GS_3.17.4_US_code.bin of=WRT54GS_3.17.4_US_code.trx

mtd write /tmp/WRT54GS_3.17.4_US_code.trx linux && reboot

I also tried updating the ipkg list but the file in which I had to add (/etc/ipkg?) other package addresses was read only with no chmod being available

Is there some other way to update the firmware to a Sveasoft firmware or am I doing something wrong? Any and all help would be greatly appreciated.

Thanks

Hi,

Sounds like you're struggling like I was.. For some 50-odd people to read this and not give you the slightest advice is disappointing.

OK, I'm going to assume you haven't read the OpenWRT user guide, or FAQs.

The first thing you need to do is get tftp working again, I reckon.  It sounds like you still have access to the WRT, console-wise, so that should be easy enough.  From the OpenWRT console, type:

nvram set boot_wait=on

Then, verify with:

nvram get boot_wait

it should return with: "on"

then type:

nvram commit

wait for that process to finish, it'll take a few seconds...Then you'll have tftp again.  I suggest you get it back to a Linksys firmware first, to verify it's all good.

Read the "Getting Started" tips here

http://www.openwrt.org./GettingStartedTips

To learn more about OpenWRT.  I am a Linux midget but now have my WRT singing!  Actually I find it to be more robust than the Sveasoft, and much leaner. Give it a try!!

Hope this helps

Cheers,
J

Sorry for dropping off the face of the planet but kinda got tied up in other stuff. Am attempting this again, I've tired new/old openwrt firmware and new/old linksys firmware. I tried tftping and get the following messages

putting WRT54GS_2.06.1_US_code.bin to 192.168.1.1:WRT54GS_2.06.1_US_code.bin [octet]
sent WRQ <file=WRT54GS_2.06.1_US_code.bin, mode=octet>
sent WRQ <file=WRT54GS_2.06.1_US_code.bin, mode=octet>

After which nothing happens.

with MTD i get bad crc errors

DD command used
C:\cygwin\bin>dd bs=16 skip=2 if=WRT54GS_2.06.1_US_code.bin of=WRT54GS_2.06.1_US_code.trx

MTD Session
root@OpenWrt:/# mtd write /tmp/linux.trx linux && reboot
writing /tmp/linux.trx to linux
freeram=[20041728] bufferram=[860160]
The free memory is enough, writing image once.
sum=[3182592]
/tmp/linux.trx: Bad CRC

Any ideas? I just want to get rid of openwrt somehow

(Last edited by syyid on 19 Apr 2005, 04:11)

tftp won't accept files bigger than 3 mb. flashing to sveasoft's (free) satori, booting it, then flashing to the original firmware via the web interface should do the trick. if satori supports the wrt54gs unit.

if not, you'll have to do it from the openwrt's cli. use the search feature (on both the forum and the wiki), there should be instructions somewhere.

Thanks for the tip, I tried that with the same problems, timeouts and the mtd giving bad crc errors . What CLI commands are you referring to, I couldn't find any references in the forum. Thanks again

pretty much the ones you used. wget/dd/mtd

I tried disabling the firewall (iptables flush) but no luck also the newest openwrt gs binary (2.3 megs) is causing the same timeout prob . Also tried tftping while resetting the router , with both 100 mbps/full duplex and 10 mbps/half duplex

updated the router using openwrt-gs-code.bin from http://www.wildcatwireless.net/wrt54g/. I converted it to a trx n did a wget n mtd. Worked without a crc error but now i can't login via telnet nor does the router route internet packets. i can ping 192.168.1.1 but thats it

Try failsafe mode, and if it still does not work, you will probably have to build a serial adapter or a JTAG one.

It apparently has ssh working but the connection is closed (apparently an incorrect login or something), is there a default ssh login/pass?

Hi Guys,

This is a long shot, but has anyone any advice for this bricked router problem? After flashing a corrupt firmware, the WRT54G v2.2 became unresponsive. Telnet failed and I could not ping it. So after all the usual contingencies, I shorted pins 15-16 and was able to ping the router. Then I was also able during the 3 sec failsafe period to TFTP the original Linksys firmware up into the router (in binary mode). The TFTP finished and the router rebooted, after which all the normal lights came back on (power, LAN and Wireless). BUT I cannot ping the router on default IP 192.168.1.1 and I can't telnet into it, neither can I access a Linksys web interface. It appears as it was before the TFTP.

If anyone has any advice on this please let me know. I don't really want a new blue and black paperweight, but as things are going at the moment, that is what I am going to have.

Cheers,

Niall

It sounds like your using netkit's tftp client, i was unable to load any firmware with it.

try using the advance tftp client it works well, but be sure to plug the router in quick after executing
the put command or it will time out

from:
http://openwrt.org/OpenWrtDocs/Installi … WrtDocs%29

Advanced TFTP commands:

atftp
tftp> connect 192.168.1.1
tftp> mode octet
tftp> trace
tftp> put openwrt-g-code.bin

This should work for any firmware

(Last edited by captainsmock on 10 May 2005, 01:38)

I noticed you were using cygwin.. Just so that you know, there's a tftp client with Windows 2000 and XP. It's command-line only, but it worked first time..