Troubleshooting Google Pay Not Working on Motorola Edge+ 2023 (rtwo / Moto Edge 40 Pro)

Experiencing issues with Google Pay on your Motorola Edge+ 2023, also known by its codename rtwo or the Moto Edge 40 Pro, can be incredibly frustrating. When a service as essential as contactless payments fails, it disrupts daily routines and can leave users searching for definitive solutions. We understand that Google Pay’s functionality is heavily reliant on device security and integrity, and for some users, especially those who have explored rooting their devices, this can lead to unexpected roadblocks. This comprehensive guide is designed to address the specific challenges reported with the Motorola Edge+ 2023 and provide actionable steps to restore Google Pay functionality, even in complex scenarios involving custom ROMs, root access, and firmware modifications. Our aim is to help you overcome these hurdles and ensure your device can once again be a reliable tool for seamless mobile payments.

Understanding the Root Cause of Google Pay Issues on Motorola Devices

Google Pay, and by extension, its underlying payment tokenization system, operates with a stringent set of security protocols. These protocols are designed to protect your financial information and prevent fraudulent transactions. For this reason, Google Pay employs SafetyNet Attestation or Play Integrity API checks to verify the integrity of your device. If your device is detected as compromised, either through an unlocked bootloader, the presence of root access, or even certain custom ROMs, Google Pay may refuse to function.

The reports of Google Pay failing on the Motorola Edge+ 2023, even after attempting to flash stock firmware and relock the bootloader, suggest a deeper level of scrutiny or a persistent flag within the device’s system that Google Pay is detecting. This could be related to specific hardware identifiers, firmware signatures, or a residual effect of previous modifications that hasn’t been fully purged. It’s a common challenge in the Android modding community where reclaiming full functionality after rooting can sometimes be more complex than initially anticipated. The device’s Secure Element (SE) or Trusted Execution Environment (TEE) might be flagging the device as untrusted, preventing the secure processing of payment information.

Common Scenarios Leading to Google Pay Failures

Several factors can contribute to Google Pay not working on your Motorola Edge+ 2023:

• Unlocked Bootloader: An unlocked bootloader is often the primary reason for Google Pay’s failure. It signifies a potential pathway for unauthorized modifications, which Google’s security measures are designed to prevent.
• Root Access (Magisk, APatch, KernelSU): While Magisk is renowned for its ability to hide root from specific apps, it’s not always foolproof. Google’s detection mechanisms are constantly evolving, and some apps, including Google Pay, might still detect residual signs of root. The specific modules used, their configuration, and the underlying rooting method can all play a role.
• Custom ROMs: Some custom ROMs, even if they don’t overtly expose root, might have modifications that interfere with Google Pay’s security checks. The integrity of the ROM itself is paramount.
• Modified System Partitions: Any alterations to system partitions, even those intended for performance enhancement or customization, can trigger Google’s security flags.
• Firmware Integrity: As observed in the reported case, even flashing back to stock firmware might not always resolve the issue if the flash process wasn’t perfectly clean, or if there’s a persistent hardware-level flag that’s not reset by a standard firmware installation.
• Google Play Services or Wallet App Issues: While less common when facing persistent security-related blocks, outdated or corrupted Google Play Services or Google Wallet app data can also cause payment failures.

Advanced Troubleshooting Steps for Google Pay on Motorola Edge+ 2023

Given the complexities, we will delve into advanced troubleshooting methods. These steps are designed to address the persistent issues reported, focusing on restoring the device’s perceived integrity for Google Pay.

Verifying and Restoring Device Integrity

The core of resolving this issue lies in convincing Google Pay that your Motorola Edge+ 2023 is a secure and unmodified device.

Ensuring Stock Firmware is Truly Stock

If you’ve flashed back to stock, it’s crucial to ensure the firmware is absolutely pristine and free from any residual modifications.

1. Download the Official Firmware: Always obtain firmware directly from Motorola’s official support channels or reputable firmware repositories. Verify the firmware version matches your device’s original software release for your region.
2. Perform a Clean Flash: Use the official flashing tools provided by Motorola or reliable community tools like fastboot. A clean flash typically involves wiping all partitions, including user data, cache, and system. Execute commands like fastboot erase userdata, fastboot erase cache, and fastboot format userdata before flashing the stock ROM.
3. Relock the Bootloader: This is a critical step. After successfully flashing the stock firmware, ensure you relock the bootloader using fastboot oem lock or the specific command for your device. A locked bootloader is essential for passing Google’s integrity checks.
4. Verify Device Status: After relocking, reboot your device and check the bootloader status again via fastboot oem device-info or similar commands to confirm it’s reported as locked.

Clearing Google Play Services and Wallet Data

Sometimes, cached data within Google Play Services or the Google Wallet app can hold onto old integrity flags.

1. Navigate to App Info: Go to Settings > Apps > See all apps.
2. Locate Google Play Services: Find and tap on Google Play Services.
3. Storage & Cache: Select Storage & cache, then tap Clear cache and Clear storage (or Manage space and then Clear all data).
4. Locate Google Wallet: Find and tap on Google Wallet (or Google Pay).
5. Storage & Cache: Select Storage & cache, then tap Clear cache and Clear storage (or Manage space and then Clear all data).
6. Restart your device after clearing the data.

Advanced Root Hiding Techniques (If Re-Rooting is Considered)

If you are considering re-rooting your device after confirming the stock firmware and locked bootloader do not resolve the issue, or if you wish to maintain root access for other purposes, advanced hiding techniques are necessary. This requires a deep understanding of Magisk and its ecosystem.

Magisk Configuration for Optimal Hiding

Magisk’s primary function for Google Pay is to hide the root environment. This involves several layers of configuration.

1. Mount Namespaces: Ensure Magisk is correctly configured to use Mount Namespaces to isolate root access. This is typically enabled by default but worth checking in Magisk settings.
2. MagiskHide (Legacy) / DenyList: The DenyList feature in Magisk is crucial. You need to ensure that Google Play Services, Google Wallet, and any other related Google services are added to the DenyList. This tells Magisk to hide root from these specific applications.
   • Open Magisk App.
   • Go to Settings.
   • Enable Configure DenyList.
   • Expand Google Play Services.
   • Select all checkboxes to hide root from all components of Google Play Services.
   • Expand Google Wallet (or Google Pay).
   • Select all checkboxes to hide root from Google Wallet.
   • Additionally, add any other apps that might be involved in payment processing or security checks.

Using Universal SafetyNet Fix / Play Integrity Fix Modules

These modules are specifically designed to spoof the SafetyNet or Play Integrity API responses, tricking apps into believing the device is certified and has a clean bill of health.

1. Obtain the Latest Module: Download the latest version of a reliable Play Integrity Fix module. PIF-Next is a highly regarded option. Ensure you are downloading from a trusted source, such as its official GitHub repository.
2. Install via Magisk:
   • Open the Magisk app.
   • Go to the Modules tab.
   • Tap Install from storage.
   • Navigate to and select the downloaded .zip file for the Play Integrity Fix module.
3. Reboot: After installation, reboot your device.
4. Check Play Store Certified: After rebooting, open the Google Play Store. Navigate to Settings > About phone. It should now say “Device is certified.” If not, the module may not be working correctly or is incompatible with your current setup.

Specific Module Combinations and Considerations

The user reported trying various combinations: PIF-Next, Tricky Store + Addon, TreatWheel, or Shimako. When troubleshooting, it’s often best to start with a single, well-maintained module like PIF-Next to rule out conflicts.

• PIF-Next: This module aims to pass the Play Integrity API checks. Ensure you are using the most up-to-date version.
• Tricky Store: This module is designed to help apps that rely on the Play Store’s integrity, which can indirectly affect Google Pay.
• TreatWheel / Shimako: These are less common, and their effectiveness can vary greatly. If PIF-Next doesn’t work, exploring these might be a secondary step, but focus on the most supported solutions first.

Clearing Magisk App Cache and Reinstalling

If you suspect an issue with Magisk itself:

1. Uninstall Magisk Modules: Temporarily disable or uninstall any recently installed Magisk modules to check for conflicts.
2. Clear Magisk App Data: Go to your app drawer, long-press the Magisk app, and select “App info.” Then go to “Storage & cache” and “Clear cache” and “Clear storage.”
3. Reinstall Magisk: It might be beneficial to uninstall Magisk completely and then reinstall it from its official source. You may need to reboot into recovery mode for this.

Exploring Alternative Payment Solutions (Temporary Workaround)

If, after exhausting all troubleshooting steps, Google Pay remains non-functional, you might consider alternative payment apps. However, these will also likely face similar security checks. This is more of a diagnostic step to see if the issue is specific to Google Pay or a broader system integrity problem.

Potential Firmware-Level Issues and Advanced Flashing

The observation that even flashing back to stock firmware didn’t resolve the issue is concerning and points towards a potential deeper system anomaly.

Clean Flash with Factory Reset

Ensure that when flashing stock firmware, you are performing a full factory reset during the process or immediately after. This wipes all user data and settings, providing the cleanest possible slate.

1. Boot into Recovery Mode: Power off your phone. Press and hold the Volume Down and Power buttons simultaneously until the bootloader menu appears.
2. Select Recovery Mode: Use the volume buttons to navigate to “Recovery mode” and press the power button to select it.
3. Wipe Data/Factory Reset: Once in recovery mode, select “Wipe data/factory reset.” Confirm the action.
4. Reboot System: After the wipe, select “Reboot system now.”

Flashing via Official Motorola Software (If Available)

If your device came with a specific Motorola PC software for updates or recovery (like Rescue and Smart Assistant), consider using that. These tools are designed to perform thorough reinstalls of the operating system and might address deeper firmware corruption that standard fastboot flashing might miss.

The Role of Specific Hardware Components and TEE

The problem might stem from how the Trusted Execution Environment (TEE) or the Secure Element (SE) on your Motorola Edge+ 2023 is interacting with Google Pay’s security checks. These are hardware-based security enclaves. If these environments are flagged as insecure due to any past modification, even a full firmware flash might not reset their status without a specific procedure.

Unfortunately, directly manipulating or resetting the TEE or SE is usually not possible for end-users without specialized tools or manufacturer-level access. This is a significant reason why some devices, after extensive modification, can permanently lose functionality for sensitive applications like mobile payments.

Troubleshooting Specific Error Messages

The errors you described are key indicators:

• “Device can’t use Tap to Pay” when adding a physical card: This suggests a failure in the primary security check for NFC-based payments, likely related to device integrity.
• “Check Your Network Connection” when adding a virtual card: This error, while seemingly network-related, can sometimes be a fallback message when a more specific security or authentication error occurs and the system defaults to a generic network problem. It’s less likely to be a genuine network issue if your Wi-Fi and mobile data are functioning perfectly for other apps.

Re-evaluating Modules and Their Interactions

If you’ve tried various modules, it’s important to consider potential conflicts.

• Module Conflicts: Ensure you are only using one primary Play Integrity Fix module at a time (e.g., PIF-Next). Other modules that modify system behavior, especially those related to security or systemless modifications, could interfere.
• Module Order: In rare cases, the order of module installation in Magisk can matter. However, for PIF modules, this is usually not a significant factor.
• Outdated Modules: Ensure all Magisk modules are up-to-date.

When All Else Fails: The Difficult Reality

If you have meticulously followed these steps, including flashing a verified stock firmware with a locked bootloader and have ensured your Google Play services are clean and the Play Store reports device certification, and Google Pay still fails with persistent security-related errors, it is possible that there is a persistent hardware-level flag or a firmware anomaly that cannot be resolved through standard user-accessible methods.

In such cases, the options become very limited:

1. Contact Motorola Support: While they may not be able to assist with devices that have been rooted or modified, if you are experiencing this issue on a device that has never been rooted and you have confirmed it’s stock firmware, it might indicate a manufacturing defect or a specific firmware bug that they are aware of.
2. Live with the limitation: Unfortunately, for some users, the security requirements of Google Pay may be too strict for their modified device state, and it might not be possible to restore functionality without a completely uncompromised device.

Our comprehensive approach prioritizes restoring Google Pay’s functionality on your Motorola Edge+ 2023 by systematically addressing the potential causes, from firmware integrity to the intricate workings of Magisk and security APIs. By focusing on these detailed steps, we aim to provide the most effective solutions for users facing these challenging issues.