I'm on RR with Franco kernel but I'm not sure that matters for this.
I use figerprint for device security. It works great for my needs, i don't have to type a code or pattern and my 2 year old can't get into my phone.
My problem is this, in order to utilize twrp (install zips, nandroid, etc) I have to disable all security before booting into recovery/twrp or all the files are encrypted within twrp and I can't find what I'm looking for. Once finished within trwp i can then reapply fingerprint security but then I have to reprogram all fingerprints.
Is there a way to deactivate security, use twrp and then reactivate without having to reprogram the fingerprints everytime?
I don't disable fingerprint security and still can use TWRP. Just enter your pin. Afaik you have to enter your pin if you use fingerprint security. So use this pin in TWRP.
Maybe use a different twrp ??? Sometime if its too new or too old will have some kind of bugs. Always try a different built if anything fails. That's what I did for mine when my phone went had error occured.
Lupus77 said:
I don't disable fingerprint security and still can use TWRP. Just enter your pin. Afaik you have to enter your pin if you use fingerprint security. So use this pin in TWRP.
Click to expand...
Click to collapse
You are correct, that works. thanks!
Related
I'm on stock ROM Nougat 7.1.1 B02 on my A2017G. ZTE had promised full phone encryption with 7.1.1, however, the phone doesn't ask me for my password at boot time but only after asking for the SIM's PIN at first login. In the security settings it says that the phone is encrypted, however, I'd rather have the full encryption that uses my password for encryption as well. Has anyone gotten encryption with PW to work on a A2017G on stock ROM? Or am I missing something and encryption is already working properly?
1. you can activate a password or pattern that will be asked after every boot or reboot
Indeed. But that's after the boot process which leads me to believe that the password isn't used as part of the encryption key. Other Nougat devices I use ask for the password before the main boot process takes place.
Hi,
I was changing pattern. Somehow I applied wrong pattern and then locked phone.
Now I can't unlock with fingerprint. There aren't any connect Google Account button even I am connected to internet mobile + wifi.
I didn't install TWRP and my phone is not rooted. Are there any way to unlock without losing any data? I can do anything possible (like root or install twrp) if I wont lose data.
wont a hard reset work
Without TWRP you can't do much...
chester2011 said:
wont a hard reset work
Click to expand...
Click to collapse
That will delete data.
Unfortunately, hard reset is the only way out of this. Since the data on the phone is encrypted, you require the pattern to decrypt the data in order to access it. This also includes access to the hash that is generated by your fingerprints which is why you need to enter your PIN or pattern on startup before you can unlock with your fingerprint.
Bottom line, never ever forget your backup authentication method!
Edit: I can't guarantee this will work, but it's worth a try:
Visit https://www.google.com/android/find (Find My Device)
Log in with your Google account
Click "Lock" and enter a new password.
Try that new password on your phone.
Sent from my ONEPLUS A5000 using Tapatalk
i forgot the pattern of my xiaomi and now im stuck in ''to launch android write the pattern''
is there a way to avoid losing my data? android device manager isnt detecting the phone
most likely not. As far as I know AndroidOne devices are encrypted by default and without the pattern you can not decrypt the data.
I 'm facing the same issue. Could you tell me how did you get over it? Please somebody reply fast.
https://forum.xda-developers.com/showpost.php?p=38147605&postcount=72
You need to unlock your bootloader and boot in twrp
Remove pattern lock by boot in TWRP and remove all security and patterns with the TWRP file manager.
Localhorst86 said:
most likely not. As far as I know AndroidOne devices are encrypted by default and without the pattern you can not decrypt the data.
Click to expand...
Click to collapse
This is correct. If it shows "To start Android..." on boot, your phone is encrypted with full disk encryption, and the only way to decrypt is to enter the correct pattern.
There is however a scenario which had occurred when I re-encrypted the phone by changing the password (which I believe didn't work as Magisk was installed, or possibly another reason), where even if the correct password was entered, Android would not accept it. In this case, try entering the password or pattern in TWRP. If it works, backup the data partition, as well as /sdcard separately, then erase it to remove the password and then restore the backup.
Trying to determine whether I should decrypt. Encrypted phone requires re-entering the password twice.
Encryption has nothing to do with requiring pin at start up. You can turn it off. And turning off encryption is not something you should do. Anyways to turn start up pin just remove the pin pass or pattern you have currently and then when you add again the first screen that pops up is the confirmation screen asking whether you want startup pin enabled. Select no and you are done..
The only real benefit to decrypting your device is if you use a custom recovery like TWRP--especially if it's not an official build of TWRP.
On some devices (especially those from One Plus) there are issues where TWRP either can't decrypt the data partition or stops being able to decrypt the data partition after an OTA.
On some phones you can just boot back up if that happens but on others you are locked out and need to reformat and reflash just so you can use the device again and if that can't be done which has been the case on some treble phones like the MI-A1 and the Essential PH-1 then your device is permanently bricked and is pretty much just an expensive paperweight.
Hello,
I need help: my note 7 asks me for a PIN when I start the system (Android) and also when I enter TWRP, and I want to remove these PIN requests.
In the 1st rom change (from Miui to pure Android - HavocOS), I did, in the following order:
-format data
-Wipe: system, dalvick, cache and date
When the system started for the first time, I configured the fingerprint sensor together with a 4 digit PIN and it is this PIN that I have to put in the system and the TWRP.
I tested other roms (Bootleggers, crDroid) and it happens the same. I've tried other recoverys, including OrangeFox and the same happens.
I've also tried reinstalling the rom by doing only format data (not doing Wipes) and doing the same.
I received the device with the rom: MIUI 10.3 Stable (10.3.5.0) [PFGMIXM]
The model name is: M1901F7G.
The Android version: 9 PKQ1. 180904.001
What else can I do?
Try not to setup pin after flashing rom and see bro...
I have managed to solve half of the problem: it is no longer encrypted and in TWRP it no longer asks for any PIN.
But on Android I do not accept the PIN that I set up along with the digital print, tell me that it is wrong.
Now the problem is to use PIN + fingerprint. I set up a PIN and when using that same PIN, tell me the PIN is wrong.
If you do not configure PIN, I can not use it without problems, but I lose access to the use of the print sensor
I rooted my device and installed magisk on the stock rom miui 10.3.5 for redmi note 7 will i receive ota updates?
and if not in order to flash newer miui versions of the rom do I need to flash vb meta?
P.Rabbit said:
I have managed to solve half of the problem: it is no longer encrypted and in TWRP it no longer asks for any PIN.
But on Android I do not accept the PIN that I set up along with the digital print, tell me that it is wrong.
Now the problem is to use PIN + fingerprint. I set up a PIN and when using that same PIN, tell me the PIN is wrong.
If you do not configure PIN, I can not use it without problems, but I lose access to the use of the print sensor
Click to expand...
Click to collapse
i am in the same situation man, i don't understand what is the problem and what is wrong...
In my case it was bad configuration, because I set up safe boot and this way I mistakenly assumed that this was related to encryption, but the error was only mine.
Check if you have set safe boot. With safe, always-on boot (a pin, a pattern or a password) every system boot and every time you enter TWRP.
Sorry my English.