| Zyxel NBG-416N firmware recovery During a recent firmware upgrade, I bricked my NBG-416N. This is a Realtek based Wireless 802.11n/b/g router and I couldn't fork out how to recover. Over the weekend, I could not reach Zyxel support. Once I did, they sent me a "Firmware Recovery Kit" with instructions on how to unbrick it. Worked like a champ!! They provide a root.bin and linux.bin file in a ZIP file and you can TFTP then direct to the router.
In recovery mode, all of the ports just bridge to each other. The default IP address is 192.168.1.6. It does not answer pings, and the MAC address will be different than the one on the bottom of the unit.
Here are the instructions in the kit, corrected to a little bit.
1. Connect the PC to a port on the NBG-416N
2. Set the PC IP address in 192.168.1.10/24
3. Put the files of "root.bin" and "linux.bin" where you can easily find them.
4. Power on the NBG-416M while holding the reset button - hold for five seconds then release it.
5. On the PC or Linux device, use CLI command " tftp -i 192.168.1.6 put root.bin " (Or on your favorite GUI TFTP client, I used TFTP32)
You will see the message " Transfer successful: xxxx bytes in 1 second, xxxx byte/s ", that the files is uploading to device and please wait for 1 minute. >.
6. Power off the NBG-416N
7. Press and hold the reset button plugging in the NBG-416N, after five seconds then release it.
8. On the PC or Linux device, issue CLI command " tftp -i 192.168.1.6 put linux.bin "
You will see the message " Transfer successful: 954386 bytes in 1 second, 954386 byte/s ", that the files is uploading to device
and please wait for 1 minute. The device will initialize without further intervention.
9. When you finish the recovery steps, the KEY LED will light up and then the wireless LED will light up. At this point, you can access NBG-416N. It will answer pings and well as web requests.
10. You can now access »192.168.1.1/hiddenpage.asp for version verification and region setting.
At this point, you should be able to go to »192.168.1.1 and configure the device. |
|
|
|
| 
Inside shot of NBG-416N |
A Realtek RTL8196C and RTL8188RE chipset drives the NBG-416N: ESMT M12L128168A provides 16MB (128mbit) DRAM. 32-100HIP 4MB (32 mbit) Flash. No DD-WRT support. 10/100MB only
A nice little box at a great price. |
|
| reply to remaker
Thanks for posting....I just bought tried to update to the latest firmware and bricked mine too. Unfortunately the instructions they provided are slightly beyond my understanding ( or lacking info needed for a newbie eg step 2)
Can I just use regular FTP client in windows command prompt? I think I might not be connected properly. I tried both windows FTP and the TFTP32 program you mention but nothing happens. Any suggestions? Do I need a crossover and connect to the LAN port? maybe I am not understanding the simple step 2. I connected With regular cable and set my computer to static ip .10 with 255 sub and gateway .24. Any suggestions would be greatly appreciated. |
|
| reply to remaker
I tried to update mine to NBG-416N_V1.00(USA.4)C0 and BRICKED. Seeing you post, trying to download the NBG416N_recover_kit.zip kit, but only downloads 184k file and not the 2.4Mb file.... not sure what is going on.
Tried google/zyxel for this file and cannot get it anywhere else. HELP...!! any other place that I can get this file from? |
|
| Since the file is large you have to sign in to download it. |
|
| reply to remaker
I tryed it, Firmware upgrade failed. but this method doesnt seem to work. the TFTP client cant connect to the router. I think it another kind of brick ?. Or do i need an crossover cable for this procedure |
|
| The recovery is work, i just tried because the router is dead after doing firmware upgrade, the tricky is you need to execute the tftp command in short time after the router startup (get the conmand line ready, once the lan is up then press 'enter' |
|
| I have the same issue -- router bricked after applying the firmware upgrade. Following the above instrux to the letter, setting up the LAN, resetting the brick, I am not able to connect to the router via tftp. tftp consistently returns with a timeout. I have ordered a new router, a CISCO. I can't recall being this annoyed with hardware before. |
|
| The given above method worked fine, bu then I am not able to log into the device entering admin / 1234. Weird. Reset did not help. |
|
| reply to remaker
Thanks, it worked fine. I bricked my router the same day when dslreports went down and had to wait to be able to register and download it for weeks, coz this is the only site on the Internet containing the recovery kit. I also tried to contact zyxel support but without answer(zyxel support $%(&$!!!). I don't understand why is this not officially public.
Thank you very much again! |
|
hardlyPremium
join:2004-02-10
USA | fyi for anyone who can use one, they are currently $19 delivered at Buy.com
»www.buy.com/prod/zyxel-nbg416n-1···784.html |
|
| reply to remaker
Thanks for the instructions -- worked just as described, although I had to use 3rd party TFTP on my Win7 x64 -- I used tftpd64 client tab for that with firewall off.
After recovering NBG-416N to the usable state, I have also succeeded in upgrading it to the V1 00(USA 5)C0 (with official 100USA5C0.bin firmware) -- used Ethernet cable for upgrading because last time when I tried to upgrade it over wireless connection, I bricked it.
Upgrade process takes a while, some 4-5 minutes, so be patient and do not restart the router during that time. The LAN port LED will flash intermittently (cca 3 secs flashing and cca 3 secs lights still). My web session refreshed automatically after upgrade was successful. |
|
| Thanks, bperkic. I was struggling to get this to work following the original instructions, but using tftpd64 worked like a charm.
In case anyone else runs into this problem in the future and is running Win7 x64, here's what I did that worked.
First, reboot the router into recovery mode as described above and connect your computer to the router via ethernet (do not use the WAN port, any of the LAN ports will work).
In the TCP/IP settings of the ethernet connection, set the IP address to 192.168.1.10, subnet mask to 255.255.255.0 (that's what the /24 means) and set the default gateway to 192.168.1.1. In the system tray, the network icon should say unidentified network, no internet access. If it says no network access, try disabling and reenabling the ethernet connection.
Then, instead of using the command line interface (CLI), I used tftpd64 as follows:
Go to the tftp client tab. Put in 192.168.1.6 as the host (leave port blank). Select root_V1.00_USA.3_C0.bin as the local file, root.bin as the remote file, and click "put". Then reboot into recovery mode as described above, and repeat using linux_V1.00_USA.3_C0.bin and linux.bin.
A couple minutes later, the router should work as normal. I didn't even need to reboot the router, but its probably a good idea to.
Thanks everyone. |
|
2 edits | reply to remaker
After a few tries and re-searching for this web page I was able to D/L these files. Also I had trouble with 2 versions of the Zyxel firmware sites, one with a march version and one with a newer July version. Following the win7 directions above,and using tcfpd64 - I tried lots of times with the LAN plugged in and then I, 1. reset the modem 2. plugged in the LAN wire. I then saw the files uploading to the router.  Now if I can figure out why I am having DNS errors. I hope this helps someone. Thanks all. Gray |
|
| reply to remaker
Trying to download this kit several times and it's consistently downloading 198 bytes. Any ideas why or where else I could find it? My searches lead to dead ends. |
|
 BranoI hate VogonsPremium,MVM
join:2002-06-25
Burlington, ON
kudos:6 | Download works fine here (just tested). Check (temporary disable) your security scanner / Anti-virus. |
|
| Thanks for testing it! You may be right. I am trying to download at work and there may be other forces at play. I'll try again at home. |
|
