i strongly recommend the lom modified xvortex cfe if you are going to be doing a lot of testing.
all it takes is one bad flash that overwrites the devinfo partition and the router will require serial recovery from stock cfe, and then it's a major kludge if you havent backed up the devinfo data.
downside of xvortex cfe is that dd-wrt cannot be upgraded from the gui (requires ssh or telnet)
i strongly recommend the lom modified xvortex cfe if you are going to be doing a lot of testing.
all it takes is one bad flash that overwrites the devinfo partition and the router will require serial recovery from stock cfe, and then it's a major kludge if you havent backed up the devinfo data.
downside of xvortex cfe is that dd-wrt cannot be upgraded from the gui (requires ssh or telnet)
Managed to brick 2 routers, trying to put on DD-wrt.
Any tricks to get it back and working.
The network lights flash when I plug in a network cable, but no flashing power light.
Been there, done that. I've managed to unbrick them with 30/30/30 and a couple times with tftp. After releases 30xxx from either Kong or BS, I've never had any issue with bootloops . Currently I have 1 with Kong r30225 and BS r30284 running as expected.
The power light will not come on if it just booted up from full reset, after you logged on and applied some settings, it would come on (no light if it set to client bridge), the key is be patient, it takes sometime to have the webui show up initially.
Managed to brick 2 routers, trying to put on DD-wrt.
Any tricks to get it back and working.
The network lights flash when I plug in a network cable, but no flashing power light.
Been there, done that. I've managed to unbrick them with 30/30/30 and a couple times with tftp. After releases 30xxx from either Kong or BS, I've never had any issue with bootloops . Currently I have 1 with Kong r30225 and BS r30284 running as expected.
The power light will not come on if it just booted up from full reset, after you logged on and applied some settings, it would come on (no light if it set to client bridge), the key is be patient, it takes sometime to have the webui show up initially.
edit to add: they're both on stock CFE
I believe I've done the 30/30/30 reset, but no luck. Been trying about 2 days now/
My initial flash was the Asus rt-56u
When i pint 192.168.1.1, i get destination unreachable
Managed to brick 2 routers, trying to put on DD-wrt.
Any tricks to get it back and working.
The network lights flash when I plug in a network cable, but no flashing power light.
Been there, done that. I've managed to unbrick them with 30/30/30 and a couple times with tftp. After releases 30xxx from either Kong or BS, I've never had any issue with bootloops . Currently I have 1 with Kong r30225 and BS r30284 running as expected.
The power light will not come on if it just booted up from full reset, after you logged on and applied some settings, it would come on (no light if it set to client bridge), the key is be patient, it takes sometime to have the webui show up initially.
edit to add: they're both on stock CFE
I believe I've done the 30/30/30 reset, but no luck. Been trying about 2 days now/
My initial flash was the Asus rt-56u
When i pint 192.168.1.1, i get destination unreachable
Managed to brick 2 routers, trying to put on DD-wrt.
Any tricks to get it back and working.
The network lights flash when I plug in a network cable, but no flashing power light.
Been there, done that. I've managed to unbrick them with 30/30/30 and a couple times with tftp. After releases 30xxx from either Kong or BS, I've never had any issue with bootloops . Currently I have 1 with Kong r30225 and BS r30284 running as expected.
The power light will not come on if it just booted up from full reset, after you logged on and applied some settings, it would come on (no light if it set to client bridge), the key is be patient, it takes sometime to have the webui show up initially.
edit to add: they're both on stock CFE
I believe I've done the 30/30/30 reset, but no luck. Been trying about 2 days now/
My initial flash was the Asus rt-56u
When i pint 192.168.1.1, i get destination unreachable
Have you tried to ping with the -t switch?
Yes I have. What I want to know is if some kind o recovery is possible. I've even reinstall stock firmware.
if you can access the serial port, you might be able to recover.
if lan ports do not respond, you will probably have to use ifconfig to set a lan ip address. then you could load a new image over lan.
if devinfo is gone, stock firmware wont work.
there are pages and pages of detail about this earlier in this thread.
if you can access the serial port, you might be able to recover.
if lan ports do not respond, you will probably have to use ifconfig to set a lan ip address. then you could load a new image over lan.
if devinfo is gone, stock firmware wont work.
there are pages and pages of detail about this earlier in this thread.
Kinda new to this recovery thing sicne this is the first time in 5 years i've had a brick router...so I apologize in advance for noob questions.
How do I do serial recovery? I've been reading from post 1 to see if i can get any headway with it
Thanks for all your hard work and info. I studied this forum pretty well before working on my EA6400 that I picked up used for $10 (I think I got a pretty good deal). Anyway, I wanted to re-compile and update the instructions to throw DD-WRT onto the device. Feel free to review and comment; it would be nice to set up a Wiki page from this info.
Thanks again!
HI! I follow up this post by butterworth and my Router EA6400 flashed DD-WRT. And now I want to revert to Stock Linksys EA6400 firmware. How I can do? and What do I care for my Router will not brick when I flash back to Stock? Please advise me! thanks
if you can access the serial port, you might be able to recover.
if lan ports do not respond, you will probably have to use ifconfig to set a lan ip address. then you could load a new image over lan.
if devinfo is gone, stock firmware wont work.
there are pages and pages of detail about this earlier in this thread.
Kinda new to this recovery thing sicne this is the first time in 5 years i've had a brick router...so I apologize in advance for noob questions.
How do I do serial recovery? I've been reading from post 1 to see if i can get any headway with it
tftp through LAN code1:flash -noheader 192.168.1.254:file.bin nflash0
tftp through LAN code1:flash: <no check> <server ipaddr>:<file> <device name>
tftp through serial code2:flash -noheader uart1:file.bin nflash0
tftp through serial code2:flash: <no check> <com port serial>:<file> <device name>
(used ters term for easier)
or you can set up what ever by CLI ENV
show eth0 info code: printenv
creating temp server env code: env set server_ipaddr 192.168.1.x
EA6300v1 or R6300v1 used BCM4706 soc BCM4706 CPU = MIPS32® 74K Core compare to EA6250 or EA6300v2 or EA6400 or EA6700 or R6300v2 or DIR 868L all use BCM4708 cpu with Advanced ARM® Cortex™-A9 Dual-Core.
if you can access the serial port, you might be able to recover.
if lan ports do not respond, you will probably have to use ifconfig to set a lan ip address. then you could load a new image over lan.
if devinfo is gone, stock firmware wont work.
there are pages and pages of detail about this earlier in this thread.
Kinda new to this recovery thing sicne this is the first time in 5 years i've had a brick router...so I apologize in advance for noob questions.
How do I do serial recovery? I've been reading from post 1 to see if i can get any headway with it
tftp through LAN code1:flash -noheader 192.168.1.254:file.bin nflash0
tftp through LAN code1:flash: <no check> <server ipaddr>:<file> <device name>
tftp through serial code2:flash -noheader uart1:file.bin nflash0
tftp through serial code2:flash: <no check> <com port serial>:<file> <device name>
(used ters term for easier)
or you can set up what ever by CLI ENV
show eth0 info code: printenv
creating temp server env code: env set server_ipaddr 192.168.1.x
EA6300v1 or R6300v1 used BCM4706 soc BCM4706 CPU = MIPS32® 74K Core compare to EA6250 or EA6300v2 or EA6400 or EA6700 or R6300v2 or DIR 868L all use BCM4708 cpu with Advanced ARM® Cortex™-A9 Dual-Core.
Thanks for the assist, but I'm a bit unsure of what I'm using for the commands (noob question...sorry)
