Discussion in 'Other Firmware Projects' started by cybrnook, Sep 24, 2015.
Discontinuing this guide.
Almost 250 views and no response I guess that means it just works and nobody has anything to add .
If there are any areas that were written unclear, please let me know.
Congrats great job and tutorial, i am on r7000 and Xvortex since first released and now .55-2 and runs just fine.
Thaksfully to Merlin & Xvortex.
I am also on R7000 with xvortex so i did not reply. Congrats btw for the tutorial. Does the CFE fields are the same as in your tutorial ?
(secretly, I also am on the R7000 running XVortex/RMerlin 54_2 ) I made this guide while setting up a router for my brother in law who still lives at home with his parents. I had them on a TP-Link Archer C7 v2. However, we started to have an issue where he would call me (or text) me every other day when the router would lock up. 2.4 would drop completely, and the link to WAN would die. Hard lined, you could still connect to the router, and a reboot would solve the issue, until it came back within 48 hours. Since they have an ATT virtual cell antenna, land line magic jack phone, and all smart phones and computers on it, when it went down it always became a big issue. Especially since my in-laws are a bit older. Any hiccup in technology becomes an ordeal, especially when the phone goes down. Plus, I feel bad for him having to absorb the flak every time something happened.
So I wanted to get him on something affordable, but also stable. For $50 - 75 (which the EA6900 can be found for, since it gets poor reviews on stock firmware) I thought this would be a great router for them. Especially once I got it flashed over to an RT-AC68U/R7000 (since they are all on the same platform).
He is going on over a week of 24x7 up time Problem solved, and worlds better wifi range to boot.
For the most part yes they are the same "main" fields. However my logic is as follows (when using XVortex's 22.214.171.124 provided CFE for your target):
On Target (NEW METHOD):
et0macaddr=et0macaddr (from source)
secret_code=(your private secret_code from source)
hello, i need some help with some things.....
i have installed the asus merlin without the updated bootloader, and now i can't return to stock or ddwrt to upgrade the bootloader.
i have the access to ssh but the command mtd is not available on the firmware.
i'm using the ea6900_378.55_2
thanks in advance
Just as an fyi, doing anything on this router outside of stock firmware while still using the stock cfe is just asking for trouble. Your nvram variables are likely already a mess. You would be doing yourself a favor to erase your nvram after upgrading cfe's.
Follow Jernau's instructions close to the bottom to see how to flash under asus merlin (make sure to use the ea6900 cfe above and not the r7000 in his post):
Pay special attention to:
"./mtd-write -i new-cfe.bin -d boot
(mtd-write is in the zip file I linked I don't think mtd-write2 included in the firmware can write to boot)"
Thank you very much! You saved my router. It dropped out every day until now!!! I can not understand they sell them like this
Just 2 adjustments/remarks:
Link to XVortex EA6900 CFE and CFEdit Tool
-> this link does not give the editor (after searching for 20 min I found it somewhere else)
After you have hit upload, it will appear as though the interface has frozen. That’s fine, just BE PATIENT. If all goes well, will take maybe 10 – 15 seconds and then you will see
-> This took me like 2 min in chrome
But is is working now. Otherwise I had to bring this router back!
Aye yai yai you're right. The link was missing the tool. I changed the link to a zip file now that contains the edit tool and the cfe.
For my testing I was using Internet Exploder, took about 15 seconds. Perhaps the web server is temperamental to browsers?
Either way, glad it worked out for you, thanks.
Stupid question I will be having Directv installed Wednesday 10/14 I expected to have the new WRT-1900acs in my hands but alas the ship date is now OCT 14th Pickup October 15th. So I was wondering if I could just use the Brain-Slayer DD-WRT image as an improvement over the existing factory image build from linksys/cisco/belkin. I can absolutely follow this guide (I am technical) just seems like a cadre of steps if I am getting a new router a day later anyway. I just want better speed for the Directv tech so he does not blame my "router" for any setup issues he runs into when configuring the Genie Wireless I am getting good coverage with my spectrum analysis utilizing a RE1000 to cover the rest of my house albeit wave speed test is around 30MB but it is consistent throughout the home. Or do you believe that I will not see any improvement or lack of stability by using the Brain Slayer build vs the factory image build from Cisco/Linksys?
For the record I will definitely flash this router for my daughter to use when she moves out for many of the reasons you state for yourself but I don't want to brick my only working router without a backup as I have already given away 4 "old" routers that have already been flashed with Tomato or Open WRT and even a DD-WRT bridge.
Thanks in advance for your response! Great guide by the way I may write a script to automate this process as per this extensive guide if/when I do I will be sure to upload it to make this easier for people in the future. (of course they still need to dl the tools but you can only bring them to the water)
Also my Ea6900 does not have a "power switch" so I assume you mean unplug understanding that this manual is designed for a few different platforms.
If it's working fine for you now, I don't think dd-wrt would yield you any benefit from a general use stand point. Performance wise, I personally, always had worse performance on dd-wrt when compared to other open source firmware.
With that said, if you do want to try open source firmware (XVORTEX being the recommended), I would recommend you go all in. You need to flash the custom bootloader if you want to run anything other than stock. That is my recommendations.
And yes, you could unplug as well ( no 30 30 30 though, I never recommend that). The basic reason I ask to power off and back on is for you to cleanly get into the recovery Web server that comes with the custom cfe. You need to be coming from a powered off state while holding the reset button.
Good luck either way, wrt1900ac v2 is supposed to be nice with openwrt.
Thank you OP for the guide. My main router right now is the Asus RT-N56U with Padavan firmware and my spare is a ea6900 (got it cheap). For sure will follow your guide in the near future. Thanks again for the hard work.
One question is if my mac address ends with 00 does the above mean
0: mac address +1 which means last number is now 01
1: mac address +2 which means last number is now 02
Also the last part, do I wait till it reboot and turn it off and do the nvram reset?
If your et0macaddr ends with :00 then you should be safe with 0: being :01, and 1: being :02. As long as they are different you should be fine. The firmware will calculate 0: and 1: anyways on boot, but still, better to make them correct in the CFE.
the NVRAM reset I am recommending to do directly after you successfully flash the new XVortex firmware. As an alternative, you can wait for the new firmware to boot (then go through the entire setup) then from the admin page you can reset the router. But I find it easier to just hold the WPS button while powering on the router. Once the lights start flashing, you can let go and NVRAM will reset, then reboot.
And I think it's time to make the EA6900 your main router. It's so much better than the RT-N56U. My brother in law used to have one, we also ran padavan. But the internal antennas really kill the range on that unit.
Cybrnook, I got to the last step of the guide. When I tried flashing the Vortex firmware from the Asus CFE mini server, it indicates that the firmware image is invalid. However, I was able to flash the DD-WRT firmware without any problem. Any idea of what's wrong?
Only make sure you unzip the XVortex firmware. Also make sure you downloaded for ea6900 and not accidentally for r7000 or something.
Thanks for your response, Cybrnook. I was thinking about that. So I just need to flash the .trx file and it should work?
Yes, from the asus web server you want to flash the .trx file. As that is the native format for Asus firmware, that is what the web server will likely take.
Okay. One last question. If I want to revert to DD-WRT, I could just flash the DD-WRT firmware from the Asus web server? No additional steps needed?
I have not reverted from XVortex firmware, but yes that sounds about right. You may actually be able to flash from the XVortex webgui. Only this time use a newer build for the EA6900, not an initial flash image.
Please to be safe check "Important" paragraph at first page and first Xvortex post here http://www.linksysinfo.org/index.php?threads/asuswrt-merlin-on-netgear-r7000.71108/ you'll find your question full answered there.
I am not confident the back to stock firmware in the r7000 thread will work for the ea6900.
Pehaps some guy in Xvortex forum may clarify, i didn't tested that router.
I think the best practice for switching firmware for the ea6900 is to flash via the webserver. Then once on XVortex firmware you can flash via the webgui. (As long as you are on the custom cfe)
Thank you very much cybrnook.
Now I have a problem, I just finished doing according to the guide. One thing the mac address in the stock-cfe is different from the mac address printed on the bottom of the ea6900 which is the same mac address as ddwrt shown. I boot up with xvortex firmware and now my mac address is totally different. Should I edit a new cfe file with the correct mac address and reflash? If I do, can i just do the putty step of writing the new cfe or do I need to go through the steps again? Tia
You want to be taking the mac address from the cfe backup you took (EDIT: take MAC from the bottom of the router). Once modified (correctly) you can just flash in putty again. After you flash, make sure to reset the router via the webgui so the firmware reloads the cfe values.
the mac address from the cfe backup is totally different from the one printed on the bottom of my ea6900. My Linksys is now using a Epigram inc mac address. Does the vortex firmware has telnet and SSH enabled? I need to rewrite a new cfe and move it to the ea6900 to reflash. Thanks in advance.
ok thanks, so I suppose I shouldn't have any problem instead of program reporting my ea6900 as a Linksys device but now a Epigram Inc device. By the way, your guide is very easy to follow except don't know why my back up cfe has a different mac address.
If I were you, I would open my backed up CFE (EDIT : use MAC from bottom of router ), see what my original et0macaddr was , take that and use the basic +1 and +2 as above. Substitute those values into XVortex's provided CFE and re-flash that to your router (Using winscp and putty from above) after you have enabled ssh in the firmware.
Then check to see what is being reported. You have not followed the process as I have instructed you to (you deviated), so I am not surprised you may see something strange. However, this is an easy fix, once you do the above.
Without getting too winded, your router has a few mac address. The main mac's we are dealing with are for the wifi. So I am not surprised that it does not match your mac on the bottom as that is you lan mac. (Of course, assuming you have not bought a used router someone else has already tampered with).
Anyways, good luck. I trust the path is clear for you now.
I think I know what may be wrong. I have used the router with stock firmware for a week in August or maybe because it is a refurbished item. I did not reset it and just went in (stock firmware) and flashed ddwrt (the one you provided) and then follow your guide exactly. Anyway after enabling ssh, winscp won't let me log in via sftp only scp and putty won't let me telnet in only ssh. I better leave it now and research more how to reflash this.
that's fine, winscp letting you in via SCP is completely okay, as well as coming in with putty over ssh, this is all good (as long as you are in, you are in)
I am able to put the new-cfe.bin into /tmp/home/root directory via winscp. but when I execute the following command, putty gave me error something like -sh mtd not found. any idea? Tia.
mtd unlock /dev/mtd0
mtd write –f /tmp/home/root/new-cfe.bin /dev/mtd0
or should i use the following command instead (from R7000 thread) since my ea6900 is already on vortex merlin 378.5.4_2 firmware
chmod +x ./mtd-write
./mtd-write -i new-cfe.bin -d boot
Well, you are sooo close. The difference here, and sorry I forgot, is that you are flashing your CFE under Asus Merlin firmware which does not have the mtd-write utility by default.
So yes, you want to download the CFE package from the R7000 thread to get access to the mtd-wrte utility. Then upload that via winscp into the same folder (/tmp/home/root) as your new cfe. Set permissions to executable (chmod 755 mtd-write, or chmod +x mtd-write) and then flash the bootloader.
read Jernau's thread and use what he links, he makes special mention of the version of mtd-write he used:
Asuswrt-Merlin on Netgear R7000
All done, thank you very much for your help.
Better to discuss in here, than in the R7000 thread. But looking forward to the next EA6900 release @XVortex
Thanks for all the work you do! You make it all possible.
Thanks to you too, cybrnook. Your guide is so easy to follow, took me less than 30 minutes to cross flash it. My 1st ea6900 took me more than 2 hours and that was following another guide over in ddwrt forum. By the way, I flashed the router with opera browser and I did not encounter any problem.
I agree that the guide was very easy to follow. I successfully flashed the Vortex firmware on my EA6900. It is very stable and I don't think I would go back to dd-wrt any time soon. Thanks cybrnook for putting together the easy-to-use guide and your support.
Just noticed this when I was flashing a friend's ea6900 this morning, his stock cfe has the same mac address as my back up stock cfe, I also checked someone else's backup cfe which he posted on pg 17 of the other thread at ddwrt forum and he has the same mac address. This mac address is different from the original mac address of each ea6900. There must be a bug somewhere on the original cfe that when you extract it, it changes your original to this particular mac address.
Good find, I will say that the 2 x units I have done so far had unique MAC's (Sealed, Retail units founds cheaply online). I doubt there is a bug in the dd process, as that is a basic low level UNIX command. So I have doubt that one entry is changed when when the dd process takes place. (dd is just a UNIX way to "convert/copy")
Also, is your friends router a refurbished unit as well? I would not be surprised if the repair center that is refurbishing these is loading the same generic, initial image on all these units in mass, then shipping them back out as "fixed". It would be the most cost effective way instead of each tech reading the bottom, building the unique mac into a uniquely built CFE then flashing that. No way that's what they are doing.....
I suspect this may be more along the lines of what is happening. This may be something to watch out for, as the refurb units are very popular for this router ($60 here in the U.S.). I wonder what issues this would pose having 2 x refurb units on the same network, if any conflict would happen.
In this case I would just bump your last digit from :01 to :02 and then do +1 and +2 off that if you are going to put a second unit on the same network.
Added Tomato to the list. I have not tired it, but it should flash just fine as it is also a .trx file, and the Asus Web Server will accept .trx files. So you theoretically substitute the initial loading of XVortex for Tomato Shibby if desired.
(OR Tomato Shibby if you choose):
Interestingly, I also have the same MAC address as provided by apvmtan and I brought my EA6900 brand new at Best Buy. Cybnook, do you recommend editing and reflashing the cfe again to correct the MAC address or just leave it be? Now I'm not even sure how to get the true MAC address.
I think if a lot of people have the same MAC then it will cause a problem with the DDNS registration.
@XVortex what do you think? Do you remember having the EA6900, maybe you still have the original CFE dump? Did you also have the same et0macaddr? I checked my 2 x backups as well and both are the same as the two users above, et0macaddr=00:90:4C:0F:F0:01
Instead of pulling the mac from et0macaddr, should we modify our steps and use the MAC from the bottom of the router as et0macaddr, then +1 , +2 from there?
Let me clarify this mac address thing. This mac address (et0macaddr=00:90:4C:0F:F0:01) only appear on the backup stock cfe file, the file that you extract and save aside as per post #3 instruction. So if you don't want the above mac address, don't put it in the xvortex modded asus cfe when you edit the cfe but enter the mac address printed on the bottom of the ea6900 before you flash it and you'll be ok.
Well, we are also dumping it to have a backup of the original bootloader. Not that you would ever want to go back...
I agree with you, why would anyone want to go back, the stock firmware is very buggy.
If I reflash the CFE, do I have to reflash the firmware as well?
No, but you will want an nvram erase afterwards.
Just to confirm. This is the same as resetting the NVRAM "by holding the WPS button while powering the router on, holding until the Linksys logo starts to flash."
That's what I did.
You should not have to take a MAC address from the stock CFE.
For Linksys it is a abstract MAC for recovery. It is the same for all devices.
Real MAC address stored in the nvram or at bottom label.
Here is my EA6900 stock CFE.
Thanks, I will change the steps in the guide later today.
Okay @XVortex @apvmtan @mrdigital I revised two paragraphs in the third section.
I'm trying reflash the cfe to correct the mac address issue. I'm having trouble logging into the OS layer via WinSCP. I'm on the Vortex firmware. what is the username and password?
Make sure to set WinSCP to scp protocol (it defaults to sftp). Default user name / password is admin / admin. Unless you set a new password, in that case use that.
This is what I did to correct the mac address issue, I have vortex merlin 378.54_2 firmware on the ea6900.
1) Download the cfetool.zip from post #57 of R7000 thread
2) Extract cfetool.zip, it has two files (mtdwrite and nvsimple)
3) a corrected new-cfe.bin file with the correct mac addresses
4) Enable SSH in the firmware
5) Run Winscp in scp protocol, your default (target) folder should be tmp/home/root
6) transfer mtdwrite nvsimple new-cfe.bin (three files) to tmp/home/root
7) run putty in ssh protocol
8) type pwd to make sure you are in tmp/home/root folder
9) type ls -l to make sure all three files are in that folder
10) type the two command below one by one
chmod +x ./mtd-write
./mtd-write -i new-cfe.bin -d boot
11) turn off router
12) holding the WPS button while powering the router on, holding until the Linksys logo starts to flash
Hope this help others.
By the way, the username and password is the username and password of the firmware eg if you have set your username and password as admin admin use that for both winscp and putty.
Thank you apvmtan and cybrnook. I will follow your guide to correct the mac address.
One correction, all that you need to upload is mtd-write and new-cfe.bin. Other than that, very thorough.
I successfully re-flashed the cfe with the correct mac address. Thanks again for providing the instructions to fix this issue.
@XVortex has released 378.56_0 for EA6900
Very Thankful sir Roman for your continued support.
how to flash tomato from Xvortex merlin firmware and if tomato is better? Tia
@XVortex, in your opinion on the EA6900, do we need a "back to stock" before transitioning to a new firmware. Or would we be fine going from XVortex to Tomato by flashing through the web recovery server. (Or even flashing directly from within the XVortex gui)? Do we need that middle step, like R7000?
No. There is no "back to stock" for EA6900. Due to the custom CFE it is almost impossible.
And due to the custom CFE you can safely flash what you want through web server recovery or even through GUI.
But do not forget to erase NVRAM (wps btm).
Awesome, that's what I was thinking (hoping) you would say. But, is always best to ask the boss first ;-)
@apvmtan , you can flash from webserver or directly in asusmerlin.
Thanks but do you know if Tomato 1.32 is stable, last time I heard, some of ea6900 function does not work well with 1.28.
No idea, haven't run Tomato since my RT-N66U (years ago). However, I would say try it yourself as you never know who is posting negatively online. Very well could be someone running the stock bootloader and when they ran into issues, the pointed at Shibby instead of their own ignorance.
All in all, I think Tomato is a good option. (But keep in mind you get no hardware acceleration like you do on XVortex)
I would be interested to hear what you have to say after running it for a bit. "Stable" is in the eye of the beholder.....
To be honest, last time I ran Tomato was with the WRT54G many years ago. I have no problem with Vortex firmware, so better like they say "if it ain't borke, don't fix it"
I followed the instructions for updating the CFE and installing the XVortex firmware.
It's working sort of...
Wired networking is fine
5GHz netowrking is fine
However, my 2.4GHz network is not showing up for any of my devices.
Did I miss something?
Set your channels to a fixed chanel for your region. I assume you have everything on auto?
I'll give that a try. Out of frustration, I installed Tomato late last night and it seems to work fine.
No worries, it happens. If you read over the R7000 thread, you will see many people had your same issue. It happens because XVortex has given country code of #a in the bootloader and firmware which basically unlocks all global channels. However devices in regional areas only work on certain channels. So you need to know what channels are available in our country and set your wifi channels accordingly.
My short experience is that Tomato 1.32 (AIO) is running perfectly stable. That being said... I REALLY liked the XVortex interface as I was poking around. I can't wait to get home and flash it again to see if I can get it working with manual channels.
What other benefits does XVortex bring to the table?
Now that you mention it... I did see 6+8 or something like that next to the 2.4GHz settings... It didn't even strike me as odd at the moment, but 8 is not a normal channel at all.
A few things about the tutorial that I noticed.
- There is no "switch" on my ea6900. I just pulled the power adapter.
- After the first flash, the router tried to go to a named page that didn't exist. I forget what the domain was, and it was on a weird port (52000 or something). I had to manually replace the named domain with 192.168.1.1. If it does it again tonight, I'll take better notes.
- The directions for updating the CFE through me for a loop at first. I think a better step by step is needed there... it wasn't clear at first that I had to open the provided .bin first. That is mentioned after the fact, but I was able to figure it out.
All in all, it was an extremely good tutorial. I was happy that I didn't have to go to 10 sites to figure everything out... even though I would have.
XVortex/RMerlin offer hardware acceleration. Plus, I just enjoy running it, it has been rock solid for me. There is a wealth of knowledge over in the SNB forums in regards to RMerlin firmware and many little guides and tools. Much more than what is available for Tomato. As well, the XVortex/RMerlin base is continually being updated by Asus, then RMerlin. Tomato has been in a stuck state for a while now , with many tweaks and bolt ons.
Everything seems good now that I manually set a channel.
version 1 has no power switch while version 1.1 has one.
378.56_2 released. Many bug fixes:
I just want to thank you man, after almost 1 year with DD-WRT and constant reconfiguring after any power outage or random reboots, the 32k bug, poor AC speeds (less than 100Mbps), now with your guide I could finally install this firmware and enjoy greater speeds and stability, I can watch 1080p content wirelessly on mi Rpi (I had to use a wireless repeater to wire it), configured openVPN server on it and get full speed connections.
I just have 1 issue to the moment, I have an ubuntu server with transmissionbt on it, I port forwarded the correct port and can't seem to get it open, I check it on transmission client and keeps saying its closed, I even DMZ the server with the same results, I disabled the firewall and still. Could anyone help me with this? I would be very grateful.
Have you tried telnet from another system on the same network to see if that port is actually open or not? May be your ubuntu box.
I've tried online services to check the port, but the strange thing is that I get full download speeds, and when I connect to the OpenVPN server I can see my 2 raspberry pi's, access them as I was in the same network, the router config page, everything, except, the ubuntu server, I've been trying to replace it with the ea6900 anyways now that it's working perfectly, two wxternal hardrives, install and config transmission with flexget and I won´t need the server anymore. I'm really hapy with my router's new performance.
I have a Linksys ea6900 V1.1 and I have modified the cfe_ea6900.bin file that came with the CFE Edit tool transferred it to the router via winscp ran the command in putty mtd unlock /dev/mtd0 but when I attempt to run mtd write –f /tmp/root/new-cfe.bin /dev/mtd0 I get the following:
root@DD-WRT:~# mtd write –f /tmp/root/new-cfe.bin /dev/mtd0
Usage: mtd [<options> ...] <command> [<arguments> ...] <device>
The device is in the format of mtdX (eg: mtd4) or its label.
mtd recognizes these commands:
unlock unlock the device
erase erase all data on device
write <imagefile>|- write <imagefile> (use - for stdin) to device
Following options are available:
-q quiet mode (once: no [w] on writing,
twice: no status messages)
-r reboot after successful command
-f force write without trx checks
-e <device> erase <device> before executing the command
Example: To write linux.trx to mtd4 labeled as linux and reboot afterwards
mtd -r write linux.trx linux
Can you derive from that something I may have done incorrectly? Any help you could provide would awesome.
What you've done so far is amazing.
Looks fine: mtd write –f /tmp/root/new-cfe.bin /dev/mtd0
make sure you run the unlock command right before you flash (looks like you did)
make sure that you have uploaded the new .bin to the /tmp/root folder. You should be there by default.....
You can check what folder you are in by using "pwd"
If you are going to use the naming systax I gave in the example "new-cfe.bin", please make sure that is what you have actually named the .bin file.
Lastly, make sure the permissions are open on the .bin file, execute:
"chmod 777 new-cfe.bin" without the "" from within the /tmp/root folder (where you should have your newly uploaded new-cfe.bin file)
@XVortex is working on a new release. Will allow you the ability to use the Asus Android app to manage router.
I am on 54_2, wondering if I can update to 56_2 with the firmware web GUI or I have to go through the CFE mini server to update firmware? TIA
I believe you can go through Webgui
Thanks, I'll try and if it doesn't work, I will use the other method. Anyway, it seems that 56_2 is not better than 54_2, so I'll wait for the new one and see.
hey guy im using window 7 ult.
on the putty part i can type in the user : root
but cant type in password is like freeze but i can enter key and right click mouse that it. any help would appriciate.
Try either the latest or an older version of putty and see if that helps. http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Have read through this excellent tutorial and am about to take the plunge. One small question (may be moot), is in the final steps above, it says to reset NVRAM after uploading firmware, XVortex in March said to clear NVRAM then upload firmware. Does it make a difference?
Hold red reset during power up waiting 10-15 sec
Reset NVRAM using WPS button
@XVortex over on ddwrt EA6900 thread (cannot create link yet)
Enable SSH by dd-wrt webinterface at the "services".
Connect by ssh to the router
Copy the cfe here: /tmp/cfe_ea6900.bin
Then flash it: snip
Reboot the router, enter recovery, clear nvram, upload firmware...
I am going with your directions...
UPDATE: Never having done a dd-wrt or linux commands, completed the upgrade to EA6900_378.56_2 in about 2 hours after a number of hours previous days, reading thru and prepping, and it seems to be working very well. I do speak dos from an earlier age, but linux took some thought and time, especially looking up and understanding the commands. Wow.
Thanks in advance, and compliments for the well written tutorial!
Follow my steps please. The NVRAM reset prior to flashing will do nothing for you (unless your NVRAM is already corrupted by running DD-WRT without a custom bootloader). NVRAM reset after flashing will make sure you load all the new variables needed for the new firmware.
Back in MARCH and moving forward, in DD-WRT you have folks who are dead set on leaving the buggy Linksys bootloader (1.0 and 1.1), but still wanting to run DD-WRT. And this yields all kinds of NVRAM issues because of the NVRAM corruption that happens with the bugged Linksys bootloader. In that sense, you likely need to reset NVRAM prior to doing anything because the variables would be sooo screwed up already. But what we are doing bypasses all this, so no worries and no need to reset prior (unless the above sounds familiar and applies to you). My guide is written in the sense we are starting with a clean slate, linksys router running linksys firmware.
You have someone who, basically not being familiar followed through the tutorial and it worked the first time. The only slight puzzle (in the tutorial steps) was when getting to the recovery web interface after holding down the reset for 10-15 sec, the web interface came right up, but there were no black screen ping "reply from 192.168.1.1" responses as shown in the screenshot. So, repeating reboot got the same XVT -CFE miniWeb Server - I just went ahead and uploaded 56_2 and after about 2 minutes got the Upload Completed page....Voila.
That is absolutely correct. The black ping page you see is a completely separate page window I have opened. Unrelated to the steps.
I am just demonstrating what a ping against the router would look like when the webserver is up and running.
Good job, and enjoy your "new" router.
Great news, since I was kind of sad not being able to use my payed DD-WRT app, thanks man for this announce (y).
Just to be sure, passwords won't show, are you sure this is not happening to you?
@XVortex ,you think you would be so kind as to compile some of the alphas for the EA6900 so the user base can see the app control functionality, and basic new fixes and functionality? Would be much appreciated.