Database Users

passing safetynet with magisk 10.2 on x727 or x720?

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?

Android Pay Not Working Lineage OS 14.1 passes safetynet

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.

Netflix Error 5.2 after updating to Android 8.0- UNROOTED, STOCK

Hi all,
Just updated my stock, unrooted Verizon Galaxy S8 this morning to Android 8.0. Now, whenever I try to watch a show on Netflix, I get an error message saying "This video could not be played. (5.2)". I have already uninstalled and reinstalled, restarted my phone, and called Netflix (who said to just contact Samsung- and we all know how useful that will be). Any ideas here for how to fix?
Thanks!

I fixed that using root.
In a nutshell:
Rename the following file:
/system/lib/liboemcrypto.so to /liboemcrypto.so.bak
Not sure if you can root a Verizon S8, try your luck at this thread for a discussion on the issue.

Ahmer Jamil Khan said:
I fixed that using root.
In a nutshell:
Rename the following file:
/system/lib/liboemcrypto.so to /liboemcrypto.so.bak
Not sure if you can root a Verizon S8, try your luck at this thread for a discussion on the issue.
Click to expand...
Click to collapse
I can't, and don't want to root- I feel like Netflix and/or Samsung really screwed up here

This is an issue with Android's DRM implementation, I guess. Can you check if your device passes SafetyNet?

That's ... Odd. Netflix works fine for me

ryanpm40 said:
That's ... Odd. Netflix works fine for me
Click to expand...
Click to collapse
Never mind- It randomly started working again!

mancoh51 said:
Never mind- It randomly started working again!
Click to expand...
Click to collapse
Haha well I'm glad it's working for you! After it working all night for me, I'm now getting the same exact error you were getting. It's really annoying me, going to try rebooting next I guess.
Edit
So, rebooting was enough to let me watch one episode of a show, but then I got that error when I autoplayed to the next. I cleared the app's data and that fixed it, too. We'll see if that's a permanent fix.

I have this exact same problem. Don't want to root or unlock. I've tried uninstalling and installing the app. I've tried clearing data and cache. Is the next step a factory reset? Anything else I can do before that?

Buffpandabear said:
I have this exact same problem. Don't want to root or unlock. I've tried uninstalling and installing the app. I've tried clearing data and cache. Is the next step a factory reset? Anything else I can do before that?
Click to expand...
Click to collapse
Same thing happened to me. Just uninstalling and reinstalling the app didn't work. Had to reboot the phone after reinstalling and after logging back into Netflix, went to settings and ran check network. Everything came back OK. Was able to watch without any issues since. Hoping it stays that way.

Netflix problem?

anyone have netflix problem after unclock bootloader? I kept getting a "This app is not compatible with your device." I uninstalled the manufacture using ADB and sideload a version from APK mirror, I kept running into the same error, please help thanks.

Works fine here. Do you have Magisk installed with Magisk hide enabled? I know Netflix is unavailable in play store if safetynet fails, so maybe it needs to pass for it to work too? Just guessing here.

Widevine changes after you unlock the bootloader.

efex said:
Works fine here. Do you have Magisk installed with Magisk hide enabled? I know Netflix is unavailable in play store if safetynet fails, so maybe it needs to pass for it to work too? Just guessing here.
Click to expand...
Click to collapse
aoaleman said:
Widevine changes after you unlock the bootloader.
Click to expand...
Click to collapse
yes it is indeed boot loader unlock with magisk installed, anyway around this?

Vio281 said:
yes it is indeed boot loader unlock with magisk installed, anyway around this?
Click to expand...
Click to collapse
Can you find Netflix in play store? Make sure your play is certified, in case this makes a difference. If you enabled Magisk hide, just clear data for play store and play services and it should get certified correctly.
As I said, Netflix works just fine here, unlocked and rooted with Magisk and hide enabled. No further tweaks needed.

efex said:
Can you find Netflix in play store? Make sure your play is certified, in case this makes a difference. If you enabled Magisk hide, just clear data for play store and play services and it should get certified correctly.
As I said, Netflix works just fine here, unlocked and rooted with Magisk and hide enabled. No further tweaks needed.
Click to expand...
Click to collapse
I use apk mirror app to install netflix I download via apkmirror and it work.

Banking app crashing on rooted Android 11

Hey, all
Successfully upgraded and rooted my phone on Android 11 and have now discovered my banking app isn't working; it's crashing within seconds of trying to start.
I have Magisk itself hidden and my banking app, Navy Federal, checked under the MagiskHide section but it's not making a difference.
Anyone else having this issue and/or figured a way to resolve it?

Magisk hide isn't always going to work.
You could try hiding the magisk name but beyond that there isn't a lot you can do

@PassingInTime Are you passing the Safetynet check?

Yeh, see if magisk mgr is passing safety net...

XxSUPRAxX said:
@PassingInTime Are you passing the Safetynet check?
Click to expand...
Click to collapse
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.

PassingInTime said:
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.
Click to expand...
Click to collapse
What banking app has the issue? Ill test it out on my device.

Sometimes it's bank sided, when I rooted my device after updating to A11, my bank app didn't work and I thought it had something to do with root.
I ended up calling them, it turned out that they didn't update the app and after a couple of days I received an update and it's working again.
If it worked for you before root, try to hide Magisk, does it pass safetynet anyway?
EDIT: Just noticed that it passes safetynet, I'd suggest to restore stock boot and see if it works, if so, try rooting again.
Are you using beta canary?

roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.

Enable USB debugging and use ADB logcat ... Start the app ... Stop the logcat and check for errors in the log ... Maybe you'll find why in there

cali310 said:
roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.
Click to expand...
Click to collapse
Finally works for me too - took them awhile.