I performed a reset yesterday and used the same backup file to restore it and after 24hr there are no random reboot. Must be some random bug back then and i wasn't able to get the logs for it.
did you had to follow any additional steps other than renaming the latest tftp snapshot to tp_recovery.bin and changing the ip on tftp machine to 192.168.0.66
I was running Archer_C5(SP_ESWISP)v4_3.16.0_0.9.1_up_boot(221210)_2022-12-11_13.02.43.zip prior to trying to flash the latest openwrt snapshot
I tried flashing the latest snapshot, the power button was constantly blinking after flashing, after sometime it stabilized but both wifi LEDs started blinking continuously
I switched back to my old firmware using the same steps and it was successful, surprising part was all the router settings was like before
I also tried the v19 build mentioned on the device page but it also failed. The same image worked a year back on the same variant of router but it isn't working now. My router was replaced by my isp earlier this year but it has the same version number and model number
i am also having the same act router, did you ever try to flash the snapshot build of openwrt ?
The router is available in two versions:
- with the RTL8367S chip (from the RTL8367C family)
- with the RTL8367S-VB chip (from the RTL8367D family)
Currently, only the RTL8367C family is fully supported.
For the RTL8367D family, only alpha/test version is available at: https://disk.yandex.ru/d/HrT5PMczO8PPBw
how can i identify which of those chips is my router using ?
Look at Support for new Archer c5 v4 - #549 by luizluca and photos above.
I want to enable TFTP recovery on my archer C5 v4. It's not accept TFTP recovery because the current bootloader(is it uboot?) version is too old.
- U-Boot 1.1.3 (Nov 27 2018 - 05:52:37)
- Firmware Version:3.16.0 0.9.1 v6014.0 Build 181127 Rel.22110n
I had updated to newer stocker firmware proviced
I updated to mietekn provided stock firmware Build 190815 but U-boot still the same and TFTP is still not working.
PS. which one is newer and better between C5v 4 lastest snapshot or dkpost3 provided's Openwrt 22.03.2 . ( can't find any 23.0x)
The Archer C5_V4_190815 firmware supports TFTP, I have been using it for years.
You can easily check if it supports it by looking for the strings "serverip 192.168.0.66" and "tp_recovery" in the firmware file.
TFTP upload procedure for this router:
- Rename the firmware bin file to tp_recovery.bin
- Change computer IP to 192.168.0.66, connect to router LAN port.
- Run TFTP serwer. Make sure that the firewall of the system on which you have the TFTP server is not blocking it.
- Start the router with the reset button pressed, the file will be automatically downloaded and after a while the router will restart.
- After updating, set your computer's IP to DHCP.
That's all.
You can find the latest firmware here at:
https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=ramips%2Fmt7620&id=tplink_archer-c5-v4
1 Like
Disclaimer: not familiar with this particular device, so this is only a generic idea, make sure to check the details for your device.
This suggests to me that you have flashed the (stripped?) OEM firmware from OpenWrt, doing that won't touch the bootloader though (that's the whole purpose of stripping, as mtd and friends can't cope with multiple mtds concatenated in one image file). So assuming you are now running the OEM firmware, download the original/ untampered OEM firmware matching your device from tp-link's servers and flash it (same version) it to your device again. If the downloaded OEM firmware includes a tftp enabled bootloader, that will be flashed -using the OEM updater- to your device that way.
1 Like
Thanks for reply slh and mietekn.
I flashed mietekn's vendor build 190815 after Openwrt via serial. Here are detail from the begining.
Default stock build 181127 --> Benwht's Openwrt 19.07.2(Device page suggestion ,My first time using serial as update via stock gui and TFTP recovery is not working) and then followed by these 3 bin (1) mietekn's proviced firmware build 190815 via serial (2) dkpost3's Openwrt 22 via serial (3) Snapshot with luci via Sysupgrade( My first time on Snapshot)
I only understand less than 50% from slh post. I don't know t stripping and mtd (his friend ,too 
) but I guess update via serial can't enable TFTP recovery mode ,only vendor firmware update page can update Uboot. right?
Do I have to run any command line in U-boot prompt?
So I have to return to build 190815 or older via serial and flash build 190815 again via vendor firmware update page to enable TFTP recovery mode , correct?
The TFTP procedure for this router does not require a serial, you connect via LAN, turn on the router with the reset button pressed and wait for it to finish. It probably couldn't be simpler.
1 Like
I was able to flash this particular firmware but I am encountering frequent reboots. Here is the system log that causes this.
mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
mt76x2e 0000:01:00.0: Build: 1
mt76x2e 0000:01:00.0: Build Time: 201607111443____
mt76x2e 0000:01:00.0: Firmware running!
ieee80211 phy0: Hardware restart was requested
Steps I have tried to fix this:-
-changing to a less used channel
-changing transmit power to 20dbm from default
-changing to WPA2-PSK
Add an issue on https://github.com/openwrt/openwrt/issues
On this router, I found incorrect output power indications, the antenna gain (5dBi) is omitted. In order not to exceed the limits in Poland, I reduce the gain to 15dBm (20-5) for 2.4GHz and to 18dBm (23-5) for 5GHz.
Can you mention about output power problem in your new notification.
I think I found the error, by default tp-link only allows channels up to 48 on the router that I had, it seems the error was being caused by setting the channels in the upper bands, 157 ish in this case, no errors since I set it to a lower band. It might be due to the overheating when using the upper channels or a hardware issue with the router itself.
Also the wireless for 5ghz band stops working at channel 52 no matter what country I select in the config. My country does allow channel 52 to be used.
Update on this, its still restarting but its less often.
Hello, I manifest after compiling .bin but it brings a kernel that is not compatible. How do I choose the target kernel or custom kernel before compiling the binaries? This is the kernel version for this release.
manifest after compiled
change kernel - 5.15.150-1-cd377b79c71a91df861d543ca3d926fc
by kernel - 5.15.150-1-51d8e34c6fc1acbb504dc09cfad98012
base-files - 1554-r23809-234f1a2efa
busybox - 1.36.1-1
ca-bundle - 20230311-1
cgi-io - 2022-08-10-901b0f04-21
dnsmasq - 2.90-2
dropbear - 2022.82-6
firewall4 - 2023-09-01-598d9fbb-1
fstools - 2023-02-28-bfe882d5-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2022-08-13-4c7b720b-2
hostapd-common - 2023-09-08-e5ccbfc6-6
iw - 5.19-1
iwinfo - 2023-07-01-ca79f641-1
jansson4 - 2.14-3
jshn - 2023-05-23-75a3b870-1
jsonfilter - 2024-01-23-594cfa86-1
kernel - 5.15.150-1-cd377b79c71a91df861d543ca3d926fc
kmod-cfg80211 - 5.15.150+6.1.24-3
kmod-crypto-aead - 5.15.150-1
kmod-crypto-ccm - 5.15.150-1
kmod-crypto-cmac - 5.15.150-1
kmod-crypto-crc32c - 5.15.150-1
kmod-crypto-ctr - 5.15.150-1
kmod-crypto-gcm - 5.15.150-1
kmod-crypto-gf128 - 5.15.150-1
kmod-crypto-ghash - 5.15.150-1
kmod-crypto-hash - 5.15.150-1
kmod-crypto-hmac - 5.15.150-1
kmod-crypto-manager - 5.15.150-1
kmod-crypto-null - 5.15.150-1
kmod-crypto-rng - 5.15.150-1
kmod-crypto-seqiv - 5.15.150-1
kmod-crypto-sha512 - 5.15.150-1
kmod-gpio-button-hotplug - 5.15.150-3
kmod-leds-gpio - 5.15.150-1
kmod-lib-crc-ccitt - 5.15.150-1
kmod-lib-crc32c - 5.15.150-1
kmod-libphy - 5.15.150-1
kmod-mac80211 - 5.15.150+6.1.24-3
kmod-mt76-core - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt76x02-common - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt76x2 - 5.15.150+2023-09-11-f1e1e67d-1
kmod-mt76x2-common - 5.15.150+2023-09-11-f1e1e67d-1
kmod-nf-conntrack - 5.15.150-1
kmod-nf-conntrack6 - 5.15.150-1
kmod-nf-flow - 5.15.150-1
kmod-nf-log - 5.15.150-1
kmod-nf-log6 - 5.15.150-1
kmod-nf-nat - 5.15.150-1
kmod-nf-reject - 5.15.150-1
kmod-nf-reject6 - 5.15.150-1
kmod-nfnetlink - 5.15.150-1
kmod-nft-core - 5.15.150-1
kmod-nft-fib - 5.15.150-1
kmod-nft-nat - 5.15.150-1
kmod-nft-offload - 5.15.150-1
kmod-nls-base - 5.15.150-1
kmod-ppp - 5.15.150-1
kmod-pppoe - 5.15.150-1
kmod-pppox - 5.15.150-1
kmod-rt2800-lib - 5.15.150+6.1.24-3
kmod-rt2800-mmio - 5.15.150+6.1.24-3
kmod-rt2800-soc - 5.15.150+6.1.24-3
kmod-rt2x00-lib - 5.15.150+6.1.24-3
kmod-rt2x00-mmio - 5.15.150+6.1.24-3
kmod-slhc - 5.15.150-1
kmod-swconfig - 5.15.150-1
kmod-switch-rtl8366-smi - 5.15.150-1
kmod-switch-rtl8367b - 5.15.150-1
kmod-usb-core - 5.15.150-1
kmod-usb-ehci - 5.15.150-1
kmod-usb-ledtrig-usbport - 5.15.150-1
kmod-usb-ohci - 5.15.150-1
kmod-usb2 - 5.15.150-1
libblobmsg-json20230523 - 2023-05-23-75a3b870-1
libc - 1.2.4-4
libgcc1 - 12.3.0-4
libiwinfo-data - 2023-07-01-ca79f641-1
libiwinfo20230701 - 2023-07-01-ca79f641-1
libjson-c5 - 0.16-3
libjson-script20230523 - 2023-05-23-75a3b870-1
liblucihttp-ucode - 2023-03-15-9b5b683f-1
liblucihttp0 - 2023-03-15-9b5b683f-1
libmbedtls12 - 2.28.7-2
libmnl0 - 1.0.5-1
libnftnl11 - 1.2.6-1
libnl-tiny1 - 2023-07-27-bc92a280-1
libpthread - 1.2.4-4
libubox20230523 - 2023-05-23-75a3b870-1
libubus20230605 - 2023-06-05-f787c97b-1
libuci20130104 - 2023-08-10-5781664d-1
libuclient20201210 - 2023-04-13-007d9454-1
libucode20230711 - 2023-11-07-a6e75e02-1
libustream-mbedtls20201210 - 2023-02-25-498f6e26-1
logd - 2022-08-13-4c7b720b-2
luci - git-23.051.66410-a505bb1
luci-app-firewall - git-24.067.01746-69867db
luci-app-opkg - git-24.043.63812-c89a68b
luci-base - git-24.073.29889-cd7e519
luci-light - git-23.024.33244-34dee82
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-24.075.44893-ac63bea
luci-mod-status - git-24.064.82650-3cbf270
luci-mod-system - git-24.067.01860-7a82b2f
luci-proto-ipv6 - git-23.355.78874-80140aa
luci-proto-ppp - git-21.158.38888-88b9d84
luci-theme-bootstrap - git-24.072.69878-ca51167
mtd - 26
netifd - 2024-01-04-c18cc79d-1
nftables-json - 1.0.8-1
odhcp6c - 2023-05-12-bcd28363-20
odhcpd-ipv6only - 2023-10-24-d8118f6e-1
openwrt-keyring - 2022-03-25-62471e69-2
opkg - 2022-02-24-d038e5b6-2
ppp - 2.4.9.git-2021-01-04-4
ppp-mod-pppoe - 2.4.9.git-2021-01-04-4
procd - 2023-06-25-2db83655-2
procd-seccomp - 2023-06-25-2db83655-2
procd-ujail - 2023-06-25-2db83655-2
rpcd - 2023-07-01-c07ab2f9-1
rpcd-mod-file - 2023-07-01-c07ab2f9-1
rpcd-mod-iwinfo - 2023-07-01-c07ab2f9-1
rpcd-mod-luci - 20240305-1
rpcd-mod-rrdns - 20170710
rpcd-mod-ucode - 2023-07-01-c07ab2f9-1
swconfig - 12
ubox - 2022-08-13-4c7b720b-2
ubus - 2023-06-05-f787c97b-1
ubusd - 2023-06-05-f787c97b-1
uci - 2023-08-10-5781664d-1
uclient-fetch - 2023-04-13-007d9454-1
ucode - 2023-11-07-a6e75e02-1
ucode-mod-fs - 2023-11-07-a6e75e02-1
ucode-mod-html - 1
ucode-mod-math - 2023-11-07-a6e75e02-1
ucode-mod-nl80211 - 2023-11-07-a6e75e02-1
ucode-mod-rtnl - 2023-11-07-a6e75e02-1
ucode-mod-ubus - 2023-11-07-a6e75e02-1
ucode-mod-uci - 2023-11-07-a6e75e02-1
ucode-mod-uloop - 2023-11-07-a6e75e02-1
uhttpd - 2023-06-25-34a8a74d-2
uhttpd-mod-ubus - 2023-06-25-34a8a74d-2
urandom-seed - 3
urngd - 2023-11-01-44365eb1-1
usign - 2020-05-23-f1f65026-1
wireless-regdb - 2024.01.23-1
wpad-basic-mbedtls - 2023-09-08-e5ccbfc6-6
search the forum for vermagic.
I generated the vermagic with the OpenWrt hash and extracted the config build from these parts: https://downloads.openwrt.org/releases/23.05.3/targets/ramips/mt7620/config.buildinfo. However, it compiles unnecessary packages which makes the compilation heavier, compiling more than 3500 packages compared to the first time which had fewer packages. Is there another way to do this without using config.buildinfo?
The TFTP without a serial interface worked for ages. However, the vendor image was not compatible with it. If you wanted to return to vendor firmware, you needed to cut a header from the firmware. See https://openwrt.org/toh/tp-link/archer_c5_v4#restoring_back_to_the_stock_firmware_via_tftp_recovery_mode
1 Like
I didn't ask about it or even ask any question, but the information may be useful to others.