Any specific initial flush instructions for E3000: tftp, recovery mode, cisco web interface for firmware upgrade?
Cisco web interface, start with the smaller file in top of this thread then update to big if you need those functions.
The router will take a couple of minutes to rebuild nvram after a flash so just leave it alone and let it do what it has to do.. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Wed Jun 09, 2010 18:00 Post subject: Working well so far...
I went straight to the big from the stock. I reset the defaults and re configured. I've got better signal than the stock fw. I'll repost if anything crops up.
Posted: Wed Jun 09, 2010 18:03 Post subject: Do we need a cfe?
Do you all need a .cfe for the E3000, or are you all good? _________________ NETGEAR R9000 DD-WRT v3.0-r45192 std (12/29/20) (ROUTER)
NETGEAR ORBI Stock FW V2.7.2.102 (MESH)
WRT3200ACM (BS Build Usually) (BACKUP)
Hey guys. I am new here and have never used DD-WRT. I have a Linksys E3000 and I need DD-WRT, because the stock fw has problems getting multiple computers on the network to have an open NAT by opening certain ports for games. I have looked this up online and apparently multiple people experience this with the E3000 using computers and game consoles.
Someone said that using DD-WRT would very likely fix this by providing working port forwarding, plus many other more advanced features not available in the stock fw.
Anyway I have read through the stickies and there is a lot of information to process and I feel as though a good deal of it doesn't apply to me.
So my question is:
This release of DD-WRT for the E3000 is not yet official, correct? Can I just flash the big version straight up or do I need that smaller one first? Is there a version coming bigger than the big one? I heard they go up to 8mb. Would the flashing procedure be the same as detailed for official versions?
You should start by flashing the smaller build, and yes, that process is the same as doing a normal official upgrade. Once that is successful you can flash the larger mega build.
Do yourself a favor though- take a look at the peacock thread sticky, paying extra attention to the part about 30-30-30 resets.
You should start by flashing the smaller build, and yes, that process is the same as doing a normal official upgrade. Once that is successful you can flash the larger mega build.
Do yourself a favor though- take a look at the peacock thread sticky, paying extra attention to the part about 30-30-30 resets.
Welcome to DD-WRT!
Thank you! OK I just did the 30-30-30 reset and flashed the small build and it is working now (I first backed up my cfe file). I am very cautions, so I would like to confirm the procedure for flashing the mega build.
Do I have to perform the 30-30-30 reset again before I do it? Or since I already have the small build, is that not necessary?
Also if I do the 30-30-30 reset, should I then set up a username and password before flashing the mega build? If not, what username and password is the default for me to log in?
Joined: 19 Jan 2008 Posts: 36 Location: Montreal, Qc
Posted: Thu Jun 10, 2010 2:48 Post subject:
Working perfect on a WRT610Nv2 flashed to E3000.
How I did it:
I SCP'ed a edited E3000 CFE (with my MAC and serial) and the E3000 bin firmware to the TMP directory; and did this in telnet:
"cd /tmp"
"mtd unlock cfe"
"mtd write -f cfe_new.bin cfe"
But I had a problem with this line:
"write E3000.bin linux"
Something about bad TRX. I think at this moment the old CFE was still running and would not take the bin because of the header.
So before I rebooted, I went into the web gui and upgraded the firmware from there, selecting "reset default option", it worked since the web interface don't seem to care about the header.
After the router finished reseting, I did a 30-30-30, configured everything, did a backup of the CFE and compared it to the one I flashed, and now I'm happily running a "E3000" with 60k NVRAM
I SCP'ed a edited E3000 CFE (with my MAC and serial) and the E3000 bin firmware to the TMP directory; and did this in telnet:
"cd /tmp"
"mtd unlock cfe"
"mtd write -f cfe_new.bin cfe"
After the router finished reseting, I did a 30-30-30, configured everything, did a backup of the CFE and compared it to the one I flashed, and now I'm happily running a "E3000" with 60k NVRAM
You just opened up Pandora's box, there will be lots of bricked WRT610v2 for sale on ebay soon. _________________ Kernel panic: Aiee, killing interrupt handler!
Joined: 19 Jan 2008 Posts: 36 Location: Montreal, Qc
Posted: Thu Jun 10, 2010 4:40 Post subject:
People just have to be careful and do as I did; read as much as possible on the wiki & forums before trying something dangerous like that :)
In my case I knew I was risking bricking it; but I assumed full responsability for it
LOM wrote:
FrancoisC wrote:
Working perfect on a WRT610Nv2 flashed to E3000.
How I did it:
I SCP'ed a edited E3000 CFE (with my MAC and serial) and the E3000 bin firmware to the TMP directory; and did this in telnet:
"cd /tmp"
"mtd unlock cfe"
"mtd write -f cfe_new.bin cfe"
After the router finished reseting, I did a 30-30-30, configured everything, did a backup of the CFE and compared it to the one I flashed, and now I'm happily running a "E3000" with 60k NVRAM
You just opened up Pandora's box, there will be lots of bricked WRT610v2 for sale on ebay soon.