I am hoping you guys can let me know if my WRT54GS v4.0 is salvageable from brick land.
I purchased the router only 2 weeks ago and immediately installed OpenWRT - openwrt-wrt54gs_v4-squashfs.bin
Everything was going fine until I had troubles NATing to an internal FTP server. Rather then deal with the head-aches of the /etc/firewall.user file, I decided to forgo openWRT and try hyperWRT instead. I knew taking the easy way out would cause me problems!
At this point I ran the following to begin the update. Please note that I did not run boot_wait=on in my NVRAM settings before doing this.
> wget http://www.example.org/hyperWRT.bin
> dd bs=32 skip=1 if=hyperWRT.bin of=hyperWRT.trx
> mtd -e linux -r write hyperWRT.trx linux
Upon rebooting, my power light was flashing repeatedly and would not respond to my pings. My router was bricked.
After following these instructions to short ping 15-16 I was able to revive my router to at least respond to my ping.
http://www.linksysinfo.org/modules.php? … amp;pid=33
The instructions told me to power-cycle my Linksys to TFTP the HyperWRT.bin file to it. This failed repeadely with a Invalid Password error. So I tried the latest linksys.bin file.
> TFTP -i 192.168.1.1 PUT WRT54GSV4_1.05.2_US_code.bin
> Error on server: Invalid Password!!
I also tried the Linksys-Setup-Wizard 2.0 which is similair to the earlier Auto Update Utilities from Linksys. This also failed givig me the error message: Invalid Password.
ftp://ftp.linksys.com/pub/network/WPS54 … rd-2.0.zip
I believe I am receiving the invalid password because my NVRAM is not giving me the time to flash it. This is probably happening because I have never set my boot-wait to ON.
Can someone tell me if I am screwed?
(Last edited by 5t3v3 on 3 Feb 2006, 03:49)