If anyone can help that would be awesome - this is the first time i have encountered this problem on an android device.
one of the first things i do is remove encryption on my android phones because
1. i like the option
and 2. i notice a considerable amount of difference.
now starting from Pie we have metadata encryption with file encryption
removing metadata encryption causes 0 problems.
however when i remove file encryption i run into a problem
i am un-able to setup a fingerprint (the option isnt even there anymore)
also when i set up a PIN, i am unable to change it (it says incorrect pin)
when i use the pin to unlock the phone, it says "wrong pin" but it works in unlocking the phone.
i didnt experience this on my oneplus 5/6 or samsung / huawei devices having them decrypted.
does anyone know how we can get fingerprint / pin working without encryption?
i notice the phone is more responsive and snappy without encryption
Related
If you use device encryption, do you then have to enter a password each time you turn the screen on, or only each time you power the phone on after it had been powered down?
And can you later decide to undo the encryption?
After further searching, I've discovered that the device-encryption password is only entered when the device powers up (reboots). However, the UI forces the same password to be used for the unlock screen as for the device encryption, so it's just as though the device-encryption password has to be used for each unlock. (There are hacks to work around that restriction, but they require rooting.)
New question for anyone using device encryption, please: Are you still able to set a long delay (up to one hour) before the lock screen engages, or does it always engage immediately when the device is encrypted, requiring password entry each time you pick up the phone?
Also, still wondering if anyone who's tried it knows whether device encryption can later be reversed/disabled. If so, I'll just go ahead and experiment. But I'd rather not do so if I'd have to factory-reset in order to undo it.
I is it possible to use the fingerprint reader to unlock the phone with encryption turned on?
I would like to setup Tasker to force a reboot after 3 failed login attempts, thus forcing encryption on and the use of a strong password. But, if I have to use a strong password to unlock the phone every time I use it, I don't want to turn on encryption.
gscrypt can be used (root required) to setup different passwords to unlock vs. decrypt. Is there something similar for enabling the fingerprint sensor?
Hey guys,
I have always had my op3 encrypted and I've become used to always entering the pin when booting up, accessing twrp etc. but today when I rebooted into twrp I didn't have to enter any pin to use twrp. When booting up the system I didn't have to enter a pin either.
When I check the settings under Security & Fingerprint it looks as in the attached screenshot, I don't have any options to decrypt or anything either
I'm running OOS 4.1.3, FrancoKernel #23 , Magisk 12, twrp-3.1.0-x_blu_spark_v27.
Is this something that anyone has experienced and know how to fix?
I want to keep my encryption but then, of course, you should have to use the pin.
Cheers!
Then the pin is defaulted and thus you don't need any. I don't need one, too and never did, but all is encrypted (Even locked down with a pin on bootup and fingerprint otherwise)
I believe this is an option you need to setup during the wizard when you initially set up the device. It asks you whether you want to require a pin on startup or not.
But, you can also turn this on by going to settings>security>screen lock.
From there, you click on the area where it says PIN. Confirm your pin, then click PIN again, and there should be an option to require pin for startup. Other than that, you are still encrypted, but it is all bypassed in order for quicker startup.
Sent from my ONEPLUS 3 using Tapatalk
noobtoob said:
I believe this is an option you need to setup during the wizard when you initially set up the device. It asks you whether you want to require a pin on startup or not.
But, you can also turn this on by going to settings>security>screen lock.
From there, you click on the area where it says PIN. Confirm your pin, then click PIN again, and there should be an option to require pin for startup. Other than that, you are still encrypted, but it is all bypassed in order for quicker startup.
Sent from my ONEPLUS 3 using Tapatalk
Click to expand...
Click to collapse
Ah that was it! it had somehow disabled itself, simply going in and enabling "require pin to start device" solved it.
Thanks!
Try removing the lock screen password and setting it up again and it will be back again in twrp.?
Ok so I'm a little bit of a security freak, I care about how my data are secure on my device and make sure that not a single bit of Google's code is left and tracking me (I debloat roms myself).......... The biggest issue is Encryption
I have both OP3 and 3T
Pre OS setup
OP3:
- OB 28 firmware
- Blu.Spark TWRP 8.61
OP3T
- OB 19 Firmware
- Blu.Spark TWRP 8.61
The issue I faced is that once I set an encryption password I either cannot change it, or a garbage password will be set and I won't be able to boot to my phone again unless I "fastboot format userdata"
- Type 1 issue, Set encryption password but can't change later: happens in all RR and LOS based roms (I even read somewhere that this bug was reported but due to it not being a popular feature the issue was cancelled", they suggested that in order to change it I have to make a complete back up, decrypt, restore back up, and encrypt again with a new password.... And this is a no go for me.
- Type 2 issue, Set encryption password and a rubbish password will be set: this happened to me in a few AOSP based roms (CardinalOS for example), so if I set a pattern for example, the encryption password will not be the same pattern I set, thus I'll be locked out of my phone unless I format userdata
I tried the cryptfs command
"vdc cryptfs changepw password '<old encryption password>' <new password>"
But nothing changes
Not all AOSP roms have this issue tho, PureFusion ROM (which is AOSP based) is fine, and all OOS based roms are fine too
Is there any fix for such issue? I'd love to use another rom,
possibly RR (Currently using FreedomOS), but the encryption issue is bothering me
According to latest part of your post, the "buggy" cryptfs concerns only some custom roms.
How would you solve that issue? It's depending by rom developer, the only attempt you could try is a bug report.
But there's a good risk to be ignored, because many people are not so obsessed by security, developers won't to find time for very rare issues.
DaKing1512 said:
Ok so I'm a little bit of a security freak, I care about how my data are secure on my device and make sure that not a single bit of Google's code is left and tracking me (I debloat roms myself).......... The biggest issue is Encryption
I have both OP3 and 3T
Pre OS setup
OP3:
- OB 28 firmware
- Blu.Spark TWRP 8.61
OP3T
- OB 19 Firmware
- Blu.Spark TWRP 8.61
The issue I faced is that once I set an encryption password I either cannot change it, or a garbage password will be set and I won't be able to boot to my phone again unless I "fastboot format userdata"
- Type 1 issue, Set encryption password but can't change later: happens in all RR and LOS based roms (I even read somewhere that this bug was reported but due to it not being a popular feature the issue was cancelled", they suggested that in order to change it I have to make a complete back up, decrypt, restore back up, and encrypt again with a new password.... And this is a no go for me.
- Type 2 issue, Set encryption password and a rubbish password will be set: this happened to me in a few AOSP based roms (CardinalOS for example), so if I set a pattern for example, the encryption password will not be the same pattern I set, thus I'll be locked out of my phone unless I format userdata
I tried the cryptfs command
"vdc cryptfs changepw password '<old encryption password>' <new password>"
But nothing changes
Not all AOSP roms have this issue tho, PureFusion ROM (which is AOSP based) is fine, and all OOS based roms are fine too
Is there any fix for such issue? I'd love to use another rom,
possibly RR (Currently using FreedomOS), but the encryption issue is bothering me
Click to expand...
Click to collapse
If you really are concerned with security then stay on stock and lock your bootloader. Anything else weakens the security of a device.
But really really. Mobile security is a myth. It is a fear mongering tool used by people to keep you in line. If someone wants your info they will get it and they dont need your device.
this might happen with you , happened with me (✖╭╮✖)
I have the Strong Protection setting (previously called Secure Startup) enabled, but it recently stopped working (probably sometime since the ASI3 firmware update for N975U1). Instead of prompting for my password early in the boot process, the phone gets all the way to displaying my lock screen (showing my contact information, selected background image, etc.), which suggests that the phone's encryption has already been unlocked with no password entered yet. (It does still require my password to get past the lock screen.)
I've tried disabling and then re-enabling the Strong Protection setting, and clearing the system cache, but the phone still boots all the way to the lock screen without requiring a password.
Has anyone else encountered this problem? Alternatively, is there anyone else (with the ASI3 firmware) who is *not* encountering this problem?
It may have changed a bit in an update?
Ever since I got my note 10+ (build ASJ2 and the previous 2 updates) that is how strong protection has worked.