topic PIN wrongly indicated as not correct in XPERIA archive

PIN wrongly indicated as not correct

Nico83 — Tue, 08 Apr 2014 18:45:41 GMT

After the phone crashes and reboots itself (which unfortunately happens quite frequently and randomly) I am mostly (mostly, because sometimes the phone seems to store the PIN during reboot) asked for the PIN of my SIM1 card (SIM1=with PIN, SIM2=without PIN).

Once in a while, if I enter the PIN correctly, the phone keeps telling me that I have entered the wrong PIN and have three attempts left. I can continue to enter the right PIN, and the same screen is shown, with always three attempts left, the counter doesn't decrease.

As soon as I hit the power button shortly to black the screen and hit it again to wake it up again, the PIN screen is gone and the normal swipe-lock screen appears. And after unlocking the status of SIM1 is connected and it works all right; so the phone has received and used the correct PIN in the first place and kept prompting the wrong screen with the PIN-entry.

This is definately a software bug; anybody else has made the same experience?

Re: PIN wrongly indicated as not correct

Alexander1 — Wed, 09 Apr 2014 11:12:07 GMT

Hi,

I haven't hear this before. I would suggest that you try to boot your phone into safe mode to see if the problem may be related to any 3rd party app that you have installed in your phone:

http://talk.sonymobile.com/t5/FAQ/How-to-boot-your-phone-into-safe-mode/m-p/348008#U348008

If the behavior persists in safe mode I would suggest that you try to reinstall the phone software using PC Companion:

http://www.sonymobile.com/update

In PC Companion, press start on Support Zone > Start on Update the phone/tablet software > Press the blue link that says "Repair phone/tablet".

Before repairing the software in your device you may want to backup your information first. Check out this topic for more information on how to:
http://talk.sonymobile.com/t5/FAQ/Backup-amp-Transfer/m-p/407253#U407253

Re: PIN wrongly indicated as not correct

dip14 — Thu, 01 May 2014 16:51:39 GMT

Same thing happened with me...fixed by update leading to new problems...