x10 R9000 Bricked, can anyone help?

8 posts / 0 new
Last post
BrightDwarf
BrightDwarf's picture
x10 R9000 Bricked, can anyone help?

Hi I Loaded the Kong DD-WRT for NETGEAR X10 Nighthawk R9000 (Initial) to my x10 Nighthawk the firmware uploaded but reset twice during thefirmware upgrade. What suprised me was the router said it needed to reset a second time. Since the upgrade I have only got a power blinking light. I can ping the router at 192.168.1.1 and have 4 solid replies without packet loss. I can connet another internet connection to the router LAN and canthen use the router as a switch without any problems. I have tried power cycling the router and doing the 30/30/10 reset. Help router is only 4 months old! If anyone can suggest a fix please let me know.

kpoert
kpoert's picture
Got the same issue. Please

Got the same issue. Please help!

 

 

[url=http://www.matchbox-photography.com]newborn photography dublin[/url]

Voxel
Voxel's picture
Try to use TFTF to upload

Try to use TFTF to upload stock firmware again:
 

https://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-...
Voxel.

fuzzboom
fuzzboom's picture
TFTPT.exe and upload

TFTPT.exe and upload whichever firmware your heart desires.

fuzzboom
fuzzboom's picture
TFTPT.exe and upload

TFTPT.exe and upload whichever firmware your heart desires

 

semiazas
semiazas's picture
Just applied the most recent

Just applied the most recent dd-wrt firmware for R9000 available from the ftp.dd-wrt.com website and put the router into a boot loop.  No idea if there was a flash failure, bad download, or bad transfer, but it effectively bricked the router.  Using tftp.exe utility refernced in the Network knowlege article linked above would not work.  It would get partway through the file transfer, hang for a moment, and retry.  Even when forcing a recovery mode by holding reset and power cycling.  This was across my LAN, and connected directly (via crossover) to my computer.  I had to resort to a linux based tftp client to transfer successfully.  It did not (tftp doesn't normally require any sort of password) require a password.  This allowed me to get the router back into service.  It's likely a Windows command line tftp client would be equally viable assuming you can track one down, for those not comfortable with Linux.  

It was a fun couple of hours sweating bullets.  

jwortiz
jwortiz's picture
@brightdwarf,

@brightdwarf,

I thought I bricked the router too a while back exactly how you described it.  I just took a paper clip and stuck it in the little whole in the back.  Keep it down for about 8 seconds and let go.  Let the router do it's thing for about 5 minutes and try again to connect to it.  It's important to leave it alone for at least 5 minutes after the paper clip reset. If that doesn't work, do it again with the paper clip, but hold it down for about 30 seconds.  Then release and leave it alone for about 5 minutes or so and see what happens.  Hope this helps.

 

jwortiz
jwortiz's picture
haha ... I replied to the

haha ... I replied to the wrong message.  disregard!