Related
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Flash factory images?
Sent from my Nexus 6 using Tapatalk
Will this mess up TWRP?
DRatJr said:
Will this mess up TWRP?
Click to expand...
Click to collapse
does it matter? it takes 10-15 seconds to flash twrp, or reflash. but anyways i have a feeling that itll ask again, i hope not.
Yea. I would fastboot erase and reflash everything. If bootloader is locked you are hosed.
DRatJr said:
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Click to expand...
Click to collapse
Contact the previous owner for his unlocking gesture or code/pin and Gmail account, then factory reset and login with his account and when done delete this accoubt in /settings/accounts/. Then data factory reset again and it should be fixed imo. Or send your phone to the prev. owner so he can do it himself. Look here too http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504.
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
DRatJr said:
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
Click to expand...
Click to collapse
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
gee2012 said:
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
Click to expand...
Click to collapse
Oh sorry :/ haha. Wasn't sure if it seemed that way. But nah this has been my baby since unboxing lol
Today a scenario popped up and I quickly set up a 4 digit PIN code and pressed enter. As is on stock Lollipop 5.1, I'm required to enter password twice to confirm. So I did (and as far as I could tell, it was four digits, from a quick glance), but then when I wanted to unlock, it wouldn't, typing in the same passcode that I thought I'd typed in (and the one I used previously when it had a screen lock, disabled it in June). I've tried to brute force my way through, up to almost 300 attempts, but no luck. There's no forgot password option, at least not in plain sight, and Android device manager was no help (it locked the phone, but I could press home and I'd just be back at the lock screen). ADB is disabled. PC doesn't recognize phone. Does anyone know of secret tricks or programs that can brute force through for me? Thanks!
Do you have your bootloader unlocked and a custom recovery? As long as you didn't enable encryption with this code, you should be able to use recovery to backup files from your phone... However there is no way for you to get into your phone without the code. So after backing up, you would need to factory reset it. As far as brute forcing goes there is no way for you to do it. You would have to enter every combinaton that exists manually. That would take forever... So factory reset is your best option.
Sent from my XT1095 using Tapatalk
AGISCI said:
Do you have your bootloader unlocked and a custom recovery? As long as you didn't enable encryption with this code, you should be able to use recovery to backup files from your phone... However there is no way for you to get into your phone without the code. So after backing up, you would need to factory reset it. As far as brute forcing goes there is no way for you to do it. You would have to enter every combinaton that exists manually. That would take forever... So factory reset is your best option.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
No custom recovery. Encryption isn't on. Is there an app or hidden Google solution for this? (I'm in denial right now, ha)
AB__CD said:
No custom recovery. Encryption isn't on. Is there an app or hidden Google solution for this? (I'm in denial right now, ha)
Click to expand...
Click to collapse
You said no custom recovery... but you didn't say if your bootloader is unlocked or not. If it's unlocked, you are in luck and can flash a custom recovery, then backup your files. If it's locked... No choice but to factory reset.
Sent from my XT1095 using Tapatalk
AB__CD said:
Today a scenario popped up and I quickly set up a 4 digit PIN code and pressed enter. As is on stock Lollipop 5.1, I'm required to enter password twice to confirm. So I did (and as far as I could tell, it was four digits, from a quick glance), but then when I wanted to unlock, it wouldn't, typing in the same passcode that I thought I'd typed in (and the one I used previously when it had a screen lock, disabled it in June). I've tried to brute force my way through, up to almost 300 attempts, but no luck. There's no forgot password option, at least not in plain sight, and Android device manager was no help (it locked the phone, but I could press home and I'd just be back at the lock screen). ADB is disabled. PC doesn't recognize phone. Does anyone know of secret tricks or programs that can brute force through for me? Thanks!
Click to expand...
Click to collapse
Sounds suspicious... You did enter the 4 digit pin, but cant get it unlocked with those code? Is that your own phone or others? Sorry, but your case is very strange...
Sent from my XT1095 using Tapatalk
bimasakti85 said:
Sounds suspicious... You did enter the 4 digit pin, but cant get it unlocked with those code? Is that your own phone or others? Sorry, but your case is very strange...
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Absolutely is my phone. I entered it so quickly i may have mistyped it. And no, bootloader is locked.
Normally there is an option to put in your Google email and password if you forget your password
chapelfreak said:
Normally there is an option to put in your Google email and password if you forget your password
Click to expand...
Click to collapse
Not there in Lollipop. Apparently they took it out. Because it only shows emergency call, below the numbers where it used to be in KitKat, and the dialog box that prompts you every 5 failures will only warn you and have an OK button.
AB__CD said:
Not there in Lollipop. Apparently they took it out. Because it only shows emergency call, below the numbers where it used to be in KitKat, and the dialog box that prompts you every 5 failures will only warn you and have an OK button.
Click to expand...
Click to collapse
That's stupid of Google to do that. I guess I would do a nandroid backup and factory reset if I forgot mine.
chapelfreak said:
That's stupid of Google to do that. I guess I would do a nandroid backup and factory reset if I forgot mine.
Click to expand...
Click to collapse
Yeah it's absolutely idiotic. Wish they'd do something about it.
Sent from my XT1092 using Tapatalk
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.
koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems
Hello all,
I'm in a bit of a predicament. I have an old OnePlus 3t that I have not used for years. The device contains extremely important business information that I need to recover. However, I cannot for the life of my remember my lock screen pattern to boot the device. I tried to remember the password and have now triggered the messaging of "This device will be wiped after 8 more tries."
I haven't updated the phone in years, so it would be on an old version of Android. Is there any toolset that could remove this lockscreen and allow the device to boot?
async-mesh said:
Hello all,
I'm in a bit of a predicament. I have an old OnePlus 3t that I have not used for years. The device contains extremely important business information that I need to recover. However, I cannot for the life of my remember my lock screen pattern to boot the device. I tried to remember the password and have now triggered the messaging of "This device will be wiped after 8 more tries."
I haven't updated the phone in years, so it would be on an old version of Android. Is there any toolset that could remove this lockscreen and allow the device to boot?
Click to expand...
Click to collapse
If you:
1. Have unlocked the bootloader, AND
2. Do NOT have an on-boot password set (a lock screen password is ok)
then it is possible to remove the lock screen password.
So, do you meet this requirement? If you do, then do you have TWRP installed?
Screenshot showing on-boot password request:
Sent from my OnePlus3T using XDA Labs
BillGoss said:
If you:
1. Have unlocked the bootloader, AND
2. Do NOT have an on-boot password set (a lock screen password is ok)
then it is possible to remove the lock screen password.
So, do you meet this requirement? If you do, then do you have TWRP installed?
Screenshot showing on-boot password request:
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I thought my bootloader was unlocked, but I cannot completely remember. When I boot the phone with volume down and power, I see a OnePlus branded screen that is also asking me to swipe the password pattern. I assume this means the bootloader is not unlocked, right? If I try to enter the password on this screen, will it use up the twies that trigger the wiping of my phone?
async-mesh said:
I thought my bootloader was unlocked, but I cannot completely remember. When I boot the phone with volume down and power, I see a OnePlus branded screen that is also asking me to swipe the password pattern. I assume this means the bootloader is not unlocked, right? If I try to enter the password on this screen, will it use up the twies that trigger the wiping of my phone?
Click to expand...
Click to collapse
Power+Vol down takes you to recovery. The fact that it's asking you for a password tells you that the phone is encrypted and has an on-boot password.
So, unfortunately you're not going to be able to recover the data on your phone.
Sent from my OnePlus3T using XDA Labs
async-mesh said:
I thought my bootloader was unlocked, but I cannot completely remember.
Click to expand...
Click to collapse
If your bootloader is unlocked, you will always see the unlocked bootloader warning screen when you power on or reboot (before it goes to any other screens.
If you do not see that bootloader unlocked warning screen, the bootloader is locked.
redpoint73 said:
If your bootloader is unlocked, you will always see the unlocked bootloader warning screen when you power on or reboot (before it goes to any other screens.
If you do not see that bootloader unlocked warning screen, the bootloader is locked.
Click to expand...
Click to collapse
It is definitely locked then..
Is there any known exploit that might be available for the device? It is older and has not been updated in years... Even if there were a way to keep trying patterns without triggering the device wipe, that would be hugely beneficial.
async-mesh said:
It is definitely locked then..
Is there any known exploit that might be available for the device? It is older and has not been updated in years...
Click to expand...
Click to collapse
The security features and encryption are very secure. You won't be able to exploit these, to extract your data. They do this on purpose, otherwise it would defeat the whole purpose of data security in the first place.
If the data was important to you; you should have been backing it up. Many easy and free options available to back up your data. I'm always surprised how many folks don't take advantage of any of those backup options. Then they come scrambling over to xda once a disaster has struck, asking for ways to retrieve their data. By that time, it's too late. Don't wait until after the car has crashed, to put your seatbelt on!
If your device is rooted and had twrp, I got a file to flash and it cleans the pattern or password, it safe my life, many times. So let me know. To upload the file.
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
baleskoil said:
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
Click to expand...
Click to collapse
Did you find a solution?
Nope
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
baleskoil said:
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
Click to expand...
Click to collapse
As of right now me and you are the only two that seem to have this issue.when I get home from work I'm going to go ahead and I'm actually going to relock my bootloader and and do everything and then I'm going to unlock it and see what happens.I can let you know in this thread if it works for me and that way you don't have to waste your time unlocking and relocking
Yes please
i would say lock and unlock again and just install everything again
baleskoil said:
Yes please
Click to expand...
Click to collapse
So i locked the bootloader ,then unlocked it and did a fresh install of 11 and i have face unlock back
Good .
I need to reflash the Factory image before relocking right ?
To be safe
baleskoil said:
Good .
I need to reflash the Factory image before relocking right ?
To be safe
Click to expand...
Click to collapse
I locked the bootloader then rebooted back into the boot loader and unlocked it and then flashed
Works for me too.
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
neo_lithic3K said:
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
Click to expand...
Click to collapse
I tried that and it's a no go. Looks like bootloader is the way for now.
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
seipersei said:
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
Click to expand...
Click to collapse
I had the exact same problem as you. face unlock became unreliable after the Android 11 upgrade, so I deleted face data and tried to set up again. It keeps saying 'fit face into frame' no matter the angle or the lighting. Did a factory reset and no improvement. I have never rooted or unlocked the bootloader on this phone. I informed google support and they are sending me a replacement.
Just to share an experience with the community: After android 11 update I was having glitches with face unlock. (Totally stock, no root & all latest ota) This got worse until it wouldn't work at all. Deleting face & starting over didn't work as it just refused to even acknowledge trying to register anything. Then the auto brightness starting flicking up and down and finally half the screen disappeared under green flickering. A factory hard reset made no difference. I even did it twice but the welcome screen on rebooting was still covered in green flickering. Searching for a new phone reluctantly. I picked up my pixel 4xl again to see if I could think of a way of selling it for any purpose & it was fine! Set up & reinstalled a backup & everything including face unlock works perfectly like new. What was all that about!?
Can you describe full algorithm for noob, please?
Stiil don`t working
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
I've done relocking bootloader, but it didn`t help, face unlock still not working, OC is stock, latest.
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
kingkong0821 said:
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
Click to expand...
Click to collapse
This is a known problem, and so far Google has not fixed it. Unsure if they ever will.
Sent from my Pixel 4 XL using Tapatalk