Bricked R8000

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
DrCast
DD-WRT Novice


Joined: 08 Jan 2016
Posts: 6

PostPosted: Fri Jan 08, 2016 11:20    Post subject: Bricked R8000 Reply with quote
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
Sponsor
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Jan 08, 2016 17:25    Post subject: Re: Bricked R8000 Reply with quote
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
DrCast
DD-WRT Novice


Joined: 08 Jan 2016
Posts: 6

PostPosted: Fri Jan 08, 2016 19:54    Post subject: Reply with quote
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.
DrCast
DD-WRT Novice


Joined: 08 Jan 2016
Posts: 6

PostPosted: Fri Jan 08, 2016 21:20    Post subject: Reply with quote
Is it possible to unbrick via serial tty connection?
Paint
DD-WRT User


Joined: 22 Jun 2015
Posts: 131

PostPosted: Fri Jan 08, 2016 21:54    Post subject: Reply with quote
DrCast wrote:
Is it possible to unbrick via serial tty connection?


yes, that is the best way if the option Kong posted does not work for you.

Serial connection on the R8000 is the same as the R7000, which have many guides on google and here:

http://myopenrouter.com/article/how-debrick-or-recover-netgear-r7000-r6300v2-or-r6250-wi-fi-routers
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=56739

_________________
pfSense i7-4510U + 2x Intel 82574 + 2x Intel i350 Mini-ITX Build
940/880 mbit Fiber Internet from FiOS
Dell PowerConnect 2716 Gigabit Switch
Netgear R8000 AP, running DD-WRT
Asus RT-66U AP, running DD-WRT
DrCast
DD-WRT Novice


Joined: 08 Jan 2016
Posts: 6

PostPosted: Fri Jan 08, 2016 22:34    Post subject: Reply with quote
thank you. Which if the pins on the R8000 is gnd,rx,tx.
The board layout is different to the R7000
DrCast
DD-WRT Novice


Joined: 08 Jan 2016
Posts: 6

PostPosted: Fri Jan 08, 2016 22:52    Post subject: Reply with quote
Got it

http://www.myopenrouter.com/article/how-set-serial-console-netgear-r8000

Router is alive again. Thanks!
rajdude
DD-WRT Novice


Joined: 25 Oct 2016
Posts: 5

PostPosted: Tue Oct 25, 2016 4:25    Post subject: is the cable the only option left? Reply with quote
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 Sad
Tried different tftp clients, no dice Sad


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)

Any other option I could try?
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Tue Oct 25, 2016 5:49    Post subject: Re: is the cable the only option left? Reply with quote
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 Sad
Tried different tftp clients, no dice Sad


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)

Any other option I could try?


You just have to use the reset button to clear nvram.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
rajdude
DD-WRT Novice


Joined: 25 Oct 2016
Posts: 5

PostPosted: Tue Oct 25, 2016 11:06    Post subject: Reply with quote
Hi Kong, thanks for chiming in.

I should have mentioned it earlier, I have also tried your reaet nvrqm procedure, that 5-15 one, it did nothing. Router still behaves the same way.

There was another thread I read somewhere lasr night. Someone was saying that installation od 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 5he firmware in a text editor, change something in the first bits amd then resend. It worked for some ppl. That thread was for R7000, though.

Thoights?
rajdude
DD-WRT Novice


Joined: 25 Oct 2016
Posts: 5

PostPosted: Tue Oct 25, 2016 13:39    Post subject: interesting info... Reply with quote
ok I found the thread I was talking about :
https://community.netgear.com/t5/Nighthawk-WiFi-Routers/SOLVED-Steps-for-debrick-unresponsive-R7000-softbricked/td-p/414034

Look for ghoffman's post. and I quote him:

Quote:
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


I am wondering if this applies to the R8000 also.
rajdude
DD-WRT Novice


Joined: 25 Oct 2016
Posts: 5

PostPosted: Mon Oct 31, 2016 13:18    Post subject: fixed mine Reply with quote
Just to follow up on my posts in this thread...

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

Done!

PS: boardid was NOT a problem.
PS: Magnetron1.1's post in this thread was immensely helpful
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=905027
Betch
DD-WRT Novice


Joined: 12 Jan 2020
Posts: 8

PostPosted: Sun Jan 19, 2020 15:27    Post subject: Reply with quote
I soft bricked mine when I flashed OpenWRT, I played around with it for a couple of hours but it doesn’t seem to be as good as ddWrt.

Router R8000
Firmware: 42015
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum