wl500g dead, dead, dead... Or not ?

Looks like the wrong baud rate.

according to a guy on the dd-wrt forum it is: 19200,8,n,1

Have you checked PSU output and the capacitors on the main board, before jumping into harsh measurements :p

I have a WL-500GD (that's how it's labeled, but for the purposes of this question, it's a WL-500gx). I upgraded some outlets in my house and had my router plugged in when I flipped the breaker back on. The immediate problem was that the router wasn't working although the power light, wan, and lan lights were on, but every 5 seconds or so, all LAN lights would come on and the router would reset. I've tried going through the process of using nvram clear and restore any number of times (with my ethernet IP set static 192.18.1.2), but one thing that doesn't change is that when the port connects, the name I gave my AP is still there. So, in other words, I can't really clear the router to default settings.

Based on what I've read, I thought power supply was the culprit. I scored a used, but hopefully good 5V 2A supply, and no change (in fact, my original supply didn't show symptoms of being bad, like a swollen capacitor). I've tried pin 10 / 9 and pin 12 shorting, and while those are clearly doing something, I can't figure out what, and it isn't consistent. Bottom line is, my router still isn't reset to default, with default settings, after all of that.

I can get into restore mode, ping 192.168.1.1, flash, and everything, but I'm always back to square one when I install firmware - the router keeps resetting itself and I can't get into it through a browser.

So, anyone have any ideas what trick might work to really clear all of it's memory? Also, I want to clarify whether one should or shouldn't use nvram restore with the WL-500gx, or just nvram clear. Thanks.

Hello,
some time ago my wl500g Deluxe started automatically rebooting itself after every 10secs. At first I tought it's the adapter, so I bought a new 5V/2A adapter. Now I see the problem is still there. I somehow came to disabling the wireless just before it can restart itself and it looks to solve the problem, is there some kind of log to look at to see what's wrong with it? I have a working telnet connection.

Thanks, Martin