Anyone else get message this morning to say your device does not meet security requirements and now you cant use Google Wallet for contactless?
I made no changes yesterday so looks like Google made a change remotely.
Yep, got the same message.
Interestingly, still passing SafetyNet checks in YASNAC though?
Edit: Fixed.
Google Play Services was no longer hidden in Magisk for some reason? Added this to the DenyList, cleared app data for Google Wallet, Google Play Services & Google Play Store, and was able to re-add my cards without any roadblocks.
Exact same problem here
DanielF50 said:
Yep, got the same message.
Interestingly, still passing SafetyNet checks in YASNAC though?
Edit: Fixed.
Google Play Services was no longer hidden in Magisk for some reason? Added this to the DenyList, cleared app data for Google Wallet, Google Play Services & Google Play Store, and was able to re-add my cards without any roadblocks.
Click to expand...
Click to collapse
On latest MagiskHide is no longer there so I use Denylist Unmont module under zysik
Nekromantik said:
On latest MagiskHide is no longer there so I use Denylist Unmont module under zysik
Click to expand...
Click to collapse
Yeah, Magisk has used Zygisk DenyList since 24.1 - in theory the same thing as MagiskHide, but your mileage may vary depending on apps you use.
DenyList > show system > select Google Play services (I also selected Google Wallet but unsure if that makes any difference).
I'm assuming Google pushed some sort of server-side update which then pinged client-side, and triggered this. Could be a sign of things to come, or could just be a mistake my end (forgetting to deny GPS) .
fix was updating to USNF MOD instead of official
Updating to USNF still hasn't fixed issue for me, even though I pass all checks on YASNAC. Can't add cards for contactless payments due to security standards error. annoying!
Also happened to me but the problem is solved by installing the modified usnf. Look here:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
another possible issue: Android Police: Some people aren't able to tap and pay with Google Wallet right now. https://www.androidpolice.com/google-wallet-security-issue/
Wish there was a way to hide/encrypt our 'tools' to make it harder for google to 'counter our counters'. This never-ending cat & mouse game is getting reeeally old now.
I had the same issue last week.
I went back and hid everything 'google', uninstalled wallet, re-booted, and reinstalled wallet.
The error has not come back, but I also haven't tried T2P.
I downloaded Integrity check from the play store (@1nikolas)
I pass Device integrity and Basic Integrity, but not Strong Integrity
biTToe said:
I had the same issue last week.
I went back and hid everything 'google', uninstalled wallet, re-booted, and reinstalled wallet.
The error has not come back, but I also haven't tried T2P.
I downloaded Integrity check from the play store (@1nikolas)
I pass Device integrity and Basic Integrity, but not Strong Integrity
Click to expand...
Click to collapse
You don't have to pass strong integrity to be able to T2P
biTToe said:
I had the same issue last week.
I went back and hid everything 'google', uninstalled wallet, re-booted, and reinstalled wallet.
The error has not come back, but I also haven't tried T2P.
I downloaded Integrity check from the play store (@1nikolas)
I pass Device integrity and Basic Integrity, but not Strong Integrity
Click to expand...
Click to collapse
In addition to what @felek73 said, the only way you'll pass Strong Integrity is with a locked bootloader. Fortunately, you don't need pass Strong Integrity for most things.......................yet
Lughnasadh said:
In addition to what @felek73 said, the only way you'll pass Strong Integrity is with a locked bootloader. Fortunately, you don't need pass Strong Integrity for most things.......................yet
Click to expand...
Click to collapse
Except for that annoying nag everytime I boot about how my phone is insecure and could use some self-help
Had the same issue, fixed with USNF MOD update. Didn't want to clear data in wallet and redo all the cards so left it, 3 days later wallet working perfectly. So if like me you are a lazy SOB then update and wait...if you have the patience!
OzBoy1 said:
Had the same issue, fixed with USNF MOD update. Didn't want to clear data in wallet and redo all the cards so left it, 3 days later wallet working perfectly. So if like me you are a lazy SOB then update and wait...if you have the patience!
Click to expand...
Click to collapse
I tried clearing data/ cache of Google play store and it works immediately without having to add the cards again
cescman said:
I tried clearing data/ cache of Google play store and it works immediately without having to add the cards again
Click to expand...
Click to collapse
I tried the cache but no luck. When you say you cleared data do you mean that you cleared storage? My understanding if that you clear storage then you will need to add your cards again, at best it will remember some details but you will have to reconnect and add some details. Thanks for the reply it all helps. Cheers mate.
OzBoy1 said:
I tried the cache but no luck. When you say you cleared data do you mean that you cleared storage? My understanding if that you clear storage then you will need to add your cards again, at best it will remember some details but you will have to reconnect and add some details. Thanks for the reply it all helps. Cheers mate.
Click to expand...
Click to collapse
Yes, I am referring to clearing storage of Google play store. If you don't clear data in wallet, the cards will still be there
cescman said:
Yes, I am referring to clearing storage of Google play store. If you don't clear data in wallet, the cards will still be there
Click to expand...
Click to collapse
Thanks for confirming, tried that but didn't work for me, hopefully this helps someone else.
Weird my google wallet app doesn't appear. It shows as google pay app
Related
I have been rooted with SuperSu/Suhide since September and now am using Magisk 14.2 with the October security updates (flashed image and removed "-w" to retain data). I pass all of the safetynet checks from various apps under both conditions. I am having a problem adding cards to Android Pay. I add the card, verify the CVC, agree to the terms, and then get a popup saying that Google Play services has stopped. It does not finish verifying the card and clicking on the card results in the "Google Play services keeps stopping" error. This has happened since the September security update (did clear user data then) and I cannot find what may be causing it. I did edit the hosts file and build.prop when using SuperSu/Suhide, but now only the hosts file with Magisk. Anyone have a similar issues or know of solutions? Thanks.
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
Not sure if it's related, but I updated to September's Oreo build using fastboot flash of the factory image. I removed -w to save data. After this I was no longer able to purchase apps in the play store, always caused the play store to crash. Free downloads worked fine but paid transactions never went through. I ended up flashing the factory image and wiping data and all is well. I am unrooted.
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
I have the same issue can't buy apps. Get to the point of buying it and get FC. Doesn't matter if I'm rooted or not. Tried magisk and suhide
Not sure what could be the exact reason. I had google play services stopped problem on my Note 3, but it was not rooted. I followed a guide on Mobipicker, that worked for me. You can also refer, but not sure that will work for rooted devices.
I know this is old, but I found this thread because I had been having the same problem...I found the fix for my situation and figured I'd share in case anyone else came across the same issue... Everytime I tried to verify my card Google play services stopped...
I remembered that it checks that you have a secured lock screen when you set up at some point...I turned off smart lock location, on body detection, and face... Worked without any problems...
I'm at home, so I'm not sure if smart lock was preventing it from working just by being turned on, or if it thought I didn't have a secured lock screen because smart lock was triggered by me being at home...
Google pay is no longer working for me on DP3. Not sure what happened. I've never unlocked the bootloader once on this phone. I didn't even check the option to allow bootloader unlock. But I have run ADB commands for navigation gestures. So today I decided to just factory reset and try to get Google pay working again...right after reset I still get the same error. I'm lost now. Factory reset should have also reset any ADB commands I ran...if those were the issue. I also ran a safety net check and failed. Mind boggling. Anyone know what's up?
Pictures attached.
Happened to me yesterday after factory resetting DP3. Just clear Data and Cache on Google Play Services and Google Play Store, reboot and make sure your device is shown as "Certified" in Play Store settings. Safetynet should pass and Google Pay work normally
Phazonclash said:
Happened to me yesterday after factory resetting DP3. Just clear Data and Cache on Google Play Services and Google Play Store, reboot and make sure your device in shown as "Certified" in Play Store settings. Safetynet should pass and Google Pay work normally
Click to expand...
Click to collapse
Thx man! This fixed it for me. Finally!
You're welcome, glad it worked for you
Mr Patchy Patch said:
Thx man! This fixed it for me. Finally!
Click to expand...
Click to collapse
Holy crap, this worked for me also! Thanks to @Phazonclash!
megatomic said:
Holy crap, this worked for me also! Thanks to @Phazonclash!
Click to expand...
Click to collapse
It's so nice to have Google pay at my side again ?
Lol
I tried this, but when I checked if it was certified, there wasn't anything there. It just ended with the Play Store version.
Also, after I did a factory reset, I have to re-verify they cards. Why??
chadhoard said:
I tried this, but when I checked if it was certified, there wasn't anything there. It just ended with the Play Store version.
Also, after I did a factory reset, I have to re-verify they cards. Why??
Click to expand...
Click to collapse
Just give it a few minutes. Check the certification status later and you should see where it says Certified once again. You shouldn't have to reset again.
megatomic said:
Just give it a few minutes. Check the certification status later and you should see where it says Certified once again. You shouldn't have to reset again.
Click to expand...
Click to collapse
I will check in a few hours to see...
If I had already verified my debit card with my bank, why would I need to re-verify the card since I did a factory reset???
chadhoard said:
I will check in a few hours to see...
If I had already verified my debit card with my bank, why would I need to re-verify the card since I did a factory reset???
Click to expand...
Click to collapse
Security. It's better to be too secure than not secure enough.
Phazonclash said:
Happened to me yesterday after factory resetting DP3. Just clear Data and Cache on Google Play Services and Google Play Store, reboot and make sure your device is shown as "Certified" in Play Store settings. Safetynet should pass and Google Pay work normally
View attachment 4537615
Click to expand...
Click to collapse
Thanks a million!! I decided to do a wipe of DP3 and was stuck with this nagging issue for the past few days.
I ended rolling back and forth, wiping, formating...you name it, I've done it all and all a long this simple fix resolved the issue :victory:
Is anyone having problem getting the weather to show on the lockscreen after doing above fix?
Jay01 said:
Is anyone having problem getting the weather to show on the lockscreen after doing above fix?
Click to expand...
Click to collapse
I got it to work again by using this ADB command and rebooting:
adb shell "settings put global always_on_display_constants smart_space_enabled=true"
Phazonclash said:
I got it to work again by using this ADB command and rebooting:
adb shell "settings put global always_on_display_constants smart_space_enabled=true"
Click to expand...
Click to collapse
Thanks, Do you need a unlocked bootloader to use the above command
UPDATE: just tried it, seems to be working for now. Thanks
Has anyone received the DP4 today?
I updated via OTA but now the weather widget is gone, I tried the above fix but still nothing
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
Update: now its back, didn't do anything other than unlocking my phone and locking it back.
Tried clearing Google Play services and Google Play store data and cache as well as rebooting but Google Pay still not working on DP4...any ideas?
Shawn5162 said:
Tried clearing Google Play services and Google Play store data and cache as well as rebooting but Google Pay still not working on DP4...any ideas?
Click to expand...
Click to collapse
According to topjohnwu (Mr. Magisk) and Nathan Chance (Mr. Flash) there is nothing you can do until google fixes it on DP5.
https://mobile.twitter.com/topjohnwu/status/1014059549643247616?s=19
Badger50 said:
According to topjohnwu (Mr. Magisk) and Nathan Chance (Mr. Flash) there is nothing you can do until google fixes it on DP5.
https://mobile.twitter.com/topjohnwu/status/1014059549643247616?s=19
Click to expand...
Click to collapse
Looks like Google fixed it already...
ram4ufriends said:
Looks like Google fixed it already...
Click to expand...
Click to collapse
Yep, fixed for me now. Again. Lol
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.
Another problem with Google Wallet.
After updating Google Wallet, this app again tells me that the phone is rooted.
It has worked without problems until now.
Root - magisk and other supporting actions are already done from the previous editing.
Thanks in advance for your help
had this issue yesterday and didnt manage to fix without flashing another rom but here's a post with the latest fixes for it.
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
Do you remember me? I also had that problem. I'm now using Evolution X ROM based on Android 13. Everything is working. Magisk + Zygisk + SafetyNet Fix Module
So
I tried clearing data from google play services, play store and completely uninstalling google wallet.
Next, I disabled MagiskHide Props Config for a while.
I downloaded USNF (safetynet-fix-v2.3.1-MOD.zip) and flashed it over the old USNF.
I restarted the mobile phone, installed Google Wallet, registered a bank card and so far everything is fine - the device meets the security requirements.
In magisk, I haven't added Google Wallet to the denylist yet.
We'll see how long it lasts.
Cleared cache and data of wallet, rebooted, and it works again. Very very strange.
sanguinesaintly said:
Cleared cache and data of wallet, rebooted, and it works again. Very very strange.
Click to expand...
Click to collapse
I wrote the procedure a little more extensive. I did many more actions and differently than you write!
jkmaxfli said:
I wrote the procedure a little more extensive. I did many more actions and differently than you write!
Click to expand...
Click to collapse
Google has made some backend changes by the looks of things. All working now without root or Magisk.