I ran "erase linux" and "reboot" and after the router rebooted I couldn't connect to it anymore (no DHCP lease) and the power led blinks (green).

I'll see what happens if I assign a static IP and gateway, but my hopes aren't up...

Anyone ideas accept waiting for the USB-TTL cable and follow the debrick procedure?

Update: Static IP & Gateway did the trick! A good idea would be to update the tutorial with that information. When the router reboots the attached PC will try to obtain a new IP using DHCP (which didn't work in my case) thus assigning the "couldn't get a IP"-address 169.x.x.x and therefore I was unable to tftp to 192.168.1.1.

I've tried two different revs of Netgear factory firmware, I've tried the two files listed in the DD-WRT router database for WNR3500v2, and I've tried teddy_bear's Tomato beta. The factory files successfully complete tftp but nothing happens. The other ones cause the router to go offline, and after waiting a long time, I reset it only to come back to a continuously blinking green power LED.

Ping continuously returns TTL=100 which I read to mean it's ready for tftp.

I've also tried shorting the two pins to reset the NVRAM as posted by fabien somewhere on this site.

It worked great for me, no flashing green light and the router works fine with one exception:

- I can't log in on the router. Have tried admin & password, root & admin and all other combinations of usernames and password that I used during my 1-day dd-wrt era. Turned the thing off and resetted to factory settings and tried the above usernames and passwords again. Still no access.

Any ideas anyone?

Update: A Hard Reset did the job. The reset I mentioned above was not according the the "simple reset" or "30-30-30 reset" described elsewhere in this forum.

So does this process require that the user assigns a static IP address to their own computer in order to perform the reflash? (if so, how does one do so?)
I'm trying to get back to factory firmware after trying a version of DD-WRT on this site that isn't nearly as stable as the factory original.

Alright! I completed the flash successfully!
I followed the steps above, and when it came time to tftp the router I changed directories in cmd to where I had the router firmware stored, then tftp'd it. I also made sure to assign a static IP to my computer before doing this. I think these are some crucial steps that should be added to this post to ensure clarity and allow everyone to successfully complete the flash.

Before doing this procedure, make sure the IP of the router is 192.168.1.1! I had changed mine to something custom, but it would only allow me to tftp to 192.168.1.1, which meant I had to assign a static ip locally, yadda yadda.

Also strange, after restoring the factory firmware it went back to my custom IP, but I could not login. A hard reset (via the button) fixed that.

This procedure has worked for me 2 out of 2 times (and confirmed by another member) to flash Netgear stock firmware back from Tomato 9047:

This is what I did going from tomato 9047 to Netgear 1.0.2.50. After a 30-30-30, I simply upgraded to Netgear 1.0.2.50 in chk format. It took, but the power light keeps blinking.

At this point, I power cycled (30 sec), did 30-30-30, and then tftp'd to 192.168.1.1 [ tftp -i 192.168.1.1 put filenameofnetgearfirmware] (NOTE: I HAVE ALSO SUCCEEDED EVEN WHEN YOU SKIP THE POWER CYCLE AND 30-30-30. JUST TFTP DIRECTLY.)

Wait 5 minutes, power cycle, 30-30-30...VOILA.

IN MY EXPERIENCE, IT IS IMPORTANT THAT YOU SET A STATIC IP ON YOUR PC WHEN PLAYING AROUND WITH ROUTER FIRMWARE UPGRADES!!

@Heintz, got exactly the same problem. I didn't actually figure out that I need to set a static ip on my PC after erasing DD-WRT.

But I was able to re-flash it from that point back to the original firmware using "Firmware recovery utility" that is on the bundled CD.

I think this whole process of re-flashing could be done from very beginning using that Netgear's recovery utility rather than telnet-ing and tftp-ing... I presume it's just does all these steps from tutorial in the background. Am I right?

taekwon3dan said: This procedure has worked for me 2 out of 2 times (and confirmed by another member) to flash Netgear stock firmware back from Tomato 9047: This is what I did going from tomato 9047 to Netgear 1.0.2.50. After a 30-30-30, I simply upgraded to Netgear 1.0.2.50 in chk format. It took, but the power light keeps blinking. At this point, I power cycled (30 sec), did 30-30-30, and then tftp'd to 192.168.1.1 [ tftp -i 192.168.1.1 put filenameofnetgearfirmware] Wait 5 minutes, power cycle, 30-30-30...VOILA. IN MY EXPERIENCE, IT IS IMPORTANT THAT YOU SET A STATIC IP ON YOUR PC WHEN PLAYING AROUND WITH ROUTER FIRMWARE UPGRADES!!

kosskossy said: Here is what I did to get mine to work -Downlaod the latest firmware from netgear and rename it to WNR3500.chk -Save it on your C drive -Open cmd -Type "cd\" and hit "enter", this will move you to the C drive -Type "tftp -i 192.168.1.1 PUT WNR3500.chk" DON'T PRESS "ENTER" -Now plug in the power to your router while holding a screw driver in your hand -wait until all lights flashes and then short the 2 pins shown in Fabian pic -while having your screwdriver on the 2 pins, go to the cmd window and press"ENTER" - wait until you get a confirmation that the file transferred sucessfuly==> Then my lights started blinking green==> -Now put your screwdriver on the table and press the "upward" arrow and then press "enter" to send the firmware file a second time. - The light color will change from blinking green to blinking orange... wait... wait... wait... wait 5 minutes and the router will be restored.

I did this, minus all the shorting stuff. In addition, I also assigned a static IP to my NIC. Some of the other comments on this page explain how to do that.

If you keep getting a flashing green light and the tftp command is not working. I have the most easiest fix. Just pop the CD in your PC. Have that ethernet cable still hook up. set IP 192.168.1.8, 255.255.255.0, 192.168.1.1 is default gateway. Run the recovery utilty from the CD and it'll put eveything back like it was. You may still have to do up to the erase linux part of this tutorial but after that the CD will take it from there if you run into problems. Hope this helps. It help me.