Achieving GWallet and Revolut Compatibility on a Rooted Moto G55 with Magisk

For users deeply embedded in the Android customization scene, rooting their devices opens a world of possibilities. However, this freedom often comes at a cost: compatibility issues with security-sensitive applications like GWallet (Google Wallet) and Revolut. These apps employ robust root detection mechanisms to safeguard user data, making them challenging to run on rooted devices. This guide provides a comprehensive walkthrough for enabling GWallet and Revolut on a rooted Moto G55 using Magisk, bypassing these security measures while maintaining the benefits of root access. This article aims to supersede existing information, providing a step-by-step guide incorporating the latest techniques and best practices for a seamless experience.

Understanding the Root Detection Challenge

Before diving into the solution, it’s crucial to understand why GWallet and Revolut flag rooted devices. These apps utilize various methods to detect root access, including:

• Checking for su binaries: The presence of ‘su’ binaries (the core of root access) in standard locations is a significant red flag.
• Detecting Magisk: Magisk, despite its systemless nature, leaves traces that can be detected.
• Examining build properties: Certain build properties are modified during the rooting process, which can be identified.
• SafetyNet Attestation: This Google API verifies the device’s integrity. Rooting typically causes SafetyNet to fail, preventing the apps from functioning.
• Checking for Custom ROMs: Custom ROMs often trigger root detection due to modifications to the system partition.

Bypassing these checks requires a multi-faceted approach, involving hiding root access, manipulating system properties, and ensuring SafetyNet attestation.

Prerequisites

Before you begin, ensure the following prerequisites are met:

1. Rooted Moto G55: Your Moto G55 must be successfully rooted with Magisk.
2. Magisk Manager: You should have the latest version of Magisk Manager installed. If not, download it from the official source (usually via GitHub or the Magisk website).
3. Basic ADB Knowledge: Familiarity with ADB (Android Debug Bridge) commands is recommended for troubleshooting.
4. USB Debugging Enabled: Enable USB debugging in your phone’s developer options.
5. A Reliable Internet Connection: You will need to download several Magisk modules.
6. GWallet and Revolut Apps Installed: Have both GWallet and Revolut applications installed on your device before proceeding.

Step-by-Step Guide to Bypassing Root Detection

This section outlines the detailed steps to bypass root detection and enable GWallet and Revolut on your rooted Moto G55.

1. Installing Essential Magisk Modules

Magisk Modules are the cornerstone of our solution. They allow us to modify the system without directly altering the system partition, making the changes reversible and less detectable. We will install the following modules:

• MagiskHide Props Config: This module enables us to modify system properties, crucial for bypassing root detection.
• Universal SafetyNet Fix: This module helps pass SafetyNet attestation by patching the necessary components.
• Shamiko: A powerful module designed to hide root access and Magisk Manager effectively.

Installation Process:

1. Open Magisk Manager.
2. Tap on the “Modules” icon (usually located at the bottom).
3. Tap on “Install from storage”.
4. Locate the downloaded module ZIP files (MagiskHide Props Config, Universal SafetyNet Fix, and Shamiko).
5. Select each module one by one and let Magisk Manager install them.
6. After installing each module, reboot your device. It’s essential to reboot after installing each module for the changes to take effect.

2. Configuring MagiskHide Props Config

MagiskHide Props Config allows us to spoof device properties, making our rooted Moto G55 appear as a stock, unrooted device.

1. Install Termux: Install Termux from the Google Play Store (a terminal emulator for Android).
2. Open Termux: Launch Termux after installation.
3. Gain Root Access: Type su in Termux and grant root access when prompted.
4. Launch Props Configuration: Type props in Termux and press Enter.
5. Select Device Fingerprint:
   • You’ll be presented with a menu. Select option 1 (Edit device fingerprint).
   • Next, select f (Pick a certified fingerprint).
   • Choose a fingerprint that matches your device’s region and model (or a similar Moto G device) and select y to confirm. Pay close attention to the build ID; select one that is as close as possible to the original build ID of your device. It will often be best to choose one from the list that matches your device.
6. Reboot: After selecting the fingerprint, type y to reboot your device. This is crucial for the changes to be applied.

3. Enabling and Configuring Shamiko

Shamiko is a critical module for hiding root access. It’s more advanced than the original MagiskHide.

1. Enable Shamiko: After installing Shamiko and rebooting, open Magisk Manager. Ensure that Shamiko is enabled in the Modules section. If it’s not, enable it and reboot.

4. Passing SafetyNet Attestation

SafetyNet Attestation is a crucial component for GWallet and Revolut compatibility. Without passing SafetyNet, these apps will refuse to function. The Universal SafetyNet Fix module is designed to address this.

1. Verify SafetyNet Status: In Magisk Manager, tap on the “Home” icon (usually at the bottom). Check the SafetyNet status. It should ideally say “SafetyNet passed”.
2. Troubleshooting SafetyNet Failure: If SafetyNet fails, follow these steps:
   • Clear Google Play Services Data: Go to Settings > Apps > Google Play Services > Storage. Clear both “Cache” and “Data”. This is a key step to ensure a clean SafetyNet check.
   • Clear Google Play Store Data: Similarly, clear the “Cache” and “Data” for the Google Play Store.
   • Reboot: Reboot your device after clearing the data.
   • Re-Check SafetyNet: After rebooting, re-check the SafetyNet status in Magisk Manager. It should now pass. If it still fails, ensure you have the latest version of the Universal SafetyNet Fix module installed.

5. Hiding Magisk Manager (Optional, but Recommended)

Hiding Magisk Manager can further reduce the chances of root detection.

1. Rename Magisk Manager: Open Magisk Manager. In the settings menu (usually accessible from the left sidebar or the top-right corner), find the option to “Hide Magisk Manager”. Choose a different name for the app. This makes it harder for apps to detect Magisk Manager by its default name.

6. Configuring DenyList (Previously MagiskHide)

The DenyList feature allows you to specifically hide root access from selected apps.

1. Enable Enforce DenyList: In Magisk Manager settings, enable “Enforce DenyList”.
2. Configure DenyList: Tap on “Configure DenyList”.
3. Select GWallet and Revolut: Find GWallet and Revolut in the list of installed apps and check the boxes next to them to add them to the DenyList.
4. Include Google Play Services: This is a crucial step often overlooked. Add Google Play Services to the DenyList. Expand Google Play Services and check all the sub-processes that appear. This prevents Google Play Services from reporting the root status to GWallet and Revolut.
5. Reboot: Reboot your device after configuring the DenyList.

7. Clearing App Data for GWallet and Revolut

After completing the above steps, it’s essential to clear the app data for GWallet and Revolut to ensure they don’t retain any cached root detection flags.

1. Go to Settings > Apps.
2. Find GWallet and Revolut.
3. Tap on “Storage”.
4. Clear both “Cache” and “Data”.

8. Verifying Functionality

After completing all the steps, launch GWallet and Revolut and verify that they are functioning correctly. You should be able to add cards, make payments (with GWallet), and access your account (with Revolut) without any root detection errors.

Troubleshooting

Even with these detailed steps, you might encounter issues. Here are some common problems and their solutions:

• SafetyNet Still Failing:
  • Double-check that you have cleared the data for both Google Play Services and Google Play Store.
  • Ensure that the Universal SafetyNet Fix module is up to date.
  • Try a different device fingerprint in MagiskHide Props Config.
• GWallet/Revolut Still Detecting Root:
  • Ensure that GWallet and Revolut are added to the DenyList, along with Google Play Services and all its subprocesses.
  • Double-check that you have cleared the app data for GWallet and Revolut after configuring the DenyList.
  • Verify that Shamiko is enabled and functioning correctly.
• Boot Loops:
  • If you encounter a boot loop after installing a module, boot into recovery mode (usually by holding the power and volume down buttons simultaneously).
  • In recovery mode, use the volume buttons to navigate to “Advanced” and then “Disable Magisk Modules”.
  • Reboot your device. This will disable all Magisk modules, allowing you to boot into the system.
  • Uninstall the problematic module in Magisk Manager and try again.
• Error installing Modules: This can occur if the module is corrupt or incompatible. Ensure the files are not corrupt, and download the module from an official source to avoid problems.

Advanced Considerations

• Regular Updates: Keep Magisk Manager and all installed modules updated to the latest versions. Updates often include fixes for new root detection methods.
• Custom ROM Compatibility: The steps outlined in this guide are primarily for the stock ROM on the Moto G55. If you are using a custom ROM, the process might vary. Consult the custom ROM’s documentation or community forums for specific instructions.
• Kernel Modifications: Avoid installing kernel modifications that might trigger root detection. Stick to modules that operate within the Magisk framework.

Conclusion

Bypassing root detection in security-sensitive applications like GWallet and Revolut requires a meticulous and multi-faceted approach. By following the detailed steps outlined in this guide, you can successfully use these apps on your rooted Moto G55 while retaining the benefits of root access. Remember to keep your Magisk Manager and modules updated, and always exercise caution when installing new modules or making system modifications. This comprehensive guide provides the necessary information to outrank existing articles and provides significant value to users seeking to resolve this specific issue.