{"id":4354,"date":"2014-12-04T10:00:18","date_gmt":"2014-12-04T15:00:18","guid":{"rendered":"http:\/\/me-en.kaspersky.com\/blog\/?p=4354"},"modified":"2020-02-26T18:59:22","modified_gmt":"2020-02-26T14:59:22","slug":"pin-vs-secret-code","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/pin-vs-secret-code\/4354\/","title":{"rendered":"Kaspersky Internet Security for Android: Secret Code vs. PIN"},"content":{"rendered":"

Today, we are returning to our favorite topic of mobile solutions<\/a>, or more accurately, the uninstallation procedure. There have been a number of inquiries on our corporate forum describing the following issue: a user, acting in accordance with the proper instructions<\/a>, deletes our product, enters the secret code and then \u2014 wham! \u2014 his or her phone is blocked!<\/p>\n

Moreover, it requires some PIN code. Understandably, the user sees an apparent correlation between this necessary \u2018PIN\u2019 and the Kaspersky product that they have just uninstalled, and then s\/he attempts to enter the secret code again. But it won\u2019t work. Perhaps the user thinks that they might have entered it incorrectly, and so they try to re-enter the secret code<\/a> \u2014 again, with no success.<\/p>\n

The root of the problem in this case is misinterpretation. In actuality, our product is no longer installed on the device as it was successfully deleted. This means that it is no longer responsible for protecting the device, and the lock screen has absolutely no relation to Kaspersky for Android. This is easy to understand by just looking at the buttons on the screen. The window that pops up, requesting the secret code, looks like this:<\/p>\n

\"secret-code-EN\"<\/a><\/p>\n

The design of the window corresponds to the overall design of the product and the buttons have only numbers on them. What is problematic for users might look like this:<\/p>\n

\"pin-kisfa\"<\/a><\/p>\n

In other words, it is a standard phone keyboard with numbers and characters with the regular wallpaper that is installed on the phone screen. One important detail should be taken into account when differentiating the two screens: in the first case, it is our product that requires the secret code<\/strong>; in the second case it is the device, which requires the PIN<\/strong>.<\/p>\n

So what does this all boil down to? In the majority of cases, the entire situation likely has to do with some encryption software being installed on the device. Say you purchased a license key to our antivirus solution, installed Kaspersky Internet Security for Android, and then your security officers at work suggested that you also install, for example, KNOX.<\/p>\n

The problem here is that our apps are not compatible with such programs. If you installed the encryption software prior to our product, our antivirus will notify you upon installation and ask that you delete that incompatible software. However, such notifications do not work in the opposite direction. It is likely that you will not know about this incompatibility issue in the first place, unless you delete our antivirus.<\/p>\n

That\u2019s essentially why it happens the way that it does. Upon activation of the Anti-Theft function, you must enter a secret code. Having encrypted the device again, with a newly installed encryption app, you will have a second password for your system, which will be responsible for system boots and home screen launches.<\/p>\n

The last time Kaspersky Internet Security for Android will request the secret code is upon confirming uninstallation.<\/div>\n

The last time Kaspersky Internet Security for Android will request the secret code is upon confirming uninstallation. After that, the product is removed and will stop working. Normally the system will stop asking for passwords and will reset those that were used before. However, this is not possible on encrypted devices \u2014 which is the source of the problem with a lock-up where you are required to enter your PIN.<\/p>\n

So, what is the solution to this problem? There is a chance that you might be able to get into your phone by simply pressing Enter on the keyboard without entering any numbers. In some cases, the password to unlock the system is empty. If this does not work then the only other thing that you can do is what we call a \u2018hard reset\u2019 \u2014 resetting the device to its initial state.<\/p>\n

Installing an additional #antivirus onto your device won\u2019t make it safer, but instead it could lead to a major headache<\/p>Tweet<\/a><\/blockquote>\n

Once this process is done, you will then have to press a combination of buttons (depending on the model of the smartphone). This will erase all of the data stored on your device, including photos, contact lists and multimedia files. This is a very unfortunate occurrence, so we hope that you do not end up in this situation. To be on the safe side, we suggest that you regularly back up the data on your smartphone so that you will be able to retrieve your valuable content.<\/p>\n

In closing, there is one idea that we should reinforce: installing additional antivirus solutions onto your device won\u2019t make it safer, but instead it could lead to a major headache. The secret code for your Anti-Theft tool is reliable enough to keep your data well protected.<\/p>\n","protected":false},"excerpt":{"rendered":"

We have seen a number of cases where a user has deleted our product for Android and ended up with a locked device. Here we discuss why this happens and what can be done about it. <\/p>\n","protected":false},"author":208,"featured_media":4355,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7,1486,9],"tags":[105,1062,2804,853,426,97,45,49],"class_list":{"0":"post-4354","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-products","8":"category-threats","9":"category-tips","10":"tag-android","11":"tag-antivirus","12":"tag-kaspersky-for-android","13":"tag-kaspersky-internet-security-md","14":"tag-mobile-devices","15":"tag-security-2","16":"tag-smartphones","17":"tag-tablets"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/pin-vs-secret-code\/4354\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/pin-vs-secret-code\/4424\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/pin-vs-secret-code\/4894\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/pin-vs-secret-code\/5164\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/pin-vs-secret-code\/4994\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/pin-vs-secret-code\/6327\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/pin-vs-secret-code\/6921\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/pin-vs-secret-code\/5734\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/pin-vs-secret-code\/6327\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/pin-vs-secret-code\/6921\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/pin-vs-secret-code\/6921\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/android\/","name":"Android"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4354","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/208"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=4354"}],"version-history":[{"count":3,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4354\/revisions"}],"predecessor-version":[{"id":15956,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4354\/revisions\/15956"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/4355"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=4354"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=4354"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=4354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}