[MAGISK MODULE] [APP] Google Pay downgrader for Wear OS on Pie & RootPayEnabler app
OreoPay4PieWear
version 1
Wear Magisk module to downgrade Google Pay on Wear OS Pie to Oreo version to bypass unsupported country message
This module if for all who updated their Wear OS devices to Pie and are locked out of Google Pay due to the Geo-location restrictions on the Pie version that are present for the wear but not the phone. This module will likely become obsolete once Google decides to deprecate the Oreo version of Google Pay and prevent the use of it. Hence please continue to support this thread https://www.reddit.com/r/WearOS/comments/bghqiq/just_talked_with_google_support_they_have_no_idea/
Instructions:
Install/Flash Magisk module: OreoPay4PieWear_v1.zip
Refrain from updating Google Pay in the play store
If accidentally updated, just uninstall updates on the play store page
Optional: Because using this module means that your device is rooted, use my version of PayEnabler attached that uses "pm enable" to re-enable and automatically start Google Pay instead of accessibility services when it gets automatically disabled.
Use Google Pay from unsupported countries on wear again
Changelogs:
v1 - Initial release
-----
RootPayEnabler
{
"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"
}
version 1
Wear application that uses root privileges to enable (if disabled) and open Google Pay automatically
Uses "pm enable" and root (apparently required) to enable Google Pay, then proceeds to open Google Pay
Demo:
https://gfycat.com/boringtestyincatern
Instructions:
Install and open app via ADB: RootPayEnabler.apk (adb install path/to/RootPayEnabler.apk)
On screens that cover the allow button, let the root request dialog to timeout and allow it manually in manager
Allow root access if not allowed yet and re-open the app
Open the app every time Google Pay is needed
Changelogs
v1 - Initial release
Are there people who are unable to add cards due to a rooted device message?
If so, please try this: https://forum.xda-developers.com/showpost.php?p=79636737&postcount=1719
If that still doesn't work, try this: https://forum.xda-developers.com/showpost.php?p=79637148&postcount=1720
Please do let me know which method works so I can incorporate into the Magisk module for v1.2, thank you.
The magisk module is pushed to the watch?
@jarylc appreciate if you can help cause I am not sure I should install the above apk's. I was running Google Pay from @moneytoo here https://forum.xda-developers.com/wear-os/development/app-pay-enabler-android-pay-oreo-t3750815/page8 and it was running perfectly fine and accessibility used to open Google Pay in about 8 seconds, then suddenly and without any updates on my watch (as both play store and system auto-update is turned off) the accessibility feature stopped performing, hence I have to enable google pay manually every time. I am running Wear OS v2.6 on Oreo v8.0.0 and Pay Enabler v6 from the above link. When I uninstall Google Pay, it only gets disabled and it does not actually gets uninstalled. Appreciate if you can help.
Hello, please how to install module into phone through Magisk manager? When I open the menu and select Modules, then I click on the button to browse for modules but it says that no application can perform this action... Thank you.
krecoun said:
Hello, please how to install module into phone through Magisk manager? When I open the menu and select Modules, then I click on the button to browse for modules but it says that no application can perform this action... Thank you.
Click to expand...
Click to collapse
I assume you are talking about the watch...
You have to download a file manager from wear playstore (not all of them work with Magisk) or you can try to flash the module through twrp, but I never tried it so I don't know for sure if it would work
Sent from my SM-T720 using XDA Labs
Can you please recommend a file manager? I tried one but no luck. I tried to flash this file through TWRP and it is not possible.
krecoun said:
Can you please recommend a file manager? I tried one but no luck. I tried to flash this file through TWRP and it is not possible.
Click to expand...
Click to collapse
I think File Explorer FTP Server can do that
jarylc said:
OreoPay4PieWear
version 1
Wear Magisk module to downgrade Google Pay on Wear OS Pie to Oreo version to bypass unsupported country message
This module if for all who updated their Wear OS devices to Pie and are locked out of Google Pay due to the Geo-location restrictions on the Pie version that are present for the wear but not the phone. This module will likely become obsolete once Google decides to deprecate the Oreo version of Google Pay and prevent the use of it. Hence please continue to support this thread https://www.reddit.com/r/WearOS/comments/bghqiq/just_talked_with_google_support_they_have_no_idea/
Instructions:
Install/Flash Magisk module: OreoPay4PieWear_v1.zip
Refrain from updating Google Pay in the play store
If accidentally updated, just uninstall updates on the play store page
Optional: Because using this module means that your device is rooted, use my version of PayEnabler attached that uses "pm enable" to re-enable and automatically start Google Pay instead of accessibility services when it gets automatically disabled.
Use Google Pay from unsupported countries on wear again
Changelogs:
v1 - Initial release
-----
RootPayEnabler
version 1
Wear application that uses root privileges to enable (if disabled) and open Google Pay automatically
Uses "pm enable" and root (apparently required) to enable Google Pay, then proceeds to open Google Pay
Demo:
https://gfycat.com/boringtestyincatern
Instructions:
Install and open app via ADB: RootPayEnabler.apk (adb install path/to/RootPayEnabler.apk)
On screens that cover the allow button, let the root request dialog to timeout and allow it manually in manager
Allow root access if not allowed yet and re-open the app
Open the app every time Google Pay is needed
Changelogs
v1 - Initial release
Click to expand...
Click to collapse
Hi. Can you give a more detailed response on how you rooted the watch and installed the apk? Thank you.
This is great, thanks.
But from time to time the Google Pay app get disabled again.
Did anyone find out what is triggering this?
Is it when the device connects directly to Wifi and google play services checks that we are on a unauthorized country?
I think of an app that can run in the background, or a contrab job, that check if the package is disabled, and enables it again.
@jarylc Did you thought on making this part of the magisk module ?
magisk-gpay-wearos-downgrade
So .. I decided to do it by myself
I created a new magisk module.
This will install the right google pay and will have a job running every 2 hours to enable the package.
In case you want, we can increase/decrease that time.
I will start testing in a daily basis and see how it goes.
Source code here: https://github.com/cinzas/magisk-gpay-wearos-downgrade
I'm also attaching the module in case you want to test it.
So by installing this it will install GPay on my watch? Should I need to root my watch first?
warrencoakley said:
So by installing this it will install GPay on my watch? Should I need to root my watch first?
Click to expand...
Click to collapse
Hi
I have been trying since this morning. I will publish a new one to enable every hour, but this is working fine
To install this on your device you need to have Magisk installed (so yes, root is needed).
What device do you have ?
ashes said:
Hi
I have been trying since this morning. I will publish a new one to enable every hour, but this is working fine
To install this on your device you need to have Magisk installed (so yes, root is needed).
What device do you have ?
Click to expand...
Click to collapse
I have a ticwatch pro.
What do you mean by publish one every hour? Why do you have to do that?
From time to time (didn't find the pattern yet), google detects that the gpay app is enabled on the phone and deactivates it.
I changed the module to turn it on every 30 mins (does not consume battery), so it is always available when you need it - no need to call an app to enable it
Can anybody link me to instructions how to root my ticwatch pro 4g?
edit: nevermind, i already found it. Rooted the watch and succesfully installed this magisk module. Set up my cards and working perfectly! I'll monitor if google pay still gets disabled, but at least it starts! Very happy now. Thanks for this module, great work...
Hey. I have TicWatch Pro 2020 and I'm trying to sideload the OreoPay zip, but I get only error: Updater procces ended with ERROR : 127. Can u help?
Related
Hi everyone,
I'm glad to present my first xposed module: DirectAPKInstall
[What it is]
DirectAPKInstall is a PackageInstaller mod which avoid enabling and disabling "Unknown sources" every single time you need to manually install an APK.
Usually, when you try to install an apk without having "Unknown sources" enabled, an alert stops the installation; this mod replace that alert showing you an alternative pop-up which permits you to install anyway the package without enabling "Unknown sources".
It's an alternative to the "Get in the settings, enable unknown sources, install the package and disable unknown sources" procedure
[Screenshots]
Before:
{
"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"
}
After:
[Downloads]
The module was tested on a Galaxy S3 with CM11; I'm pretty sure it will work on any device with Android OS 4.0+.
If it does not work on your device or it works on a version of Android prior to 4.0 let me know in the comments!
Code:
Plugin: [URL="http://repo.xposed.info/module/it.matsca09.xposedmod.directapkinstall"]http://repo.xposed.info/module/it.matsca09.xposedmod.directapkinstall[/URL]
Source code: [URL="https://github.com/Matsca09/DirectApkInstall"]Github[/URL]
Hope you like it :highfive:
Matsca09
Ehm... OK, good work,
but, is it not better to enable unknow sources by default?
why use it instead?
PeppeBove said:
Ehm... OK, good work,
but, is it not better to enable unknow sources by default?
why use it instead?
Click to expand...
Click to collapse
Sure you can enable "Unknown sources", but there are some people (like me) who don't like leaving it always enabled for various reasons (it's a possible security issue in my opinion).
So I've developed this mod in order to avoid the "Get in the settings, enable unknown sources, install the package and disable unknown sources" procedure I had to do every time I installed an apk.
Matsca09
For Xposed installations I have set up a tasker profile allowing me to install modules and updates right away, and switching off when I leave the xposed installer. But if I install them from my browser,I get the"nag screen"
Thanks, this is exactly what I need
I don't see how its a security issue to just leave unknown sources enabled
Sent from my amazingly awesome OnePlus One using Tapatalk
hi, on ICS I found it opens the install screen in Xposed installer, but doesn't do anything... stays black but the top row with the application's name ...
Disabled, and installation works again.
Done with "unknown sourced" enabled.
I think the only added security of this module is that by leaving unknown sources on, you will get a prompt every time you try to install such on the device so you know when the source is unknown.
ZareliMan said:
I think the only added security of this module is that by leaving unknown sources on, you will get a prompt every time you try to install such on the device so you know when the source is unknown.
Click to expand...
Click to collapse
But the source is *always* unknown
Sent from my amazingly awesome OnePlus One using Tapatalk
Googling and found this... https://securitystreet.jive-mobile.com/#jive-document?content=/api/core/v2/posts/6219
Dont know how true it is.. but i think this module is great for our own precautions :good:. I've xperienced before on some mtk devices installing chinese apk which i know it's not part of system apk that comes with device's rom nor downloaded/installed by myself (tho it's just contains chinese apps link/ads and once installed it's hard to be removed.
Thanks to @Matsca09 for this module. Works on Zenfone 5.
Matsca09 said:
Hi everyone,
I'm glad to present my first xposed module: DirectAPKInstall
[What it is]
DirectAPKInstall is a PackageInstaller mod which avoid enabling and disabling "Unknown sources" every single time you need to manually install an APK.
Usually, when you try to install an apk without having "Unknown sources" enabled, an alert stops the installation; this mod replace that alert showing you an alternative pop-up which permits you to install anyway the package without enabling "Unknown sources".
It's an alternative to the "Get in the settings, enable unknown sources, install the package and disable unknown sources" procedure
[Screenshots]
Before:
After:
[Downloads]
The module was tested on a Galaxy S3 with CM11; I'm pretty sure it will work on any device with Android OS 4.0+.
If it does not work on your device or it works on a version of Android prior to 4.0 let me know in the comments!
Code:
Plugin: [URL="http://repo.xposed.info/module/it.matsca09.xposedmod.directapkinstall"]http://repo.xposed.info/module/it.matsca09.xposedmod.directapkinstall[/URL]
Source code: [URL="https://github.com/Matsca09/DirectApkInstall"]Github[/URL]
Hope you like it :highfive:
Matsca09
Click to expand...
Click to collapse
Great job on this app. Very useful but the only problem is that it doesn't work with the Amazon app. Works fine with the Amazon app store app but not with updating Amazon apps using the regular Amazon app
As far as I know, since the latest update of the Amazon app, you cannot install/update applications via the main application.
Matsca09
Nice work.
chw9999 said:
For Xposed installations I have set up a tasker profile allowing me to install modules and updates right away, and switching off when I leave the xposed installer. But if I install them from my browser,I get the"nag screen"
Thanks, this is exactly what I need
Click to expand...
Click to collapse
Can you share that tasker profile ? Also, can u give me your tasker profiles description ( what it does) in a PM ? Im out of ideas Thank you !
Force said:
Nice work.
Can you share that tasker profile ? Also, can u give me your tasker profiles description ( what it does) in a PM ? Im out of ideas Thank you !
Click to expand...
Click to collapse
Hi, I'd rather write in public
Basically, you need Secure Settings to allow Tasker to switch permit installation of "Unknown sources".
https://play.google.com/store/apps/details?id=com.intangibleobject.securesettings.plugin
Simply, in Tasker...
1. create a profile for Xposed Installer (app start event) or any other app you want to allow to install "Unknown sources"
2. create and add Enter Task -> add step Plugin "Secure Settings" set to allow "Unknown sources"
3. create and add Exit Task -> add step Plugin "Secure Settings" set to deny "Unknown sources"
Done
You can make it more comfortable if you add a wait timer before switching OFF "allow Unknown sources", and a "Kill deny Unknown sources"-Task in the "allow Unknown sources"-Task. This way you may switch shortly to another app without losing "allow Unknown sources". But it is NOT necessary to do so.
Hope it helps!
Cheers,
Christoph
Matsca09 said:
As far as I know, since the latest update of the Amazon app, you cannot install/update applications via the main application.
Matsca09
Click to expand...
Click to collapse
Wonder why... hope they don't plan on phasing out the Amazon App Store app but it seems like they are making efforts to do it
Great work either way!
Mainly because Google changed its Terms of Service for Play store apps (basically no alternative stores inside the Play Store), so they had to split the application into two parts: Amazon Shopping (which you can find on the Play Store), and the Amazon App Store (which you have to download from their website).
All the story: http://9to5google.com/2014/12/11/google-amazon-app-store/
Matsca09
EDIT: the module should be Lollipop-compatible. If there are problems, let me know, thanks.
Version 1.0.1 doesn't work on Galaxy Nexus (Android 4.3). I have to enable unknown sources manually. Version 1.0 works.
degg said:
Version 1.0.1 doesn't work on Galaxy Nexus (Android 4.3). I have to enable unknown sources manually. Version 1.0 works.
Click to expand...
Click to collapse
Thanks for the report.
The new version (1.0.2) should solve your problem (tested on stock 4.3 on Galaxy S3).
Matsca09
Matsca09 said:
EDIT: the module should be Lollipop-compatible. If there are problems, let me know, thanks.
Click to expand...
Click to collapse
Hey @Matsca09 I love this module. It was working great on my Nexus 6 with Android 5.0.1 but looks like 5.1.1 broke it. Can I do anything to help update it so that it works?
sansnil said:
Hey @Matsca09 I love this module. It was working great on my Nexus 6 with Android 5.0.1 but looks like 5.1.1 broke it. Can I do anything to help update it so that it works?
Click to expand...
Click to collapse
Hi sansnil, thanks for the report and sorry for the slow reply.
I've updated the module; now it should work on Android 5.1.1 (tested on 5.1.1 on SGS3)
Please try the new version (1.0.3) and let me know if it works for you
Matsca09
Matsca09 said:
I've updated the module; now it should work on Android 5.1.1 (tested on 5.1.1 on SGS3)
Please try the new version (1.0.3) and let me know if it works for you
Click to expand...
Click to collapse
Hi Matsca09, I just tested 1.0.3 and it does indeed work great again in 5.1.1 -- THANKS!!
Update to Android 11 and Greenify crashes.
[dots] - Settings
It freezes first, then turns into blackscreen for a while, and finally there is "Greenify isn't responding"
This it my first post so outside link isn't possible. Screen recording taken and posted at youtu.be STAzWI1ig7o
Please point it out and help me improve if there is any issue in my first post
{
"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"
}
Just so that you know you are not alone I too am having the exact same problem.
I recently installed it on my rooted pixel 4 XL. Greenify 4.7.5 becomes unresponsive when I choose its settings menu. As soon as I choose settings the screen goes black and the app appears to freeze. I'm running the latest version of Android 11. I've tried deleting cache and data for the app with no success.
I see the app hasn't been updated in a year period I hope it's not dead.
Same problem on Oxygenos 11 (SOLVED)
Any tutorial on how to gather debug info so that I may post them?
I'm New to Android.
@Un1Gfn @burbank @ShosXDA I have got the same unresponsive setting issue on android 11 I have solved this by enabling xposed module. Try it, If it doesn't work for you reply me I will post the proper instruction what I have done to make it work. Tested on OnePlus 8 Pro.
Zer0De8th said:
@Un1Gfn @burbank @ShosXDA I have got the same unresponsive setting issue on android 11 I have solved this by enabling xposed module. Try it, If it doesn't work for you reply me I will post the proper instruction what I have done to make it work. Tested on OnePlus 8 Pro.
Click to expand...
Click to collapse
Thanks for your information. Now on Android 10. I'll back and give a feedback after update my OnePlus 8 to 11 again.
Zer0De8th said:
@Un1Gfn @burbank @ShosXDA I have got the same unresponsive setting issue on android 11 I have solved this by enabling xposed module. Try it, If it doesn't work for you reply me I will post the proper instruction what I have done to make it work. Tested on OnePlus 8 Pro.
Click to expand...
Click to collapse
Hello, I have 8 pro too since today and getting the same issues. Can you please post a short guide? Thank you so much.
By the way, is it still worth to use greenify on android 11? Thank you again
addsfsds said:
Hello, I have 8 pro too since today and getting the same issues. Can you please post a short guide? Thank you so much.
Click to expand...
Click to collapse
Have you installed EdXposed? Just enable greenify module in EdXposed and reboot.
addsfsds said:
By the way, is it still worth to use greenify on android 11? Thank you again
Click to expand...
Click to collapse
I don't use greenify on Android 11 but I managed to make it work.
For battery/memory saving I preferred to manipulate doze mode Instead of killing system apps. I also use Ice Box to disable apps that I don't use daily and Drowser for killing some users apps.
addsfsds said:
Hello, I have 8 pro too since today and getting the same issues. Can you please post a short guide? Thank you so much.
By the way, is it still worth to use greenify on android 11? Thank you again
Click to expand...
Click to collapse
I only use greenify to hibernate apps, I did manage to access settings and disable auto hibernation and tracking but even tracking is wort something as greenify shows you apps that are waking up and how many times.
I have installed lite version and was able to access settings.
I also use aptoide for whatever reason it doesn't go to sleep after you close it down you can see in developers running apps, even if you place aptoide in deep sleeping apps it won't go to sleep with greenify I just press shortcut and all apps I don't want to run in the background are going to sleep immedietaly.
Even for that simple ram almost free shortcut greenify is worth of using on android 11
I'm having the same issue on my OnePlus 8T running Android 11, but I'm sure the settings did work on a previous version of Greenify 'cause I must have set it up with the donation package.
EDIT: Just tried the previous version (4.7.3beta) from APK mirror and the settings menu works fine, so may have to stay back on that version for now.
Greenify 4.7.3 beta (Android 5.0+) APK Download by Oasis Feng - APKMirror
Greenify 4.7.3 beta (Android 5.0+) APK Download by Oasis Feng - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Zer0De8th said:
Have you installed EdXposed? Just enable greenify module in EdXposed and reboot.
I don't use greenify on Android 11 but I managed to make it work.
For battery/memory saving I preferred to manipulate doze mode Instead of killing system apps. I also use Ice Box to disable apps that I don't use daily and Drowser for killing some users apps.
Click to expand...
Click to collapse
It worked for my xiaomi redmi note 6 pro , thank you.
Neither.
Using Xposed allow settings again.
But EdXposed can't passes on SafetyNet and was lied down by the dev. Solution? LSposed.
I didn't like the way that LSposed manage apps (can't understand how Black/white list works) to avoid detections.
Gpay and others apps can't open running any Xposed distro.
Zer0De8th said:
@Un1Gfn @burbank @ShosXDA I have got the same unresponsive setting issue on android 11 I have solved this by enabling xposed module. Try it, If it doesn't work for you reply me I will post the proper instruction what I have done to make it work. Tested on OnePlus 8 Pro.
Click to expand...
Click to collapse
Tested on OOS11 & Evolution X (both on android 11)
Works perfect with LSPosed
Greenify was updated
Download Oasis Feng apps for Android - APKMirror
Download Oasis Feng apps for Android - APKMirror Free and safe Android APK downloads
www.apkmirror.com
I am on android 11, using greenify 4.7.5 + donation package play store, I had to uninstall greenify, install it, go through setup process, from the main screen select settings and leave it there, then issue these cmds through adb
Code:
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
adb -d shell pm grant com.oasisfeng.greenify android.permission.READ_LOGS
tap on doze setting and enable it, go back to settings and enable or disable what ever you want.
now make sure you have what you want because next time try go into settings is the black screen.
Hope this helps.
Let me know if it worked for you.
Hi all, I noticed today that safetynet is suddenly failing. I don't think I made any changes to the system today that would have an affect on SafetyNet. I was playing around yesterday with an exposed module and while doing so, was switching between xposed frameworks to compare them (Edxposed was NOT one of them, because that always trips SN for me).
So I am wondering...did Google make any recent changes to SN that would affect the CTS profile passing?
Is it possible that the experimenting with different xposed frameworks changed the system in such a way that the only way to get SN back is to start from scratch?
Thanks for any insights you might have.
Yes, SafetyNet API got changed: it no longer looks for a phone's CTS profile locally stored on phone but externally stored on Google server - uploaded there by phone's manufacturer.
{
"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"
}
The cat-and-mouse game has ended.
jwoegerbauer said:
Yes, SafetyNet API got changed: it no longer looks for a phone's CTS profile locally stored on phone but externally stored on Google server - uploaded there by phone's manufacturer.
Click to expand...
Click to collapse
Where did you get this info from?
Pls send link
devaponnadsm said:
Where did you get this info from?
Pls send link
Click to expand...
Click to collapse
SafetyNet Attestation API | Android Developers
The SafetyNet Attestation API provides services for determining whether a device running your app satisfies Android compatibility tests.
developer.android.com
jwoegerbauer said:
The cat-and-mouse game has ended.
Click to expand...
Click to collapse
People have said that before.....i said just two days ago that if google suddenly finds a way to bypass magiskhide for good, then i'd be inclined to blame topjohnwu.
Is there absolutely no way around this?
Magisk no longer can't prevent this, because it can't intercept this server-side query.
Take note that the developer of Magisk has already adnitted that!
MagiskHide became obsolete.
jwoegerbauer said:
Magisk no longer can't prevent this, because it can't intercept this server-side query.
Take note that the developer of Magisk has already adnitted that!
MagiskHide became obsolete.
Click to expand...
Click to collapse
And all this happened yesterday?
Depends on when Google Play Services Framework got updated on your phone: SafetyNet is integral part of Google Play Services Framework.
OK. I set up the XPrivacyLua with the assistance of this youtube video.
I only watched the video once and set it up using the google play store app. but after reading your response, I set it up using the "google play services" process, and now my phone passes safetynet again.
Hope this helps someone.
gfrank227 said:
OK. I set up the XPrivacyLua with the assistance of this youtube video.
I only watched the video once and set it up using the google play store app. but after reading your response, I set it up using the "google play services" process, and now my phone passes safetynet again.
Hope this helps someone.
Click to expand...
Click to collapse
Its work for me is poco x3 pro , thanks
Hi @gfrank227 et all.
My Safetynet was working due to the instructions in the video you posted above. This could be a classic case of 'If it ain't broke don't try and fix it'.
I got a Magisk update message, and 'perhaps stupidly' I installed it in Magisk. I then lost my 'Check SafetyNet' option in the main screen of Magisk, and in Magisk Settings I lost the 'MagiskHide' option.
I also got a message to update LSposed, so I downloaded the zip, and decided to re-follow the youtube video above again this time installing the new LSposed zip.
Nothing's changed, I still have those missing options in Magisk, and also now in Google Play Store my device is now showing as 'Not Certified'.
SafetyNet Test App states 'Failed'.
However, LSposed & XPrivacyLua are actually set up correctly as per the youtube video.
Not sure how to proceed to fix this. Could really do with my Google Pay back.
jaccydan said:
Hi @gfrank227 et all.
My Safetynet was working due to the instructions in the video you posted above. This could be a classic case of 'If it ain't broke don't try and fix it'.
I got a Magisk update message, and 'perhaps stupidly' I installed it in Magisk. I then lost my 'Check SafetyNet' option in the main screen of Magisk, and in Magisk Settings I lost the 'MagiskHide' option.
I also got a message to update LSposed, so I downloaded the zip, and decided to re-follow the youtube video above again this time installing the new LSposed zip.
Nothing's changed, I still have those missing options in Magisk, and also now in Google Play Store my device is now showing as 'Not Certified'.
SafetyNet Test App states 'Failed'.
However, LSposed & XPrivacyLua are actually set up correctly as per the youtube video.
Not sure how to proceed to fix this. Could really do with my Google Pay back.
Click to expand...
Click to collapse
You must have installed the latest magisk canary. Have you tried the magisk module universal safety net fix?
Thanks for the reply, sorry it took so long to get back to you - (for some reason I didn't get an email notification, but never mind).
Anyway, yes I was looking at those very 2 things. I actually went into Magisk and 'installed from storage' the latest safety net fix, but nothing's changed.
With Canary, I have gone into the Magisk App tab in settings, and clicked on 'Update Channel', then clicked on Canary, but nothing happens. What am I doing wrong here?
I think this Canary build thing could be the answer.
I am also unsure if I need to download a latest canary apk and install it via Odin or something. Not sure how to proceed.
Thanks in advance.
Here's my Magisk Home Screen:
Some additional information:
Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.
jaccydan said:
Thanks for the reply, sorry it took so long to get back to you - (for some reason I didn't get an email notification, but never mind).
Anyway, yes I was looking at those very 2 things. I actually went into Magisk and 'installed from storage' the latest safety net fix, but nothing's changed.
With Canary, I have gone into the Magisk App tab in settings, and clicked on 'Update Channel', then clicked on Canary, but nothing happens. What am I doing wrong here?
I think this Canary build thing could be the answer.
I am also unsure if I need to download a latest canary apk and install it via Odin or something. Not sure how to proceed.
Thanks in advance.
Here's my Magisk Home Screen:
View attachment 5441241
Some additional information:
View attachment 5441249
Click to expand...
Click to collapse
Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.
gfrank227 said:
Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.
Click to expand...
Click to collapse
This might sound stupid but when I go into modules there seems to be no way now of searching for modules online through Magisk - it only seems to be an option to install from storage, so I can see if I need to update magiskhide props config.
Btw, I already have a version of magiskhide props config activated, so I probably don't need to do anything with that.
This page states ( I think) that yesterday this v.23.0 build of Magisk has been updated with a new Canary build:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I think therefore I need to install this Magisk version and then activate Canary in it.
I'm a newbie, so if you could advise me which method to install this, it would be much appreciated. Am i going back to Twrp or Odin or can I do it more easily via the Magisk app? I came across this page explaining various installation methods, but I'm not sure which one to follow in my circumstance:
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks.
jaccydan said:
This might sound stupid but when I go into modules there seems to be no way now of searching for modules online through Magisk - it only seems to be an option to install from storage, so I can see if I need to update magiskhide props config.
Btw, I already have a version of magiskhide props config activated, so I probably don't need to do anything with that.
This page states ( I think) that yesterday this v.23.0 build of Magisk has been updated with a new Canary build:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I think therefore I need to install this Magisk version and then activate Canary in it.
I'm a newbie, so if you could advise me which method to install this, it would be much appreciated. Am i going back to Twrp or Odin or can I do it more easily via the Magisk app? I came across this page explaining various installation methods, but I'm not sure which one to follow in my circumstance:
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks.
Click to expand...
Click to collapse
Yeah, so it's not stupid. You're right. Topjohnwu, the developer of magisk recently joined the Google security team. As a result, magisk development was put on hold pending approval. Due to conflicts of interest, it was determined that he would not be creating software intended to get around Google's security checks. This is the reason why Magiskhide is gone in the newest canary build.
The other change he made was to remove the built-in modules. You will have to therefore download the zip file for magiskhide props config from github. The props in magiskhide props config were only added in the past couple of months. so you should make sure you are downloading the latest version, or at least the one right before the latest.
If you have both modules I reference and are still failing, then this is because these modules were not intended to fully replace magiskhide. I am confident that eventually they will be able to fully replace it; but until then, you should simply uninstall the magisk manager and then install the apk from the github site that you reference above. That's the correct latest stable version. Then, forget about the canary version.
After the canary version goes as a full update, I recommend that you don't update magisk right away but wait until there's a suitable replacement module that works.
Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager. In theory, you should then have magiskhide back and pass safety-net.
Eventually, of course, google will find a way to bypass this so eventually, we will certainly need to hope for a fix. But this is the best solution for the short term.
If you look at the change-log from the three or four most recent releases, you'll be able to see if magiskhide props config you are running has the magiskhide props.
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
gfrank227 said:
simply repatch using the magisk app
Click to expand...
Click to collapse
Thanks for that info @gfrank227 that is very helpful.
When you said the above (see quote), do I need to rename that Magisk .apk to .img before using Magisk Install to 'Select and Patch a File' from out of my downloads folder?
It's the 2nd part of your reply that I'm stuck on:
"Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager."
Can you run me through this process, I'm not familiar with patching images?
Went from stock to Lineage 18.1 no issues
installed latest Magisk 24.3
Zygisk enabled
Deny list enabled
Systemless host enabled
Universal SafteyNet fix 2.2.1 installed.
Root is working fine, but seems like google is still detecting this tablet is rooted, and it wont show Netflix and Disney+ for install.
Yes, I know I can side-load it, but that means there is still a problem with other apps, like Banking apps or other Apps that checks for rooted devices.
Did I miss anything to make SafetyNet work?
On other Samsung phones it's been so hit and miss. I always make sure to include all Google services and framework (all the relevant ones, anyway) and I always delete Playstore data and Netflix still doesn't appear on Playstore. Out of nowhere it appears the next day. And then any random day it disappears again. Honestly I don't know what the heck it takes. But I can say this: Even if Netflix doesn't appear on Playstore, if I add my banking apps on Deny list it does hide it successfully from the banking apps. So I would not correlate one thing to the other. You can always download a safetynet checker to make sure you're passing it.
Nope, did not work at all, tried all that already.
Amazon Prime will not show the local channels.
Netflix even when sideloaded will not play
Disney+ is working fine.
some other security sensitive Apps, wont work even after hiding them with Magisk and enforce hidden, as well has hidden Magisk.
CTS always fails the SafetyNet test.
AllGamer said:
CTS always fails the SafetyNet test.
Click to expand...
Click to collapse
Well then this is your problem right here. If I remember correctly, you fix the CTS profile by installing MagiskHide Props Config and installing either your device's stock props or that of a similar device.
ShaDisNX255 said:
Well then this is your problem right here. If I remember correctly, you fix the CTS profile by installing MagiskHide Props Config and installing either your device's stock props or that of a similar device.
Click to expand...
Click to collapse
Thanks, I gave that a try, installed the module, rebooted the tablet, ran the SafetyNet test again and same error CTS profile issue.
I tried it on both Lineage 18 and 19, same issue.
At this point I think i'm going to flash it back to Stock, so I could watch my shows and TV, as that was the main purpose of the tablet, as a portable "TV"
Failing the CTS profile test is causing all kind of weird issues with the Stream Apps not allowing me to watch some contents, or simply not running at all like Netflix.
AllGamer said:
Thanks, I gave that a try, installed the module, rebooted the tablet, ran the SafetyNet test again and same error CTS profile issue.
Click to expand...
Click to collapse
Do you know how it works? I'm not trying to be rude I just want to make sure you know how to run the module because this kind of makes me think you installed the module and didn't run it
And if you did, did you try a few different props or just 1?
ShaDisNX255 said:
Do you know how it works? I'm not trying to be rude I just want to make sure you know how to run the module because this kind of makes me think you installed the module and didn't run it
And if you did, did you try a few different props or just 1?
Click to expand...
Click to collapse
Actually I do not know.
I was under the impression it's like most other modules that you install and forget about it types.
It shows up in Magisk, it only has an On/Off option, was there something else that was supposed to show for settings ?
AllGamer said:
Actually I do not know.
I was under the impression it's like most other modules that you install and forget about it types.
It shows up in Magisk, it only has an On/Off option, was there something else that was supposed to show for settings ?
Click to expand...
Click to collapse
This one in particular is a little more complex.
After installing and rebooting, you're supposed to run it via a terminal emulator. I used Termux.
Give it root perms with "su" and then type props and make your selections accordingly. It gives you a few options, your goal is to change the props to a device to pass CTS profile
Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.
You can also run the command with options. Use -h for details.
Thanks for the heads up, I'll give that a try.
@ShaDisNX255 Thanks, that took care of the CTS profile issue,
{
"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"
}
but the Netflix and Prime Video are still having issues, Netflix gives error "Cannot reach Netflix Service, please try again -93" this guy has exactly the same error I'm getting https://github.com/kdrag0n/safetynet-fix/issues/176
They are using OnePlus 10 running Android OS 12, but that seems to suggest it might be an issue with Magisk 24.3 not hiding / bypassing rooted check properly.
The issue in Prime Video, is that it hides the local and other included channels section.
AllGamer said:
@ShaDisNX255 Thanks, that took care of the CTS profile issue,
View attachment 5617327
but the Netflix and Prime Video are still having issues, Netflix gives error "Cannot reach Netflix Service, please try again -93" this guy has exactly the same error I'm getting https://github.com/kdrag0n/safetynet-fix/issues/176
They are using OnePlus 10 running Android OS 12, but that seems to suggest it might be an issue with Magisk 24.3 not hiding / bypassing rooted check properly.
The issue in Prime Video, is that it hides the local and other included channels section.
Click to expand...
Click to collapse
I also have Magisk 24.3 and I just downloaded Netflix and played something with no problem
But I am using OneUI so there could be a problem somewhere in aosp. Hopefully you can find a resolution, I'm out of ideas.
Netflix don't even show up on latest stock ROM, seems to be a netflix restriction for this device.
Just install the latest netflix or disney .apk from APKPure.
Worked for me on stock ROM as well as on HavocOS ROM.
All features, incuding HDR are working as they should.
With magisk v25.2 ,passed safety net , clear play store and play services data rebooted but netflix not showing up on my note 7 pro
Hello everyone,
So my banking app instapay is a harsh one when it comes to root, I've tried everything to hide it but failed. I have magisk 24.3, zygisk and lsposed installed. Stock may update pixel 6
I have tried to enforce deny list and normal, also installed a bunch of hiding tools like Enhance mode for HideMyApplist, Shamiko , Universal SafetyNet Fix, xprivcylua and all failed.
I would appreciate your help the app would crash on first start. Im also okay with any virtual space solution that would work as well i tried island with work profile and parallel space both failed too
InstaPay Egypt - Apps on Google Play
InstaPay enables you to send and receive money instantly 24x7.
play.google.com
Not sure if anyone here is going to have a solution, especially where you have tried all the standard solutions. You may simply have to deal with not using the app on your device.
The only thing I can suggest is getting rid of your Xposed clone. The app I believe is almost certainly detecting it.
Similar situation for me recently with Citibank, I have only Universal SafetyNet Fix and MagiskHide Props Config installed as modules, nothing else.
Magisk 24.3 was hidden, Citibank worked until May 14. This day it suddenly detected Magisk and told me me right out your mobile is rooted with Magisk or any other app.
I added a second user, installed Citibank for the second user and it worked. (seems it doesn't care that the bootloader is unlocked).
Then, I tried the following as Main user::
1. deleted Data and Cache from Citibank
2. Unhide Magisk, Hide it again but this time a new name (not the standard suggestion "Settings")
3. Opened Citibank again, logged in and it worked.
4. Deleted the second user again (optional)
Why? Can't give a specific reason, but a possibility is, that 2 x Settings in the AppDrawer was flagged as suspicious.
So you could try to have a second profile on your mobile or try the steps above.
Cheers
Tom
If you are using adaway to block ads via root, run the DNS log to see what urls the app is trying to connect to.
I had this issue with a UK Halifax banking app, all was working fine until middle of May, and then i found a new URL the app was connecting to, when i blocked it, it worked OK,
Moe information on this here:-
[How To] Bypass Lloyds and Santander Root Detection
Hi All, I've seen mention of Santander but not of Lloyds bypassing the root detection. After much trial and error it's quite simple and my method will bypass both Santander and Lloyds. If bypassing Santander just do the same for the Santander...
forum.xda-developers.com
Is there a way to hide lposed?
@xxqxpxx
Instapay detects zygisk
Only way around is Magisk Alpha with magisk hide activated (It's on Telegram)
Riru, Riru Universal Safetynet fix and Riru xposed (if needed).
Configure the deny list as per screenshot.
Reboot and you're good to go
{
"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"
}
shoey63 said:
@xxqxpxx
Instapay detects zygisk
Only way around is Magisk Alpha with magisk hide activated (It's on Telegram)
Riru, Riru Universal Safetynet fix and Riru xposed (if needed).
Configure the deny list as per screenshot.
Reboot and you're good to goView attachment 5623057
Click to expand...
Click to collapse
can you give me the link for the telegram alpha download please
I'd suggest to download any Magisk only from the official source: https://github.com/topjohnwu/Magisk
Currently the following downloads are available:
Magisk v24.3, Version Code 24300
Magisk Beta: v24.3, Version Code 24300 (same as final)
Magisk Canary: v24.313, Version Code 8dfb30fe
Magisk Debug: v24.313, Version Code 8dfb30fe
Cheers
Tom
xxqxpxx said:
can you give me the link for the telegram alpha download please
Click to expand...
Click to collapse
No Telegram links allowed on XDA so here you go.
Also don't worry about Alpha Magisk Devs. They are MAJOR contributors to the official TJW Magisk code. All transparent on Github
you can disable magisk and enable it when ever you want .
you my need to disable Adaway as well
use this app https://play.google.com/store/apps/details?id=com.iamaner.oneclickfreeze
Ibramj12 said:
you can disable magisk and enable it when ever you want .
you my need to disable Adaway as well
use this app https://play.google.com/store/apps/details?id=com.iamaner.oneclickfreeze
Click to expand...
Click to collapse
Didn't work
This is what they use : any ideas?
public static boolean isRooted(Context context) {
String str = Build.TAGS;
if ((!isEmulator && str != null && str.contains("test-keys")) || new File("/system/app/Superuser.apk").exists()) {
return true;
}
return !isEmulator && new File("/system/xbin/su").exists();
}
xxqxpxx said:
This is what they use : any ideas?
public static boolean isRooted(Context context) {
String str = Build.TAGS;
if ((!isEmulator && str != null && str.contains("test-keys")) || new File("/system/app/Superuser.apk").exists()) {
return true;
}
return !isEmulator && new File("/system/xbin/su").exists();
}
Click to expand...
Click to collapse
This is common check most apps will have it.
i tried the app. i belive its Egpt instapay. i was able to run it without error but cant see the login page.
I used the below module and it solved the instapay problem along with the latest myfawry update issue with root
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
Only Install it and disable deny list
tom1807 said:
Similar situation for me recently with Citibank, I have only Universal SafetyNet Fix and MagiskHide Props Config installed as modules, nothing else.
Magisk 24.3 was hidden, Citibank worked until May 14. This day it suddenly detected Magisk and told me me right out your mobile is rooted with Magisk or any other app.
I added a second user, installed Citibank for the second user and it worked. (seems it doesn't care that the bootloader is unlocked).
Then, I tried the following as Main user::
1. deleted Data and Cache from Citibank
2. Unhide Magisk, Hide it again but this time a new name (not the standard suggestion "Settings")
3. Opened Citibank again, logged in and it worked.
4. Deleted the second user again (optional)
Why? Can't give a specific reason, but a possibility is, that 2 x Settings in the AppDrawer was flagged as suspicious.
So you could try to have a second profile on your mobile or try the steps above.
Cheers
Tom
Click to expand...
Click to collapse
One thing I noticed whenever I updated the Citibank app is that it always turns off something in DenyList that was previously turned on, causing it to catch root. All I do now is whenever I updated the Citibank app, I check DenyList to make sure none of the Citibank files have been turned off. If so, I just turn it back on and all is good.
I have problem with instalation and I had test every thing and still have same problem
Any one have solution to this case
Its working for me here, and thats my setup: magisk delta (google it) using riru & magiskhide (the old root hiding way) with modules: USNF, riru momohider, riru lsposed, riru enhanced mode for magisk hide, MHPC, initrchider & hiding the app in magisk via magiskhide
AhmadOkda said:
I used the below module and it solved the instapay problem along with the latest myfawry update issue with root
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
Only Install it and disable deny list
Click to expand...
Click to collapse
Thanks bro this really helped me
AhmadOkda said:
I used the below module and it solved the instapay problem along with the latest myfawry update issue with root
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
Only Install it and disable deny list
Click to expand...
Click to collapse
تسلم ياكبير
The latest Update (1.5.4) Requires More work to hide root it includes most of work done here in this thread but will be explained without reading all comments
1) Update Magisk Alpha to v26 and Enable Zygisk
2)Install Universal SafteyNetFix Mod (You Should use this )
[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...
forum.xda-developers.com
3) Install Shamiko latest update
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
4) Dont Enfore Zygisk and Add InstaPay to Denylist
5) Clear Data to G Play Services ,Reboot and Enjoy