Discontinuing this guide.


cybrnook

Addicted to LI
Member
That's fine, seems to be about normal operating temp for this platform (If I recall correctly, XVortex mentioned it somewhere that the max was much higher as the R7000 users also see temps in the 70's)

My brother in law's, who I have on an EA6900 also run's around 80 for 4 months now, no issues so far.
 

Faran_

Serious Server
Registered
Hello !

First post here :)

I seem to have the same problem as thenmens http://www.linksysinfo.org/index.php?threads/asuswrt-merlin-tomato-shibby-on-linksys-ea6900.71718/#post-268746

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


root@DD-WRT:~#


I´ve used "pwd" and "ls -1" to see that im in the right folder and to ensure that the file exist.

root@DD-WRT:~# pwd
/tmp/root
root@DD-WRT:~# ls -1
new-cfe.bin
nvram_dump.txt
stock-cfe.bin

And i have also used the "chmod 777 new-cfe.bin" command. Should it give a answer back or something ?

root@DD-WRT:~# chmod 777 new-cfe.bin
root@DD-WRT:~#

Does someone have a solution ? :rolleyes:

Btw in putty should i use the telnet or the ssh connection type? I have used both with no success..

Thanks
Faran_
 
Last edited:

apvmtan

Networkin' Nut
Member
Newbie question. My network card died and my new network card can no longer log on to the router or get internet access due to I setted DHCP server to assign ip address to my old network card mac address.

My question is how do I reset the ea6900 to default, I have 378.54_2 firmware with custom cfe. TIA

One last thing, is ea6900 with 378.54_2 default user/password is admin/admin Thanks again.
 

cybrnook

Addicted to LI
Member
Newbie question. My network card died and my new network card can no longer log on to the router or get internet access due to I setted DHCP server to assign ip address to my old network card mac address.

My question is how do I reset the ea6900 to default, I have 378.54_2 firmware with custom cfe. TIA

One last thing, is ea6900 with 378.54_2 default user/password is admin/admin Thanks again.
Power off the router. Then, while powered off, hold the WPS button and turn on the router. Keep holding the WPS button for about 20 seconds then let it go. The lights should flash and the router should reboot to a fresh install.

On XVortex there is no default username / password. The firmware wizard at the beginning will have you set it up.
 
Last edited:

m3digi

Serious Server
Member
I followed the guide for my EA6900, but discovered the issue with the MAC Address after everything was set up. I did a reset on the router to clear the existing configuration.

My goal was to the initial Brain Slayer Build to restart the process. I then uploaded a revised CFE with the correct MAC address values.

I had no success uploading the initial build via the GUI. I resorted to the DD-WRT command line to do so. Once I executed the command, the DD-WRT console remained active.

Since doing that, the GUI no longer appears after reboot. Mysteriously, the DD-WRT console no longer showed the Initial Brain Slayer build (#23158), but the latest build (28846).

I configured the build. After reboot, I am now returned to the 23158 build. Have I corrupted my NVRAM? Is there any way to fix this, or return to the stock build? I'm worried that I have damaged my EA6900.
 

Idmpcthis

Serious Server
Member
Hi!

Thanks for the guide, it was really easy to follow. I went all the way to the end and successfully installed Vortex Asuswrt firmware.

However, I have a problem now that my PPPoE connection doesn't work, and I can't figure out why (I'm pretty sure my username and password are correct).

Is it possible to return to the original linksys firmware just for me to see if the issue only happens with Asuswrt or if I actually broke something?
 

apvmtan

Networkin' Nut
Member
I assume that both of you have successfully flashed the new cfe, if that is the case you should both have a new bootloader and should able to use the following to load any firmware:
"With the router powered off, press in and HOLD the red “reset” button on the back of the router. Continuing to hold the reset button in, flip the power switch on, powering up the router.
You will want to hold the reset button for approx. 10 – 15 seconds (sometimes less, sometimes more). Once you feel you have held it in long enough, attempt to navigate back to 192.168.1.1, you should see:"

Please also make sure to reset the router after finish flashing new firmware, ie by pressing wps button while turning on router, hold until the "Linksys" logo starts to flash.

Please refer to the guide in this thread on post #1 for both steps. Better still, wait for cybrnook to confirm both steps.
 

cybrnook

Addicted to LI
Member
I followed the guide for my EA6900, but discovered the issue with the MAC Address after everything was set up. I did a reset on the router to clear the existing configuration.

My goal was to the initial Brain Slayer Build to restart the process. I then uploaded a revised CFE with the correct MAC address values.

I had no success uploading the initial build via the GUI. I resorted to the DD-WRT command line to do so. Once I executed the command, the DD-WRT console remained active.

Since doing that, the GUI no longer appears after reboot. Mysteriously, the DD-WRT console no longer showed the Initial Brain Slayer build (#23158), but the latest build (28846).

I configured the build. After reboot, I am now returned to the 23158 build. Have I corrupted my NVRAM? Is there any way to fix this, or return to the stock build? I'm worried that I have damaged my EA6900.
Sounds like you need to confirm you flashed the CFE correctly. If so, do as apvmtan suggests and get into the recovery webserver, flash a fresh firmware of your choice. After flash (like the guide says) do an NVRAM reset. Appears like you already came in sideways and maybe already had DD-WRT flashed without the bootloader.....? If you followed the guide (mine), then you shouldn't have a CFE issue. That only comes from flashing DD-WRT on stock bootloader.

Hi!

Thanks for the guide, it was really easy to follow. I went all the way to the end and successfully installed Vortex Asuswrt firmware.

However, I have a problem now that my PPPoE connection doesn't work, and I can't figure out why (I'm pretty sure my username and password are correct).

Is it possible to return to the original linksys firmware just for me to see if the issue only happens with Asuswrt or if I actually broke something?
Someone a few posts up talked about ppoe and I sent him some links. You can always try tomato or DD-WRT as well, might have better luck. ( I have no idea about ppoe or anything, I am but a simple user)

If you want to go back to stock, you need to flash the stock CFE first, then flash the stock firmware. Not really sure, as nobody wants to go back to stock :)

But I would suggest trying Tomato or DD-WRT before going back to stock.
 

m3digi

Serious Server
Member
Sounds like you need to confirm you flashed the CFE correctly. If so, do as apvmtan suggests and get into the recovery webserver, flash a fresh firmware of your choice. After flash (like the guide says) do an NVRAM reset. Appears like you already came in sideways and maybe already had DD-WRT flashed without the bootloader.....? If you followed the guide (mine), then you shouldn't have a CFE issue. That only comes from flashing DD-WRT on stock bootloader.
I followed the guide to the letter. I wasn't aware of the MAC address issue until after the flash. As I stated, I tried to correct it using the method I described above, which has resulted in the present issue with my router.

I'm having no luck getting into the recovery web server to hopefully correct the problem. I do want to return to stock so that I can restart the process.
 

cybrnook

Addicted to LI
Member
if you have (and are sure) a revised copy of the CFE uploaded and installed with your correct MAC address, then all you need to do is an NVRAM reset. OR flash your new firmware and then do a hard nvram reset.

No need to make your situation worse by trying to undo what has been done, especially if you are not sure what point you are really at.

If your not getting the recovery webserver to come up, and you are noticing that your DD-WRT builds are flipping between version on reboots. It sounds like you never flashed the CFE correctly...... You might want to start there. The flipping between builds is a Linksys CFE thing that has 2 x partitions for recovery. If you successfully flashed the modified CFE, then you should no longer have the 2nd partition to fail back on. Also, if you try and flash a new version of DD-WRT THROUGH DD-WRT webgui, and it fails, then you are still on stock CFE. Only option of flashing DD-WRT versions on stock CFE is through command line as the people in the DD-WRT forums will tell you (that dont want a modified CFE).

That's the best info I can give you. I don't own any of this :) just trying to help the community, so maybe some smarter members than I can help you further.
 

Boullie

Serious Server
Member
First post! Yay! :D
So I followed the guide and after a few bumps in the road, it's all running smoothly.


Here are my findings:
@cybrnook
I followed your guide to the letter and have to say, all is explained thoroughly and it went sort of smoothless.

A few remarks however:
1) Perhaps add an example of how the mac-addresses should look?
As you wrote it, it appears af if you have to write
Code:
"0:macaddr=et0macaddr+1"
instead of
"0:macaddr=AA:BB:CC:DD:EE:01"
(when MAC is AA:BB:CC:DD:EE:00)
2) As @Jeroen Houben and @floydo pointed out, the upload takes a lot longer than 15 seconds.
I used firefox and the upload took me about 3 minutes.
3) The command "mtd write –f /tmp/root/new-cfe.bin /dev/mtd0" failed all the time for me.
I received the same messages as described in @thenmens post.
What worked for me though, was to run the command as follows
Code:
mtd write –f new-cfe.bin /dev/mtd0
I double checked and the files were stored under /tmp/root/ so why the command failed was a bit strange to me.

One question though (perhaps @XVortex can clear this up):
IF I were to choose to go back to DD-WRT or switch to Tomato.
How do I return to the bootloader to flash the firmware?
Is it by doing the "press wps button on power on" or "keep pressing the red reset button"?
The guide is a bit confusing regarding this (as it says the 30-30-30 procedure is replaced by the wps trick, which to me appears to reset to default and not return to the bootloader).
Can DD-WRT be flashed from CFE? (as it uses the .bin extension and not .trx, which makes me think it's a different type/container of file which could cause a flash failure)
Does this "return to bootloader" actually ERASE the internal memory? Thus removing whatever files are stored there? (as to make sure whatever issues were caused by previous flashes do not return after loading already existing files/folders)
 

cybrnook

Addicted to LI
Member
Added your notes to the guide on notes 1, 2.

note 3 is a mixed bag, basically whatever works for users :) I have see 3 different syntax's up to now, so who knows.....

For flashing to DD-WRT, I think flashing from command line should work for you. No, you don't want to do 30-30-30 anymore, just hold the WPS button while booting to reset NVRAM (benefit of custom CFE).

so, upload your firmware to XVortex OS, and execute steps for mtd write commands:
How can force Flash fw using Telnet or SSH ?

mtd-write -i /path/to/file.trx -d linux && reboot

I "think" this should work.

Then do a NVRAM reset after flashing.
 
Last edited:

m3digi

Serious Server
Member
I resolved the issue from the dd-wrt forum. I used the commands provided:

"I use the below at the startup script and telnet to get the nvram down.
for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done
nvram commit

On telnet to flash the firmware
Code:
mtd write dd-wrt.v24-K3_AC_ARM_STD.bin linux

5. Wait...
6. Restore factory defaults using erase nvram command or reset button

Code:
erase nvram
reboot
I was able to upload the Brain Slayer initial build, as well as a revised CFE file. Everything is back in working order.
 

cybrnook

Addicted to LI
Member
I resolved the issue from the dd-wrt forum. I used the commands provided:



I was able to upload the Brain Slayer initial build, as well as a revised CFE file. Everything is back in working order.
Thanks for responding back with the fix for you. This may help others in the future.
 

Idmpcthis

Serious Server
Member
Sounds like you need to confirm you flashed the CFE correctly. If so, do as apvmtan suggests and get into the recovery webserver, flash a fresh firmware of your choice. After flash (like the guide says) do an NVRAM reset. Appears like you already came in sideways and maybe already had DD-WRT flashed without the bootloader.....? If you followed the guide (mine), then you shouldn't have a CFE issue. That only comes from flashing DD-WRT on stock bootloader.



Someone a few posts up talked about ppoe and I sent him some links. You can always try tomato or DD-WRT as well, might have better luck. ( I have no idea about ppoe or anything, I am but a simple user)

If you want to go back to stock, you need to flash the stock CFE first, then flash the stock firmware. Not really sure, as nobody wants to go back to stock :)

But I would suggest trying Tomato or DD-WRT before going back to stock.
Hmmm... I'm trying to revert back to DD-WRT but I'm probably doing something wrong. When I select the firmware file (linksys-ea6900-webflash.bin) via the web interface of Vortex's asuswrt, it says it can' flash the firmware because it's probably corrupted or something (I assume it's because it's a different firmware and is possibly failing some initial check). If I try to upload the firmware from CFE mini webserver, after a while I get a timeout and when I reset the router, I'm back at XVortex's asuswrt.

Is there any specific way to be able to flash the DD-WRT from XVortex's AsusWRT?
 

cybrnook

Addicted to LI
Member
I guess you skipped reading all the conversation from today.

Read 4 posts up 133 and 134 ;-) and even the post after that. They all would I think answer this question.
 

Idmpcthis

Serious Server
Member
I guess you skipped reading all the conversation from today.

Read 4 posts up 133 and 134 ;-) and even the post after that. They all would I think answer this question.
Thanks for the tip!

I managed to write back my stock CFE (by using the same command that was used to write the custom CFE but specifying the backed up stock CFE), and also downloaded a .img file which is the original firmware from linksys' website and wrote it with the mfd write command that you pointed me too, 5 posts up.

After that, I rebooted my router and then reset it. But now the quick setup says the router hasn't been properly configured, asking me to reset it (no matter how many times I reset it), and if I try to skip it, and I type in the password to get past the login page, it tries to load the configuration page, but never finishes loading. Now I'm stuck here with not a lot of options.

My EA6900 also came with a external DSL modem, and the router is connected to the modem. Anyone know if it's possible to directly access the modem? Maybe there's some kind of configuration I need to do on it for PPPoE to work on my router if I ever manage to get it back to DD-WRT...
 

don_ernesto

Serious Server
Member
thank you very much for this great tutorial.

In my case i just had to do
mtd -f write /tmp/root/new-cfe.bin /dev/mtd0

instead of the syntax used in the main post

Also, my first 3 attempts using firmware 380.57_2 failed at the moment of uploading the firmware from the XVT -CFE miniWeb Server. Then i repeated the whole process but with 378.54_2 and worked fine. after that, i upgraded to 380.57_2 using the web interface and everything seems to be working fine. Probably this was something circumstantial, but in the case it fails for you with the newest firmware, try the older one and then upgrade
 

Top