Do you guys have any fixes to this issue? I've hidden magisk and hidden pubg new state within magisk but nothing works.
It's easy for any app to detect whether Android is got rooted or Magisk got installed or device's bootloader got unlocked.
{
"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 found one lib file but i dont know how to edit lib
I will attach that file here, if anyone can modify it then ig we can play New state on rooted phones Lib file that detects root
1 Disable Developer Options
2 Add the game in Magisk Hide
3 Install Airfrozen app and use it to freeze Magisk app
4 Run the game
5 Make sure to thaw Magisk after playing the game within Airfrozen
k4ustu3h said:
1 Disable Developer Options
2 Add the game in Magisk Hide
3 Install Airfrozen app and use it to freeze Magisk app
4 Run the game
5 Make sure to thaw Magisk after playing the game within Airfrozen
Click to expand...
Click to collapse
Thanks now I can play pubgi
Unfortunately none of those worked for me. But you can delete or rename libbugsnag-root-detection.so
from its data/app/libs dir then the game starts for me.
Im Also using magisk and have an unlocked bootloader.
Update : it doesn't work the second time
k4ustu3h said:
1 Disable Developer Options
2 Add the game in Magisk Hide
3 Install Airfrozen app and use it to freeze Magisk app
4 Run the game
5 Make sure to thaw Magisk after playing the game within Airfrozen
Click to expand...
Click to collapse
That worked, thanks!
The game keep crashing after a while, couldn't finish the update
k4ustu3h said:
1 Disable Developer Options
2 Add the game in Magisk Hide
3 Install Airfrozen app and use it to freeze Magisk app
4 Run the game
5 Make sure to thaw Magisk after playing the game within Airfrozen
Click to expand...
Click to collapse
I cant seem to find where to hide apps in magisk. All i find is the hide magisk in magisk settings but not where to hide specific apps. I am running on magisk 23 and andriod 10 oneplus 7 pro.
BlurAirll said:
I cant seem to find where to hide apps in magisk. All i find is the hide magisk in magisk settings but not where to hide specific apps. I am running on magisk 23 and andriod 10 oneplus 7 pro.
Click to expand...
Click to collapse
MagiskHide was removed in Magisk 23014. You can't hide your apps anymore.
You will have to downgrade your Magisk or find another alternative.
SlightlyWind said:
That worked, thanks!
The game keep crashing after a while, couldn't finish the update
Click to expand...
Click to collapse
Update: did a clean install with the same magisk patch root applied today. The game starts with magisk disabled, dev options off with (almost) the same root apps. Running fine which does not explain at all why did it crash, or forced close
Yeah Im going to try those now. I thought It was because it could tell we had our bootloader's unlocked
Mohammed saliq said:
I found one lib file but i dont know how to edit lib
I will attach that file here, if anyone can modify it then ig we can play New state on rooted phones Lib file that detects root
Click to expand...
Click to collapse
libbugsnag-root-detection.so dissassembled
they seem to be looking for these to confirm your device either has root or enabled adb start adbd confirms this
so, if an app is actively using root at the start of the game, or adbd is started, the game won't start (notice I left adbd running after exit root):
https://imgur.com/a/uToFxep
however
1324khaled said:
Unfortunately none of those worked for me. But you can delete or rename libbugsnag-root-detection.so
from its data/app/libs dir then the game starts for me.
Im Also using magisk and have an unlocked bootloader.
Update : it doesn't work the second time
Click to expand...
Click to collapse
either they have a backup file placed somewhere else, or they have a fallback solution
also
SlightlyWind said:
That worked, thanks!
The game keep crashing after a while, couldn't finish the update
Click to expand...
Click to collapse
SlightlyWind said:
Update: did a clean install with the same magisk patch root applied today. The game starts with magisk disabled, dev options off with (almost) the same root apps. Running fine which does not explain at all why did it crash, or forced close
Click to expand...
Click to collapse
Cooro said:
Do you guys have any fixes to this issue? I've hidden magisk and hidden pubg new state within magisk but nothing works.
Click to expand...
Click to collapse
I have orange fox recovery and I uninstalled magisk and then installed new state.I then installed magisk through orange fox as zip and installed needed modules and enabled magisk hide and now i have root and pubg new state also runs.I thinks It was by pure chance but I did all this today.It is running right now and I still have root.This only worked this time as the last time I tried with Twrp and it did not work then.Maybe I am lucky.I have a poco x3 pro a12 8/256 with base rom.Maybe you can also try my process and you might get lucky.
SORRY FOR GRAMMAR AND THIS IS ALSO MY FIRST POST SO I HOPE IT HELPED IN ANY WAY.
Somehow I've managed to run new state after installing the module shamiko on magisk.
Basically, just do all the previous steps, with shamiko module installed on magisk.
ViGard03 said:
Somehow I've managed to run new state after installing the module shamiko on magisk.
Basically, just do all the previous steps, with shamiko module installed on magisk.
Click to expand...
Click to collapse
Thanks bro installing shamiko and disabling deny list worked
i tried shamiko + airFrozen still crashes at start
AddictedA1 said:
i tried shamiko + airFrozen still crashes at start
Click to expand...
Click to collapse
Did you put new state in deny list?
yes but deny list has to turn off for shamiko to work both cases dosen't start
EDIT: WORKING !! I havent installed lspeed modules correctly while making axis bank app work figured everything.
ViGard03 said:
Did you put new state in deny list?
Click to expand...
Click to collapse
AddictedA1 said:
yes but deny list has to turn off for shamiko to work both cases dosen't start
EDIT: WORKING !! I havent installed lspeed modules correctly while making axis bank app work figured everything.
Click to expand...
Click to collapse
Help me please, I'm using magisk 26, shamiko, safetynet fix, magisk hide and freeze magisk with ice box.
New state crashes few seconds after launch
Related
Master_T has modified the standard YouTube with the modification from the Xposed module and packaged it into a working APK. He then integrated Arter97's ad-free modification to the app. Better yet, another user has created a Magisk module for the modified app so you won't have to mess with your system partition.
The YouTube adaway and background-playback Xposed modules were the only reason I even considered rolling back to Marshmallow. Now, there's nothing compelling me to return. I have installed the app on OOS 4.0.3 Nougat and background playback is working flawlessly without ads.
You do need to be rooted to install the app. You will also have to uninstall the stock YouTube app to use it, even with the use of the Magisk module. I tried flashing the Magisk module without deleting the stock app, and reverting the stock app back to factory condition, but it kept overriding the Magisk-mounted modified app.
Check out the original thread for more details.
Also, if you want to disable the modded YouTube app's market link to prevent accidental auto-updates, check out hinxnz's script, which also happens to be Magisk compatible. It's a simple script that runs 60 seconds after boot and removes market links from certain apps every time you boot. While it was developed to mask substratum theme-ready apps, they work for original and modded versions of the apps as well.
Note, 360 degree videos will cause the app to crash unless you extract the lib folder from the app and place it into /system/app/YouTube/lib and granting the folders 755 and files 644 (permissions). I've remade the Magisk version such that it includes the lib folders in the correct location with the correct permissions, link is posted below. This Magisk module contains only the ad-blocked and background playback-enabled version of the modified YouTube app for ARM64 devices (such as the OP3/T) and will not work for ARM(32) or Intel devices. You can flash this in Magisk or TWRP. Don't forget to delete your stock YouTube app first. I have tested this Magisk module on my OP3T running OOS 4.0.3. This should work on any other ROM that Magisk works on. Magisk is required for this module, you can download the original (non-Magisk) modified APKs from Master_T's thread. Please also visit his thread to thank him~
Edit: You do not have to completely delete your YouTube folder using a root-enabled app or through TWRP. The Magisk module now works if you remove the updates to YouTube from /data/app.
Simply go into Settings > App > YouTube and delete updates (restore to factory settings).
You can achieve this by disabling the app in settings, then re-enabling it.
The link has been updated.
Ad-Blocked/BG-Playback/360-Enabled Magisk Module v12.27.57 (by @ZaneZam):
https://drive.google.com/open?id=0B8lY7pYQ4GSzUkpWTFppR1huWE0
Original Developer: Master_T
Main Thread: https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900
{
"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"
}
Magisk module did not work. I also didn't uninstalled the stock youtube.
Background playing is working on Magisk Module: OOS OB3. Adblock doesn't seem to work. Adblock wasn't integrated in the magisk module. Pushing Apk manually to system works as a charm.
If you want to use the ad-blocked version with magisk, you can simply open the zip for the magisk module and replace the modded YouTube app inside with the version you want. The original magisk module on the post contains the non-ad-blocked, bg-enabled app by default.
Correct Lucky Patcher is considered warez and is not to be discussed on XDA.
Thread cleaned.
Thanks,
Sloth
Confirmed working on Oneplus 3T
timeToy said:
Confirmed working on Oneplus 3T
Click to expand...
Click to collapse
Magisk or apk? When I try to install any of the APK they say corrupt.
Any way to successfully remove system apps on stock rooted OB3? Titanium backup and similar apps do not remove successfully.
yung40oz84 said:
Magisk or apk? When I try to install any of the APK they say corrupt.
Click to expand...
Click to collapse
Magisk version is working on my OP3T with OOS 4.0.3. You still have to delete the stock YouTube app from system if you use Magisk though.
k.s.deviate said:
Any way to successfully remove system apps on stock rooted OB3? Titanium backup and similar apps do not remove successfully.
Click to expand...
Click to collapse
I had used ES File Explorer's system app removal tool to remove the old YouTube app, though you could probably use any root explorer to manually delete the YouTube folder from /system/apps
yung40oz84 said:
Magisk or apk? When I try to install any of the APK they say corrupt.
Click to expand...
Click to collapse
I used the apk, no ads and background playback.
- Restore Youtube to the stock system app (Uninstall updates)
- Delete the stock Youtube app from systems/app/Youtube
- Copy the modded Youtube apk in the same folder and set the permissions
---------- Post added at 10:12 ---------- Previous post was at 10:11 ----------
k.s.deviate said:
Any way to successfully remove system apps on stock rooted OB3? Titanium backup and similar apps do not remove successfully.
Click to expand...
Click to collapse
I used Root explorer
timeToy said:
I used the apk, no ads and background playback.
- Restore Youtube to the stock system app (Uninstall updates)
- Delete the stock Youtube app from systems/app/Youtube
- Copy the modded Youtube apk in the same folder and set the permissions
---------- Post added at 10:12 ---------- Previous post was at 10:11 ----------
I used Root explorer
Click to expand...
Click to collapse
Nothing I use will remove system apps. Its strange..
k.s.deviate said:
Nothing I use will remove system apps. Its strange..
Click to expand...
Click to collapse
Let me guess: read-only file system, remount failed. OOS based custom ROM or stock ROM.
ast00 said:
Let me guess: read-only file system, remount failed. OOS based custom ROM or stock ROM.
Click to expand...
Click to collapse
Yes.. stock OB3 or 4.0.3 rooted. I've never encountered this before.
k.s.deviate said:
Yes.. stock OB3 or 4.0.3 rooted. I've never encountered this before.
Click to expand...
Click to collapse
Just use the TWRP file manager. Works wonders.
ast00 said:
Just use the TWRP file manager. Works wonders.
Click to expand...
Click to collapse
It didn't allow me to replace, but I'll try and use it to delete.
It was pointed out that 360 degree video causes the app to crash due to a missing lib folder. I've made a Magisk module for the ad-blocked version of the app with the correct lib placement and uploaded it, link's in the first post as well as Master_T's original thread. It is now fully functional, as far as I can tell anyways.
Any way to disable the app from updating in the playstore? When youtube updates itself the mods are gone.
Znil said:
Any way to disable the app from updating in the playstore? When youtube updates itself the mods are gone.
Click to expand...
Click to collapse
Follow this guide. It works for the modded YouTube as well.
i didn't have a youtube preinstalled so i created the folder "Youtube" in system\app gave it proper permissions placed apk in the proper folder with the proper permissions, rebooted, tried to open it, got oneplus logo, back to launcher. No youtube opens, no force close.
oos 4.1.0
Hey fellow P10 owners, xposed framework is already out for Nougat and if anyone is interested here is the link for the download https://forum.xda-developers.com/showthread.php?t=3034811 . I have tried it out and it hasn't given me any issues so far, I had Amplify before in another phone since it needs this framework to work i decided to give it a try. Also Gravity box for Nougat is also in Alfa and some things are working ok on the P10 like center clock, modify the navigation keys also the Swype gesture on the finger reader can be reworked at some extent. It hasn't caused any bootloops so far, some issues with gravity box is when changing themes it makes it crash for which you have to uninstall and install the app again, either way it still and Alfa so be aware of some bugs. Here is the link for gravity box https://forum.xda-developers.com/xposed/modules/app-gravitybox-v7-0-0-tweak-box-android-t3653953 big shouts and thanks for the developers of xposed framework and also gravity box all credits to them!
{
"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"
}
Sent from my VTR-L09 using XDA-Developers Legacy app
By the way your phone does need to be rooted! I would recommend using https://forum.xda-developers.com/p10/development/rom-fromfuture-stock-rom-b164-t3657812
Big thanks to @Blackball for this Rom. This Rom is already root which makes it perfect and also it has the latest update for the P10!
Sent from my VTR-L09 using XDA-Developers Legacy app
great news to hear xposed finally worked on p10
Is it possible to assign the double tap for recents on the home(fingerprint) key? It's the only thing i'm missing from Huawei configuration of that button
demolatorul said:
Is it possible to assign the double tap for recents on the home(fingerprint) key? It's the only thing i'm missing from Huawei configuration of that button
Click to expand...
Click to collapse
You can get it but it would be the swipe kind of gesture. The same movement you would on the fingerprint key for recents but twice, you can get the last used app future like that .
Sent from my VTR-L09 using XDA-Developers Legacy app
You guys can always check out this thread also they keep updating gravity box for N https://forum.xda-developers.com/showthread.php?t=3653953
Sent from my VTR-L09 using XDA-Developers Legacy app
So i have fromfuture rom but i can't get xposed to work, which version of xposed do you guys have and how to make it work? Thanks!
demolatorul said:
So i have fromfuture rom but i can't get xposed to work, which version of xposed do you guys have and how to make it work? Thanks!
Click to expand...
Click to collapse
I'm running 88.1, now it's a bit buggy at times, just flash the zip in TWRP and reboot from the link that's provided in the op. I'm either case of it doesn't work just used the unistaller remember to have root privilege.
Now greenify is not really working for some reason it doesn't show as turn on in the app but it does in Xposed.
demolatorul said:
So i have fromfuture rom but i can't get xposed to work, which version of xposed do you guys have and how to make it work? Thanks!
Click to expand...
Click to collapse
Sent from my VTR-L09 using XDA-Developers Legacy app
You can do it via magisk, just get the latest beta 14.3 and then look for Xposed systemless from topjohnwu
Sent from my VTR-L09 using XDA-Developers Legacy app
Sent from my VTR-L09 using XDA-Developers Legacy app
Cannot get Xposed to work (not active)
Hi,
I'm on fRomFuture B171 with Magisk 14.3 beta and the Xposed SDK 24 module, but I can't seem to get it to work.
I rebooted after installation through Magisk but Xposed Installer (3.1.2 by dvdandroid) tells me Xposed is installed but not active.
Soft rebooted through Xposed, same issue.
I also tried uninstalling from Magisk and flashing 88.1 through TWRP, but to no avail. I flashed the uninstaller first.
I looked through /data/data/de.robv.android.xposed.installer but couldn't make out any solutions (Xposed doesn't log either).
Aforementioned folder has permissions fixed (0777), root is available and working.
Do I miss something?
Uninstall the app and module reboot to recovery clean dalvik and cache, now reboot, install module, and reboot install app from topjohnwu and now you should see the module active don't reboot from the apps when ever you activate a module just press the power button and do from there.
Sent from my VTR-L09 using XDA-Developers Legacy app
lil_kujo said:
Uninstall the app and module reboot to recovery clean dalvik and cache, now reboot, install module, and reboot install app from topjohnwu and now you should see the module active don't reboot from the apps when ever you activate a module just press the power button and do from there.
Click to expand...
Click to collapse
Just got home and tried this, it's working now! Awesome.
Thanks so much.
EDIT: Okay, so I enabled some modules (Boot Manager, InstallerOpt, Xposed Torch) and restarted.
I tested, it worked, then I restarted again (from the power menu) resulting in the same issue.
(Framework v 88.1 (Systemless by topjohnwu) is installed, but not active).
Xposed still doesn't log :/
Triple EDIT ftl:
Restarted again, it works again... But I can't yet make out a pattern
Ok so the thing is that the bug that it's having is related to the restart, if you have a module active and you reboot the phone it will break the module so you have to unchecked and check the modules again and reboot, I have done many testings and for me it seems the issue is that the xposed framework breaks after a reboot.
Sent from my VTR-L09 using XDA-Developers Legacy app
@lil_kujo
Seems the most likely. Pretty inconvenient, but it will have to do for now.
Also, is there any chance that the 88.2 update that is present within Xposed Installer solves this issue?
I'm afraid to update right now since it's barely working.
oscillum said:
Just got home and tried this, it's working now! Awesome.
Thanks so much.
EDIT: Okay, so I enabled some modules (Boot Manager, InstallerOpt, Xposed Torch) and restarted.
I tested, it worked, then I restarted again (from the power menu) resulting in the same issue.
(Framework v 88.1 (Systemless by topjohnwu) is installed, but not active).
Xposed still doesn't log :/
Triple EDIT ftl:
Restarted again, it works again... But I can't yet make out a pattern
Click to expand...
Click to collapse
no xposed error in the log.
huawei has turned off logging by default.
* # * # 2846579 # * # * enter in the dialer and 1 after 3 menu items.
glehel said:
no xposed error in the log.
huawei has turned off logging by default.
* # * # 2846579 # * # * enter in the dialer and 1 after 3 menu items.
Click to expand...
Click to collapse
Didn't work for me. Would reset to unticked on reboot /power-off & on and Xposed still wouldn't show logs.
oscillum said:
Didn't work for me. Would reset to unticked on reboot /power-off & on and Xposed still wouldn't show logs.
Click to expand...
Click to collapse
it keeps me as I set it up.
glehel said:
it keeps me as I set it up.
Click to expand...
Click to collapse
Just tried again but it's the same, selections unticked and no logs.
It's not too bad, I only wanted Xposed logs for troubleshooting, but since powering off & on instead of restarting, Xposed works just fine.
Thanks for the help though
[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?
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