Can't succesfully complete firmware upgrade.

[cloud]

Good am,

My WL-500G Premium after pluggin in power is always in the restoration mode (Power led is flashing and I can ping it, but cannot enter using web interface).

I am trying to upload any firmware. Firmware (.TRX file) is uploaded successfully (both with Asus Firmware Restoration tool and TFTP) but after that nothng happens. Device either stops responding to PING (Power led at this point either switched on or switched off), or it stays in the restoration mode (responds to ping and power led is flashing). After plugginf off/on power supply it goes again into restoration mode.

I tried different firmwares (WL500gp_1.9.7.5_TW.trx, wl500gp-1.9.2.7-8.trx), I tried the procedure described here: http://www.dd-wrt.com/wiki/index.php/Installation (
1) flash - tftp wl500g-clear-nvram.trx
2) 10 seconds unplug,
3) flash - tftp wl500g-recover.trx
4) 10 seconds unplug,
5) flash- wl500gp-1.9.2.7-8.trx
6) 10 seconds unplug
) -- nothing changed. After power switched on it is in the restoration mode.

What you suggest me to try or check something it this situation? I have searched in the forums, and found a couple of messages with the same sympthoms, but authors reported at the end, that the problem magically dissapeared. It doesn't want to dissapear in my case, so I do not know what to do.

[Serpent]

What you have tried to do?!?

I can only suggest to you the "pin 9 trick", followed by flashing of "clear + recover" trx.
Look here (http://wl500g.info/showpost.php?p=33787&postcount=9) .
But you will lose your warranty...

[cloud]

I can only suggest to you the "pin 9 trick", followed by flashing of "clear + recover" trx.

As far as I understood reading the forum, "pin 9 trick" helps when you cannot get a device into the restoration mode. In my case, it always goes into the restoration mode after switching on (pwr led is flashing once a second). Do you think I still should try "pin 9 trick"?

[Serpent]

The trick lets the router to override all the settings from NVRAM at boot time, invalidating his content.
If you have some wrong settings in NVRAM, as it seems, this can be the only way to bypass them, in my opinion.