I have a 6 digit pin enabled on my remix install.... every time I boot up, the very first time I enter the pin it says the pins is incorrect and that I have X many attempts remaining. It doesn't seem to make a difference if I use keyboard or touchscreen to enter the pin. It then works from the second attempt onwards.
It also doesn't seem to matter how long I leave it after booting, it will always reject the first attempt.
Initially I thought it was fat fingers, but it is definitely not that.
Has anyone else come across this issue?
Thanks
Dan
Bump - in the absence of a solution - any trouble shooting advice would be greatly appreciated.
Related
Hi,
Not sure if this has been asked before, but If a pin number or password is set up for the lock screen, this can be bypassed by pressing the home button 5 or 6 times and will then open up the phone without the need to enter the password or pin. A work colleague found this out by accident and was able to access the phone uninhibited. Is this a feature in case of forgotten passwords / pins or is it a bug. Or can it be disabled? as it doesn't seem all that secure
Mine doesnt do that, tried it several times
must be a bug on your phone
Yeah I though that but another work colleague has the same phone and his does it as well. You have to press it quite quickly it seems to go into the voice control when it comes on and then goes on to normal phone use. I have found other references to it googling, but seems to be relating to a fix if you have actually forgotten the password.
We've been having a fiddle , and now having powered off the phones cold and restarting after setting the pin numbers it has stopped doing it. Up untill now after setting the pin code we hadn't actually powered off completely just into standby. SO you presumably must have to reboot the phone after setting the pin number.
Anyway both phones are working and cant replicate the issue, so hopefully sorted.
Thanks
(Sorry for posting this to a general forum, but I figured there's a good chance this issue is not model-specific.)
I noticed some strange behavior (henceforth referred to as "the behavior") on my stock 4.1.2 T-Mobile GN2 lock screen (numeric PIN) recently. Twice, on random occasions, when I pressed the power (right-side edge) button to wake up the phone, before even touching the screen I immediately caught the "Try again in X seconds" in the middle of its countdown on the lock screen, just below the clock. The first time the countdown was at about 1s (almost done), and the second time it was at about 10s. There is no way myself or anyone else had physically tried and failed 5 times. Both times the phone was sitting near me face-up on a table, nothing else touching it, and nobody else around.
The first thing that came to mind was some kind of malware. But if an attacker is already "inside" so to speak, why would they want or need to brute-force the lock screen? And can the lock screen even be seen from "within"? I thought it was only relevant to physical access (on-screen or USB storage).
Does anyone know details about the lock screen mechanism to say what on earth this could be? Google search returns a few similar reports but only in dead-end threads. Even though my device is stock I figured this question may be above and beyond the usual users' forums, so I am hoping the expertise at XDA can help. Thanks in advance.
Here are more details that could be relevant:
- The device works fine otherwise.
- I saw the behavior happen randomly twice in the last 24 hours, and I had rebooted in between. Prior to that I had never seen it. I cannot recreate it at will.
- WiFi and GPS were set to off. The first time the phone was on AC charger (mains, not PC), the second time it was on battery.
- There have been no major changes (that I know of) to my phone. I have not even installed any new apps in the last few weeks.
- When I try failing the lock screen 5 times on purpose, I get the "Try again in X seconds" countdown under the clock AND a popup with OK button saying that I failed. In the behavior, there is no popup, just the "Try again" countdown.
- I do not notice any other suspicious activity like unfamiliar processes or unusual bandwidth usage, although I do not have the tools or know-how to examine individual packets or anything like that.
Sometimes when i use the knock on feature several times in a short time period, it starts to ignore my taps.
When i try to unlock my phone again, it barely recognizes my touch events as follows it gets hard to unlock it.
Mostly i have to restart it.
Do you experience the same or a similiar problem?
Regards
Hi all!
This is my first post, but not for a happy reason.
Briefly, I took my Asus Zenfone 4 screen (broken) to exchange.
The technician (friend that I trust) asked me my unlock pass (PIN) and unlock screen pass too, to restart it for tests. He removed the passwords to work freely. Restarted the phone 2 times, everything ok.
The problem (a bit desperate) is that now, supposedly for no reason, we can't access phone. Says: To start your Android, enter your PIN (Pin, not password, just numbers). Seems like smartphone took a PIN itself.
We tried old PIN few times but says that 3 more attempts and the data will be deleted (!!).
(Note: I had App Lock installed and protected almost all important apps with the same Pin, but I think there's nothing to do with this problem).
The only solution will be reset the system?? Unfortunately I have some files without backup that I can't lose.
There is any original Pin?
Any help is welcomed! Thank you so much!
Hey, thanks for clicking hopefully you can help,
I have a One Plus 5.
Here are the symptoms, screen is just black with a couple flashes of blue sometimes lot of physical damage, trying to get the screen to work is definitely not an option. The phone plugs in and charges and the LED seems to work only when the screen is "off" (should be), the three main buttons seem to work, they vibrate when I press them.
I have tried to follow a couple adb guides on how to enable debugging like this but am having a hard time.
when I type '.\adb devices' it shows an 8 letter device name that is 'unauthorized'.
My guess is that there is something to do with the fact that my USB transfer mode is not file, I can't even access any of my phone's files on my PC.
I have no idea what to do past this point, although I have tried a couple of code pasting which didn't result in much.
Any lead would be appreciated, you guys probably know how important a phone is nowadays, with every authentication and bank payment authorizations done on mobile I am quite lost.
Thank you for any info.
bump
one last bump in desperation