Batboard

Has anyone tried reading an XTS5000 with an older version of firmware, in this case vintage R12, make a change and upload the change to the radio, then find that the radio is now showing the dreaded 01/82 error ? I have had this happen with 3 different radios and 2 very different computers. Both computers work perfectly fine when programming one with R17 firmware. The only I could recover it was to use FlashZap, because the regular CPS could no longer communicate with the radio.

Regards
Dave

What version R17 firmware were you using? 17.00.00 was a known problem child that nuked a lot of radios regardless of CPS used.

The firmware in the radio was an R12 series. I am using the latest 17.01.02 that caused the bricking. After reading the radio, making a change and programming it, the radio would come up with the 01/82. At that point most atempts to try and push the original codeplug or even read the radio would fail. At some point , while trying to read the radio, a
"NexGen 10" error would come up. These messages are related to firmware/software mismatch issues.

My immediate reaction is that this is why it's never a good idea to rush to the latest version of firmware or CPS from Motorola.

So what's the flashcode in the radios?

This particular Flashcode is 540008-000482-4. The model # is H18KEF9PW6AN.

escomm wrote:My immediate reaction is that this is why it's never a good idea to rush to the latest version of firmware or CPS from Motorola.

So at this point it seems there is no alternative, everything since 17 has been a problem.

FWIW I went thru the same when upgrading firmware, and FW19 brought it back (but I can't get it to actually upgrade the radio FW, just the heads).

So just stay at CPS 15.00.00? There have been so many CPS upgrade issues and debates around 16/17/18 that I've lost track of what's good and what's not...