TP-Link Archer C50 (EU) V6.0 - 5 GHz interface not present

I just updated the build after doing another rebase. It's running already on my Archer C50:

https://s-berg.nl/files/openwrt-ramips-mt76x8-tplink_archer-c50-v6-squashfs-sysupgrade.bin

http://files.s-berg.nl/archer-c50-v6/ (has the new build and also has the previous builds)

The new URL does work and i got it loaded onto my Archer and have to configure it now.
The IPv6 topic was about my internet line.
Pure IPv6 will not be available anytime soon. :expressionless:

1 Like

Great you have it working! Be sure to let us know how it goes! I'll try to keep the image also in that other spot. I didn't realize I could use my ISP's webspace that way before.

i tried to flash the sysupgrade.bin through archers firm upgrade and it got bricked,ive tried flashing through tftp a bunch of stuff but nothing works,the router keeps blinking yellow with the last one red no matter what(the flashing through tftp doesnt gives errors but wont work

Connection received from 192.168.0.66 on port 59717 [18/10 23:44:22.984]
Write request for file <tp_recovery.bin>. Mode octet [18/10 23:44:22.984]
OACK: <blksize=512,tsize=7929856,> [18/10 23:44:22.985]
Using local port 59718 [18/10 23:44:22.985]
<tp_recovery.bin>: rcvd 15489 blks, 7929856 bytes in 1 s. 0 blk resent [18/10 23:44:23.823]

So first feedback from me after configuring the Archer C50v6 just as AccessPoint with 2 VLANs:

Everything responding faster than with my old WDR4900 and so far no connection problems with IoT or End devices.

One thing that is strange is that the LAN Port connected to my Zyxel XGS1210-12 is only negotioating to 100MBits.

root@gmdeernimp01ap:/var/log# ubus call system board
{
"kernel": "5.15.135",
"hostname": "gmdeernimp01ap",
"system": "MediaTek MT7628AN ver:1 eco:2",
"model": "TP-Link Archer C50 v6 (CA/EU/RU)",
"board_name": "tplink,archer-c50-v6",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "SNAPSHOT",
"revision": "r24122+32-4e5d45f1e6",
"target": "ramips/mt76x8",
"description": "OpenWrt SNAPSHOT r24122+32-4e5d45f1e6"
}
}
root@gmdeernimp01ap:/var/log# swconfig dev switch0 show
Global attributes:
enable_vlan: 1
alternate_vlan_disable: 0
bc_storm_protect: 0
led_frequency: 0
Port 0:
disable: 0
doubletag: 0
untag: 0
led: 5
lan: 0
recv_bad: 0
recv_good: 0
tr_bad: 0
tr_good: 0
pvid: 0
link: port:0 link:down
Port 1:
disable: 0
doubletag: 0
untag: 0
led: 5
lan: 1
recv_bad: 0
recv_good: 0
tr_bad: 0
tr_good: 0
pvid: 0
link: port:1 link:down
Port 2:
disable: 0
doubletag: 0
untag: 0
led: 5
lan: 1
recv_bad: 0
recv_good: 0
tr_bad: 0
tr_good: 0
pvid: 0
link: port:2 link:down
Port 3:
disable: 0
doubletag: 0
untag: 0
led: 5
lan: 1
recv_bad: 0
recv_good: 0
tr_bad: 0
tr_good: 0
pvid: 0
link: port:3 link:down
Port 4:
disable: 0
doubletag: 0
untag: 0
led: 5
lan: 1
recv_bad: 0
recv_good: 457
tr_bad: 0
tr_good: 346
pvid: 1
**link: port:4 link:up speed:100baseT full-duplex** 
Port 5:
disable: 1
doubletag: 0
untag: 0
led: ???
lan: 1
recv_bad: 0
recv_good: 0
tr_bad: 0
tr_good: 0
pvid: 0
link: port:5 link:down
Port 6:
disable: 0
doubletag: 0
untag: 0
led: ???
lan: ???
recv_bad: ???
recv_good: ???
tr_bad: ???
tr_good: ???
pvid: 0
link: port:6 link:up speed:1000baseT full-duplex 
VLAN 1:
ports: 4t 6t 
VLAN 107:
ports: 4t 6t 

Hi xristos, did you follow the instruction that explains prepending the bootloader to the sysupgrade image? According to the instructions if there is no bootloader prepended, it will cause a brick. It seems good news that the router is still attempting a tftp connection. Which model are you using? What tp_recovery.bin file are you using?

From what I observe, the ethernet ports are all limited to 100 MBit/s. This is also what it says on the box of my device.

The biggest advantage of this device would be its low power usage plus the fact that the device mostly already has OpenWRT support for a long time with significant testing done by users of previous device versions.

Did this device make it into the official release that just dropped?

i didnt cut anything i just stupidly downloaded and upgraded with openwrt-ramips-mt76x8-tplink_archer-c50-v6-squashfs-sysupgrade.bin
after that i tried all available firmware from here and c50's page on wrt but nothing seems to do anything


like so
tried both on remote file(tp_recovery / tp_recovery.bin) also the names of previously flashed firms but no luck

its c50 v6 EU

I'm sorry to hear this. Let it know if you feel it would be right to add extra warnings related to this and where it might be helpful.

From your screenshot it seems you're trying to use a TFTP client. If I understand the procedure correctly, you should actually set up a TFTP server which serves the right file. The device would request a particular filename from a particular IP address when you trigger its TFTP recovery mode. Note that I did not check this, please double check the instructions. Also note that it seems you need to do something specific with the official firmware image if that is what you are trying to recover to.

Alright, this model should work. Please keep us posted on your recovery process. I have the feeling you will figure it out! Just be extra careful with the image you will use for the recovery at this point!

No, the PR is still open. I hope that there can be more attention to it now that the release is out.

i tried the server thingy but i dont understand how it will serve the file since there is no option to choose a file (if there is a procedure on how to flash a file then whenever a file is uploaded it would help to also mention in the same post the said procedure) since its a working progress the posts are a mess .thats an idea though

ive tried to recover to of and wrt none works like this ,so i do something wrong i guess like you said with the tftp server/client

Is there an option to choose a directory to serve? The filename would have to match with what the box tries to fetch.

Please share what kind of image you are trying to flash. Did you prepare it specifically with the instructions written down for TFTP recovery? Using dd to deal with the relevant parts? What instructions are you following? If you make a mistake now I think the chances of recovery do become very small.

like i said ive tried the stock from tp link Archer C50(EU)_V6_211108 i even cutted the parts said in the archers wrt page , ive tried an experamental from here ive tried some others found around ,none does anything the light keep blinking ,only option is to point to a dir through tftp server and i did that but i get

Message truncated (length was 8) [19/10 14:45:22.594]

and thats all

used hxd to select and cut the first 200 then Insert 0x30000 bytes at offset 00 and then also cut from the bottom up another 30.000 length then added

I'm sorry at this point I'm afraid it's not clear enough what's happening on your end for me to assist more. If you could find somebody in your vicinity with knowledge on the topic maybe that would help more also to provide more detailed information on what exactly you're trying and what's happening at this point.

i cant say im a programmer but i have no idea what information you are looking for , i have told you the steps i took , i have told you the way i tried to flash it and you replied that it should be done through the server and not the client and i thank you for it ,but i have no idea what are you looking for , it the same as all bad flashes ,i flashed the https://s-berg.nl/files/openwrt-ramips-mt76x8-tplink_archer-c50-v6-squashfs-sysupgrade.bin
the router got bricked , i tried getting the stock image ,cutted the first 200 then added 30.000 zeros and then i cutted the last 30.000 tried to flash it ,nothing ,then i tried the stock without touching it ,the same,then i tried the experamental here,the same ,then i tried some others i found ,the same .what more could someone else tell you that i cant ? i dont think you asked me for something i could tell you

after some messing around i manage to the server and flash it by using lan1 (thats the only change i made so i cant think it was something else) the firm flashes but i get a router with no lights at all after that

Connection received from 192.168.0.2 on port 3722 [19/10 15:49:15.394]
Read request for file <tp_recovery.bin>. Mode octet [19/10 15:49:15.394]
OACK: <timeout=1,> [19/10 15:49:15.397]
Using local port 59951 [19/10 15:49:15.397]
<tp_recovery.bin>: sent 15490 blks, 7930368 bytes in 3 s. 0 blk resent [19/10 15:49:18.631]
Connection received from 192.168.0.2 on port 1801 [19/10 15:56:36.714]
Read request for file <tp_recovery.bin>. Mode octet [19/10 15:56:36.714]
OACK: <timeout=1,> [19/10 15:56:36.718]
Using local port 57278 [19/10 15:56:36.718]
<tp_recovery.bin>: sent 15490 blks, 7930368 bytes in 3 s. 0 blk resent [19/10 15:56:39.945]

for future ref i managed to flash Restoring Stock Firmware for Archer C50 V4 - #9 by pnlshd its for v4 but it worked , i lost the radio for access point though

2 Likes

I'm sorry if my questions were not clear enough. I can imagine it can be quite nerving when you have such a situation. I was mainly confused where you were finding the instructions that you were following.

Great that you have a running firmware again!! At this point having the carefully crafted firmware along with the bootloader from an ODM/stock firmware should allow flashing to OpenWRT with working radio I guess.

Let's make sure we capture as much as possible from your experience and document! Please share suggestions on what you believe could be helpful and what we could add to the documentation. Thank you so much for sharing everything!

can you give me the instructions so i wont mess up again ?
im on windows and every command is for linux os ,i would prefer not to install ubuntu cmd just for that

you probably referring to

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

is there an alternative to dd for win?

The main instruction is in the commit message over here:
https://github.com/openwrt/openwrt/pull/13547/commits/b64d816043b9ea87cd3753ac2e743ddb60ed285b

It was mostly copied from the v4 commit message. If you have any feedback on how it could be improved, that would be great.

Note that there seem to be different instructions to generate the file used for flashing through the stock firmware and the instructions to generate the file for flashing through the ODM firmware interface. The commands you are showing are related to the TFTP recovery variant if I'm correct.
The one you would need to flash through the ODM firmware would be:

TP-Link image:             tpl.bin
OpenWRT sysupgrade image:  owrt.bin

 > dd if=tpl.bin of=boot.bin bs=131584 count=1
 > cat owrt.bin >> boot.bin

This is the one I used myself to create the initial OpenWRT firmware to flash.

My knowledge is very limited regarding Windows. There might be similar tools to dd for Windows, but if they do something slightly differently for this particular situation, then I'm afraid you may run into a "brick" again. You will want to be sure you follow these instructions very precisely as it turns out that TP-Link's software does not really do any sanity checks on whatever image is provided before starting the flashing procedure.