Database Develop

Magisk 16 Now TV detecting root

Has anyone else experienced issues with nowtv detecting root.
Now TV updated the app recently was running on magisk 15.3 fine, then started to detect a modified boot img. Its on a Samsung Galaxy a6.
I wiped the tablet and started fresh last night, stock rom, upgraded to Magisk 16, get the same message again on now tv, that its a modifed boot img.
Have it hidden within magisk hide (this used to work)
All other streaming services are working fine (Netflix, amazon)
It passes the safety net test fine.

wookieg said:
Has anyone else experienced issues with nowtv detecting root.
Now TV updated the app recently was running on magisk 15.3 fine, then started to detect a modified boot img. Its on a Samsung Galaxy a6.
I wiped the tablet and started fresh last night, stock rom, upgraded to Magisk 16, get the same message again on now tv, that its a modifed boot img.
Have it hidden within magisk hide (this used to work)
All other streaming services are working fine (Netflix, amazon)
It passes the safety net test fine.
Click to expand...
Click to collapse
Having the same issue this end too if anyone can point us in the right direction.

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
If none of that works, maker sure to provide logs (it's described in the link).

I fixed it by repackaging/hiding the magisk app

Sorry, noob question but what do you mean?

Aaronmod said:
Sorry, noob question but what do you mean?
Click to expand...
Click to collapse
Open Magisk Manager --> Settings --> Tap On Hide Magisk Manager

liboemcrypto disabler
Hi, I found the final solution. The liboemcrypto disabler module is for us. I used it on Redmi 5 Plus with OmniROM 8.1 20180812 and Magisk 16.6. I tried everything and it seems to me crazy in SafetyNet, which perhaps does not even have to do. Then I installed the module in question, restarted and everything works perfectly. Thanks to "ianmacd".
This is the module link: https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393

ooonea said:
Hi, I found the final solution. The liboemcrypto disabler module is for us. I used it on Redmi 5 Plus with OmniROM 8.1 20180812 and Magisk 16.6. I tried everything and it seems to me crazy in SafetyNet, which perhaps does not even have to do. Then I installed the module in question, restarted and everything works perfectly. Thanks to "ianmacd".
This is the module link: https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393
Click to expand...
Click to collapse
It still works now, just tried with NowTV version 10.7.0 and it works, thanks man!

ooonea said:
Hi, I found the final solution. The liboemcrypto disabler module is for us. I used it on Redmi 5 Plus with OmniROM 8.1 20180812 and Magisk 16.6. I tried everything and it seems to me crazy in SafetyNet, which perhaps does not even have to do. Then I installed the module in question, restarted and everything works perfectly. Thanks to "ianmacd".
This is the module link: https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393
Click to expand...
Click to collapse
Hi, it doesn't work on my phone with LineageOS 14.1 on it.

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

[Discussion] Fate Go Magisk Discussion Thread

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.

Magisk root detected by app

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.

Sky go help needed to hide root with magisk

On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks

hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk

vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.

hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader

hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks

somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).

h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine

yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?

Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy

beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.

Hast everyone a sollution for running the sky Go App on rooted phones?

Skygo doesnt Work... hast anyone a sollution?

eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com