InlandAZ
Member
I loaded this up so long ago I've forgotten. How do I find this file on my PC or Scanner?
Oops, figured it out - I should have known
Last edited:
Pro-668: Radio Shack PRO-668 loaded with Whistler DMR firmware
- Thread starter trp2525
- Start date
- Status
I loaded this up so long ago I've forgotten. How do I find this file on my PC or Scanner?
Oops, figured it out - I should have known
I have noticed an unusual feature in the Whistler EZ-Scan version 2.22 program. It appears to be modifying the CONFIG__.BIN file upon launch. My original version 3.10 file is 91,644 bytes. After EZ-Scan launches the file size becomes 91,128. This appears to have begun occurring recently as I do not recall seeing this activity when I previously programmed my scanner. The file modification will occur even if the file is marked as read only.
I haven't had any problem programming either of my two scanners with 2.22. The last time was 7/4.
I never did anything update wise until I read in here a bit to see if the updates were ok and would work with Eric's modifications.
A user on here though told me old Config.bin files would not restore his scanner even though he had old files archived. So going back doesn't seem to work.
I think this is wrong on Whistler's part to do this and its making me rethink whether I want to actually buy that TRX now. If this is how they treat customers/people then I don't know that I want to support them by buying their products. Maybe another 536 instead.
I never did anything update wise until I read in here a bit to see if the updates were ok and would work with Eric's modifications.
A user on here though told me old Config.bin files would not restore his scanner even though he had old files archived. So going back doesn't seem to work.
I think this is wrong on Whistler's part to do this and its making me rethink whether I want to actually buy that TRX now. If this is how they treat customers/people then I don't know that I want to support them by buying their products. Maybe another 536 instead.
AtlasFBG2
Member
I just updated the dsp again 3.1
Config_.bin file in the scanner changed from 5-22-17 to 7-9-17
I changed the clock date as before.
So far it is still receiving dmr and so far still connects with the tool Eric made.
- Joined
- Feb 18, 2016
- Messages
- 1,958
- Reaction score
- 338
That might just squash the conspiracy theory.
If we can get some more to try this to confirm. Then those with a problem can start looking locally for a problem.
I believe everyone who had the issue of losing DMR and the use of Eric's tools was updating from DSP 3.0 to DSP 3.1. I know that applied to myself and also to RR member sibley. Perhaps if you are already at DSP 3.1 you are not affected with a re-install of the DSP 3.1 firmware.
I don't think we need any further proof about what is happening here after Eric revealed what he found in the source code (information posted above). That pretty much confirms the speculations and hypotheses that have been floating around.
AtlasFBG2
Member
After I updated the pc application software it said something about needing additional setup.
I didn't read it quick enough.
Now it no longer receives dmr and the tool will not work. Wont even go back to Radio Shack firmware.
So is it the pc application software that triggers the date coding in dsp 3.1?
I was going to send the scanner in anyway so it is no big loose here.
- Joined
- Feb 18, 2016
- Messages
- 1,958
- Reaction score
- 338
So your now on ezscan 2.24? it worked in ezscan 2.23?
The 1080 version on Whistler site for download is 2.22
Last edited:
AtlasFBG2
Member
On 2.24 now was on 2.20 I think.
Hello,
I had an interesting day. I found that the routines to load the CONFIG__.BIN file changed in 4.6. When the file is read to initialize the DSP, any extra data in the file is put in a buffer. This only happens on power up.
I did an experiment. I wrote code that used the library routines in the firmware to dump part of the ram to a file on the SD Card. I modified the CONFIG.BIN while keeping the same file length. I powered up the scanner and powered it down after about 15 seconds of scanning. The dump file was on the SD Card. I went back to DSP Version 3.0.
I also found the scanner now reports boot version 1.0 in GREFwTool instead of Erased. I reflashed the scanner after I modified the DSP Version 3,1 file as the M16c code in the DSP 3.1 file modifies the bootloader and two CPU firmware routines. I am having some difficulty is figuring out how the code is changed. Maybe it has bugs and does not work properly on some models of scanner.
This is an interesting development as it provides a path to modify the scanner similar to the magic lantern program for Canon cameras.
Magic Lantern | Home
73 Eric
I had an interesting day. I found that the routines to load the CONFIG__.BIN file changed in 4.6. When the file is read to initialize the DSP, any extra data in the file is put in a buffer. This only happens on power up.
I did an experiment. I wrote code that used the library routines in the firmware to dump part of the ram to a file on the SD Card. I modified the CONFIG.BIN while keeping the same file length. I powered up the scanner and powered it down after about 15 seconds of scanning. The dump file was on the SD Card. I went back to DSP Version 3.0.
I also found the scanner now reports boot version 1.0 in GREFwTool instead of Erased. I reflashed the scanner after I modified the DSP Version 3,1 file as the M16c code in the DSP 3.1 file modifies the bootloader and two CPU firmware routines. I am having some difficulty is figuring out how the code is changed. Maybe it has bugs and does not work properly on some models of scanner.
This is an interesting development as it provides a path to modify the scanner similar to the magic lantern program for Canon cameras.
Magic Lantern | Home
73 Eric
A little Progress is great feeling hope you can break the code ...Great work my friend.
nice.
can you dump the bootloader ver. 2.0?
interesting what different from ver. 1.0.
Unintended Consequences
Guess my sixteen years of insider wisdom have fallen on deaf ears, not surprising with apparent big egos. I sincerely hope I'm wrong where this may ultimately lead hurting all of the scanning community more than you can imagine. Regards to all, Craig
nice.
can you dump the bootloader ver. 2.0?
interesting what different from ver. 1.0.
Guess my sixteen years of insider wisdom have fallen on deaf ears, not surprising with apparent big egos. I sincerely hope I'm wrong where this may ultimately lead hurting all of the scanning community more than you can imagine. Regards to all, Craig
Encryption and online feeds are already doing that @cpunut
I wasn't going to bring that up as the person who gives me the privledge to post here is the largest provider of online feeds. As you can imagine we have done business over the years and I have expressed concern.
I totally agree with you.
Here's how it works: With the exception of some paranoid jurisdictations who encrypted all, most might just encrypt tactical talkgroups. Then online feeds allow anyone with a portable device to listen, purchasing a scanner or knowing how to use one is no longer required. Some will post real time information to twitter feeds to make it even more easy to acquire information at the lowest end of the capability scale. This has caused specific event issues as we know, "sightseers" showing up, etc., and interfering with public safety operations. Remember when Boston PD asked Broadcastify to shut down the feed?
This leads to more encryption. A prime example is D.C. Police who went all encryption and noted online feeds as the major reason. I know more but it isn't useful to post publicly. This is a problem.
The hacking is just another aspect and am not sure people are reading between the lines of what I'm typing to see the danger. I'm not going to make a roadmap.
We need to help the hobby and not hurt it. Starts and ends with personal responsibility, whether being a sightseer or hacker.
Hello,nice.
can you dump the bootloader ver. 2.0?
interesting what different from ver. 1.0.
Whistler tightened up security. The connection to the website now uses TLS and a different base directory for update files. It appears the Ez-Scan application uses the boot version to either use the old method (Version 1) or a new method (Version 2) where they send the new encrypted file directly to the scanner rather than having the Ez-Scan application transcode it.
Whistler opened up a large security hole in the scanner. This reminds me of one aspect of the Sony BMG hack where they compromised security of the user's computer when they improved the security of their IP. It also has the potential of compromising their recent work to lock down the scanner with the Version 2.0 boot loader.
I have not published any GRE or Whistler Source Code and I am not going to start.
73 Eric
Septa3371CSX1
Member
Appears my 668 is no longer able to receive DMR. On a saved object (trunked wildcard or conventional DMR channel) I'll see the signal bars light up (and on a non DMR scanner hear DMR noise) but no voice or time slot and talkgroup info comes across. On search it stops on an active signal for a split second then resumes. I am on DSP 3.1 (which doesn't show on the GREWFTool) and DMR was working until the beginning of the month I'd say. I don't have DSP 3.0 to try to roll back. I may try the date trick and see if that does anything.
Welcome to the club lost my DMR about 2 weeks ago.I tried everything to bring it back no luck..Unless Eric Cotrell is kind enough to make a new Firmware we are stuck on VER,4.6 with no DMR.
Last edited:
I can confirm that once you have lost DMR with DSP 3.1, rolling back the DSP to 3.0 does not bring back DMR reception. EZScan confirmed that my DSP was in fact back to 3.0 but DMR reception and the use of Eric's tools did not return.
The only available "fix" at this point is to send your radio to Whistler for the official upgrade. As an added bonus you will then be able to upgrade your CPU firmware to 4.8 which will allow you to take full advantage of the logging feature in the new Control Demo 2 (computer control software) that Whistler recently released.
- Status
Similar threads
