Who knows? (Hint: nobody, unless you're religious.) But generally, no.
The only proven safe "encryption" is a one-time pad but that's very impractical... I'm going to save you the long, technical story.
You have probably heard of some real world encryption algorithms: RSA, AES, RC4, etc. The thing is that we do not know whether any of these are secure, we only know that they've been around for a long time and not yet broken despite many, many attempts. Well, cross out RC4 in the list of safe ones: cryptanalysts' relationship status with RC4 is "it's complicated".
Let's take AES. It translates bits of data into other data. You put "CAT" in, give it key "4ZD" and "YYR" comes out. You give it "YYR", provide key "4ZD" and "CAT" comes out. Of course there is more to it than that, but that's the idea.
If AES was completely secure, you would need to try all options (in this case AAA through ZZZ and 000 through 999) in order to find that "4ZD" is the correct encryption key. There are however attacks by which you can find a small bit, for example you can learn that one of the key characters is a digit but you don't know which digit in which position. Still many possibilities to try.
But this is the best we've been able to do in the 16 years that AES exists. It seems unlikely that it will ever be fully broken. There are however security features in AES against things that went wrong in older encryption algorithms:
It is, so far as we know, secure against known plaintext attacks. This means that given "CAT" and "YYR", you cannot learn that the key is "4ZD". Why is this useful? Well consider websites: many webpages contain English words. If you intercept https data and run it against an English dictionary, one of the keys that you get would be the correct one for the rest of the webpage. But as I said, this is not possible with AES.
AES is, so far as we know, also secure against chosen plaintext attacks. If you are allowed to choose what is going to be encrypted and are then able to see the encryption, you can still not determine the encryption key, thereby still being unable to decrypt the rest of the data. An example is a little more complicated but if you want I can try to explain it without getting too technical.
When using similar but not identical passwords, such as
P@ssw0rd1, the encryption result is completely and unpredictably different. Or given similar but not identical texts, it would also be completely different. I think you can see where this is useful.
So things like guessing the password character for character are not possible. You'd need to get the whole password correct at once. The average number of attempts this takes is
sqrt(2^password_security_in_bits). Take it from me that with AES-128, this is impossibly long. (Of course 4ZD is not a realistic password.)
And there are many more of these common attacks, all of which our modern encryption algorithms try to protect against. The only way to break this encryption is circumvent it (as far as we know). It might be that the police in your fiction series previously installed a keylogger to record the password from the suspect. It might be that they have a camera recording where the suspect enters his password. Or he might have used a super weak password that was hackable in seconds.
Other than that, it's pretty much bullshit.