r8000 with dd-wrt in boot loop

9 posts / 0 new
Last post
raven-au
raven-au's picture
r8000 with dd-wrt in boot loop

Hi all,

I installed the dd-wrt from myopenrouter, reset to defaults just to be sure, made a number of configuration changes then rebooted OK.

Next made some changes to the wireless configuration and rebooted which resulted in a continuous boot loop.

Does anyone know how to do a firmware recovery for this router?

Ian

raven-au
raven-au's picture
Hi all,

Hi all,

So setting a 5Ghz interface to Client Bridge causes a kernel panic.

Having found that out I didn't spend much time on this so don't have much detail to offer.

It should be straight forward to reproduce though so if whoever maintains this build can't reproduce it and is interested in fixing it I'll try and provide more info.

I have to say I'm not too keen on taking the router apart again to access the serial port though.

 

Ian

Sayan Mukherjee
Sayan Mukherjee's picture
I have faced the same issue

I have faced the same issue in 5Ghz interface.

The board can be recovered using serial port only.

Developers are working to fix this issue.

Meanwhile, firmware recovery can only be done from the serial console.

Thanks.

raven-au
raven-au's picture
Hi all,

Hi all,

So setting a 5Ghz interface to Client Bridge causes a kernel panic.

Having found that out I didn't spend much time on this so don't have much detail to offer.

It should be straight forward to reproduce though so if whoever maintains this build can't reproduce it and is interested in fixing it I'll try and provide more info.

I have to say I'm not too keen on taking the router apart again to access the serial port though.

 

Ian

Sayan Mukherjee
Sayan Mukherjee's picture
I have faced the same issue

I have faced the same issue in 5Ghz interface.

The board can be recovered using serial port only.

Developers are working to fix this issue.

Meanwhile, firmware recovery can only be done from the serial console.

Thanks.

Psyglitch
Psyglitch's picture
I'm also stuck in a boot loop

I'm also stuck in a boot loop what is the process to use the serial to recover?

invoke
invoke's picture
This is happening to me too,

This is happening to me too, I did not know that setting the wl2 to Repeater Bridge would brick the device, is it possible to recover?? which is the procedure??

 

Thanks!!

 

Paint
Paint's picture
Please buy a USB to TTY cable

Please buy a USB to TTY cable and follow these instructions in order to setup the interface: 

 

http://myopenrouter.com/article/how-debrick-or-recover-netgear-r7000-r63...

 

Please make sure you buy the correct USB to TTY cable that is compatable with windows 8.1..... here is the one I bought.... http://www.amazon.com/gp/product/B00LO2JM34?psc=1&redirect=true&ref_=oh_...

bottswana
bottswana's picture
For anyone that gets stuck in

For anyone that gets stuck in this situation:

Serial into the device, you need a UART cable at 3.3v. A normal serial (12v) will not work.

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

I used this one: https://www.amazon.co.uk/gp/product/B01CYBHM26

 

Boot the router, you will see it decompress the CFE

Spam Ctrl and C until you see 'Boot aborted' followed by a CFE prompt 'CFE>'

 

Identify which wireless interface you set to client bridge mode with:

nvram get wl0_mode

replace wl0 with wl1, wl2 respectively.

mode=ap means the wireless interface is an access point

mode=wet means the wireless interface is wireless bridge mode

 

Change all interfaces in 'wet' mode to 'ap' mode with

nvram set wl0_mode=ap

replace wl0 with wl1, wl2 respectively.

 

Commit changes with

nvram commit

 

Then reboot:

reboot

 

The router should now boot up with all aps set to 'AP' mode and with all of your settings intact.