Bug #7779

KT-8900 will not enter clone

Added by Lou Theriault about 2 years ago. Updated almost 2 years ago.

Status:Feedback Start date:04/08/2020
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:QYT KT-8900


Hi folks

I have a QTY KT-8900 mobile radio. I have recently received a programming cable and I'm trying to program the radio with CHIRP 20200227. I have selected the vendor, QTY and 8900 to download from radio. It starts to download then I get an error, radio did not enter clone mode. How can I sort this out? I did see to try the WACCOM 8900, this to did not help.

I noticed that there's another member that had the very same problem about 3 months ago, but I don't see a fix for it.

Please advise.


Related issues

related to Bug #7557: qty kt8900 -clone mode Closed 01/14/2020
related to Bug #7037: QYT KT-7900D - Radio did not enter clone mode Closed 09/05/2019


Updated by Bernhard Hailer about 2 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • Model affected changed from (All models) to QYT KT-8900
  • Platform changed from Windows to All

Have you been able to resolve this on your own since you submitted this?
If you haven't, and if you're still having this issue, please refer to the Wiki "How To Report Issues" and provide a debug log. Thanks!

Updated by Lou Theriault about 2 years ago

My apologies for not looking back into this bug. Shortly after I posted this bug report, we had a serious house fire. I haven't returned to check the status, nor try to find a solution to the issue. I will be checking in on a regular basis but it is highly unlikely that I'll have time to try troubleshooting the issue. But, by all means, if someone has a fix for this, please let me know. Thx. Lou.

Updated by Bernhard Hailer almost 2 years ago

Hello Lou, wow, I hope you and your family recovered well from the fire. We have too much of that here in California right now...
Regarding the problem you have: unfortunately there's not too much we can do without seeing the debug log (see my previous post). So when you get a chance, please collect that file and post it here.

Updated by Jim Unroe almost 2 years ago

Hi Lou,

This sounds to me like you are either selecting the wrong Vendor/Model or the radio has an MCU Version that CHIRP doesn't know about. Attaching a clean debug.log to this issue might shed some light on which one it is.

To create a "clean" debug.log file do the following.

1 Close CHIRP
2 Open CHIRP
3 Cause the error
4 Close CHIRP

Locate the debug.log file by using the instructions here.


Also available in: Atom PDF