XTS5000 fail 01/82 not accepting old codeplug

[Terriers618]

OK - Sorry to be repetative but I wanted to post this in its own thread with proper title etc.

So - I am getting the 01/82 - I cant jam a old codeplug back in - tried 15 times with diff codeplugs and even tried to use a newer CPS version. It all says write successful but then radio still says fail!!!!

Any ideas? This transpired from me hacking the CPS to allow out of band. I turned the radio off and back on and boom there was the error.

CPS has been reinstalled and old hex edited patport file deleted.

Any ideas??? This radio is in great shape, it will kill me to know I ruined it.

Thanks for the help!

[tvsjr]

I suspect you mean Fail 01/82... not 01/28.

[Terriers618]

Yes. And the last post was not off topic. I felt it was necessary after posting there to create a new thread in the appropriate forum so that users with similar issues can easily find solutions. At least reference this thread in the thread you locked!


Still cant get a codeplug into the radio to relieve the error

[n7maq]

What style of programming cable are you using? Is it OEM?


Jim

[wavetar]

Possibly whatever you did to allow out of band programming caused the CPS to write to a section of the codeplug which it normally cannot? Or, it may be pure coincidence. I have seen similar 01/82 problems with the Jedi series, where often using LAB to force in a codeplug has fixed it where a regular RSS write did not. I have also seen where even that did not fix it, and it was an actual hardware failure.

Todd

[Terriers618]

The cable is an after market cable that I have been using for some time now from a reputable dealer. I had read in certain places that it took users multiple times of writing the codeplug to have the problem resolved. I dont want to make anything worse than it already is so I dont want to continue jamming different codeplugs into the radio.

CPS says it accepts and has written - radio continues to display fail.

[n7maq]

The cable is an after market cable that I have been using for some time now from a reputable dealer. I had read in certain places that it took users multiple times of writing the codeplug to have the problem resolved. I dont want to make anything worse than it already is so I dont want to continue jamming different codeplugs into the radio.

CPS says it accepts and has written - radio continues to display fail.

Try to use an OEM USB cable, or send it to some who has one. I have seen this problem on a friends radio, and he also used a "good" (no such thing for an Astro25) a/m cable. He was not able to recover the radio.

What band, and flash was it?

Jim

[Terriers618]

Flash

500008-000002-9

Q split UHF-L

This is not good news!!

[Terriers618]

I spoke to MOL today. They said that when re-writing the codeplug does not alleviate the problem then the radio needs to have the firmware reloaded(75 bucks). If that doesnt work then its off to the depo for 360 bucks(this would imply the flash chip is corrupted)

If anyone has any other ideas let me know. Or any extra flash keys they want to toss my way for a discounted rate!

[Terry_Glover]

I kind'a hate to post this but...

A search of past posts here will yield a whole bunch of horror stories from guys who have bricked high end radios then had to send them off to the depot for BIG $$ restoration. Number one reason for killing their equipment was an over confident attitude and cheap programming cables and hacked software.

It's best to take the advice of others here who are more experienced than some of the rest of us. I've followed good basic programming practices recommended here and, fortunately, I've never run into any issues.

It's to bad you're about to go into this weekend knowing that you've bricked an XTS5K... That sucks... I even feel your pain.

[akardam]

Knowing what the current host/dsp of the radio is might also help. I say that because there was at least one bug in Astro25 firmware that was related to codeplug corruption, that I am aware of.

The cable is an after market cable that I have been using for some time now from a reputable dealer.

I spoke to MOL today. They said that when re-writing the codeplug does not alleviate the problem then the radio needs to have the firmware reloaded(75 bucks). If that doesnt work then its off to the depo for 360 bucks(this would imply the flash chip is corrupted)

If anyone has any other ideas let me know. Or any extra flash keys they want to toss my way for a discounted rate!

I wouldn't trust anything short of an OEM cable for doing firmware refreshes on an Astro25 radio.

During the process of reloading the firmware, certian parts of the codeplug are touched that CPS does not normally touch - that's one reason the radio goes into bootstrap during such a proceedure. They are correct in saying that this proceedure might fix the problem. If it doesn't, it doesn't necessarily mean that the Flash ROM that stores the codeplug is bad, but it is a possibility. What is more likely is simply codeplug corruption beyond CPS's ability to deal with it.

Could you fix it with the tools at your or another entheusiasts disposal? Perhaps. Would I recommend it? Not unless you're %110 percent sure you know what you're doing. If not, and no offense but I suspect not, then I'd suck it up and have the unit flat rated to Motorola. Find a reputable MSS in your area and they should be able to take care of it.

[Terriers618]

You are absolutely right. I am learning my lesson the hard way. At this point I only hope that its only a 75 dollar lesson not a 360 dollar lesson. Either way its worth sending the radio for th 360 rather than selling for parts and not making nearly as much towards a new radio.

I will be purchasing a OEM cable immediately!

I think that our local shop can re flash it for next to nothing in cost. You are right in suspecting that dealing with flashing and firmware upgrading is not my expertise. I do however desire to give it the cheaper shot before shelling out the 360ish dollars to fix the issue at the depot.

The host/dsp is version 11 it just got updated in February.

Unfortunately I love to experiment, but I have learned my lesson about experimenting with my nicer equipment!

[akardam]

The host/dsp is version 11 it just got updated in February.

Is it Host 11.00.00? There was a known 01/82 problem with that revision. I don't know if there's an openly acknowledged SRN about it, but if there is, you may be able to get your radio fixed under warranty. I'd look into it.

[Terriers618]

Correct version. Going to give it an upgrade to 12 at local shop first. When I spoke to Motorola they didn't mention anything about the issue with version 11. We will see, I think that the flash upgrade should resolve the problem but we will see in a few days. In the mean time I will be posting a wanted ad for an OEM cable!!!

[Terriers618]

I would love to update you guys on how this went but the radio has been stolen in transit to the local shop where it would of been flash upgraded.... If I ever recover it I will let you know how I solved the issue.