• If posting about a radio issue: Include the HOST, DSP and UCM/secure firmware versions, flashcode and CPS version you're using along with the operating system info. This is critical information.

Rebooting XTS5000s

Status

PhillyPhoto

Contributing Member
Joined
Feb 17, 2013
Messages
84
Does anyone know why an XTS5000 would reboot on it's own? Using an OEM Impres battery, and I've reseated all the internal cables. You can hit and shake the radio around and it will not reboot, but reboots while sitting on a table listening. It's a model 3, so they only way to know it's done this is that it's back on the lock screen and you have to unlock it. It only does it while a certain site is being listened to on one system (hidden channel method, using preffered sites), but have seen it on another system as well (plain smartzone). It only happens at certain times, and if it's an inhibit command, it should be bricked, and shouldn't boot without an issue. I've seen it happen with another 5000, but don't have it anymore, so I know it's an issue not limited to 1 particular radio. Also, it was upgraded to ~R20 firmware with a legit ibutton, so the firmware shouldn't be an issue.
 

Mars

Prolific Contributor
CS Forums $upporter
Joined
Dec 21, 2011
Messages
4,993
It could be bad SRAM. That is where everything runs. That radio is going on 12 years old. (Unknown what year yours was made in).
 
OP
PhillyPhoto

PhillyPhoto

Contributing Member
Joined
Feb 17, 2013
Messages
84
Is that on the controller? Would it be worth it to replace it, or just deal with it at this point? Since it seems to be just certain sites, is there any software remediation possible? I don't have the radio or codeplug in front of me to check the serial number for it's age.
 

Mars

Prolific Contributor
CS Forums $upporter
Joined
Dec 21, 2011
Messages
4,993
Please reference the service manual for parts ID and locations.

You should also check Motorola's firmware release notes to verify there is not a firmware fix for your radio. I realize it has somewhat recent firmware already.

It is extremely difficult to pinpoint the problem through exchanges on a discussion forum without actually looking at the radio and debugging the issue.
 
Status