GPay Fix EU ROM

[fw85]

GPay works just fine on EU ROM build 20.9.24 - before launching it, I made sure:
- that my Magisk Manager is hidden under a different package name,
- that I enabled Magisk Hide on the whole Google Play Services, Framework and Google Pay,
- and finally that I used MagiskHide props config to force basic key attestation.

 

[Zorthos]

For me this worked fine. I had no Problems. I just flashed the eu rom and it worked fine out of the box.

Which version did you flash?

 

[MrBeefshop]

Which version did you flash?

The latest beta. (12.10.15)
I installed it completely fresh, with format data.

 

[AerationCheese]

Yeah none of the suggested fixes in here work anymore.

Tried all kinds of settings in the props thing. Nothing.

This showed up 3 days after in installed the ROM. So don't say "I just installed it and it works fine" apparently it doesn't happen immediately.

 

[sahafdeen]

I haven't posted how I fixed this on the Xiaomi EU forum.

The curious thing is that I bootlooped my phone two days ago by installing the Viper Module from Magisk and again I couldn't pass the Cts profile in Magisk. My safetynet failed. Pokemon Go would keep on asking me to login and Gpay wouldn't work.

I fixed this again by using MagiskHide Module but this time using the latest Magisk Canary build. The normal Magisk 20.4 works fine as well.

The fix is to root your phone using Magisk, install Magisk via Twrp, install the Magisk Manager Apk. Once in Magisk Manager install the HideMagisk Module.

Also have a terminal app installed. Once you have gotten to this step in terminal run command "su" without quotes.

After execute command "props"

Follow the instructions that the terminal gives to you but only updating Force Basic Key Attestation and change the Fingerprint prop value. Both values can be set to the Pixel 4xls. This only seems to break Google Chrome for me. I can only fix the chrome issue by uninstalling the MagiskHide Prop.

Installing Edexposed after all of this breaks everything again so don't attempt to install Edxposed. It breaks SafetyNet.

just type SU and props
Both values can be set to the Pixel 4xls <<<< need to Edit or input.
pls guide!

 

[Hudge]

i just used the script from this post: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658 after getting the safteynet error: "evalType HARDWARE" as described here: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
"If the SafteyNet check in the Magisk Manager fails CTS and shows "evalType HARDWARE" you'll need to use this feature. See here for details on hardware based key attestation for detecting the bootloader state: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3

This feature has nothing to do with the device fingerprint, but uses the included fingerprints list to find the necessary value to use for the ro.product.modle prop.

As long as Google doesn't roll out hardware based key attestation universally, it seems like we can fool SafetyNet into using the basic attestation by changing the ro.product.model prop (to pass the CTS profile check even with an unlocked bootloader). The module scripts will also alter partition specific props (odm, product, system, vendor and system_ext) to match, if they are available. Thank you to @Displax over at XDA for finding this: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40658"

And it worked perfectly

 

[MoneyFist]

Argh, this is all a headache ??. I'm current waiting for the 160hours to unlock, but I think I'll stick to the Chinese rom.
I've debloated everything with ADB. Banking apps and Googlepay works fine

 

[ToneLa]

Argh, this is all a headache . I'm current waiting for the 160hours to unlock, but I think I'll stick to the Chinese rom.
I've debloated everything with ADB. Banking apps and Googlepay works fine

What a worthless post.

 

[BarrySamuels]

Taking the plunge!

I have ordered a Xiaomi Mi 10 Ultra and am now waiting for it to be despatched and delivered. I wish I had found this forum earlier and I might have ordered from a different (recommended) seller. I'm told that despatch will be no later than Friday 4th December - we shall see.

I have ordered the Chinese version and have bookmarked a web page which explains how to access the appropriate settings, not being able to read Chinese, by using icons. I'm hoping that I can get through that to convert to English otherwise I'm stuck. I see that unlocking the bootloader is pretty straightforward so I shall start that process as soon as I receive the 'phone.

I have flashed custom ROMs and rooted most of my previous 'phones although now that I'm 84 I have to work from a printed list of instructions in order that I don't forget something. Bad memory comes with age. I haven't yet decided whether or not to flash the European ROM.

I have seen, on the web two differing opinions regarding the Chinese ROM camera and the European ROM camera. I am buying this phone because of its camera and I have seen remarks that infer that the camera in the European ROM is not as good as the one in the Chinese ROM so I am wary of flashing the EU ROM. Does anyone have any knowledge of this?

Now I just have to wait.

 

[pszyman74]

You can flash EU rom and then flash Chinese camera if you consider rooting the phone. There's a thread in this forum with Magisk module replacing camera. Then you can always revert the changes if you're not happy.
Currently I'm on EU rom with Chinese camera and it works fine except one thing - video recording using front camera and stabilization generates green movie. That did not happen using the same camera software on Chinese rom. Other than that, I have not seen any issues.

Sent from Mi 10 Ultra...