Posted: Tue May 29, 2007 12:48 Post subject: WL-500gP bricked: Power LED blinking, no Ping
Hi folks!
After months of perfect service, my Asus running dd-wrt didnt supply IP Adresses to new clients (as dhcp server stopped). As i was in a hurry, i just rebooted the device - but unfortunately it didnt come up again :-(
When powering, the Power-LED keeps blinking, LAN-Ports LEDs are flashing/lightening as supposed when a cable is connected. I can't ping the box (with fixed, static IP) - even not during boot-up.
I tried the shortcut pin 9 - method as described on another thread - no chance.
As i cannot ping the router, i cant fix it via tftp or recovery-tool.
Sure... but resetting seems to have no effect at all: The device keeps blinking its power-LED and no pings are beeing returned...
(tried resetting while in power as well as during connecting to power... 10secs, 30 secs whatever: no change of the state)
I bricked my Premium several times but was always able to unbrick it by using the shortcut trick. The last time, however, this didn't work.
I don't know how to connect a jtag to the Premium and as far as I know not anyone else on this forum.
It seems one can access the router using its serial interface. However, the problem with the serial interface is that it works on TTL-level, which is 5 Volt. The RS-232 interface works @ 12 Volt. Therefore you need a Serial to TTL-converter.
I bricked my Premium several times but was always able to unbrick it by using the shortcut trick. The last time, however, this didn't work.
I don't know how to connect a jtag to the Premium and as far as I know not anyone else on this forum.
It seems one can access the router using its serial interface. However, the problem with the serial interface is that it works on TTL-level, which is 5 Volt. The RS-232 interface works @ 12 Volt. Therefore you need a Serial to TTL-converter.
Dude69 clearly stated that his router couldn't be revived using the recovery tool.
This according to my own experience.
When I bought my Premium I had the bad luck to flash it with a bad version of the most current firmware at the time....
I only resorted to shortening if all the rest failed...and it recovered several times this way....
Nowadays I always flash it using the CLI....
Code:
write dd-wrt.bin linux
_________________ Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge
For a bricked linksys I made myself a jtag last week and that worked like a bliss.
It's a shame that I can't use that cable for my Premium _________________ Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge
Hyperterminal (using Xon/Xoff on the correct COM6 port of the cable) says that i am connected, but when i power up the router i get this answer (look at the attachment) :-)
Oh thanks man! Now I am in CFE... now its time to read into more information about further actions... :-)
Code:
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: ¤T 12¤ë 14 15:54:18 CST 2005 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.23.0
rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
CPU type 0x29006: 264MHz
Total memory: 33554432 KBytes
Total memory used by CFE: 0x80800000 - 0x8089B590 (636304)
Initialized Data: 0x80831700 - 0x80833DE0 (9952)
BSS Area: 0x80833DE0 - 0x80835590 (6064)
Local Heap: 0x80835590 - 0x80899590 (409600)
Stack Area: 0x80899590 - 0x8089B590 (8192)
Text (code) segment: 0x80800000 - 0x80831700 (202496)
Boot area (physical): 0x0089C000 - 0x008DC000
Relocation Factor: I:00000000 - D:00000000
Device eth0: hwaddr 00-17-31-DC-08-39, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
Boot program checksum is invalid
Hello!! Enter Rescue Mode: (Check error)
Update: Still no idea how I can get a new firmware onto the device... tftp server cycles endless with timeouts on the console... - i cant pint the box from external or internal. But when I try the recoverytool, at least the cycling messages are disrupted:
