Archer C64 Freezes and Goes Offline After Updating to Firmware 1.14.3
Hello,
After updating to the latest firmware, my Archer C64 started freezing, and I can no longer connect to it either online or within the local network.
The only solution that works is a physical reboot. The issue occurs every 1-2 hours.
I have a main router and two secondary ones set up with EasyMesh. Before the update, everything was working perfectly.
Unfortunately, I cannot seem to downgrade to the previous firmware version (e.g., Archer C64(EU)_V1_1.13.15 Build 240812) from:
https://www.tp-link.com/en/support/download/archer-c64/#Firmware
In the logs, I see the following entries:
158 INFO 0days, 00:11:21, [upgrade]start upgrade
159 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
160 ERROR 0days, 00:11:21, [upgrade]CID not match, 0x4444:0x4544
161 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x504a
162 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5552
163 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5754
164 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5242
165 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x4143
166 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
167 ERROR 0days, 00:11:21, [upgrade]CID not match, 0x4444:0x4144
168 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5552
169 ERROR 0days, 00:11:21, [upgrade]SID not match, 0x5545:0x5355
170 ERROR 0days, 00:11:21, [upgrade]main version 0x10d00 is smaller than 0x10e00!
Considering that resolving this issue might take time, I kindly ask you to provide instructions on how to downgrade to the previous firmware version.
These problems have rendered my device almost unusable, and I urgently need a solution.
Thank you!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
As I mentioned earlier, the device freezes when the UART console endlessly outputs "[mt7626]kick out msg fail".
This indicates that the device is stuck in an infinite loop.
I can assume that during this time, the CPU is at 100% utilization, which causes the entire device to overheat — something it wasn’t designed to handle.
Now imagine what might happen if the router is left unattended or not rebooted for a few days in this state.
How did I figure out the issue is related to RTMP?
It was straightforward — I searched for the error message the router provided via UART on GitHub.
The search returned 83 results, all of them tied to RTMP on various devices.
Here are a few examples:
These findings strongly suggest that the issue is tied to how RTMP is handled on this firmware version.
- Copy Link
- Report Inappropriate Content
The support engineer has offered you a beta firmware via email, have you found it? It's suggested to update the beta firmware and monitor if the issue can be fixed.
- Copy Link
- Report Inappropriate Content
@Kevin_Z
Thank you for your response. I’ve installed the beta version and will monitor the issue. I’ll report the results once I have more information.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 36
Views: 1132
Replies: 33
Voters 1
