CHIRP

Are you putting the radio into programming mode? If so, that's your problem. The radio should be on but in normal mode in order for chirp to be able to talk to it.

Dan Smith wrote in #note-1:

Are you putting the radio into programming mode? If so, that's your problem. The radio should be on but in normal mode in order for chirp to be able to talk to it.

No, not using program mode. Sorry about the last sentence in my post, "It won't let me upload an image". I meant that I couldn't upload an image of the radio with my post, like the rules say. I didn't have one handy, nor my phone for a pic. I tried to test it using "QS Portable Radio CPS", but I can't get it to connect using that program neither. I found my 3rd cable, and tried it, and I get the same outcome.

I went to device manager and checked everything pertaining to the connection with COM3. I found a warning logged in Event Viewer under, Source, Kernel-PnP.

Device FTDIBUS\VID_0403+PID_6001+12345678A\0000 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_2CA3&PID_0008\0001A0000000
Class Guid: {4d36e978-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719

UPDATE UPDATE UPDATE UPDATE

Even though the cable was fully inserted into the HT. I held the radio tight and put A LOT of pressure on the MIC/SPKR connector, tried to read and upload the data while doing so, and it was successful. So even though the cables were fully inserted, there still wasn't sufficient contact to transfer.

Okay, yep, this is a very common (maybe the most common) problem with the chinese radios. Very cheap manufacturing and very loose tolerances.

So are you good, I should close this?