XG-100M won't keyload

[tweiss3]

I have a XG-100M/CH721 that refuses to keyload. KFD Shield has no problem loading the 100P with the same keys. I have a OEM 14002-0143-10 REV2249 cable that was modified from the MX connector to Hirose. I go to Keyload - KVL and hit menu, the radio just sits "Idle". I can't read or load any key information. Below is the firmware versions read out just now.



Obviously, the firmware update on the mobile is a bit different than the portable, so I didn't go monkeying around there, afraid to brick it.
I have firmwares: 100M XLP R06T02, CH271 Main R07G17, DES-CFB R04B03 & HALM R04A01

I'm not even sure if firmware reflashes would do anything. Any help will be great. I do have 35, 37 & 45 in the feature set, so I "should" be good to go.

 

[prcguy]

I've never been able to keyload a 100M except with Harris KeyAdmin and a DB9 programming cable.

 

[tweiss3]

I've never been able to keyload a 100M except with Harris KeyAdmin and a DB9 programming cable.

That's discouraging. Even with the OEM cable and a real KVL?

After spending too much time reading this morning, I'll dig into the mission plan and make sure there isn't something stupid turned off.

 

[Echo4Thirty]

That's discouraging. Even with the OEM cable and a real KVL?

After spending too much time reading this morning, I'll dig into the mission plan and make sure there isn't something stupid turned off.

The OEM cable for the XG series of mobiles is a level converter and is very hard to find. If you do find one, expect to pay hundreds of dollars for it.

 

[tweiss3]

The OEM cable for the XG series of mobiles is a level converter and is very hard to find. If you do find one, expect to pay hundreds of dollars for it.

I did purchase the OEM XG Keyloading Cable, and yes, it was rather expensive, more than I would have liked to pay if it's not going to work.

 

[Echo4Thirty]

To confirm you do have the correct AES/DES software modules installed as well as the proper features enabled in the feature string?

 

[tweiss3]

Feature code has 37 AES and 45 DES, firmware version is readable for both AES & DES.

 

[prcguy]

Feature code has 37 AES and 45 DES, firmware version is readable for both AES & DES.

What about software modules and revisions. do they show up when reading the radio?

 

[tweiss3]

1st post is what I got from RPM

ECP R06T02
OTP N/A
MCU No Response
VRB N/A
CH721 Main R07.16
RHHC N/A
AES 4.01
DES 4.03

The MCU no response has me confused, I'm not sure if that's a problem or not. All other features operate as expected when used. I also found in the mission plan that OTAP was off (turned on for good measure) and under Digital Voice Options, Max Key Bank was the default 0, will be revised to 2 for testing.

 

[tweiss3]

Well, I refashed AES, DES, ECP/XGP, CH721 main app & burn app (all successful):

BurnApp : R13C03
BOOTAPP : 13
ECP/XGP : R06T02
OTP/VRM : Not Applicable
MCU : RNo Resp
VRB : Not Applicable
CH721/CH25 Main App : R07.17
RHHC : Not Applicable
AES Load Module : v04.01
DES Load Module : v04.03

I also updated the "Max Key Bank" and OTAP in the code plug. I either have something faulty in either the radio or the cable (maybe both).

The MCU "RNo Resp" has me concerned. I don't have an MCU firmware, or even know if this is normal.

This has been an extremely frustrating evening.

 

[nikronzo]

If the keyload cable was changed from MX to Hirose, it sounds like that might be the point of failure. Your versions, firmwares and features all look correct. I have had no issue keyloading from a KVL to the 100M using the OEM cable. You should double check that the radio accepts any keys by using Keyloader and putting the radio into HKL load mode and trying to load keys via the RS232 on the rear of the brick.

 

[Forts]

The MCU is not applicable to the 100M, so no worries there. Also, if you are going to be using DES-OFB you'll need option 14 (that has nothing to do with your keyloading adventures however).

 

[Echo4Thirty]

The MCU is not applicable to the 100M, so no worries there. Also, if you are going to be using DES-OFB you'll need option 14 (that has nothing to do with your keyloading adventures however).

I thought I read somewhere that on later firmware in the Unity, if you had 37 you also had DES-OFB. 45 shows up as DES-CFB, which is not the same as DES-OFB from what I understand.

 

[Forts]

I'm my experience, that is not true. You still need option 14 for OFB. And correct CFB and OFB are different variants of DES.

 

[Echo4Thirty]

I'm my experience, that is not true. You still need option 14 for OFB. And correct CFB and OFB are different variants of DES.

Maybe I am thinking about the goofy unity portable.

 

[TDR-94]

There are only two feature options (ENCRYPTION and DES-CFB) in XG-100P. ENCRYPTION enables AES-256 and DES-OFB.The XG-100M has the older feature code numbers for the different encryption types. At least that's how the features are displayed with the standard display.

 

[Echo4Thirty]

The 100M seems to have a hybrid type feature display. The ones we have do not list 01 03 04 etc, but start at higher numbers. Our displayed features are 33 37 39 41 42 44 47 48 49 58. While it does not display 06, we can program Proscan features for example.

 

[TDR-94]

Yeah, it's strange how they morphed the two types of displaying features into the XG-100P as well.

 

[tweiss3]

Good to know about the MCU. It loaded DES keys with only 45, no 14. I did never get the cable to work, had to ask for some help to get keys loaded elsewhere.