January 31, 2010 7:27 AM updated: January 31, 2010 8:50 AM

just worth a try; instead of the tftp command try PumpKIN tftp software
set your ip adress of the network interface to 192.168.1.24 (or an ip adress in the same range that isn´t used/has a lease), connect to some port on the router(not wan), hard reboot and send through pumpkin the original firmware, there is a special timing needed, so just try it a few times

please tell me if it worked out for you

PS forgot to mention; also try holding the reset button while rebooting, hold it, press it few times, also this has to be done a few times to be sure it is not working like that ;)

January 31, 2010 2:35 PM

i´ve had to do it that way today, because my router also bricked today while i was playing around with openwrt.... before that this way worked for me several times on the wrt54gl

and today i wasn´t useing the original firmware, i directly put the ddwrt firmware on it, worked perfectly but needed a few tries, tftp put the firmware on the router, the package installed, router rebooted and was accessable via browser

February 2, 2010 12:37 AM

After booting the board, are you able to access the board ? Is ping to the board working ?
Do you have any serial cable ?
Can you please send me your compiled firmware ? I will try it on my board.

February 9, 2010 11:21 PM

It looks like the firmware that you used is wrong in the sense either it is not fully booting or network is not working.
It is normal that you are getting 1-4 times ping when the board is booting. Actually CFE giving that ping response. Once firmware is booting you will not get any response until and unless it boots completely and network is up properly.
I really want to check it out. You can send me that image through email. Check your private message, I will give my email id there.

February 15, 2010 12:30 PM

If using Windows you might try this to get pings faster to your computer on re-boot of the router.
Grab a Network Hub.
Plug it into computer and set a static TCP/IP address to the computer as 192.168.1.10, default gateway 192.168.1.1, and 255.255.255.0.

Using the hub you don't have to wait on router bootup to get an IP address.

Then plug your router into the hub.
Start ping 192.168.1.1 and plug in your router. Watch and see if you get any replies at all. If you do you can try TFTP as soon as you get a ping reply. You may have to try it a few times to catch the right time.

http://placeshiftingenthusiasts.com/

February 15, 2010 2:02 PM

i would say it´s definately possible, in most cases,... but in your case, i think you f...bricked your router up.... so why just buy the cable and be prepared for all future bricks!

February 17, 2010 3:10 AM

I have tested your firmware. It is not booting, at least no message is coming up in the console. So some where in the booting it is crashing and that is before initialing serial console.
The only way you can revert it back is by using serial cable.
By the way, which source code did you use to build that firmware ?

March 22, 2010 4:35 PM updated: March 23, 2010 2:14 PM

Hi,
Is there a way to fully restore the factory settings?

I successfull downloaded the original firmware to my WNR3500, and using the serial cable I can enter the BusyBox.

However, it seems some settings are still wrong. The ssid is the same as before I bricked the router but I get a very strange IP address and cannot access the internet. The router prompt me for password when I go to 192.168.1.1, but I can not log in using the standard password.

Update: By pressing and holding the reset button while powering up the router I managed to reset the NVRAM.

When holding the reset button down I see the following message on the serial output:

.
.
.
Committing NVRAM...done
Waiting for reset button release...

After releasing the button the memory is restored and the router boots normally!