# After Firmware update !!!
**URL:** https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085
**Category:** Professional Radios
**Created:** [January 15, 2017, 5:27pm UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085 "2017-01-15T17:27:27Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@nb9e](https://discourse.checkcheckonetwo.com/u/nb9e)
#### Post date: [January 15, 2017, 5:27pm UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/1 "2017-01-15T17:27:27Z")
After updating to the latest firmware on this site, my older(non removeable antenna 650’s) and newer 550’s and 650’s now all have the same unit private ID of 1234567891 and also now none of them will talk to CPS on serial cable. How do I change the ID and why aren’t they communicating over the serial port ? They are all at factory default programming as well. Reminds me of the unofficial Waris upgrade etc. Any ideas ? My original intent was so all these radios would talk to each other in private and public groups !!! Brian
---
### Author:  [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 15, 2017, 7:47pm UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/2 "2017-01-15T19:47:47Z")
> [@nb9e](#):
>
> After updating to the latest firmware on this site, my older(non removeable antenna 650’s) and newer 550’s and 650’s now all have the same unit private ID of 1234567891
Did you follow the [flashing instructions](http://www.checkcheckonetwo.com/forum/showthread.php?1424-Motorola-DTR-Radios-Start-Here&p=6560&viewfull=1#post6560) to the letter? My first guess is that you didn’t do the factory reset.
Let’s get the ID sorted out and then look at the CPS issue.
---
### Author:  [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 23, 2017, 1:24am UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/3 "2017-01-23T01:24:14Z")
How did you make out?
---
### Author:  [@nb9e](https://discourse.checkcheckonetwo.com/u/nb9e)
#### Post date: [January 28, 2017, 11:15am UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/4 "2017-01-28T11:15:54Z")
Got them fixed thanks !!! Sure wish I could land on a pair of dtr 2450’s I have some thins I would like to try with those. If anyone has a pair please contact me !!! Brian nb9e
---
### Author:  [@n1das](https://discourse.checkcheckonetwo.com/u/n1das)
#### Post date: [January 28, 2017, 11:58am UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/5 "2017-01-28T11:58:19Z")
> [@nb9e](#):
>
> Got them fixed thanks !!! Sure wish I could land on a pair of dtr 2450’s I have some thins I would like to try with those. If anyone has a pair please contact me !!! Brian nb9e
What was the fix?? This information can greatly help others in case they run into the same problem.
---
### Author:  [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 29, 2017, 1:03am UTC](https://discourse.checkcheckonetwo.com/t/after-firmware-update/2085/6 "2017-01-29T01:03:50Z")
I’m sure the “fix” was to follow the instructions as I mentioned.
[http://www.checkcheckonetwo.com/forum/showthread.php?1479-WEIRD-Unit-ID-s-All-Reseting-to-quot-1234567891-quot-When-Updating-Firmware](http://www.checkcheckonetwo.com/forum/showthread.php?1479-WEIRD-Unit-ID-s-All-Reseting-to-quot-1234567891-quot-When-Updating-Firmware)