Anyone run into this? When I read the radio with CPS, it says its codeplug version CP03.10.0F, firmware version R5E.06.05, and a DTR410.
However, the case is a DTR550, black glass screen with DTR550 on the outside. Can these be easily rehoused with a different model?
I’ve heard that 550s can be flashed with 410 firmware, but I’ve not seen it myself or talked to anyone who’s done it.
I haven’t got a radio handy, but is there not a label under the battery with the model # on it?
Yep it does say Mdi: DTR550 Jul 06,2012
Sounds like you found the sticker. Here’s one of mine:
Have you tried flashing it to a 550?
All Ive tried is flashing it with the two firmware’s you have posted. Both times it says it had the most recent already. Is there a separate file I should be flashing with? Your pic looks identical to mine.
So the flashing software will not allow you to “downgrade” i.e. flash the radio to R5E.06.01? (R5E.06.05 is the latest)
I have no idea if fooling around like this might brick your radio, btw.
I have another piece of software on my computer, I don’t know if it’s any different than the other flash software, but you can give it a try if you’re feeling brave…
Here’s the log when I try to flash that radio with your Gen3Flash.zip attachment:
[15:23:44] Updating configuration parameters
[15:23:44] Reading configuration file C:\Program Files (x86)\Motorola\DTR Gen3 Flash Tool\DTR 550 Gen3 Flasher\DTR550 Flash.cfg
[15:23:44] Reading product file C:\Program Files (x86)\Motorola\DTR Gen3 Flash Tool\DTR 550 Gen3 Flasher\iDEN_Falcon.xfp
[15:23:44] USB> Driver successfully intialized on Windows XP
[15:23:48] USB1> Device Attached
[15:23:50] USB1> Queueing item with sequence number 0
[15:23:50] USB1> Starting FDI-Enhanced Reverse Flash
[15:23:55] USB1> Starting file save rev_flash.s19
[15:23:55] USB1> Item finished with sequence number 0
[15:23:55] Error> unable to flash due to model mismatch. Please choose the right tool to flash the radio.
Log from the General Flashing Tool or (R5E.06.01):
[15:26:17] Updating configuration parameters
[15:26:17] Reading configuration file C:\Program Files (x86)\Motorola Solutions\DTR Flash Tool - General\DTR Flash.cfg
[15:26:17] Reading product file C:\Program Files (x86)\Motorola Solutions\DTR Flash Tool - General\iDEN_Falcon.xfp
[15:26:18] USB> Driver successfully intialized on Windows XP
[15:26:21] USB1> Queueing item with sequence number 0
[15:26:21] USB1> Starting FDI-Enhanced Reverse Flash
[15:26:25] USB1> Starting file save rev_flash.s19
[15:26:25] USB1> Item finished with sequence number 0
[15:26:30] Error> The radio has the latest firmware. The flash operation stops.
Then finally, the R5E.06.05 Flash tool:
[15:28:16] Updating configuration parameters
[15:28:16] Reading configuration file C:\Program Files (x86)\Motorola Solutions\DTR Flash R5E.06.05\DTR Flash.cfg
[15:28:16] Reading product file C:\Program Files (x86)\Motorola Solutions\DTR Flash R5E.06.05\iDEN_Falcon.xfp
[15:28:16] USB> Driver successfully intialized on Windows XP
[15:28:18] USB1> Queueing item with sequence number 0
[15:28:18] USB1> Starting FDI-Enhanced Reverse Flash
[15:28:21] USB1> Starting file save rev_flash.s19
[15:28:22] USB1> Item finished with sequence number 0
[15:28:26] Error> The radio has the latest firmware. The flash operation stops.
Well, it’s beyond me. You may be stuck with a 410-flashed 550 unless someone joins up that knows the secret…
If you don’t care about bricking your radio, you could try playing around with the settings in DTR Flash.cfg. If you brave, maybe changing enable_smart_flashing=1 to enable_smart_flashing=0
Again, just shooting in the dark. Don’t try anything if you don’t want to risk bricking your radio.
Sir, I have just read your posts. As an outsider looking in, I suspect that you actually have, for all practical purposes, a Motorola DTR410 in a DTR550 case. This may have been a mistake from the factory, or someone who has moved the board from a destroyed 410 and placed it into an inoperative DTR550 case that was still in pretty good shape. I cannot imagine someone doing this, but if your CPS is reading the radio as a 410, I seriously doubt it is a simple flashing issue. I am not an expert here, but fairly knowledgeable with electronics. I also cannot imagine Motorola making two different board for these units, however, there probably is a reason beside the removable antenna that the 410 is less expensive than the 550/650’s. If I am thinking right the 410 also does not have the capability of private channels like the 550/650’s. Did you purchase this radio new or used?
It was a used radio. Its unfortunate if thats really the issue.
I’ve heard of this cross-flashing before, which makes me believe that it’s probably not a 410 in a 550 case. 3rd-hand info, but still…
http://forums.radioreference.com/budget-entry-level-transceivers/297792-dtr550-flashed-dtr410-need-help.html
http://batboard.batlabs.com/viewtopic.php?t=102348#p449772
I felt brave, so tried some settings changes in DTR Flash.cfg. Nothing I tried allowed me to flash my 550 with the 410 firmware. There’s something in the firmware file that has to match to the hardware. If someone were so inclined, maybe decompiling the firmware file and changing it’s header to match the hardware would work, but that sounds like way too much work!
I just went through some used radios I bought off of eBay and found that three of the DTR550s have this problem too. It’s killing me because we use a lot of private groups, so these radios aren’t going to be much use to us. Any chance anyone has found a work-around with it yet? Please let me know if there’s anything I can do to help. I don’t mind having some of these radios be guinea pigs with the possible risk of bricking.