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.
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?
I have no fingerprint auth option in Google Play. Also in my banking app, that specific option doesn't show up.
It worked fine in the past, I'm literally out of ideas what could've caused it to disappear... It used to work back when I was using SuperSU and SafetyNet wasn't passing for me, then it still worked when I moved to Magisk then after some time it just disappeared.
Fingerprint sensor is working, already tried removing all fingerprints and pattern locks (then rebooting) and re-adding them, tried also a method with removing few specific files from data (that remove any locks and saved patterns/fingerprints) partition from within TWRP - still no luck. However when I uninstall updates of Google Play the option is back up, but once the store updates it disappears again...
Redmi 3S with latest xiaomi.eu 7.9.21 + Magisk, SafetyNet passes, Google Play certified.
kwski43 said:
I have no fingerprint auth option in Google Play. Also in my banking app, that specific option doesn't show up.
It worked fine in the past, I'm literally out of ideas what could've caused it to disappear... It used to work back when I was using SuperSU and SafetyNet wasn't passing for me, then it still worked when I moved to Magisk then after some time it just disappeared.
Fingerprint sensor is working, already tried removing all fingerprints and pattern locks (then rebooting) and re-adding them, tried also a method with removing few specific files from data (that remove any locks and saved patterns/fingerprints) partition from within TWRP - still no luck. However when I uninstall updates of Google Play the option is back up, but once the store updates it disappears again...
Redmi 3S with latest xiaomi.eu 7.9.21 + Magisk, SafetyNet passes, Google Play certified.
Click to expand...
Click to collapse
This might be problem with the rooted ROM
Better flash the stock ROM once again and lock the bootloader
Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!
Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.
If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.
Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.
Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.
Hey everyone, I'm pretty new with ROMs and everything regarding Android, but I've been trying to flash an AOSP ROM, whether official or not, just to get GPAY or my banking app to work on my A20e.
You can download the apps, they run fine, you can add your card and input the SMS code and everything, only problem is at the last step where GPay just gives me a standard error and my banking app gives me a "Digitization not finalized".
I got both GPAY and BTPay (my banking app) to work with the stock rom, so It can't be the card itself.
Has anyone ran into this or managed to fix it?
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
burningcreation said:
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
Click to expand...
Click to collapse
It's not rooted.