What's new

pingable, but unrecoverable firmware?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

qwell

New Around Here
Hi, I have an RT-N66U (B1) which I tried to put a Shibby version of tomato onto, using the CFE web interface. After the upgrade, the router never came back up. It now appears to be stuck in rescue mode. I've cleared nvram using both the CFE GUI and the WPS button. I can ping the device (according to the peacock thread, this should means good news), but I don't appear to be able to successfully recover the firmware. After the final attempt last night, I let it sit overnight, and now this morning it has still not rebooted itself.

Last night, I was only ever getting TTL=100. As soon as a file gets uploaded to the device, it stops responding to pings.

I've tried installing the following firmwares using ASUS Rescue Utility, CFE GUI, and tftp, to no avail:
tomato-K26USB-1.28.RT-N5x-MIPSR2-112-AIO-64K.trx
ASUS RT-N66U Firmware Version 3.0.0.4.374.168
ASUS RT-N66U Firmware Version 3.0.0.4.372.1393
ASUS RT-N66U B1 Firmware Version 3.0.0.4.276

The sticker on the bottom says it came with 3.0.0.4.274 (which is not available for download on support.asus.com).

What other things can I try?
 
Last edited:
Hi, I have an RT-N66U (B1) which I tried to put a Shibby version of tomato onto, using the CFE web interface. After the upgrade, the router never came back up. It now appears to be stuck in rescue mode. I've cleared nvram using both the CFE GUI and the WPS button. I can ping the device (according to the peacock thread, this should means good news), but I don't appear to be able to successfully recover the firmware. After the final attempt last night, I let it sit overnight, and now this morning it has still not rebooted itself.

Last night, I was only ever getting TTL=100. As soon as a file gets uploaded to the device, it stops responding to pings.

I've tried installing the following firmwares using ASUS Rescue Utility, CFE GUI, and tftp, to no avail:
tomato-K26USB-1.28.RT-N5x-MIPSR2-112-AIO-64K.trx
ASUS RT-N66U Firmware Version 3.0.0.4.374.168
ASUS RT-N66U Firmware Version 3.0.0.4.372.1393
ASUS RT-N66U B1 Firmware Version 3.0.0.4.276

The sticker on the bottom says it came with 3.0.0.4.274 (which is not available for download on support.asus.com).

What other things can I try?

You could also try flashing using the Firmware Recovery tool from Asus's website in case something is preventing your browser from properly uploading the FW.

A recovery flash can take up to 15-20 minutes to complete, so even if the recovery tool gives you a "Router not in recovery mode" 10 mins after you flashed with it, give it a few more minutes.
 
You could also try flashing using the Firmware Recovery tool from Asus's website in case something is preventing your browser from properly uploading the FW.

Yes, I referred to that as "ASUS Rescue Utility" in my post. I tried using that with each of the firmware versions I listed, using both the version downloaded from support.asus.com and the version on the CD.
 
Yes, I referred to that as "ASUS Rescue Utility" in my post. I tried using that with each of the firmware versions I listed, using both the version downloaded from support.asus.com and the version on the CD.

Make sure you unplug every other devices (including your modem) from the router, keeping only the connection between the router and the computer being used for recovery.

Also try the following procedure:

1) Turn router off
2) Press reset button, turn router on
3) Wait 5 secs, then release reset and immediately press WPS
4) Wait 5 secs, release WPS, and see if you are in recovery.
5) If you are, proceed with reflashing.

The idea is to clear the nvram and immediately enter recovery mode without allowing the router to try to boot the FW (in which case it might recorrupt your settings).
 
Hi,
In that case, if I were you, I'd TFTP f/w file and done with it.
 
Make sure you unplug every other devices (including your modem) from the router, keeping only the connection between the router and the computer being used for recovery.
Nothing was ever plugged into the WAN port, and I only ever had my laptop on the LAN port.

Also try the following procedure:

1) Turn router off
2) Press reset button, turn router on
3) Wait 5 secs, then release reset and immediately press WPS
4) Wait 5 secs, release WPS, and see if you are in recovery.
5) If you are, proceed with reflashing.

The idea is to clear the nvram and immediately enter recovery mode without allowing the router to try to boot the FW (in which case it might recorrupt your settings).
I had cleared nvram many times, by booting up with WPS held, and then after a few seconds, switching to rescue by holding reset instead.

This is the first I'd seen this order suggested. It appears to have done the trick. The last stock firmware version I had flashed came up, and all was well. I've since flashed tomato successfully, without issue.

For people who see this later:

After you finish flashing, wait. When you think it's time to reboot, wait some more. Then continue to wait. It took nearly 45 minutes for the flash process to complete, and for the newer stock firmware to come up.
 
Confirmation and Thanks!

Nothing was ever plugged into the WAN port, and I only ever had my laptop on the LAN port.


I had cleared nvram many times, by booting up with WPS held, and then after a few seconds, switching to rescue by holding reset instead.

This is the first I'd seen this order suggested. It appears to have done the trick. The last stock firmware version I had flashed came up, and all was well. I've since flashed tomato successfully, without issue.

For people who see this later:

After you finish flashing, wait. When you think it's time to reboot, wait some more. Then continue to wait. It took nearly 45 minutes for the flash process to complete, and for the newer stock firmware to come up.

Thank you to RMerlin and qwell. I tried everything including reading the manual which definitely does not mention holding the WPS button for 5 seconds as the last step before flashing. Holding the WPS button made everything work and I will confirm that from the time the firmware recovery software (not browser) finished writing the firmware it was 42:22 before the power light came back on (updated to FW_RT_N66U_3004374979.trx). It took all my will power to wait so I just kept rereading the last line of qwell's post.

Just to be clear, this router was brand new, during initial setup it told me there was a firmware update available (it came with original fw 3.0.0.4.274) so I let it do its thing and download the firmware it found and flash itself. It failed all by itself and left me with a brick minutes out of the box. I'm honestly not sure if the WPS button did anything (it certainly didn't hurt) but waiting 45 min absolutely did because I would have never waited that long.:)
 
Thank you RMerlin. I was digging through forums for about an hour until I found this. Your button sequence worked perfect for me. I was just about ready to RMA this thing.

Cheers
 
these routers are more prone to a unsuccessful flash but they are near impossible to actually brick to the point of requiring a jtag flash the ASUS recovery CFE is a nice bit of work I wish more vendors used something like it
 
Followed all these steps on my RT-N66W and nothing. Anything else I can try before I throw it in the trash? It still accepts a ping so that is good news.
 
Followed all these steps on my RT-N66W and nothing. Anything else I can try before I throw it in the trash? It still accepts a ping so that is good news.

Is the returned ping TTL 64 or 100? If it's 100, it means you are properly in recovery mode - you can then either use the Firmware Recovery tool, or set your computer with a static IP within the 192.168.1.0/24 network, and try to use the CFE mini web interface at 192.168.1.1.
 
Is the returned ping TTL 64 or 100? If it's 100, it means you are properly in recovery mode - you can then either use the Firmware Recovery tool, or set your computer with a static IP within the 192.168.1.0/24 network, and try to use the CFE mini web interface at 192.168.1.1.

I got it into recovery mode and used the CFE mini web interface. The firmware was accepted. I went to bed and slept for a few hours and it was good to go. So it may have took maybe an hour or 2 to complete the process. Thanks for all of the points in this thread. I learned my lesson now. LOL!
 
I got it into recovery mode and used the CFE mini web interface. The firmware was accepted. I went to bed and slept for a few hours and it was good to go. So it may have took maybe an hour or 2 to complete the process. Thanks for all of the points in this thread. I learned my lesson now. LOL!

I got to CFE mini web interface, uploaded stock ASUS firmware and am at stop where I have on browser 'Upload Completed...Please wait a few minutes.'

Been waiting quite some time now. Power light on router was solid, but now slow flash again. Do I continue to wait or there is a 'Continue' link, do I click on that?

FYI, after the N66u went down, I attached another router so I have network capability. Have asus router attached to a laptop with no internet connection. Merely laptop to router with cat5 cable.
 
Confirmation and Thanks!



Thank you to RMerlin and qwell. I tried everything including reading the manual which definitely does not mention holding the WPS button for 5 seconds as the last step before flashing. Holding the WPS button made everything work and I will confirm that from the time the firmware recovery software (not browser) finished writing the firmware it was 42:22 before the power light came back on (updated to FW_RT_N66U_3004374979.trx). It took all my will power to wait so I just kept rereading the last line of qwell's post.

Just to be clear, this router was brand new, during initial setup it told me there was a firmware update available (it came with original fw 3.0.0.4.274) so I let it do its thing and download the firmware it found and flash itself. It failed all by itself and left me with a brick minutes out of the box. I'm honestly not sure if the WPS button did anything (it certainly didn't hurt) but waiting 45 min absolutely did because I would have never waited that long.:)


Exactly! Thanks for that.

I feel it is important to note:
I have B1 Revision:
1 - The power light remains off during the firmware upgrade (after it is uploaded).
2 - Ping will stop working after the upload of the firmware is complete.
3 - You will need to wait a long time after the Firmware Tool has given you the error. The power light will remain off after the error is displayed and the LAN port will still be active. - Be patient, the router will reset after it is completed and the power light and wifi light should be on in addition to the LAN port. Also took me about 40 min.
4. After the long wait the router reset and my pings came back, the power light was on along with the LAN port and Wifi light. I then went to the web page and I was at the entry page for the stock ASUS firmware.

Thanks for the help,
-Pish
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top