[Guide][EdXposed][GPay] Discussion

Search This thread
Jun 1, 2020
32
1
Last edited:

i5lee8bit

Senior Member
Jul 18, 2006
378
731
New Jersey
FWIW, I was able to get fully up to date with SafetyNet passing and no crashing at all. Unfortunately maybe no help for those on Android 11; I'm still on Android 10.

Currently now up-to-date with the following
main core versions:

Again, I'm on Android 10 still, Dec 2020 firm
Magisk v21.2
EdXposed v.0.5.1.4 (4655) YAHFA
Riru Core v23.1
(edit) - Kernel: Kirisakura 5.2.6

Magisk Modules:
Advanced Charging Controller (ACC) v2020.11.20
AK3 Helper Module (Kirisakura kernel addon for A10 - obsolete for A11)
Busybox for Android NDK v1.31.1
Call Recorder - SKVALEX v2.1.0 (3.4.2)
GPay SQLite Fix v2.2
MagiskHide Props Config v5.3.6-v109
Riru / Riru EdXposed, obviously as indicated earlier
SQLite for ARM aarch64 devices v1.3
Systemless Hosts v1.0
YouTube Vanced (my module)

(Ed)Xposed Modules:
Edge Sense Plus 1.32.0
Fingerface 1.1.0
GravityBox [Q] v10.1.0 WOOHOOO

not sure if this post was a waste of my time, but if anybody else on A10 were hesitant like me, it's working perfectly as of now.
 
Last edited:

Kris Chen

Senior Member
Jan 10, 2013
687
291
Taoyuan
Thanks, mate !

I make my google camera work again after flashing the most update Edxposed V0.5.1.4(4655) YAHFA after seeing this post from yours. My ROM is A11, stock version.

So to the other people, please flash most update edxposed V0.5.1.4(4655) YAHFA will fix google camera cannot be opened issue.

FWIW, I was able to get fully up to date with SafetyNet passing and no crashing at all. Unfortunately maybe no help for those on Android 11; I'm still on Android 10.

Currently now up-to-date with the following
main core versions:

Again, I'm on Android 10 still, Dec 2020 firm
Magisk v21.2
EdXposed v.0.5.1.4 (4655) YAHFA
Riru Core v23.1

Magisk Modules:
Advanced Charging Controller (ACC) v2020.11.20
AK3 Helper Module (Kirisakura kernel addon for A10 - obsolete for A11)
Busybox for Android NDK v1.31.1
Call Recorder - SKVALEX v2.1.0 (3.4.2)
GPay SQLite Fix v2.2
MagiskHide Props Config v5.3.6-v109
Riru / Riru EdXposed, obviously as indicated earlier
SQLite for ARM aarch64 devices v1.3
Systemless Hosts v1.0
YouTube Vanced (my module)

(Ed)Xposed Modules:
Edge Sense Plus 1.32.0
Fingerface 1.1.0
GravityBox [Q] v10.1.0 WOOHOOO

not sure if this post was a waste of my time, but if anybody else on A10 were hesitant like me, it's working perfectly as of now.
 
  • Like
Reactions: vdevl and i5lee8bit

i5lee8bit

Senior Member
Jul 18, 2006
378
731
New Jersey
Thanks, mate !

I make my google camera work again after flashing the most update Edxposed V0.5.1.4(4655) YAHFA after seeing this post from yours. My ROM is A11, stock version.

So to the other people, please flash most update edxposed V0.5.1.4(4655) YAHFA will fix google camera cannot be opened issue.

edit: I should preface by saying I finally just updated to Android R as of just 2-3 days ago.

So apparently, for both me and my wife's phones, our camera apps never updated to v8.1.x (despite being last updated in early December) even after updating to Android 11 and running app updates. Today, both of our phones' cameras wouldn't work. Either nothing happened (screen would flash black for a second), or would get force closed notification. Running all of the recent versions of Magisk, Riru, EdX, etc. as mentioned earlier. Then I noticed it would work again after uninstalling all Camera app updates (thus reverting back to v7.5/x or whatever)...

In order to fix this, I needed to add the camera app to app blacklist (in EdXposed Manager). Immediately worked afterwards. Just to be safe (may not be necessary), I also added it to Magisk Hide list (just the first entry, not every component). As far as Magisk Hide though, again I don't think it's necessary, as simply disabling EdXposed module altogether made Camera work again during testing.

So if anybody is having Camera v8.x crashes, make sure to blacklist the app in (at least) EdXposed Manager!! (and possibly, but probaby not necessary in, Magisk Hide)
edit: this also includes the Google Recorder app!
 
Last edited:
  • Like
Reactions: vdevl and beeshyams

beeshyams

Senior Member
Dec 29, 2014
1,590
535
Bangalore
edit: I should preface by saying I finally just updated to Android R as of just 2-3 days ago.

So apparently, for both me and my wife's phones, our camera apps never updated to v8.1.x (despite being last updated in early December) even after updating to Android 11 and running app updates. Today, both of our phones' cameras wouldn't work. Either nothing happened (screen would flash black for a second), or would get force closed notification. Running all of the recent versions of Magisk, Riru, EdX, etc. as mentioned earlier. Then I noticed it would work again after uninstalling all Camera app updates (thus reverting back to v7.5/x or whatever)...

In order to fix this, I needed to add the camera app to app blacklist (in EdXposed Manager). Immediately worked afterwards. Just to be safe (may not be necessary), I also added it to Magisk Hide list (just the first entry, not every component). As far as Magisk Hide though, again I don't think it's necessary, as simply disabling EdXposed module altogether made Camera work again during testing.

So if anybody is having Camera v8.x crashes, make sure to blacklist the app in (at least) EdXposed Manager!! (and possibly, but probaby not necessary in, Magisk Hide)

Same with recorder stock app. Restoring to factory fixed
 
  • Like
Reactions: vdevl and i5lee8bit

i5lee8bit

Senior Member
Jul 18, 2006
378
731
New Jersey
Same with recorder stock app. Restoring to factory fixed

Wow why didn't I think of that for Recorder!! I've mentioned a few times before (since before upgrading to Android 11) about the same problem with Recorder... But unlike Camera, it wasn't as big a deal so I didn't bother trying to fix it (just uninstalled updates and turned off auto update). Same deal with Recorder - blacklisting in EdXposed Manager allows latest updates to work!
 
  • Like
Reactions: vdevl and beeshyams

i5lee8bit

Senior Member
Jul 18, 2006
378
731
New Jersey
YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Explained very well here, as to why it's failing again: https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389

tl;dr - even if BASIC hardware attestation is being reported, it is still actually running HARDWARE-based test, at least under the hood. Please go and thank the original creator of this method: https://github.com/kdrag0n/safetynet-fix, as well as where I found the original info: https://forum.xda-developers.com/t/unable-to-pass-safetynet.4192073/post-84282209

The Github release files are just raw files in the zip, so you'll need to download, unzip, then rezip (without compression) into the proper Magisk file/folder structure.
For your convenience, I've also uploaded v1.2 of kdrag0n's Magisk module to AFH, already ready to be flashed in Magisk Manager: https://www.androidfilehost.com/?fid=17248734326145715249

kdrag0n already updated the module to support earlier versions of Android, plus some code changes to make it more reliable. Go get it from his Github; the .zip's are now flashable-ready! Here: https://github.com/kdrag0n/safetynet-fix/releases
I'm sending a donation over to him right now to show my appreciation... I hope others do the same!

Obviously flash at your own risk - it worked perfectly fine on my P4XL, on January 2021 patch, running latest Magisk 21.2, Riru Core 23.3, EdXposed (4655), etc.

edit: as an added bonus, it looks like we can now choose to only force basic attestation (in MagiskHide Props Config) while maintaining the actual device fingerprint for what we're using. This worked on both of our phones. No big deal, but it did get a little confusing sometimes when apps would track registered devices, or seeing the "wrong" metadata on photos taken. Looks like the way kdrag0n's magisk module passes the key attestation info allows for this.

Very weird thing that I never bothered mentioning before is that I was always able to keep my own phone (P4XL) fingerprint as an actual P4 XL, but on my wife's P4 I had to change it to something else (both being forced to basic attestation, obviously). Mine would still pass, but hers would always fail unless I changed the fingerprint as well. I always thought that was odd.
 
Last edited:

crashnova

Senior Member
Aug 17, 2010
308
123
Yonkers
FWIW, I was able to get fully up to date with SafetyNet passing and no crashing at all. Unfortunately maybe no help for those on Android 11; I'm still on Android 10.

Currently now up-to-date with the following
main core versions:

Again, I'm on Android 10 still, Dec 2020 firm
Magisk v21.2
EdXposed v.0.5.1.4 (4655) YAHFA
Riru Core v23.1
(edit) - Kernel: Kirisakura 5.2.6

Magisk Modules:
Advanced Charging Controller (ACC) v2020.11.20
AK3 Helper Module (Kirisakura kernel addon for A10 - obsolete for A11)
Busybox for Android NDK v1.31.1
Call Recorder - SKVALEX v2.1.0 (3.4.2)
GPay SQLite Fix v2.2
MagiskHide Props Config v5.3.6-v109
Riru / Riru EdXposed, obviously as indicated earlier
SQLite for ARM aarch64 devices v1.3
Systemless Hosts v1.0
YouTube Vanced (my module)

(Ed)Xposed Modules:
Edge Sense Plus 1.32.0
Fingerface 1.1.0
GravityBox [Q] v10.1.0 WOOHOOO

not sure if this post was a waste of my time, but if anybody else on A10 were hesitant like me, it's working perfectly as of now.
Mind sharing the riru core 23.1? It's not GitHub anymore.
 

crashnova

Senior Member
Aug 17, 2010
308
123
Yonkers

crisco654

Member
Jul 17, 2014
33
8
I'm on android 11, passing safetynet with this latest trick. But the new google pay app won't work(the old one does tho). Does anyone know why?

Edit:Nevermind, it works now. Just had to clear my cache
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    Get Edxposed, Magisk, and GPay to work together.

    1. Install or make sure you are on latest Magisk Manger (7.5.1 or newer)

    2. Install or make sure you are on latest Magisk (20.3 or newer)

    3. Hide the following in Magisk Hide

    -Google Pay
    -Google Play services, only select the following
    -com.google.android.gms
    -com.google.android.gms.unstable​
    -Google Play Services for AR
    -Google Play Store, select everything but com.android.vending
    -Google Services Framework
    -Nfc Service​

    4. Install the following modules
    -GPay SQLite Fix (Full Edition)
    -SQLite for Arm aarch64 devices via Magisk Manager
    -hardwareoff by @Displax (Thanks to @Kris Chen for making me aware of it) or use MagiskHide Props to set check to basic and fingerprint to Pixel 3a

    5. Reboot

    At this point make sure you have GPay working before installing edxposed. If for some reason you are unable to use GPay try deleting data for Google Play Services/Google Play Store/Google Pay

    After you confirm that GPay is working then move on to installing edxposed

    1. Download and install Riru - Core via Magisk Manager

    2. Download Edxposed Manager (4.5.4 or newer) (Don't Install Yet!)
    3. Download Edxposed (4563) (Don't Install Yet!)
    I'm personally using the YAHFA version.
    https://ci.appveyor.com/project/ElderDrivers/edxposed/history

    4. Once you have all these files downloaded turn on Airplane Mode and install the Edxposed Magisk Module (Magisk -> Modules and press the + sign, find the downloaded zip and select it, Magisk will install it) and Edxposed Manager APK and reboot

    5. Once booted up remain in Airplane Mode

    6. Open Edxposed Manger and go to Settings and turn on "App List mode"

    7. Exit and reopen Edxposed Manager

    8. Go to Applications on the side menu (should say "Black List" on top) and select the following apps
    -Google Pay (may not be needed)
    -com.android.nfc.auto_generated_rro_product_
    -com.android.nfc.auto_generated_rro_vendor_
    -Nfc Service
    -pixelnfc (new in Android 11)​
    9. Go to Settings on the side menu, at the bottom of settings find and enabled "Pass SafetyNet"

    10. Reboot and turn off Airplane Mode

    11. Optional* Hide Magisk Manager

    Note. Steps 4-9 should be done in Airplane Mode, this will keep anything tripping safety net during the setup process.
    6
    How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.

    I disable big modules like Xposed when I update. Then re-enable them once update is completed. I'll put a step by step here.

    When phone detects update

    1. Disable any desired Magisk modules, ex. Edxposed
    2. Reboot
    3. In Magisk, select Uninstall, press Restore Images
    4. Do NOT Reboot
    5. Install OTA Update via Settings -> System -> System Updates
    6. When prompted to reboot, Do NOT Reboot
    7. In Magisk Manager press Install
    8. Select Install to Inactive Slot
    9. Reboot
    10. Enable the Magisk modules one by one

    In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.

    One requires ADB

    While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.

    adb wait-for-device shell magisk --remove-modules
    adb reboot

    This will remove all modules and you should be able to boot.

    The second way is via fastboot. More information in this thread.

    https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
    5
    When phone detects update

    1. Disable any desired Magisk modules, ex. Edxposed
    2. Reboot
    3. In Magisk, select Uninstall, press Restore Images
    4. Do NOT Reboot
    5. Install OTA Update via Settings -> System -> System Updates
    6. When prompted to reboot, Do NOT Reboot
    7. In Magisk Manager press Install
    8. Select Install to Inactive Slot
    9. Reboot
    10. Enable the Magisk modules one by one

    In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.

    One requires ADB

    While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.

    adb wait-for-device shell magisk --remove-modules
    adb reboot

    This will remove all modules and you should be able to boot.

    The second way is via fastboot. More information in this thread.

    https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557


    Here are some screen shots of it working
    4
    YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
    Explained very well here, as to why it's failing again: https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389

    tl;dr - even if BASIC hardware attestation is being reported, it is still actually running HARDWARE-based test, at least under the hood. Please go and thank the original creator of this method: https://github.com/kdrag0n/safetynet-fix, as well as where I found the original info: https://forum.xda-developers.com/t/unable-to-pass-safetynet.4192073/post-84282209

    The Github release files are just raw files in the zip, so you'll need to download, unzip, then rezip (without compression) into the proper Magisk file/folder structure.
    For your convenience, I've also uploaded v1.2 of kdrag0n's Magisk module to AFH, already ready to be flashed in Magisk Manager: https://www.androidfilehost.com/?fid=17248734326145715249

    kdrag0n already updated the module to support earlier versions of Android, plus some code changes to make it more reliable. Go get it from his Github; the .zip's are now flashable-ready! Here: https://github.com/kdrag0n/safetynet-fix/releases
    I'm sending a donation over to him right now to show my appreciation... I hope others do the same!

    Obviously flash at your own risk - it worked perfectly fine on my P4XL, on January 2021 patch, running latest Magisk 21.2, Riru Core 23.3, EdXposed (4655), etc.

    edit: as an added bonus, it looks like we can now choose to only force basic attestation (in MagiskHide Props Config) while maintaining the actual device fingerprint for what we're using. This worked on both of our phones. No big deal, but it did get a little confusing sometimes when apps would track registered devices, or seeing the "wrong" metadata on photos taken. Looks like the way kdrag0n's magisk module passes the key attestation info allows for this.

    Very weird thing that I never bothered mentioning before is that I was always able to keep my own phone (P4XL) fingerprint as an actual P4 XL, but on my wife's P4 I had to change it to something else (both being forced to basic attestation, obviously). Mine would still pass, but hers would always fail unless I changed the fingerprint as well. I always thought that was odd.
    4
    There is an update to edxposed that passes safety net

    v4.6.3

    It's under canary in edxposed manager
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone