Hi guys, because Magisk Hide doesn't work for my mobile banking app, I have to remove it for now. Can someone tell me how I do it without losing my data? I am on 9.5.11 on the EU version and don't have twrp. Would it be enough to just install the next update from the zip without installing Magisk before the reboot, or would my system break this way?
Just a thought...
Did you only use Magisk hide or did you also go to settings to Hide Magisk Manager? If you didn't use the latter option as well, then that could be why you're bank app still detects root
runningslow said:
Just a thought...
Did you only use Magisk hide or did you also go to settings to Hide Magisk Manager? If you didn't use the latter option as well, then that could be why you're bank app still detects root
Click to expand...
Click to collapse
Thank you for your suggestions, but I did hide the manger as well. I researched about the app and no one has a solution with current 19.3 version of Magisk. It works with the Canary build, so it should work again on 19.4 I think, but I have to pay my rent in October again.
Just Uninstall in Magisk Manager. But you should use 19.4.
Kleva94 said:
Thank you for your suggestions, but I did hide the manger as well. I researched about the app and no one has a solution with current 19.3 version of Magisk. It works with the Canary build, so it should work again on 19.4 I think, but I have to pay my rent in October again.
Click to expand...
Click to collapse
Then... Why not use the Canary build for now?
runningslow said:
Then... Why not use the Canary build for now?
Click to expand...
Click to collapse
I've read it's quite unstable and I don't want to risk a data loss.
Good News, everybody. Upgrading to Android 10 somehow solved the problem.
Related
Does anyone know why the app is crashing? I do have magisk but safety net is passing.
Did you hide SU/Magisk for that app via Magisk Manager?
matase said:
Does anyone know why the app is crashing? I do have magisk but safety net is passing.
Click to expand...
Click to collapse
Try clearing data and cache from banking app, if safety net is passing.
akxak said:
Did you hide SU/Magisk for that app via Magisk Manager?
Click to expand...
Click to collapse
Magisk hide isn't working. At least not for me anyway!
hallo dare said:
Magisk hide isn't working. At least not for me anyway!
Click to expand...
Click to collapse
For me, it does... and solved problems especially with banking apps where developers don't understand that a rooted phone usually implies an experienced user taking care of his device and keeping it up to date... in opposite to "locked" devices with outdated firmware and open for any sort of side attacks.
akxak said:
For me, it does... and solved problems especially with banking apps where developers don't understand that a rooted phone usually implies an experienced user taking care of his device and keeping it up to date... in opposite to "locked" devices with outdated firmware and open for any sort of side attacks.
Click to expand...
Click to collapse
Keep getting error code 99z on my sky q app when i try to access viewing.
Magisk hide is on, but making no difference.
What version of magisk you running?
You on 5.1.8 update from today?
hallo dare said:
Keep getting error code 99z on my sky q app when i try to access viewing.
Magisk hide is on, but making no difference.
What version of magisk you running?
You on 5.1.8 update from today?
Click to expand...
Click to collapse
I am on 5.1.8, but it worked also on 5.1.7 before. Question is what Sky verifies... If Sky (like others) checks Widivine, then the unlocked bootloader downgrades from L1 to L3.
Check with the DRM Info app from the Play store.
My Chase app started that
akxak said:
I am on 5.1.8, but it worked also on 5.1.7 before. Question is what Sky verifies... If Sky (like others) checks Widivine, then the unlocked bootloader downgrades from L1 to L3.
Check with the DRM Info app from the Play store.
Click to expand...
Click to collapse
Yep L3.
akxak said:
Did you hide SU/Magisk for that app via Magisk Manager?
Click to expand...
Click to collapse
That worked. Thanks! I forgot I can hide apps
For what it's worth, hiding Magisk from my PNC app allows the app to run just fine UNTIL I attempt to deposit a check. At this point, it crashes every time. I'm currently on PNC app version 4.4.1. I didn't have this issue until about June of 2018. However, I'm not certain as to which version last worked as desired. My guess is that there's not easy solution for this.
My current work around is to to keep a copy of both the stock and patched boot.img file on my device. If ever I need to deposit a check, I can reboot to TWRP... flash the stock boot.img... reboot... deposit the check... reboot to TWRP... flash the patched boot.img... and reboot.
If someone knows of an easier approach, please share.
Nexus 6P
ABC Rom 8.1.0 (6/24/18)
Magisk v. 16.0
Anyone managed to run google and phone pay working on rooted PIE OS
nitinvaid said:
Anyone managed to run google and phone pay working on rooted PIE OS
Click to expand...
Click to collapse
yes bro.Both are running smoothly on my rooted Pie
Yes can confirm works perfectly....
kakkooran said:
yes bro.Both are running smoothly on my rooted Pie
Click to expand...
Click to collapse
what are the steps which file you flashed i am using magisk v17.1
Aduser345 said:
Yes can confirm works perfectly....
Click to expand...
Click to collapse
It's not working for me do I have to any anything specific settings
nitinvaid said:
It's not working for me do I have to any anything specific settings
Click to expand...
Click to collapse
First you have to be unrooted completely meaning...safetynet should pass....(i hope you know how to check)
Unrooting means you should be on oos 9 stock without custom recovery with bootloader unlocked
Then register or login in google pay using google id and phone number then root back again it should work just fine?? i hope it helps
Aduser345 said:
First you have to be unrooted completely meaning...safetynet should pass....(i hope you know how to check)
Unrooting means you should be on oos 9 stock without custom recovery with bootloader unlocked
Then register or login in google pay using google id and phone number then root back again it should work just fine i hope it helps
Click to expand...
Click to collapse
well like this phonepe was working working till yesterday i made some payments too but today its giving me error can not send payment from this device or something like that
Here
nitinvaid said:
Here
Click to expand...
Click to collapse
As a senior member you should know better, you have posted this question 3 times in different threads. What worked for me when this happened was to clear playstore data.
yldlj said:
As a senior member you should know better, you have posted this question 3 times in different threads. What worked for me when this happened was to clear playstore data.
Click to expand...
Click to collapse
Yea sorry for that I wanted to create thread but I posted there also....
And I have already tried all possible steps.. I have even uninstall and installed app.. still no luck
Google pay works on my 9.02 build but can't get it to work on any of the custom ROMs (AOSIP, Havoc, etc). On the interview xda had with one of the security software people from Google, the sw eng said that to pair down the number of possibles it first looks to see if it recognizes the name of build. Might explain why rooted stock works but not custom OS. Oh and it's not a safetynet issue, i can get safetynet to pass on custom roms....even to get google pay to accept and load credit cards....it just won't transact at the store.
Anyone found a solution to this?
I'm OOS OB7 with Magisk installed. SafetyNet passes and I use Magisk Hide to hide play store and google pay. However, When I try to register with Google Pay it says I have a custom ROM or rooted.
syedtahir16 said:
Anyone found a solution to this?
I'm OOS OB7 with Magisk installed. SafetyNet passes and I use Magisk Hide to hide play store and google pay. However, When I try to register with Google Pay it says I have a custom ROM or rooted.
Click to expand...
Click to collapse
Did you use the repackage magisk option? It's under settings in magisk
hallo dare said:
Did you use the repackage magisk option? It's under settings in magisk
Click to expand...
Click to collapse
Here is what I have tried so far:
Uninstalled Pay.
Made sure Magisk is running and SafetyNet is passing.
Repackage Magisk
Magisk Hide - Google Play Store.
Clear Playstore cache and data
Reboot
Install Google Pay
Magisk Hide Google pay
Launch Google Pay registration. App launches but on receiving OTP, it says that the devices does not meet google sec requirements etc and fails.
syedtahir16 said:
Here is what I have tried so far:
Uninstalled Pay.
Made sure Magisk is running and SafetyNet is passing.
Repackage Magisk
Magisk Hide - Google Play Store.
Clear Playstore cache and data
Reboot
Install Google Pay
Magisk Hide Google pay
Launch Google Pay registration. App launches but on receiving OTP, it says that the devices does not meet google sec requirements etc and fails.
Click to expand...
Click to collapse
Search for Tez hider in xda. it's a magisk module
kakkooran said:
Search for Tez hider in xda. it's a magisk module
Click to expand...
Click to collapse
It's not for magisk 18
you need disable telephone permission of Google Play service
You don't need to unroot and lock the bootloader and register gpay and root it back again and all those shiz. These steps will save you time:
• Disable "Telephone" permission for Google Play Services
• Clear data of GPay
• Hide GPay in Magisk Hide
• Register again on GPay
Use magisk and magisk hide plus
Remove phone from play service
It will work
But clear the data of Google app before doing above steps
Goto app settings > Google Pay > force close, clear data.
Goto settings > apps > google play services > turn off telephone (dialer)
Open google pay..
turn on the dialer icon later again after you've restored the account and stuff
I updated to the new OOS 11 via the Oxygen updater app and all is fine except safety net fails. I have an unlocked boot loader and coming from root, but I just wanted to try this out and don't care about having a rooted device at the moment, so I upgraded without doing anything else, but now safety net fails. And stuff like google pay doesn't work now.
Does anyone know how to fix safety net?
J3STUR said:
I updated to the new OOS 11 via the Oxygen updater app and all is fine except safety net fails. I have an unlocked boot loader and coming from root, but I just wanted to try this out and don't care about having a rooted device at the moment, so I upgraded without doing anything else, but now safety net fails. And stuff like google pay doesn't work now.
Does anyone know how to fix safety net?
Click to expand...
Click to collapse
yeah i can confirm having the same problem. I unrooted the phone and google pay only operates in rooted mode.
Unlocked bootloader always trips SafetyNet.
Go into Magisk settings and enable the "Magiskhide - Hide Magisk from various forms of detection" then reboot and try again.
Should show attached after that
djsubterrain said:
Go into Magisk settings and enable the "Magiskhide - Hide Magisk from various forms of detection" then reboot and try again.
Should show attached after that
Click to expand...
Click to collapse
I don't have that option in the settings. Do I have the wrong magisk version or something. I think it's the newest version.
J3STUR said:
I don't have that option in the settings. Do I have the wrong magisk version or something. I think it's the newest version.
Click to expand...
Click to collapse
I don't think you have root applied properly, this is what I see...
djsubterrain said:
I don't think you have root applied properly, this is what I see...
View attachment 5269509
Click to expand...
Click to collapse
on the main screen of magisk. tap the shield icon on bottom of screen. you should be able to find the magisk hide then.
MrSteelX said:
on the main screen of magisk. tap the shield icon on bottom of screen. you should be able to find the magisk hide then.
Click to expand...
Click to collapse
Um, why you telling me? Mine is working fine?
djsubterrain said:
I don't think you have root applied properly, this is what I see...
View attachment 5269509
Click to expand...
Click to collapse
No I don't have root. I just wanted to go back to stock, so I directly install the android 11 without doing anything. Do I need factory wipe to get it to back to normal?
J3STUR said:
No I don't have root. I just wanted to go back to stock, so I directly install the android 11 without doing anything. Do I need factory wipe to get it to back to normal?
Click to expand...
Click to collapse
Well, Magisk is for obtaining root, if you don't have root then why would you need to "hide" root that you haven't applied?
If you're asking about the bootloader then the only thing you could do is to lock it again, which will wipe your storage so make sure you back up
I'm on OB4 with lastest magisk canary without problems, try using it and enable magisk hide option and if problem persist enable magisk hide por Google play services and wipe playstore data.
Title. Im coming from the one plus 7, and am wondering if I'm still going to be able to pass safety net if I root my new phone.
It passes!
I had to use the magisk hide props config module, but I got my op9 the day it was released. Probably not needed with a newer version of magisk.
mx597turbo said:
I had to use the magisk hide props config module, but I got my op9 the day it was released. Probably not needed with a newer version of magisk.
Click to expand...
Click to collapse
I flashed boot img to obtain root. Even with Magiskhide I still failed Safety check. You are saying you passed ?
inspron said:
I flashed boot img to obtain root. Even with Magiskhide I still failed Safety check. You are saying you passed ?
Click to expand...
Click to collapse
I am rooted with Magisk and have MagiskHide enabled, and pass SafetyNet. I can use Google Pay with no issues.
Make sure you have Google Play Services ticked in MagiskHide settings (it should be ticked by default, but I don't know why else you would fail SafetyNet).
I too cannot seem to pass safetynet even after ensuring that G Play services is checked and installing props config. Any help would be appreciated.
xkelx said:
I too cannot seem to pass safetynet even after ensuring that G Play services is checked and installing props config. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure that you click on everything you can find related to Google and check them off. You'll need to tap on the individual app/service and checkmark everything that isn't already checked, as Magisk doesn't seem to want to check everything off even when you tap the checkmark. There's a dropdown for each app/service if you tap on the name of it.
I've been working on my son's OP9 (haven't gotten mine yet). I couldn't pass SafetyNet until I used the canary version of Magisk. Download the canary version of the manager TJW's Github page then install and update. Clear data on Google Play and you should be good.
I'm passing with that and EdXposed.
So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant
Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.
I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.
There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.
BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.
I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process
Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...
If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.
Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.
Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.
I dont have any issues with safetynet.