Pro-668: Radio Shack PRO-668 loaded with Whistler DMR firmware

[joec157]

To adddress the issue of my USB working I had used it to update with Erics tool and updateded files.(3.1 and 4.6). So I didn't give it a thought. The options were: 1 do nothing and refund my $60.00 and the radio or keep my money and credit towards a TRX-1which will end up costing me $445.00. My thought was why not offer to fix it and do the upgrade? Have a call into them and waiting a reply.I even asked if they want my cable to see if there is a mating problem but any USB to mini a should work.Kind of bummed that this is happening,was looking forward to the upgraded radio.

 

[joec157]

And as far as any damage in shipping, the radio was wrapped in bubble wrap and in a box with no room for movement.Also sent UPS not USPS. Really just surprised this turning out to be a real hassle. I also think the price of the TRX-1 is a bit high since some places are selling it for around $450. Wendy HELP!

 

[Ghstwolf62]

Whistler released new updates for their SD scanners last Friday (June 30th) that included new PC Application versions, CPU Firmware versions and a new Control Demo version. Although DSP 3.1 was not re-numbered to a new version number at that time, I suspect that a change may have been made to DSP 3.1 to do a "check" to make sure it was installing to a genuine WS1080 or officially upgraded PRO-18/PRO-668/PSR-800. If that check was not successful, I believe DMR functionality was then disabled. It also did something that then made all versions of Eric's tool unable to change the CPU firmware back and forth.

My suspicions are just that but are based on what I personally experienced and what 3 other posters (Fasteddy2, carbonfiber and sibbley) here on RR have also confirmed. It appears that the original DSP 3.1 (which was released on May 22nd) initially worked OK with scanners that had been updated using Eric's tool but that apparently is no longer the case. Because all of the other latest updates were released on June 30th I believe that is when the change may have occurred. I can confirm that I downloaded DSP 3.1 on July 2nd and sibbley posted that he downloaded it on June 30th and we both experienced the same issues afterwards. YMMV

Sending you a PM

 

[trp2525]

To adddress the issue of my USB working I had used it to update with Erics tool and updateded files.(3.1 and 4.6). So I didn't give it a thought. The options were: 1 do nothing and refund my $60.00 and the radio or keep my money and credit towards a TRX-1which will end up costing me $445.00. My thought was why not offer to fix it and do the upgrade? Have a call into them and waiting a reply.I even asked if they want my cable to see if there is a mating problem but any USB to mini a should work.Kind of bummed that this is happening,was looking forward to the upgraded radio.

The offer to keep your $60 and give you credit towards a TRX-1 which will cost you an additional $445.00 is not really a good deal ($505.00 actual cost for the TRX-1). You can purchase a brand-new TRX-1 from Zip Scanners for $484.90 and that includes FREE shipping and no sales tax: https://www.zipscanners.com/trx-1-police-scanner.html

Whistler charges a flat-rate $120 for repairing their scanners that are out-of warranty. Even if they are willing to repair your PRO-668's USB port, I think there is a more cost-effective option. I would recommend that you have Whistler send the PRO-668 back to you and then have the USB port repaired/replaced at a place like G & G Communications in LeRoy, NY (highly recommended BTW). After it is repaired you can then send it back to Whistler for the upgrade and all should be well at that point. A little bit of a hassle and a little more work, but a workaround for the current dilemma that you are in.

 

[EricCottrell]

Hello,

I compared the DSP version 3.1 I updated after July 1st with one downloaded shortly after release and they are the same file. Here is the information on the DSP releases I have.

DSP Versions
File		Size	DSP	VOC	Build 	Release
dsp_0075	83,590	1.3	1.6	 75	03/24/2014 Initial WS-1080 Release
dsp_0090	87,076	2.1	1.6	 90	05/31/2016 Initial DMR
dsp_0093	86,572	2.2	1.6	 93	06/16/2016 DMR Simplex and DMR/X2 fixes
dsp_0094	86,582	2.3	1.6	 94	06/21/2016 DMR PDU Transmission Changes
dsp_0101	91,128	3.0	1.6	101	12/15/2016 Initial NXDN
dsp_0103	91,644	3.1	1.6	103	05/22/2017 P25 PDU Minor Enhancements

I would look at possible differences in the configuration files on the scanner for differences in performance. For example, Version 2.20 of the Ez-Scan Application had changes that will change user data. Zeromatic settings could cause problems with reception.

Version 2.20 - May 22, 2017

    Added Options to allow modification to the ZeroMatic values for the scanner, including a Load Defaults button on the Receive/PCIF Options sub-tab.

     Changed the Zeromatic code to verify and correct all values if they are found to be outside of allowed ranges. port when importing. If it cannot determing the correct port, the user will have to chose a port.

73 Eric

 

[n3617400]

dsp 3.1 contain code which check bootloader for some conditions
if conditions are match then make some patches in bootloader and firmware
this code disable receiving of dmr for unofficial firmwares and disable posibillity of using eric's tool
so it goes (vonnegut)

 

[joec157]

Thanks trp2525 that sounds like a way better deal than what they are offering.I will try to contact G&G and see what they say.Thanks again.

 

[Wackyracer]

dsp 3.1 contain code which check bootloader for some conditions
if conditions are match then make some patches in bootloader and firmware
this code disable receiving of dmr for unofficial firmwares and disable posibillity of using eric's tool
so it goes (vonnegut)

This not true...DMR worked fine on my hacked 668 with dsp 3.1 and either cpu firmware 4.5 or 4.6. If your having problems not receiving DMR it is strictly on your end, not the hacked firmware or Whistlers dsp version 3.1

I suspect something got corrupt on your computer or the scanner or your version of ezscan.

 

[n3617400]

This not true...DMR worked fine on my hacked 668 with dsp 3.1 and either cpu firmware 4.5 or 4.6. If your having problems not receiving DMR it is strictly on your end, not the hacked firmware or Whistlers dsp version 3.1

I suspect something got corrupt on your computer or the scanner or your version of ezscan.

ok. presumably this code disable receiving of dmr for unofficial firmwares and disable posibillity of using eric's tool.
i don't have PRO-668 for say this with 100% probability.
i see code which patched 1 place in bootloader and 2 places in firmware, but i dont know for which firmware it's corrections are intended

 

[Wackyracer]

ok. presumably this code disable receiving of dmr for unofficial firmwares and disable posibillity of using eric's tool.
i don't have PRO-668 for say this with 100% probability.
i see code which patched 1 place in bootloader and 2 places in firmware, but i dont know for which firmware it's corrections are intended

The bootloader loads the firmware to the chip, The CPU and DSP firmware didn't disable anything, You fail to account for why My 668 picked up DMR and I sold it that way and my mother's 668 still picks up DMR with DSP 3.1.

If it works for hundreds, but a few have a problem then it is a localized problem. Concentrate on why it doesn't work for you and solve the problem on your end.

 

[trp2525]

This not true...DMR worked fine on my hacked 668 with dsp 3.1 and either cpu firmware 4.5 or 4.6. If your having problems not receiving DMR it is strictly on your end, not the hacked firmware or Whistlers dsp version 3.1

I suspect something got corrupt on your computer or the scanner or your version of ezscan.

The bootloader loads the firmware to the chip, The CPU and DSP firmware didn't disable anything, You fail to account for why My 668 picked up DMR and I sold it that way and my mother's 668 still picks up DMR with DSP 3.1.

If it works for hundreds, but a few have a problem then it is a localized problem. Concentrate on why it doesn't work for you and solve the problem on your end.

While it is true that DSP 3.1 worked fine with CPU 4.5 or CPU 4.6 and DMR functionality remained intact, that is no longer the case based on information posted here on RR. DSP 3.1 was initially released on May 22nd and that initial version worked OK just like you and others have posted on this thread.

The Whistler PC application and CPU firmware versions for these scanners were updated last Friday, June 30th. While the DSP firmware remained at version 3.1 on June 30th it is speculated that some code was changed with DSP 3.1 (like what RR member n3617400 posted above) on that date and anyone downloading and installing it since then will lose the DMR functionality and the use of Eric's tool to change CPU versions.

I can state that I downloaded DSP 3.1 on July 2nd and lost my DMR and the functionality of Eric's tools and RR member sibley has posted that he downloaded and installed DSP 3.1 on June 30th and the same thing happened to him. For further confirmation of this change with DSP 3.1, RR members Fasteddy2 and carbonfiber also posted in this thread that they lost DMR and the use of Eric's tool after their installation of DSP 3.1 but they did not post the actual date(s) of their download and install. I just can't believe that all 4 of us have corrupt files or a "localized problem" as you state. I myself tried this on 2 different computers with 2 different operating systems (Windows XP SP3 and Windows 10 Home) and had the same exact results. Are both of my computers corrupt?

I can account for the fact that you had 2 working scanners with DSP 3.1 with DMR functioning fine (the one that you sold and your mother's scanner) because you downloaded and installed DSP 3.1 prior to the change(s) that Whistler made to it around June 30th. If you are totally confident in the information you have posted above you should do an experiment for all of us. You should take your mother's PRO-668 with DSP 3.1 that has functioning DMR and use EZScan to re-install the latest/newest version of DSP 3.1 that is currently on the Whistler update server. Please report back if you still have DMR functionality and the use of Eric's CPU change tools afterwards. It's certainly a gamble because like I and others have reported in this thread you may lose DMR and the use of Eric's tools on your mother's PRO-668 scanner if you do so.

 

[EricCottrell]

dsp 3.1 contain code which check bootloader for some conditions
if conditions are match then make some patches in bootloader and firmware
this code disable receiving of dmr for unofficial firmwares and disable posibillity of using eric's tool
so it goes (vonnegut)

Hello,

I noticed the Bootloader version on my PSR-800 shows Erased for the Bootloader version in the tool. This means it is was set to FF. I suspected there would be other moves, like tightening up the security of the firmware update. This is a chance you take. I am glad I did not go down this move/countermove rabbit hole.

73 Eric

 

[SCPD]

Interesting comment

Hello,

I noticed the Bootloader version on my PSR-800 shows Erased for the Bootloader version in the tool. This means it is was set to FF. I suspected there would be other moves, like tightening up the security of the firmware update. This is a chance you take. I am glad I did not go down this move/countermove rabbit hole.

73 Eric

I find your above comment interesting, as in this case you are the definition of "move" and if I'm correct made one or two "countermoves". Seems to me you're pretty deep in the rabbit hole and if someone's radio has been damaged, you are partly responsible.

 

[IAmSixNine]

I find your above comment interesting, as in this case you are the definition of "move" and if I'm correct made one or two "countermoves". Seems to me you're pretty deep in the rabbit hole and if someone's radio has been damaged, you are partly responsible.

He is in no way responsible for it. Saying he is partially responsible is pure ignorance.
The end user who opted to modify their radio is the responsible one.

Take some responsibility for your own actions. You (not you directly but the scanner owner) the scanner owner who opted to download software and modify the scanner is the responsible one. Eric provided us a way to make the units better, purely experimental and not required or mandatory.

 

[sibbley]

He is in no way responsible for it. Saying he is partially responsible is pure ignorance.
The end user who opted to modify their radio is the responsible one.

Take some responsibility for your own actions. You (not you directly but the scanner owner) the scanner owner who opted to download software and modify the scanner is the responsible one. Eric provided us a way to make the units better, purely experimental and not required or mandatory.

Correct. We as owners are completely responsible for opting to participate in this experiment. I don't think anyone ever said their scanner was damaged. Simply no more DMR/TRBO decode.

 

[sibbley]

Hello,

I noticed the Bootloader version on my PSR-800 shows Erased for the Bootloader version in the tool. This means it is was set to FF. I suspected there would be other moves, like tightening up the security of the firmware update. This is a chance you take. I am glad I did not go down this move/countermove rabbit hole.

73 Eric

Seems like those of us having "localized" problems were on to something after all.

Eric, I'd like to thank you again for allowing all of us, who wished, to participate in this experiment. It was fun while it lasted.

 

[JustLou]

He is in no way responsible for it. Saying he is partially responsible is pure ignorance.
The end user who opted to modify their radio is the responsible one.

Take some responsibility for your own actions. You (not you directly but the scanner owner) the scanner owner who opted to download software and modify the scanner is the responsible one. Eric provided us a way to make the units better, purely experimental and not required or mandatory.

Well said.

 

[MaximusTheGreat]

I find your above comment interesting, as in this case you are the definition of "move" and if I'm correct made one or two "countermoves". Seems to me you're pretty deep in the rabbit hole and if someone's radio has been damaged, you are partly responsible.

Dude!!! I don't know if you are from California or what, but you are smoking wayyyyy to much of that legal stuff they serve over there.

Eric is and should not be liable for any damages that the user did on his own accord. At NO time did he represent himself as a RS or Whistler representative or agent.

Eric posted very "Specific Instructions" on how to do it, what works and what doesn't work. I followed his ADVICE Or suggestions on what worked for HIM and proceeded at my own risk. I knew from the get go that any harm to my scanner is due to MY error. That being a power outage during procedure, computer problems, me unplugging the scanner while the update is happening. That's a risk I determined to be acceptable. A perfect example is how we ROOT our Android devices, Jailbreak the iPhones. Another example that I can bring up for those that don't understand what above means, Chirp programming software for amateur radios. If you use Chirp like most of us do. You can't expect to blame the developers of such software as you shouldn't of been using it or any third party software besides that of the manufacturers programming software. But those of us that use the software for the main purpose is that "It WORKS" better then the manufacturers software. There's always an unknown factor. Blaming him or anyone that gives us these tools is not the person that needs to be blamed. Look in the mirror and own it, you messed up for whatever reason. 3.5 worked for me and I stayed on it. I'm not going to keep pressing the update button when I know I'm not supposed to update it in the future. If I want future updates, then I'll pay for the official version. For my purposes, I am EXTREMELY happy with this tool. I know many people are. Just read the forums and FB for yourself.


There are ALOT of people in this forum and on FB that are computer illiterate. Those people are the ones that should NOT be messing around with tools on the computer that are considered for people that can ACTUALLY read, follow directions and can proficiently Google anything. A person that has a flip phone for cell phone or is stuck with using windows xp as there primary OS has no reason to being "Experimenting" with tools like this.

Long story short, people like you are the ones that should ALWAYS wait for official updates and use official software from whatever companies. And if no updates are available, then buy a newer model. Thanks to Eric, Whistler finally decided to take on the RS 668 and give it life again by extending support to it. Because of him we SHOULD ALL BE THANKFUL for his dedication and time involved with the project.

PS.. I'm beating a dead horse already. But I truly hope that people who blame him for this tool. Should NOT even bother with tinkering the MD 380 and installing MD 380 tools on your radio. Cause I'm sure you'll also blame Travis and the others for forcing you to do something that's "unofficially supported" by the manufacturers.

 

[SCPD]

Dude!!! I don't know if you are from California or what, but you are smoking wayyyyy to much of that legal stuff they serve over there.

Eric is and should not be liable for any damages that the user did on his own accord. At NO time did he represent himself as a RS or Whistler representative or agent.

Eric posted very "Specific Instructions" on how to do it, what works and what doesn't work. I followed his ADVICE Or suggestions on what worked for HIM and proceeded at my own risk. I knew from the get go that any harm to my scanner is due to MY error. That being a power outage during procedure, computer problems, me unplugging the scanner while the update is happening. That's a risk I determined to be acceptable. A perfect example is how we ROOT our Android devices, Jailbreak the iPhones. Another example that I can bring up for those that don't understand what above means, Chirp programming software for amateur radios. If you use Chirp like most of us do. You can't expect to blame the developers of such software as you shouldn't of been using it or any third party software besides that of the manufacturers programming software. But those of us that use the software for the main purpose is that "It WORKS" better then the manufacturers software. There's always an unknown factor. Blaming him or anyone that gives us these tools is not the person that needs to be blamed. Look in the mirror and own it, you messed up for whatever reason. 3.5 worked for me and I stayed on it. I'm not going to keep pressing the update button when I know I'm not supposed to update it in the future. If I want future updates, then I'll pay for the official version. For my purposes, I am EXTREMELY happy with this tool. I know many people are. Just read the forums and FB for yourself.


There are ALOT of people in this forum and on FB that are computer illiterate. Those people are the ones that should NOT be messing around with tools on the computer that are considered for people that can ACTUALLY read, follow directions and can proficiently Google anything. A person that has a flip phone for cell phone or is stuck with using windows xp as there primary OS has no reason to being "Experimenting" with tools like this.

Long story short, people like you are the ones that should ALWAYS wait for official updates and use official software from whatever companies. And if no updates are available, then buy a newer model. Thanks to Eric, Whistler finally decided to take on the RS 668 and give it life again by extending support to it. Because of him we SHOULD ALL BE THANKFUL for his dedication and time involved with the project.

PS.. I'm beating a dead horse already. But I truly hope that people who blame him for this tool. Should NOT even bother with tinkering the MD 380 and installing MD 380 tools on your radio. Cause I'm sure you'll also blame Travis and the others for forcing you to do something that's "unofficially supported" by the manufacturers.

I guess computer illerate would sure describe newbie me I didn't say "liable", I said *partially* responsible. I'm always amazed how words are changed followed by attacks. No I'm not in California. Guess we'll have to see about the damage part. One person noted that Whistler couldn't upgrade his radio.

 

[sibbley]

I guess computer illerate would sure describe newbie me I didn't say "liable", I said *partially* responsible. I'm always amazed how words are changed followed by attacks. No I'm not in California. Guess we'll have to see about the damage part. One person noted that Whistler couldn't upgrade his radio.

The person that noted Whistler couldn't upgrade his radio stated it was because of a faulty usb port. That would not be damage caused by the experimental upgrade.