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
Next revisionBoth sides next revision
docs:guide-user:troubleshooting:vendor_specific_rescue [2019/09/02 10:54] – [Manufacturer-generic firmware recovery procedures] nmrpflash added tmomasdocs:guide-user:troubleshooting:vendor_specific_rescue [2023/07/29 16:16] – formatting vgaetera
Line 1: Line 1:
 ====== Rescue from failed firmware upgrade ====== ====== Rescue from failed firmware upgrade ======
- +<WRAP info>
-<WRAP center round tip 80%>+
 **RECOMMENDED:** **follow the procedures detailed at [[docs:guide-user:troubleshooting:failsafe_and_factory_reset| Failsafe and Factory Reset]] first**\\ **RECOMMENDED:** **follow the procedures detailed at [[docs:guide-user:troubleshooting:failsafe_and_factory_reset| Failsafe and Factory Reset]] first**\\
 That's what will most likely help you if you can't reach the OpenWrt interface anymore after installing packages, changing the password or the network configuration. That's what will most likely help you if you can't reach the OpenWrt interface anymore after installing packages, changing the password or the network configuration.
Line 8: Line 7:
 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. 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.
  
-This 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.+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 20: Line 19:
  
 ===== 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 30: Line 28:
 | 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]] | | 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]] |
 |:::| nmrpflash | https://github.com/jclehner/nmrpflash | |:::| 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]]. | [[http://forum.tp-link.com/showthread.php?81462-How-to-recovery-the-router-when-you-bricked-it|TP-Link forum 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]]. | [[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]] | | ::: | 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. | |
 | ZBT (ZBTLink) | Several devices support a [[#rescue_firmware_partition|rescue partition]].\\ On some devices, TFTP on a PC client can be used to rescue the firmware. | | | ZBT (ZBTLink) | Several devices support a [[#rescue_firmware_partition|rescue partition]].\\ On some devices, TFTP on a PC client can be used to rescue the firmware. | |
 +
 ===== Recovery for disk-image-based devices (e.g. SD-cards) ===== ===== Recovery for disk-image-based devices (e.g. SD-cards) =====
 Examples: the different Raspberry PI's, devices of PC Engines). Examples: the different Raspberry PI's, devices of PC Engines).
Line 41: Line 40:
  
 ===== 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:guide-user: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
  • Last modified: 2024/10/09 11:28
  • by danitool