I was out shopping in sunny MK and something weird happened to my phone. I took it out of my pocket to check something and the screen was on the emergency pin screen, like i had tried 5 attempts to unlock the phone and failed. I entered my pin as normal, and did what i needed to, but the next time i unlocked the phone, the complete knock code/security had vanished off the phone and the it was set to swipe unlock?
Ive put the knock code security back on, but is this something that has happened to anyone before? is it something i should be worried about.
cheers
Ray
It happens anytime you try 5 times and fail. Once you put your security code in you have to reset it.
sent from my rooted lg g3 locked to tmobile
Related
Hello,
first of all I want to say hello to this active community. I have been a reader for a long time.
today I have experienced a strange bug with still persist. I am running a Samsung Galaxy Nexus and recently change the screen lock from pattern to PIN.
Today I have unlocked the screen via PIN multiple times, but now the PIN is suddenly not working.
I called Samsung support and they told me to send the phone to them. They think it is a bug since I can enter the PIN unlimited times and the phone does NOT get blocked.
Is there a way to do a reset? What can i do? I am a bit helpless at the moment.
I have read that a hard reset/ wipe does not overwrite the PIN. Whats my best bet to access the phone again?
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.
Did you unlocked bootloader before root ?
Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.
I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.
I was wondering if anyone else is experiencing the following issue, perhaps it's related to https://forum.xda-developers.com/mi-9-se/help/ghost-touch-mi-9-se-t3953616 ?
Sometimes, when trying to unlock the phone from the lock screen, it will not register my touches. Or perhaps more likely, only register them partly.
First I need to swipe up to get to the unlock pattern. This step will sometimes not work at all, or sometimes swipe up a bit.
If I get past the first step and get to the pattern screen, it will no let me draw the pattern. It might recognize one of the points you're supposed to touch to draw the pattern, or it might just vibrate whenever it's touch.
Waiting a while, or furiously cleaning the screen will sometimes work, sometimes not.
Did a factory reset, but the problem came back after a few days. Sent to service (purchased from eGlobalCentral). Did another factory reset before sending it in, but they couldn't reproduce it of course, even though I gave instructions that it was intermittent and needed to be used daily for a few days after factory reset.
Wasted around $60 on this.
No touch issues when I finally manage to unlock it.
Anyone had similar issues?
Lately my phone has not been accepting my fingerprint every time to unlock it, so earlier today I went to scan a new fingerprint and discovered my PIN no longer works.
I've tried opening a couple things that require the PIN as well as locking the phone, but despite being the same PIN that's been working for ages, today it is no longer accepted.
I'm reluctant to restart the phone as it requires a PIN after a restart, but I'd like to get this fixed, ideally without a factory reset. As is, I can't get to any security settings and when the fingerprint is not recognized cannot open many apps. Anyone experienced this? Found some threads about the S8 having this issue, but not the Note 10+.
Thanks.
Take it to the FBI. Otherwise, you're probably have to do a factory reset.
Sent from my SM-N976V using Tapatalk
naiku said:
Lately my phone has not been accepting my fingerprint every time to unlock it, so earlier today I went to scan a new fingerprint and discovered my PIN no longer works.
I've tried opening a couple things that require the PIN as well as locking the phone, but despite being the same PIN that's been working for ages, today it is no longer accepted.
I'm reluctant to restart the phone as it requires a PIN after a restart, but I'd like to get this fixed, ideally without a factory reset. As is, I can't get to any security settings and when the fingerprint is not recognized cannot open many apps. Anyone experienced this? Found some threads about the S8 having this issue, but not the Note 10+.
Thanks.
Click to expand...
Click to collapse
So, you can unlock the phone, and some apps can not be opened? Or, you have no lockscreen, but only apps require pin or fingerprint?
winol said:
So, you can unlock the phone, and some apps can not be opened? Or, you have no lockscreen, but only apps require pin or fingerprint?
Click to expand...
Click to collapse
I can unlock via fingerprint, but say if I want to add a new fingerprint, it asks for the PIN first, entering the PIN that previously worked now no longer works.
Similarly, was trying to unlock an app via fingerprint which wasn't being recognized, so the phone then switched to requiring a PIN and failed to accept it.
If i were to restart and it says "PIN required after restart" then I'd be potentiality screwed if it won't accept the PIN.
Randomly, after doing nothing and the phone sitting on my desk, it's all of a sudden working again. No idea if it will remain working or decide the PIN is incorrect again though.
What I'd do then is turn off all the security, if it lets you then set up security again.
If you are feeling daring, kill all the security, do a factory reset and then set up again...
Might be a corrupt file that is causing issues...