just installed 20121222 cm10 att nightly, and found my lock screen changed from 6x6 to 3x3. my code does not now work to unlock the screen. any ideas how i can log back into my phone?
entered a code >40 times in the hope that a google login screen would pop up and allow me to bypass this lockout.
failing that any hope for getting off a single file that i forgot to backup before flashing this rom?
very grateful for help.....
This is a known issue. Before updating it has been advised to remove pattern locks, unfortunately it wasn't detailed in the OTA.
There are only two solutions.
1) Download the following app from the play store. It is 4.20 USD and not a guaranteed solution. Follow the solution in the app's description. https://play.google.com/store/apps/...dium=organic&utm_term=android+lock+bypass+pro
2) Do a factory reset in your recovery mode. This is a guaranteed option, but you will lose your data.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If a proper back up was made before flashing (as recommended,i believe),a factory reset will not take too long to get back to the way you are now
thank you both for taking the time to help. I reset the phone to an earlier backup and swallowed the loss of data.
note to self: backup daily not weekly!
Related
Hi everyone,
I recently updated cyanogenmod10 to 10.1 only to find out that my 5x5 pattern was changed to 3x3! I cannot un-lock my phone not matter what pattern I try. No, the "forgot password" method does not work, I got it wrong 25 times and still not "forgot password?" button. Please help! I have NO backups for some reason. I did but then they were deleted...
Probably going to have to wipe.
HaruSoul said:
Probably going to have to wipe.
Click to expand...
Click to collapse
How can I prevent this problem in the future?
TimeAndroid said:
How can I prevent this problem in the future?
Click to expand...
Click to collapse
It was stated on the official thread that this is a known issue of 10.1. Unfortunately it wasn't detailed in the CM OTA Update. You will have to wipe to restore access to your phone, from what I've read so far. In order to prevent this issue in the future, you will need to remove your pattern lock before updating.
RPelham said:
It was stated on the official thread that this is a known issue of 10.1. Unfortunately it wasn't detailed in the CM OTA Update. You will have to wipe to restore access to your phone, from what I've read so far. In order to prevent this issue in the future, you will need to remove your pattern lock before updating.
Click to expand...
Click to collapse
How do you wipe restore access? Do I use clockwork recovery to do that?
You can try this method if you'd like to regain access without data loss, but it costs 4.20 USD and I not a 100% guarantee for all devices. Follow the directions in the description of the app: https://play.google.com/store/apps/details?id=net.thomascannon.screenlockbypass.pro&hl=en
OR if you don't mind the data loss, boot I to recovery mode (CWM/TWRP/Stock) and select Factory Reset. This will wipe your data and present you with the appearance of a brand new phone when you reboot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hi guys, I've just ran into the same issue. About the Screen Lock Bypass is there a way I can install it without having to choose my device because it doesn't work.
Just a thought - I'm using 01062013 CM10.1 and it appears to support up to 6x6 on the lock screen.
Can you copy that build to your external SD card, boot into recovery mode and flash it?
I recently just wipe did a factory reset on a encrypted (factory encryption) Galaxy S3, after rebooting it i have found that i am unable to get past the initial password prompt screen. I have tried to flash stock ROM, multiple times, to no avail as after each reboot i get the same password prompt screen. i have tried to flash custom ROM, multiple times, this to to no avail as it will not even go onto the device through push in Samsung toolkit v7 or slideloader. i have wiped the ROM to the point of nothing being on the phone and re-installed the factory ROM again this to with not avail as it still has the password screen. Now before i go back to t-mobile and see if they will help me, i decided to get community input to see if there is anything that can be done outside of the Factory as i have void warranty using Samsung Galaxy S3 Toolkit v7.
******UPDATE******* for those with similar problem, i just fixed this. Issue is as follows with possible fix action:
Issue was that encrypting the Samsung Galaxy S3 with the factory encryption and then wiping the system will cause the password file to be deleted but the encryption to stay on the phone. My fix action was that download original ROM from the provider, delete existing ROM on phone till it is basically a brick with USB debugging on and re install the original providers ROM. After it is re install you have to go in and wipe the phone's data one more time. This resulted in the password prompt screen disappearing and the basic start setup being initiated as if you just bought the phone from the store. Although this is my fix and other fixes for future reference would be much appreciated to. *********UPDATE************
zidale said:
I recently just wipe did a factory reset on a encrypted (factory encryption) Galaxy S3, after rebooting it i have found that i am unable to get past the initial password prompt screen. I have tried to flash stock ROM, multiple times, to no avail as after each reboot i get the same password prompt screen. i have tried to flash custom ROM, multiple times, this to to no avail as it will not even go onto the device through push in Samsung toolkit v7 or slideloader. i have wiped the ROM to the point of nothing being on the phone and re-installed the factory ROM again this to with not avail as it still has the password screen. Now before i go back to t-mobile and see if they will help me, i decided to get community input to see if there is anything that can be done outside of the Factory as i have void warranty using Samsung Galaxy S3 Toolkit v7.
******UPDATE******* for those with similar problem, i just fixed this. Issue is as follows with possible fix action:
Issue was that encrypting the Samsung Galaxy S3 with the factory encryption and then wiping the system will cause the password file to be deleted but the encryption to stay on the phone. My fix action was that download original ROM from the provider, delete existing ROM on phone till it is basically a brick with USB debugging on and re install the original providers ROM. After it is re install you have to go in and wipe the phone's data one more time. This resulted in the password prompt screen disappearing and the basic start setup being initiated as if you just bought the phone from the store. Although this is my fix and other fixes for future reference would be much appreciated to. *********UPDATE************
Click to expand...
Click to collapse
When you say you reinstalled the original provider's ROM, I'm not sure if you mean you used ODIN. I believe ODIN install is the only way to recover from this as it reformats the partitions.
An ODIN flash back to OTA did not help my issue.
My company now requires the encrypt device policy for exchange, so I went ahead encrypted the device while running CM10. The encryption succeeded, but every time the screen timed out, it would turn off the device instead of just turn off the screen (CM10 bug?) - didn't want to have to deal with having to cold boot the device every time I want to do something, not to mention the phone being off :/
So I did a nandroid restore to my last known state and now I get prompted for the unencrypt password. However, the password doesn't work. Probably because the password file was deleted, but the system and data partitions are still encrypted.
I've tried doing a full wipe in TWRP and flashing multiple ROMs. I've also tried ODIN flashing root66 and OTA JB 4.1.1 with no success. It still asks for the unencrypt password. I suspect the only way to fix this is to completely re-create the system and data partitions.
If anyone knows how to accomplish this, I'd be grateful because I have a soft brick right now (i.e. can't get past unencrypt password prompt with any ROM)
OMG THANK YOU SO MUCH FOR THIS. I was in the same exact situation you were in and thank god for this thread. I thought my phone was pretty much done for.
fix
BTT8 said:
OMG THANK YOU SO MUCH FOR THIS. I was in the same exact situation you were in and thank god for this thread. I thought my phone was pretty much done for.
Click to expand...
Click to collapse
flash ur rom. then flash CF-Auto-Root, boot to recovery, factory restore, done
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
PriyanPhoenix said:
Three days in with a replacement Pixel C, it has stopped recognising my lockscreen pattern. I know it is correct as I use the same pattern on my phone. Wiping the cache has no effect.
I can't use Android Device Manager to set a new password as it detects that the lock screen is already active.
Is there any option other than a factory reset?
Click to expand...
Click to collapse
In this case, even a factory reset might not help.
Just to confirm, should anyone else have the same issue, a factory reset did solve the problem and the error has not returned. Still no idea what could have caused it though.
Solution
I had this problem also just hold the power button down for like a minute.
I'm having the same problem, was working fine a few hours ago then not recognizing the pattern. I've tried holding the power button but that just powers it off. When I turn it back on it asks for my pattern to power the device back on and it recognizes the pattern then just fine but once it power's up and I try to put the same pattern in to unlock the screen it says wrong pattern!! What the hell is going on here? Any help please?
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
NJ72 said:
This happened to me and Google RMA'd the unit. I had to factory reset it, but if you want to retain the data on it I strongly recommend installing something along the lines of Airdroid so that you can access the file hierarchy remotely even if the device is locked.
Airdroid has its benefits in other areas, however I found it a lifesaver for that one incident which allowed me to pull my files prior to the factory reset.
Click to expand...
Click to collapse
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
1barlog17 said:
Thanks I'll have to check into that app. I already did a factory reset this time and it worked but I'm just curious what caused it and if I should just not use a screen lock on it anymore? So when you say you RMA'd the unit you mean Google swapped the unit out for another one? Or they recommended you to do a factory reset? Thanks again for the advice.
Click to expand...
Click to collapse
Yes, Google sent me a new unit. They didn't advise to do a factory reset, they just advised to return the unit. Part of their RMA process is that they recommend you wipe data (for data protection) so I ended up doing both.
I imagine that there are other apps which would offer access to your device data without unlocking, I just have experience with Airdroid.
I also had this problem, but I was using a pin instead of a pattern. Very concerning to be locked out of your own tablet. Had the tablet for about 3 months before it happened. Factory reset fixed it, hasn't returned since but only time will tell. Doesn't inspire a lot of confidence in the device knowing that maybe you could get locked out at any moment.
The same problem has been found on the Nexus 6p. Lockscreen not unlocking with the correct pin/password, appears to be a problem with the lockscreen as the phone can be booted or decrypted with the correct password.
The suggested fix was to ensure you have prey or another similar program installed. Changing your unlock password remotly via prey fixes the problem allowing you access to your phone.
Just had this problem today. Went to login with the same pattern I've been using for the past 3+ months, and it said "Wrong Pattern" over & over again. I tried to reboot and try again, same story. I used Android Device Manager to lock it & entered a password. Then my Pixel C confirmed that it was locked via the Android Device Manager, but when I went to log in, it asked me for a pattern, not a password! (Bad sign!) And, of course, I entered the right pattern and it told me it was the wrong pattern.
The Google support rep said I had to do a factory data reset. It is indeed disconcerting and frustrating. Next time I'll use Backup!
are you guys rooted? I had this problem on my N5X during rooting and trying to install ROMs. wiping data helped but I simply reset the device anyway. I noticed this also happened on some devices when an incompatible version of SuperSU was installed. If not rooted then you got me.
I am not rooted. I haven't done anything to the tablet except install & use apps and install a p12 certificate (which, I believe, unfortunately, requires you to use some kind of lock screen).
So, I used Android Device Manager to erase my tablet & the problem went away. Yay! I changed to using a PIN instead of a pattern. Now, today, just over a week later, the problem has recurred. <sob!> It says "Wrong PIN" when I try to login, even after powering off & on again, and I am facing the prospect of having to go through all that again.
Just had the same issue, tablet not rooted no developer options unlocked/used just left as factory with apps installed from play store.
Factory reset in progress...
Just happened to me (on the official beta ROM)
This just happened to me today on my Pixel C. I found threads on Google Forums that this has been happening for over a year without a fix.
If your bootloader is unlocked, you can always boot TWRP, Advanced > File Explorer, change to /data/system and delete locksettings.db, locksettings.db-wal and locksettings.db-shm.
Does anybody has an idea here? I'm confronted with this issue: Wrong PIN. No matter how many times i give the correct PIN
restarting Pixel C does not help. Is there any other way to fix this issue?
Shame on Google for this!
farsiray said:
Shame on Google for this!
Click to expand...
Click to collapse
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
bornheim2 said:
Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.
Click to expand...
Click to collapse
Looks you have no clue what you're talking about. Do some more reading before you give a useless comment.
This is an issue with Pixel C since 2016, Google still hasn't fixed it.
https://issuetracker.google.com/issues/62404336
https://productforums.google.com/fo...ce=footer#!msg/nexus/ImQsmQ8-8JA/n-1kqOv9AwAJ
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Willyb211 said:
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Maybe a little late to reply but what did you wipe?
Recommended way to turn phone over to another user is to remove fingerprint(s) and accounts while booted. And make sure the reactivation lock isn't enabled.
You can factory reset after the above.
Maybe you can still factory reset but if that doesn't work, I don't know why it wouldn't unless reactivation lock is enabled.
Did you try the factory reset? Did that work or no?
Edit: if it's just a persistent fingerprint issue, try this but read the whole thread.
https://forum.xda-developers.com/showpost.php?p=63327098&postcount=1
Sent from my SM-N920P using Tapatalk
Willyb211 said:
So I gave my mother my note 4 rooted Ultimate Note7 Hybrid SM-N930P and I wiped everything before I gave it to her. But when setting up her phone it asks for pin number for screen lock so I make one. Then when trying to unlock it it won't allow it. It looks to go to the next screen but flashes then goes back to lock screen.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Flash this zip file from twrp or any custom recovery and it will bypass any lockscreen security lock. pin/pattern/password/fingerprint.
https://mega.nz/#!fQ03xarS!Rmik-8KQSxvnZ9AYFsU_t03RdmjZeqwF-ahnXLQi41s
samep said:
Maybe a little late to reply but what did you wipe?
Recommended way to turn phone over to another user is to remove fingerprint(s) and accounts while booted. And make sure the reactivation lock isn't enabled.
You can factory reset after the above.
Maybe you can still factory reset but if that doesn't work, I don't know why it wouldn't unless reactivation lock is enabled.
Did you try the factory reset? Did that work or no?
Edit: if it's just a persistent fingerprint issue, try this but read the whole thread.
https://forum.xda-developers.com/showpost.php?p=63327098&postcount=1
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I wiped it from recovery mode with the TWRP
It isn't a finger print issue. It's the 4-12 digit pin number
Willyb211 said:
I wiped it from recovery mode with the TWRP
It isn't a finger print issue. It's the 4-12 digit pin number
Click to expand...
Click to collapse
Trying to help so I won't debate the issue. It's important to recall if you went back through setup wizard and were prompted for original user and account password.
I still don't know what partitions you wiped. You likely need to root again if you wiped data or factory reset. I thought a factory reset would remove fingerprints.
The reason I think it's a fingerprint issue is the prompt for pin after reboot. I think that still applies since it asks for one and won't unlock. On initial prompt after you wiped it, did you input your personal backup pin to unlock and set another pin? Original pin should be wiped but if not your accounts and likely prints still exist.
I may be wrong but you may have to restore a stock backup or go back to stock tar in Odin if the two suggestions given aren't helping. I'd suggest the same stock tar as before in case it is factory reset protection causing the issue. You may have use your original Google or Samsung account user and password to unlock it.
But before following through with Odin, one important thing to look for in phone's display is reactivation lock while phone is booted to download mode (for Odin). If enabled, factory reset protection is applied. I wouldn't flash but pull battery and factory reset and sign in with original user and password. The prompts should direct just that. After setup wizard, remove anything of yours like fingerprints and accounts and factory reset within system Settings app.
As I said in my initial reply, you need to remove your accounts and check for fingerprints and remove those if applicable. Then factory reset. I didn't mention it before but factory reset in system Settings app is recommended to avoid issues handing phone to another user. Not sure but it may be a more sanity check to ensure you've removed accounts and fingerprints and encrypted data. I forgot to mention encrypted earlier.
Sent from my SM-N920P using Tapatalk
Hey all,
I have updated by Redmi Note 8 Pro, to 11.0.3 yesterday. The updated stated to be solving some issues with Netflix (although it worked perfectly fine for me).
The issue:
After unlocking the phone, it reboots itself after a few seconds 10-20s, and goes into redmi-recovery 3.0.
Thankfully it is giving me enough time to use google authenticator (I have extremely important auth codes here that I cannot lose).
Edit: Worth mentioning that this happens when the Xiaomi Sim Activation Service is performing its activation.
Edit2: The "unlocking", refers to unlocking the screen by drawing the pattern.
Way forward:
As I don't have a secondary phone with the authentication codes, the option to wipe the system is a no go here.
I have been scouring the forums for any hints etc, but did not come across anything useful for my case.
Do you have any suggestions how this situation could be averted? Any feedback welcome.
Thanks!
khorne55 said:
Hey all,
I have updated by Redmi Note 8 Pro, to 11.0.3 yesterday. The updated stated to be solving some issues with Netflix (although it worked perfectly fine for me).
The issue:
After unlocking the phone, it reboots itself after a few seconds 10-20s, and goes into redmi-recovery 3.0.
Thankfully it is giving me enough time to use google authenticator (I have extremely important auth codes here that I cannot lose).
Edit: Worth mentioning that this happens when the Xiaomi Sim Activation Service is performing its activation.
Way forward:
As I don't have a secondary phone with the authentication codes, the option to wipe the system is a no go here.
I have been scouring the forums for any hints etc, but did not come across anything useful for my case.
Do you have any suggestions how this situation could be averted? Any feedback welcome.
Thanks!
Click to expand...
Click to collapse
Unlocking of the bootloader if I am not mistaking always goes with an automatic wipe of system and I am afraid nothing can be done to avoid this besides of course not unlocking bootloader in the first place.
From what I recall it does not go to recovery by itself when it completes the unlocking procedure, it just reboots to fresh new start of OS.
Sorry if I am bringing some bad news here.
Good luck!
Muad.Dib said:
Unlocking of the bootloader if I am not mistaking always goes with an automatic wipe of system and I am afraid nothing can be done to avoid this besides of course not unlocking bootloader in the first place.
From what I recall it does not go to recovery by itself when it completes the unlocking procedure, it just reboots to fresh new start of OS.
Sorry if I am bringing some bad news here.
Good luck!
Click to expand...
Click to collapse
Thanks for your feedback even though it might not be positive!
> Just to clarify I did not unlock the bootloader, it was a standard OTA update pushed to my phone.
>> By unlocking I mean drawing the pattern on the screen, the phone works fine while "locked", but as soon as I unlock it (draw the pattern), it will restart after 10-20 seconds.
Thanks again.
The issue somehow disappeared on its own.
For people who would experience this in the future (I have no idea if any of those steps fix the issue).
>Since I had a limited amount of time to take all the actions, I performed a sync of all accounts + did a fresh google backup
>Once triggered I quickly locked the phone (This prevented the restarts).
After I completed backing up all my data and was about to wipe the phone, it suddenly started working as usual.
I have no idea if the backups triggered some mechanism or did the mi account sync trigger the SIM Activation Service, but the issue is now gone.