Trouble Flashing Shibby from Asuswrt-Merlin on RT-AC66U

Discussion in 'Tomato Firmware' started by bhall7, Apr 3, 2014.

  1. bhall7

    bhall7 LI Guru Member


    I am currently running Asuswrt-Merlin ( and I'm trying to flash with Shibby's build (tomato-RT-AC66U_RT-AC6x--116-AIO-64K.trx) on my ASUS RT-AC66U.

    Unfortunately, every time I try to flash, I get the following error: "Firmware upgrade unsuccessfully. It may result from incorrect image or error transmission. Please check the version of firmware and try again."

    Any ideas on how to resolve this?


    Attached Files:

  2. tbjerret

    tbjerret Network Guru Member

    Can you use the restore mecanism - in restore mode?
  3. teh_g

    teh_g Networkin' Nut Member

    I believe you need to use the restoration tool to go between ASUS-WRT and Tomato
  4. bhall7

    bhall7 LI Guru Member

    I assigned my machine a static IP (, I put the RT-AC66U into rescue mode, and tried to load Shibby via the Firmware Recovery tool, but it says, "The wireless router is not in rescue mode".

    So, I flashed it with DD-WRT, then flashed it with Shibby (selecting the option to clear all settings). But, upon reboot, it would not respond at all. I can't get out to the WAN, can't ping it, nor can I access it via the web interface. What a nightmare! It didn't used to be this hard.
  5. bhall7

    bhall7 LI Guru Member

    I tried telnet-ing to my RT-AC66U, but there is no response.

    I tried putting it into rescue mode with the WPS button instead of the reset button, but it did not work. Any other suggestions? I fear I may have bricked it.
  6. bhall7

    bhall7 LI Guru Member

    Ugh! OK, I was finally able to flash my RT-AC66U successfully with Tomato (Shibby v 116). I wish I had just done this method from the start. Hopefully subsequent upgrades won't be as traumatic.

    "Put the router into recovery mode, set a static IP address on the computer then run in the shell:
    put [filename].trx"

    (Hat tip to commenter Simeon W. on post:

    I tried using the TFTP client on Windows 7, but I ended up having to use the TFTP client on my MacBook. Not sure why.
  7. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    Windows 7 doesn't doesn't let you immediately access devices connected over ethernet. There is enough of a delay that you will miss the window for a successful tftp flash. XP didn't have this problem/feature (all a matter of perspective).
  8. dc361

    dc361 Network Guru Member

    The problem is (likely) that windows 7 take a few moments to recover when the ethernet port comes up. One solution that I've found is to use an ethernet hub or switch between the router and the computer. I know it sounds more than a little redundant, but it works.
    Marcel Tunks likes this.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice