yashsingh1/xdaforums huggingface dataset:
[Magisk] PattayaGlock:
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?
[Magisk] amk316:
some apps "stc pay" can find root by magisk app even if you hide it

if you delete the magisk app it will not find root!!!
[Magisk] elhennig:
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?
[Magisk] pndwal:
Installation Instruction update:

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
[Magisk] zgfg:
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
[Magisk] pndwal:
Please say device (model), what Magisk version, if any, you had working before installing v.23.0, etc. PW
[Magisk] pndwal:
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
[Magisk] 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
[Magisk] pndwal:
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?

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

Likely solution:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84790337 PW
[Magisk] J.Michael:
@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.
[Magisk] 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 !! :D :D
[Magisk] wtosta:
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.

No, it doesn't occur.

I am trying to test what is written in the solution, but with no avail :-(
[Magisk] zgfg:
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)
[Magisk] Didgeridoohan:
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).
[Magisk] zgfg:
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
[Magisk] 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 !
[Magisk] whitewallman:
This is probably a stupid question, but what does that last number in parentheses in the version number indicate? In my case, (21)
[Magisk] Elcosomalo:
Hey thanks! I've been looking if someone reported this issue and couldn't find it! will keep an eye on it
[Magisk] 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.
[Magisk] Didgeridoohan:
That's the app stub version. The stub is installed when you repackage the app with a random package name.
[Magisk] whitewallman:
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?
[Magisk] pndwal:
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
[Magisk] pndwal:
So you still need to boot into Recovery each time, (and now seems you'll need USB connected due to changes), but timing of key release is critical:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Hope it helps. PW
[Magisk] pndwal:
Have you cleared app's data (to reset) SINCE adding to hide list?

This, or something else here may help:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84936057 PW
[Magisk] whitewallman:
Can you dumb that down a bit? 😊

Is it normal, or should I reinstall somehow to not get that stub number?

Thanks in advance.
[Magisk] J.Michael:
It is normal. Reinstalling won't change anything.

It is telling you the version of three software components installed/available. The stub version is the version that will be used if you engage "rename Magisk Manager to hide it". Whether you've used it or not, that is the version that is currently on your machine, waiting to be used.
[Magisk] wtosta:
Finally I figure out what was the cause of the problem in enabling the NFC module when launching the Google Pay application and trying to make a contactless payments. The NFC module was turned on, but Google Pay app said that NFC wasn't set up. The cause was a fix safetynet-fix-v1.1.1-samsungmod.zip for the Samsung phone. But when I applied the safetynet-fix-v1.1.1.zip, contactless payments work, but some bank applications refuse to use fingerprint sensor as an authorization method.

However, I must add that after applying the safetynet-fix-v1.1.1-samsungmod fix and later uninstalling it, rebooting and installing safetynet-fix-v1.1.1 did not help. The NFC error in Google Pay still occurred, so I had to make a clean system installation. No cleaning of the apk cache or resetting Magisk and Google Pay apk's data to their defaults did not help.

So I must assume that Magisk 23 has probably nothing in common with the issue. But only the fix that turns on basic evalType in SafetyNet check causes problems with using fingerprint authorization. These are just my assumptions. I am not an expert on the subject here.
[Magisk] Didgeridoohan:
That is a correct assumption. Universal SafetyNet Fix v1.1.1 is known to cause fingerprint authorisation issues on Samsung. This is surely discussed a few times in the module thread...

There's a test version on GitHub that should solve your issue.
[Magisk] xdathermoman:
With latest Magisk 23 Update on Raphael (LineageOS, Android 10) WIFI doesn't work anymore. Wifi gets disabled 2 seconds after enabling it.
[Magisk] pndwal:
Ah, good result.

So, have you:

- got 'Device is certified'

- selected Google Pay in MagiskHide list and rebooted

- AFTER the above, wiped Google Pay Data (not just cache)?

As you don't get error message, I'm guessing this could also be a conflict with NFC, an not 'root' detection issue at all.

Have you tried booting / testing with all Magisk modules other than USNF?

Nb. USNF is also known to break biometrics (including w/ GPay) and other functions on heavily skinned ROMs, especially Samsung One UI.

In the (very likely) event that this is breaking NFC compatibility, the test module I mentioned recently will likely fix it for you:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85001087 (Ignore references to OnePlus specific issues w/ Android 11. It fixes many Sammy issues w/ earlier Android.)

Other solutions are found in closed issue threads for USNF, some of which are linked from that pull request thread, including a number of modified USNF modules in this one in particular:

https://github.com/kdrag0n/safetynet-fix/issues/6

I think the test2 mod is a likely fix. Read the thread for insight. If doesn't fix, read last thread thoroughly too. Seems S8, S9, S10 issues / fixes are similar. 👍 PW.
[Magisk] pndwal:
Seems you already worked out it's the second issue I mentioned in last post... Sorry, I nearly sent that a few hours ago, but ran out of lunch break (Sydney time), and finished / posted it after work.

However, the USNF pull request link opening post explains why SafetyNet Fix on non standard AOSP ROMs (ie 'heavily skinned' / heavy keystore customizations like One UI) is difficult and breaks things, but why 'Shim the keystore service instead of replacing it' method is more successful for these devices.

Hope the test module or others posted / adapted by users helps. PW
[Magisk] pndwal:
Have you tried 'Hide the Magisk app' function in Magisk App settings? PW
[Magisk] pndwal:
It's been well explained, but did you notice that version number only appears in App - Latest, as per your screenshot? This indicates clearly that it's not installed (so there's no need to disengage it).

If you do use 'Hide the Magisk app' function in App settings, you'll see it both in App - Latest and in App - Installed. In this case it is clear that it is installed (and that Magisk App has been repackaged as an unknown, ie hidden, app using different app signing key). 'Hide the Magisk app' function will also change to 'Reatore the Magisk app'.

Usage details here:

https://www.didgeridoohan.com/magisk/MagiskHide#

Scroll down to 'Hiding the Magisk app'

👍 PW
[Magisk] wafna:
thanks :-) I also had read this and it seems I am somewhat never getting the time right, because in the latest 24 hours I only got Magisk to boot once. I found out about the cable just by chance. If anybody else has a Note 10+ running Android 11 and knows how to boot into Magisk please write :-)
[Magisk] pndwal:
Xiaomi Redmi K20 Pro / Mi 9T Pro?

Do you have any Magisk Modules installed? Which? (ViPER4Android modules are reported to cause WiFi issues for example).

Did you take LOS update, then flash older patched boot.img to restore root? (You must patch boot image extracted from actual ROM in use. boot.img mismatch is a common cause of wifi issues). PW
[Magisk] xdathermoman:
Yes, exactly that.

I had only 2 Modules installed for the Camera to work with the google camera app.

I just updated via Magisk App. It informed me about an update and I did the update.
[Magisk] pndwal:
So boot.img is from same rom as in use?

Could be worth Disabling all modules, reboot and test. PW
[Magisk] wtosta:
Thanks to pndwal hints I finally figured out SafetyNet working configuration for starlte.

SafetyNet fix for Samsung OneUI 2.5 working for me along with Magisk 23.0 on Samsung Galaxy S9 phone.

I will write briefly what I was able to determine. Maybe someone will find it useful.

Device: Samsung Galaxy S9 (starlte)

ROM: Alexis Rom 2.7_FUD5 OneUI 2.5

Magisk version: 23.0

Helpful topic

Working SafetyNet fix

SafetyNet check succeeded with evalType: Basic

Biometric authorization is working in banking apps.

NFC module and so contactless payments are working in the Google Pay.

Thank you pndwal for helping me to resolve this issue.

Best regards,

Witek
[Magisk] pndwal:
Great! That issue thread looked promising with a number of custom mods for Sammy's various Keystore implementations. Glad you narrowed it down.

So this post has working fix for your Samsung Galaxy S9. Interestingly, it uses Galaxy note 10+ N975F Keystore:

https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-765364783

It's surprising that the one from here https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-764129632 didn't work for you - it's supposed to work for Android 10, tested on Samsung One UI 2.5 (but I think you removed that one earlier). It's a complicated business.

I do hope that @kdrag0n's 'Shim the keystore service' test module can be improved to become the next Universal SafetyNet Fix and include devices (like Samsung) that heavily extend the keystore service beyond AOSP.

Clearly, a mod that fully replaces so many keystore variations is impractical...

... Unless a database can be set up and members contribute their Keystores... Just like @Didgeridoohan's elegant MagiskHide Props Config database of fingerprints, replete with contributing devotees! 😛 (JUST a thought. 😉 )

👍 PW
[Magisk] wafna:
Fixed. A module was causing Magisk not to load. Here is the incantation to load Magisk on a Note 10+ with that bad operating system:

a) on the computer:

1) install the latest adb

2) open a "powershell" (shift and right-click on an open space in the folder where adb has been extracted)

3) start the adb daemon with ./adb start-server

b) on the working phone

1) turn off USB debugging

2) revoke authorisations

3) turn on USB debugging

4) connect the phone to the computer with a cable - allow USB debugging from this computer "all the time" (not once!)

5) detach phone

6) turn off phone

c) on the computer:

1) give the command ./adb wait-for-device shell magisk --remove-modules

d) back to the phone

1) attach the phone to the computer

2) turn it on by pressing shortly just the power key, you will get a warning about "phone bad, bootlocker unloaded"

3) quickly press power and volume up, keep them pressed "a short while" (you will get it by trial and error)

4) you then will get a second triangle on the bottom saying press power to start

5) it will seem like the phone is stuck in the bootscreen, it's not

6) let it boot. The command in the "powershell" will execute, it won't show success or anything

7) the phone will reboot

8) unplug the phone from the computer

9) turn the phone off again

repeat steps d1 to d5. While the phone is booting "after some time" unplug it again from the computer

if you are lucky then maybe you booted up with Magisk and no modules.

Very simple and straight-forward. With the hardware key-attestation and this I see that Google and Samsung with every update are getting more friendly for the consumer. Somehow imho they don't understand that if Android users wanted an "applified" phone that they can't play with, they would get an apple.

Good luck :-)
[Magisk] wtosta:
I agree with this it is a very complicated matter. The fix that you have mentioned above has broken the NFC in Google Pay app. I have written about this previously.
[Magisk] J.Michael:
If the point of this procedure is to disable modules: Did you try booting to Safe Mode?

Safe Mode is an Android notion, some button combination for your phone. I don't think it matters whether Magisk is active in Safe Mode. The next boot after Safe Mode, you do need to get Magisk to activate, but if you do, Magisk will disable all modules for that one boot.
[Magisk] wafna:
aaahhh thanks, I had forgotten about safe mode, maybe it would have worked :)

I have no idea how to get it in a Note 10+ :)

Also Android 11 seems to be making fun of the users, it says "Super Fast Charging 2.0" :-D there is FAST and SUPER FAST but also SUPER FAST 2.0

Next will be a charger that is REALLY SUPER FAST!

and in settings it shows hashtags before the search such as #notifications and #security, I thing they are being ironic at this point

But thanks for the reminder about safe mode, also Magisk loads without a cable being attached luckily :-)
[Magisk] zgfg:
Both Safe mode and -remove modules (and more) explained in Magisk Wiki pages linked from Magisk github site
[Magisk] amk316:
yes... for the beginning

this is a new method i am sure of it.
[Magisk] Didgeridoohan:
Apps detecting the Magisk app even when it's hidden is not new, not even with the stub hiding method. I've had a mention about that in my guide for some time:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hide_the_Magisk_app

There are several ways of detecting Magisk that can't currently be circumvented.

If you can figure out exactly what the app in question is detecting in the stub, with logs and everything, you could open an issue ticket on GitHub and possibly help make Magisk's hiding methods even more robust.
[Magisk] whitewallman:
Thank you for clearing that up! Yes, I noticed the latest vs installed. Which is why I posted the question. Thanks for sharing your expertise. 👍
[Magisk] chrcol:
guys, I see the latest magisk seems way more complicated than it needs to be requiring patching method, and checks for ramdisk support.

Does anyone here still do it the good old easy way inside twrp and works ok for you?

If it really is not reccomended now I may stick with 21.4 and older.
[Magisk] zgfg:
You should ask specifically for which device/ROM and which TWRP - e.g., you may have A11 and your TWRP might not be properly compatible with, etc

On the other side, patching is not that complicated at all, you just need to learn it first time. Particularly, ask/discover which image you need to patch (again, depending on your device/ROM) and next time you will just repeat the same procedure

Check also on XDA forum for your device

By your profile, seems you have OnePlus device - I'm pretty sure they have been covered here in the previous posts, questions, answers (I have Xiaomi and cannot help you)
[Magisk] Didgeridoohan:
Nothing has changed regarding installation methods between Magisk v21.4 and later releases (currently v23.0). If you could install Magisk v21.4 through TWRP you can do the same with v23.0 (generally, there are some internal changes that may cause incompatibilities but most devices should be unaffected by that). John hasn't recommended installation through TWRP for a long time, way before v21.4.

The main difference (regarding installation) between v21.4 and later releases is that there's no separate zip file. Everything is contained in the apk now and if you want to install through TWRP you just rename the .apk to .zip. But this has been covered many times since the release of v22, so if you want more details you can surely find those here in the thread...
[Magisk] DomeNinchen:
Good day dear community,

I have a question regarding the use of the app S-pushTAN(https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan) and the Magisk Manager.

I have hidden the app in MagiskHide and renamed Magisk. There is no file/folder named Magisk, root or TWRP in my memory, yet the app does not work based on root detection according to the message. What can I do? Does anyone have any ideas? The picture shows the current Magisk version I am using.

Many thanks already

Spoiler content hidden.

Translated with www.DeepL.com/Translator (free version)
[Magisk] ValeV008:
Hi all. What do you think I should do if magisk manager doesn't start and just hangs?

Basically my Magisk Manager notified me of new update, so i went to menu (where all apps are shown) and clicked on Manegr (i changed the name of Magisk Manager). Sadly app didn't start, and android OS became almost not responding, it kinda crashed. This happens everytime i want to run magisk manager.

I am thinking of uninstalling magisk manager and reinstalling it, but i'm not sure how that will affect the root, and also because it has different name (Manegr). My other idea is dirty installing it over the current one, but same problems could arise.

Anyone got similar problem?
[Magisk] DomeNinchen:
Hello,

I had the same problem. Just uninstall the app, download the latest version from github, then reinstall and change the name again. All the settings you made should be retained, that's how it was for me.

Kind regards
[Magisk] unknowndrop:
Hello.

I am planning to install Proton to my Pixel 2 XL over stock rom. Since I am really out of rooting 'scene'. Does magisk bypass safetynet and snapchat or mcdonalds app work while magisk is installed?