BC125AT - 1.05.01 latest firmware - any updated info?

[JoeBearcat]

The backup is always a good idea, but your data should not have been erased.

 

[cellphone]

The backup is always a good idea, but your data should not have been erased.

Just FIY, I did the firmware update this morning from 1.05.01 to 1.06.05. All of my frequencies were cleared to 0.000, but the alpha tags remained. It was not a big deal for me as I had the programming saved, but this might bite others.

 

[626hawkeye]

The backup is always a good idea, but your data should not have been erased.

When I did the latest firmware update I had to reload my programming as well.

 

[737mech]

626hawkeye thanks for heads up, I just backed up my programming, did the firmware update and yes had to reload the freqs back in. 1 06 05 now.

 

[JoeBearcat]

Thanks for the reports. I will pass this on.

 

[RCjim]

The backup is always a good idea, but your data should not have been erased.

Just letting you know all was erased, when I turned it back on there was nothing to scan!
I know on my SDS scanners doing the updates doesn’t erase the info.
But once again thank you.
Looking forward to seeing you on Scanner Guys on YouTube in the near future!

 

[JoeBearcat]

"

Looking forward to seeing you on Scanner Guys on YouTube in the near future!

It might not be "near future". I want to get things under control first. I hope to be well into phase III by then (major bug fixes).

 

[JustLou]

Just FIY, I did the firmware update this morning from 1.05.01 to 1.06.05. All of my frequencies were cleared to 0.000, but the alpha tags remained. It was not a big deal for me as I had the programming saved, but this might bite others.

Same here

 

[JoeBearcat]

Will add a cautionary note to the TWIKI and inform the engineers.

 

[JoeBearcat]

For anyone who has had the 'frequencies zeroed out' issue, do you have a 370Z model or a 370A model?

 

[jaspence]

There has been some speculation that the last two firmware versions were for a part change. I have seen at least one report where attempting an older 1.03.01 version update bricked the 125.

 

[JoeBearcat]

There has been some speculation that the last two firmware versions were for a part change. I have seen at least one report where attempting an older 1.03.01 version update bricked the 125.

All true. You can confirm it on the TWIKI:

BC125ATFirmwareUpdate < UnidenMan4 < TWiki

info.uniden.com

 

[RCjim]

For anyone who has had the 'frequencies zeroed out' issue, do you have a 370Z model or a 370A model?

I have the 370Z. I had 1.04.02 before the update, from what I can hear it works as good as it did before the update, I guess I just like having the latest.

 

[JoeBearcat]

Has anyone had this issue with the 370A?

 

[cellphone]

For anyone who has had the 'frequencies zeroed out' issue, do you have a 370Z model or a 370A model?

Mine was a 370Z.

 

[JustLou]

For anyone who has had the 'frequencies zeroed out' issue, do you have a 370Z model or a 370A model?

370Z

 

[737mech]

For anyone who has had the 'frequencies zeroed out' issue, do you have a 370Z model or a 370A model?

I have the 370Z model.

 

[JoeBearcat]

OK. Lots of 370Z cases. Any with 370A?

 

[pro92b]

OK. Lots of 370Z cases. Any with 370A?

Didn't 370A always ship with 1.06.05 firmware? Does BC_VUP allow overwriting the firmware with the same version? BC_VUP isn't working at the moment with the Uniden server being down.

 

[JoeBearcat]

Some users did downgrade and re-upgraded to the latest firmware. I realize that is a very small subset, but was hoping someone might have done this and could tell if the issue exists in those models. I will tell the engineers to try it.

Some 370A units did ship with earlier versions (there were three versions after the latest main version previously available in BC_VUP). None shipped with 1.03.xx which I think was the latest BC_VUP version available until a few weeks ago when I updated it. The server is down so I can't check specifics.