bugmenotplz
Occasional Visitor
Use PING to show when an Asus RT-N66U is finished updating
Hello All:
I was just passing by this website and wanted to add a few insights for anyone with a ASUS RT-N66U router who feels they "bricked" it and just get that "CFE WebServer" page.
First, definitely use the Firmware Restoration Utility available from the AsusTek website. Secondly, download the stock Asus RT-N66U firmware (or if that fails then download a small custom firmware like "Tomato by Shibby").
Now here's what I do to figure out when the firmware recovery has actually completed. Before you begin, open a Command window (or Terminal) and type this at the command prompt:
ping -t 192.168.1.1
...which will begin pinging the router again and again. This is your friend and it will show you how the router is responding throughout the entire process, including when the process completes.
Before starting the recovery, do a 30/30/30 reset. Then when you're ready, start the Firmware Restoration Utility, browse for the firmware file, and click the update button. Ensure that the router was detected and the firmware is being uploaded. If you did everything correctly, you should see a progress bar going across the screen v-e-r-y slowly. At this point, WALK AWAY. Seriously, go have lunch or walk the dog and come back in about an hour. For some reason there are Asus RT-N66U routers that take seemingly forever to do a firmware recovery, and the wait will make you crazy. When the progress bar finishes, if you should see an error claiming there was a problem then DON'T BELIEVE IT. Believe me, the firmware update takes a whole lot longer than that progress bar has time for. It's the ping window that will tell you when the router is responding again, so for now just go do something for an hour.
While the firmware recovery is in progress, the ping window will display messages like "Destination host unreachable" and "Timed out". This is normal. When the update finally completes, the window will look something like this:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
...over and over again. This indicates that the router is responding again. Go open a web browser to http://192.168.1.1 and see if you get the web interface. If you're prompted for a login, try using the default userid "admin" with password "admin. Now leave the route alone for 15 mins for it to calm down, do another 30/30/30 reset, and then after that leave it alone for another 15 mins.
If all goes well, you will now have three options you didn't have before:
1. Use the stock firmware (it's not so bad). Or...
2. Install the custom firmware you really want, in a version that is compatible with the Asus RT-N66U (with 64-bit CFE if that's what the router has). Or...
3. Return the router to the store and exchange it.
Be Blessed,
Yeshua is Messiah
Hello All:
I was just passing by this website and wanted to add a few insights for anyone with a ASUS RT-N66U router who feels they "bricked" it and just get that "CFE WebServer" page.
First, definitely use the Firmware Restoration Utility available from the AsusTek website. Secondly, download the stock Asus RT-N66U firmware (or if that fails then download a small custom firmware like "Tomato by Shibby").
Now here's what I do to figure out when the firmware recovery has actually completed. Before you begin, open a Command window (or Terminal) and type this at the command prompt:
ping -t 192.168.1.1
...which will begin pinging the router again and again. This is your friend and it will show you how the router is responding throughout the entire process, including when the process completes.
Before starting the recovery, do a 30/30/30 reset. Then when you're ready, start the Firmware Restoration Utility, browse for the firmware file, and click the update button. Ensure that the router was detected and the firmware is being uploaded. If you did everything correctly, you should see a progress bar going across the screen v-e-r-y slowly. At this point, WALK AWAY. Seriously, go have lunch or walk the dog and come back in about an hour. For some reason there are Asus RT-N66U routers that take seemingly forever to do a firmware recovery, and the wait will make you crazy. When the progress bar finishes, if you should see an error claiming there was a problem then DON'T BELIEVE IT. Believe me, the firmware update takes a whole lot longer than that progress bar has time for. It's the ping window that will tell you when the router is responding again, so for now just go do something for an hour.
While the firmware recovery is in progress, the ping window will display messages like "Destination host unreachable" and "Timed out". This is normal. When the update finally completes, the window will look something like this:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
...over and over again. This indicates that the router is responding again. Go open a web browser to http://192.168.1.1 and see if you get the web interface. If you're prompted for a login, try using the default userid "admin" with password "admin. Now leave the route alone for 15 mins for it to calm down, do another 30/30/30 reset, and then after that leave it alone for another 15 mins.
If all goes well, you will now have three options you didn't have before:
1. Use the stock firmware (it's not so bad). Or...
2. Install the custom firmware you really want, in a version that is compatible with the Asus RT-N66U (with 64-bit CFE if that's what the router has). Or...
3. Return the router to the store and exchange it.
Be Blessed,
Yeshua is Messiah
