Me and my wife have been loving our S6es, but after the experience that happened today, I'm now very concerned about this
My young daughter tried to unlock my wife's S6 15 times, and then it started asking for a backup PIN. I figured no big deal, but THEN my wife told me she didn't create one. I was absolutely dumbfounded.
Device Manager would not work and my wife doesn't have a Samsung account, so I had no choice but to call Verizon. They told her to try a certain PIN to see if it worked, but after she tried a couple of times, the phone wiped itself, all her contacts, messages and pictures gone. My wife is distraught now because she had some very meaningful pictures in there, and now she'll never see them again.
I can't believe that Samsung apparently let this bug slip past. I always use a backup PIN on my phone, but this is still very concerning to me as it shows they didn't test the lock method correctly. There was never an option to unlock through Google, either.
This is on 5.1.1, by the way. Did anyone else ever experience this issue? Personally, I've always been a Samsung guy, but I believe I'll be thinking twice about buying any Samsung phone in the future after this incident.
My young daughter tried to unlock my wife's S6 15 times, and then it started asking for a backup PIN. I figured no big deal, but THEN my wife told me she didn't create one. I was absolutely dumbfounded.
Device Manager would not work and my wife doesn't have a Samsung account, so I had no choice but to call Verizon. They told her to try a certain PIN to see if it worked, but after she tried a couple of times, the phone wiped itself, all her contacts, messages and pictures gone. My wife is distraught now because she had some very meaningful pictures in there, and now she'll never see them again.
I can't believe that Samsung apparently let this bug slip past. I always use a backup PIN on my phone, but this is still very concerning to me as it shows they didn't test the lock method correctly. There was never an option to unlock through Google, either.
This is on 5.1.1, by the way. Did anyone else ever experience this issue? Personally, I've always been a Samsung guy, but I believe I'll be thinking twice about buying any Samsung phone in the future after this incident.