Gargoyle Forum

Successfully installed v1.4.5 on WRT54GL and tried to update via web admin to 1.4.7...
Router unresponsive, tried to telnet into it to no avail, (http://wiki.openwrt.org/doc/howto/generic.failsafe)
I got only power led blinking rapidly.

It takes a few minutes (during which the power light will blink) for the router to initialize (filesystems created, ssl keys generated, etc.). Make sure you wait at least 5 min and see if the router boots normally. Otherwise this is how I get into failsafe mode.

Set your computer to have a static ip address of 192.168.1.100, subnet 255.255.255.0 and gateway 192.168.1.1. You pulled the power plug on the router, then plugged it back in. Immediately start pressing over and over the Cisco logo button on the front of the router. Once the power led is rapidly blinking, telnet should be enabled. Telnet in (no password required) and run the command firstboot from the shell. Then power cycle the router (i don't know if the reboot command works or not from telnet failsafe). Again you will have to wait about 3 min for the system defaults to initialize, during which the power led will rapidly blink. When the power led stops blinking, you should be good to go.

mix wrote:It takes a few minutes (during which the power light will blink) for the router to initialize (filesystems created, ssl keys generated, etc.). Make sure you wait at least 5 min and see if the router boots normally. Otherwise this is how I get into failsafe mode.

Set your computer to have a static ip address of 192.168.1.100, subnet 255.255.255.0 and gateway 192.168.1.1. You pulled the power plug on the router, then plugged it back in. Immediately start pressing over and over the Cisco logo button on the front of the router. Once the power led is rapidly blinking, telnet should be enabled. Telnet in (no password required) and run the command firstboot from the shell. Then power cycle the router (i don't know if the reboot command works or not from telnet failsafe). Again you will have to wait about 3 min for the system defaults to initialize, during which the power led will rapidly blink. When the power led stops blinking, you should be good to go.

I tried to no avail... Power LED light rapidly flashes ALL the time, when telnet 192.168.1.1 no response although when I ping it returns:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Seems pretty odd you can ping the router. It's not bricked. What program are you using for telnet? putty? Have your tried tftp to upload the gargoyle_1.4.7-wrt54g-squashfs.bin firmware again?

mix wrote:Seems pretty odd you can ping the router. It's not bricked. What program are you using for telnet? putty? Have your tried tftp to upload the gargoyle_1.4.7-wrt54g-squashfs.bin firmware again?

------------------
I did set ip address to 192.168.1.100, subnet 255.255.255.0 and gateway 192.168.1.1,,, but LED light always as I said flashes and I used CMD as admin under Vista, "ping 192.168.1.1" and "telnet 192.168.1.1"

http://www.dd-wrt.com/wiki/index.php/Re ... _Bad_Flash

You can recover via TFTP

It's harder to recover with Vista / Win 7 because of the
upgraded TCP/IP stack and Windows turning off the ethernet port
when the router is turned off

Easier if you can borrow a Windows XP machine or you may have
to get a Linux Live CD (Mint, Ubuntu, etc) and boot with that,
then do the tftp recovery that way.

DoesItMatter wrote:http://www.dd-wrt.com/wiki/index.php/Re ... _Bad_Flash

You can recover via TFTP

It's harder to recover with Vista / Win 7 because of the
upgraded TCP/IP stack and Windows turning off the ethernet port
when the router is turned off

Easier if you can borrow a Windows XP machine or you may have
to get a Linux Live CD (Mint, Ubuntu, etc) and boot with that,
then do the tftp recovery that way.

Thank you! Just used borrowed netbook to "ping -t -w 2 192.168.1.1" and as soon as it successfully pinged, used "tftp -i 192.168.1.1 PUT dd-wrt.v24_mini_wrt54g.bin" and it all good.
Thanks

Hi, I have a similar problem. After trying to upgrade to the latest version, my router appears bricked. The power light rapidly flashes all the time, and cannot get a ping from any port on it. I have tried telnet firstboot command, and tried pinging from Ubuntu live.

Any ideas?