WL-500g Premium died After Upgrading Firmware

[Erusletum]

No I cannot ping it, it times out. I had changed the IP address of the router and it does not respond at the new IP address nor at the factory default IP. (And yes I used static IPs from within the same network to test each individually.)

I'll try adding the bridge before the power and see if that works.

[bitbrain2101]

Changing the IP adress of the router seems to be a dangerous task, even with asus original software. That also was the reason for my problems.
With pin9 to ground you pull down one adress line of the nvram so at boot the firmware thinks that nvram content is corrupted and loads default settings. You have to power off/on again after that.

Edit:
It is only a feeling, but I think it is a good recommendation to change the LAN IP of the router as a single task, no other settings changed at the same time.

[dexluv]

hello
i have a problem with my 500gp i can not connect to it, the power led is on and the link leds are on if i put a cable,
4 LAN leds all light up then go off and if a LAN cable is plugged into any ports that led stays on same with WAN , NO AIR come on at all at any moment

when i put it in restoration mode i can ping 192.168.1.1
i tried to put:
clear nvram
restore
asus latest firmware
both by tftp and asus restore firmware and i couldnt see an improve?
what can i do?

[wpte]

I guess you already tried resetting the settings with the reset button?
sometimes firmware doesnt want to be flashed when old settings are available.

if it all just doesnt work... I guess the "pin9 trick" is the only option

[cbmarkjennings]

I've been reading about some of the workarounds when one bricks a router but I'm not sure it is bricked. I just got my WL-500gPv2 router. Here's what happened. I hope somebody can help.

1. I started out trying to load tomato. I booted the router up into restore mode. The power LED was flashing and I TFTP'd the lastest Tomato Firmware 1.23 to the router. As soon as the file started, the power LED turned off (not flashing). I waited about 7-8 minutes and power-cycled the router
2. It came up with the power LED on but there was no connectivity and I couldn't ping 192.168.1.1 from my static 192.168.1.2 on my laptop.
3. Rebooted in Restore mode and I could ping the router again - but, again, no other connectivity (telnet, web, etc.) and I couldn't get out.
4. Tried to load Tomato again with the same results.
5. Got the Asus Firmware Restoration software and the latest Asus Firmware (1.9.7.7). Booted the router into restore mode and loaded the firmware with the Asus program. It said it was a success. I waited 15 minutes but no luck whatsoever.
6. Rebooted. Still could not access the router. Tried again with the same result.

So, I can ping the router (and apparently TFTP) when it is in Restore mode but I can't do anything when it boots to the normal mode. Is this a symptom of a bricked router? What should I do next?

[OVERKILL]

I have a WL-500W here that I put DD-WRT 2.4 SP1 on after it had randomly frozen one weekend.

It was fine for a couple weeks then locked up. A power cycle was necessary to get it functional again. This then occurred a few times again. Then the last time it happened (Friday) it simply goes to solid LED's on the LAN ports. No illuminuation of the PWR or WLAN LED's.

I tried the PIN 9 method.

Nothing.

Pulled the wireless card out.

And using the 30/30/30 or the Pin-9 method, the switch will function, but nothing for the PWR LED.

Seems to be a total brick now.......?

[wpte]

is your router quite hot after these crashes?
might be a burn or something...

[OVERKILL]

is your router quite hot after these crashes?
might be a burn or something...

No, it is not hot at all.

[wpte]

I wouldn't have a clue then

[dreKion]

Hello, I bricked my Asus WL-500W.. the same...

I tray pin9 method....

Cable to DC



Cable to PIN9



After:



The leds LAN1,LAN2,LAN3,LAN4 and WAN are turned on...

[bkiss]

I will describe below shortly what happened to us.

We have 2 pcs. of asus 500 G Premium. (now both of them is Brick - or
switch - whatever)

My friend wanted to put back the original firmware from asus, he has
DD-WRT - 24 sp1 before, but it was too difficult for him to get the
printer workink.

We use:
1. the original firmware restoration tool from asus,
2. Enter in failsafe mode, restore button and power cord in
3. Upload the file: WL500gp_1.9.7.7_TW.trx
4. Wait until the software finishes about 5 min.
5. after we cut the power and we put it back, the router goes back
automatically in failsafe mode (power led slowly blinking)
6. We use the restoration software again to put the same file again.

7. after this the router it's like a switch. if we connect anything to
the ethernet port the led's are ok, but power led is off, and air is
dimmed.

We have tried already to get in failsafe mode:

1. restore button + powercord in ---> nothing
2. Pin 9 to ground + powercord in (wait) --> nothing
3. tryed also 10, 9/10, 16, 17, 16/17 but nothing
4. we made a connection with max232 -> tx0 rx0 gnd hyperterminal
115000, 8, n, 1, n ---> at boot time we cannot see nothing



We have the same problem with another router 500 gp, but with this one
we proceed different (before it was ddwrt 2.4.sp1):

1.after the first flash WL500gp_1.9.7.7_TW.trx ---> failsafe (we get the power led flashing)
2. put clear-nvram.trx
put recover.trx

after this THE SAME simptoms like you have read before.


If you have any suggestion or solution please let us know.

[skyraven]

Hello,

Did you find any solution for this ?

I'm in the same "club" and I even attached a serial console to the router..but issueing nvram erase from that ..makes the console freeze => requires reboot
also I see this in the boot seq:
Device eth0: hwaddr 00-1E-8C-72-2E-CE, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
Reading :: TFTP Server.
Failed.: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Optionsnull)
Loading: . 0 bytes read
Failed.
Could not load flash0.os:: Error

Of course..IP is not pingable via any method like:
- after boot
- hard-reset
- 30/30/30 method
- keeping ping on, then power off, ping on, power on..etc
I don't even get by using a Linux, any arp reply from the router..seems like it's as solid as a wall.

[laowai]

Good day,

I have a problem: on the console last what I see is:

Null Rescue Flag.
: Device not found

There is no difference which button pressed or not pressed. The last is ": Device not found". It happened after I just a click save and reboot on dd-wrt web gui.

How can I reanimate this device?

Thank you.

[Lesiuk]

Just restart router.

[laowai]

it didn't help.

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: 67108864 KBytes

Total memory used by CFE: 0x80800000 - 0x8089BA00 (637440)
Initialized Data: 0x80831B70 - 0x80834250 (9952)
BSS Area: 0x80834250 - 0x80835A00 (6064)
Local Heap: 0x80835A00 - 0x80899A00 (409600)
Stack Area: 0x80899A00 - 0x8089BA00 (8192)
Text (code) segment: 0x80800000 - 0x80831B70 (203632)
Boot area (physical): 0x0089C000 - 0x008DC000
Relocation Factor: I:00000000 - D:00000000

Device eth0: hwaddr 12-34-56-78-90, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.

---> IT STOPPED HERE

: Device not found


It does not matter button pressed or not.