Beruflich Dokumente
Kultur Dokumente
!!
Original: http://www.shadowandy.net/2012/03/asus-rt-n66u-tomatousb-firmware-flashing-guide.htm
(http://www.shadowandy.net/2012/03/asus-rt-n66u-tomatousb-firmware-flashing-guide.htm)
!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.
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)
https://gist.github.com/joshenders/3941269 Page 1 of 4
How to flash RT-N66U with Shibby's TomatoUSB firmware 3/25/14, 1:41 PM
You can either flush the NVRAM either through key presses or through web admin.
https://gist.github.com/joshenders/3941269 Page 2 of 4
How to flash RT-N66U with Shibby's TomatoUSB firmware 3/25/14, 1:41 PM
User: root
Pass: admin
Once you are in, follow the next step to clear out the previous settings
Awesome, I plan on picking up this router tomorrow. Thank you for the clear and concise instructions!
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?
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.
https://gist.github.com/joshenders/3941269 Page 3 of 4
How to flash RT-N66U with Shibby's TomatoUSB firmware 3/25/14, 1:41 PM
@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 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.
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.
https://gist.github.com/joshenders/3941269 Page 4 of 4