Magisk General Support / Discussion

[elhennig]

2021.5.12 Magisk v23.0
This release is focused on fixing regressions and bugs.

Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher.

When I try to install v23 apk i get only one method to chose the file to be patch and I have no idea how to proceed there. Having renamed apk to zip and ran the installation from the TWRP recovery the app claims the Magisk is not installed. What can I do?

 

[pndwal]

Installation Instruction update:

John Wu, 41m

I just spent some time rewording parts of the installation instructions. Hopefully this makes it less confusing to newcomers!
https://topjohnwu.github.io/Magisk/install.html

I really want to make things simpler, but as anything that involves Android, it is of course an absolute mess due to fragmentation, so unfortunately the instructions are super verbose

www.twitter.com/topjohnwu/status/1392409550024679426

(Commit, for comparison:
https://github.com/topjohnwu/Magisk/commit/4f73534837bda59fd58ca010fe25d3d66556883e )

Have a look. New look / quite a few clarifications. PW

 

[zgfg]

im on V23 and have still safetyNet error, what can i do?

How can somebody help if you don't specify what is precisely the error reported, what is your phone, firnware, etc

And/or, attach screenshots of your Magisk apk (main window) and SN test results

 

[pndwal]

When I try to install v23 apk i get only one method to chose the file to be patch and I have no idea how to proceed there. Having renamed apk to zip and ran the installation from the TWRP recovery the app claims the Magisk is not installed. What can I do?

Please say device (model), what Magisk version, if any, you had working before installing v.23.0, etc. PW

 

[pndwal]

Had some issues w the last update:

Oneplus 6T, Elemental Kernel, XXX_NO_LIMITS ROM

After I updated I passed safety net for the 1st time in ages, but my sim cards were not registering.

Uninstalled all my modules, rebooted, phone worked.

No longer passed safety net.

Added my modules back 1 by 1 and rebooted, phone still works.

After I added XXX back I got a weird reboot about a minute in. Couple of odd restarts from OS14 Launcher, but everything is working.

Still don't pass safety net though. Magisk hide is turned on. Magisk Hide props config is installed. Tried all the different configs for the 6t via Termux terminal, none got me to pass safety net.

Really odd that when my phone wasn't working I passed but now I don't....again.

Not a HUGE deal as I have no google account on my phone, but would be nice to have it working.

Thoughts?

For SafetyNet pass, you generally need Universal SafetyNet Fix even with basic attestation reported, due to Google changes.

Nothing else needed for most stock ROMs, but if Chinese uncertified stock, or custom ROMs w/o certified fingerprint spoofing, you'll need MagiskHide Props Config, and a certified fingerprint set up. If using certified stock ROM, best to remove MHPC.

Re. SIM issues:

Try disabling all modules except USNF (and MHPC if needed) and rebooting.

Nb. Mods like OOS Native Call Recording module have been reported to cause symptoms like yours in OnePlus devices, and may no longer be compatable with Android 11 for example.

Nb.2. Some OnePlus users have had issues with USNF module also, especially after Android 11 upgrade. However, surprising success is reported with a test module from the same Dev, eg:
https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-792931429

The test SafetyNet Fix module the user above reported fixed his OnePlus Nord w/ A11 ("works flawlessly"), is linked in the same pull request thread. It tests "Shim the keystore service instead of replacing it", and is designed to test the following scenarios and issues:
- 32-bit ARM devices
- Heavy OEM skins
- Samsung One UI
- MIUI
- Broken biometric authentication in apps
- Unstable system (i.e. rebooting and/or crashing)

Download link:
https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

This may well help you especially if running Android 11. PW

 

[wtosta]

My device is Samsung S9 with the latest Magisk 23.0 installed. I also applied the safetynet-fix-v1.1.1.zip and turned on the MagiskHide option in Magisk settings. SafetyNet passes with the basic integrity check and also I am able to register the payment cards in Google Pay. But when I try to turn on the NFC module to start using contactless payments the Google Pay app says that it can't set up the NFC. I had the same problem with the previous versions of Magisk Canary just before the official version 23.0 was released. Have any of you encountered such a problem before?

Best regards
Witek

 

[pndwal]

My device is Samsung S9 with the latest Magisk 23.0 installed. I also applied the safetynet-fix-v1.1.1.zip and turned on the MagiskHide option in Magisk settings. SafetyNet passes with the basic integrity check

Do you mean basicIntegrity is checked (ticked), or that SafetyNet Check uses Basic attestation evalType? (Two very different things). Also, can we assume ctsProfile pass as well?

and also I am able to register the payment cards in Google Pay. But when I try to turn on the NFC module to start using contactless payments the Google Pay app says that it can't set up the NFC.

Do you get an error message here? Eg un-secure / modified environment, or root / jailbreak detected?

I had the same problem with the previous versions of Magisk Canary just before the official version 23.0 was released. Have any of you encountered such a problem before?

Likely solution:
Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84790337 PW

 

[J.Michael]

@pndwal

• [App] Update snet extension. This fixes SafetyNet API errors.

Is "snet extension" the "SafetyNet Fix" module?

I thought the release note was saying that Magisk now did what was needed to pass SafetyNet. I assumed that meant that the separate module was no longer needed.

 

[Alexkidd85]

Hi guys

problem: pixel4xl updated to the latest patch and flashed last boot patched.

apps that require root work (probably only the old ones with permissions already granted), magisk passes the safatynet BUT...


on "installed" gives me n / a
obviously I can't hide anything

and, I did not know that now android, seeing the root, also canceled the unlock with my face (or at least I think that is why, it would make sense)

anyone have any ideas?

if I have to format everything, i'm not ready for android 12 yet !!

 

[wtosta]

Do you mean basicIntegrity is checked (ticked), or that SafetyNet Check uses Basic attestation evalType? (Two very different things). Also, can we assume ctsProfile pass as well?

After applying safetynet fix (before applying the fix evalType was Hardware and the SafetyNet check didn't pass).
Currently:
SafetyNet check: Succeeded
basicIntegrity: ticked
ctsProfile: ticked
evalType BASIC

Forgive me being imprecise.

Do you get an error message here? Eg un-secure / modified environment, or root / jailbreak detected?

No, it doesn't occur.

Likely solution:
Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84790337 PW

I am trying to test what is written in the solution, but with no avail :-(

 

[zgfg]

Hi guys

problem: pixel4xl updated to the latest patch and flashed last boot patched.

apps that require root work (probably only the old ones with permissions already granted), magisk passes the safatynet BUT...


on "installed" gives me n / a
obviously I can't hide anything

and, I did not know that now android, seeing the root, also canceled the unlock with my face (or at least I think that is why, it would make sense)

anyone have any ideas?

if I have to format everything, i'm not ready for android 12 yet !!

Hint (every second day somebody asks the same and it usually helps) - search through the Settings, Apps and uninstall your previous/old Magisk Manager, or old mngr/apk if you did hide it.
If needed, uninstall also the new Magisk app (not the Magisk itself) and install the apk again.
You can basically find the same in Magisk Wiki, available on Github, link from Magisk main window - IMO, users should take time and read to be familiar where to find the answers when something goes wrong)

 

[Didgeridoohan]

@pndwal

Is "snet extension" the "SafetyNet Fix" module?

I thought the release note was saying that Magisk now did what was needed to pass SafetyNet. I assumed that meant that the separate module was no longer needed.

No. That has nothing to do with the SafetyNet fix to circumvent hardware backed key attestation. That's just the update to the Magisk app SafetyNet check so that it uses a new API key (since the old one got revoked).

 

[zgfg]

@pndwal

Is "snet extension" the "SafetyNet Fix" module?

I thought the release note was saying that Magisk now did what was needed to pass SafetyNet. I assumed that meant that the separate module was no longer needed.

That is the same fix (new/valid SN API key) that has previously been applied to Magisk Canary apk - hence to avoid the API error.
Because of that API error the real SN test was not executed and Basic Integrity / CTS profile 'failures' had no meanings

Hence, there is no more need to switch to Canary or to use third party SN checkers - but it doesn't help to pass SN if there are real problems with Basic Integrity or CTS profile

 

[absinth4]

Sorry if I am postin on the wrong thread about this, wasnt sure where to do it . I have noticed that one of my banking apps (Bank of Scotland) is recognizing that my phone is rooted and wont let me log in. I have tried all the ways to bypass that, like magisk hide , hide props config, hiddin the magisk app itself, rebooting, reinstalling the banking app, but seriously nothing at all seems to work. with other banking apps that ppl had similar issues like Revolut, something from the above seemed to work but not for this. Am i missing any other workarounds for my issue guys? i would be really greatful !

 

[whitewallman]

This is probably a stupid question, but what does that last number in parentheses in the version number indicate? In my case, (21)

 

[Elcosomalo]

Interestingly, I saw this issue... It's still open! ... Might want to watch that space:
https://github.com/topjohnwu/Magisk/issues/4093 PW

Hey thanks! I've been looking if someone reported this issue and couldn't find it! will keep an eye on it

 

[wafna]

updated to the latest Android (11) on a Note 10+, using Odin, patched AP file etc. Usual standard method. Got Magisk to start only once. Can boot into recovery while plugging in a USB-C earphone cable.

Magisk itself (framework) only loaded once, all other times Magisk Manager says Magisk is not installed. No clue. Used to be that Magisk needed a Volume Down press together with Power On and then release.

Now if I try that, nothing happens (except the double warning that my phone has been modified). Can boot into recovery by using a Volume Up + Power Key + something plugged in.

Does anyone have any advice? will reflash and probably downgrade back to Android 10 but maybe someone has an idea. Thanks.

 

[Didgeridoohan]

This is probably a stupid question, but what does that last number in parentheses in the version number indicate? In my case, (21)

That's the app stub version. The stub is installed when you repackage the app with a random package name.

 

[whitewallman]

That's the app stub version. The stub is installed when you repackage the app with a random package name.

Thanks for the response, and pardon my ignorance... But I don't believe I repackaged the app. I installed the APK that I downloaded from the magisk GitHub link. Is it something I inadvertently did?

 

[pndwal]

Thanks for the response, and pardon my ignorance... But I don't believe I repackaged the app. I installed the APK that I downloaded from the magisk GitHub link. Is it something I inadvertently did?

Then you didn't Install stub... But that's the included version that will be used if you click 'Hide the Magisk app' in App settings. PW