Is anyone getting a problem passing safetynet with the March install? Clean wipe and install, I have root but can't pass safetynet. I've wiped it 4x... no luck. Can anyone help?
I have a feeling SafetyNet hasn't been updated with the March builds (hoping anyway). Unless they've figured a way to detect root and we need a Magisk update.
It wasn't giving me any problems before after installing March update but just noticed now it isn't passing. Sometime in the last 2 days something happened.
Having the same problem. Was fine yesterday.
JasDevi said:
Having the same problem. Was fine yesterday.
Click to expand...
Click to collapse
Guessing Google did something to detect unlocked bootloader since a bunch of people are experiencing it.
I flashed back to a clean Feb build and got the same thing. I thought it was me.
Gosimer4 said:
I flashed back to a clean Feb build and got the same thing. I thought it was me.
Click to expand...
Click to collapse
I tried that as well no luck
I too am having this issue.
I tried fixing it with " Magisk Hide Props Config" with no luck.
Guess we just have to wait until there's a Magisk update
same here
wonderlander17 said:
same here
Click to expand...
Click to collapse
It's a widespread problem being discussed over in the magisk forums. Seems like Google is changing something server side with their checks. Don't think it is related to the March updated since checks are failing on older firmwares
Same here for me.
Anyone else have "Device is not certified", under Play Protect certification?
This happens on nearly all phones running March 2020. Saw it on my Pixel 2XL running March 2020 PixelDust and on a Pixel 3XL running Srock with Magisk as well. Just look into the Magisk Discussion Thread and you'll see that Google seems to have changed something again. Reports are coming in on the said thread in masses.
Sent from my Pixel 4 XL using XDA Labs
Was just about to create a thread about this.
I didn't know this was a common issue amongst many users, so I clean flashed twice in just as many days
I thought maybe I had accidentally flashed the AT&T version when that's not my carrier, or that my dtbo or boot image was corrupt, or patching the stock boot image in Magisk went wrong. I also tried switching kernels and so on.
So far no functionality for my use case has been broken so at least that's a plus.
Same thing happened here with Pixel Experience ROM. Used to work fine, then updated to March 5 security patch, and ctsprofile won't pass anymore.
Though at some moment it did pass, as I've even could get Play Store to show certified and such, but then it failed later on.
Google Pay, banking apps and everything seems to be still working, so it's just a visual glitch for me, at least.
Enviado de meu MI 9 usando o Tapatalk
This literally just happened to me today. Was all good on March update until today and now can't pass cts no matter what.
I read somewhere that may be correlated with unlocked bootloader. So we have to wait for new Magisk update probably.
Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...
tisla said:
Oh wow I thought I had installed a module that may have failed it but when I tried just Magisk it still broke. Now I know that the March Security update broke it...
Click to expand...
Click to collapse
It's something Google has done on their end. So going to an earlier firmware won't help. Definitely looks like the bootloader status is being detected.
It is most definitely on Google's side, I ONLY use Carbon ROM 9 (AOSP) and it hasnt changed in weeks, no updates, no security changes, then out of the blue a few days ago, it fails. The only thing that changed was Google's side, to test it out, I just rebuilt my Pixel 2 XL with the same Carbon ROM OS, same steps, same base Google firmware (which was working last week), and it fails CTS. No changes on my side, not one, this is Google modding changes on their side unfortunately. I will note, that Netflix shows up in the play store NP (when it IS a problem or MAGISK isnt passing correctly, it wont show up in the play store), so it still works perfectly fine for me. I do not use any bank apps but TD (which is fine, but no GPay) so I dont know if it affects GPay.
GPay still working over here on March update
Related
...
cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
Upgrade to the latest version or install persona's b632 if you have kirin 620
..
cmmx said:
I already have the latest, b632.
I can't see how a custom rom could succeed where the stock one fails, though. Still I rather keep the phone stock ftm, at least until I get to decide what changes are applied and how.
Just reset and updated the app and no change. Phone isn't rooted.
Click to expand...
Click to collapse
I still get this problem some times if i switch from custom rom to stock, and i just reinstall rom again with a clean install and all is good, device get certified by google
Enviado desde mi hi6210sft mediante Tapatalk
...
cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
If You have root! Best Way to bypass It root Your phone with Magisk root
...
cmmx said:
I don't have root, and can't see why that would affect it, because what it says is the certification is for the device's hw (not sw), so it shouldn't matter if it's rooted or a custom rom or whatever (and I'm on stock Emui, anyway).
And it has nothing to do with Safety net either, because Magisk Manager (now) says it passes both cts and basic integrity (a week ago, the same version (other install) only passed basic integrity, and a couple months ago (other version) it didn't pass either one, with someone on Magisk thread even telling me that's because Magisk itself wasn't installed - guess what: it still isn't, yet it now passes both...).
Either way, I haven't noticed any problems from it, so far, so I'm just puzzled.
Click to expand...
Click to collapse
Bugged Google Play,just wipe data for gplay app.
...
Just wanted to create a thread similar to the Pokémon Go one because i've seen the only one having problems with this app and magisk despite the John announncement made in September...
Anyway, back to the main topic, in this thread i would like to gather all users with some requirements:
- Fate GO istantly closes, opens the default mail app and prompts the "Error 61" in the mail, other errors have nothing to do with magisk.
- Latest version of Magisk Dev
- Magisk Hide enabled and Fate GO ticked in the list
- Magisk Manager hidden
- Check if other apps (Like GPay for example) find Magisk/Root or not
- Safetynet "full" passes
- No Xposed
- Running the uninstaller of magisk makes Fate GO working normally
- Always write: ROM, Kernel, Magisk Version, Fate GO version and region (NA, CN, JP ecc...)
Thanks in advance to everyone that will help with this problem or share their experiences or thoughts, and if someone else would like to test itself you can find the apk on APKPure if it's no present on play store.
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Sent from my Pixel using Tapatalk
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Chocobubba said:
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Click to expand...
Click to collapse
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Niiya said:
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Click to expand...
Click to collapse
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Killua96 said:
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Click to expand...
Click to collapse
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Niiya said:
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Click to expand...
Click to collapse
Btw my bank app doesn't work with and without magisk, anyway the problem is that FGO was advised as playable since September and it's not...
Hello, i get some problems like this. My device - Asus me302kl with Nitrogen os 8. I install magisk (canary), hide fate app, and rebuilt magisk with new package name. After killing process in app settings i can play, but after some time (i think when magisk has autolaunch) fate found magisk and i recieve error 61. After this I need restore and rebuild package again, for normal fgo launch.
Now i try something for stable result.
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Killua96 said:
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Click to expand...
Click to collapse
And in fact now magisk is not detected at all by FGO, finally...!
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Niiya said:
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Click to expand...
Click to collapse
If you have added fgo to the magisk hidelist, and have hidden MagiskManager trough the option in the settings then you could try to use the ProcGate apk and see if the proc bug is the issue.
FGO works well now, no errors or anything. This is great because I use root regularly, but wasn't willing to let go of it.
:victory:
I have android 6, well I can always use an emulator.
Just tried this game and can't open just white screen and there some gmail option
-AEX N 7.1
-latest mgisk cannary
-3.10.108
-latest NA
I can play dragalia lost just fine with magisk hide,this game sure annoyingxD
Edit: Oookay its weird,I just reboot my device and it work like a charmxD
Niiya said:
I have android 6, well I can always use an emulator.
Click to expand...
Click to collapse
Check with procgate app if you have leaks, if there are unfortunately there aren't solutions atm on Android versions bellow nougat...
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
AsakuraVN said:
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
Click to expand...
Click to collapse
What error code you have last? 61?
Try hide MM from framework+google apps
Lordische said:
What error code you have last? 61?
Try hide MM from framework+google apps
Click to expand...
Click to collapse
Already tried. Right now it's 60.
Guilhermex12 said:
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
Click to expand...
Click to collapse
Yes. Poke GO and FGO work with Magisk - at least with 17.4 and 18.1. i played Fate a few days ago, no problem on Pie.
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
caniko2 said:
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
Click to expand...
Click to collapse
I have the same issue with Santander Wallet. But SafetyNet is intact and I am able to use GPay.
Please share if you find a solution elsewhere.
Any solution to this?
My banking app checks if ADB debugging is enabled, but it still says "root detected". If I disable ADB debugging, it works fine
Sent from my MI 5 using Tapatalk
Same thing with the Barclays banking app. It was working fine until a few days ago with Magisk Hide. Now, the app sends a superuser request and no matter what you choose (grant or deny), it detects the phone is rooted and gives a message that it doesn't support rooted devices. Also, the app hasn't updated since January 4th, so something else must have changed.
Edit. Using this method worked for me https://forum.xda-developers.com/apps/magisk/santander-app-custom-rom-root-device-t3794753/post77321403#post77321403
I use two apps which are detecting root in my OnePlus 6 with OOS Beta 11 and Magisk 18:
VR-SecureGo
Die TK-App
Same problem
Well, I am not using a "Banking" app. But can say that an install of the Marlboro app.!!!
Install was ok. However, when starting app, it said that my phone was rooted! Then it stated that it can not be used on my devise and shut down. Will not actually restart now!
Devise - Samsung Galaxy S5, On Lineage 15.1 latest build, as well as Unofficial 16.0 build. With or with out SmartPack Kernel.
Both using the Latest Magisk 8.1!
(Yes, no Exposed used) just a few modules...
P. S. I can say, in 7.0-7.3 this was NOT an issue.
My only, other issue with 8.0 an 8.1.... Extremely hard to use the 2nd Partition (formatted - Ext4) Using Link2SD Plus! Can say didn't not have this on on prior Versions.
Still trying to fix this, but nothing yet (working many hours this past week) and nothing to stick... Yet!
Tanx for letting me blow off some steam on this...
Anyone that's having issues with root detecting apps could give the new MagiskHide implementation a try (it's been rewritten from scratch). Would be interesting to know if there's any improvement... Currently only found in the Canary builds (as of now at build 18108), but will of course find it's way to a stable release eventually. Having more users test the new implementation before a stable release is of course always nice though...
I tried beta manager, same thing. Unable to pay with Google pay.
Tesco pay+ now detects root as of today. It is enabled in Magisk Hide. App last updated 31st Jan but it was working fine last weekend - Google changed detection possibly?
if you have warez apps (lucky patcher, freedom, creehack, aptoide, acmarket, gameguardian etc) installed it may detect and uses 'root detected' as a generic message
My phone is One Plus 5T with bootloader unlocked and using the BETA latest OxygenOS.
Nothing was updated and from one day to another my google pay does not work anymore. Tried to add the card again, and it told me about "my phone is altered in some ways"
Before magisk was doing the job. Looks like we need to wait for some updates. I am amazed about the only few entries I found in internet about that.
caniko2 said:
I am using the DnB online banking app. The new version of the app, released a few days ago, detects magisk root with hide turned on. Safetynett is also intact. Thought it may be of interest; I will be using the older version for now.
Link to app page:
https://play.google.com/store/apps/details?id=no.apps.dnbnor
Click to expand...
Click to collapse
I got DNB running with magisk Canary , use magisk hide and and systemles hosts in magisk settings .
stian230 said:
I got DNB running with magisk Canary , use magisk hide and and systemles hosts in magisk settings .
Click to expand...
Click to collapse
Does it still work for you? I keep getting phone is rooted with latest Canary build.
SLAiNTRAX said:
Does it still work for you? I keep getting phone is rooted with latest Canary build.
Click to expand...
Click to collapse
It works for me ?. Running magisk canary and DNB app .
fleischbanane said:
I use two apps which are detecting root in my OnePlus 6 with OOS Beta 11 and Magisk 18:
VR-SecureGo
Die TK-App
Click to expand...
Click to collapse
VR SecureGo works for me with this instruction:
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
pollonhokairos said:
VR SecureGo works for me with this instruction:
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
Click to expand...
Click to collapse
Thank you very much. With Magisk 19 I have zero issues!
Salty Wagyu said:
Tesco pay+ now detects root as of today. It is enabled in Magisk Hide. App last updated 31st Jan but it was working fine last weekend - Google changed detection possibly?
Click to expand...
Click to collapse
I've similar issue, OnePlus 6, latest stock ROM, latest Magisk (v19.2), it detects the root... Can someone suggest me something to resolve this?
Has anyone else than Stian got DNB to work? I am using magisk 19.3 and it's not working.
Google Pay: "You can't pay in Stores with this device" on Unrooted LineageOS 16
Hi. I have issues paying with Google Pay since April of this year. It worked before and without any modifications to the System, it stopped working since the beginning of this month.
I had my Phone rooted ages ago with Magisk but have removed it in January since it was causing the same issue I have now. Only that my Phone is now unrooted. The Phone is Google Play Protect Certified and still passes all the SafetyNet checks (since it's not rooted, this should be obvious)
My Phone is Running LineageOS 16 since March and (as I said before) it was working even with LOS 16. It just stopped working for no appearant reason.
Anyone having a similar Problem, or any idea on how to fix it?
Chickenbreadlp said:
Hi. I have issues paying with Google Pay since April of this year. It worked before and without any modifications to the System, it stopped working since the beginning of this month.
I had my Phone rooted ages ago with Magisk but have removed it in January since it was causing the same issue I have now. Only that my Phone is now unrooted. The Phone is Google Play Protect Certified and still passes all the SafetyNet checks (since it's not rooted, this should be obvious)
My Phone is Running LineageOS 16 since March and (as I said before) it was working even with LOS 16. It just stopped working for no appearant reason.
Anyone having a similar Problem, or any idea on how to fix it?
Click to expand...
Click to collapse
If you had been following the LOS thread you would already have your answer. LOS no longer passes Safetynet out of the box. You need a Custom Kernel.
Or use Magisk again.
Bear in mind that LOS is never supposed to pass Safetynet out of the box. It goes against their policy. The last few months have been a gift, but this is simply a return to normal condition for LOS. Custom Kernel or Magisk. Same as it always was.
Dirk said:
If you had been following the LOS thread you would already have your answer. LOS no longer passes Safetynet out of the box. You need a Custom Kernel.
Or use Magisk again.
Bear in mind that LOS is never supposed to pass Safetynet out of the box. It goes against their policy. The last few months have been a gift, but this is simply a return to normal condition for LOS. Custom Kernel or Magisk. Same as it always was.
Click to expand...
Click to collapse
So the only way of getting Google Pay consistently working on LOS is by using a custom Kernel? I've quit Magisk because it was causing Problems.
Chickenbreadlp said:
So the only way of getting Google Pay consistently working on LOS is by using a custom Kernel?
Click to expand...
Click to collapse
Yes.
The goto Kernel used to be Caesium, but development has stopped again. The last build will work fine though, and was tested a few days ago on LOS. Safetynet passed as expected. There are of course other Kernels and other ROMs. crDroid is based on LOS, and passes Safetynet out of the box.
Just remember to clear Data and Cache on Play Store after flashing the Kernel. Google Pay etc will work fine afterwards.
Or if you build your own LOS builds you can simply let your build patch this in LOS kernel. [emoji4]
Also, most problems with Magisk gets solved by adding those apps to MagiskHide.
Skickat från min ONEPLUS A3003 via Tapatalk
hello!
just joined this super cool community as I am experiencing some issue since I've update my Mi 11 Ultra to v.12.5.6. A few days after the new firmare, I've woken up to a notification from Google Pay that my phone was rooted. Indeed, my safetyNet check now fails. Let me tell you, my Magisk has been working flawlessly up till the update.
I have noticed 2 weird things:
- all other apps do work except GPay
- there something weird in the Magisk UI because there is little to none settings and all my modules seem to have disappeared and there isn't seem to be a way to get them back.
Posting some pictures.
Has anyone else had the same issue?
thanks folks
Seems to me that Magisk got uninstalled ("Installed: N/A").
I suggest to put the phone in fastboot mode and reflash the Magisk patched boot.img again.
I've had the same thing on my POCO F3, with latest MIUI 12.5.x.
Thank you! Yes that's very strange. I'll try that and will let you know. It would just be annoying if it's something that needs to be done at ever update