Related
Hey guys just updated to the latest magisk manager and magisk root on my pixel a few days ago but i just noticed that my Google pay had removed my bank card. Checked magisk manager and went into the magisk hide list and nothing was checked so i manually checked necessary apps including Google pay. Now even after that and after a reboot and clearing data of Google pay AND despite magisk passing a safetynet check Google pay still refuses to accept my bank card. Should i roll back to an earlier version when it was working? Is there something broken in the lastest magisk manager?
Thanks in advanced.
February security update
Magisk manager 7.0
Magisk 18.1
ElentalX-P2-2.09
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
CyberpodS2 said:
No idea why you have the problem but I just made a purchase today at the supermarket Price Chopper...
Here is my setup:
Click to expand...
Click to collapse
Thanks so much for confirming must be a problem on my end. I've been getting random freezes at night which had me waking up with no alarm. Guess it's time for a clean install because obviously something went wrong on my end. Thanks again G.
Yeah....there's a (good) chance that it's just as what happened with @acheney1990 and me...
you can read all about it HERE, but suffice it to say; it can easily be on the banking's end "flagging" with all the validation that's needed -- which is it's own headache trying to understand why they keep tripping it up this way....
Hey did you ever happen to get a solution on this? I seem to have run into the same problem because everything is setup the same as before, but since I've upgraded to Pie in Feb security, I can't use Google Pay (unable to pay in store), Zelle, or the Chase app (force closes immediately, apparently on checking my GPS location it seems).
My problem started when I updated my Moto x4 to latest Pie update 29.69-26-5. I was on Magisk 18.1, and Manager 7.0 which I had to uninstall to get the update. After reinstalling Magisk, Passing safety net, I get a message at the POS saying my phone won't work with Google Pay. My debit card (Chase) is still listed in Google pay on my phone but when I try to add another card I get "This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way"
if I clear the storage and uninstall and re-install Google Pay, it still has my debit card listed, so for whatever reason, it's keeping my payment info even though I cleared the storage.
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Itachisasuke said:
ongoing issue over on the Magisk Forum. An update to Google Play Services isn't working nicely with Magisk.
Click to expand...
Click to collapse
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
simplepinoi177 said:
Hmmmm...if this is the case, wouldn't "removing updates" and installing an older/stable version (from apkmirror.com or something) and keeping it from updating be a workaround, for now....?
Click to expand...
Click to collapse
That is exactly what has been suggested and even outlined here and there. I tried a couple different scenarios but it became too cumbersome trying to juggle it all. I'll just wait for an update to be released. Lol
FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
mine is fine
try re flash your rom
i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703
My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text
dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).
Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do
TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.
Try safety patch module in Magisk to pass Safetynet
HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same
I had to completely wipe my phone since recently the battery life started tanking hard, and I couldn't figure out why. I decided to just start over from a clean slate, since I had the same configuration since I got the phone about a year or two ago (stock Android 9, unlocked, and rooted with Magisk and EdXposed).
I figured that I would flash the July image without wipe first, but the battery issue persisted. I then decided to just flash it with the wipe (after backing up data, of course), and the battery seemed to be a bit better while I was setting up.
The problem I'm now having is that my device seems to be missing Play Certification. I noticed this when I was unable to install Netflix from the Play Store (although Google Pay seemed to work fine?). I've tried flashing the image several times, and even tried older images, but I can't seem to keep Play Certification.
I tried locking the bootloader after flashing the July image, and that finally gave me Play Certification and I was able to download Netflix.
Obviously however, I need to keep an unlocked bootloader for other things too.
Is there any way to get Netflix (and Play Certification) to work with an unlocked bootloader?
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
nitrous² said:
Doesn't MagiskHide provide just what you're asking for? If you don't want to use Magisk, maybe try PeNoire's SafetyNet Spoofer which works without Magisk but still requires a custom recovery like TWRP.
Click to expand...
Click to collapse
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Latiken said:
How would I get MagiskHide to work with Netflix without being able to install the app from the Play Store? Would enabling hide for the PS work, or do I need to sideload the app and then use Hide on the app?
Click to expand...
Click to collapse
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
nitrous² said:
Netflix doesn't care about the existence of Magisk once it is already installed on your device. So don't get confused there. You're problem is with the Play Store, specifically with SafetyNet. One step at a time;
When you unlock your bootloader, you are going to fail some SafetyNet checks. This will result in a restricted Play Store, meaning, certain apps won't be visible to you. To circumvent that, you flash something like Magisk or PetNoire to hide your bootloaders state to SafetyNet checks. This will result in an unrestricted Play Store. Unlock, install Magisk or PetNoire and then you should be able to get unrestricted access to Play Store apps.
Unlock the bootloader of your device
Install the latest version of Magisk
MagiskHide should be enabled by default, if not:
Download and install PetNoir's SafetyNet Spoofer
Click to expand...
Click to collapse
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
You just need to install Netflix through apk, not playstore. it is working well
Latiken said:
I've tried this, but something seems to not be working, or I'm doing something wrong.
I have Magisk 19.3 installed, and I can see that MagiskHide was automatically enabled for ”com.google.android.gms.unstable" under Google Play services, but Play Store Certification still shows that my device isn't certified, and Netflix won't appear.
The SafetyNet check in MagiskManager passes, however, so I'm wondering if there's something else going on. I'm going to try the other suggested SafetyNet bypass.
EDIT: Installed the other Spoofer, and the Certification listing in the Play Store disappeared, but Netflix is still nowhere to be seen. I tried uninstalling all updates for the Store and clearing storage and cache, but still nothing.
Wondering if I should just sideload Netflix and see if it works fine.
EDIT2: After a few moments, the Play Store now says that my device is certified, but I'm still unable to find Netflix in the Store for some reason. Tried rebooting and clearing cache but still nothing.
Click to expand...
Click to collapse
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
giants8058 said:
I'v been been having the same issue for about 5-6 months now with both Android 9 and 10. It was working fine on Pie and showing up in Google Play, but then after I flashed one of the monthly system images with a wipe, the app no longer showed up in the play store. And after I restored the most recent Netflix app at the time from a backup, it would constantly crash. I have all Google Play Services, Google Play and Netflix selected in Magisk hide. Google Play says my device is certified. Magisk SafetyNet test passes along with any SafetyNet test app. Logged out of my Google account, wiped data for Google Play, Google Play services and Netflix, rebooted and signed back in but still not showing up. Downloaded and installed the newest Netflix app from their site but I get an error stating the device is not supported with the app which clearly isn't the case.
Can you select this link and have it open in the Google Play app on your phone: https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en_US
It shows up for me but says in red font: "This app isn't compatible with your device anymore. Contact the developers for more info". Which I did...went back and forth with Google and Netflix for hours yesterday, but both of their support is completely useless.
The newest version of the app that works for me is version 6.26.1. You can download it here if you haven't already: https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
The only thing is how long is it going to continue to work. A future update will most likely break that version as well.
Have you made any progress since July?
Click to expand...
Click to collapse
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Latiken said:
That's actually the exact same version of Netflix that I was able to get working, and I've been using it since July.
It works exactly as it should, but the resolution seems to be capped at 480p or 720p, as I notice a lot of blurriness. It's still usable, but I'm considering getting rid of Magisk and going to 10 to avoid these issues.
Reading on what you've done, it's exactly what I went through in July.
I'm not sure what's changed since prior to updating to another security patch, Netflix was working completely fine from the Play Store with Magisk.
Click to expand...
Click to collapse
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
giants8058 said:
Yeah and also after a few minutes of watching a video, the screen dims like right before your phone auto-locks itself due to inactivity. So far the only way I was able to get it to show back up in Google Play was re-locking the bootloader, but that's not really an option for me since I want to stay rooted. But it really doesn't make any sense since all the SafetyNet compatibility tests pass and the device is certified. Maybe I'll try reaching out to the Magisk dev and see if he's willing to take a look into it.
Click to expand...
Click to collapse
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Latiken said:
I don't seem to have that screen dimming issue, so it's possible that something else is going on on your end for that.
It's possible that Netflix is able to detect root through some other way that's irrelevant to Google Play Protection. And it could also be a thing where the resolution is limited if you're not on the latest version.
If I do figure something out in the future, I'll be sure to post here again.
Click to expand...
Click to collapse
I don't think the issue is because of being rooted, but instead the unlocked bootloader as it still doesn't show up after uninstalling Magisk or after a system image flash with wipe. Like I mentioned earlier, the only way I can get it to show in Google Play or have the newest version work when side loaded at this point is when the bootloader is locked. So if you don't mind not being rooted or being able to manually flash updates without a factory reset each time, just re-lock your bootloader (just remember to backup your data since it wipes your phone) and Netflix should work normally again.
But I'll be sure post here as well if I come across anything that works.
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
simplepinoi177 said:
What you both need is to install/flash a custom kernel...
On top of many multiple things a custom kernel can do, one significant thing is to be able to mask root on many/most root detecting processes. When I first rooted 2 years ago, I couldn't get Google Pay to work because of the root detecting. I had inadvertently flashed a custom kernel, and was pleasantly surprised that Google Pay began to work (back then, but now more than a custom kernel is required).
The best general all-around custom kernel was called Flash, but that became EOL and stopped development, but one called Caesium was built based off of Flash and continued from there; even collaborated with the maker of Flash.
Give it a try, and see how it works wonders for both your issue (root detection) battery life, and even responsiveness of the system!
Hope this helps...
Click to expand...
Click to collapse
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Latiken said:
Thank you for the suggestion, I'll make sure to try this after updating to the latest Pie build. I'm sure that this will work, as I remember using a custom kernel last time that Netflix was working just fine for me.
I also just found a thread with a stock kernel infused with a SafetyNet patch that says that Netflix and other apps refused to work on unlocked bootloader devices because something trips in SafetyNet, leading me to believe that this is what me and @giants8058 have been experiencing.
I will let everyone know if this works later this week.
Click to expand...
Click to collapse
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
murphyjasonc said:
You have to flash a custom Kernel to hide bootloader unlock. After you flash the custom kernel the play store will still show as not being certified. You will have to force stop the play store then delete the cache and storage. When you reboot it will show that it is certified.
Click to expand...
Click to collapse
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Latiken said:
I flash the August stock build along with the Sultan kernel (as I couldn't get Caesium or the SafetyNet patched kernel to flash), and followed your instructions, but my Play Store isn't showing my device as certified yet.
Is there something else I need to do?
Click to expand...
Click to collapse
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
murphyjasonc said:
1. Download TWRP 3.3.0 img file
2. Download TWRP 3.3.0 zip file (optional)
3. Download Magisk 19.3
4. Download kernel of choice. (I use Sultan)
5. Boot to fastboot
6. Boot to TWRP. (fastboot boot TWRP. Img) I shorten the file name to make it easier.
7. Flash kernel first if using Sultan
8. Flash TWRP zip. (optional)
9. Flash Magisk 19.3
10. Let phone boot then delete data/cache in play store.
11. Reboot phone
These are the steps I use. If I remember correctly there was a couple of versions of the play store that showed uncertified no matter what. The latest play store version is 16.5.15. I can confirm it works. I also hide Google Play services in Magisk hide but I don't think that's needed unless you want Google Pay to work.
Click to expand...
Click to collapse
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Latiken said:
Those steps are actually exactly what I did, but the certification label in the settings is missing, and Netflix won't appear.
If it means anything, I noticed that I actually had Sultan kernel installed before doing any of this, so it might be that the kernel isn't working on my end.
Click to expand...
Click to collapse
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
simplepinoi177 said:
Well...I can say, at least, that I am having the same experience as murphyjasonc and am able to get "Play Protect Certification" certified and I have an unlocked bootloader with root and even a custom recovery.
I would make sure you do as he suggests and at the very least disable or "uninstall updates" for the Play Store and Google Play Services. But, also, custom kernels are things that also need to be updated; so this might be the explanation on it no longer working. But I know you had recently reflashed Sultan, so it is rather puzzling that you are still having those issues.
Just making sure, you are using TWRP to install the latest version of those kernels, correct? Also, when you had ran the August patch, did you use the Full Factory version? Are you able to pass safetynet currently?
Hopefully retrying these will get things up and running...
Click to expand...
Click to collapse
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Latiken said:
I used the latest version of TWRP to install the August OTA patch, as well as to install the latest Sultan kernel.
I just ran a SafetyNet test in MagiskManager and it passed correctly.
Click to expand...
Click to collapse
Give this a try...
instead of the OTA, try the Full Factory version -- and be sure to remove the "-w" in the flash-all to keep your data intact -- and then, also, be sure to disable/"uninstall updates" for both the Google Play Store and the Google Play Services (you can enable it after disabling it of course). After that, boot up TWRP and flash the Sultan kernel and Magisk and see if you don't have the certification after all that.
If you don't know; you can't simply run the Full Factory .zip's in TWRP, so if you don't know how to do a Full Factory version, I can point you in the right direction...
Good luck!
Hi all,
Got a new phone and finally decided to see if I could root the old Pixel 2 XL. It's unlocked, bought directly from Google. Never before unlocked bootloader until now.
It was flashed to factory Android 11 2020-12, and rooted from there. Magisk 21.1 beta was installed from zip while booted into TWRP 3.0.4, as advised in this thread. The latest Play System Update (Oct 5, 2020) was automatically installed while I was messing around afterwords.
I confirmed root access thru a checker and Termux, which is pretty neat! Hadn't rooted a device in a long time!
Unfortunately, device certification fails in Play Store, Magisk SafetyNet check and being unable to add a credit card to Google Pay. Magisk says basicIntegrity passes, but CTSprofile fails.
Things I've tried, mostly from this exhaustive guide:
Hidden Magisk Manager
Enabled MagiskHide, rebooted
Remove Magisk zip from storage
Lock bootloader again, rebooted
Clear app storage for Play store and Play services, rebooted
Disable USB debugging
Disable Play Protect scanning
Looked over XDA boards, Magisk changelog/documentation/guides
Things I haven't done (yet?):
Spoofing device fingerprint. I wouldn't expect this to be necessary, since it's actually authentic! But maybe there's more to it that I don't understand?
Start over from scratch, with Magisk Canary build - doesn't appear to be any improvements to MagiskHide according in current release notes
Is this possible to achieve?
composition said:
Is this possible to achieve?
Click to expand...
Click to collapse
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Google I believe is using hardware-backed CTS profiling, which Magisk cannot circumvent. Your only chance of passing CTS is to hope Google ISN'T using the hardware-backed version, so you can employ one of the workarounds I gave in the link above.
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Larzzzz82 said:
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Click to expand...
Click to collapse
Apparently we're both having brain farts. I didn't even think there was such a setting. Then again, I don't use Google Pay.