Question Instapay banking app detects root help please - Google Pixel 6

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

Related

[MOD][AROMA][NO-ROOT]Angel's abyss ad-block + ad-free YouTube *banking supported*

{
"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"
}
^ Sorry for the OCD unfriendly logo- will fix ^​
WILL NOT WORK CURRENTLY- I CANNOT FIX UNTIL O2 SEND ME A NEW DEVICE.
/* Reasons */
I got fed up of loosing my Barclays and Halifax banking apps when I root (mainly just for Adblock).
I decided to make this for my one plus 3T, Unlocked bootloader and twrp recovery required but no root needed.
/* Info */
Overwrites current hosts file, doesn't merge.
If running OOS 4+ please ensure you are running latest twrp with system decryption enabled.
May work on other devices please report findings.
Version with hosts only replaces your hosts file with latest adblock sites pulled with my script.
Version with YouTube Includes nodpi by arter97. (Deletes old YouTubes and replaces with ad-free version).
Not tested on all banking apps.
Known to work:
Barclays
Halifax
Metro
Natwest
Not needed on:
Santander
Nationwide
/* WARNINGS */
Requires unlocked bootloader and latest twrp recovery.
WARNING UNLOCKING BOOTLOADER AND FLASHING RECOVERY WILL TRIGGER SafetyNeT
Please flash at own risk.
Please only use if your bootloader is already unlocked and your recovery already flashed.
Please verify you can already access the required apps without error before flashing this zip.
Aroma-BETA is a testing version. Please inform me of bugs.
/* Log */
Hosts files updated regularly.
Hosts obtained from:
Code:
[url]http://hosts-file.net/ad_servers.txt[/url]
[url]http://www.malwaredomainlist.com/hostslist/hosts.txt[/url]
[url]http://winhelp2002.mvps.org/hosts.txt[/url]
[url]https://adaway.org/hosts.txt[/url]
[url]http://someonewhocares.org/hosts/hosts[/url]
[url]http://pgl.yoyo.org/adservers/serverlist.php[/url]
My Own local blocklist
Parsed and merged using my own script.
MOAAB was excluded due to browsing issues when merged. Think its linked to host files size.
***A experimental whitelist/blacklist feature added.***
MAY CONTAIN GORNS.
I have attached a copy of host files for anyone who wants to ensure no naughtiness
/* Install instructions */
Download version required and copy to root of sdcard/internal storage.
Boot into twrp and install zip
wipe dalvik/cache.
Reboot and enjoy.
Aroma-BETA:
Download and copy to root of sdcard/internal storage.
Boot into twrp and install zip
Await instructions.
Reboot and enjoy.
---------
can sideload if preferred.
To use Whitelist/Blacklist please note:
Run blacklist/whitelist option
The installer will create 2 files on the root of your sd card "blacklist.txt and whitelist.txt"
You will then have to edit these by adding the domains of the sites you want to block or whitelist.
e.g
Code:
google.com
linda.com
startrek.com
stargate.com
Note you don't enter return ip or HTTP/HTTPS/WWW....
Once complete reboot into twrp and run the AngelsAbyss Aroma installer again
re-run the whitelist and blacklist option
The script will take care of the rest.
This will have to be done each time the whitelist and blacklist is updated (for now)
/* Downloads */
DONT DOWNLOAD UPDATE BROKEN
Aroma BETA
Nightly hosts Aroma BETA
/* Advisory */
Please inform me if format of this thread needs editing.
/* Thanks to */
arter97
Wanam
Logo by blueSpaceling
Anyone else I missed.
Weekly Changelog and news:
20/01/2017
Latest hosts
Working and tweaked whitelist and blacklist
New installer
Script cleaned up.
File size reduced
Google DNS option added for faster dns resolve.
Web server option added but not yet loading - currently testing why.
19/01/2017
YouTube permission fix pushed to Nightly.
Script cleaned up.
Foundations for cleaner method.
Test version with dns changes added.
New features added on weekends weekly.
14/01/2017
Errors reported with ad-free youtube, applied possible fix.
ad-free YouTube updated to 12.01.54.
Added a Nightly host option for those who like to keep updated.
Created script to automate host update and parsing.
Nightly's are fully automated so no new features until weekly pushed, just latest hosts!
Further reduced zip size.
Started build environment for New app for handling whitelist and blacklist without need to flash after each amendment.
12/01/2017 Version 0.2a Beta 2b
Added experimental Whitelist and Blacklist feature.
Added foundation for optional web host to allow pages and apps that fail if ad server doesn't respond.
Improved zip compression.
11/01/2017 Version 0.2 Beta 2
Aroma installer beta.
Latest hosts file generated by my own script.
latest ad-free youtube_11.49.55-114955640 nodpi.
foundation for whitelist/blacklist - non working.
9/01/2017 Version 0.1 Beta 1
Initial adaway hosts.
ad-free youtube 11.47
flashable zip installer.
but on a Samsung galaxy S7 if the bootloader is unlocked or twrp is flashed, afaik it will trigger knox security 0x1 ?
vtec303 said:
but on a Samsung galaxy S7 if the bootloader is unlocked or twrp is flashed, afaik it will trigger knox security 0x1 ?
Click to expand...
Click to collapse
Correct, but Knox doesn't affect the mentioned banking apps, android pay is a different matter ofc. But my wife's end no issues. Stock with unlocked and twrp. No root. Halifax opens and initiates fine.
Saying this I can't speak for all users. I'll update thread to reflect this.
Magisk hide is doing the job for me......i use dbs bank app and snapchat with systemless root
Sent from my Pixel XL using Tapatalk
mysterio619 said:
Magisk hide is doing the job for me......i use dbs bank app and snapchat with systemless root
Click to expand...
Click to collapse
Ahh, this was the case for me until barclays discovered how to detect. It just closed itself instead. Snapchat was always easy with root, xposed was what it didn't like. Unless they've changed there too.
Thank you for input
Santander works fine with root, afaik. I logged in before rooting just to be safe, but the app still runs fine with root.
Sent from my OnePlus 3T using XDA Labs
FishyFing said:
Santander works fine with root, afaik. I logged in before rooting just to be safe, but the app still runs fine with root.
Click to expand...
Click to collapse
Good to know, I believe Santander and Nationwide. Both allow root.
Installed this for ad free youtube but it seems that it does not work.
tdamocles said:
Installed this for ad free youtube but it seems that it does not work.
Click to expand...
Click to collapse
Interesting, In works my end, can you please inform me of what part isn't working?
Also did you pick hosts and youtube or whitelist+blacklist and youtube?
Please ensure auto updates are off in play store incase its replacing ad-free version?
Update, I may have noticed a permission error on the latest update. I have applied a fix, please check again? Not the nightly version.
I flashed the latest beta (non nightly) and my YouTube works (with no ads).
Thanks!
What happens if i flash it and must phone isn't decrypted?
x.raze said:
What happens if i flash it and must phone isn't decrypted?
Click to expand...
Click to collapse
Untested, I believe it wont work.
Full decrypt isn't needed, just in twrp (type password) when prompted when entering recovery. But if twrp decryption fails it wont flash.
Feel free to try, nandroid backup first.
As far as I know though system wont mount without decryption.
AdAway isnt working for me on freedom os 4.0.1
I
Dhairya said:
AdAway isnt working for me on freedom os 4.0.1
Click to expand...
Click to collapse
Ive just tested this on freedom os v 1.0 - , its working my end. When installing freedom make sure adaway isn't installed from their installer as it clashes with my hosts files.
This wont put an icon on your app draw or allow the adaway app. This is a replacement for adaway.
I used these settings on test...
what is the difference from adaway?

[MAGISK MODULE] [APP] Google Pay downgrader for Wear OS on Pie & RootPayEnabler app

[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?

[APP][XPOSED][11/07] Discover Killer - Replace the Google Discover page on your home screen

{
"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"
}
Discover Killer is an Xposed module that allows you to replace the Google Discover page of your home screen with whatever you want. Tired of garbage clickbait articles and ads? This module can replace the page with your favourite app, RSS feed or other supported 'Overlays'
Examples:
(Replacing the page with Entertainment Space, an RSS feed and launching the BBC News app)
Configuration:
Discover Killer has a number of options to configure the 'overlay' (the panel to the left of your home screen), including:
Replace it with another overlay
Supported overlays include Entertainment Space; which shows TV shows, music and games, a custom RSS feed, and HomeFeeder. See the Wiki page for more info
OR
Launching an app when fully open (any app is supported)
Whether to launch the app fresh from each swipe, or to resume the app
Pick from a list of backgrounds (based on the app's splash screen and icon) to show on the overlay when opened
Pick a colour from your wallpaper to use for Material You
Compatibility:​The module should work on any launcher that has the Discover page. It hooks the Google app rather than the launcher, which allows this. I've tested it on Lawnchair, Nova Launcher and Action Launcher successfully.
This module has been tested and is working with LSposed, but should also work with EdXposed. Make sure you enable hooking for the Google App when enabling the module (it should be pre-selected)
Download:
Version 3.0
Changelog:
Version 3.0:
Another rewrite? Yeah.
Discover Killer 3.0 removes Snapshot, but replaces it with the ability to use custom overlays. These include a simple RSS feed, Google's Entertainment Space (which shows movies, TV shows, games, music and books), or HomeFeeder. See the Wiki page for more info.
There's also a rewritten settings UI which is simpler, and has much less wait time as the preview has gone. Instead, the overlay changes immediately, so simply swipe to go home to view the updated overlay.
Please note: If you're updating from an old version, please uninstall it before installing this new build. You will need to re-hook the Google App (and Entertainment Space if you have it installed), and then reboot for it to take effect.
Version 2.2:
Tweaked Material You theming on Snapshot, with colors now applied to the FAB, bottom pill and some icons. Cards are handled from the server so can't be tinted easily.
Allowed Snapshot to draw behind the status bar and added padding to handle that
Added the ability to bypass the Xposed checks, please only use this if your Xposed install is working but the checks are failing.
Improved the hiding of status bar backgrounds to prevent a grey line appearing on Snapshot
Click to expand...
Click to collapse
Source Code:
is on GitHub
This is pretty cool. I have all the exposed modules installed, but it still gives me a EdXposed error. Which version of EdXposed is it supposed to work with? I'm on a pixel 3xl.
Edit: finally got rid of the errors but the app does not work. I can select an app, but Nova does not show it instead of discover. Let me know what's needed to troubleshoot and help others.
Having the same issue as above, everything seems to be in order but Discover persists. Tried using loads of different apps and no luck.
Can someone with the above issue please post their xposed log
Here it works but I have to swipe it slightly to the right, otherwise I have a white/dark screen with nothing.
Quinny899 said:
Can someone with the above issue please post their xposed log
Click to expand...
Click to collapse
https://drive.google.com/file/d/15hkgrOv2yTY51T7cPLEmWQJD8RfKrXy4/view?usp=drivesdk
Entertainment Space APK and Magisk module attached, as well as builds of HomeFeeder until the developer is in a position to re-create the Telegram channel.
Quinny899 said:
Can someone with the above issue please post their xposed log
Click to expand...
Click to collapse
Unable to post links because of new account, sent log to email listed in your profile, hope you have access. PM me if you need another way
Issue fixed with help. Google App was out of date, updated to newest version and worked immedietely. Thanks for the help dude.
Module is great, just what I was looking for. Tested with several apps and all seemed to work fine.
If you're facing the same issue, I updated Google App to - Google App 11.17.10 beta
Quinny899 said:
You appear to be using the whitelist, please whitelist your launcher & the google app.
Click to expand...
Click to collapse
That worked!
Install DiscoverKiller
In Magisk install RIru - Edexposed and Riru (Riru -Core)
In Edexposed, whitelist DiscoverKiller, Google, and your launcher
Reboot (thoughts and prayers)
Please submit for taichi if you can
Edit: after trying to use edxposed, it doesn't work. I have only play services, play services for ar, play store, service framework in the blacklist
Hi, the apps didn't work... Not sure what's the problem..
I'm using Nova Launcher with Nova Companion
Device: OnePlus 5T
Rom: LineageOS 18.1
Xposed: LSposed 1.3.5
Spoiler: Log for LSposed
Build version: v1.3.5 (5551)
Current date: 2021-04-13 01:05:45
Device: OnePlus ONEPLUS A5010
SDK: 30
Stack trace:
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CREATE_DOCUMENT typ=*/* (has extras) }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2067)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1727)
at android.app.Activity.startActivityForResult(Activity.java:5320)
at androidx.activity.ComponentActivity.startActivityForResult(Unknown Source:0)
at androidx.activity.ComponentActivity$b.b10)
at androidx.activity.result.ActivityResultRegistry$a.a(Unknown Source:15)
at org.lsposed.manager.ui.activity.LogsActivity.onOptionsItemSelected2)
at android.app.Activity.onMenuItemSelected(Activity.java:4269)
at ca.onMenuItemSelected(Unknown Source:0)
at l0.onMenuItemSelected(Unknown Source:0)
at mr.onMenuItemSelected(Unknown Source:2)
at mr.onMenuItemSelected(Unknown Source:2)
at androidx.appcompat.widget.ActionMenuView$d.b2)
at androidx.appcompat.view.menu.e.e(Unknown Source:4)
at androidx.appcompat.view.menu.e.r1)
at androidx.appcompat.widget.ActionMenuView.b1)
at androidx.appcompat.view.menu.ActionMenuItemView.onClick(Unknown Source:6)
at android.view.View.performClick(View.java:7448)
at android.view.View.performClickInternal(View.java:7425)
at android.view.View.access$3600(View.java:810)
at android.view.View$PerformClick.run(View.java:28305)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7660)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
I tried using this on my Samsung device but it doesn't work. App keeps telling me "module is not enabled or hooks are not working". I can confirm module is enabled and even magisk and edxposed are installed fine.
Any suggestions?
karan5chaos said:
I tried using this on my Samsung device but it doesn't work. App keeps telling me "module is not enabled or hooks are not working". I can confirm module is enabled and even magisk and edxposed are installed fine.
Any suggestions?
Click to expand...
Click to collapse
You probably need to enable the module on itself via EdXposed (basically whitelist or un-blacklist Discoverkiller). But the hooks need updating so I don't think it'll work at the moment.
I need to find a way to find the class without hardcoding obfuscated names again really.
Hui531 said:
Hi, the apps didn't work... Not sure what's the problem..
I'm using Nova Launcher with Nova Companion
Device: OnePlus 5T
Rom: LineageOS 18.1
Xposed: LSposed 1.3.5
Spoiler: Log for LSposed
Build version: v1.3.5 (5551)
Current date: 2021-04-13 01:05:45
Device: OnePlus ONEPLUS A5010
SDK: 30
Stack trace:
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CREATE_DOCUMENT typ=*/* (has extras) }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2067)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1727)
at android.app.Activity.startActivityForResult(Activity.java:5320)
at androidx.activity.ComponentActivity.startActivityForResult(Unknown Source:0)
at androidx.activity.ComponentActivity$b.b10)
at androidx.activity.result.ActivityResultRegistry$a.a(Unknown Source:15)
at org.lsposed.manager.ui.activity.LogsActivity.onOptionsItemSelected2)
at android.app.Activity.onMenuItemSelected(Activity.java:4269)
at ca.onMenuItemSelected(Unknown Source:0)
at l0.onMenuItemSelected(Unknown Source:0)
at mr.onMenuItemSelected(Unknown Source:2)
at mr.onMenuItemSelected(Unknown Source:2)
at androidx.appcompat.widget.ActionMenuView$d.b2)
at androidx.appcompat.view.menu.e.e(Unknown Source:4)
at androidx.appcompat.view.menu.e.r1)
at androidx.appcompat.widget.ActionMenuView.b1)
at androidx.appcompat.view.menu.ActionMenuItemView.onClick(Unknown Source:6)
at android.view.View.performClick(View.java:7448)
at android.view.View.performClickInternal(View.java:7425)
at android.view.View.access$3600(View.java:810)
at android.view.View$PerformClick.run(View.java:28305)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7660)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Click to expand...
Click to collapse
+1
karan5chaos said:
I tried using this on my Samsung device but it doesn't work. App keeps telling me "module is not enabled or hooks are not working". I can confirm module is enabled and even magisk and edxposed are installed fine.
Any suggestions?
Click to expand...
Click to collapse
Karan?! read in prvt messgasess please
Just released version 2.0, a total rewrite from scratch.
No obfuscation class/field names (should be immune to Google app updates)
True embedded Google Assistant Snapshot page
More options for launching other apps
A brand new UI, Material You style
Some screenshots:
The download is in the first post, or on GitHub.
Always saying xposed module not enabled, though lsposed is active and working perfectly for other modules. I'm on android 12 beta 4 gsi
PritamGhosh8009 said:
Always saying xposed module not enabled, though lsposed is active and working perfectly for other modules. I'm on android 12 beta 4 gsi
Click to expand...
Click to collapse
The check for that is a self hook, it literally cannot fail is LSposed hooks are working. Try rebooting, and if that fails reinstall the module.
Quinny899 said:
The check for that is a self hook, it literally cannot fail is LSposed hooks are working. Try rebooting, and if that fails reinstall the module.
Click to expand...
Click to collapse
I did both... Reboot and reinstall... Still same problem
For your kind notice, here is my lsposed module log

SafetyNet Suddenly Fails

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?

PUBG NEW STATE instant crash on rooted devices with Magisk.

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

Categories

Resources