Instantly share code, notes, and snippets.

What would you like to do?
How to flash RT-N66U with Shibby's TomatoUSB firmware


Download Asus RT-N66U Flash utility

Download Shibby RT-N66U firmware

K26RT-N is appropriate for the RT-N66U. Go ahead and pick the latest release by date. Inside that directory you want the to pick the Asus RT-N66u 64k. The 64k in the name means that 64k of flash memory will be used as NVRAM. Inside that directory the .trx file with AIO in the name has all possible features compiled in and enabled. If this is your first time installing, AIO is a good jumping off point.

Preparing for firmware restoration to TomatoUSB (Shibby)

The steps are simple, you will need to:

  1. Connect the ASUS RT-N66U to your network
  2. Start the firmware restoration process (using firmware restoration utility in the ASUS Utility package) so that it is searching for router
  3. Put the ASUS RT-N66U into firmware restoration mode and start the firmware restoration process

Before you proceed, pull out the power cable to your RT-N66U and have a pen ready to press the reset button (between the USB ports and WAN port)

Flash the TomatoUSB firmware onto the RT-N66U.

  1. Launch the firmware restoration utility (this is one of the tools in the Utility you installed earlier)
  2. In the firmware restoration utility, browse for the TomatoUSB firmware you have downloaded earlier
  3. Start the firmware flashing and a prompt should appear stating that it is an incompatible firmware. Proceed to the next step.

Putting the RT-N66U into emergency firmware restore mode

  1. Press and hold on to the reset button
  2. While holding down the reset button, plug in the power cable so that the RT-N66U turns on. Note: Keep holding the reset button until the power led starts to flash (on and off). When power led starts flashing, release the reset button and proceed.
  3. On the firmware restoration utility, agree to the prompt saying that it is a incompatible firmware. The utility should be scanning for device. Proceed to the next step
  4. Wait until the flashing is complete
  5. The router will automatically power cycle when it is complete

Finally, clearing the NVRAM before you use TomatoUSB

It is always a good practice to clear out the previous settings (in NVRAM) whenever you flash to different firmwares. This is true for PC BIOSs as well. In this case, it is required to flush out the NVRAM from values that may have been previously stored by the stock firmware that are no longer valid for TomatoUSB.

You can either flush the NVRAM either through key presses or through web admin.

Clearing NVRAM via key presses

  1. Power off the RT-N66U
  2. Press and hold down the WPS button
  3. While holding the WPS button, plug in the power cable to turn RT-N66U on
  4. Keep holding the WPS button for 30 seconds before releasing The router should reboot
  5. Congratulations. The NVRAM has been cleared.

Clearing NVRAM via web admin

The TomatoUSB administration web should be at If it is not, do a “ipconfig” or “ifconfig” and navigate to the gateway address with your web browser. If you are not able to get an IP address from DHCP, you might want to set your computer’s IP address to

When prompted for a login, the default is:

  • User: root
  • Pass: admin

Once you are in, follow the next step to clear out the previous settings

  1. Navigate to Administration -> Configuration
  2. Under Restore Default Configuration, select “Erase all data in NVRAM memory (thorough)
  3. Click “OK”
  4. Wait for the router to be ready

This comment has been minimized.

nickelfault commented Jun 13, 2013

Awesome, I plan on picking up this router tomorrow. Thank you for the clear and concise instructions!


This comment has been minimized.

graysky2 commented Jul 5, 2013

Nice guide, thanks for taking the time to post it. Is there any tested alternative to using a Windows/only util like the Asus Firmware restoration you show?


This comment has been minimized.

stephech commented Dec 12, 2013

Any reason I shouldn't be able to go back to the original FW?


This comment has been minimized.

larcher commented Dec 27, 2013

A couple hints that might save someone else some trouble, since this post is currently near the top when googling "rt-n66u shibby tomato":

  • the firmware restoration tool, for whatever reason, did not work in Windows 8 -- always got the "router is not in rescue mode" error (maybe a firewall thing? but I did attempt to tweak the firewall settings .. ). But it worked fine on the first try from a Windows 7 box.
  • don't change your PC's IP address (from DHCP to static) while it's uploading the firmware because you didn't notice the upload was working this time. But if you do, and the router gets stuck in a rescue mode/power cycle loop, try holding down the reset button while plugging it in (again) to get it out of this loop.

I'd also be interested in a non-Windows method for flashing. One possibility (though I didn't try it myself): other guides mention using tftp to upload the firmware image.


This comment has been minimized.

sfarestam commented Jan 6, 2014

@larcher - As soon as the router enters recovery mode it offers a minimal recovery mode web ui which allows for uploading any firmware (tomato shibby works fine). This means that the ASUS firmware recovery tool is not required. However, this website is only active for 10-15 seconds, so one needs to be very fast in selecting the appropriate firmware file and press upload.

It should be easy to reverse engineer the recovery web ui and create a one line curl script that uploads the firmware. This in combination with a script that checks when the emergency website becomes active could make the whole firmware upload process very smooth.


This comment has been minimized.

bmtphoenix commented Feb 27, 2014

This guide worked for me, with the exception of having to wait nearly half an hour for the router to come back up. It would go through the update, then sit there with no power light for at least 20-30 mins, then come up and was fine. So if the power light goes off, and the firmware recovery tool says "System recovery in progress..." for a while, then says "Failed to connect to wireless router. Check if the router's power LED is blinking, which denotes that the router is in rescue mode," don't fret. Just let it sit there with the power light off for about half an hour, and if yours is like mine was, it will come up just fine. Once the power light is on, you're good to reset the NVRAM then set up. Also, mine did not throw the error saying that the firmware was incompatible. Not sure why, but everything worked out fine.


This comment has been minimized.

royhaddad commented Mar 6, 2014

I had exactly the same experience as bmtphoenix just now, except that I kept trying to flash because I thought it hadn't worked, but really I just had to wait long enough for it to come back on.


This comment has been minimized.

voglster commented Apr 2, 2014

also have the same issue with the long reboot time.. currently at about 5 minutes and crossing my fingers.

another few things to note:
I had to update the router firmware to latest from ASUS before i could even get the restore utility to work.
Since I had another ASUS router on my network I hard-lined and set my computer to a static IP address of The router in firmware upload mode defaults to,


This comment has been minimized.

NelsonMinar commented Apr 25, 2014

This guide is clear and simple and well-loved by Google. Thanks!

You don't have to use ASUS' proprietary firmware flasher; any tftp client will work if you're comfortable with manually configuring your IP address. This blog post does a good job explaining the steps on a Mac. Should be the same on Linux.

These instructions work fine on an ASUS RT-AC66U too. The only change is to get the right firmware, the N firmware won't work on the AC. I used tomato-RT-AC66U_RT-AC6x--117-AIO-64K.trx.


This comment has been minimized.

0x4d4e commented Apr 29, 2014

The newest builds for the N66U are in the K26RT-AC directory:

I flashed tomato-RT-N66U_RT-AC6x--117-AIO-64K.trx today, works perfectly!
The ASUS utility also reported the "Failed to connect ...." error, but after several minutes I was able to connect via telnet. Shortly afterwards the web-ui was also available.


This comment has been minimized.

LilMinmax commented May 22, 2014

so, this will still work with newly purchased N66U units, it sounds like? No revisions to look out for etc?


This comment has been minimized.

DickSmith commented Jun 20, 2014

I've performed these steps on both an RT-N66U and an RT-AC66U. Other than needing the correct version of both the Shibby Tomato firmware and Asus Flash Utility, the steps worked perfectly for both.

The only main difference is the long reboot time (about 5-10 minutes if I remember) on the N66U that has been previously mentioned; the AC66U was almost instant.


This comment has been minimized.

baileyweiler commented Jun 21, 2014

What worked for me was to flash the DD-WRT firmware from the console administration web console, then flash the shibby firmware from the DD-WRT admin web console.


This comment has been minimized.

Globespy commented Jul 15, 2014

If I'm already using Shibby Tomato and simply want to update to the latest version (121 I believe), I can do this through the Tomato update GUI and then clear NVRAM?
No need to use the Asus utility if already running Tomato?


This comment has been minimized.

docbill commented Jul 31, 2014

The instructions here simply did not work. They were however close enough, so eventually I got there.

The first problem is the instructions start off to unplug your router. But if your router is not connected to your computer the restoration program will simply give an invalid IP address error, and not allow you to even select the firmware file. The second problem is the instructions to wait for the flashing LED simply don't make sense. As near as I can tell if you are holding on he power, the LED starts off slowly blinking. If you "wait" for it to blink faster or such, you'll simply wait forever. Third problem is if you don't start the upload soon enough, the router will leave recovery mode, and your upload will fail part way through. The last problem is at the end of the process the firmware recovery program will give you an error about not being able to connect and ask if your router is in recovery mode. It turns out this error is perfectly normal, you have to simply know to give the router more time... Oh, also the firmware recover program never gave me an "error" about incompatible firmware...

So here are the instructions that worked for me.

  1. Connect the router to the computer.
  2. Turn on/plug in the router.
  3. Wait for your computer to connect.
  4. Start the firmware recovery program.
  5. Select the firmware.
  6. Unplug the power from the router.
  7. Holding down on the reset button, plug in the power to the router.
  8. While still holding the button, press the upload button in the recovery program.
  9. As soon as the recovery program starts counting out % upload, release the reset button.
  10. Wait.
  11. After a long time look at the error message and scratch your head.
  12. Wait a good 5 minutes more. You'll probably see the lights flash indicating the router is rebooting.
  13. Connect to in your web browser.
  14. Use whichever procedure you like to reset the nvram.
  15. Configure the router and have fun.

This comment has been minimized.

razvanyork commented Aug 21, 2014

Docbill's answer is right. After failing a couple of times I reached the same conclusion. Thank you!


This comment has been minimized.

irneh commented Sep 12, 2014

Issues I had after flashing an AC66U:

  • Had to physically power cycle the router for Tomato to detect the 5GHz antenna
  • Builds 120 and 121 do not allow you to change wireless channels (fails silently and channels are pinned to 1 & 36). Had to revert to build 119 to get channel changing working correctly

This comment has been minimized.

mllrjb commented Dec 9, 2014

You can do this without the Asus Firmware utility - just use the web client. That requires you assign a manual IP with DHCP (e.g. in order to connect to At least, that's what I had to do on OS X.


This comment has been minimized.

auswalk commented Mar 29, 2015

Just flashed latest Mar 25th v128. Using the Win 7 recovery flash util, it successfully uploaded, but once done, the power light stayed on and after a bit I power cycled the router, only to find the power light blinking and in recovery mode. So I happened to go to and it prompted me to upload firmware there. So I selected the tomato firmware there, after the upload was successful, the power light went off, came back on 25 minutes later and all is well.

I also had my ip address manually set at


This comment has been minimized.

Atanoman commented Mar 31, 2015

Flashed last night. Followed Docbill's instructions using the flash recovery tool on Windows 7. Hung up at about 65%, then the router entered rescue mode. Rebooted but was unable to get an IP. Ran the recovery tool again and that time it worked. Still unable to get an IP but could log in wirelessly. Cleared NVRAM and all is good now. Hope this helps.


This comment has been minimized.

AaronCompNetSys commented Apr 21, 2015

I had similar experiences, here was my process for fixing.
NOTE: if the router is in a constant reboot loop (it actually boots the wifi interface and then reboots), then flashing it will may not make a difference. I was not able to bring one back to life, no factory or aftermarket firmware resolved my bootloop issue. It was an older unit with B1 stamped on it. My newer one does not have B1 stamped on it.

As others have mentioned it takes FOREVER to write the system using the stock recovery. You must be quick about starting it too. I tried the 30MB and 20MB system flash and it took over 30 minutes before I gave up on it. I found using the webui to be better than the utility that you install, you just have to be quick about it.


  1. Set your IP to GW:
  2. Point your web browser to in advance.
  3. Use the power switch to power the unit up in recovery, by holding the button next to it as you power it up, it usually only takes a second or two and the power light blinks slowly (on 2 sec, off 2 sec).
  4. Manically refresh your browser and once you get the recovery webui, quickly put in the smallest compatible firmware you have. I used Shibby's 7MB VPN version.
  5. After submit the power light should go out and stay out. It will stay out until the system is flashed. The 7MB one took about 15-20 minutes. If the light does not go out, I think you might have been too slow, I was never able to get it to work unless the light went out.
  6. Once flash is complete, the power light will come back one and nothing else will happen. You can now reboot manually and Tomato should come up after the standard couple auto reboots.
  7. From Tomato webui, flash whatever system you actually want, the 20MB one took a minute or two to flash and reboot.
  8. Wipe NVRAM from Tomato webui.

This comment has been minimized.

still-dreaming-1 commented May 4, 2015

This says to use the K26RT-N firmware, but it does not explain why. According to the router list (, you can you that version or K26RT-AC. Based on information from the download page and the names you see inside the download links, it appears the N version uses version 5 of some SDK, while the AC version uses version 6 of this SDK. What is the difference between these? Which one should I use?


This comment has been minimized.

auswalk commented May 18, 2015

I gave up on tomato and went back to the factory firmware. The DLNA server on tomato is slow and inferior to the factory firmware, as is the networking to a USB drive connected to the router. I get 9MB/s with the factory firmware and less than 1MB/s with tomato.


This comment has been minimized.

ethomas997 commented Mar 27, 2016

The thing that tripped me up for a while was that after the firmware is uploaded, the router takes a long time (30+ minutes) to process the update and reboot. If you cut the power during that time the update fails and the router ends up showing only the "ASUSTeK - CFE miniWeb Server" page. During that processing the router shows no signs of life (other than the LAN led blinking if connected). Finally it reboots, the other lights come on, and it's good to go.


This comment has been minimized.

ghost commented Apr 18, 2016

I have noticed an error in linkage on the newest build "build5x-136-EN-MultiWAN".

If you try to navigate to the VLAN page it's a broken link. It directs to /advanced-vlan-r1.asp, however if I remove the -r1 from the link it appears to load the page properly.

Hopefully this can be fixed in the future as it's more of an annoyance than anything else.

Other than that, so far so good on everything else.


This comment has been minimized.

siemsen commented Jul 13, 2016

I followed AaronCompSysNet's instructions (thank you) and hit a speed bump. Once the router had rebooted, supposedly with Tomato running, I couldn't reach from the computer connected directly to the router's LAN1 port over Ethernet. Purely by chance, I was doing this at work. Our local wireless administrator came by asking if I was responsible for the "rogue" wireless router that was offering an SSID of "Tomato24". Cool! I connected to the router over wireless. I was still connected from another laptop (with its wireless disabled) over an Ethernet cable to the LAN1 port on the router. I couldn't ping from that laptop. This despite rebooting the router. Using the wireless connection, I used the web interface to clear NVRAM. After the router rebooted, and the LAN1 connection started working.

BTW I installed I think that's Tomato 1.37, right? The web interface said it's Tomato 1.28. Now to take it home and have some fun...


This comment has been minimized.

cpryor6 commented Jul 19, 2016

I have one of the older units marked B1 and ran into the reboot loop after not getting the webui up fast enough and having the upload fail partway through. I was able to recover it by clearing NVRAM which gave me the default ASUS login page as if it was brand new out of the box. I was quicker with the webui next time and got the 9MB VPN version installed in like 15 minutes. Thanks to the OP and contributors for this writeup.


This comment has been minimized.

robertvorthman commented Jul 20, 2016

For Mac OSX users, ASUS has an app in the Mac App Store called "ASUS Firmware Restoration". I just used it to flash my RT-N66U with Tomato on my MacBook and it was easy.


This comment has been minimized.

netrbrunet commented Jul 28, 2016

Thank you to all' this was great. And extra credit to docbill for the simplified version.

Note, my new N66U's disk did not come with the recovery utility, and I had to download it from ASUS site. At first, I was trying to upload tomato via the default firmware's updater but this is not the same as the specialized firmware recovery utility.
However, I should note that it never gave me an error (maybe a newer version of the updater?). It uploaded the file (a short progress bar), and then started a subsequent "system recovery in progress" progress bar which took about 5-10 minutes to complete.


This comment has been minimized.

morgant commented Sep 9, 2016

I just did this from a Mac and found the process to be very unreliable. I ultimately got it to work with a combination of @docbill's & @AaronCompNetSys's instructions, plus the note I found in Googling regarding watching for whether the antenna lights were active or not, that really helped).

  1. Erase the NVRAM (because of failed flashing attempts, it was trashed anyway; you might move this step to the end or skip entirely if you're wiping the NVRAM via Tomato's web interface)
    1. Turn off router
    2. Hold down the WPS button
    3. Press the power button to turn the router back on (the power light will flash quickly)
    4. Continue holding down the WPS button for a full 30 seconds, then release
    5. The router will reboot
  2. Flash the firmware using ASUS Mini Web:
    1. Set your Mac/PC to static IP in range (I used (IP), (subnet mask), and (gateway))
    2. Turn off router
    3. Unplug router
    4. Hold down the reset button
    5. Plug the router back in
      6 Press the power button (the power light should blink slowly—2s on, 2s off)
    6. Load in the browser on your Mac/PC
    7. Quickly select the firmware you want to use (MIPSR2-138-Mega-VPN didn’t work for me, but MIPSR2-137-Mega-VPN did)
    8. Click ‘Upload’
    9. AS SOON as the “Received file” message loads in your browser, LET GO OF THE RESET BUTTON!
    10. The power light on the router should go off (if it doesn’t, it didn’t work… maybe not fast enough selecting the firmware, maybe a poorly timed release of the reset button… go back to the beginning and try again.)
    11. Wait for 5+ minutes for the firmware to process/install (the power & antenna lights will remain off for this entire time, though the ethernet light for the port you’re plugged into should stay on)
    12. Once successfully installed, the router should reboot (power light will come back on, then the two antenna lights.. if this doesn’t happen, esp. the antenna lights, something didn’t work… I’d suggest trying a slightly older firmware version)
    13. Give it another minute or so and then load in the browser of you Mac/PC
    14. Log in with the default username/password of “root”/“admin”
    15. If the NVRAM wasn’t successfully cleared, do so now (either manually as described above or through your new firmware).

This comment has been minimized.

deviantintegral commented Oct 13, 2016

I was having real trouble getting larger images to flash at all, either through the recovery app, the web UI, or TFTP. I ended up searching for the smallest image I could find, and used tomato-K26-1.28.RT-N5x-MIPSR2-120-MiniVPN.trx. From there, I could flash a recent all-in-one image.


This comment has been minimized.

dalehamel commented Mar 1, 2017

Process that worked for me on a Mac:

  • Install the asus device discovery and firmware flash utils from app store
  • Reset NVRAM (not sure if necessary, but why not) using steps above
  • Put it into emergency firmware restore mode (otherwise the upload craps out at about 25%) using steps above
  • Upload a small tomato firmware, I just used because @deviantintegral recommended it. This is because the finicky part of this process seems to be going from Asus -> tomato.
  • Reset it manually (toggle switch on and off)
  • Wait for a new DHCP address (about 30 seconds)
  • Installed a fully featured, recent all-in-one image, checking the "clear NVRAM on reboot" setting so that it automatically clears the NVRAM again. This takes a few minutes to upload and reboot, and will reboot a couple of times, but the Web UI is very informative on the progress.
  • Confirm the new firmware version
  • Enjoy my new, recent, tomato firmware.

This comment has been minimized.

tomaszkoperski commented Mar 30, 2017

Double check the version of your router. I've spent some time following the instruction here without success. Finally I've double checked and it seems ASUS released a "B1" hardware version of RT-AC66U, which is not compatible with all previous generation firmwares for RT-AC66U (A1).


This comment has been minimized.

cumanzor commented Apr 19, 2017

@tomaszkoperski: Do you know if there's a tomato-shibby (or AdvancedTomato) version that is compatible with the RT-AC66U_B1 hardware revision?


This comment has been minimized.

Trefilov22 commented Apr 21, 2017

Is there any newer Tomato than from 2015? The file I am looking at doesn't have the same naming schematic as the one to poster says...


This comment has been minimized.

Trefilov22 commented Apr 21, 2017

And why couldn't you use the firmware update option from inside the Router? I only ask this because my laptop doesn't have an ethernet port to connect directly to the router, I pretty much have to do everything thru WiFi...


This comment has been minimized.

kikiSK commented May 14, 2017

I ask for help.
How to connect Asus VDSL AC68U / main router / and Asus RT N66U Tomato 1.28 shibby I think Lan to WAN port


This comment has been minimized.

rackflot commented Sep 24, 2017

I have the RT-66R router, will this firmware work on this one too?


This comment has been minimized.

quangv commented Oct 26, 2017

anybody have a mirror of this? is down for me

edit: yeup, it's back


This comment has been minimized.

R4U5CH1337 commented Oct 29, 2017

Looking for the same as @quangv. is still down.
Especially for versions before 138 MultiWAN for my RT-N66U. Thanks a lot!

Edit: it's back online.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment