Tytera MD-UV390 encryption issue

[naffMaster]

Did you get these from Buy Two Way Radios - Lowest 2 Way Radio Prices Anywhere! by chance? I am having the same issue with mine. My buddy got ones off of Amazon and they worked without any issues.

No, from AliExpress. Loot at my first post from 24 August, to see the solution for your issue.

 

[turdish]

Hello, I've recently boutght Tyt MD-UV390 10 watts version with AES256 encryption. It has a "AES256" sticker along with "Plus" in battery chamber, so I guess it's Plus version. AES256 doesn't work, neither do ARC4 and AES128. Enhanced and basic did their job well. Creating keys then changing them don't work.Everyone can hear the voice as if it were not encrypted. CPS v02.34. When trying to download "privacy", it downloads it correctly - name and type of enc is correct, although keys are blurred and protected. Where is the problem? Thanks for any advice.

Disclaimer: in my country, ham radio can use enc.

3 Questions;

1)I under channel programming, did you select enc type AES and key ID assignment for the specific channel?
2) what version of firmware are you running on HT? I was able to get it working on FW ver s119.33 (link found on a forum link here somewhere).
3) when you initially load encryption in cps it is in the clear. I advise saving it off to a .Dec file on your PC for other radio programming If needed. For some reason when reading the enc from radio it obfuscates the keys (security feature, I guess). Once you read from radio you can save to a .dec file and reload on other radios.

The trick to getting AES universally working with other radio brands (Moto, Anytone, radioddity); you have to ensure that the Key Alias is named the same on all radios. For example; by default TYT naming convention for keys is numerical name (1,2,3, etc). Radioddity uses name conventions are hard coded to "AES1", "AES2". So to get them both using the same key, the TYT keys need to be renamed to "AES1" "AES2".

Hope that helps a bit. Will try and find fw and cps links and post them for you.

 

[naffMaster]

1. I select universal enc and key name/ID/whatever.
2. S219.043, as I have written.
3. Is this necessary to have the communication between Radioddity and TYT by naming the keys exactly the same? In Tyteras 390 Plus it doesn't matter. I had checked it already.

I have the CPS for my FW. Thanks.

 

[turdish]

Hey sorry for late response. Yeah for me the key had to have the same name. I'm not a DMR engineer, but I think the key name may be incorporated with the key checksum in the initialization frame/header when Txing...maybe.

 

[WFRP399]

3 Questions;

1)I under channel programming, did you select enc type AES and key ID assignment for the specific channel?
2) what version of firmware are you running on HT? I was able to get it working on FW ver s119.33 (link found on a forum link here somewhere).
3) when you initially load encryption in cps it is in the clear. I advise saving it off to a .Dec file on your PC for other radio programming If needed. For some reason when reading the enc from radio it obfuscates the keys (security feature, I guess). Once you read from radio you can save to a .dec file and reload on other radios.

The trick to getting AES universally working with other radio brands (Moto, Anytone, radioddity); you have to ensure that the Key Alias is named the same on all radios. For example; by default TYT naming convention for keys is numerical name (1,2,3, etc). Radioddity uses name conventions are hard coded to "AES1", "AES2". So to get them both using the same key, the TYT keys need to be renamed to "AES1" "AES2".

Hope that helps a bit. Will try and find fw and cps links and post them for you.

Does anyone know what Motorola/Vertex use for key aliases with ADP?

I have been goofing around with a UV-390 Plus and an EVX-534 trying to get the ARC4 to work together but they won't.

 

[WFRP399]

Here are the Settings in the CPS for the UV390



Here the settings in the CPS for the Vertex EVX-534

I can't the EVX and the UV390 to talk to one another. I tried naming the Alias "1" on both radios and also tried "PRVY - 1" on both radios. The squelch opens up, the radio tags appear but the audio is scrambled. Two UV390s will however work together just fine using the above settings.

Any idea of the Enhanced Privacy on the Vertex is something other than ARC4/RC4?

 

[doriboni]

Does anyone know what Motorola/Vertex use for key aliases with ADP?

I have been goofing around with a UV-390 Plus and an EVX-534 trying to get the ARC4 to work together but they won't.

Do you have the possibility to record a.wav file with an RTL-SDR of your ARC4-UV390 and your ARC4-VERTEX?

 

[irudzko]

Hello, I've recently boutght Tyt MD-UV390 10 watts version with AES256 encryption. It has a "AES256" sticker along with "Plus" in battery chamber, so I guess it's Plus version. AES256 doesn't work, neither do ARC4 and AES128. Enhanced and basic did their job well. Creating keys then changing them don't work.Everyone can hear the voice as if it were not encrypted. CPS v02.34. When trying to download "privacy", it downloads it correctly - name and type of enc is correct, although keys are blurred and protected. Where is the problem? Thanks for any advice.

Disclaimer: in my country, ham radio can use enc.

Hello! It seems like you're experiencing issues with encryption on your TYT MD-UV390 Plus. The problem might be related to the CPS version you're using. CPS has been updated, and the latest version is v02.41. Updating to this version could resolve the encryption issues you're facing.

You can find the updated CPS v02.41 and related firmware at TYT MD-UV390 Plus CPS and Firmware.

Back up your current settings before updating, and carefully follow the instructions provided to ensure a smooth update process. I hope this helps!