Telegram

GWallet Problems: Regaining Access After an EvoX Update

The frustration of losing access to your GWallet (Google Wallet) after a system update is a common issue, particularly for users of custom ROMs like EvoX. The dreaded message, “This phone doesn’t meet security requirements,” can lock you out of contactless payments and other essential features. At Magisk Modules, we understand this issue. This comprehensive guide is designed to help you troubleshoot and potentially regain access to your GWallet after updating your Pixel 6 Pro from EvoX 11.0 to EvoX 11.3, or experiencing similar problems on other devices. We’ll explore the underlying security mechanisms, common causes, and potential solutions, while emphasizing the importance of device security.

Understanding the Root Cause: Security Attestation and Device Integrity

The reason GWallet often fails after a custom ROM update boils down to security attestation. Google Wallet relies on the SafetyNet API (now deprecated in favor of the Play Integrity API) to verify the integrity and security of your device. These APIs assess several factors:

  • Root Access: Whether or not your device is rooted. Custom ROMs often require root access, which can trigger security flags.
  • Bootloader Status: Whether the bootloader is locked or unlocked. Unlocked bootloaders are a common requirement for flashing custom ROMs and are a red flag for security-sensitive applications.
  • System Modifications: Any modifications to the system partition, including the presence of custom ROMs, custom kernels, or altered system files.
  • Tampering: Evidence of any attempt to tamper with the device’s hardware or software security mechanisms.
  • Virtual Environments and Emulators: Whether or not the system is running in a virtualized environment or emulator.

If the SafetyNet or Play Integrity API detects any of these issues, it will report that the device does not meet security requirements, and GWallet will refuse to function. Specifically for the Play Integrity API, Google provides various levels of attestation, including “MEETS_BASIC_INTEGRITY”, “MEETS_DEVICE_INTEGRITY”, and “MEETS_STRONG_INTEGRITY”. GWallet requires “MEETS_DEVICE_INTEGRITY” at a minimum to function.

EvoX Updates and GWallet Issues: A Common Scenario

EvoX is a popular custom ROM known for its performance and customization options. However, updating EvoX can sometimes introduce issues with GWallet compatibility for several reasons:

  • Changes in Security Settings: The update may inadvertently modify security settings or configurations that affect SafetyNet or Play Integrity attestation.
  • Kernel Modifications: Updates often include kernel changes that can impact device integrity checks.
  • Magisk Compatibility: The updated ROM may not be fully compatible with your current Magisk version or installed modules.
  • Prop Changes: The update process could inadvertently alter build.prop values that affect the device’s perceived security status.
  • New Security Patches: Google frequently updates its security attestation requirements. An EvoX update based on a newer Android version with updated security patches may expose previously hidden incompatibilities.

When upgrading to EvoX 11.3 from EvoX 11.0, there may be internal configuration changes that trigger SafetyNet or Play Integrity API failures.

Troubleshooting Steps: A Systematic Approach

Before making any drastic changes, we advise taking a systematic approach to troubleshooting:

1. Check SafetyNet or Play Integrity Status

First, confirm whether your device is failing SafetyNet or Play Integrity.

  • SafetyNet: Install the “SafetyNet Helper” app from the Play Store (if you’re still using Android versions supporting SafetyNet). Run the test. If it fails, proceed to the next steps.

  • Play Integrity: Install an application that tests Play Integrity API (search the Play Store). Check the output:

    • “MEETS_BASIC_INTEGRITY”: Indicates basic integrity checks passed.
    • “MEETS_DEVICE_INTEGRITY”: Indicates a genuine device running a Google-approved Android version. This is the minimal requirement for GWallet.
    • “MEETS_STRONG_INTEGRITY”: Indicates a genuine device with hardware-backed key attestation (more secure, not always required).
    • If any of these checks fail, proceed to the next step.

2. Verify Magisk Installation and Modules

If you are using Magisk (which is very likely with EvoX), ensure that it is properly installed and up-to-date.

  • Update Magisk Manager: Open the Magisk Manager app and check for updates. Install the latest version.
  • Reinstall Magisk: If updating doesn’t resolve the issue, try reinstalling Magisk by flashing the Magisk ZIP file in recovery.
  • MagiskHide/Zygisk (if applicable): Older versions of Magisk relied on MagiskHide to hide root. Current versions utilize Zygisk and Shamiko for the same purpose. Ensure your preferred method is properly configured.

3. Check for Conflicting Modules

Incompatible or outdated Magisk modules can interfere with SafetyNet or Play Integrity.

  • Disable Modules: Disable all Magisk modules. Reboot your device. Retest SafetyNet or Play Integrity.
  • Isolate the Culprit: If SafetyNet/Play Integrity passes with all modules disabled, re-enable them one by one, testing after each re-enable, to identify the problematic module. Common culprits include modules that modify system files or introduce custom tweaks.

4. Clear Google Play Services and GWallet Data

Sometimes, cached data can cause issues with security attestation.

  • Clear Cache and Data: Go to Settings > Apps > Google Play Services > Storage. Clear both Cache and Data. Repeat this process for Google Wallet.
  • Reboot: Reboot your device after clearing the data.
  • Retry GWallet Setup: Try setting up GWallet again.

5. Check Build.prop Modifications

Incorrect modifications to the build.prop file can trigger SafetyNet/Play Integrity failures.

  • Review Changes: If you have manually modified the build.prop file, carefully review your changes. Revert any modifications that you suspect may be causing the issue.
  • Verify Fingerprint: The ro.build.fingerprint property is crucial. Ensure it matches the correct fingerprint for your device and ROM version. Incorrect fingerprints are a common cause of SafetyNet/Play Integrity failures.
  • Use a Build.prop Editor: If you need to edit build.prop, use a dedicated build.prop editor app to prevent syntax errors.

6. Flash the Correct GApps Package

If you flashed a GApps package (Google Apps) after installing EvoX, ensure you used the correct package for your Android version and architecture (ARM64).

  • Verify GApps Version: Double-check that the GApps package you installed is compatible with Android 11 (or the Android version your EvoX ROM is based on).
  • Re-flash GApps: If you suspect the GApps package is the issue, re-flash the correct GApps package in recovery.

7. Look for Known Issues with EvoX 11.3

Search online forums, Reddit, and the EvoX community for reports of GWallet issues specifically related to EvoX 11.3 on the Pixel 6 Pro.

  • EvoX Forums: Check the official EvoX forums for any announcements or troubleshooting guides related to GWallet issues.
  • Reddit (r/EvolutionX): Search the r/EvolutionX subreddit for similar reports and potential solutions. The original reddit post you referenced is a good starting point.

8. Try a Different Kernel

Sometimes, the default kernel included with EvoX may be the cause of the problem.

  • Research Alternatives: Research alternative kernels that are known to be compatible with EvoX 11.3 and have good SafetyNet/Play Integrity support.
  • Flash a Custom Kernel: Flash the custom kernel in recovery.
  • Test SafetyNet/Play Integrity: After flashing the kernel, test SafetyNet or Play Integrity to see if the issue is resolved.

9. Use a Magisk Module to Fix Play Integrity (Play Integrity Fix)

As SafetyNet has been depreciated, the need to pass Play Integrity API checks is becoming increasingly important. There are a couple of modules available for Magisk that try and solve this. It is important to note that the effectiveness and safety of these modules vary, and may break Google’s terms of service.

  • PIF Module: There are a couple of Play Integrity Fix modules available on GitHub, you can try installing one of those through the Magisk Manager and enabling Zygisk.

10. Factory Reset (Last Resort)

If all else fails, a factory reset may be necessary. Back up your data before performing a factory reset.

  • Factory Reset from Recovery: Boot into recovery mode and perform a factory reset.
  • Reinstall EvoX: After the factory reset, reinstall EvoX 11.3.
  • Test GWallet: Set up GWallet after reinstalling the ROM.

Advanced Troubleshooting: Analyzing Logs

For more advanced users, analyzing logs can provide valuable insights into the cause of the GWallet issue.

  • Logcat: Use adb logcat to capture system logs. Look for errors or warnings related to SafetyNet, Play Integrity, or Google Play Services.
  • Kernel Logs (dmesg): Use adb shell dmesg to view kernel logs. Look for errors related to security or device attestation.
  • Magisk Logs: Check the Magisk Manager app for logs related to MagiskHide/Zygisk and module activity.

Analyzing these logs can help identify specific errors or issues that are causing SafetyNet or Play Integrity to fail.

Preventing Future Issues

To minimize the risk of encountering GWallet issues after future updates:

  • Research Compatibility: Before updating your ROM, research whether there are known compatibility issues with GWallet.
  • Backup Your System: Create a full backup of your system before updating, so you can easily revert if necessary.
  • Update Magisk and Modules: Ensure that Magisk and all installed modules are up-to-date before updating your ROM.
  • Clean Flash: Consider performing a clean flash of the ROM, which involves wiping all data partitions before installing the new version.
  • Monitor Forums: Keep an eye on EvoX forums and other online communities for reports of issues and potential solutions.

Disclaimer

Modifying your device’s software can be risky and may void your warranty. We are not responsible for any damage that may occur as a result of following these instructions. Proceed with caution and at your own risk. Tampering with your device’s security settings may have unintended consequences and could potentially compromise your personal information.

We hope this comprehensive guide helps you regain access to your GWallet after the EvoX update. We at Magisk Modules are committed to providing the best possible resources for managing your device. Visit our Magisk Module Repository for a wide selection of modules to enhance your Android experience.

You also may like 〣〣
      Explore More
      Redirecting in 20 seconds...