Posts: 0
Registered: ‎2008-10-20

Guide: How to "unbrick" your WGR614v9 after a bad firmware update!

[ Edited ]

Hi everybody!


This is a guide on how to "unbrick" your Netgear WGR614v9 after a bad firmware update, f.x. trying to update over wireless.


Before you continue below, make sure you've first tried a hard reset to revive your router: 

  1. Disconnect the router from all cables except the power cable.
  2. Push reset button for 30 secs.
  3. Without releasing reset button, disconnect power cord.
  4. Hold the reset button for another 30 secs.
  5. Replug the power cord.
  6. Still hold the reset button for another 30 secs.
  7. Release the reset button and give the router about 10 secs to resettle.
  8. Disconnect power cord for another 10 secs and then reconnect.
  9. All should be in default settings now.


During startup, the router will pause to accept a temporary firmware upload via TFTP, so:
Connect your computer with the router using a wired connection and try pinging it.
If pinging does not work, check the IP Address of your computer and make sure it is assigned an IP address in the subnet of the router IP. For simplicity sake you can assume "192.168.1.x" is good. If you do not have a good IP, the DHCP Server might not be working. So set your IP manually to something like with as your gateway and then try pinging the router again.


Power the router on with a continuous ping running in a command window:
ping -t -w 2


(The -w 2 parameter forces a lower timeout for the ping answer, this makes easier to get an answer from the bricked router.)


You should see at least a few replies from Do this several times to be sure. If it does you have good chance of simple recovery. If you still receive no response, the IP address may be something other than You should attempt to obtain the IP address of the router. Especially if previous firmware set the boot_wait variable to on, the router pauses even longer than normal during bootup to accept a recovery flash. All you need to do is provide a firmware to it via TFTP during this window of time.


Prepare your PC, firmware file and TFTP software and play with the timing of powering it on and starting the TFTP session just after applying power (or as soon as you start to see ping replies). If you try it a number of times (at least 10) you will probably rescue the router with no fuss!


Microsoft Windows contains a TFTP client. Windows Vista will require that you enable it in Programs and Features. With TFTP, all of the information about the transfer is specified during the initial setup; there is little client/server interaction as compared with standard FTP. To flash a router using Microsoft Windows, open a command prompt, change to the directory containing the original firmware to use for this boot (this example assumes the firmware file name is firmware.chk), and then enter the following command (assuming your router IP-address is


tftp -i PUT firmware.chk


If you don't have a TFTP client installed, it doesn't work or something else, then try using this TFTP program called tftp2 available here (this will start the download): tftp2.exe


Now your Netgear WGR614v9 is working like before with default settings, and all there is left to do is set it up using the normal web interface using!


Best of luck, Daniel!


(Everything you do using this guide is 100 % at your own risk!)

Posts: 1,791
Registered: ‎2008-10-01

Re: Guide: How to "unbrick" your WGR614v9 after a bad firmware update!

Excellent. Stickied.
1-888-NETGEAR - (Phone Support)

"Apple's market share is bigger than BMW's or Mercedes's or Porsche's in the automotive market. What's wrong with being BMW or Mercedes?" -Steve Jobs

Network Cards/Adapters:

GA311, WNDA3100


DGDN3300, FVS114, GS108, WRT54GL (DD-WRT)


MacBook C2D 2.0Ghz/3GB/250GB

Hackintosh C2D 2.4 GHz/4GB/700GB

iPhone 3G (16GB Black), Xbox 360, PS3
Posts: 0
Registered: ‎2008-10-20

Re: Guide: How to "unbrick" your WGR614v9 after a bad firmware update!

nobel_nomar wrote:
Excellent. Stickied.

Thanks! Appreciate it...! Smiley Happy

Discussion Stats
  • 2 replies
  • 0 kudos
  • 2 in conversation
Top Contributors