I clean flashed (wiped data, both caches and system from TWRP) Codename Phoenix, the latest build from Telegram, and flashed the recommended 8.1 Gapps, but didn't flash Magisk as I only had a 15.x build which causes bootloops unless flashed after a 14.x build which I didn't have on my internal storage.
It flashed fine, I began to set everything up and then locked my device. I was able to unlock it with my passcode as normal, but after about 10mins it stopped recognising my passcode and I couldn't unlock with fingerprint either as "additional authentication" was required.
EDIT: Should probably add I also went into trusted agents and disabled "Smart Unlock" or whatever the Google thing is, and enabled Quick Unlock (the thing that automatically unlocks your phone when you get your passcode correct). After that it stopped working.
I came from the latest Open Beta (OB3) of OxygenOS.
I figured- no problem, I'll just restore from a backup that I'd made before flashing Code Phoenix. Unfortunately, TWRP no longer recognises my passcode to decrypt my data, and default_password doesn't work either.
I have no idea what to do. I've flashed the latest blu_spark TWRP build, and there's no difference. Is the only solution to wipe my internal storage?
You enable quick unlock option which mess up with encryption keys. Only option is format data our remove user data from fastboot.
It is best to stay decrypt if you don't know what you are doing?
elliottweaver said:
I clean flashed (wiped data, both caches and system from TWRP) Codename Phoenix, the latest build from Telegram, and flashed the recommended 8.1 Gapps, but didn't flash Magisk as I only had a 15.x build which causes bootloops unless flashed after a 14.x build which I didn't have on my internal storage.
It flashed fine, I began to set everything up and then locked my device. I was able to unlock it with my passcode as normal, but after about 10mins it stopped recognising my passcode and I couldn't unlock with fingerprint either as "additional authentication" was required.
...........................
Click to expand...
Click to collapse
Do you have a backup you can restore?
Related
Hello,
I have recently flashed the Marshmallow update to my phone coming from WW-2.20.40.194. It was encrypted and used a PIN on both the boot and the lock screen. With Lollipop, I can decrypt my phone in TWRP by entering my lock screen PIN. However, neither TWRP 3.0.2.0 nor a TWRP repack (found at: https://drive.google.com/drive/folders/0Byp0425xydUaYzk1anRCak0zZXc) on Marshmallow are able to decrypt the phone, saying the password is invalid. I have tried the lock screen PIN, "default_password", as well as using an app called "SnooperStopper" to change my encryption password to something other than my lock screen PIN, with no luck. Is anyone else experiencing this or have a fix?
If i recall you must unencrypt before any flash. Your encryption key is now lost along with all your data. Sorry.
Sent from my ASUS_Z00AD using XDA Premium HD app
Maybe you'll need to downgrade to L, decrypt the phone, upgrade to M again and encrypt it a second time.
After uploading the M update, Asus also uploaded a rom to downgrade from M to L, so anyone can perform a downgrade just the same way they did the upgrade.
Thanks for the replies! I haven't lost any data, since I backed everything up manually beforehand. However, even if I didn't backup the data, I can still unlock the phone itself (get past the lock screen and to all my files), just not through TWRP's lock screen. I've tried encrypting before and after upgrading to Marshmallow, with the same results.
UPDATE:
Just tried again with TWRP (tethered and untethered) on a clean install, same results. Steps:
Used fastboot to completely erase phone (data, cache, dalvik, system, etc).
Flashed stock recovery for Lollipop (WW-2.20.40.194).
ADB sideloaded WW-2.20.40.194 in stock recovery.
Wiped data and cache again in stock recovery.
ADB sideloaded Marshmallow (WW-4.21.40.134).
Rebooted to system, logged into Google account, set up system, etc.
While setting up system, chose to lock device with PIN.
After setup, encrypted the phone.
Rebooted to bootloader.
Fastboot boot TWRP.
Tried to enter PIN, says invalid. Tried to enter "default_password", says invalid.
Fastboot flash TWRP, same results.
Hi yes, ive had the exact same problem running a nightly build of CM13 / Android 6.0.1. It just tells me the password is wrong. TWRP 3.0.2.0
Personally I think something changed in recent Android builds and TWRP just hasnt figured out that its broken yet. TWRP 3.0.2.0 is almost 6 months old now ...
I need to find a way to update my roms also so this is a problem.
I am glad to hear it is not just me having this issue. I believe this as well, though TWRP 3.0.2.0 worked just fine on an older version of XOSP (CM13-based, I think from a build around December 2015). Something must have changed since then.
I have discovered the problem. You can read all about it here.
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
tl;dr
Snapdragon 800+ CPU phones (any maybe others) have HW_Crypro (hardware crypto chip) and Android 6 + enables this. Which requires recompiled TWRP with support for HW_Crypto
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
So, I have a rooted OnePlus 3 with CM 13.1 Snapshot. But wanted to try CM 14.1. So I wipe Cache, Dalvik, Data and system, and install CM 14.1 nightly. After messing with it for a few days its was not daily driver ready for me. So same ting and install CM 13.1 back.
Now, I setup phone and all. I want to go back to TWRP to flash Exsposed. Suddenly it asks for a password (said no thanks in setup) so I assumed it would be my pin, but that was incorrect. I started the phone back up and asked for a start-up pin (even I said no thanks in setup) but that was my pin. So I tried to chance it into a pattern and hoped it would update in TWRP.
I go back to TWRP still incorrect, I go start my phone back up, but now it saying that the startup pattern is incorrect. I'm 100% sure is correct.
Now I can't enter TWRP and/or my phone.
Please help me, thanks.
Did u happen to restore from backup ?
You need clean install, else the pin information might had an issue,
This issue presence in 3.0.2.0 TWRP not sure whther it's been fixed or not.
Solution is dont use PIN (remove it) prior to doing backup
Hello,
I am having issue with my mi mix 2 (chiron), since using custom ROMs (9.0 based). The roms and everything connected with it works fine, but problem comes, when i want to install new OTA update (that is quiet offen, since developer release new version several times per weak). Everytime i boot in recovery (TWRP, last official available version for chiron), data partition is encrypted and i am unable to decrypt it in twrp (twrp says, i have inputed wrong password [i have tried to change to text password, didnt help]). I have also tried different versions of TWRP - same result. The only way how to not lose data is to install update from external storage, which is anoying. Lastly i have tried to search for help here and other forums, but did not find any solution. Does anyone else face this problem and is there any way, how to decrypt data partition in twrp?
Thanks in advance
Marek
Running Pixel Experience ROM. I always used TWRP but due to changes in the ROM in an update 2 months ago I had to install Orange Fox. All worked well. Trying to install latest update, but when I now reboot in recovery it asks for encryption password. I've tried my screen pin but that's not accepted.
I don't want to format my data partition.
Then, install TWRP again, which worked fine before, but now has the same problem: Asks for encryption password.
How can I fix this please?
Hello,
I installed multiple different custom roms, and all of them give the same error: "fingerprint enrollment didn't work" while trying setting up finger print unlock after flashing the rom. I have no idea why this error suddenly occured. :crying:
I flashed MSM-Xtended v4.0, and after Havoc-OS. Rebooting doesn't fix the problem.
EDIT: It does work when I flash stock-rom.
Going to flash custom rom now.
EDIT 2: Flashed Havoc-OS, still the same problem. Enrollment was not completed, fingerprint enrollment didn't work. Try again or use a different finger.
EDIT 3: Flashed AOSiP DerpFest, with Gapps included. It does work now. Can it be the Gapps? I want to use havoc, because Netflix worked on it. On the DerpFest rom I get the error incompatible.
EDIT 4: Flashed Havoc again, this time with another Gapps. And it's working now !!! No idea why, but it's fixed!
Hello, the fingerprint sensor has a bug on a lot of P2. On mine, it worked for 5 months straight and now it's 5 months that it works just like 1 week every 5.
Rebooting, in my case, has a 25% chance of making it work again.
joshthemajor said:
Hello, the fingerprint sensor has a bug on a lot of P2. On mine, it worked for 5 months straight and now it's 5 months that it works just like 1 week every 5.
Rebooting, in my case, has a 25% chance of making it work again.
Click to expand...
Click to collapse
I made it work again with the following procedure in TWRP:
wiping > system, data, cache, dalvik, internal data
flashing > Havoc-OS-v3.0-20191218-kuntao-Unofficial.zip
flashing > open_gapps-arm64-10.0-nano-20191209-BETA.zip
flashing > Magisk-v20.1.zip
clearing > cash and dalvik
reboot
After the reboot I just logged in with my Gmail and was able to setup a pin and fingerprint.
the OS, Gapps and Magisk links are from other posts (I don't know if I'm allowed to copy links from others)
Umbreonlvl100 said:
I made it work again with the following procedure in TWRP:
wiping > system, data, cache, dalvik, internal data
flashing > Havoc-OS-v3.0-20191218-kuntao-Unofficial.zip
flashing > open_gapps-arm64-10.0-nano-20191209-BETA.zip
flashing > Magisk-v20.1.zip
clearing > cash and dalvik
reboot
After the reboot I just logged in with my Gmail and was able to setup a pin and fingerprint.
the OS, Gapps and Magisk links are from other posts (I don't know if I'm allowed to copy links from others)
Click to expand...
Click to collapse
So I tried installing Havoc 3.2 and the same thing happend... And I still don't know exactly why this happened. Even after reinstalling Havoc it didn't work. After I tried installing the stock firmware it did work in the stock firmware. But when I installed Havoc again, the same problem..
First time:
-Wiped whole system
-Flashed Havoc 3.2
-Flashed Gapps
-Flashed Magisk
Rebooted and couldn't use fingerprint.
Second time:
-Wiped whole system
-Flashed Havoc 3.2
Booted and tried fingerprint in setting (did work), removed the fingerprints
--Back to recovery
-Flashed Gapps
-Flashed Magisk
Rebooted and everything works as intended.
I know it's an old thread, however, hope someone can still benefit from my findings, it's loose connection, lay a towel on the desk, slam the bottom part of the phone, you will be surprised!
I don't even have a fingerprint option on my p2.
Now on corvus 10 july 10th build. ?
sandeepswstik said:
I don't even have a fingerprint option on my p2.
Now on corvus 10 july 10th build.
Click to expand...
Click to collapse
It's handy and for lazy bastards like us but do you really need it? Meh I don't think so unless you are going to use apps that have biometric authentication of some kind.
Even with the stock rom I have noticed last few months that my sensor also had some issues randomly stopped working but reboot fixed it. In my case I think the sensor might fail soon, had the same with my Lenovo Zuk Z1 grey (Z1221).