E4200v2 on .37 firmware bricked by setting new port address with DNS off

Question

I hooked up my E4200v2 with the intention of replacing another router, with DNS off. While everything else was disconnected, I used a wired interface to change its address to 192.168.0.1 on the first setup page.  As soon as I pressed "Save Settings", the darned thing turned off all of its ethernet ports and lay dead.  I performed a 30on-30off-30on reset, but the darned thing wouldn't wake up.  I let it sit for a half hour and tried again, with no luck.   I tried again an hour later, and suddenly the Cisco light began to blink. I quickly hooked up my PC to the wired local port, and set my PC's wired interface statically to the new subnet. No luck. Then I tried the original subnet. No luck.  Then suddenly the ports went dead again, never to return to life, despite patient waiting followed by another attempt to 30on-30off-30on reset.  What gives?  Is there some fatal firmware flaw?  Has no one out there done this before?  This router is only about 4 months old.  Is there another reset mode?  It's like the settings poisoned it.  The Cisco light is on solid, but no recovery.

Answer 1

Puppa wrote:
I hooked up my E4200v2 with the intention of replacing another router, with DNS off. While everything else was disconnected, I used a wired interface to change its address to 192.168.0.1 on the first setup page.  As soon as I pressed "Save Settings", the darned thing turned off all of its ethernet ports and lay dead.  I performed a 30on-30off-30on reset, but the darned thing wouldn't wake up.  I let it sit for a half hour and tried again, with no luck.   I tried again an hour later, and suddenly the Cisco light began to blink. I quickly hooked up my PC to the wired local port, and set my PC's wired interface statically to the new subnet. No luck. Then I tried the original subnet. No luck.  Then suddenly the ports went dead again, never to return to life, despite patient waiting followed by another attempt to 30on-30off-30on reset.  What gives?  Is there some fatal firmware flaw?  Has no one out there done this before?  This router is only about 4 months old.  Is there another reset mode?  It's like the settings poisoned it.  The Cisco light is on solid, but no recovery.
You can hard reset the router. Try isolating it using a loop back test or use another Ethernet cable if necessary. If LAN status says, media disconnected then I think you can call tech support for replacement.