15 minute upgrade video, step by step in real time.
Disclaimer
When doing things on the firmware level there is always a possibility that something might go wrong and your router becomes bricked.
March 2022 update
AdvancedTomato (based on Tomato by Shibby) firmware hasn’t been updated in years, so I would recommend using FreshTomato (last updated 24 Dec 2021) which is still being updated, and has been running rock solid on my EA6700 for the last year. The biggest drawback is the UI isn’t quite as clean and modern as AT was.
You should also be aware of a 32K NVRAM limit, which causes a lot of issues with this router (read the comments), thus I would recommend removing this limit by following the steps here (backup mirror of steps + mirror of files), though removing the limit also means you can never go back to Linksys stock firmware, only other third party firmware like AT, FreshTomato or DD-WRT etc
I’d recommend reading through all the steps before starting to get an idea of what will need to be done, then follow the steps carefully.
The old instructions to install AdvancedTomato are below.
The long guide (for beginners)
admin)e.g. (Current Version: 1.1.40.166281) the bold part is the build version.
Once the device is back up follow these steps;
admin).If it doesn’t, wait another 5 mins, if still nothing then abort, reset it (unplug power from router, push the reset pin, plug power back in, hold reset pin for 45 seconds, then let go, wait 5 mins and the stock firmware should be back), then start again from step 1.
If you end up back on the stock Linksys firmware, start again and redo all the steps and check what IPs are assigned on your computer while the upgrades are happening (see below).
admin/admin.This is very important, if you skip erasing the NVRAM the new firmware won’t hold.
for line in $(nvram show | grep =$); do var=${line%*=}; nvram unset $var;
done
nvram commit
The quick guide (for advanced users)
for line in $(nvram show | grep =$); do var=${line%*=}; nvram unset $var;
done
nvram commit
Troubleshooting
Also check out chanz’s comment as he talks about it, as well as other comments.
Old firmware mirror
A mirror of the 166281 firmware has been hosted on my server in case Linksys takes down the link one day.
30/30/30 reset?
According to jago75, the 30/30/30 reset has no effect on ARM-based routers like the EA6700.
Why the double firmware install?
The steps for installing the Tomato firmware onto the EA6700 router are a little different than that of normal routers. It has 2 locations where it stores firmware, and if you try to install AdvancedTomato as per normal, it will just reboot back to the stock Linksys firmware.
This is why we first “upgrade” to the stock firmware (into the first location), then again with AdvancedTomato, into the second location, which is what it runs from by default. (at least this is my understanding)
Disbale all LED lights (except the Linksys logo)
In the Administration > Scripts page, put the following into the Init tab, save, and reboot.
sleep 10
et robowr 0x0 0x18 0x0
et robowr 0x0 0x1a 0x0
Some acronyms
AT = AdvancedTomato
AIO = All In One (has everything)
VPN = A cut-down version of the firmware with specific VPN support
OFW = Official Firmware, e.g. what originally come with the device
CFW = Custom Firmware, e.g. what we’re putting on the router (Tomato, DD-WRT, OpenWrt etc)
NIC = Network Interface Controller (the things where you plug the network cables into)
Disclaimer
I am by no means an expert in flashing firmware, only done it a few times, first a Netgear router (DD-WRT), then a Linksys (DD-WRT), and now this Linksys router (AdvancedTomato), just thought I’d share this as I couldn’t find anything online on this specific router and Tomato based firmware, and didn’t have much success with my initial attempts.
Alternative name
Cisco Linksys Smart Wi-Fi Router AC 1750 HD Video Pro
Feel free to leave any feedback in the comments.
]]>Installing Windows 10 using the Boot Camp Assistant app, but each time the app gets to the partitioning step it errors out saying “Your disk could not be partitioned”, suggesting “run Disk Utility to check and fix the error”.
“An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error.”
You’ve tried running Disk Utility but the error still persists. Here is what fixed it for me, there are some other possible solutions at the end of the article.
Possible solution
If you are using Time Machine to back up your Mac, then clearing out all your local snapshots could fix this.
Make sure to do a Time Machine backup in case something bad happens here or with the Windows install.
1, In System Preferences, untick “Back Up Automatically” in the Time Machine preference
2, Run this command in the Terminal app;
tmutil thinlocalsnapshots / 9999999999999999
basically, it will remove all the local backups on your boot drive, it won’t delete any of your files on your Time Machine backup drive.
3, Once the command finishes, start the Boot Camp Assistant app and try again, it should work now.
4, When you have Windows installed remember to re-enable Time Machine on the Mac side.
Not sure if this is related or not, but my boot drive at the time was formatted as APFS and I was on macOS Mojave 10.14.2
A little bit about the tmutil command:
tmutil thinlocalsnapshots <mount_point> [purge_amount] [urgency]
The <mount_point> is which drive you’d like cleaned.
The [purgeamount] is the amount of space you want to recover. (optional)
The [urgency] part is a number between 1 – 4, on how quickly you want the space recovered. (optional)
Other possible solutions:
/sbin/fsck -fy) during boot, see instructions here or here.Feel free to leave comments if you get stuck, or find other solutions to this error.
Source: Apple discussions
]]>/var/lib/docker, which will be an issue if you have /var on its own (usually small) partition.
After using Docker for a while you may start to run out of space on the /var partition, at which point you’ll need to either add more space to that partition or relocate it to somewhere with more space.
Here are the steps to change the directory even after you’ve created Docker containers etc.
Note, you don’t need to edit docker.service or init.d files, as it will read the change from the .json file mentioned below.
/etc/docker/daemon.json (if it doesn’t exist, create it){
"data-root": "/new/path/to/docker-data"
}
sudo systemctl stop docker
ps aux | grep -i docker | grep -v grep
screen if you have a large amount of data or unreliable ssh connection.
sudo rsync -axPS /var/lib/docker/ /new/path/to/docker-data
Options explanation, check out the man page for more info
-a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
-x, --one-file-system don't cross filesystem boundaries
-P show progress during transfer
-S, --sparse handle sparse files efficiently
sudo systemctl start docker
docker info | grep 'Docker Root Dir'
docker ps
Leave both copies on the server for a few days to make sure no issues arise, then feel free to delete it.
sudo rm -r /var/lib/docker
Official docs https://docs.docker.com/engine/admin/systemd/
Docker GitHub issue item https://github.com/docker/docker/issues/3127
Blog post inspired by linuxconfig
Tested and working on Debian Stretch (9.3) with Docker Docker version 17.12.0-ce
]]>Linksys E2500 N600 Dual-Band Wireless Router
For more info on this router look at wikidevi or the manufacturer’s website.
For those of you that don’t know, AdvancedTomato is a fork from the Tomato by Shibby project, but with a much improved GUI frontend, and much easier to use.
I bought this one as it’s still a current model being sold which has AdvancedTomato support and is very cheap for what you get.
Disclaimer: When doing things on the firmware level there is always a possibility that something might go wrong and your router becomes bricked.
Instructions
Enjoy!
Inspired by Lindqvist blog post, which is about installing the Tomato by Shibby version on an older version of the E2500.
]]>