Unable to Upload Tomato Firmware to Linksys Ea6700 Router

To show nvram usage, login to ssh and do nvram show. In Tomato the nvram usage is shown in the spider web admin interface too.

i. Try to revert back to previous firmware “FW_EA6700_1.1.40.166281_prod.img”. Yous can find that in
Troubleshooting>Diagnostics.

2. Flash the firmware upgrade of the same five.166281 from
here.

3. Flash the firmware
AdvancedTomato
and erase nvram.

4. If you desire DD-WRT, you lot tin can so flash
DD-WRT
from here and erase nvram by hard reset.

Remember to articulate nvram either past hard reset or past settings each time yous flash a new firmware

Promise this helps someone, equally for any reason I could non flash tomato directly from stock.

At present can safely mess around with ISP provided EA6350v2 without fear of loosing internet admission.

Well ok, if it were
totally
normal, these fixes wouldn’t be needed. The point is that this hardware tin be fabricated to perform usually running DD-WRT.

Showtime is the
set up for the dead USB port, followed by a
normal CFE
(no port reversals and, of course, no 32k-nvram bug). The third mail service covers
differences in the CFEs
bachelor for this unit.

USB Port Fix


The Internet is filled with wrong information on this. The port does car-disconnect after kicking, but
comes back to life when reinitialized. This is done automagically with the startup script beneath.

===EDIT/UPDATE===

Frequent disconnects were seen in the latest two builds (checked) not seen in before ones (v/17). iMagic’s posts on this page
and next
refer to this strangeness. The partitions show as remaining mounted, but contents are inaccessible. The port tin can exist reinitialized manually with the (original, no gpio) commands below, but will before long revert to this pseudo-connected country.

And then gave some other endeavor finding the root cause of the initial disconnect and, while failing miserably nevertheless again (for the *last time* I might add!), found a cure for the pseudo-disconnection: the
gpio command
added to the code below. This should work for
all
builds.

Now, let no one say this is an elegant prepare. It is a complete hack that should probably have no issue. Equally Kong mentions
here, “nvram var for buttons are never used by u.s.a..” The reset push itself does nothing later its function is moved to the wps button with the new CFE. But sending in an
enable
does work; partitions remain mounted and attainable. It’s just unknown how or why. (And enabling the usb port with gpio9 had no issue.)

BTW, should analyze that
sleep 5
is at that place to allow the kernel to connect, then disconnect the port. (The sleep changes to 60 seconds when added to the startup script to allow kicking time.) If the port is reinitialized before disconnection, so information technology will remain asunder.

===[/EDIT/UPDATE]===

If using ane of the patched CFEs (of XVortex origin), then:

1. Assuming an ext4 filesystem on the flash drive to be mounted, with the first partitioning on /opt and the second on /mmc — for other filesystems and mountpoints, modify args as desired. (/mnt had some odd beliefs in earlier releases then I avoid it.)
2. In the spider web GUI (Services | USB), be sure both Core USB Support and USB Storage Support are enabled, and Automatic Drive Mount is disabled. If changes are fabricated, be sure to hit ‘Apply Settings’.
3. Plug the flash drive into the USB port that dies, the usb3 port which is labeled ‘USB 1’ and located to the outside, with blue tongue.
4. Reboot.
5. SSH or telnet into the router and paste the following in a terminal:
   

   Code:

   for d in mbcache jbd2 crc16 ext4; do insmod $d; done sleep 5 gpio enable 11 IFS=” ” xc=” echo 0000:00:0b.0 > /sys/bus/pci/drivers/xhci_hcd/unbind echo 0000:00:0b.0 > /sys/coach/pci/drivers/xhci_hcd/bind mount -t ext4 -o rw,noatime,nodiratime,errors=remount-ro,barrier=1,information=ordered /dev/sda1 /opt mount -t ext4 -o rw,noatime,nodiratime,errors=remount-ro,bulwark=1,data=ordered /dev/sda2 /mmc ” for x in $90; practice eval $x; sleep 2; done

   
   
   

6. Encounter that access to mounted partitions on the flash drive now works normally, Ex. # ls -50 /opt.
7. Tweak the
   mountain options
   as preferred. The above are for
   longest life of a flash bulldoze; whatever suggestions for comeback are welcome.
8. If desired (optional), do away with the loop by pasting the xc= commands directly with a sleep 2 after each. (The higher up lawmaking is more than compact.)
9. When satisfied that the port reinitializes and partitions mount ordinarily, change the ‘sleep v’ to ‘sleep 60’ and add the code to the startup script (Administration | Commands in the GUI); paste and Save Startup. (Or just paste to begin with and reboot!)
   

• There is a slight delay in mounting on reboot, simply since these devices run for months due west/o restarting, that’s no trouble.
• For reference, I’m currently running Kong builds.
• Anyone employ this method and have trouble, please post.
• Apologies it took over a year to become time to write these up (work done autumn 2016). With open source, patience wins.
  

_________________
My erstwhile cocky
(phonetics-R-fun)

Last edited by u2n on Wednesday Jan 10, 2018 17:forty; edited 4 times in total

See fastened archive (must be logged in) containing:

• A re-create of
  XVortex’southward CFE Edit tool
  from
  his mail, cfe_edit.exe
  
• Text file with data ready to paste (into the XVortex (Fifteen) CFE tool), cfe_u2n_12-17.txt
  
• Text file with a line-by-line list of the original, XV,
  justmoi
  and u2n (this) versions, cfe_comparison.csv*
  
• CFE binary made using my edits, cfe_u2n_12-17.bin

*This is a tab-delimited csv that can be pasted into a spreadsheet or viewed in a text editor, which makes it piece of cake to compare versions. Data for the original CFE is taken from Malachi’s mail service
here. Meet next mail service for discussion.

The boot partition (which is flashed by a CFE binary file) contains the MAC addresses and secret_code, which should match the device’s characterization. It is a uncomplicated task to look at the label and edit the four fields to match.
Do not flash the included binary!
Information technology is for reference/comparison just. Fifty-fifty hex editing is not recommended. There are reports of trouble later doing this, mayhap due to a checksum mismatch.

To generate the hardware-specific CFE epitome:

1. Run Windows (sorry, no Linux version of CFE Edit tool is available)
   
2. Extract the above files
   
3. Open up cfe_u2n_12-17.txt file, select all and re-create**
   
4. Click to run cfe_edit.exe
   
5. Click Advanced tab and see page is blank
   
6. Paste, so check to see that text exactly matches text file contents
   
7. Edit 4 fields as follows:***
   • et0macaddr= <base mac address from characterization on router>
     
   • 0:macaddr= <et0macaddr+2h>
     
   • i:macaddr= <et0macaddr+4h>
     
   • secret_code= <secret code from characterization>
8. Click ‘Relieve as’ and requite an easy proper name, 6700cfe.bin
   

**Be certain to use a text editor that doesn’t auto-add together formatting characters. Geany is recommended.

***Some guides increment the 0: and 1: MACs by 1, rather than by the 2 used here. Since VLAN2 (the WAN) is automatically given a MAC of base_MAC+1 on bootup, I prefer this (2-increase) scheme. (Plus it works same as original.)

Flash the CFE binary file just created, 6700cfe.bin, to the router, which must be running the
early version of DD-WRT
(<-click to download). Guides:
Past cybrnook, and
By egc. Employ all, including this one, at user’s own chance (as usual
). With tip ii below, this tin exist every bit easy equally XV states in steps 3-5 in
this mail service.

Tips

1. To go into the mini spider web server, if preferred, prepare static IP address.
2. Rather than fiddle with putty or whatever — even scp, which I like — it is easiest to just telnet in [ telnet 192.168.1.one ] and issue # mount /tmp /mnt, then go to Services | NAS in the GUI and Add Share /mnt (proper noun ‘mnt’), ticking the Public checkbox and striking ‘Utilize Settings’. Navigate to mnt from PC’s file browser (via Network) and re-create the file(s) to exist flashed or saved. Quick and piece of cake.
3. Take care, especially with the CFE. An inadvertent error can render the device in need of series recovery.
4. Don’t freak if it goes into a boot loop. Reset past pinhole if before CFE flash, or past WPS push afterwards.
5. Allow at to the lowest degree five minutes subsequently any reset before doing anything, even if the unit appears stable. Information technology’due south not.
6. Side note: My router rests vertically, which increases air flow and cuts down on the core temperatures. Information technology normally runs ~60C CPU and ~45C wlans.
7. After some absence, I’ve returned to Optware,
   Optware-ng
   (new generation). It’s bang-up to be able to quickly install and employ different packages, equally it was with MIPS hardware for then many years. (My executables go in /opt/usr/bin, path added)
   • wget -O –
     http://ipkg.nslu2-linux.org/optware-ng/bootstrap/buildroot-armeabi-ng-bootstrap.sh
     | sh
     
   • consign PATH=$PATH:/opt/bin:/opt/sbin:/opt/usr/bin
     
   • /opt/bin/ipkg update
     
   • /opt/bin/ipkg list

Lacking documentation, I used the 15 tool to make and flash several CFEs to get this right. Or at least, best with the available time.

Using this CFE and the usb3 port fix in previous post, my router has been functioning like any other — no more buggy behavior or backwards connections. Thanks to everyone mentioned and linked hither, BrainSlayer and Kong always, and the community.

cfe_u2n_12-17.zip
Clarification:		Download
Filename:	cfe_u2n_12-17.zip
Filesize:	687.36 KB
Downloaded:	329 Time(southward)

_________________
My old self
(phonetics-R-fun)

Final edited past u2n on Thu Jan 04, 2018 0:21; edited iii times in total

Notes on Comparison of CFEs

1. The original contained two variables that none of the others had: sdram_ncdl=0 (correct after sdram_config=0x0147, which is common to all) and gpio8=wps_led (right later lan_netmask=255.255.255.0, as well common to all). Did not experiment with either of these, and neither was included.
2. The original clkfreq=800,533 was retained, though I didn’t run into any big difference using the EA6900’due south clkfreq=800,666. If not mistaken, I believe XVortex fifty-fifty overclocked to one thousand. This thing runs hot anyhow and so why button information technology when there’s no need? (Or is there always a “need for speed”?)
3. Using boardtype=0xF646 (rather than the EA6900’s boardtype=0xD646) and i:boardflagsj= (i=0 and i, j=blank and 2) seems to make all the deviation between losing the upper Air-conditioning speeds and not. Thanks to justmoi for figuring this out, besides that the CFE Edit tool could be used cross-device (no need for patches and rebuilds, every bit I thought earlier).
4. The port reversal (Ethernet WAN is part of LAN and port i becomes WAN) seen when the EA6900 CFE is flashed to the 6700 seems to be caused past a alter in convention between the ii models. The only variable I could discover potentially causing the trouble was ‘vlan2ports=iv 5u’ from the EA6900. Reverting to the original ‘vlan2ports=4 5’ apparently stock-still the problem.
5. Used the original’s wandevs=vlan2 and not the 6900’due south wandevs=et0, but couldn’t see that it made any departure either way.
6. Original boot wait_time=3 was changed to Fifteen’s wait_time=1. Just need an interval for rescue, if ever needed, so used 1.
7. By comparison, the original’s variable list is quite brusk so I’m guessing NVRAM is car-populated on boot with values stored permanently on chip, or in some uneditable location. Specifying the values explicitly apparently overrides that sequence. (More experimentation could confirm, simply I’k mostly done now!)
   

_________________
My old self
(phonetics-R-fun)

I will make a reference to your USB fix and volition see if this also applies to the EA6900

_________________
Routers:Netgear R7800, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000 (converted WRT320N), WRT54GS v1.

Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399

Install guide R7800/XR500:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614

Forum Guide Lines (of import read):
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087