WL-500g Premium died After Upgrading Firmware

Hey guys,

yesterday I tried to flash my router with olegs firmware (previously dd-wrt installed) so I uploaded clear-nvram.trx via tftp at first.
Having finished i uploaded the trx from oleg, but it seemed as if it didn't work so I uploaded the dd-wrt trx again and recognized that all settings were still the same, as if the clear-nvram did not work.

So I tried it using the firmware restauration tool from asus, but after flashing with that the router seems to be bricked.
The power LED does not flash anymore (but lan LEDs do), even if I press the reset button while power cycling.

I even tried to ground Pin9 but it didn't work either.
Am I doing something wrong? Or could there be another possibility?
I'm using a small cable to ground the pin but power led doesn't flash after power cycling and pressing reset button again.

I'd be happy If anyone could help me..

Kind regards,
Joschi

Quote:

---

Originally Posted by JoschiBK19

Having finished i uploaded the trx from oleg, but it seemed as if it didn't work

---

I've had a similar problem in the past, although I didn't migrate from dd-wrt.

At first it seemed that the firmware-flash hadn't worked, but it needed a couple of (2) reboots in a row, to get it working, after that, I haven't been able to replicate the problem.

Always, after a change of firmware do the following:

Push reset button, connect power and wait for 30 seconds, disconnect power and keep pushing for the reset button for another 30 secs. Connect power, and after 30 more seconds release the reset button. Router should reset and since the NVRam is completely empty reboot. Thing is that sometimes some param's are still saved in NVRam and gives a checksum error.
Give it 1,5 minute of your life:p!


Ed

hi,

thanks for your replies, but 30/30/30 didn't work for me either... :(

Is there any other possibility?... really tricky ^^

Kind regards
Joschi

Check if the CPU is really getting hot in 20 seconds. If it stays on a low-temp.....and before the dustbin, try to short the other pins and see what's happening. There has to be a reboot pin, and i think a combination of reboot pin and shortage of pin 9 or 17 during reboot sometimes seems to work.

It's a bit tricky, but it's what you asked for:cool:.

If the cpu is getting really hot, there's some short circuit on the board->dustbin!


Ed

Ok sounds like I have to pray for another 2 arms ^^

Well its not exactly what I asked for ;)
If there's another easier way, I'd like to use this way.

Tomorrow I'll report about my success... ;)

Hello,

I have some problems with my router. After unsuccessful upgrading official firmware, when I connect power cable the power led flashing. It doesn't matter if I press and hold restore button or not. When I use asus firmware restoration after upload (it shows 100%) and gives "Upload system recovery file failed: transfer cancelled". Computer doesn't recognize router. Ping doesn't reach it.

Have You got any ideas, what can I do with it?:confused:

search forum for:

pin 9 trick

Quote:

---

Originally Posted by avberk

search forum for:

pin 9 trick

---

Thanks, but I can't find how to open router box to apply pin 9 trick :/
There are some screw or sth?

There is no question I found this screw:)

thanks

Remove the rubber feets:

http://www.xbitlabs.com/articles/net...premium_2.html

This is what happened: i was running dd-wrt firmware on WL-500g and after changing some settings and rebooting it didnt reboot any more.

Simptoms: After powering it on Power LED blinks rapidly 2-3 times and stays on, 4 LAN leds all light up then go off and if a LAN cable is plugged into any ports that led stays on. no AIR or WAN LED's come on at all at any moment. The ruter doesnt respond to pings etc, and i cant force it into recovery mode.
The only thing that happens is if i try to ping it via cable, the corresponding LED blinks indicating traffic, but no reply from the box.

Please help :(

Hardware revision is V2.40 with 4702 processor and MX flash chip 29LV320ATTC-90

Thank you in advance :)

Tried to flash dd-wrt mega last night it seemed to work OK set up all the setting and pressed apply button. After reboot the router stopped working now all I have is the LAN and WAN lights blinking on and off.

Using the restore button I have:

1. Tried using the Asus restore tool but says invalid IP address
2. Tried using a manual ip address but Windows says cable is diconected(tried different wires)
3. Tried tftp but gives timeout.

Router seems to enter restore mode ie blinking power light, but will not give an ip. Help please

for the asus restore tool you need some patience mostly
the easiest way is if you can restore the router to factory defaults, if not... it might be a bit tricky
be sure you have the cable in LAN port 1 of the router.
wait till you get a valid ip, like 192.168.*.* (* can be anything)
be sure to turn of your firewall temporarily
try to upload the file with the asus tool...

if this doesn't work, search the forums for the so called "pin 9 trick"
but if you do this, you will void your warranty.

So this is my third Asus WL-500g Premium.

I installed some firmware and some of my settings bricked it. When I hold in the reset button and plug in the power the power LED does not flash. I tried the Pin 9 trick to get recovery mode back but it is not working.

Any ideas?

Or perhaps I am doing pin 9 wrong? I have the power on and connect pin 9 via a wire to the metal wrap around where the power comes into the circuit board for about 30 seconds. I notice NO CHANGE in the power LED during this time.

I think pin9 should be connected to ground first, then apply power. Can you ping the router ? I could re-animate my WL-500GP with a "clear NVRAM" firmware flashed with tftp in cmdline window, but you need a ping response.

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.

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.

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?

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:(

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?

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.......?

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

Quote:

---

Originally Posted by wpte

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

---

No, it is not hot at all.

I wouldn't have a clue then:confused:

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

I tray pin9 method....

Cable to DC

http://www.estoyaburrido.net/asus/Im.066.jpg

Cable to PIN9

http://www.estoyaburrido.net/asus/Im.064.jpg

After:

http://www.estoyaburrido.net/asus/Im.072.jpg

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

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.

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: Options:(null)
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.

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.

Just restart router.

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.

if you can not send new firmware by tftp or asus recover tool
JTAG the damn thing
you will find all the information you need on dd-wrt forum
where you should have put this post
after all is a dd-wrt problem

kierzniak

Could you please post some more pics of the PCB of your WL500gpv2 ? To read text on the chips. And describe how to disassemble it without damage ...

Thanx in advance.

Sorry for stupidity :) Found 4 screws, now exploring PCB, chips etc.

I'm now running Oleg's firmware 1.9.2.7-10 on my WL-500W. I see that people online had good experiences with it, so feel it is safe. I'd like to try other firmware or even build my own flash image. However, I don't want to risk bricking my router.

Are firmware updates risky? Can bad firmware unrecoverably brick the router?

I see that the router can recover via TFTP. If that can always be relied on, then I have nothing to worry about. Theoretically, it could be perfect: if the recovery routine is in ROM or write protected flash, it's safe. But did Asus do that?

I see that some people need to short pins, and some people can't even recover that way. What causes that? Is it due to firmware issues or hardware problems?

You will not get any guarantees as to success or a total brick.
I've uploaded about 4 different firmwares to 2 different Asus models and it worked, I guess because I followed the instructions meticulously, including applying factory default settings before I start. I guess some folks think this step is there just for fun and decide to not bother with that.

I have a very similar issue with a WL500gpv2.

- Upgraded to a DD-WRT mega generic.
- Router rebooted.
- Power+Wifi up, no connection, no dhcp, nothing.
- Switched to restore mode.
- Able to ping in restore mode only (not normal mode).
- Able to tftp.
- Tried tftping the nvramclean, recover and several Asus firmwares, tftp works fine. But then when I boot back, the wrouter doesn't do anything (Power+wifi up), no connection, no DHCP, nothing.

Did you manage to repair/get some help?

Cheers,

W.

Again , both of you need serial conection to actually see where is the problem, using either hyperterminal or putty. There are lots of instructions here and at other places , just search the web for "wl500gp v2 serial" or something like this.
This requires some soldering skills and opening the router which automatically voids your warranty.
So ... good luck ;)

Hello... i have the following problem ...

I tried updating dd-wrt firmware (with newer version)... while doing so i forgot to put it in recovery mode.... anyways.. i udated via web interface.. it was updating... after that my router i useless.

I cannot enter recovery mode or so anything. The power light is just lit up, doesn't blink.
If i plug in any cabled the router detects them... if i try to connect via cable (i inter ip, getaway, dns manualy: 192.168.1.2... n dns/getaway 192.168.1.1)

the router connectswith limited connectivity n the network has its old name that i had...
I cannot ping 192.168.1.1.

so this is my case.... any ideas would be appreciated

thanks !

pin9 trick perhaps?

search the forum for it.

fixed the problem..... i kept pluggin it in 'n out.
it works like this : turn touter on
- put the lan cable in lan1
- turn the outer off
- unplug the lan cable
- turn the router on
- plug the cable in after like 2 secs

That way always started working.. went on air so i could reflash it

Hi Guys,

I need some help over here, i've got an ASUS WL500W unit, it was working until yesterday after a bad attempt to change firmware.

Let me explain.

I was Running

PRE-SP2
/eko/BrainSlayer-V24-preSP2/08-13-09-r12638/broadcom/dd-wrt.v24_std_generic.bin

And tryed to update to a Mega Build Generic.

Well, something goes wrong, and IE crashed (using webinterface). So the router stopped working.

Tryed the Reset and nothing ...

After some reads of many topics of bricked routers like mine, tryed hard 30/30/30 and for about 5 ou 7 times i got Ping Response with TTL=100.

After read the Peacock post, i've understand the router is waiting for firmware.

Well, i tryed my best, and after many many reads, i've got the right momment to upload the nvram.trx to recover my router (well Asus Recovery don't worked right on Windows 7, even after firewall disable and UAC turned off).

Well first TFTP worked right.

Then following the some posts, i just continue to fix my router, and running another TFTP with wl500g-recover.trx

Well until this part i was following and everything it's OK, but the router still respond with ping with TTL=100 ( so Peacock say's, waiting for Firmware right ?? )

I've tryed the Original 1.9.7 firmware of ASUS, no chance, the TFTP works right but even after 10 minutes waiting for something, and unplug from wall, and plug it again ... Dead End. Pings shows TTL=100 so didn't work as expected.

I've tryed other's solution like ...

Do everything Again, and Again ... and Flash the Asus Mini Firmware from DD-WRT. Well, again all the TFTP worked right, but no chance to get a single response from router, Ping's TTL=100 and no change.

Router Boots, pings 5 times and timeout timeout timeout.

Well, i've bot myselft very angry, because it was 140 US Dollars from Ebay to Brazil ... Sad don't want to loose my router.

Well, went to sleep for sometime, and another billion of topics and experience share ...

Tryed the Clear Nvram.trx again, the Recover Again ...

And as sugest by google, i've looked for other firmware ( in this case OLEG ).

Well well, quite well done.

I've flashed after the restore the oleg firmware !!!
WL500W-1.9.2.7-d-r617.trx

Well, the router reboot, well now AIR led is UP and running.

Manage to ping router and Well i've got TTL=64, as Peacock says there is something on the router, is this OLEG !?

Well not so good. It's not Oleg and not Original Asus.org, it's a partial bricked DD-WRT.

If i try WebBrowser 192.168.1.1 (just work if i set the ip on LAN no DHCP on any conditions ).

I've got a prompt with my old config, asking for username and password.

But, it does not accept root, root and admin admin, and the root as user and the password i used to have.

Telnet the router works, but instead of showing something i could understand it show the router name as WL-MacAdress of the router itselft

So root/root doest no accept, and other combinations.

I'm still pinging router for now with -t option all response <=1ms with TTL=64

But if i try to TFTP with any DD-WRT firmware (TFTP Can not connect)

TFTP any OLEG firmware same result
TFTP Original asus, the same result

Well, if i reset it comes back to Ping with TTL=100

And i don't known what to do for now !!!

I think it's only partial bricked. But how can i recover !?

I've order from ebay the TTL=RS232 3.3V but i will have to wait for 15 days to have it on Brazil.

I'm Afraid of Short Pin 9 !!! So anyother chance to have it working !?

I'll try to contact asus RMA not sure if they have something on Brazil, but i don't think the will accept an EBAY item, and the Guy on Ebay will not accept it back, since i think it was my fault on something, and the Time to send defective unit just gone 3 weeks ago.

Thanks a lot for your help guys.