Question Google pay - root - November update - Google Pixel 7

Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!

hi , can someone have a good advice, i was thinking to root my pixel 7 but with this "
nformation:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software."
i worry
thanks

Use this version of Universal Safetynet Fix:
https://github.com/Displax/safetynet-fix/blob/master/README.md

thanks

I've been using the latest safetynet-fix since the beginning >
Release v2.3.1-MOD_2.0 · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Release v2.3.1-MOD_2.0 · Displax/safetynet-fix
github.com
(you sent an older version)
Currently, I cleaned storage&cache of googleplay services, added cards and everything works without warning.

hi i install "
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed"
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
this "
Play Integrity API Checker"
cant find it
but else the same proplem of Device doesn't meet security
anyy help
thanks

3dot menu -> show system apps..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

efkosk said:
3dot menu -> show system apps..
View attachment 5757789
Click to expand...
Click to collapse
i click of show system ... but i cant find the (Play Integrity API Checker)

salamdiab said:
i click of show system ... but i cant find the (Play Integrity API Checker)
Click to expand...
Click to collapse
sorry, my mistake. You don't have to hide this at all.
it is the application "Play integrity API Checker" and it is used for additional verification of whether root is hidden.
If you have a problem with google wallet, delete storage & cache in Google Play services and wallet. Next, open your Wallet, add new cards and everything will work.

thanks for answer
thats what i have

salamdiab said:
thanks for answer
thats what i have
Click to expand...
Click to collapse

As far as I know, MagiskHide Props Config does not work correctly on P7. Does volte-properties for pixel 6 work for you?
Try to turn these things off, restart the phone, delete the cache storage as I wrote above and I think it will work.
aaa did you hide magisk by renaming the application?
this is mine:
X MEETS_STRONG_INTEGRITY is OK

wow
thanks a lot
it work
and yes the volte is worke fine

nice! so the problem was MagiskHide Props Config?

efkosk said:
nice! so the problem was MagiskHide Props Config?
Click to expand...
Click to collapse
actually i didn't know download another saftet fix called mod 2 and it work

aaah, so you didn't have the same safetynet version as me.
The main thing is that it works, I'm looking forward to it!

efkosk said:
aaah, so you didn't have the same safetynet version as me.
The main thing is that it works, I'm looking forward to it!
Click to expand...
Click to collapse
i really thank you so much

efkosk said:
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
Click to expand...
Click to collapse
Hello,looks like issue resolved? Gpay is toobimportant for me , as well as call recorder, btw are you using skvalex magisk module or app? Can it recording calls calls made from Google voice?

bizkit_120 said:
Hello,looks like issue resolved? Gpay is toobimportant for me , as well as call recorder, btw are you using skvalex magisk module or app? Can it recording calls calls made from Google voice?
Click to expand...
Click to collapse
Solved, I'm on the latest Dec update.
I also use gpay daily.
I use the skvalex magisk version that automatically installs the call recorder application. I think Google Voice should also record it.

efkosk said:
Solved, I'm on the latest Dec update.
I also use gpay daily.
I use the skvalex magisk version that automatically installs the call recorder application. I think Google Voice should also record it.
Click to expand...
Click to collapse
thanks for the info,.. hmm, interesting..what is the point of flash SKVALEX module then, application itself should works already as long as it rooted..

Related

SafetyNet FIX - Google Update [March 2020]

Here is the fix for those who have SafetyNet problem.
Flash Latest Magisk: https://github.com/topjohnwu/Magisk/releases/latest
Download and Install Latest Riru-Core Module(Magisk): https://github.com/RikkaApps/Riru/releases/latest
Download and Install Latest YAHFA Module(Magisk): https://github.com/ElderDrivers/EdXposed/releases/latest
Download and Install Latest EdXposedManager: https://github.com/ElderDrivers/EdXposedManager/releases/latest
Download and Install Latest HiddenCore Module(EdXposed): https://repo.xposed.info/module/com.cofface.ivader
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Correct me if I'm wrong but the HiddenCore module only fakes the ctsProfile value, it does not actually fix your device into passing SafetyNet checks.
xGarro said:
Correct me if I'm wrong but the HiddenCore module only fakes the ctsProfile value, it does not actually fix your device into passing SafetyNet checks.
Click to expand...
Click to collapse
But I can finally watch Netflix, thanks op!
xGarro said:
Correct me if I'm wrong but the HiddenCore module only fakes the ctsProfile value, it does not actually fix your device into passing SafetyNet checks.
Click to expand...
Click to collapse
Yeah, pretty sure it does that. But its still better than nothing while waiting for magiskhide fix.
Yeah it does say that it passed but I guess Nintendo is super smart because when I launch Mario Kart Tour it says "An error has occurred" and gives a useless support code. Before the patch, I could play Mario kart tour for about 10 seconds and then the game would eternally freeze and play the same soundtrack on loop forever even when leaving the app. You needed to clear it from RAM to get rid of the sound. With this patch, can't even load past the loading screen. Anyways I think it's because Nintendo is detecting the Xposed Framework, and maybe Netflix doesn't check for this and that's why it's working.
Thanks anyways, it'll work for some apps but not all, guess I'll have to hope the Magisk team can figure out what Google did.
It's a shame that Google does everything to annoy people who just want to do whatever they want with their phone, something they bought.
I have same device with You and folow your step and its work !!! For visual only
My banking apps still fc whenever I open it,
Can you guys also post your magisk module list?
With just edxposed 4513 I cannot pass.
Device pixel 4 xl
Sent from my Pixel 4 XL using Tapatalk
Hiddencore makes safetynet pass, but i tried mcdonalds app and it shows security check failed
The main point is: how far can we trust HiddenCore? It is (was?) closed source, old thread on it here in XDA suggests it may be MALWARE, or can be just a COSMETIC thing by hooking magisk/system when reporting green SafetyNet.
I really don't know, but I prefer not to use it.
Thread on it:
https://forum.xda-developers.com/xposed/modules/hiddencore-module-doing-t3903984
If it seems open source now I'd suggest to better/deeper investigate its code and build from source before using it. At least by some recognized developer.
yes working nice job
wilsonhlacerda said:
The main point is: how far can we trust HiddenCore? It is (was?) closed source, old thread on it here in XDA suggests it may be MALWARE, or can be just a COSMETIC thing by hooking magisk/system when reporting green SafetyNet.
I really don't know, but I prefer not to use it.
Thread on it:
https://forum.xda-developers.com/xposed/modules/hiddencore-module-doing-t3903984
If it seems open source now I'd suggest to better/deeper investigate its code and build from source before using it. At least by some recognized developer.
Click to expand...
Click to collapse
Only one true state at the moment is by SafetyNet checker from Play Store!
HiddenCore is legit and do the job good until you don't mess too much as I
Guys! Do you have screen always on with HiddenCore 1.7?
Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.3, EdXposed 0.4.6.1 (build 4510), Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
Help!
I have unrooted my phone aka removed magisk completely but seems safetynet check fails on root checking apps.
Seems this time google fked it very hard this time....
Can Unlock bootloader also trigger safetynet check?
All apps working fine except Ola cab app. It keeps saying since this week:
FAILURE! SORRY SOMETHING WENT WRONG PLEASE TRY AGAIN.
or
THE OLA APP IS NOT AVAILABLE FOR USE ON THIS DEVICE.
Its a sheer shame that Gpay and banking apps are working without issues and this Ola apps refuses to. I tried clear data, uninstall reboot bla bla and even tried Dec 2019 version but same issues.
Can someone comment on some help here....
This is NOT a solution... This s*** only fakes SafetyNet results in Magisk Manager and Google Play... plus the phone's display never goes off after x seconds/minutes (idle).
I can't download Netflix in Google Play with this but I can without (even if "Uncertified" device is displayed).
(As suggested by someone in one of the the main Magisk threads...)
My banking app fails to start if it finds the TWRP folder in the internal storage partition - delete the folder and it's OK again.
That might be the reason why some people are having problems - though why the apps are allowed to search for the existence of a folder I have no idea...
Seems as this just fakes the safety of the net checks. Still I can pass all the safety net checks I need with this module. Pogo, hpwu and banking apps.
Is Safetynet issue happening if root a custom rom? Or any custom rom including without root?
Magisk may no longer be able to hide bootloader unlocking from apps
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/
Well looking at the replies, this module only fakes the status of the CTS profile. But most banking apps still work.
I just had one problem that chrome crashes whenever I open it. Everything else seems fine. Any fixes for this "chrome issue"
Poco F1 - 11.0.6 EU plus Sesh 5.1 kernel
Magisk 20.3
magisk riru core 19.7
edXposed YAHFA 0.4.6.1 (4991)
edXposed installer 2.2.4

App detects Xposed, refuses to start. Even when cloaked

I have the following annoying issue I want to solve:
It is so annoying that everytime I wish to use the app "App Cloner", I have to disable Xposed, reboot, then the app starts.
If Xposed is active, the app starts and then closes itself, giving the following message: Please deactivate Xposed while using the app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried some modules to make the app not see that Xposed is on, but it didn't work. Can anyone help? Anyone knows how to make the app "App Cloner" run and not detect that Xposed is active?
These cloak and hide modules I already tried, but the app still detects Xposed...
-I tried this https://github.com/sanfengAndroid/FakeXposed
-I tried ANRC https://repo.xposed.info/module/cat.dcat.roothide
-I tried RootCloak https://repo.xposed.info/module/com.devadvance.rootcloak2
-I tried SudoHide https://repo.xposed.info/module/com.sudocode.sudohide
using Android 8 Oreo, Xposed Installer with Xposed framework version 90-beta3
The app i want to run. but can't because I don't want to deactive xposed, is called App Cloner 2.12.5 (google banned them from playstore but their app is still elsewhere https://appcloner.app/)
Would be very happy if anyone could help.
Thank you in advance
Edit:
I just want to know out of principle, how the app knows. What does it check? What does it look for?
Is there an easy way to find out?
I know I could just use the new Xposed thats systemless like magisk. But I want to know how it actually knew.
The app is pretty good in detection, it even detects LuckyPatcher (don't know how), even after you hide it. It demands you uninstall it. Is there an easy way to bypass?
Edit: I don't expect an answer, I guess this is more of an reverse engineering questions that's too advanced for me anyway
I'd like to know as well. I've bought the license for the app and it's very inconvenient having to disable Xposed and reboot to use it normally and reboot again to use my phone with Xposed.
The old version used to work fine but it has now been expired.
hi bro
It's very simple
1.open xposed menu / open xposed hide (black) then Find and mark app cloner
2.open lucky patcher menu / open exposed setting and mark all and enable exposed module.
3.restart phone END
The most efficient way is to complie xposed source code and change some string names
Use momo, try to hide root and xposed from it, if you succeed, app cloner shouldn't detect anything.
You can download it from here
Magisk alpha
检测设备修改情况 更新日志: 修复zygisk的假阳性 修复包管理异常的检测
t.me
olik2000 said:
Use momo, try to hide root and xposed from it, if you succeed, app cloner shouldn't detect anything.
You can download it from here
Magisk alpha
检测设备修改情况 更新日志: 修复zygisk的假阳性 修复包管理异常的检测
t.me
Click to expand...
Click to collapse
Thank you but I already use Momo and I don't think it's possible to fully hide Xposed from it if Xposed is still enabled (AFAIK ART parameters are abnormal)
christantoan said:
Thank you but I already use Momo and I don't think it's possible to fully hide Xposed from it if Xposed is still enabled (AFAIK ART parameters are abnormal)
Click to expand...
Click to collapse
I had the same problem with lsposed, I solved it by going to data/adb/modules/lsposed and open system.prop using text editor and add # before the first line. Save the file and reboot then check exposed.
Lsposed shows me system prop incorrect but everything works normally and momo doesn't detect it anymore.
olik2000 said:
I had the same problem with lsposed, I solved it by going to data/adb/modules/lsposed and open system.prop using text editor and add # before the first line. Save the file and reboot then check exposed.
Lsposed shows me system prop incorrect but everything works normally and momo doesn't detect it anymore.
Click to expand...
Click to collapse
I had heard about that method as well though I haven't tried it yet with App Cloner. I was afraid it would cause unseen problems.
olik2000 said:
I had the same problem with lsposed, I solved it by going to data/adb/modules/lsposed and open system.prop using text editor and add # before the first line. Save the file and reboot then check exposed.
Lsposed shows me system prop incorrect but everything works normally and momo doesn't detect it anymore.
Click to expand...
Click to collapse
I just tried but it still doesn't work with App Cloner. However, my Momo still doesn't show clean results though. Just the ART parameters... is removed now (see attached screenshot).
Can you help?
Thank you in advance!
christantoan said:
I just tried but it still doesn't work with App Cloner. However, my Momo still doesn't show clean results though. Just the ART parameters... is removed now (see attached screenshot).
Can you help?
Thank you in advance
Click to expand...
Click to collapse
I didn't have any of these two problems, could it be that you're using a custom rom? For the traces, I had the twrp/magisk files trace, I just changed the name of the twrp folder and it was solved. Anyway, if I find anything regarding the two problems you have under "details" I'll let you know.
olik2000 said:
I didn't have any of these two problems, could it be that you're using a custom rom? For the traces, I had the twrp/magisk files trace, I just changed the name of the twrp folder and it was solved. Anyway, if I find anything regarding the two problems you have under "details" I'll let you know.
Click to expand...
Click to collapse
Thank you very much for your help as I've been also searching for the solution. For the partition mounted abnormally I've read somewhere it's because of unlocked bootloader though I haven't verified it as I need to stay unlocked.
By the way, I have magisk and lsposed. I downloaded app cloner, went to magisk and hid it in the configure denylist with
"Enforce denylist" disabled
I have the shamiko module activated
My magisk app is hidden
The way lsposed works is that it is only injected in the app you select, so if xposed is applied on all apps, that means all the apps can know if xposed is installed. Make sure to configure that in xposed settings. I've read there's an option called globally or something like that, so disable it if it's there if possible or just switch to lsposed
App cloner works fine for me
christantoan said:
Thank you very much for your help as I've been also searching for the solution. For the partition mounted abnormally I've read somewhere it's because of unlocked bootloader though I haven't verified it as I need to stay unlocked.
Click to expand...
Click to collapse
Mine is unlocked too, so I don't think that's the problem
olik2000 said:
By the way, I have magisk and lsposed. I downloaded app cloner, went to magisk and hid it in the configure denylist with
"Enforce denylist" disabled
I have the shamiko module activated
My magisk app is hidden
The way lsposed works is that it is only injected in the app you select, so if xposed is applied on all apps, that means all the apps can know if xposed is installed. Make sure to configure that in xposed settings. I've read there's an option called globally or something like that, so disable it if it's there if possible or just switch to lsposed
App cloner works fine for me
Click to expand...
Click to collapse
Turns out I've enabled App Cloner in one of my LSPosed module (Minminguard). I've disabled it now and it's working.
olik2000 said:
Mine is unlocked too, so I don't think that's the problem
Click to expand...
Click to collapse
Woah, nice knowing that!
I always thought it was due to my settings.
christantoan said:
Turns out I've enabled App Cloner in one of my LSPosed module (Minminguard). I've disabled it now and it's working.
Woah, nice knowing that!
I always thought it was due to my settings.
Click to expand...
Click to collapse
Happy to hear that, no reboots anymore!
olik2000 said:
Happy to hear that, no reboots anymore!
Click to expand...
Click to collapse
Yep! And it even still works when LSPosed system.prop is restored.
I am currently trying to get a banking app to work, "VR SecureGo Plus". There is also "VR SecureGo", but my bank wants to switch to the new Plus version...
So I have Magisk 24.3, LSPosed 1.8.0, MicroG and FakeGApps as well as Shamiko and Hide My Applist. The Applist Detector shows that nothing can be found - except the LSPosed modules, and specifically the HMA one.
As I got everything working as it should, all I want to do is hide the XPosed modules from the app (both Applist Detector to verify and VR SecureGo Plus to actually use it).
Any idea? Been trying to figure this out for hours now and I have run into several walls - both in terms of finding just about nothing and in terms of text; Google Translate doesn't seem to like Taiwanese a lot :/
Thank you in advance and kind regards,
Ingwie
Spoiler: Full setup info
Device: Razer Phone 2
OS: Lineage OS 18.1, no GAPPS
microG: via microG Installer Revived 2.6.2-0
- Services Core: 0.2.24.21481
Magisk: 24.3
- Shamiko: 0.4.4
- AuroraServices: 1.1.1
- MagiskHide Props: 6.1.2-v137
- Universal SafetyNet Fix: 2.2.1
LSPosed (Zygisk): 1.8.0
- FakeGApps: 3.0 via whew-inc fork
- Hide My Applist: 1.2.2.r296.9cab90a
christantoan said:
Turns out I've enabled App Cloner in one of my LSPosed module (Minminguard). I've disabled it now and it's working.
Click to expand...
Click to collapse
So in a short term xposed can't be hidden from apps enabled in xposed modules.
I wish there is a way to solve this..
IngwiePhoenix said:
I am currently trying to get a banking app to work, "VR SecureGo Plus". There is also "VR SecureGo", but my bank wants to switch to the new Plus version...
So I have Magisk 24.3, LSPosed 1.8.0, MicroG and FakeGApps as well as Shamiko and Hide My Applist. The Applist Detector shows that nothing can be found - except the LSPosed modules, and specifically the HMA one.
As I got everything working as it should, all I want to do is hide the XPosed modules from the app (both Applist Detector to verify and VR SecureGo Plus to actually use it).
Any idea? Been trying to figure this out for hours now and I have run into several walls - both in terms of finding just about nothing and in terms of text; Google Translate doesn't seem to like Taiwanese a lot :/
Thank you in advance and kind regards,
Ingwie
Spoiler: Full setup info
Device: Razer Phone 2
OS: Lineage OS 18.1, no GAPPS
microG: via microG Installer Revived 2.6.2-0
- Services Core: 0.2.24.21481
Magisk: 24.3
- Shamiko: 0.4.4
- AuroraServices: 1.1.1
- MagiskHide Props: 6.1.2-v137
- Universal SafetyNet Fix: 2.2.1
LSPosed (Zygisk): 1.8.0
- FakeGApps: 3.0 via whew-inc fork
- Hide My Applist: 1.2.2.r296.9cab90a
Click to expand...
Click to collapse
Maybe it checks for root?
For my banking app I used:
Magisk Hide
Sudo Hide
Root Cloak
I enabled it on all just to be sure.
*Edit: Sorry my fault, you are already using Shamiko to hide root.

Itsme not working

Any suggestions on how to get the latest itsme working (identity from gouvernance BE). Magisk was renamed and the app is added on the denylist.
For Keytrade bank I have to freeze magisk to get this app working.
Same problem
Hey all!
This has been brought up before here and I'm in the same boat as you guys: itsme is throwing "Rooted device detected" while KeyTrade, Payconiq etc. is working just fine. Please do provide technical details in order to speed up the process of solving this.
My setup:
Magisk 34b2f525 (24316), Zygisk: Yes, Ramdisk: Yes
Magisk App: 34b2f525 (24316) (31), hidden as 'MagicalUnicorn'
DenyList configured and hiding itsme but also Google Play services & Play Store
LSPosed Zygisk 1.8.3 (6552) - Parasitic manager (app isn't installed)
SudoHide is hiding 'Hide My Applist', 'MagicalUnicorn', 'SudoHide' & 'XPrivacyLua' from 'Android System', itsme, etc.
Hide My Applist V2.3.2 is basically doing more of the same
XPrivacyLua 1.30 enables 'Force stop automatically' on 'Use tracking' for itsme & Keytrade
Yet Applist Detector V1.3.2 still detects the following:
abnormal environment
XPrivacyLua (Suspicious)
libc file detection
org.lsposed.manager (Found)
syscall file detection
org.lsposed.manager (Found)
So I'm guessing itsme is tripping over LSPosed's parasitic manager and haven't found how to circumvent this. Where is it detecting this package name?
Also tried with Shamiko instead of enforcing DenyList but the result is the same. Which did bring me to another check tool: Momo. That's reporting "TEE broken" on my end. This post indicates that it may be resolved with some device spoofing so I should probably do further testing with the MagiskHide Props Config by the amazing @Didgeridoohan.
New Magisk released just today so now on 25001 Canary (now the same as v25.0?), which also didn't change anything.
The latest version of itsme 3.8.1 does not work for me. An older versions like itsme 3.6.4 works. I have downloaded this from https://www.apkmonk.com/app/be.bmid.itsme/#previous. There is a reddit thread where I got this information from but I don't know if sites like apkmonk are trusted, so I only tried if I could open the app. I didn't try to acctualy link any eid.
What I use:
Magisk 24.3 (24300); Zygisk: Yes,
Magisk app is hidden
DenyList: itsme, Google Play Store & Google Play Services
Modules:
Universal SafetyNet Fix v2.2.1 by kdrag0n
MagiskHide Props Config v6.1.2-v137 by Didgeridoohan
Universal SafetyNet Fix & MagiskHide Props Config is used to pass Googles SafetyNet Attestation API.
xenorack said:
The latest version of itsme 3.8.1 does not work for me. An older versions like itsme 3.6.4 works. I have downloaded this from https://www.apkmonk.com/app/be.bmid.itsme/#previous. There is a reddit thread where I got this information from but I don't know if sites like apkmonk are trusted, so I only tried if I could open the app. I didn't try to acctualy link any eid.
What I use:
Magisk 24.3 (24300); Zygisk: Yes,
Magisk app is hidden
DenyList: itsme, Google Play Store & Google Play Services
Modules:
Universal SafetyNet Fix v2.2.1 by kdrag0n
MagiskHide Props Config v6.1.2-v137 by Didgeridoohan
Universal SafetyNet Fix & MagiskHide Props Config is used to pass Googles SafetyNet Attestation API.
Click to expand...
Click to collapse
Right, forgot to mention Universal SafetyNet Fix, also using that. I'm down by one version: v2.2.0.
I would also be very careful with apk's from such websites related to applications like this one. The virustotal scan for itsme 3.6.4 showed up clean though but I wouldn't use it either. APKMirror is overall the most trusted alternative but no itsme there. Same for the Amazon app store. My last Titanium Backup of itsme dates from January (3.5.3) and restoring just the app does make it functional again! It flawlessly let me log into my eBox. If anyone wants it, I've attached the 3.5.3 version, which I've extracted via MiXplorer. The main goal remains tackling the new version's anti-root, of course.
Timmmmaaahh! said:
We're having the same problem with a Belgian authentication app called itsme (dedicated thread here, any assistance is most welcome! ). Can you check with Applist Detector and/or Momo what errors it throws at you? No LSPosed? Might be a solution for you.
Click to expand...
Click to collapse
Can't remember where I got this... Think someone asked... Think this passes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can't see it on Play Store... May be an old app...
PW
Same here... Hoping somebody finds a way
Timmmmaaahh! said:
I've experienced a pretty major issue with this as well in the past so I also used unhide prior to updating for a while until someone here told me they fixed that so been updating 'dirty' for the past few months now and working flawlessly every time. My 'MagicalUnicorn' updates just fine
The biggest upside of not unhiding is that I don't need to set up all my hiding measures again after every Magisk update. But you're right, it's best practice not to be as lazy as me and just unhide first.
Click to expand...
Click to collapse
Thanks guys. I'll leave it until the weekend until I try in case I have to start from scratch again. I'll try *dirty* first to see what happens ... and let you know.
robuser007 said:
Any suggestions on how to get the latest itsme working (identity from gouvernance BE). Magisk was renamed and the app is added on the denylist.
For Keytrade bank I have to freeze magisk to get this app working.
Click to expand...
Click to collapse
eboelens said:
Same problem
Click to expand...
Click to collapse
Timmmmaaahh! said:
Hey all!
This has been brought up before here and I'm in the same boat as you guys: itsme is throwing "Rooted device detected" while KeyTrade, Payconiq etc. is working just fine. Please do provide technical details in order to speed up the process of solving this.
My setup:
Magisk 34b2f525 (24316), Zygisk: Yes, Ramdisk: Yes
Magisk App: 34b2f525 (24316) (31), hidden as 'MagicalUnicorn'
DenyList configured and hiding itsme but also Google Play services & Play Store
LSPosed Zygisk 1.8.3 (6552) - Parasitic manager (app isn't installed)
SudoHide is hiding 'Hide My Applist', 'MagicalUnicorn', 'SudoHide' & 'XPrivacyLua' from 'Android System', itsme, etc.
Hide My Applist V2.3.2 is basically doing more of the same
XPrivacyLua 1.30 enables 'Force stop automatically' on 'Use tracking' for itsme & Keytrade
Yet Applist Detector V1.3.2 still detects the following:
abnormal environment
XPrivacyLua (Suspicious)
libc file detection
org.lsposed.manager (Found)
syscall file detection
org.lsposed.manager (Found)
So I'm guessing itsme is tripping over LSPosed's parasitic manager and haven't found how to circumvent this. Where is it detecting this package name?
Click to expand...
Click to collapse
DukeNemesis said:
Same here... Hoping somebody finds a way
Click to expand...
Click to collapse
Itsme detects zygisk ( ONLY ) , follow the few steps below to get it worked properly ( tested on the latest Itsme v3.8.1 ) :
1- Install Magisk alpha. Link
2- Keep Zygisk DISABLED & Enable MagiskHide.
3- Add Itsme to the Configure DenyList and DONE.
Note:
1. Don't use Magisk Canary ( because you can't configure Denylist if you keep Zygisk disabled )
2- No need to add Itsme as effective app in HMA or using ANY additional apps ( sudohide, XPrivacyLua, ...etc ).
Timmmmaaahh! said:
We're having the same problem with a Belgian authentication app called itsme (dedicated thread here, any assistance is most welcome! ). Can you check with Applist Detector and/or Momo what errors it throws at you? No LSPosed? Might be a solution for you.
Click to expand...
Click to collapse
Solved in my Post here.
@Timmmmaaahh!
pndwal said:
Can't remember where I got this... Think someone asked... Think this passes:
Can't see it on Play Store... May be an old app...
Click to expand...
Click to collapse
Yup, I see there's now 3.8.1... can someone link APK so I can try in Australia?...
Eng.Raman said:
Solved in my Post here.
Click to expand...
Click to collapse
No dice with any TJW Zygisk Magisk however?! ... Guess it would be nice for users to get a proper fix for current ItsMe w/ current official Magisk. .. PW
pndwal said:
Yup, I see there's now 3.8.1... can someone link APK so I can try in Australia?...
Click to expand...
Click to collapse
Itsme v3.8.1 Link.
Eng.Raman said:
Itsme detects zygisk ( ONLY ) , follow the few steps below to get it worked properly ( tested on the latest Itsme v3.8.1 ) :
1- Install Magisk alpha.
2- Keep Zygisk DISABLED & Enable MagiskHide.
3- Add Itsme to the Configure DenyList and DONE.
Note:
1. Don't use Magisk Canary ( because you can't configure Denylist if you keep Zygisk disabled )
2- No need to add Itsme as effective app in HMA or using ANY additional apps ( sudohide, XPrivacyLua, ...etc ).
Click to expand...
Click to collapse
Thanks! But ehh..
Debug?
pndwal said:
No dice with any TJW Zygisk Magisk however?! ... Guess it would be nice for users to get a proper fix for current ItsMe w/ current official Magisk. .. PW
Click to expand...
Click to collapse
To get Itsme worked and similar apps that detect zygisk with TJW Magisk Canary/Stable or vvb2060 Magisk alpha ( if zygisk enabled ) you need to wait for a new release of shamiko or Denylist Unmount module with another proper/more hide mechanisms for zygisk.
Timmmmaaahh! said:
Thanks! But ehh..
View attachment 5633699
Debug?
Click to expand...
Click to collapse
No Magisk Debug.
Use the latest vvb2060 Magisk Alpha ( 25001 ). Link
Eng.Raman said:
No Magisk Debug.
Use the latest vvb2060 Magisk Alpha ( 25001 ). Link
Click to expand...
Click to collapse
Oh right, the forked release. I haven't ventured outside official Magisk yet. Is that interchangeable? Say I flash this, can I easily return to official?
Timmmmaaahh! said:
Oh right, the forked release. I haven't ventured outside official Magisk yet. Is that interchangeable? Say I flash this, can I easily return to official?
Click to expand...
Click to collapse
Yes, Best to uninstall vvb2060 magisk alpha first then clean install TJW magisk canary/stable.
Don't dirty flashing each other ( Clean install recommended ).
Good Luck.
Eng.Raman said:
Itsme v3.8.1 Link.
Click to expand...
Click to collapse
Many Thanks!
Confirmed I can't bypass detection for ItsMe 3.8.1 w/ current Magisk 25001.
Eng.Raman said:
To get Itsme worked and similar apps that detect zygisk in TJW Magisk Canary/Stable or vvb2060 Magisk alpha ( if zygisk enabled ) you need to wait for a new release of shamiko or Denylist Unmount module with another proper/more hide mechanisms for zygisk.
Click to expand...
Click to collapse
My conclusion is similar...
However my Momo result for 25001 + latest USNF & Shamiko with Magisk App fully uninstalled (RN8T, Android 10 stock MIUI) shows:
Please say how we know itsme is detecting Zygisk rather than something else... PW

[UNOFFICIAL] LineageOS 20 for the Google Pixel 3a XL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito - Official builds - Potentially coming soon!
bonito - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Oh snap! Thanks for your continued work on our device !!
Thanks for building this for our device. Excited to give it a shot but there's an error with the builds page.
Works as expected. Yet to encounter any bugs!
Thanks a lot for such a great work. I installed it and everything seems to be working fine. Noticed 2 things though:
- Netflix is not available in Play Store. I do not know much about this, but I think Play Integrity API is failing.
- Noticed that only the Google dialer (Phone app) is present. Is it possible to install the Lineage Phone app? I saw in few posts that it supports call recording and that is a must have for me
keertikumar_ws said:
Thanks a lot for such a great work. I installed it and everything seems to be working fine. Noticed 2 things though:
- Netflix is not available in Play Store. I do not know much about this, but I think Play Integrity API is failing.
- Noticed that only the Google dialer (Phone app) is present. Is it possible to install the Lineage Phone app? I saw in few posts that it supports call recording and that is a must have for me
Click to expand...
Click to collapse
On officials it will be, on mine I will only include Google Dialer.
keertikumar_ws said:
Thanks a lot for such a great work. I installed it and everything seems to be working fine. Noticed 2 things though:
- Netflix is not available in Play Store. I do not know much about this, but I think Play Integrity API is failing.
- Noticed that only the Google dialer (Phone app) is present. Is it possible to install the Lineage Phone app? I saw in few posts that it supports call recording and that is a must have for me
Click to expand...
Click to collapse
For Netflix, get it from Aurora Store!
auroraoss.com
npjohnson said:
On officials it will be, on mine I will only include Google Dialer.
Click to expand...
Click to collapse
Yaznas said:
For Netflix, get it from Aurora Store!
auroraoss.com
Click to expand...
Click to collapse
Thanks both of you.
Currently, I am struggling with an authenticator app (that generates code for 2 factor authentication). It works fine in stock ROM. But it is throwing error in this ROM. Tried in both LOS 19.1 and 20 and I am seeing error. I guess, it is being blocked because of custom ROM. Any idea if there is a way to bypass custom ROM detection?
keertikumar_ws said:
Thanks both of you.
Currently, I am struggling with an authenticator app (that generates code for 2 factor authentication). It works fine in stock ROM. But it is throwing error in this ROM. Tried in both LOS 19.1 and 20 and I am seeing error. I guess, it is being blocked because of custom ROM. Any idea if there is a way to bypass custom ROM detection?
Click to expand...
Click to collapse
To block custom rom detection you'll have to get Magisk working and install a few modules.
Universal safetynet fix, MagiskHide props Config, and Shamiko are the 3 I use.
githyanki said:
To block custom rom detection you'll have to get Magisk working and install a few modules.
Universal safetynet fix, MagiskHide props Config, and Shamiko are the 3 I use.
Click to expand...
Click to collapse
I have the Magisk Beta and the modded Universal safetynet fix that is recommended by Magisk Beta for bypassing Integrity API. Shamiko and MagiskHide props dont go well with MagiskHide props Config and Shamiko it seems, so I don't have them. There are couple of banking apps which detected root after this also, but was able to bypass them using 'Hide My Applist'.
Anyway Thanks for the suggestion. For now have flashed the stock. Will try with MagiskHide props Config and Shamiko when I find time and update here.
Thanks for working on this device still. Your work is appreciated! Keeping this thing out of the trash heap
are rom links down? returning "not found" here
ty
Working fine for me.... both sets
adm1jtg said:
Working fine for me.... both sets
Click to expand...
Click to collapse
"not found" on all builds here: https://updater.oddsolutions.us/#/devices/bonito/builds. am i looking at the wrong place?
That exact link works fine for me I see all three builds and the respective recoveries
adm1jtg said:
That exact link works fine for me I see all three builds and the respective recoveries
Click to expand...
Click to collapse
are you able to download them? when i click any of them, that's when "not found" happens. ty
looks like that github is taken down 404 error.
just saw OP posting: "Server is down for maintenance. Back soon."
Long time no see, bud. Gonna give this a run tonight. Be the first time my 3a will have anything custom on it
Any idea when official rom will be released? Thanks

[MODULE] [MOD] Universal SafetyNet Fix

Universal SafetyNet Fix [MOD]
Magisk module
​Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n.
Created for the (temporary?) restoration of working capacity in the conditions of constant change of verification algorithms from Google.
If you can`t wait for update original kdrag0n`s project - feel free to use my little "experimental sandbox"
Usage:
1. Delete/disable/reset MagiskHidePropsConfig (if installed).
2. Just install it over old Universal SafetyNet Fix (if present) and reboot device.
3. You may be needed to wipe GMS data (not cache) if there is no result immediately.
4. Make sure that your SELinux mode sets to Enforcing! Otherwise, run the setenforce 1 command.
Сhecking the results:
Play Integrity API: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck
SafetyNet API: https://play.google.com/store/apps/details?id=rikka.safetynetchecker
Changelog:
Spoiler
v2.4.0-MOD_1.3
* Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp!
* Ignore props changing on Xiaomi.eu. This fixes randomly attestation failings. So strange ROM...
* Added Riru version back. Remember that is need old MagiskHide support (and adding com.google.android.gms/com.google.android.gms.unstable to HideList) !
* Added microG version. Note there is some strange behavior that GMS can crash while run SN attest more than 2 times in one session. Just do not do this. This behavior should not affect applications in real life.
v2.4.0-MOD_1.2
* Fix crash and endless tests loop/failing on Android < 9.0 (bug from original version 2.4.0).
* Do not unpatch (revert) changes. To prevent possible tests failing after a while on some ROMs (cross conflicts).
v2.4.0-MOD_1.1
* Fix KeyStore hook desynchronization (tests randomly failing problem).
v2.4.0-MOD_1.0
* It is now based on top of original v2.4.0 codebase instead of v2.3.1, with adding new hiding algorithm for current realities and some code refreshing.
Downloads: at the bottom of this post or GitHub Releases
Source code: GitHub
It worked on magisk delta, evolution x, zygisk. Thank you
Thank you for helping out and finding a solution to this problem!! v2.4.0-MOD_1.1 seemed to do the trick for me to get Google Wallet back in action on my Pixel 6 Pro! I'll try out MOD_1.2 later as well. You're a rock star!
Goat.
Thx for your unique work!
Yesterday I upgraded to Feb 2023 both security patches and Play System.
Even if I'm still on v2.3.1-MOD_3.0, so far everything works fine. I only had an unusual increase in Google Play Services usage, but seems it was just momentary. I'll stay on this former Mod until it works.
Pixel 6a TQ1A.230205.002
Magisk 25.2
Xiaomi 13 Pro with v2.4.0-MOD_1.2 installed. NFC defaults back to Embedded Secure Element after some time.
Every time I need to change payment to Google Wallet. When I do so, it works fine
You should also consider updating update.json so updates can be seen by the Magisk app of one's choosing
Gigobaito said:
You should also consider updating update.json so updates can be seen by the Magisk app of one's choosing
Click to expand...
Click to collapse
I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems.
Work. Thanks
Was having issues with my fingerprint reader misbehaving on the main 2.4.0 branch on my OnePlus 7T running OOS 12.
Working perfectly with this MOD. Thanks!
CTS was failing on my Poco X3 Pro-installed magisk, installed this, enabled zygisk-CTS passes perfectly now. Thank you so much!
Used 2.3.1-MOD_3.0 without problems. Using v2.4.0-MOD_1.2 now and working fine too. Payed several times today. Thank you (Samsung A70, Android 11)
Using 2.4.0 mod 1.2 on my Pixel and all seems well. Play integrity passes right after boot and so far haven't noticed the tests failing after some time like what used to happen on 1.1. All seems good now, thanks a lot for your hard work!
It worked for me too, thanks.
2.4.0 mod 1.2 working great on my Pixel 4a running latest Feb 2023 OTA.
Could this module have anything to do with Visual Voicemail not activating? After upgrading to A13 I have not been able to get VV to activate (it worked without issue on A12).
creeve4 said:
Could this module have anything to do with Visual Voicemail not activating?
Click to expand...
Click to collapse
Google Phone's VVM can be touchy any time with or without root. Lately there's a bug causing late messages which happens to me sometimes. Unless you changed SIMs it's hard to say why your VVM deactivated after upgrading to 13. To get it working again try turning off wi-fi so that you're only connected to the mobile network. It may not activate right away but should eventually. Other threads about this topic may have better suggestions.
I tried a lot on the new S23 Ultra
Shamiko, MagiskHide, Safetynet 2.4.0 and mod
LSPosed for KnoxGuard but with that gpay wont work.
Theres one point that let Safetynet fail instanly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
com.google.android. gms.unstable
Marianxs said:
I tried a lot on the new S23 Ultra
Shamiko, MagiskHide, Safetynet 2.4.0 and mod
LSPosed for KnoxGuard but with that gpay wont work.
Theres one point that let Safetynet fail instanly
View attachment 5839905
com.google.android. gms.unstable
Click to expand...
Click to collapse
If using Magisk Delta (you mentioned MagiskHide) then better don't use Shamiko
Also, afaik, GPS for AR are not needed in DenyList/MagiskHide
I mean MagiskHidePropsConf
But that have no key for the new S23
No need for other Google apps
ok i know, but i dont thrust Google
What if Google in future update wallet and other Services that use GMS to check root?
you go shopping, try pay and that wont work. I got this several times on my Note20 in the past
Xiaomi Mi10T Lite 5G (Gauguin), DotOS5.0. 2.4 mod 1.2 works like a charm. I owe you a beer, kind sir!

Categories

Resources