followed devianttwo directions on pg 50 plus gyrex suggestions on pg 53, and just flashed the 1/16 build as suggested by mandepsi on pg 63. thanks for the many addl posters' thoughts in this thread.
edit1: also noted alexpp's suggestion to change the 5Ghz channel in case the ssid doesn't appear visible on pg. 61
next will look in to the temps.. also, noted that there are alot of features in ddwrt, however not sure how i can make use of it, (any thoughts welcome). installed it because the orig. linksys firmware was ew.
Last edited by kkwrt on Mon Jan 18, 2016 3:07; edited 4 times in total
@Silent_Swift
thank you
putty shows following strange errors:
"
root@DD-WRT:~# cd /tmp
root@DD-WRT:/tmp# wget ftp://ftp.dd-wrt.com/betas/2015/12-24-2015-r28598/linksys
-ea6400/linksys-ea6400-webflash.bin
Connecting to ftp.dd-wrt.com (185.84.6.100:21)
linksys-ea6400-webfl 100% |*******************************| 27996k 0:00:00 ETA
root@DD-WRT:/tmp# mtd write linksys-ea6400-webflash.bin linux2
Unlocking linux2 ...
Could not unlock MTD device: linux2
linux2: Not supported
Writing from linksys-ea6400-webflash.bin to linux2 ... [e]Failed to get erase block status
root@DD-WRT:/tmp# mtd write linksys-ea6400-webflash.bin linux
Unlocking linux ...
Could not unlock MTD device: linux
linux: Not supported
Writing from linksys-ea6400-webflash.bin to linux ...
"
nevertheless flashing the device was finally succesfull.
there is a little tricky solution for the temp issue:
putting the router horizontal cause because of the silly construction of the router heat jam.
put your router vertical. this make the right air flowing possible.
there is a little tricky solution for the temp issue:
putting the router horizontal cause because of the silly construction of the router heat jam.
put your router vertical. this make the right air flowing possible.
the temp. difference is about 20C.
need to stand for this thing. maybe 3d-print a stand hah.
Yep I did notice this issue on multiple builds, though I haven't reset my nvram for a couple of months. There was some sort of changelog to say that it's been fixed on Broadcom devices, it doesn't look like so
mandepsi wrote:
@Silent_Swift
thank you
putty shows following strange errors:
"
root@DD-WRT:~# cd /tmp
root@DD-WRT:/tmp# wget ftp://ftp.dd-wrt.com/betas/2015/12-24-2015-r28598/linksys
-ea6400/linksys-ea6400-webflash.bin
Connecting to ftp.dd-wrt.com (185.84.6.100:21)
linksys-ea6400-webfl 100% |*******************************| 27996k 0:00:00 ETA
root@DD-WRT:/tmp# mtd write linksys-ea6400-webflash.bin linux2
Unlocking linux2 ...
Could not unlock MTD device: linux2
linux2: Not supported
Writing from linksys-ea6400-webflash.bin to linux2 ... [e]Failed to get erase block status
root@DD-WRT:/tmp# mtd write linksys-ea6400-webflash.bin linux
Unlocking linux ...
Could not unlock MTD device: linux
linux: Not supported
Writing from linksys-ea6400-webflash.bin to linux ...
"
nevertheless flashing the device was finally succesfull.
Mtd write will show the full output, which includes the debug information of it unlocking them dev spaces. So be warned, if it says that it fails on linux2, it doesn't; it writes _________________ Linksys EA6400/6300v1 Guide
BT Infinity FTTC
BRAS PROFILE: 76.2MBPS DOWN / 20 MBPS UP
BT Smart Business Hub 6A - Modem and AP
Linksys EA6300v1 - Broadcom DD-WRT v3.0-r36104 std
BT HomeHub 5A - Wireless AP Extender
BT Openreach Modem ECI - Unlocked OpenWrt 15.05
If you really must flash it, use the numinit small build a bunch of pages back. Never do a 30/30/30 reset on it.
After flashing the numinit file, flash the xvortex cfe that LOM or Murrkf (I can't remember who) with your info edited in.
Then proceed to try to flash whatever build someone in this thread works, flash it twice, if you can.
Then hold your breath, order a USB to uart adapter, and pray.
So I should skip step 3 (a 30-30-30 in numinit's build) in Devianttwo's instructions and do a WPS to apply instead?
I followed the instructions on page 50, and used the instructions on page 53 to write the CFE. Thank you.
The only question I have concerns the firmware flash. I used DD-WRT 1/19/2016 for EA6400. I was forced to use the recovery tool described below (WPS into Linksys firmware loop), then continued with step 14, as described. My question is with having never used the command(step 13) to flash to both locations linux and linux2, if I reset this router will I have problems? If I do a 30/30/30 after running DD-WRT, will I have problems? Do I need to flash a second time or do anything further, even though I am up and running (second flash, etc.)? Thank you.
Lastly, on stock firmware had a 433mbps connection. I now have a 433mbps connection after adjusting the 5GHz bandwidth to 80 MHz. I do not notice any difference in AC speeds.
Devianttwo wrote:
Latest Instructions (Updated 10/5/2015) to install DD-WRT or the new Test build of Merlin on a linksys EA6300/EA6400v1 Router.
8 ) telnet into router and run the following commands to flash CFE. Username/Password is your DD-WRT Login information.
*EDIT* (9/29/2015) Username/Password is the information you entered when you first booted DD-WRT.
* DO NOT CUT AND PASTE! Adjust these to match the file link and directory names.
Once done unplug the router. Hold the WPS button while plugging it in. Wait for the LED to blink fast. Release WPS button.
Code:
-----------------------------------------------------
EDIT 10/5/2015
One user had an issue at this point that caused the router to revert back to the linksys firmware. Also was unable to access the webpage as it was stuck on the "Spinning Icon"
In order to fix this do the following
1 ) Download the Asus Recovery Tool: http://support.asus.com/download.aspx?SLanguage=en&m=RT-N16&p=11&s=2&os=30&hashedid=WAa6AQFncrceRBEo
2 ) Download your flavor of Firmware (Look Below for links)
3 ) Manually set your Ip on your computer to the following
9 ) Go back into DD-WRT, Set back up user and password
10 ) Re-Enable ProFTPD same as before.
11 ) FTP Desired EA6400 Firmware that you want (Either DD-WRT or the test version of Merlin for EA6400)
Links:
DD-WRT Latest Builds: ftp://ftp.dd-wrt.com/betas/2015/
Navigate to latest folder
Navigate to the linksys-ea6400 folder
Download the linksys-ea6400-webflash.bin
12 ) Open up Putty (Or any telnet program) and connect to 192.168.1.1
13 ) Flash your new firmware with the following commands:
*EDIT* (9/29/2015) When formatting the linux2 partition it may return an error. This is safe to ignore. It is still writing the firmware.
Code:
mtd write /tmp/temp/link-to-firmware-chosen.bin linux2
(Wait for it to write)
mtd write /tmp/temp/link-to-firmware-chosen.bin linux
erase nvram
reboot
* Once again Make sure to point to the CORRECT File name.
**AFTER THIS IS DONE YOUR ROUTER WILL TAKE A VERY LONG TIME TO REBOOT FOR THE FIRST TIME! IT WILL REBOOT MULTIPLE TIMES AND CAN TAKE 2-15 MINUTES OR MORE!! JUST LEAVE IT ALONE AND GO SMOKE A CIGARETTE OR GET SOMETHING TO DRINK!! **
14 ) Navigate back to http://192.168.1.1 If you see the CFE MiniWeb then Continue to wait. If you see your new firmware then you have successfully flashed to the latest version with the newest CFE files. Configure to how you like it
Side Notes:
1 ) After a factory reset the router will take between 2-15+ Minutes to reboot for the first time. It will also Reboot multiple times. (You can check this with a ping or watching the lights on the router). This is normal. It has something to do with the new CFE.
2 ) After Initial bootup your router will take about 2-3 minutes for a normal reboot. This is normal. Also has something to do with the new CFE.
3 ) If you are having issues with your routers Temperature then this fix is for you.
Last edited by RedRover88 on Mon Jan 25, 2016 22:34; edited 1 time in total
Posted: Mon Jan 25, 2016 2:52 Post subject: Surface Connection Problems
I need some help from the experts.
My Microsoft Surface 2 can only see my 2.4Ghz network or my 5GHz network, but not both at the same time. When I look at the available networks, sometimes it will show the 2.4GHz network then seconds later show the 5Ghz network in the same slot. I cannot initiate the connection manually. But it will passively and intermittently connect to dd-wrt. If I open the settings to view the connection, it will immediately disconnect. There were no such problems on stock EA6300v1.
Now I wonder if the vortex CFE had something to do with it. I wonder if my surface sees the router networks as the same Mac device. Did I understand the Mac address modification correctly?
The last __:xx is 77 on my Mac address. Will the 0 & 1 modified be 78 and 79?
et0macaddr XX:XX:XX:XX:XX:77
0:macaddr XX:XX:XX:XX:XX:78
1:macaddr XX:XX:XX:XX:XX:79
Interestingly enough, I have had slow network problems (5mbps) with DDWRT and my Surface 2 in my former E1200 router, not present with stock firmware, which resolved after I flashed to Tomato by Shibby.
Any ideas?
Update:
Holy Smokes. I hid the SSID of my 2.4Ghz network and now my Surface connects to the 5Ghz network without problems.
I believe the Surface associates with the BSSID ignoring the SSID and therefore gets conflicting network connection information and is not able to associate. DDWRT broadcasts two SSIDs (2.4 & 5GHz networks) under the same BSSID (Mac address). Remove one and the authentication happens.
Does stock mask a different BSSID?
Last edited by RedRover88 on Sat Jan 30, 2016 22:09; edited 8 times in total
Okay, I don't visit these forums often, but I am getting bombarded with pm's about some Chinese hosting thing.
So sorry if I didn't read your messages earlier on...
I don't know if the Tomato builds of a similar router will work on this device. We did initially try using some Asus firmware for DD-Wrt but when you couldn't flash back to stock as it would brick. I would think this would do the same on those Tomato builds for R6250 builds Though it should be possible to recover seeing we now have a solution if we do have a firmware brick (due to xvortex cfe). I did notice that Asus-Merlin was a port on the AC-68U...
I wouldn't recommend flashing another manufacturer or even another device's firmware. Netgear will brick definitely brick it, it's safer to use Asus but it will still brick.
Someone suggested the Koolshare cfe is different to the xvortex cfe. Here's the pass for you to have a look at.
Posted: Wed Jan 27, 2016 13:40 Post subject: Success
Just wanted to thank everyone for their help.
I procured 9 of these Linksys EA6300v1 routers at a significant discount, so was eager to get DD-WRT on them.
I tried a bunch of things, but was finding that the GUI would fail trying the normal image (linksys-ea6400-webflash.bin)... it would get to about 30% in the progress bar, then fail, saying something like "it's too large".
So I went back (as suggested here by several folks) to page 50 & 53 and grabbed the "super-hacky smaller version" (linksys-ea6400-numinit-super-hacky-smaller-version.bin). I flashed the device with that, fully prepared for the eventuality that it may brick the device, but it worked! Then, from within DD-WRT, I upgraded to the January 16th build that was failing before, and it completed.
3 ) do a 30/30/30 with reset button to clear nvram.
4 ) log into DD-WRT. Create a User/Password
5 ) MAKE A BACKUP OF YOUR CFE BY BROWSING TO http://192.18.1.1/backup/cfe.bin
*You will need this if you EVER want to revert back to stock.
6 ) Enable ProFTPD and create a new user (SSHD does not work on the stripped down version)
Code:
-> Services
-> NAS
-> ProFTPD
7 ) FTP your modified CFE with that user
* REMEMBER TO ENABLE BINARY MODE IN FTP. suggestion: Use WinSCP
8 ) telnet into router and run the following commands to flash CFE. Username/Password is your DD-WRT Login information.
*EDIT* (9/29/2015) Username/Password is the information you entered when you first booted DD-WRT.
* DO NOT CUT AND PASTE! Adjust these to match the file link and directory names.
Once done unplug the router. Hold the WPS button while plugging it in. Wait for the LED to blink fast. Release WPS button.
Code:
-----------------------------------------------------
EDIT 10/5/2015
One user had an issue at this point that caused the router to revert back to the linksys firmware. Also was unable to access the webpage as it was stuck on the "Spinning Icon"
In order to fix this do the following
1 ) Download the Asus Recovery Tool: http://support.asus.com/download.aspx?SLanguage=en&m=RT-N16&p=11&s=2&os=30&hashedid=WAa6AQFncrceRBEo
2 ) Download your flavor of Firmware (Look Below for links)
3 ) Manually set your Ip on your computer to the following
9 ) Go back into DD-WRT, Set back up user and password
10 ) Re-Enable ProFTPD same as before.
11 ) FTP Desired EA6400 Firmware that you want (Either DD-WRT or the test version of Merlin for EA6400)
Links:
DD-WRT Latest Builds: ftp://ftp.dd-wrt.com/betas/2015/
Navigate to latest folder
Navigate to the linksys-ea6400 folder
Download the linksys-ea6400-webflash.bin
12 ) Open up Putty (Or any telnet program) and connect to 192.168.1.1
13 ) Flash your new firmware with the following commands:
*EDIT* (9/29/2015) When formatting the linux2 partition it may return an error. This is safe to ignore. It is still writing the firmware.
Code:
mtd write /tmp/temp/link-to-firmware-chosen.bin linux2
(Wait for it to write)
mtd write /tmp/temp/link-to-firmware-chosen.bin linux
erase nvram
reboot
* Once again Make sure to point to the CORRECT File name.
**AFTER THIS IS DONE YOUR ROUTER WILL TAKE A VERY LONG TIME TO REBOOT FOR THE FIRST TIME! IT WILL REBOOT MULTIPLE TIMES AND CAN TAKE 2-15 MINUTES OR MORE!! JUST LEAVE IT ALONE AND GO SMOKE A CIGARETTE OR GET SOMETHING TO DRINK!! **
14 ) Navigate back to http://192.168.1.1 If you see the CFE MiniWeb then Continue to wait. If you see your new firmware then you have successfully flashed to the latest version with the newest CFE files. Configure to how you like it
Side Notes:
1 ) After a factory reset the router will take between 2-15+ Minutes to reboot for the first time. It will also Reboot multiple times. (You can check this with a ping or watching the lights on the router). This is normal. It has something to do with the new CFE.
2 ) After Initial bootup your router will take about 2-3 minutes for a normal reboot. This is normal. Also has something to do with the new CFE.
3 ) If you are having issues with your routers Temperature then this fix is for you.
**UPDATE: 10/6/2015 When Flashing from Asus-WRT Merlin back to DD-WRT **
(Thanks Silent_Swift)
In order to flash from Merlin back to DD-WRT You would want to do the following
1 ) Make sure SSHD Is in fact Enabled.
((Administration->System->Allow SSH))
2 ) SSH Into the router
3 ) Type the following commands in the console
Code:
cd /tmp
**UPDATE THIS COMMAND TO THE LATEST BUILD!**
wget ftp://ftp.dd-wrt.com/betas/2015/09-28-2015-r27858/linksys-ea6400/linksys-ea6400-webflash.bin
mtd-write2 linksys-ea6400-webflash.bin linux
4 ) Unplug the router.
5 ) Hold the WPS Button down on the router and plug it back in
6 ) Wait for the Fast blinking light to start up and release the WPS Button.
**ALWAYS DO A FACTORY DEFAULT RESET WHEN SWITCHING FIRMWARES FROM ONE TYPE TO ANOTHER**
7 ) After words continue to resetup your router.
Sorry to quote this entire process, but I am trying to figure out why some of these steps are required.
I have an EA6400 and I was able to flash it to the stripped down initial flash, perform a 30/30/30, and then install the latest EA6400 nightly from the betas directory without any problems. Is there something that I am missing as to why you need to go through all the CFE updates and multiple flashes manually via command line?
I still havn't tested everything yet, so there might be issues, but I am just trying to understand why you can't just update using the webflash once the initial version is installed like I did.
I flashed ddr-wrt few times and also did 30/30/30, now router seems back to linksys firmware, and after login in is endless "Spinning Icon"
Tried the following many times, always unable to get rescue mode. Any idea?
Code:
-----------------------------------------------------
EDIT 10/5/2015
One user had an issue at this point that caused the router to revert back to the linksys firmware. Also was unable to access the webpage as it was stuck on the "Spinning Icon"
In order to fix this do the following
1 ) Download the Asus Recovery Tool: http://support.asus.com/download.aspx?SLanguage=en&m=RT-N16&p=11&s=2&os=30&hashedid=WAa6AQFncrceRBEo
2 ) Download your flavor of Firmware (Look Below for links)
3 ) Manually set your Ip on your computer to the following
Nothing to worry about 
Though it should be possible to recover seeing we now have a solution if we do have a firmware brick (due to xvortex cfe). I did notice that Asus-Merlin was a port on the AC-68U...
I just spent hours doing handwriting verification for the captcha.