This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
failsafe_mode_recovery [2018/02/12 11:44] ispyisail [Failsafe recovery via telnet] |
failsafe_mode_recovery [2019/04/28 09:55] (current) ispyisail [Factory Reset] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | So your router has become unresponsive and you have heard the horror stories of ' | + | ====== Failsafe Mode, Factory Reset, and Recovery Mode ====== |
- | Alternatively you might follow the closely related [[http:// | + | ===== Gargoyle (Basic) ===== |
+ | ==== Factory Reset ==== | ||
- | ===== Failsafe recovery via ssh ===== | + | With the Gargoyle router fully powered up (boot sequence finished) hold the router " |
- | This procedure assumes that: | + | //Note: The button hold time is officially between 3 and 90 seconds// |
- | - you had a good Gargoyle install on the router | + | |
- | - you messed up your settings | + | |
- | - you can no longer get to the Gargoyle Web interface | + | |
- | NOTE: Unplug | + | //Note: Not enabled for all router |
- | Open a terminal and: | ||
- | - type //ssh root@192.168.1.1// | ||
- | - provide your password | ||
- | - at the Gargoyle prompt type //firstboot -y// | ||
- | - then //reboot -f// | ||
- | |||
- | The router which should now come up in its default Gargoyle configuration and you will be able to [[getting_started|get started]] again. | ||
- | ===== Failsafe recovery via telnet | + | ===== Gargoyle/ |
+ | [[https:// | ||
+ | ==== Failsafe Mode ==== | ||
- | This procedure assumes that: | + | * Failsafe Mode is useful if you have lost control of your device, and it has become inaccessible, |
- | - you had a good Gargoyle install on the router | + | |
- | - you messed up your settings | + | |
- | | + | |
- | - you cannot get to the Gargoyle ssh interface | + | |
- | - you cannot get a ping response from your router | + | |
- | NOTE: Unplug all external drives from the router or they will be erased by the firstboot process. | + | ==== Factory Reset ==== |
- | Firmware recovery changed with 1.10.x | + | * Factory Reset erases all your packages and settings, returning the router to its initial state after installing OpenWrt. ([[https:// |
- | | + | |
- | - Use “firstboot -y” instead of “firstboot” | + | |
+ | ==== Recovery Mode ==== | ||
- | Procedure for 1.10.x and above | + | * Recovery Mode allows you to install new firmware on a router that has become corrupted. ([[https:// |
- | To recover: | ||
- | - Install [[http:// | ||
- | - Configure your computer with static IP 192.168.1.2 | ||
- | - Connect your computer to a LAN port on the router. | ||
- | - Start Wireshark and monitor the LAN connection. | ||
- | - Powerup your router, when wireshark shows the first packet from 192.168.1.1 immediately press and hold the reset button on the back of the router for three seconds. | ||
- | - Router power LED should be flashing quickly. (Failsafe mode) | ||
- | - SSH via putty to " | ||
- | - at the Gargoyle prompt type '' | ||
- | - __wait__ until the command prompt returns | ||
- | - power cycle the router. | ||
- | The router which should now come up in its default Gargoyle configuration and you will be able to [[getting_started|get started]] again. | ||
- | Procedure for any firmware below 1.10.x | ||
- | To recover: | ||
- | - Install [[http:// | ||
- | - Configure your computer with static IP 192.168.1.2 | ||
- | - Connect your computer to a LAN port on the router. | ||
- | - Start Wireshark and monitor the LAN connection. | ||
- | - Powerup your router, when wireshark shows the first packet from 192.168.1.1 immediately press and hold the reset button on the back of the router for three seconds. | ||
- | - Router power LED should be flashing quickly. (Failsafe mode) | ||
- | - From a command prompt on your computer " | ||
- | - at the Gargoyle prompt type '' | ||
- | - __wait__ until the command prompt returns | ||
- | - power cycle the router. | ||
- | The router which should now come up in its default Gargoyle configuration and you will be able to [[getting_started|get started]] again. | ||
- | ===== TFTP a new firmware image to your router ======== | ||
- | If you router' | ||
- | |||
- | Here is an example | ||
- | D:\My Documents\Downloads> | ||
- | Pinging 192.168.1.1 with 32 bytes of data: | ||
- | Reply from 192.168.1.1: | ||
- | Reply from 192.168.1.1: | ||
- | Ping statistics for 192.168.1.1: | ||
- | Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), | ||
- | Approximate round trip times in milli-seconds: | ||
- | Minimum = 0ms, Maximum = 1ms, Average = 0ms | ||
- | |||
- | D:\My Documents\Downloads> | ||
- | Transfer successful: 3346464 bytes in 6 seconds, 557744 bytes/ | ||
- | |||
- | If you get this | ||
- | D:\My Documents\Downloads> | ||
- | Error on server : code pattern incorrect | ||
- | |||
- | It means your bootloader does not understand the format of your image file. Make sure you are using the correct one for your router and make sure you reboot before trying again. | ||
- | |||
- | |||
- | ===== JTAG recovery method ======== | ||
- | If you cannot get either of the above to work for you then the next approach I use is the JTAG cable method. | ||
- | http:// | ||
- | http:// |