Yes, I did that. Followed the steps you outlined to return to 1.23.07/ 1.03.06.
Custom Firmware for Encryption
- Thread starter pb_lonny
- Start date
Yes I did for both. I then went into Sentinel and updated to latest firmware as you instructed. Still have Set Debug File and Splash screen. Am I running the Sentinel firmware, or still using the 1.99.40 beta?
If you're seeing a logo image on startup, please note this is not actually part of the actual firmware! When your SDS100 is connected to your computer via USB, go to the drive that is your radio. There should be a folder, something like BCDx36HP - Go into that folder. There should be a .BMP file (opening.bmp, if I recall). You can safely delete this, as it's not part of the firmware, or completely necessary. (Although some have such opening screens to "beautify" the startup experience - I made mine from the Sentinel startup image, for example.)
After installing version 1.23.05
I should ask you for a video of the scanner booting process, showing the “See Scanner Information”-"Firmware Version" menu item, to make sure that the official firmware version is installed.
Yes, after installing version 1.23.05, Set Debug and Open Scanner Flash screen was still on scanner. I then opened Sentinel, Updated Firmware, and Main Version: 1.23.07 Sub Version 1.03.06 is the firmware.
Yes I did.
Does it show up like this?
It's just that in my practice I've never had one firmware version successfully flashed, but in the scanneer information menu there was a different firmware version.
And I've added firmware to my scanners more than 100 times.
I would like to see the whole process from copying the firmware file to the correct folder and then the flashing process and showing the scanner info menu. Can be sent to me in a private message.
It's just that in my practice I've never had one firmware version successfully flashed, but in the scanneer information menu there was a different firmware version.
And I've added firmware to my scanners more than 100 times.
I would like to see the whole process from copying the firmware file to the correct folder and then the flashing process and showing the scanner info menu. Can be sent to me in a private message.
Yes, like you I've downloaded beta firmware's so very familiar with the process.
@n3617400 ...got it!
I had 2 SDS 200's with the beta firmware in. Tried the 2nd SDS200, and was able to revert back without an issue. Now, back to the original SDS200. I plugged the scanner in, and deleted the entire firmware file, then Cleared User Data, updated to 1.23.07 via Sentinel and let the scanner load it in. I previously was attempting this with the SD card not in the scanner but via the computer directly.
I then went back to the 1.23.05 bin file, loaded that one in again, and this time on boot up, no Splash Screen! I then continued on, reloaded the public firmware, and checked the Settings Menu and the Set Debug File option was gone.
Thank you for your assistance.
I had 2 SDS 200's with the beta firmware in. Tried the 2nd SDS200, and was able to revert back without an issue. Now, back to the original SDS200. I plugged the scanner in, and deleted the entire firmware file, then Cleared User Data, updated to 1.23.07 via Sentinel and let the scanner load it in. I previously was attempting this with the SD card not in the scanner but via the computer directly.
I then went back to the 1.23.05 bin file, loaded that one in again, and this time on boot up, no Splash Screen! I then continued on, reloaded the public firmware, and checked the Settings Menu and the Set Debug File option was gone.
Thank you for your assistance.
Since the procedure went flawlessly on SDS200 #2, I wasn't going to let SDS200 #1 beat me...LOL! My only thought was a corrupted firmware folder which I deleted, then performed a Clear User Data session, returning the firmware folder. This allowed me to load 1.23.05 again, but this time when it loaded, the Splash Screen and Set Debug option in the settings were removed. Once that was gone, I knew it's smooth sailing. No other explanation, other than it's now back to normal operations.
I was doing some scanning and I came across a frequency, but it was encryption, but I had MOT BP then it flashed RC4 1 Does any one know what that means?
Likely just a bad decode.
The whole problem is that the DMR standard does not describe BP encryption. In the custom firmware, it is shown according to the residual principle: if there is an encryption, but no known encryption is found, then BP is shown.
And known encryptions can sometimes not be detected due to bad signal, so BP is mixed with RC4.
In most cases it means that the signal has RC4 encryption, for Motorola it means EP (Enhanced Privacy). There are special cases when the signal is mimicked by Motorola or OTA or RAS is used. Then it may show that the signal has BP encryption, but in fact it does not. In general, there are a lot of small nuances.
Similar threads
