Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
docs:user-guide:vendor_specific_rescue [2018/02/20 20:48] – ↷ Links adapted because of a move operation bobafetthotmaildocs:guide-user:troubleshooting:vendor_specific_rescue [2024/09/03 09:38] – [Rescue firmware partition] dohseven
Line 1: Line 1:
 ====== Rescue from failed firmware upgrade ====== ====== Rescue from failed firmware upgrade ======
-Some device vendors provide built-in rescue functions in their device's flash ROM boot partition that remain there, even after a LEDE firmware upgradeso a LEDE upgrade will not overwrite this rescue function.+<WRAP info> 
 +If you can't reach the OpenWrt interface after installing packageschanging the password or the network configuration, try using [[docs:guide-user:troubleshooting:failsafe_and_factory_reset|failsafe mode and factory reset]] first. 
 +</WRAP>
  
-This rescue functions can be used to recover a failed flash update (no matter if the failed flash was vendor firmware or LEDE) or recover from an otherwise dead device, as long as the device hardware and the rescue function is still intact. These rescue partitions do consume a tiny piece of the flash, but renders a device mostly unbrickable.+Some device vendors provide built-in rescue functions in their device's flash ROM boot partition that remain there, even after a OpenWrt firmware upgrade, so a OpenWrt upgrade will not overwrite this rescue function. 
 + 
 +These rescue functions can be used to recover a failed flash update (no matter if the failed flash was vendor firmware or OpenWrt) or recover from an otherwise dead device, as long as the device hardware and the rescue function is still intact. These rescue partitions do consume a tiny piece of the flash, but renders a device mostly unbrickable.
  
 Unfortunately such rescue functions are not available from all vendors, sometimes not for all models from a vendor and the actual rescue process is mostly vendor specific. Unfortunately such rescue functions are not available from all vendors, sometimes not for all models from a vendor and the actual rescue process is mostly vendor specific.
Line 8: Line 12:
  
 ===== Check first: Device-specific firmware recovery procedures ===== ===== Check first: Device-specific firmware recovery procedures =====
-Check the "device page" of both LEDE and OpenWrt for your device (look for a link in the last columns of each project's table of hardware). The device page may describe a rescue method for your specific device. +Check the "device page" of your device (look for a link in the last columns of the Table of Hardware). The device page may describe a rescue method for your specific device. 
-  * https://lede-project.org/toh/start +  * [[toh:start|Table of Hardware]]
-  * https://wiki.openwrt.org/toh/start+
  
 Some of the methods may require creating a custom RS232-serial-cable or soldering-skills, while most newer devices require just a certain software trick to remote flash the device from a PC client. Some of the methods may require creating a custom RS232-serial-cable or soldering-skills, while most newer devices require just a certain software trick to remote flash the device from a PC client.
  
 ===== Manufacturer-generic firmware recovery procedures ===== ===== Manufacturer-generic firmware recovery procedures =====
- 
 Many devices of the following manufacturers support a recovery procedures as listed here: Many devices of the following manufacturers support a recovery procedures as listed here:
  
Line 23: Line 25:
 | Linksys       | Several older devices support a remote TFTP recovery procedure.\\  Several newer devices have [[#dual_firmware_partition|2 independent firmware partitions]]. | - [[https://www.linksys.com/us/support-article?articleNum=137928|Official Linksys TFTP recovery documentation]]\\ - For Linksys dual firmware, [[#dual_firmware_partition|see below]] | | Linksys       | Several older devices support a remote TFTP recovery procedure.\\  Several newer devices have [[#dual_firmware_partition|2 independent firmware partitions]]. | - [[https://www.linksys.com/us/support-article?articleNum=137928|Official Linksys TFTP recovery documentation]]\\ - For Linksys dual firmware, [[#dual_firmware_partition|see below]] |
 | Mikrotik      | TFTP-like rescure procedure with a manufacturer utility called 'netinstall' installed on a client PC. | [[https://wiki.mikrotik.com/wiki/Manual:Netinstall|Official Microtik recovery documentation]] | | Mikrotik      | TFTP-like rescure procedure with a manufacturer utility called 'netinstall' installed on a client PC. | [[https://wiki.mikrotik.com/wiki/Manual:Netinstall|Official Microtik recovery documentation]] |
-| Netgear       | TFTP on a PC client can be used to rescue the firmware. | [[https://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP|Official Netgear TFTP recovery documentation]] | +| Netgear       | TFTP on a PC client can be used to rescue the firmware. | [[https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client|Official Netgear TFTP recovery documentation]] 
-| TP-Link       | TFTP on a PC client can be used to rescue the firmware.\\ Several newer devices provide a [[#rescue_firmware_partition|rescue partition]]. | [[http://forum.tp-link.com/showthread.php?81462-How-to-recovery-the-router-when-you-bricked-it|TP-Link forum TFTP recovery documentation]] |+|:::| nmrpflash | https://github.com/jclehner/nmrpflash 
 +| TP-Link       | TFTP on a PC client can be used to rescue the firmware.\\ Several newer devices provide a [[#rescue_firmware_partition|rescue partition]]. | [[https://community.tp-link.com/en/home/forum/topic/81462?page=1|TP-Link forum TFTP recovery documentation]] | 
 +| ::: | Webpage firmware recovery\\ See link for models which support this method. | [[https://www.tp-link.com/us/faq-1482.html]] |
 | Ubiquiti (UBNT) | TFTP on a PC client can be used to rescue the firmware. | [[https://help.ubnt.com/hc/en-us/search?utf8=%E2%9C%93&query=firmware+recovery&commit=Search|Official UBNT site: site search for 'firmware recovery']] | | Ubiquiti (UBNT) | TFTP on a PC client can be used to rescue the firmware. | [[https://help.ubnt.com/hc/en-us/search?utf8=%E2%9C%93&query=firmware+recovery&commit=Search|Official UBNT site: site search for 'firmware recovery']] |
 | Xiaomi        | Several devices with USB port support a [[#rescue_usb_stick|rescue USB stick]] method. | | | Xiaomi        | Several devices with USB port support a [[#rescue_usb_stick|rescue USB stick]] method. | |
Line 32: Line 36:
 Examples: the different Raspberry PI's, devices of PC Engines). Examples: the different Raspberry PI's, devices of PC Engines).
  
-LEDE devices that use a drive-installed image.gz or sdcard.img.gz are not an issue to recover. The LEDE OS is not applied to flash ROM, but installed on a removable drive, e.g. an SD-card. For recovery, mount the removable drive in a working PC and reapply the LEDE image to the removable drive according to the device-specific instructions.+OpenWrt devices that use a drive-installed image.gz or sdcard.img.gz are not an issue to recover. The OpenWrt OS is not applied to flash ROM, but installed on a removable drive, e.g. an SD-card. For recovery, mount the removable drive in a working PC and reapply the OpenWrt image to the removable drive according to the device-specific instructions.
  
 ===== TFTP recovery mode ===== ===== TFTP recovery mode =====
- +In several of these recovery procedures you will need a working TFTP server on your PC, see how to install and configure it in [[docs:guide-user:troubleshooting:tftpserver|Set up a TFTP Server]] article.
-In several of these recovery procedures you will need a working TFTP server on your PC, see how to install and configure it in [[docs:user-guide:troubleshooting:tftpserver|Set up a TFTP Server]] article.+
  
 ===== Rescue USB stick ===== ===== Rescue USB stick =====
-Supported by some Xiaomi devices +Supported by some Xiaomi devices process for [[http://en.miui.com/thread-157895-1-1.html|Xiaomi Mi]]:
- +
-process for [[http://en.miui.com/thread-157895-1-1.html|Xiaomi Mi]]:+
   - Download firmware and store as ''miwifi.bin'' on an USB flash drive (must be FAT or FAT32)   - Download firmware and store as ''miwifi.bin'' on an USB flash drive (must be FAT or FAT32)
   - Plug USB flash drive into device USB port   - Plug USB flash drive into device USB port
Line 52: Line 53:
 Supported by several devices at least of the following vendors: D-Link, TP-Link, ZBTLink Supported by several devices at least of the following vendors: D-Link, TP-Link, ZBTLink
  
-This function is based on extra code in the boot partition in the flash ROM and it is still available on the device, even after the device has been flashed to LEDE. No further tools are needed, to trigger this rescue function.+This function is based on extra code in the boot partition in the flash ROM and it is still available on the device, even after the device has been flashed to OpenWrt. No further tools are needed, to trigger this rescue function.
  
 Procedure, to boot into rescue partition: Procedure, to boot into rescue partition:
Line 60: Line 61:
   - You can release the reset button after a few seconds.   - You can release the reset button after a few seconds.
   - The device will take ~15-20 seconds to boot a mini-web server, that provides only a single function: it can upload a firmware file and has a button to trigger the flash process. The web-server will usually be available under either (if in doubt, try both)   - The device will take ~15-20 seconds to boot a mini-web server, that provides only a single function: it can upload a firmware file and has a button to trigger the flash process. The web-server will usually be available under either (if in doubt, try both)
-    - http://192.168.0.1 (TP-Link and newer D-Link devices)+    - http://192.168.0.1 (TP-Link and newer D-Link devices) or http://192.168.0.254 (newer TP-Link devices)
     - http://192.168.1.1 (ZBT-Link and older D-Link devices)     - http://192.168.1.1 (ZBT-Link and older D-Link devices)
   - Note: You need to set your PC client to a fixed IP address beforehand, as DHCP is not supported in this rescue mode. So depending on your device, so you need to set the PC client's to a matching IP address, either:   - Note: You need to set your PC client to a fixed IP address beforehand, as DHCP is not supported in this rescue mode. So depending on your device, so you need to set the PC client's to a matching IP address, either:
Line 68: Line 69:
 Notes: Notes:
   * The rescue function provides no Internet access, WiFi or DHCP.   * The rescue function provides no Internet access, WiFi or DHCP.
-  * LEDE firmware can be flashed directly using this rescue function when using a LEDE ...**factory.bin** firmware file. There is no need to first flash official D-Link firmware. +  * OpenWrt firmware can be flashed directly using this rescue function when using a OpenWrt ...**factory.bin** firmware file. There is no need to first flash official D-Link firmware. 
-  * Official D-Link documentation of this procedure is rare, a [[ftp://ftp.dlink.de/dir/dir-600/documentation/DIR-600_revb12_howto_de_FirmwareRecovery.pdf|german D-Link documentation for the DIR-600]] exists (with the same procedure also applying for other D-Link devices, if the device supports recovery). Inofficial documentation: [[https://wiki.openwrt.org/toh/d-link/dir-505#web_interface|OpenWrt Wiki for DIR-505]] and  [[http://forums.dlink.com/index.php?topic=44909.msg162511#msg162511|D-Link Forum]].+  * Official D-Link documentation of this procedure is rare, a [[ftp://ftp.dlink.de/dir/dir-600/documentation/DIR-600_revb12_howto_de_FirmwareRecovery.pdf|german D-Link documentation for the DIR-600]] exists (with the same procedure also applying for other D-Link devices, if the device supports recovery). Inofficial documentation: [[toh:d-link:dir-505#web_interface|OpenWrt Wiki for DIR-505]] and  [[http://forums.dlink.com/index.php?topic=44909.msg162511#msg162511|D-Link Forum]].
   * Inofficial notes of [[https://fccid.io/2AH9TW826/Users-Manual/User-Manual-2994820|ZBTLink recovery]],   * Inofficial notes of [[https://fccid.io/2AH9TW826/Users-Manual/User-Manual-2994820|ZBTLink recovery]],
   * Official [[http://www.tp-link.de/faq-1482.html|TP-Link rescue partition notes]]   * Official [[http://www.tp-link.de/faq-1482.html|TP-Link rescue partition notes]]
Line 76: Line 77:
 Supported by newer Linksys devices Supported by newer Linksys devices
  
-Most newer devices (mostly those with decent amount of flash ROM) have 2 independent firmware partitions. A usage strategy could be, to install LEDE only into one of the 2 partitions and leave the vendor firmware in the other partition. No further tools are required to toggle between the two partitions.+Most newer devices (mostly those with decent amount of flash ROM) have 2 independent firmware partitions. A usage strategy could be, to install OpenWrt only into one of the 2 partitions and leave the vendor firmware in the other partition. No further tools are required to toggle between the two partitions.
  
 Procedure, to manually toggle between the two firmware partitions:  Procedure, to manually toggle between the two firmware partitions: 
  • Last modified: 2024/10/09 11:28
  • by danitool