APX APX Brick Recovery?

[BeamsBox]

Long story... short.

Just got off the phone with Motorola and they say, looks like a 'corrupt codeplug' bricked my APX 8500. Right out of the box, turned on fine. Uploaded a codeplug that's been fine up until now. When I turn it on, all I see is "APX 8500" for a split second, then it turns back off. (Not rebooting.) Like its just failing to boot altogether.

Since it doesn't fully boot, I can't even access it via CPS anymore.

Is there a recovery procedure/mode that might allow me to avoid sending the unit in to Motorola for repair?

Thanks prior.

 

[jeepsandradios]

Send to Depot.

 

[tyler3328]

Is this a dash mount or remote mount configuration? Did you do any type of firmware updates or codeplug updates just prior to complications? Have you confirmed good power to radio and control head (if remote) Double Check the ignition sense power AND if there is an accessor connector that it is securely in place. If its right out of the box and you have confirmed all the power and connections then id send it to depot.

Was the device on a TRS? Assuming that you're not able to read or write the device at all im not gonna think its inhibited as those will still let you read it will just say inhibited in the cps.

 

[BeamsBox]

Hey KB, I understand, but that's what I'm trying to avoid. I'd like to know exactly what happened to avoid the problem in the future. I assume depot will fix and return. If I just reload codeplug I risk the same situation.

Tyler, it is dashmount. I have it set up in my lab. Power and remote sense are present via a desktop power supply. I did do a codeplug update. I opened box, powered up fine. Opened CPS and verified rev18 FW. Opened the codeplug and verified it is rev18 as well. Copied it over and now radio won't even boot up. I don't know what TRS means. I will verify accessory connector in a few. Thx on that one.

 

[W3AXL]

Ignition sense line tied to +12V? Sounds like it could be programmed to require that on power-up. I'm not familiar with the APX settings for ignition sense but that was a valid option in Astro25 world.

 

[clbsquared]

I don't know what TRS means.

He’s asking if you had it programmed for a trunking system. If so, was it legit or for NAS? Could possibly have been inhibited by the system admin if it wasn’t a legit radio on the system.

 

[KevinC]

He’s asking if you had it programmed for a trunking system. If so, was it legit or for NAS? Could possibly have been inhibited by the system admin if it wasn’t a legit radio on the system.

CPS should still be able to attempt to read it if it was inhibited.

 

[BeamsBox]

Well, indeed it was the remote sense. Funny thing, I totally checked that. (Thought I had anyways.)

Thx all for helping out, I really appreciate the help!

 

[natedawg1604]

He’s asking if you had it programmed for a trunking system. If so, was it legit or for NAS? Could possibly have been inhibited by the system admin if it wasn’t a legit radio on the system.

I know it's nitpicking, but I would just add a footnote that this would ONLY happen to a NAS radio IF, AND ONLY IF, you didn't read all the instructions and warnings about how to do NAS correctly, AND you failed to setup Unitrunker to monitor the site(s) nearest you to make 100% sure you're radio is NOT affiliating (it would be totally obvious if you just check), AND you failed to notice the RED light on power-up saying "HEY IDIOT, I'M AFFILIATING" (second totally obvious sign). Put another way, the ONLY time a NAS radio would ever affiliate is if you didn't pay attention to anything and F&*%ed up big time.

 

[mancow]

You the same guy that asked on the FB page? If not there is a moto page with a guy dealing with the same issues. I want to say he resolved it and it was an imbalanced remote head power supply as opposed to brick power supply but not sure.

 

[BeamsBox]

You the same guy that asked on the FB page?

Nope, not that guy.

 

[Tech21]

If you programmed it for soft power off, try installing it. Most likely it is not broken, it's just not detecting the correct power source it is looking for, mainly ignition sense.

 

[Viking1]

Long story... short.

Just got off the phone with Motorola and they say, looks like a 'corrupt codeplug' bricked my APX 8500. Right out of the box, turned on fine. Uploaded a codeplug that's been fine up until now. When I turn it on, all I see is "APX 8500" for a split second, then it turns back off. (Not rebooting.) Like its just failing to boot altogether.

Since it doesn't fully boot, I can't even access it via CPS anymore.

Is there a recovery procedure/mode that might allow me to avoid sending the unit in to Motorola for repair?

Thanks prior.

Depot

 

[KevinC]

If you programmed it for soft power off, try installing it. Most likely it is not broken, it's just not detecting the correct power source it is looking for, mainly ignition sense.

Depot

See below...

Well, indeed it was the remote sense. Funny thing, I totally checked that. (Thought I had anyways.)

Thx all for helping out, I really appreciate the help!

 

[BeamsBox]

Problem was solved at post #8.

 

[gesucks]

I know it's nitpicking, but I would just add a footnote that this would ONLY happen to a NAS radio IF, AND ONLY IF, you didn't read all the instructions and warnings about how to do NAS correctly, AND you failed to setup Unitrunker to monitor the site(s) nearest you to make 100% sure you're radio is NOT affiliating (it would be totally obvious if you just check), AND you failed to notice the RED light on power-up saying "HEY IDIOT, I'M AFFILIATING" (second totally obvious sign). Put another way, the ONLY time a NAS radio would ever affiliate is if you didn't pay attention to anything and F&*%ed up big time.

100% not true. Even if you follow all the "NAS RULES" it still has to have an ID programmed in it. Many systems will randomly inhibit IDs that are not assigned to valid radios. That will kill your NAS radio. Example - you program your radio with ID 1234, when they send out the inhibit command for 1234, if you radio is listening to the system at that time, you will be inhibited.

 

[N4KVE]

And that’s why people use a genuine ID # that’s on the system. That way it’s not randomly inhibited. Someone with a high rank in the department.

 

[CanesFan95]

And that’s why people use a genuine ID # that’s on the system. That way it’s not randomly inhibited. Someone with a high rank in the department.

^ Which is another benefit of Unitrunker / DSD+.

 

[ElroyJetson]

Assign an ID that's used in the system but very low priority. Such as one for the dog catcher, or the street sweeper's assistant, or something like that. DON'T dupe the Sheriff's personal ID. It's especially important to try to avoid such things on systems that still use the individual call or page features. (Less common since nobody DOESN'T have a cell phone these days.)