OpenWrt Forum Archive

Topic: WRT54G3G: Unable to flash with openWRT firmware

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

Hi guys,

I have a unit of this linksys 3G router with me. Current (original) firmware version on it is

  v2.00.18-EM, Dec. 4, 2006

according to the Router Status page on the router web interface.

Downloaded the latest firmware from

  http://downloads.openwrt.org/whiterussi … uashfs.bin

as well as the snapshot version from

  http://downloads.openwrt.org/people/nbd … uashfs.bin

I set the router to default factory settings, removed the vodafone 3G card from the router, then tried the following ways of firmware flashing:

1. Via the router web interface. Keep getting "Upgrade are failed" messages so gave up after several tries.

2. tftp method from both linux as well as windows command prompt. No dice here also as I keep getting "Invalid Password" after many tries. Probably because this 3g router has boot_wait turned off by default (according to a page on openWRT wiki). Tried the "Ping Exploit" method to turn on boot_wait which also failed.

I also tried using the "Linksys Firmware Upgrade Utility" downloaded from linksys website which tries to downgrade the router firmware version to 1.99.8. Even though the utility reported that it completed successfully, the firmware stayed as v2.00.18-EM. Tried flashing via the router web interface with the v1.99.8 firmware (the .bin file downloaded from linksys website) - same "Upgrade are failed" messages.

I found some posts on this forum where people have successfully flashed wrt54g3g routers with their own openWRT images so I thought what I am trying to do should be pretty simple. Did I miss something?

Does anyone have any advice for me? Any other ways of flashing this 3g router's firmware?

Thanks in advance.

Hi nbd,

Thanks for your reply.

I tried the image from the liink you posted but still no luck. Tried both upgrading from the web interface as well as using tftp.


$ tftp 192.168.1.1
tftp> binary
tftp> rexmt 1
tftp> timeout 60
tftp> trace
Packet tracing on.
tftp> put openwrt-wrt54g3g-squashfs.bin
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
sent WRQ <file=openwrt-wrt54g3g-squashfs.bin, mode=octet>
received ERROR <code=100, msg=Invalid Password !!>
Error code 100: Invalid Password !!
tftp>


I've got this feeling its nothing to do with the openWRT images. Could it be that this 3g router is locked in some way to prevent firmware updates?

Tried pinhole reset and then upload via web interface as well as tftp. Both methods failed.

Does anyone know if it's possible to flash the firmware of a WRT54G3G router that is currently using the original firmware version "2.00.18-EM, Dec. 4, 2006"?

Tried compiling and using linksys-tftp v1.21 to upload the firmware. Still not successful.

The packaging for this 3G router says its model is WRT54G3G.  However, the router's status page says

    Router Name :       WRT54G3G-EM

Is this difference significant?

Finally managed to upload a openwrt image I compiled myself to my 3G router.

The clue came from pogarek's posting:

  http://forum.openwrt.org/viewtopic.php?pid=35934#p35934

where he mentioned that he was able to upgrade his own problematic 3G router with a particular "WRT54G3G_1.99.8.beta-etsi_ETSI...." image but not any of the others. I downloaded that beta image and determined that it uses 'W3GN' as the code pattern.

So I compiled my own openwrt image but tagged the 3G .bin file with W3GN instead. Upgrade to openwrt firmware via the original linksys web interface went through without a hitch. Woot!

I'm beginning to think that this open-source freedom is for techies only. sad The OpenWRT wiki provides are "procedure" to choose the applicable firmware, but it's not clear to someone like myself. I'm looking for a table that says, if your model is Buffalo WHRHPG54, click this link. Then, that link would take me to a file that I can download. Then, in the router, which has a cool upload button, I magically upload the correct file that I downloaded. Is this file "flashing the hardware"? Heck if I know. Can someone "break it down for me"?

By the way, the used Buffalo that I borrowed from a friend has the following firmware installed. That's what the interface says.

DD-WRT v23 SP2 (09/15/06) voip

(Last edited by aakridge on 15 Jan 2007, 23:36)

cmk wrote:

...I downloaded that beta image and determined that it uses 'W3GN' as the code pattern...

You saved my life !

I had exactly the same firmware on my brand new WRT54G3G-EM v1.1 from amazon and was unable to flash any of the common firmwares including OpenWRT.
Via web interface it simply aborted with "Upgrade are failed" and the firmware installer claimed to have it successfully installed while it actually hadn't.
However, I simply took the latest EU firmware from the German linksys site and changed the first four bytes in the bin file from "W54F" to "W3GN".
That worked like a charm and I'm pretty pleased to have my Merlin XU870 card running with 2.2 MBit HSDPA :-)

The discussion might have continued from here.