Before the noob alarm goes off I've already attempted disable credentials multiple times, disabled all adminstration, and I have never used any encryption on my phone.
The issue occurred after I updated from lollipop to marshmallow.
I am using he heavily skinned EMUI 4.0 on the huawei P8 lite, could this be the issue?
Thanks in advance
Related
Hi,
I've recently updated my N910F to Marshmallow (official). It's not the latest version but I wasn't able to download that one yet.
I made a fresh install with it (factory reset via TWRP, flashed it through ODIN, rooted via CF Autoroot, installed TWRP 3.0.2-0 and XPosed v84, restored Apps trough Titanium) and even reflashed it with a wipe of system, cache and dalvik cache before because of problems with auto rotate.
But the Fingerprint API or something like that seems to be not working how it should. I can't set screen lock to Fingerprint (I get asked "Enter a backup password.", wenn I enter one, it just says "Sorry, try again" without saying why it failed), even after going to security settings and deleting the credeintially, which fixed such problems on 5.1.1 it doesn't work.
I also had read, that you could use your Fingerprint for authentication in PlayStore, but at least in version 6.7.12.E I can't see that option.
PlayStore should use the API of Nexus Imprint for that and I thought that this is required by any OEM that want's to get a license for M, so I don't really see why it doesn't show up.
The sensor itself seems to be working, I was able to register my fingers and with FingerLock, an app locker designed for Samsungs proprietary Fingerprint API form earlier versions, I also have no problems.
I think, Samsungs own implementation is working (accept for Lock screen but they´could have changed it here for the official one), only apps for Googles standardized one are failing. But I can't really prove it. An app, that should be using the official API in M is failing, but the developer says it's a problem only with the Note 4 and he hopes he can publish a fix later this month.
The app locker MaxLock, which I thought would use fingerprint authentication with the official API doesn't show up an option for that but maybe through problems with the implementation.
Is there any way to test what's going wrong?
PS: sorry for the long text
I now have this..... Any solution?
Get a (non-TW based) custom ROM. It's the only thing that's works since Samsung most have screwed up the whole API. Their own is only useable partially and the standard one by Marshmallow is completely messed up and not worrying at all.
I was so pissed off of Samsung's incompetence that I switched to emotion ROM. It's a bit tricky to set up the fingerprint reader, but once it's done, everything using the official API is writing flawlessly. Never gonna switch back.
Hi! I hope that someone could help me.
First some informations:
I have a Huawei P9 Lite, running B370 (VNS-L31C432) + patched SuperSU root + unlocked bootloader.
My Problems:
-If I try to open developer settings, security settings, ... I always get message that settings will be closed. I don't know how long this problem exist, because last time I tried to open was 2 weeks ago.
-If I try to uninstall apps, my phone starts a reboot. But not a normal reboot. It shows me boot animation and after it I am on desktop again, without beeing asked for sim pin again. I think it will be called "Fast reboot", right? But problem is, that App is still installed.
Would be nice if someone could help me, to fix these problems.
Greetings and sorry for bad English!
77777772
Rollback to marshmallow
Goodmorning everyone,
I am desperate. I have rooted on my Huawei P9 Lite device by following the guide for Android 7 with EMUI 5. Initially it seemed to have gone smoothly. Not without difficulty I unblocked the bootloader, installed the TWRP, the kernel and the SuperUser application.
However after installing the Elite Kernel for P9 Lite All Variants CxxB3xx With MagiskSU v10.1 by HassanMirza01, I did not accept the PIN when I restarted the device despite being the right one, preventing me from entering and doing any kind of operation. I did a search on the internet and learned to be a fairly frequent thing, so I deleted with TWRP the files "gatekeeper.password.key", "gatekeeper.pattern.key", "locksettings.db", "locksettings.db-shm", "locksettings.db-wal" from /data/system as indicated.
Indeed, I rebooted my device again and I did not ask for any PIN, so I could use the device, but when I set up a new PIN, it does not allow me to. If I try to register one, after entering the PIN for the second time as confirmation, it hangs for a few seconds and goes back to the screen lock selection still set to "None".
Same thing if I try to set the fingerprint: first asks me to create the PIN and then stays impaled at the same point.
Also from "Settings" if I try to go to "Advanced" ---> "Security" the app crashes. Same speech if I try to access the "Developer Options".
Please help me solve this problem without having to do another Factory Reset because I can no longer lose all the data again.
Many thanks in advance!
Hello, my phone just updated couple of hours ago to Oreo and I can't disable swiftkey anymore and it keeps updating itself. Any ideas?
I recently flashed my P10 Lite back to stock EMUI 8.0 because I was having issues using Magisk. Now that I have it setup again, for some reason I can't enable fingerprint authentication on any apps. It just automatically fails or makes the app crash.
Has Google's root detection gotten better or am I missing something?
TheLazyHatGuy said:
I recently flashed my P10 Lite back to stock EMUI 8.0 because I was having issues using Magisk. Now that I have it setup again, for some reason I can't enable fingerprint authentication on any apps. It just automatically fails or makes the app crash.
Has Google's root detection gotten better or am I missing something?
Click to expand...
Click to collapse
So I used eRecovery to restore EMUI 8.0 again and now my fingerprint authentication in apps works again.
I'm starting to think Magisk 17.2 is breaking fingerprint authentications
OEM Unlocking doesn't break it