| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| docs:guide-user:troubleshooting:generic.debrick [2018/06/05 21:13] – link fixed tmomas | docs:guide-user:troubleshooting:generic.debrick [2018/12/19 12:54] – old revision restored (2018/09/14 19:51) per @tmomas' view jw0914 |
|---|
| |
| - if only something on the **[[docs:techref:filesystems#JFFS2]]** partition is broken, you are still able to -> **[[docs:guide-user:troubleshooting:failsafe_and_factory_reset|boot into OpenWrt failsafe mode]]** | - if only something on the **[[docs:techref:filesystems#JFFS2]]** partition is broken, you are still able to -> **[[docs:guide-user:troubleshooting:failsafe_and_factory_reset|boot into OpenWrt failsafe mode]]** |
| - if the **[[docs:techref:filesystems#SquashFS]]** partition or the **Kernel** is broken, you cannot boot into failsafe mode any longer. But you still have a functioning bootloader and so you should follow the same procedures as when you first -> **[[docs:guide-user:installation:generic.flashing#via.bootloader.and.ethernet.port|installed OpenWrt via bootloader]]**. | - if the **[[docs:techref:filesystems#SquashFS]]** partition or the **Kernel** is broken, you cannot boot into failsafe mode any longer. But you still have a functioning bootloader and so you should follow the same procedures as when you first -> **[[docs:guide-user:installation:generic.flashing#method_2via_bootloader_and_an_ethernet_port|installed OpenWrt via bootloader]]**. |
| - if the **[[docs:techref:bootloader]] is broken**, there are only two options left: | - if the **[[docs:techref:bootloader]] is broken**, there are only two options left: |
| - access your hardware through the -> **[[docs:techref:hardware:port.jtag|JTAG Port]]**, this //should// allow you to write to the flash. Restore the bootloader. | - access your hardware through the -> **[[docs:techref:hardware:port.jtag|JTAG Port]]**, this //should// allow you to write to the flash. Restore the bootloader. |
| ---- | ---- |
| |
| * https://forum.openwrt.org/viewtopic.php?id=35462 | * [[https://forum.openwrt.org/viewtopic.php?id=35462]] |
| |
| ==== As for the proper ways to recover a "bricked" router ==== | ==== As for the proper ways to recover a "bricked" router ==== |
| |
| If you have an Arduino board you can upload a sketch that will send the debrick commands via serial. An example that works for the TP-WR703N is available here: https://forum.openwrt.org/viewtopic.php?pid=191463. Note that the commands for your router could be different! | If you have an Arduino board you can upload a sketch that will send the debrick commands via serial. An example that works for the TP-WR703N is available here: https://forum.openwrt.org/viewtopic.php?pid=191463. Note that the commands for your router could be different! |
| | |
| | === Raspberry Pi === |
| | |
| | If you don't have a USB serial ttl but have a Raspberry Pi, you can use it to connect to the router's serial pins. The Raspberry Pi's uart works at 3.3V which is the correct voltage for most routers. Connect the GND to GND, the RX to TX, and the TX to RX. Leave VCC (or 3.3V) unconnected (that is, in the end you will only be connecting 3 pins out of 4). |
| |
| === WIFI === | === WIFI === |
| The example shows burning of a MX25L6406 for the [[toh/alfa.network/ap121|Alfa AP121]]. (No, I didn't brick it. ;-) I just wanted to replace a 4MB Flash with 8 MB flash.) | The example shows burning of a MX25L6406 for the [[toh/alfa.network/ap121|Alfa AP121]]. (No, I didn't brick it. ;-) I just wanted to replace a 4MB Flash with 8 MB flash.) |
| |
| Warning: If you use a FTDI cable for [[docs:techref:hardware:port.serial#prebuilt.cables|serial console]] then you probably must disable the FTDI serial port driver or exclude the product ID 0x6014 for the FT232H chip in the serial driver. Patch for MacOS: | Warning: If you use a FTDI cable for [[docs:techref:hardware:port.serial.cables#prebuilt_cables|serial console]] then you probably must disable the FTDI serial port driver or exclude the product ID 0x6014 for the FT232H chip in the serial driver. Patch for MacOS: |
| |
| <code> | <code> |