Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:user-guide:vendor_specific_rescue [2018/02/20 20:48] – ↷ Links adapted because of a move operation bobafetthotmail | docs:guide-user:troubleshooting:vendor_specific_rescue [2024/10/09 11:28] (current) – [Manufacturer-generic firmware recovery procedures] ubnt rescue linkk danitool | ||
|---|---|---|---|
| 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 upgrade, so a LEDE upgrade will not overwrite this rescue function. | + | <WRAP info> |
| + | If you can't reach the OpenWrt interface | ||
| + | </ | ||
| - | 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' |
| + | |||
| + | 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 " | + | Check the " |
| - | * https:// | + | * [[toh:start|Table of Hardware]] |
| - | * https:// | + | |
| Some of the methods may require creating a custom RS232-serial-cable or soldering-skills, | Some of the methods may require creating a custom RS232-serial-cable or soldering-skills, | ||
| ===== 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 | | Linksys | ||
| | Mikrotik | | Mikrotik | ||
| - | | Netgear | + | | Netgear |
| - | | TP-Link | + | |:::| nmrpflash | https:// |
| - | | Ubiquiti (UBNT) | TFTP on a PC client can be used to rescue the firmware. | [[https:// | + | | TP-Link |
| + | | ::: | Webpage firmware recovery\\ See link for models which support this method. | [[https:// | ||
| + | | Ubiquiti (UBNT) | ||
| | Xiaomi | | Xiaomi | ||
| | ZBT (ZBTLink) | Several devices support a [[# | | ZBT (ZBTLink) | Several devices support a [[# | ||
| 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 |
| ===== 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: | |
| - | 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: | + | |
| ===== Rescue USB stick ===== | ===== Rescue USB stick ===== | ||
| - | Supported by some Xiaomi devices | + | Supported by some Xiaomi devices process for [[http:// |
| - | + | ||
| - | process for [[http:// | + | |
| - Download firmware and store as '' | - Download firmware and store as '' | ||
| - 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:// | + | - http:// |
| - http:// | - http:// | ||
| - 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' | - 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' | ||
| 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 |
| - | * Official D-Link documentation of this procedure is rare, a [[ftp:// | + | * Official D-Link documentation of this procedure is rare, a [[ftp:// |
| * Inofficial notes of [[https:// | * Inofficial notes of [[https:// | ||
| * Official [[http:// | * Official [[http:// | ||
| 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 | + | Most newer devices (mostly those with decent amount of flash ROM) have 2 independent firmware partitions. A usage strategy could be, to install |
| Procedure, to manually toggle between the two firmware partitions: | Procedure, to manually toggle between the two firmware partitions: | ||