Related
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 used to have an LG G3 which I rooted and installed custom ROMs on. I stopped doing this for my LG G5 when my bank app and Pokemon Go started checking for root and would refuse to run on rooted devices.
I see that it is possible to install TWRP without rooting my LG G6.
Does this mean that I can install custom ROMs on my phone without the root detection causing me issues for these apps?
Thank you
PentagonVS said:
I used to have an LG G3 which I rooted and installed custom ROMs on. I stopped doing this for my LG G5 when my bank app and Pokemon Go started checking for root and would refuse to run on rooted devices.
I see that it is possible to install TWRP without rooting my LG G6.
Does this mean that I can install custom ROMs on my phone without the root detection causing me issues for these apps?
Thank you
Click to expand...
Click to collapse
Just use Magisk (Fulmics has it included in the aroma installer) and you can hide root to the apps with MagiskHide and pass the safetynet.
Killua96 said:
Just use Magisk (Fulmics has it included in the aroma installer) and you can hide root to the apps with MagiskHide and pass the safetynet.
Click to expand...
Click to collapse
Thanks. I looked up Magisk. If this app would keep itself up-to-date that would be awesome.
I guess for now I'd rather not have to rely on Magisk, since I might have to wait for updates to it, when my my banking app updates it's safetynet code.
PentagonVS said:
Thanks. I looked up Magisk. If this app would keep itself up-to-date that would be awesome.
I guess for now I'd rather not have to rely on Magisk, since I might have to wait for updates to it, when my my banking app updates it's safetynet code.
Click to expand...
Click to collapse
Didn't understand nothing. Magisk allows to hide root from the app you choose and doesn't break safetynet at all, and safetynet is not app-related but system-related so you should wait for updates only in case of android updates that break some function of magisk.
Killua96 said:
Didn't understand nothing. Magisk allows to hide root from the app you choose and doesn't break safetynet at all, and safetynet is not app-related but system-related so you should wait for updates only in case of android updates that break some function of magisk.
Click to expand...
Click to collapse
I assumed safteynet is built into the applications, such as my banking app. I thought that they can update safteynet within the app and thus break the hiding of root.
PentagonVS said:
I assumed safteynet is built into the applications, such as my banking app. I thought that they can update safteynet within the app and thus break the hiding of root.
Click to expand...
Click to collapse
Don't know if it's built in Android or in the GServices but it's a google thing, not an app one =)
Still, with magisk your device could stop passing safety net any when Google decides to raise the standards. You would then have to wait for magisk to update and pass the safety net test again, or decide to (temporarily) uninstall magisk.
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!
Hi,
I'm hoping I am posting this in the right place but after installing Magisk on OOS11 I am unable to bypass Root detection on my banking apps, I have used Magisk Hide and this shows all okay with safetynet but using Root Beer it still detects SU binaries etc.
I thought it was somehow detecting the unlocked bootloader but after uninstalling Magisk and leaving the bootloader unlocked the apps function okay.
If anyone is able to help that would be great, many thanks!
Have you tried repackaging Magisk?
Hi, yes I tried that to but still detected su binaries etc.
have you try to use Xposed module: Root Cloak?
for some apps, I can successfully bypass the root detection.
sadly for my banking apps, it's just no use. somehow it still detect the root even the xposed. so I decided not to root my phone
but, I think it might work for some banking app.
Hi, thank you for the idea but still no luck, I'm using Starling Bank if anyone else is also having the same issue.
I use starling bank also, but magisk hide is working as it should
Also force stop the app, clear the data&cache, re add to magisk hide the try again
Ps - root beer will detect su binaries; that's it's purpose. But when you use magiskhide on root beer it hides them as expected.
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.