Posted: Fri Jan 08, 2016 11:20 Post subject: Bricked R8000
Hello,
I bricked my R8000 yesterday after configuring the latest Kong release. I did some changes to the wireless security and after the reboot it was no longer accessible.
I can ping the router for a short time and after that, it seems to reboot. The router returns ttl 100 while pinging, but it's impossible to tftp a new firmware.
I tried several clients, Linux and Windows without succes. I always get time outs.
Posted: Fri Jan 08, 2016 17:25 Post subject: Re: Bricked R8000
DrCast wrote:
Hello,
I bricked my R8000 yesterday after configuring the latest Kong release. I did some changes to the wireless security and after the reboot it was no longer accessible.
I can ping the router for a short time and after that, it seems to reboot. The router returns ttl 100 while pinging, but it's impossible to tftp a new firmware.
I tried several clients, Linux and Windows without succes. I always get time outs.
Is there any hope for my R8000.
Thanks a lot!
Best wishes
Olli
Power it on, press reset after 5s and hold it for 15s. That should clear nvram.
Did you configure Client Repeater?
This was broken in the first 28600 build for the R8000, but is fixed in the 3rd Jan build
Thanks for your reply. Yes i did.
I tried the nvram reset without success.
This is what happens after power on:
Some leds turn white and go off
WPS led on (white color) and off again
WIFI led on (white color) and off again
Power led on (white color) and color change to orange
All leds turn white and off again
After that, only the power led stay orange.
I am able to ping the router for about 10 seconds, before everything seems to happen again.
Posted: Tue Oct 25, 2016 4:25 Post subject: is the cable the only option left?
I have the exact same problem.
Got a R8000
I installed Kong R30700M 9/27/16. It was unstable so I tried to revert back to stock fw. Uploaded R8000-V1.0.3.4_1.1.2.chk file which I had downloaded from Netgear's site.
Right after that, the router went into a boot loop.
Now, yes I can connect via TFTP and try to upload, but nothing good happens.
I have tried older versions of the FW, same thing
Tried different tftp clients, no dice
Is the USB-TTL cable the only option available?
I really cannot wait for the cable to be shipped out (will take a few days)
Posted: Tue Oct 25, 2016 5:49 Post subject: Re: is the cable the only option left?
rajdude wrote:
I have the exact same problem.
Got a R8000
I installed Kong R30700M 9/27/16. It was unstable so I tried to revert back to stock fw. Uploaded R8000-V1.0.3.4_1.1.2.chk file which I had downloaded from Netgear's site.
Right after that, the router went into a boot loop.
Now, yes I can connect via TFTP and try to upload, but nothing good happens.
I have tried older versions of the FW, same thing
Tried different tftp clients, no dice
Is the USB-TTL cable the only option available?
I really cannot wait for the cable to be shipped out (will take a few days)
I should have mentioned it earlier, I have also tried your reset nvram procedure, that 5-15 one, it did nothing. Router still behaves the same way.
There was another thread I read somewhere last night. Someone was saying that installation of dd-wrt may have changed something where the router thinks that it is not a r8000 anymore. As a result it fails the checks when we send the firmware via tftp. His solution was to open the firmware in a hex editor, change something in the first bits and then resend. It worked for some ppl. That thread was for R7000, though.
i suspect that the boardid has been changed so the cfe thinks the router is a differnt type. by screwing around with tomato and dd-wrt on my r6300v2 (similar router) i had the same problem.
i suspect that the boardid was rewritten as 'HDR0' instead of U12H270T00_NETGEAR (correct for an r7000)
this means the cfe loader will only take a firmware image without the identifyiing information in a netgear .chk file.
if you don;t have a serial connection to make the diagnosis, then i would just try the following steps:
1. get an older factory image for r7000.
2. use hexedit to remove the first 58 bytes, so the first four bytes of the file are 'HDR0'. make sure you a re using a binary/hexeditor, not a text editor. save it as factory.trx, a new firmware file without the identifying header.
3. give your computer a static ip address (like, 192.168.1.9, not 192.168.1.1 which is the router default). connect your ethernet port to a lan port on the router
4. hard reset the router holding the reset button for 10 sec, and alow the router to reboot.
5.confirm the cfe is waiting for firmware by 'ping 192.168.1.1' a 'ttl=100' response is what you are looking for
6. use 'tftp -i 192.168.1.1 put factory.trx' to upload you newly created image
7. wait 2-3 minute for a couple reboots.
8. if the lights look ok - great. if not, try pinging. ttl=64 menas the firmware is up. give it a few more minutes. you make need another reset.
9. do the telnetenable MACADDR Gearguy Geardog trick to enable telnet
10. telnet into the router
11. check the boardid by issueing the command 'burnboardid'
12. the proper id for an r7000 is U12H270T00_NETGEAR. if not, issue the command 'burnboardid U12H270T00_NETGEAR'.
13 reboot
Posted: Mon Oct 31, 2016 13:18 Post subject: fixed mine
Just to follow up on my posts in this thread...
I debricked my R8000 by using the serial port (via a USB to TTL cable)
Remember to cross Rx and Tx connections!
Held down "Control+C" until I saw CFE prompt
run the command "nvram erase"
run the command "tftpd"
sent stock firmware via tftp to 192.168.1.1
saw successful message
reboot
I debricked my R800 by using the serial port (via a USB to TTL cable)
Remember to cross Rx and Tx connections!
Held down "Control+C" until I saw CFE prompt
run the command "nvram erase"
run the command "tftpd"
sent stock firmware via tftp to 192.168.1.1
saw successful message
reboot
rajdude..Thanks to your post I was able to revive my r8000. My initial mistake was I was constantly hitting "Ctrl + C" on my keyboard vs holding it down like you mentioned and bam got my CFE prompt I was looking for after several days of trying different things. But yeah holding down "Ctrl + C" did the trick for me.