Archer C20 V5 not rebooting after Firmware push

Hi All,
I downloaded the kernel and sysupgrade for Archer C20 V5 from the link:

Then using Solarwinds TFTP server on windows 10 desktop, I TFTPed the kernel and rebooted the router. There were no lights lit up even though it was powered-on and the UI was not accessible over or

Then I TFTPed the sysupgrate and rebooted the router. Now the status is

  1. No light lit up even though it's powered.
  2. Only a LAN port light lits up if I connect my desktop using a LAN cable
  3. No UI is accessible over or
  4. If I assign static IP, say to my ethernet adapter, I am not able to ping It says - Destination host unreachable.

Can you please help me recover the router?


Unfortunately the firmware selector does not direct the user to vital instructions which are found here:;a=commit;h=86e7353bff2a5de257de8ec62e782f016eed143c
In short this is one of the TP-Link models which always overwrites the bootloader during an upgrade, and requires a new bootloader to be the first part of the upgrade file. Since bootloaders are generally outside the scope of the OpenWrt project, it is necessary to combine the bootloader from a factory firmware file with OpenWrt before flashing.

Flashing an improper file will prevent any booting at all. The only way to recover now is to write directly to the flash chip with a hardware SPI programmer.

Thanks @mk24 for your response. Seems it's game set match for my router :grinning:

@mk24 I managed to recover my router without SPI programmer. The trick was in the link you shared. Just followed the below steps from the link

Installing via TFTP
Prepare an image like following (Filenames from factory image steps
apply here)

 > dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1
 > dd if=tpl.bin of=tmp.bin bs=131584 count=1
 > dd if=tmp.bin of=boot.bin bs=512 skip=1
 > cat boot.bin >> tp_recovery.bin
 > cat owrt.bin >> tp_recovery.bin

Place tp_recovery.bin in root directory of TFTP server and listen on

Connect router LAN ports with your computer and power up the router
while pressing the reset button. The router will download the image via
tftp and after ~1 Minute reboot into OpenWRT.

But I am unable to get PPPoE working in Archer V5. My modem's LAN Port 4 is in bridge mode which is connected to WAN port of router. The log says - PPPoE discovery failed.

But I can PPPoE working on old TPLink router with stock firmware.

Any suggestions?

Try this firmware and Upload that firmware I marked via TFTP it's stable version 19.07.7
Forget ver 21.02 till developers release the stable one
Good Luck

Thanks @David.S.Mckellen The router booted after I TFTPed the bin file you pointed to.
The LuCI is also accessible.
But I still struggling to get PPPoE working. Though PPPoE works on an old TP-Link router with stock firmware.
Seems I've to keep trying.

Maybe you're doing something wrong somewhere,somehow

I have managed to get PPPoE working.

Now I've run into another issue, it will be great if someone can help to sort it out.

I've a modem-cum-router installed by my ISP. It has two VLANS configured:
VLAN ID 100 for internet
VLAN ID 660 for VoIP

With the idea of getting a SIP software (e.g. MicroSIP) working on my desktop I did the following configs:

In ISP Router:

  1. Changed LAN Port 4 to bridge mode in ISP's router. Connected the LAN port to WAN Port of Archer C20 V5 (flashed with Openwrt 19.07.7).

In Archer C20 V5:

  1. Defined a PPPoE interface under Network->Interfaces which use eth0.2 as parent interface. At this point PPPoE works.

  2. Under Network->Switch, created a VLAN with ID 660, with CPU and WAN ports as tagged and all other ports as off. This is to get VoIP traffic routed to a different interface (to be newly created under Network->Interfaces)

Moment I did Step 3, the PPPoE disconnected. I deleted the VLAN from Network->Switch, PPPoE comes back to life.

What could be the reason:

  1. Is my ISP router passing untagged VLANs down the bridged port?
  2. Is it a bug in OpenWRT 19.07.7?
  3. Any other reason?

Please can anyone help to fix the problem?


If it works as described, you should be tagging the pppoe packets 100. Tagged and untagged on the same cable is tricky and doesn't always work on consumer hardware.

I tried tagging 100 Also. Below are the steps I did:

Under Network-> switch

  1. Created VLAN 660 with cpu and wan ports as tagged, rest off.

  2. Created VLAN 100 with cpu and wan ports as tagged, rest off.

Under Network->Interfaces

  1. Created a PPPoE interface with eth0.100 as parent interface.

PPPoE failed this time also.

Any idea what might have gone wrong?