Related
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.
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
zee24 said:
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
Click to expand...
Click to collapse
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
SageWilliams said:
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
Click to expand...
Click to collapse
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
zee24 said:
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
Click to expand...
Click to collapse
Great, I will say its hit or miss sometimes. Mine worked in stores for a few days, then stopped saying I was rooted so I had to redo the method to get it back.
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Great. Finally a fix. All like above but used Magisk 19.0. Thanks. I hope we're able to keep finding fixes like this. Google pay is a convenience.
According to this, it is to be expected on Pixel devices, vs others.
Advantages:
If you will see the list of the advantages and the list is too long of the magisk. This is the best Android application which you can use on your device. Let’s take a dive in the advantages of the Magisk.
You can use Financial/Banking applications.
You can use Snapchat without any issues.
You can also play Pokemon Go on your rooted Android device.
You can install OTA updates on your device.
You can also install System-less Xposed framework on your lollipop and marshmallow devices.
You can use Android Pay.
You can also bypass SafetyNet.
You might Face issues in:
Google Pixel and Google Pixel XL devices. The work is in progress, and we are working on i.
Magisk Manager cannot be placed in adaptable storage, or superuser will not work
MagiskSU does not support multi-user, and we are working on it to make multi-user support.
MagiskSU does not work on Android O preview, and we are working on it.
Click to expand...
Click to collapse
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Droid_Nut said:
According to this, it is to be expected on Pixel devices, vs others.
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Click to expand...
Click to collapse
Ever since that site was verified to be a fake.
https://www.google.com/amp/s/www.xd...kmanager-com-not-official-website-magisk/amp/
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Thanks so much dude....much appreciated
Yesterday I rooted my device thanks to you guys, which went really well and passing SafetyNet was a breeze. I just have a few questions that I'd like to get solved:
1) Play Store Certification - I accomplished this by using the fingerprint mask Magisk module, and I chose OnePlus 8 Pro Android 11 for my fingerprint. Play Store certification is now accomplished, but should I have had to do this? This leads on to question 2....
2) I thought I would be able to get certification by adding the Play Store to Magisk hide, but Play Store doesn't appear in the list of apps in Magisk. Same with Netflix. I was confused by this, as a) I thought that all apps should appear and b) the root tutorial pinned to the forum specifically says to add Play Store and Netflix to Magisk hide
3) My Netflix Widevine is now L3. Did I mess up somewhere? I've read that on OOS11, unlocking the bootloader doesn't trip Widevine
samwhiteUK said:
Yesterday I rooted my device thanks to you guys, which went really well and passing SafetyNet was a breeze. I just have a few questions that I'd like to get solved:
1) Play Store Certification - I accomplished this by using the fingerprint mask Magisk module, and I chose OnePlus 8 Pro Android 11 for my fingerprint. Play Store certification is now accomplished, but should I have had to do this? This leads on to question 2....
2) I thought I would be able to get certification by adding the Play Store to Magisk hide, but Play Store doesn't appear in the list of apps in Magisk. Same with Netflix. I was confused by this, as a) I thought that all apps should appear and b) the root tutorial pinned to the forum specifically says to add Play Store and Netflix to Magisk hide
3) My Netflix Widevine is now L3. Did I mess up somewhere? I've read that on OOS11, unlocking the bootloader doesn't trip Widevine
Click to expand...
Click to collapse
Well you could have gone much easier.
1) Turn on Magisk Hide and Systemless Hosts.
2) Right bottom of Magisk Hide theres the Magnifying glass to search. Click on it and click Show System Apps. Then Play Store and Google Services will be shown. Hide everything in Play Store tab and Google Play Services Tab. Also Netflix tab.
3) Clear cache of Play Store, Google Play Services, Netflix(might even unistall updates here just to be sure, thats what i did).
4) Reboot Phone, Go Play Store and update Netflix through Play Store at this point. Should be at Widevine L1
Ninxha said:
Well you could have gone much easier.
1) Turn on Magisk Hide and Systemless Hosts.
2) Right bottom of Magisk Hide theres the Magnifying glass to search. Click on it and click Show System Apps. Then Play Store and Google Services will be shown. Hide everything in Play Store tab and Google Play Services Tab. Also Netflix tab.
3) Clear cache of Play Store, Google Play Services, Netflix(might even unistall updates here just to be sure, thats what i did).
4) Reboot Phone, Go Play Store and update Netflix through Play Store at this point. Should be at Widevine L1
Click to expand...
Click to collapse
Ok I will try this, thanks for the pointer. I had hit that System Apps thing before but perhaps it didn't refresh. I can see it now
I can't install Netflix from the Play Store, it says the app is no longer compatible with my device. If I search for it, it doesn't appear. I can only get there by clicking the pre-installed icon, and then I can't do anything
samwhiteUK said:
I can't install Netflix from the Play Store, it says the app is no longer compatible with my device
Click to expand...
Click to collapse
Download it from apkmirror. Give it some time should be available soon on playstore after it gets Certified. Wasnt for me on playstore at first. give it some time and check again. BTW did you delete your module of fingerprint?
Ninxha said:
Download it from apkmirror. Give it some time should be available soon on playstore after it gets Certified. Wasnt for me on playstore at first. give it some time and check again. BTW did you delete your module of fingerprint?
Click to expand...
Click to collapse
I will download from there, that's what I did before. I deleted the fingerprint, and hid the Play Store, and I'm now certified with Play Protect without all that rubbish. Is it just a matter of time then before Netflix shows up again? I will install the APK - presumably I will still be able to get updates through the Play Store after that. I will let you know if I get Widevine L1
Nope, still L3. I don't even watch Netflix that much on my phone, so it's not urgent, but I'd just like to know that everything was working as a standard phone would :/
To me it was shown after some time. got a update of netflix through playstore and got widevine L1. Unistall udpates on Netflix and wait maybe u will get it from playstore after some time
Did you start off with Widevine L3 when you first unlocked? If it's supposed to remain at L1 and it hasn't for me, then I don't know if it's worth waiting. Can it go back up?
samwhiteUK said:
Did you start off with Widevine L3 when you first unlocked? If it's supposed to remain at L1 and it hasn't for me, then I don't know if it's worth waiting. Can it go back up?
Click to expand...
Click to collapse
I dont actually know that. Netflix was not available after rooting. And since i had just unlocked bootloader phone was resetted. So i was installing all apps and updates and netflix was not available. I managed to install all updates of apps and installed new apps, did magisk hide and hide netflix, play store, google services, clear cache, reboot. still netflix wasnt available but i did not open it, until later when i got an update through netflix, logged in, checked it was L1
Got the update, just came through. Added to Magisk hide, logged in, but it's still L3.
samwhiteUK said:
Got the update, just came through. Added to Magisk hide, logged in, but it's still L3.
Click to expand...
Click to collapse
:/.. clear cache again idk... damn
samwhiteUK said:
Got the update, just came through. Added to Magisk hide, logged in, but it's still L3.
Click to expand...
Click to collapse
Does Playstore says certified? There would be no reason for L3 if you already got netflix on play store working fine... Try unistall it again, clear data again, reboot and go install it again from playstore..... meh
I'll wait and see if anyone else comes along, and I'll do some more searching. Thanks for your help!
Ninxha said:
Does Playstore says certified? There would be no reason for L3 if you already got netflix on play store working fine... Try unistall it again, clear data again, reboot and go install it again from playstore..... meh
Click to expand...
Click to collapse
Yeah, Play Store certified, assuming I'm checking in the right place (in the settings menu)
samwhiteUK said:
Yeah, Play Store certified, assuming I'm checking in the right place (in the settings menu)
Click to expand...
Click to collapse
Yes play store settings and then about in the end... Try one more time what i told you and idk what else. I got L1, dont think i was just lucky...
Ninxha said:
Yes play store settings and then about in the end... Try one more time what i told you and idk what else. I got L1, dont think i was just lucky...
Click to expand...
Click to collapse
Yeah, uninstalled and reinstalled and it's still L3. DRMInfo says L3 as well
Although Widevine L1 is displayed, it becomes L3 and gives an error when watching Netflix downloaded content. not working properly.
samwhiteUK said:
I can't install Netflix from the Play Store, it says the app is no longer compatible with my device. If I search for it, it doesn't appear. I can only get there by clicking the pre-installed icon, and then I can't do anything
Click to expand...
Click to collapse
Reset you fingerprint and reboot, then wipe play store and services and try again also make sure to rename hide magisk app in magisk settings
toolhas4degrees said:
Reset you fingerprint and reboot, then wipe play store and services and try again also make sure to rename hide magisk app in magisk settings
Click to expand...
Click to collapse
I have Netflix installed now. The only issue I have now is the DRM is L3
Work from :
StratospherePerformance
Legend_Gaming077
Google has started to use hardware to check the phones bootloader which cannot be faked as it uses secure part of the phone that is not accessible.
There is a "hardware off" magisk module which changes your device id to a device that still uses software checks, this will pass safteynet but it will mean that galaxy store will stop working.
Eventually there will be no way round this to use SafetyNetFix !!!
!!!IMPORTANT!!!
There are 2 Versions
1 If you use Magisk Riru
2 If you use Magisk Zygisk
3 Any questions ?? Just ask here we help!
Happy Flashing!
safetynet-fix-zygisk-v2.2.1 = https://drive.google.com/file/d/1GppsrAlJ_eWjj613miRxFiYmUnztUVk2/view
safetynet-fix-riru-v2.1.3 = https://drive.google.com/file/d/1GrtnauPbFjSCGH8BuBiSS4YMay_5SPAx/view
Hello colleague, I have magiks
He says:
Installed: 24.3 (24300)
Zygisk: yes
ramdisk: yes
I'm still on UI 4.0 G770FXXS6FVD2
Do I have to install the file you provide?
I really don't have much knowledge.
Thank you
mezacorleehone said:
Hello colleague, I have magiks
He says:
Installed: 24.3 (24300)
Zygisk: yes
ramdisk: yes
I'm still on UI 4.0 G770FXXS6FVD2
Do I have to install the file you provide?
I really don't have much knowledge.
Thank you
Click to expand...
Click to collapse
Yes you can install safetynet-fix-zygisk-v2.2.1
Google pay just updated to Google wallet in my country and it doesn't work.. It says Google wallet is updating.
I think it see root and doesn't work. Google pay was working. I have safetynet fix zygisk and everything else. In every other app (banks etc) i hide root and everything is working. Magisk 25.2
I have deleted data, deleted data form gapps, re install Google wallet, nothing works.
If everyone have any other solution to try..
Thanks,
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.
You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.
dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk
Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!
aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.
This actually worked, thank you!