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!!!
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://forum.xda-developers.com/t/...etynet-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?
...Resolved by changing selinux status to permissive...
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?
All later Magisk builds are a Stand Alone (no need for internet connection / json files to downgrade), single package solution, both debug (Canary) builds (from 22402):I have upgraded from 22002 to 22100. Everything is fine. But in 22.1 I have no possibility to choice canary version. The user based url https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json doesn't work. Is there a special mm apk for 22.1?
Yes, I'm aware you have Magisk in boot ramdisk. I think you did from the beginning of this discussion. But since you said you did direct update with Recovery mode checked, I was curious whether that succeeded
fixed for me on my phone (rig see below) with Magisk v22.1 - thank you @topjohnwu !!!The latest magisk 21.2 when I install it xposed moudel is not working (activated in edexposed managet ) riru edxposed yahfa 0.4.6.4 4563 instaled . riru 21.3 as riru 23.1 causes that exposed moudel not working… . so I am back to magisk 20.4 working perfect any fix to instal the latest magisk my device redmi k20 pro premium edition miui 12.0.6 eu
Good result (so far)!1) Obviously.
2) As specified / already mentioned I would have mentioned it if I had known it before. I thought it was a general problem.
3) Sure, that would be plan B.
Looks like you have /dev/bootimg as your real partition location and it is still higher in the list in util_functions.sh like how I fixed it in the linked commit, so this is definitely a regression from some other recent change to Magisk.. sigh, I'll look into it.@osm0sis
Thank you for having an eye on that.
Did the "ls" twice, first from a TWRP-terminal in recovery, second from a terminal while phone is "up and running".
No, the phone is an Estar Takee1.
ROM is from here: Mikel Android 7 for Takee1
and is itself a port from this ROM: RidonOS for Micromaxx A311
You're right, sorry for that. Now here the installation log for canary-version:
- Target image: /dev/BOOT
- Device platform: armeabi-v7a
- Installing: f152b4c2 (22005)
nanddump: MEMGETINFO: Not a typewriter
Parsing boot image: [boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
That was quick... Didn't even have to whisper your name three times in the mirror.
Boot image is here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84688655
And this is supposedly the install log:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84686805
And for good measure there's a Magisk log as well:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84695083
And some device info:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84689305