Database Users

Fingerprint misbehaviour

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.

Magisk not passing Safetynet check after disabling fused position

Like the main title said, i've just installed magisk today (ver 16.7) and it worked fine.
After that i've installed a fake Gps App for mock my location. I've made it a system app and it worked fine, the only thing was that the position was unstable (the marker on Google Mpas "jumps" over the real and the mock position) so i decided to disable the fused position module via the Disable Service app (downloaded on the Google Play Store) for make the position stable, then i reboot my p9 lite. After that i got a bootloop, after 3 reboot a wipedata was performed on the phone. So i decided to reflash magisk but this time i'n not passing the SafetyNet check (both BasicIntegrity and ctsProfile are false).
I state that i've read the Magisk Issues and question and I didn't find nothing helpful. I've tried to install the magiskHide props module too and doing some thinkgs via terminal but nothing seems to work.
Any suggestion/help?

Google Pay stopped working

Hi,
im a little bit confused about this problem. From one day to another, G Pay stopped working with NFC. "This device cant be used because its rootet or modified."
I use Magisk with stock Rom severeal month now and gpay ran without any problems. The confusing thing is that I didn´t changed anything what could cause this behaviour.
What I already tried:
-GPay: Delete cache, uninstalled updates. Tried many times to activate NFC payment.
-Erased Cache in TWRP
-Installed complete offline OTA. (Root and TWRP was gone and it still wont work)
-Tried Magisk Hide and random app name.
Does anybody have an idea? I dont want to reset the whole phone for this or lock the bootloader.
Thanks for your help!

Did you update the Gpay app? Mine still works but I never installed the update

I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.

sharksfan7 said:
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
Click to expand...
Click to collapse
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.

Probably because having a rooted phone, especially if you are using to send/receive money, opens up a SECURITY HOLE, even if you are using something to "bypass" google.
NOTHING is 100% safe, but, I for one, will never root my phone, if I am using it to spend money.
The days of rooting will be over one of these days. Google is locking down things more and more.

hlzocker said:
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Click to expand...
Click to collapse
Make sure you have hide enabled for pay.
I'm on 18.1 and I don't have issues.

I fought with the same problem.
latest Magisk Canary build was the solution that worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551

Coumodo said:
I fought with the same problem.
latest Magisk Canary build was the solution the worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Click to expand...
Click to collapse
Yes, that solved the problem for me. Now the activation was successfull. Thanks!

Apps Update atleast Thrice

Hi All,
So I'm facing this weird issue, where my app updates from the Google Play Store don't seem to stick.
I started having this problem when I was using LOS, and I thought maybe the ROM was the issue. But then, I switched to OOS, same thing.
An app will update and play store will show all apps updated. Then after a few hours the app will update again, and then once more. Usually the update sticks after the third update.
Also, even though I haven't kept a log, but it doesn't seem specific to some apps, it appears to be the case with all apps.
I use Magisk for Titanium Backup. But nothing else.
Also, I thought this was an issue with apps restored with Titanium Backup, but that isn't the case.
PS: I haven't tried without Magisk, as I wouldn't want to use the phone without that.
Any ideas?

fash_ahmed said:
Hi All,
So I'm facing this weird issue, where my app updates from the Google Play Store don't seem to stick.
I started having this problem when I was using LOS, and I thought maybe the ROM was the issue. But then, I switched to OOS, same thing.
An app will update and play store will show all apps updated. Then after a few hours the app will update again, and then once more. Usually the update sticks after the third update.
Also, even though I haven't kept a log, but it doesn't seem specific to some apps, it appears to be the case with all apps.
I use Magisk for Titanium Backup. But nothing else.
Also, I thought this was an issue with apps restored with Titanium Backup, but that isn't the case.
PS: I haven't tried without Magisk, as I wouldn't want to use the phone without that.
Any ideas?
Click to expand...
Click to collapse
Currently using Magisk on OOS and I do not have this issue, so root isn't the issue. I think it may have to do with the play store itself, as it doesn't seem to actually update the apps until the third time like you said. The only two solutions I can come up with are as followed:
1. Hold down on the play store app and clear the data on it and then disable the app (Make sure the option to go back to the factory version comes up after you press disable) and then re-enable the app again. Open it and see what happens afterwards. The idea is to get the play store to re-update itself and fix the issue.
2. Get on a computer and fastboot flash OOS again and see if it persists after you get your phone set up again.

Sadistic_Loser said:
Currently using Magisk on OOS and I do not have this issue, so root isn't the issue. I think it may have to do with the play store itself, as it doesn't seem to actually update the apps until the third time like you said. The only two solutions I can come up with are as followed:
1. Hold down on the play store app and clear the data on it and then disable the app (Make sure the option to go back to the factory version comes up after you press disable) and then re-enable the app again. Open it and see what happens afterwards. The idea is to get the play store to re-update itself and fix the issue.
2. Get on a computer and fastboot flash OOS again and see if it persists after you get your phone set up again.
Click to expand...
Click to collapse
Hi.. Tried these already... The problem persists.

Google Play Protect Certification

Hello there. I have a question regarding getting my phone to be Google Play Protect certified again. I have unlocked the bootloader, which if I understand correctly is what breaks the certification, Flashed TWRP 3.0.4-1, and installed Magisk v20.4 via TWRP. I verified Root by using the app Root Checker on the play store (and also SU requests popped up after rebooting). I enabled MagiskHide inside Magisk Manager and performed a SafeyNet Check and both the ctsProfile and basicIntegrity returned as True (the first time I ran it cts failed so I enabled hide and rebooted). There are a few apps that I use that indicate my device is not compatible and it is because of this I am guessing (Chewy, Disney+ for example). Oddly, as I was typing this I tried again and looked in the "My Apps" list and I could install Disney+ from there (10 minutes ago I couldn't) but clicking on the app it still said that it was incompatible. Chewy, however, remains unable to be used.
Since I could only find references to this on this thread (https://forum.xda-developers.com/pixel-2-xl/help/play-certification-unlocked-bootloader-t3950857) and the second way to correct this problem, that thread says it doesn't resolve the ctsProfile) I figured I'd ask on here. I already soft-bricked it once and successfully used the MSM tool to bring it back so if I screwed something up I'll try again, but probably only once more :fingers-crossed:
*edit* I haven't activated my actual phone use yet since I want it to be stable first! Not sure if that makes a difference, I don't think it should.
*edit 2* I've since activated my phone. I can receive calls but no text messages. The plot thickens.
Thanks!