Good for you, i already hidden Magisk Manager appfound a solution for the revolut problem in reddit. go to magisk app, and hide it (it is an option in settings). then reenable magisk hide for revolut. you are done!!!
I am going to *GUESS* that the playstore will update regardless of the auto updates setting, its too important/dangerous for google to allow you to not update it. I have never seen the playstore in the list of available updates, I think it updates at the very start of the playstore if there is one available; i.e. no chance to show in a list.Do you have "auto-update" turned off in Google Play settings?
I don't remember if Play Services shows up in list of apps with updates. If it does, I probably take it because at some point update refuses to work with outdated Services.
In Android Settings -> Apps, Play Services has a button to uninstall updates. Maybe you can use that.
can you please be more specific?found a solution for the revolut problem in reddit. go to magisk app, and hide it (it is an option in settings). then reenable magisk hide for revolut. you are done!!!
...Is there any way to stop google play services from updating itself ? I want to keep old version of gms.
Do you have "auto-update" turned off in Google Play settings?
I don't remember if Play Services shows up in list of apps with updates...
I am going to *GUESS* that the playstore will update regardless of the auto updates setting, its too important/dangerous for google to allow you to not update it. I have never seen the playstore in the list of available updates, I think it updates at the very start of the playstore if there is one available; i.e. no chance to show in a list...
I had everything working using the earlier Carary Build. I updated to the latest Canary Build yesterday (direct install), and now many of my apps are force-closing, most banking apps are detecting root, and MagiskHide list is getting automatically unchecked. Everything's messed up now. Looks like this issue is with the Magisk update, and not with the updated banking apps. And lesson learned: don't try to fix what is not broken!magisk 21.2
magisk manager 8.0.5(4802)
running
magiskHide props config 5.4.0-v113
universal safetynet fix 1.0.2 by kdragon
hardware off 1.1 by displax
if i am not mistaken iam up to date. this just happened... probably i am the first to report?
Its CANARY! by definition its about fixing things so that tfuture functionality can be implemented. Possibly beta or stable would be a better choice. I personally am only on beta as I am on A11, otherwise I'd onl.y install stable.I had everything working using the earlier Carary Build. I updated to the latest Canary Build yesterday (direct install), and now many of my apps are force-closing, most banking apps are detecting root, and MagiskHide list is getting automatically unchecked. Everything's messed up now. Looks like this issue is with the Magisk update, and not with the updated banking apps. And lesson learned: don't try to fix what is not broken!
Stable is now also on 21200 (same as Beta) and therefore as well good for A11Its CANARY! by definition its about fixing things so that tfuture functionality can be implemented. Possibly beta or stable would be a better choice. I personally am only on beta as I am on A11, otherwise I'd onl.y install stable.
I'm aware of that, but in the past, I've had apps detecting root on stable versions of Magisk. So I switched to Canary, which solved the problems.Its CANARY! by definition its about fixing things so that tfuture functionality can be implemented. Possibly beta or stable would be a better choice. I personally am only on beta as I am on A11, otherwise I'd onl.y install stable.
NB. As Danny indicates here, MHPC remains a vital cog in Magisk's MH gearbox. PWLatest release
v1.1.1
@kdrag0n released this 4 hours ago
Changes
- Removed security patch fixup to fix CTS profile mismatches on some devices
Some devices will now need to use MagiskHide Props Config in addition to this module in order to pass CTS profile checks as part of basic attestation. Altering the CTS profile is no longer in scope for this module as it breaks more devices than it fixes
You serched for a day and didn't find this thread? https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/page-7#post-84299679i cannot hide magisk manager in miui 8.1.4.0 android 6.0 marshmallow,
the device Mi5
os miui 8.1.4.0 android 6.0
latest magisk 21.2
what i have try:
-clean install, no internet connnection turn off play protect and setenforce 0
-clean install, turn on internet connection, let gapps update to latest, turn off play protect and setenforce 0
-clean install, turn on internet connection, don't let gapps update to latest, turn off play protect and setenforce 0
can it be fixed? or some workaround?
after searching for a whole day most of i found fixed with setenforce 0 and turn off play protect.
Universal SafetyNet Fix v1.1.1 is now available.
Changes
- Removed security patch fixup to fix CTS profile mismatches on some devices
Download
Some devices will now need to use MagiskHide Props Config in addition to this module in order to pass CTS profile checks as part of basic attestation. Altering the CTS profile is no longer in scope for this module as it breaks more devices than it fixes.
If this module helped you, please consider a recurring donation for sustainable support, or alternatively buy me a coffee. Everything helps, but a recurring donation is the best way to keep the project alive in the long term.
Issues on heavy OEM skins
This is a reminder that heavy OEM skins are not officially supported. They may happen to work depending on your luck and the particular ROM in question, but nothing is guaranteed. Please do not report problems on such ROMs. It's surprising that it works at all on them; I wouldn't expect everything to be fully working. I will not provide more support for issues related to heavy OEM skins.
The compatibility issue does not lie in the SafetyNet fix itself, but rather how the Magisk module is built. It's possible to make the Magisk module version of the fix slightly more portable, but I have no interest in supporting heavy OEM skins, nor do I have any devices running such ROMs.
You will always have the best luck with a ROM not too far from AOSP, e.g. most custom ROMs and Pixel stock ROMs.
With today's 21203 Viper4Android also does not work: Status AbnormalUpdated from Canary 21202 to 21203, but no good - Viper4Android shows Status Abnormal
That's why I never update directly nor flash through TWRP but patch an image and keep for a while - flashed my yesterday's 21202 patched and Status is back to Normal
Xiaomi.eu A11 beta
I already faced this issue since 21.2.With today's 21203 Viper4Android also does not work: Status Abnormal
I can simply reflash between my various saved patched boot images back and forth, last version of Magisk where V4A works is 21202
Anybody else here using V4A, and how is V4A for you?
Still working for me on Magisk Beta 21.3. Previously I had installed through the Magisk Repo and when Beta 21.2 came out it broke it. I uninstalled that V4A version and reinstalled by just installing the apk (2.7.2.1) and it worked and is still working with 21.3. I also had JamesDSP, AML, and ACP installed prior to reinstalling the 2.7.2.1 apk.With today's 21203 Viper4Android also does not work: Status Abnormal
I can simply reflash between my various saved patched boot images back and forth, last version of Magisk where V4A works is 21202
Anybody else here using V4A, and how is V4A for you?
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.I'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or DebugIs the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls!Direct Install with recovery mode checked worked for me. You were right.
After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about itI'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Run magisk -c from adb shell and see what version it reports.I actually updated the app from the app itself before doing my OTA upgrade so it get the version 27 of magisk, I tried installing that one again I had in my downloaded folder. But I also downloaded again the app from github.
I do have root, I've modified the boot file with magisk, so I'm not sure what to do now. I'll try installing an older version. But as you see of the screenshot from app manager, I don't know how the app is installed and removed almost immediately. At first I thought it was caused by an android 14 new security change.