This happened to me before and I spent quite a while googling different ways to fix it with no luck...I had to just wipe and start again. I changed to a pattern lock today whereas normally I go without, however for various reasons I wanted it on. When I have went to change it back to just swipe, its greyed out and says 'disabled by administrator, encryption policy or credential storage'.
I know its not the end of the world but I'm so used to just swiping, so its a bit of a pain. Anyone know how to fix it or will I have to factory reset and start again?
Did you ever figure this out? I just dug up my old p8max and want to use it as a tablet for the kids. Would be nice to not have a pattern, pin, etc...
Related
I've just got the HTC One S from Three in the UK, when I went into the Settings>Security>Screen lock there was no option for face unlock. The only options were none, pattern, pin and password.
I had completely forgotten about this feature, until I was scrolling through the all apps list under Settings> Apps. I saw the settings logo and 'face unlock' but when I tried to find it, it was no where to be seen.
I have rebooted the phone a number of times and done a factory reset as well, but it hasn't made any difference. The only thing I could think, potentially, is it's not connected to the internet yet as I'm still waiting three to unlock it. But then again, I can't see how that would make a difference.
I was wondering if anyone else had come across this issue?
Something strange and unexpected has happened with my Nexus 5... Upon first setting up my device after unlocking it and rooting it, I encrypted the phone before ever adding any of my info or apps to it, full knowing that I would forever have to use a locked screen etc. To side step the annoyance and lack of security that Android has with having the Encrypted boot time password being the exact same as the lockscreen's password I used this app 'Cryptfs Password' to change the boot time password to something much more lengthy and secure, while allowing me to have a standard simplified passcode for simple screen unlocks.
As time went on I found myself in need to wipe the device to troubleshoot an issue I was having with my wifi and wireless tethering no longer functioning properly, I wished to go back to an initial factory state to begin doing restores from Titanium to find the culprit per say and figur eout where I went wrong and borked my ability to toggle wifi.
Upon wiping the phone in TWRP (standard dalvik, cache, and ROM - not system or data) I rebooted and flashed my Titanium Backup.zip and Super USer.zip and then proceeded to set up the device again when I noticed something very odd...
I still needed to enter my previously exact password upon booting the device, however the lock screen no longer any security of any kind!
When I checked in settings this is what I found:
https://i.imgur.com/RR2SFxL.png
Clearly you can see the device is still encrypted however the default "slide" screen lock is now able to be used? Whaaaaat?!?!
Opening the Screen Lock settings menu reveals:
https://i.imgur.com/FtOqUY5.png
I have not yet sleected to change it to a PIN or PASSWORD as I am home and wanted to see if I could gather any other information about this first. I have a feeling that upon changing to a PIN or PASSWORD that I would not be able to change it back again.
Is this a flaw or error of some kind? I do not see any huge security vulnerability, I mean even though this does allow you to bypass the lockscreen, you still need the password at boot to even get into the phone or any Recovery - but this is interesting nonetheless. I was under the impression that it was IMPOSSIBLE to have both device encryption and essential NO LOCK SCREEN?!?!
I have seen threads such as this one: http://forum.xda-developers.com/showthread.php?t=1873700 where it is shown and discussed how to use the pattern lock for example, but this is obviously much different.
Can anyone else replicate this with their own android device?
EDIT:
Was able to find this thread https://groups.google.com/forum/#!topic/android-security-discuss/G4N5pBreyhM
where someone was able to essentially achieve a similar situation by using a 3rd party lock screen....
Hey guys,
Is there an app to track down an errant credential in credential storage?
I used to be able to use Secure Setting and Tasker to turn the pin lock on and off until this week.
The task is running right, but its not removing the pin at home.
After tracking it down I have found that something is adding itself to Credentials and it turning swipe and none screen lock options off.
Clearing the credentials fixes it till the next tasker task to turn the pin back on runs, than i have to remove credentials again.
Thanks
I think I've got it sorted out now. I recently purchased the pro version of Secure Settings and I decided to disable then re-enable the System+ Module. Not sure what happened, but that seems to have cleared it.
Edit: still acting up.
So much for that being the fix.
Just had my phone decide to add that errant credential back in again several times since (this is the earliest I could get back on to update).
Hello,
I think my phone just had a heart attack...
It sounds funny, but not for me. I just don't know how to describe what just happened.
I was just chatting with my sister on WhatsApp, I wasn't doing anything special.
Then, the screen froze, and the phone rebooted.
Recently, I had some "home restarting", sometime once a day, sometimes more, but less since I upgraded to Lineage OS 17.1 (from the previous Lineage OS version).
But this time, it's a full reboot by it's own. Scary...
And the nightmare starts now.
After the boot logo, I arrive on a black screen, asking in English (not my language) for my password... but I never used any password when I start my phone.
So I try my PIN code, the only possibility coming to my mind, and it worked.
Yeah ! It works ! Nope... new black screen in English...
That time, it says that my password is correct, but that unfortunately, my data is corrupt.
I have an inner drop of sweat running on my forehead while reading that...
Then... "To resume using your phone, you need to perform a factory reset. When you set up your phone after reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Only one button : "erase all data", my only option...
I have an inner tear running on cheek while reading that... but what else could I do ? Nothing... so I press the button...
I have a kind of "work in progress" white popup that blinks for half a second, and the phone reboots... on the same password screen !
Next thing to do : the diagnostic of the patient. I power off the phone, then boot in TWRP.
TWRP is in English, not in my language like I set it up a long time ago, and it starts on an unusual screen asking me if I want to keep my system partition in "read only".
It sounds like the patient is in a coma... so I agree on "read only" by pressing the button.
I want to check my data partition, so the most simple way : I choose "install" to go into the "/sdcard"... and it's empty.
Then "up a level" and I go into "/data"... empty... "/system"... empty... "/firmeware"... empty... "/boot"... empty...
Only empty folders, and sometimes empty folders into empty folders.
I go back in the functionalities to go into "partition mounting", and I choose all partitions... but "Data" can't be selected, no matter how much I do the heart massage.
I go back to check in the mounted folders... more empty folders...
So... does anyone have an idea about how to solve such a problem ?
Is there anything to do, or does it look like a DNR wish from an old phone which had a great life and tells me it's time to let it go ?
You have a chance to check if someone made a cruel joke by providing you with a script that did the rest with your unconscious approval, or if it is a hardware failure.
Just install the original ROM, do not unlock the bootloader and use the OPO for a long time and watch the device behavior.
.
.
You saved my day (literally, as you answered during the same day). Thank you.
I hoped to have something without data lost, but as I can use my phone again, it's already a good thing.
I guess you are right : a script that did the rest with your unconscious approval.
When I think about it, as OnePlus system images are not validated by Google, they are not DRM Widevine L1.
So I installed Disney+ from another source... and I guess I got it there.
The good thing is that the market place now sees my phone as already having Disney+ and I can install it (or maybe it's the update from November 19th).
For those having the problem, I followed those steps :
I did the installation process, except that I didn't do the factory reset / data formatting, in the (vain) hope to recover my data.
Apply all the stuffs : Lineage OS nightly-bacon-signed, open_gapps-arm nano, magisk.
Restart the phone : again, the black screens, but this time it reboots to erase everything... it took a very long time.
The phone restarts by itself and I go throw the setting process like for new phones.
It restores what it can restore... some settings of the OS to find back to tweak them...
I can't unlock my phone with the Pattern I assigned it. I always use the same Pattern, so I was pretty sure it's not an error. When I draw the pattern, it says "incorrect pattern" and makes me wait 30 seconds before trying again (from the first try).
Luckily, I have access to Samsung's Find my Mobile, I unlocked the device, removed the lock. But every time I restart the device, the bugged lock screen would come back, and I would have to unlock the device again with Find my Mobile.
please note that I can't set a new lock after unlocking the device, it will revert back to no lock after setting a new pattern/pin/password. definitely a bug.
if there is any method to fix this, or to reset Samsung's lock screen app, please let me know!
my device is Samsung Galaxy A8+ in case anyone was curious.
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
blackhawk said:
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
Click to expand...
Click to collapse
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
majdcomp said:
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
Click to expand...
Click to collapse
Oh my bad, it locks no matter what. That's not good.
Boot menu>clear system cache (don't hit factory reset by accident).
Google for the button sequence to hit for that model. Timing is critical, you might need to try more then once.
That might get it.
Try clearing the Dynamic Lock Screen data.
I would backup all critical data now if you haven't. Do not use Smart Switch to transfer settings if you do factory reset, ha-ha.
Someone here probably has a better solution as I know little about this system.
As always do a Google search, you can probably use solutions from other Samsung models going back a few years.
Erratic and strange behavior can also be a sign of a virus, rootkit etc.
When in doubt, factory reset especially if you can't track down the root cause.
Finding the root cause and correcting it is always preferable to a factory reset but not always possible. If the OS load is older then a year a factory reset be a good plan anyway... nothing like a clean, fresh OS.
Delete your Google account before you factory reset so that doesn't password pester you. I'm told if you reset from settings vs the boot menu that doesn't happen. Not sure haven't tried a factory reset that way.
sammiev said:
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
Click to expand...
Click to collapse
Can you do that on a stock Android that's not rooted?
blackhawk said:
Can you do that on a stock Android that's not rooted?
Click to expand...
Click to collapse
You would need to be rooted.
sammiev said:
You would need to be rooted.
Click to expand...
Click to collapse
I read if you load TWRP you'll lose things like Samsung Pay.
Seems risky at least to me. I like to play with it but don't have a phone to burn.
A factory reset for me at this point is fairly painless ie no data loss and takes under a couple hours.
If it's of any interest here:
On Android the pattern lock data (SHA-encrypted) is kept in a file named gesture.key and stored in the /data/system folder.
If phone's Android is rooted you simply delete that file to bypass the pattern lock. Using ADB you would run command sequence
Code:
adb devices
adb shell "rm -f /data/system/gesture.key"
to achieve this.
The phone should be now accessible with no pattern lock applied.