Related
So now Netflix is out of Google Playstore, any clue how magisk going to work around this issue?
Thanks!
Most users can get Netflix, and other apps that use the same check, back by making sure SafetyNet passes (Magisk Hide), clearing data for the Play store and open it up again. A reboot is usually necessary before the apps show up and sometimes it takes a while. A few users have reported that it doesn't work, but I can consistently replicate this on a Nexus 6, Nexus 6P and a OnePlus 3T on different ROMs.
You can check in the Play store settings, at the bottom, if your device is certified or not. SafetyNet pass = certified.
Got Netflix working on the latest version with root using magisk... No problem there
Using Nexus 6p
Sent from my Nexus 6P using Tapatalk
Even if you are not able to get it through the Play Store, there are other ways to get the latest version of an app, like apkmirror. This check doesnt prevent the installation or usage of those Apps, it just hides them on the Play Store.
nemexs said:
So now Netflix is out of Google Playstore, any clue how magisk going to work around this issue?
Thanks!
Click to expand...
Click to collapse
As long as the SafetyNet checks are okay, the store and most apps don't know about root.
The one exception to this and I can't figure it out is an application called [email protected] by Mobile Iron.
Not matter what I do, it can see the compromised status of the phone.
Also Android Wear on my watch can detect the status so Android pay on my watch won't work, not matter what I do.
Yes, I've tried Magisk Hide on just about everything.
Didgeridoohan said:
Most users can get Netflix, and other apps that use the same check, back by making sure SafetyNet passes (Magisk Hide), clearing data for the Play store and open it up again. A reboot is usually necessary before the apps show up and sometimes it takes a while. A few users have reported that it doesn't work, but I can consistently replicate this on a Nexus 6, Nexus 6P and a OnePlus 3T on different ROMs.
You can check in the Play store settings, at the bottom, if your device is certified or not. SafetyNet pass = certified.
Click to expand...
Click to collapse
Interesting. I never noticed that before. However I just checked and my Play Store settings says Uncertified. SafetyNet passes both basic integrity and cts profile match. Netflix appears and downloads via Play Store for me. I even cleared data on the Play Store and rebooted as suggested. Still uncertified, weird.
RoyJ said:
Interesting. I never noticed that before. However I just checked and my Play Store settings says Uncertified. SafetyNet passes both basic integrity and cts profile match. Netflix appears and downloads via Play Store for me. I even cleared data on the Play Store and rebooted as suggested. Still uncertified, weird.
Click to expand...
Click to collapse
Interesting. Since your device can pass SafetyNet I'd expect Netflix (etc) to appear in the Play store, but from reports (and testing) you should first have to make it show as certified. Again: interesting...
About not being able to get "certified": Do you have multiuser active? If so I believe you'll have to clear Play store data for all users before it can show as certified.
Didgeridoohan said:
Interesting. Since your device can pass SafetyNet I'd expect Netflix (etc) to appear in the Play store, but from reports (and testing) you should first have to make it show as certified. Again: interesting...
About not being able to get "certified": Do you have multiuser active? If so I believe you'll have to clear Play store data for all users before it can show as certified.
Click to expand...
Click to collapse
Nope, just me. Can you get your play store to switch being certified or not by enabling and disabling hide? I'm wondering if I was on a ROM or something that was uncertified and it just permanently tagged my device as such?
RoyJ said:
Nope, just me. Can you get your play store to switch being certified or not by enabling and disabling hide? I'm wondering if I was on a ROM or something that was uncertified and it just permanently tagged my device as such?
Click to expand...
Click to collapse
Yes. I can 100% replicate getting my devices to certified or uncertified status by enabling or disabling Magisk Hide (passing or failing SafetyNet).
RoyJ said:
I'm wondering if I was on a ROM or something that was uncertified and it just permanently tagged my device as such?
Click to expand...
Click to collapse
You don't get permanently tagged. My device says uncertified until I enable Magisk hide, clear play store data and reboot. What device do you have and are you using a custom kernel?
Still no go for me. SELinux is set to enforcing, USB debugging disabled, play store certified, passed safetynet, used magisk hide on every apk that had the word "Google" on it, I have rebooted, waited, clear play store data (still certified), waited some more, rebooted again, waited some more... Idk what else to do.
Idc about Nexflix. I am however concerned that other apps will use the same detection method.
It working on mine. I can download and use Netflix.
Pure Nexus.
Franco Kernel.
Magisk 12.
Passes SafetyNet and is Google Playstore Certified.
Edit:
Just clean flashed SAOSP with Franco and Magisk 12.
Still passing SafetyNet but Google Playstore now reports Uncertified. BUT! I still can see, download and use Netflix.
Checking the play store in the magisk hide list worked for me.
mkhcb said:
Still no go for me. SELinux is set to enforcing, USB debugging disabled, play store certified, passed safetynet, used magisk hide on every apk that had the word "Google" on it, I have rebooted, waited, clear play store data (still certified), waited some more, rebooted again, waited some more... Idk what else to do.
Idc about Nexflix. I am however concerned that other apps will use the same detection method.
Click to expand...
Click to collapse
I'm also having this issue on my OnePlus One running unofficial Lineage build. Device shows certified, safetynet passes, magisk hide etc..... still wont show up.
however, for my Nexus 7 tablet running the official lineage build configured the same way, it shows up..
JRJ442 said:
You don't get permanently tagged. My device says uncertified until I enable Magisk hide, clear play store data and reboot. What device do you have and are you using a custom kernel?
Click to expand...
Click to collapse
I have the same situation with my Droid Turbo, I am on latest ROM for my device, MM 6.01 with a kernel to hide unlocked boot. I am on Magisk V12, Safetynet passes, I can see Netflix in playstore, I can also use Android Pay it is functional. Yet Google Playstore says uncertified.
Edit: I cleared playstore cash, rebooted, same result. I added playstore to hidden programs, rebooted same result.
i am on ROM Tesla with Arsenix Kernel on my Oneplus X and passing safety net with Magisk 13 (BETA) and also getting verified in play store can download Netflix but if i start it it says uncompatible with your device. Any suggestions ? should i try Magsik 12 ?
I am also experiencing this.
My OnePlus One running Sultan's unofficial lineageOS with magisk v13 passes safetynet, it also shows certified in google play, android pay works, etc.... but no netflix in gogole play....
My Nexus 7, rooted with magisk v13, it does show up.
My OnePlus 5, official OOS with magisk v13 passes safetynet, it also shows certified in google play, android pay, etc..... it DID have netflix, HOWEVER.... I played around a bit with different magisk versions and the latest magisk beta was not passing safetynet.... I wiped my phone and went back to using my previous setup but now no mater what I do, I can't get netflix to show back up.
I'm going to agree with others saying that their device gets flagged, because I believe this is what I am also experiencing with my OP5
EDIT: I cleared play store cache/data (which I have already been doing) and then restarted the phone before going back into the play store, that seemed to fix it for my OP5
I used to find netflix with magisk hide now it dont show anymore even through my safatynet is bypassed and phone is showing certified on playstore ...... Cleaned everything and restarted my phone múltiple times yet no netflix... Anyboby got a fix?
lexie90 said:
I used to find netflix with magisk hide now it dont show anymore even through my safatynet is bypassed and phone is showing certified on playstore ...... Cleaned everything and restarted my phone múltiple times yet no netflix... Anyboby got a fix?
Click to expand...
Click to collapse
There is always apkpure. An alternative to playstore with updates. That's how I got netflix back after my last clean flash since I forgot to back it up
NOt really a problem but Magisk Hide is on and SafetyNet check is a pass, but my play store shows uncertified.
I can still download Netflix and use it like normal.
EDIT; Clearing Play Store data seemed to fix it
Introduction
Fix UNCERTIFIED status in Play Store for OP2/OP3/Note4 and maybe more.
Uncertified status may lead to some restrictions on specific apps (saying Netflix). It is not only judged by SafetyNet status but also some build props in your ROM. So this module does NOT may or may not help you to pass SafetyNet.
More specifically, to pass SafetyNet, if you are on a custom ROM/Kernel,
a patch in your kernel like this is REQUIRED (maybe optional because of MagiskHide?)
If you are on stock ROM or other ROMs that enabled dm-verity, never touch system part.
SELinux is always enforcing
Installation
Search for "Play Store Visa" in Magisk Manager or download at Github.
Support for New Devices
This module made it by injecting proper build fingerprint properties per device, most commonly ro.build.fingerprint. So device support is highly dependent on a working build fingerprint from a certified stock ROM. You can test and find a combination by your own and add to service.sh accordingly.
I used to find those fingerprints hard to search around. Although one fingerprint may work for all devices of a kind, but people barely shares it. Pull requests are very welcomed so we may help one another!
Define: a working fingerprint
For the time being, I test the prop edits working by:
clean data of Play Store
reboot for the module to apply (or invoke resetprop through adb)
open and check certification status in settings. (may have some delay)
search for Netflix in Play Store.
If you can see Netflix in search results after wiping store's data, then your props edits are good to go!
Enjoy
Q&A
Q:
Only for OP2/OP3/note4? Not support for other device?
A:
To support other device, we need the value of `ro.build.fingerprint` from a stock ROM. I don't own other devices so I may not have chance to extract it. Contributions are welcomed, and I may search for other useful ones in the future..
Q:
What's the difference between this module and this one?
A:
We both solved part of the problem, see my explanation below. I'm happy to contribution my parts, if necessary, to prevent reinventing the wheels.
XDA:DevDB Information
Play Store Visa, App for all devices (see above for details)
Contributors
ttimasdf
Source Code: https://github.com/Magisk-Modules-Repo/playstore_certification_bypass
Version Information
Status: Beta
Created 2018-03-26
Last Updated 2018-03-31
Only for OP2/OP3/note4?
Not support for other device?
What's the difference between this module and this one?
ttimasdf said:
More specifically, to pass SafetyNet, if you are on a custom ROM/Kernel,
a patch in your kernel like this is REQUIRED
If you are on stock ROM or other ROMs that enabled dm-verity, never touch system part.
SELinux is always enforcing
Click to expand...
Click to collapse
That patch you're talking about is unnecessary if you use Magisk. MagiskHide already changes ro.boot.verifiedbootstate to "green".
MagiskHide also hides a permissive SELinux, so keeping it enforcing isn't necessary to pass SafetyNet if you use Magisk. Although keeping SELinux enforcing is highly advisable...
I'm also curious as to what observations you've made about SafetyNet and a certified Play Store. From my own (very light) research I've found that it relies on SafetyNet. Not directly, but the CTS profile matching part. From the link to Google support in the OP:
If your device is uncertified, Google doesn’t have a record of the Android compatibility test results.
Click to expand...
Click to collapse
If your device hasn't passed the Android compatibility test, it won't be reported as certified in the Play Store, and it won't pass SafetyNet. On the other hand, if you pass SafetyNet, your device has passed the compatibility test, and then it'll also be certified in the Play Store.
Would love the hear your findings if you're up to sharing.
---------- Post added at 13:27 ---------- Previous post was at 13:25 ----------
abacate123 said:
What's the difference between this module and this one?
Click to expand...
Click to collapse
Quite similar in that we both change the device fingerprint. We go about it a bit different, and mine has a couple of other features as well.
My play store don't have "Device certification" tab :'(
zerlkung said:
My play store don't have "Device certification" tab :'(
Click to expand...
Click to collapse
Can you find and install Netflix? If so, your device is certified. If not, it's uncertified.
Was this created in response to Google blocking GApps on uncertified devices/roms? If so then that is great, I didn't expect a solution to come out so fast.
That being said, based on current reports it would not be hard to create a universal "coyote mode" by getting the existing ro.build.fingerprint and then modifying the build date portion so that it is before March 2018. Said mode would not make the device certified if it wasn't already but would allow GApps to run normally thus the term "coyote mode" (a coyote is a person who smuggles other people across the border).
nl3142 said:
Was this created in response to Google blocking GApps on uncertified devices/roms? If so then that is great, I didn't expect a solution to come out so fast.
Click to expand...
Click to collapse
Google is not blocking gapps for custom roms. At least not yet.
In fact, you can actually register an uncertified device using a custom rom (it says android id, but it'll accept the imei number) here: https://www.google.com/android/uncertified/
abacate123 said:
Google is not blocking gapps for custom roms. At least not yet.
In fact, you can actually register an uncertified device using a custom rom (it says android id, but it'll accept the imei number) here: https://www.google.com/android/uncertified/
Click to expand...
Click to collapse
Though since the Android ID is regenerated after either every factory reset (pre-Oreo) or even every boot (Oreo) it will be pretty easy to run into the 100 Android ID limit.
nl3142 said:
Though since the Android ID is regenerated after either every factory reset (pre-Oreo) or even every boot (Oreo) it will be pretty easy to run into the 100 Android ID limit.
Click to expand...
Click to collapse
IMEI fellow...
abacate123 said:
IMEI fellow...
Click to expand...
Click to collapse
Which wifi only devices like tablets don't have, so obviously that isn't going to work.
Cbk | Unknown said:
Only for OP2/OP3/note4?
Not support for other device?
Click to expand...
Click to collapse
As said above, to support other device, we need the value of `ro.build.fingerprint` from a stock ROM.
I don't own other devices so I may not have chance to extract it. So we only need some contributions
abacate123 said:
What's the difference between this module and this one?
Click to expand...
Click to collapse
Oh, I know that module but didn't read it's doc until you mentioned. In a word, the same solution for different questions.
My problems is, my ctsProfile is True for my phone but I cannot get Netflix from the store. But after some props edit it just works so I published my solution. Maybe I could make a PR into it
Didgeridoohan said:
That patch you're talking about is unnecessary if you use Magisk. MagiskHide already changes ro.boot.verifiedbootstate to "green".
MagiskHide also hides a permissive SELinux, so keeping it enforcing isn't necessary to pass SafetyNet if you use Magisk. Although keeping SELinux enforcing is highly advisable...
I'm also curious as to what observations you've made about SafetyNet and a certified Play Store. From my own (very light) research I've found that it relies on SafetyNet. Not directly, but the CTS profile matching part. From the link to Google support in the OP:
If your device hasn't passed the Android compatibility test, it won't be reported as certified in the Play Store, and it won't pass SafetyNet. On the other hand, if you pass SafetyNet, your device has passed the compatibility test, and then it'll also be certified in the Play Store.
Would love the hear your findings if you're up to sharing.
---------- Post added at 13:27 ---------- Previous post was at 13:25 ----------
Quite similar in that we both change the device fingerprint. We go about it a bit different, and mine has a couple of other features as well.
Click to expand...
Click to collapse
Your project goes a lot further than mine but I didn't notice it as a key to my problem :silly:
From my finding, SafetyNet ctsProfile seems to rely solely on ro.build.fingerprint and the "certified" status does the same. The rom I used on Note4 patched the fingerprint and passed SafetyNet from the very beginning.
But Play Store seems to have more verifications on other build props, in my case, ro.build.version.release, ro.build.version.incremental to match the ones in fingerprint. The patch I used for OP3 did not patched them (for I have no time to inspect) so I passed SN, get certified, but still cannot search for Netflix. I don't know it's a more strict policy enforced by Netflix or Google but it makes the certification imperfect. Maybe we shall look into this together
ttimasdf said:
Oh, I know that module but didn't read it's doc until you mentioned. In a word, the same solution for different questions.
My problems is, my ctsProfile is True for my phone but I cannot get Netflix from the store. But after some props edit it just works so I published my solution. Maybe I could make a PR into it
Your project goes a lot further than mine but I didn't notice it as a key to my problem :silly:
From my finding, SafetyNet ctsProfile seems to rely solely on ro.build.fingerprint and the "certified" status does the same. The rom I used on Note4 patched the fingerprint and passed SafetyNet from the very beginning.
But Play Store seems to have more verifications on other build props, in my case, ro.build.version.release, ro.build.version.incremental to match the ones in fingerprint. The patch I used for OP3 did not patched them (for I have no time to inspect) so I passed SN, get certified, but still cannot search for Netflix. I don't know it's a more strict policy enforced by Netflix or Google but it makes the certification imperfect. Maybe we shall look into this together
Click to expand...
Click to collapse
Hm... I'm wondering. From what I've tested and seen reported, all that is needed is to pass SafetyNet for your device to be certified. On that we're on the same page though.
I've also seen reported (and experienced) that even after getting your device certified in the Play Store, it can take several reboots and/or up to a whole day before the apps that rely on the certification status (Netflix, etc) to show up/install. Could it be that you were simply experiencing a delay when you couldn't install Netflix? It's possible that any other props are part of the new Gapps blocking on uncertified devices, but somehow I don't think so... I will do more research and report back.
And as a side note, about the CTS profile test:
Changing the device fingerprint is only one part of making a device pass. That causes the devices to be recognised as a certified device with trusted software, even if the manufacturer hasn't certified the device or if you've installed a custom ROM (both would normally cause ctsProfile to be false). It will also report false if your bootloader is unlocked or if you've rooted your device, but both of these will be taken care of by MagiskHide. Xposed will of course also cause issues, but for the ctsProfile check this can actually be fooled by the No Device Check Xposed module. It'll still cause a basic integrity failure though, and be detected in other ways.
I'll be back...
Didgeridoohan said:
Hm... I'm wondering. From what I've tested and seen reported, all that is needed is to pass SafetyNet for your device to be certified. On that we're on the same page though.
I've also seen reported (and experienced) that even after getting your device certified in the Play Store, it can take several reboots and/or up to a whole day before the apps that rely on the certification status (Netflix, etc) to show up/install. Could it be that you were simply experiencing a delay when you couldn't install Netflix? It's possible that any other props are part of the new Gapps blocking on uncertified devices, but somehow I don't think so... I will do more research and report back.
And as a side note, about the CTS profile test:
Changing the device fingerprint is only one part of making a device pass. That causes the devices to be recognised as a certified device with trusted software, even if the manufacturer hasn't certified the device or if you've installed a custom ROM (both would normally cause ctsProfile to be false). It will also report false if your bootloader is unlocked or if you've rooted your device, but both of these will be taken care of by MagiskHide. Xposed will of course also cause issues, but for the ctsProfile check this can actually be fooled by the No Device Check Xposed module. It'll still cause a basic integrity failure though, and be detected in other ways.
I'll be back...
Click to expand...
Click to collapse
Thanks for the hint. I do a few tests today. My module seems to be broken today but after added Play Store and `com.google.android.gsf` to MagiskHide list it works again.
And most interestingly, the fingerprint for my Note4 from the ROM seems to be blacklisted by Google.
I wiped data, disabled module, reboot. Device become uncertified and even cannot pass `basic integrity`. wipe-enable-reboot become certified and able to download again.
It's a cat and mouse game after all:angel:
Also I tested for the "delay" you mentioned. After a wiped reboot, tested 2 out of 3 times the Netflix shows in result. However, whether it can start download still depends on the certification status. If uncertified, download will say error after some time. With module enabled, the download succeeded normally. So Netflix is the most timely and accurate way to speak if your device is certified.
For I have not yet used any apps that check SafetyNet status at runtime, maybe I'll check it later.
Profound Thanks For You. Your Module Was Useful To Make A Specified One For My Phone. :good:
After installing this module, I get force close popup in most Google and non Google apps. FYI, I also have Youtube Vanced installed via Magisk module. I uninstalled the module but I still get the same popups. Also, the device remains certified. Is there any way to actually undo everything? From what I can understand, my device should remain uncertified for everything to work.
GeorgePr said:
After installing this module, I get force close popup in most Google and non Google apps. FYI, I also have Youtube Vanced installed via Magisk module. I uninstalled the module but I still get the same popups. Also, the device remains certified. Is there any way to actually undo everything? From what I can understand, my device should remain uncertified for everything to work.
Click to expand...
Click to collapse
This module merely changed some build props, if and only if your device is supported. Theoretically it should not mess other things around. Check your logcat if there's anything worth notice and clear app data if necessary
ttimasdf said:
As said above, to support other device, we need the value of `ro.build.fingerprint` from a stock ROM.
I don't own other devices so I may not have chance to extract it. So we only need some contributions
Click to expand...
Click to collapse
I made a screenshot from my Pixel 8.1 stock - april security patch
Maybe can help for pixel support :good:
Sent from my Google Pixel using XDA Labs
It is working on my Nexus 7 2013 WiFi tablet. Running Flo classic asop 8.1 r28 May 2018 version with Ground Zero Gapps. Did the clear data (clear cache alone didn't work) rebooted and open Playstore, my apps updates and installed tabs show zero item. A few hours later, check again and I get a Certified in Playstore settings.
Thank you, good job! :good:
Also trying on OnePlus One running AEX 8.1 v5.5. currently updates and installed tabs are also zero item. Going to let it be and see if it will populate over time. Under Playstore version build number, nothing under. Before installing Visa module, it say uncertified.
Library tabs on both show my history of apps.
The new Fortnite Game for Android detects system modifications like having root or an unlocked bootloader, in addition to that it makes a SafetyNet check, which means no Fortnite for root users....
I know, it's just a game but I thought you should know, I found out about it today after indtalling it.
I can't even install it. The installer keeps crashing on me!
He "block" user having Root/Not Safety Pass, don't "Ban", not the same thing
If you unroot, clean install your device stock, you can play isn't it?
Wouldn't install it anyway tbh, purely for them circumventing the Play Store, that's highly dangerous, there'll be all sorts of malicious packages out there pretending to be legit copies. Plus PUBG4LYFE!
Like Snapchat, Netflix, Pokemon Go etc... Its not the first time but we live in the age of Magisk
Pho3nX said:
He "block" user having Root/Not Safety Pass, don't "Ban", not the same thing
If you unroot, clean install your device stock, you can play isn't it?
Click to expand...
Click to collapse
I got the following message "after too many attempts your account might get banned"
freaky2xd said:
I got the following message "after too many attempts your account might get banned"
Click to expand...
Click to collapse
Yes you are banned BECAUSE you have try to connect to the Fornite server so many times, not because you have try once time to connect with a device rooted
And i think it's a temporary ban (some minutes/hours)
i have tried this and it's working for rooted users
https://highonandroid.com/android-howtos/how-to-run-fortnite-on-any-rooted-android/
djsubterrain said:
Wouldn't install it anyway tbh, purely for them circumventing the Play Store, that's highly dangerous, there'll be all sorts of malicious packages out there pretending to be legit copies. Plus PUBG4LYFE!
Click to expand...
Click to collapse
I mean, losing 30% of potentially ~100 millions $/mo from mobile just to stay on Google Play is a stupid business decision. It's simple enough: you want the game, you go on Epic's website. If people get caught downloading another version of the APK that contains a virus, they're dumb (in the end, it's their problem).
This forum is meant for people who are getting locked out of their accounts due to "3rd Party Plugins or Applications"
We need to stop this from happening so share your experiences and thoughts on the matter.
I have 2 devices: a Nexus 6P running Pie (Pixel Experience) and a Pixel 3XL on the stock Pie rom. Both are rooted with Magisk Canary builds and both have Magisk Hide turned on. Snapchat never detects root on the Nexus but ALWAYS detects it on the Pixel. I've even repackaged Magisk on the Pixel but that doesn't help. I've read that it's easier for apps to detect root on A/B partition devices so maybe the newer, updated Snapchat apps have code to detect it. When I have time, I'll try an old version and see if it works...
Note that I don't believe Snapchat bans just by detecting root. It is detecting certain apps that are somehow triggering it. If you check the list of apps that you have given permission for superuser, it would be one of those. The app that I had that was triggering Snapchat was an app named app ops. I had downloaded it and just giving it permissions alone was getting me banned on Snapchat. I think this problem only affects users running Oreo or higher for whatever reason. I myself had an old phone running marshmallow with app ops and never experienced a ban. I don't think that any of the people reporting the problem had anything lower than Oreo. If you have somehow discovered the app causing your problems, uninstalling it may not fix your problem. I had to wipe my phone in order to fix it because I was still receiving bans despite uninstalling the app that was causing my problems
I've never installed app ops so that's not my problem.
As for A/B partitioning, I'm on a Samsung galaxy Note 8 and it didn't come out with this on my device so yeh ?
The main thing I found out that I had to do, was repackage the manager and I haven't been banned for the last 4 days
I am on the S8 plus and was locked out for 12 hours before. Snapchat continued to lock me out even when I fully uninstalled magisk. I decided to clean install a different Rom which seemed to do the trick. A month later I decided to go back to my original Rom and guess what? Can't even login coz of some mod I think.
So I would say it depends on what mods you have installed yourself or packaged with the custom ROM.
Snapchat ban
I have same problem. Yesterday they gave me ban but i was unbanned with their site. But today they give me one more ban but now is for 24h ... anyone know how to fix snap or maybe hide root? S7 9.0 blackdiamond v3
Downloaded an early January 2019 version of Snapchat and signed up for a new account on my Pixel 3XL. All was good at first then I closed the app. When I tried to sign back in, I got the "problem connecting to server" error which requires an update to the most current version. I updated and after just a few hours, I got the "12 hour account locked" message for "3rd party apps". I've had Magisk Manager repackaged but that obviously didn't help. BTW, I have not repackaged Magisk on my Nexus 6P and it's still works. I found a comment by a user of the Bitmoji app (which I use on my Pixel but not my Nexus) that reported his Snapchat was locked by this app so I uninstalled it. We'll see how it goes when my 12 hour ban is up...
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
newkydawg said:
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
Click to expand...
Click to collapse
What apps have you given superuser? The app causing you problems is likely in that list
I had this happen before to me, i uninstalled edXposed and i was able to use snapchat even while on a 24 hour ban
iMystic said:
What apps have you given superuser? The app causing you problems is likely in that list
Click to expand...
Click to collapse
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
newkydawg said:
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
Click to expand...
Click to collapse
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
iMystic said:
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
Click to expand...
Click to collapse
Both my Pixel 3XL and Nexus 6P are running Android 9 rooted with Magisk Canary (19005). Both have the same apps with superuser rights. All this to say that Snapchat was working fine on both for months and for about the last 6 weeks, my Pixel 3 XL's account gets locked and my Nexus 6P does not.
Thanks for trying to help and glad you figured your problem out.
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
There are all the reasons why i purely stopping to use Snapchat, and also due to the fact that the application is so badly optimized for Android (even since the complete redesign of the application), in the end considering my use so irregular, I just uninstalled it, so no problem.
The time of Snapprefs and Snaptools was fun and funny, and especially less vicious as a concept than the basic one.
The good old days, but all good things must come to an end.
Rom said:
snip
Click to expand...
Click to collapse
It's what happens when a company becomes complacent and puts more effort into blocking modifications instead improving their terrible app.
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
I have got a problem, I have a Nokia 7 Plus, stock fw no changes at all!
And I keep getting banned... Support is a joke, I just get automatic replies...
The only reason i may have for getting bans is if snap scans the sd card, where I have magisk and roms files from other devices...
Any tips ???
newkydawg said:
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
Click to expand...
Click to collapse
I tried to follow the instructions but snapchat keeps saying there was a connection problem with the server.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
Does this mean that I can't use energized adblock magisk module? Do I have to use only the Snapchat adblock magisk module that you linked for any kind of adblocking on the device.
Thanks!
Basically what the title says. I know is not a big deal not having Netflix, Mario Run or Mario Kart (maybe more, those are the ones I use) on Play Store, but it is useful for auto updates.
AFAIK this happens when Play Store is not certified or detecting unlocked bootloader. Now, the thing is, I have everything hidden in Magisk, SafetyNet pass on both Magisk and this app:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
And weirdly enough, they seem to show up from time to time. How exactly does this work? Is it a play store detection thing, or is it some kind of flag on google's database? Because from the web, the apps shows as "not compatible" with my phone (when they don't appear on the phone, when they appear they are compatible on the web as well).
Sometimes I clear the data of play store and play services, but it doesn't seem to work, or seems to work randomly. I also tried clearing google services framework data, and it helped a couple of times, although I don't do that know, it mess up with apps and I learned that the hard way hehe
I'm just trying to figure out the google handling of this, and maybe a permanent solution from there.
I have a Xiaomi Mi 10 Pro with MIUI 12 (xiaomi.eu), Magisk and Xposed (phone's fingerprint is faked from an untouched phone and I can pass all the tests and use GPay, have Widevine L1... so all seems ok execpt for the apps things, which is beginning to bug me.
Thanks in advance.
I managed to get the apps showing on the store by doing these steps:
-Disabling internet connection on the phone
-Wiping play store and play services and rebooting
-Logging out from the device through the google security panel website
-Waiting 30min to 1h.
-Enabling internet again.
Then the apps were compatible again, as I can see on the play store web (not the app).
BUT, after 24h hours, or a bit less actually, they AGAIN appear as NOT COMPATIBLE on the play store web.
I'm trying to figure out why this may happen. Any clues? Thanks!
eXtremeDevil said:
I managed to get the apps showing on the store by doing these steps:
-Disabling internet connection on the phone
-Wiping play store and play services and rebooting
-Logging out from the device through the google security panel website
-Waiting 30min to 1h.
-Enabling internet again.
Then the apps were compatible again, as I can see on the play store web (not the app).
BUT, after 24h hours, or a bit less actually, they AGAIN appear as NOT COMPATIBLE on the play store web.
I'm trying to figure out why this may happen. Any clues? Thanks!
Click to expand...
Click to collapse
Hi, not sure if this answer will solve your problem, I'll post anyway.
I needed an app available only in US on time. So I got a VPN and connected it. But the app still wasn't available. So I force closed the app and cleared the data (only for the play store) and it worked perfectly.
I know you already cleared data. But this time, try those steps, maybe it'll work:
1- Enable Magisk Hide
2- Force Close Play Store
3- Clear only the Play Store Data
4- Launch the Play Store and see if it worked
Hope this will help.
Have a good day
Thanks for the answer, but I think the problem is a bit more complex than that. Yesterday I re-did all my steps again and I got this:
This time I have not turned off my phone since then, and the "compatibility" is maintained. I will try to stay another 24h with my phone on, then I will turn it off on tuesday night and see what happens.
Also, I think this post would be more useful in the Magisk thread, maybe? Could an admin move it there?
Thanks!
@eXtremeDevil
The "incompatible with your device" message is only shown if you open Google Play Store in PC's browser., not if you run Google Play Store on phone: there an incompatible app simply isn't listed.
Your issue has nothing to do with fact that Magisk is installed on your phone.
Download APK from another market. Open it with 7zip or any other unpacker. Look inside extracted file Manifest.xml for any app's restrictions.
jwoegerbauer said:
Your issue has nothing to do with fact that Magisk is installed on your phone.
Click to expand...
Click to collapse
Then where's the issue? Netflix is obviously compatible, is not a "real" incompatibility. Seems to me that google play store or services detect something on the phone then tell google servers to flag those apps as incompatible, therefore they are NOT shown on the phone and listed as "incompatible" on the web.
What I'm trying to do is to prevent this, prevent the phone from detecting whatever it is detecting and prevent my phone services to tell to google services/servers/database/whatever.
Because I can assure you, before rooting/Magisk this did NOT happen. So no, this is not a "real" incompatibility issue. Actually, as you can see on my screenshot, it IS compatible right now xD Who knows how many hours will this time last...
@eXtremeDevil
If your statement "SafetyNet passed and device certified" - what indicates Magisk gets not detected - is actually still true then turn on your mind.
That's the kind of help I'm asking here, AGAIN, my device is FULLY compatible with Netflix or Mario Run. I installed them through Play Store with no issues and I can run them with no issues. BUT for some reason, even passing SafetyNet and being the device certified, sometimes google detects something that makes those apps incompatible, and no, is it not the hardware or the ROM, is a security related issue, only I don't know which one.
OK, so today after 3 or for days without issues (and without rebooting) I rebooted the phone and the problem went back. I wiped both play store and play services data, rebooted three times and so far so good. Let's see what happens.
Could any forum moderators move this thread to the Magisk subforum?
Thanks.
eXtremeDevil said:
OK, so today after 3 or for days without issues (and without rebooting) I rebooted the phone and the problem went back. I wiped both play store and play services data, rebooted three times and so far so good. Let's see what happens.
Could any forum moderators move this thread to the Magisk subforum?
Thanks.
Click to expand...
Click to collapse
Nice to see it worked
(I'll ask the mods for the thread to be moved, if you wanna do that yourself next time just report your thread and select "thread moving")
Raiz said:
Nice to see it worked
(I'll ask the mods for the thread to be moved, if you wanna do that yourself next time just report your thread and select "thread moving")
Click to expand...
Click to collapse
Thanks for the moving trick, I didn't know that
Ask for the problem, is not actually fixed, I still lose those apps from time to time, and I'm still looking for a cause and for a definitive solution
It happened again after 2 or 3 reboots. I suspect the culprit is EdXposed or one of its modules. What I can't understand is why my other phone doesn't have that issue, or my girlfriends phone, that actually has the original Xposed...
I was seeing a similar issue. Without Magisk installed I was able to download Netflix from the Play store without issue. After Magisk installed and pass CTS, going back to play store Netflix app page showed red error msg, "This app isn't compatible with your device anymore. Contact the developers for more info." Force stop Play Store, clearing cache/storage resolved issue.
Curious but did you try setting the Magisk Manager option to hide and rename the manager package? Also if you have either ed/xposed, did you check if installing SudoHide module and hiding Magisk Manager from Play Store turns out different results? Doing the latter will remove Play Store (or any app you hide from Magisk through SudoHide for that matter) from the Magisk hide app list, something to keep in mind in case you need magisk hide enabled for play store, but I'm assuming you don't need to since you tried that already to no avail. Otherwise I'm curious to know if either, both, or neither solves this issue.
mr3p said:
I was seeing a similar issue. Without Magisk installed I was able to download Netflix from the Play store without issue. After Magisk installed and pass CTS, going back to play store Netflix app page showed red error msg, "This app isn't compatible with your device anymore. Contact the developers for more info." Force stop Play Store, clearing cache/storage resolved issue.
Click to expand...
Click to collapse
Yes, that seemst to work. I think I also need to clean Play Services app as well.
mario0318 said:
Curious but did you try setting the Magisk Manager option to hide and rename the manager package? Also if you have either ed/xposed, did you check if installing SudoHide module and hiding Magisk Manager from Play Store turns out different results? Doing the latter will remove Play Store (or any app you hide from Magisk through SudoHide for that matter) from the Magisk hide app list, something to keep in mind in case you need magisk hide enabled for play store, but I'm assuming you don't need to since you tried that already to no avail. Otherwise I'm curious to know if either, both, or neither solves this issue.
Click to expand...
Click to collapse
Tried that, didn't work. And yes, I have the manager renamed to something random.
SafetyNet does not pass 100% of the time, the clear data works but only for a while, I guess there's nothing to be done here...