I haven't check the DTEK app in a while, didn't receive any notifications, but today I noticed that the integrity of the operating system is compromised.
Any ideas? Is this a false alarm? Should I reinstall the app?
I actually wish it had happened to me on any of my BlackBerry Android devices. I would have liked to try to diagnose it.
The general consensus was that it was a false alarm due to a problem with the app. It was fixed when an updated version of DTEK was pushed through Google Play. Hopefully it's the same thing this time.
Perhaps those reading this forum post can do a quick check of their DTEK app to see what it says?
The general consensus was that it was a false alarm due to a problem with the app. It was fixed when an updated version of DTEK was pushed through Google Play. Hopefully it's the same thing this time.
Perhaps those reading this forum post can do a quick check of their DTEK app to see what it says?
Mine is still listed as 'Excellent'. I did have the compromised issue on my Priv, though, quite some time ago. Was able to resolve the issue by a downgrade, an upgrade and a reboot.
Mine is still listed as 'Excellent'. I did have the compromised issue on my Priv, though, quite some time ago. Was able to resolve the issue by a downgrade, an upgrade and a reboot.
Posted via CB10
Yeah, I tried that with the PRIV at the time, but it didn't work. As soon as BlackBerry released the updated app, the issue went away.
If I recall, unfortunately, in some cases only reloading the OS fixed the issue for some users. Dtek needs to be more detailed in suggesting what the problem is.
If I recall, unfortunately, in some cases only reloading the OS fixed the issue for some users. Dtek needs to be more detailed in suggesting what the problem is.
But it's really not possible since DTEK just does an overall checksum with the system files. Anything more complex would take far too much CPU.
I had this "thing" a while back while im checking the build date of my keyone via *#2886#, I tried some test in that menu that ended up having os compromised, fixed after factory reset of device, worked for me.
I had this "thing" a while back while im checking the build date of my keyone via *#2886#, I tried some test in that menu that ended up having os compromised, fixed after factory reset of device, worked for me.
Me too, it happened the exact same thing after i checked my build date. DTEK was saying the device was compromise but I'm too lazy to reconfigure everything again after i just set up my replaced Keyone!
I had this "thing" a while back while im checking the build date of my keyone via *#2886#, I tried some test in that menu that ended up having os compromised, fixed after factory reset of device, worked for me.
Hmmmmm.... I did that check a couple of weeks ago too, just to see the build date. I didn't check DTEK after that, but.... maybe that's what caused the issue.
But it's really not possible since DTEK just does an overall checksum with the system files. Anything more complex would take far too much CPU.
Then someone should tell us what kind of THING can compromise the system files. They are not as incorruptible as the Boot Loader stuff??? (notice my highly precise techno lingo!!!)
Hmmmmm.... I did that check a couple of weeks ago too, just to see the build date. I didn't check DTEK after that, but.... maybe that's what caused the issue.
I did that check last week (when it became popular) and I just ran Dtek - I'm still in the not great but not compromised OS. Not great because it wants more encryption and I have not give it Contact permissions.
Then someone should tell us what kind of THING can compromise the system files. They are not as incorruptible as the Boot Loader stuff??? (notice my highly precise techno lingo!!!)
Nothing is supposed to compromise system files, hence the advice to do a factory reset asap.