yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Their is no new official build as yet so all is still the same.

So far MagiskHide still exists in new commits, but "Remove all non-Magisk hiding code" commit means 'Magisk no longer interferes with any signals/info that were not created or caused by Magisk itself.'

Indications are that while SafetyNet will fail initially in new builds, MagiskHide will still exist and settings to pass S/N can easily be reinstated. (See my post above re. latest unofficial Alpha). PW
[Magisk] Didgeridoohan:
Better to run adb wait-for-device shell magisk --remove-modules with device hooked up but turned off, and then turn on the device. That way you'll know that the command will run at the right time.
[Magisk] Homeboy76:
Yup, I was a little late arriving at the party. :)

I'll try and be on-time for the next party. :)
[Magisk] pndwal:
Key Combo Timing for Safe Mode on MIUI / Xiaomi

Thought I'd try safe mode on my (Xiaomi) devices... for my own safety. 😜

I have Mi Pad 4 (LTE) w/ LOS18.1 (Android 11), and Redmi Note 8T w/ stock MIUI (Android 10).

Indeed, I have not been able to access Safe Mode from RN8T / MIUI from booted system any which way 🤨, but no problem on Mi Pad 4 / LOS.

From device powered down I also had issues with timing on both Mi Pad 4 / LOS and RN8T / MIUI.

Holding the pwr button down for more than ~6 seconds after MI / REDMI logos appear causes black screen and fresh reboot, so it is necessary to release pwr after about 4 seconds.

Releasing pwr then pressing vol- immediately after MI / REDMI logos appear doesn't trigger Safe Mode.

After releasing pwr at ~ 4 seconds, then waiting(about 10 seconds more) for boot animation (LineageOS / MIUI animated logos), then holding vol- until booted, I get Safe Mode but Magisk has not detected button combo, and MagiskHide / modules are still enabled.

Working method:

However, by holding the pwr button down and releasing it after about 4 seconds, then holding vol- during these logos as well as boot animation logos until booted I get safe mode and Magisk detects / disables MagiskHide and modules.

So clearly Magisk's button detection is not reliable, and it seems there is a critical timing sweet spot, at least for Xiaomi, where Safe Mode is triggered and Magisk also detects the key combination. 🤪 PW

Edit: I've now opened an issue ticket for this.
[Magisk] pndwal:
John wants this:

Magisk root on PC w/ Windows 11! 😜

www.twitter.com/topjohnwu/status/1432766910513307650

... and I have a big bridge for sale... anyone interested? PW
[Magisk] zgfg:
His decision but IMO, it's just distraction from the Magisk 'core business'

Besides, who will really need Magisk for PC Windows?

People usually have their own PCs where they are configured themselves as Admins (hence they have full access).

If they have Linux PCs, they are indeed roots on them

For the employees with business PCs, users are usually given only limited permissions but PCs are monitored

Personally, I will never even think about installing Magisk to my business laptop (I get calls from our company IT when they scan drives and find that I temporarily stored my TWRP nandroid backup from the phone).

And for my own PC at home, I can do whatever I want with and don't need Magisk for that

Edit: Yes, I've seen on Github Magisk Issues how some people play by building Magisk for PCs, but again, it's IMO of very limited interest
[Magisk] pndwal:
I assumed it was a joke... but maybe not. 😜

Doubt Windows Subsystem for Android will be anything like Android-x86...

Perhaps I'll keep that bridge after all! PW
[Magisk] zgfg:
With the latest Alpha, does the magiskhide cli command still work from terminal root?

Also, upon the update, does MagiskHide tab still list all apps/processes that have been enabled for MagiskHide with the previous Magisk versions (like with Alpha 31)?

I'm asking because I want to know would I have to re-enable MagiskHide for all apps (that previously were enabled for MagiskHide) or that the latest Magisk update only removes gms from its MagiskHide enabled list?
[Magisk] pndwal:
Ive never played with Magisk from CLI, but I'd be surprised if anything here differs much...

Perhaps you could give me a simple command to try and I can report... Or I'll look at this later.

Yes, all manually added items are unchanged.

Only Auto-added (w/ MagiskHide toggle) SafetyNet process (com.google.android.gms.unstable) in Google Play services is gone for me, but once added manually it survives MagiskHide toggles and works fine.

I recall you reported that MagiskHide toggle adds two Google Play services processes are added on your Redmi device. I've never understood this especially since John only ever mentioned SafetyNet process (com.google.android.gms.unstable), but perhaps extra Google Play services processes will need to be manually added on some devices.

All apps are hidden / working as before so far, including Bank app (mine needs only standard MagiskHide setup).

I haven't yet tried Google Pay contactless payment, but I suspect this will be fine too.

Having said this, I am running Universal SafetyNet Fix and Riru-MomoHider modules, both of which may be covering for other Magisk changes.

Momo and Magisk Detector results are much as before:

- I don't recall if 'bootloader unlocked' trace showed before; do you get that w/ Alpha-31?

After clearing data and reboot, this:

Then ½ an hour later, no reboot or changes, last item changes:

This often occurs and still baffles me.

Momo result is unchanged.

Only changes here are as above.

I was pleasantly surprised that historic MagiskHide has been so easy to reinstate, but we should note that John is still making new commits.

We may be in for new surprises when we get his first release as an official "Googler". 😜

However, I'm quietly optimistic that he's done reverting the MagiskHide device state detection circumvention functions (ie functions that 'spoof/alter/manipulate non-Magisk related signals and traces') he indicated that he would. 😬 PW
[Magisk] pndwal:
Further to this, I just ran Check SafetyNet with MagiskHide disabled after manually adding SafetyNet service, com.google.android.gms.unstable, in Google Play services to MagiskHide list (I'm running new Alpha with TJW commits to 30 Aug) and was surprised to find that it is still showing full pass! - Strangely seems MagiskHide list is hidden but not disabled.

However, this reverts to failed (MagiskHide list disabled) after reboot. 😜. To pass again, toggle on MagiskHide (reactivates MagiskHide list); no reboot needed.

Guess that's why John's keeping MagiskHide

option. 😛 PW
[Magisk] zgfg:
Ok, thanks, I'll update today but in the evening

You can just try (list of enabled processes):

su

magiskhide ls

Without an arg it will give you help (man page), rm ... removes, add ... ... ads

I don't use riru modules and I always had abnormal status but didn't bother about

We'll see what future brings but per my understanding MagiskHide will be fully removed at least its UI from Magisk app (requiring a module to handle) - if not also its full functionality from Magisk itself.

Currently, just by disabling per default gms unstable does not require a module at all
[Magisk] pndwal:
List works; guess that's enough to confirm...

Maybe, and it'll all come out in the wash for sure...

However John said:

Does this mean MagiskHide list will be replaced with MagiskDeny list which will deny root access and ability make root-access-required changes? And is that essentially exactly what MagiskHide does but with focus on denying ability to make privileged modifications rather than simply privileged probes? (...a re-badging to remove connotations of hiding 😜?)

Interpretation anyone else?

Yup, but most will of course still need current spoofing modules for SafetyNet anyway... PW
[Magisk] zgfg:
Ok, thanks, I've updated to f98c68a2-Alpha (apk, then patched and flashed my A11 boot.img)

MagiskHide was enabled with all my previous apps|services except GooglePlayServices

I had to enable it for GMS again, but both checking in:

com.google.android.gms

com.google.android.gms.unstable

Only the second one (with reboot) was not enough

With both enabled and after reboot, SafetyNet is passing, Device is certified and Play Protect is ok

And yes, MagiskHide CLI works (for me, CLI would be enough - can live without MagiskHide tab in the app)

We'll see what comes in future (from Google, John, vvb2060, etc)
[Magisk] asripath:
on magisk 23.0 for a while without any issues.

magiskhide on, magisk is hidden,

everything was working fine for months...till today

noticed safetynet test is failing
[Magisk] zgfg:
I've seen similar reports on USFN thread. Maybe Pixel (device, ROM)?

Irreversible climate changes and maybe doomsday is coming earlier
[Magisk] gamehust:
The same today on my phone. Google Pay stopped working 30 min ago. Google Play services or gpay updated over air?
[Magisk] rodken:
At least my Google Pay still functions with f98c68a2-Alpha.
[Magisk] pndwal:
Please say device / model. 👍 PW
[Magisk] dcarvil:
Safetynet now failing for me also. Pixel 2XL and Pixel 3, both on LineageOS. Play Store still shows device is certified.
[Magisk] asripath:
same here on mi 9T pro on custom rom

playstore cert is fine
[Magisk] thibault_44:
Same case for me on same device. EvoX rom install.
[Magisk] zgfg:
When SN starts failing, it will take some time that Device becomes not certified😥
[Magisk] rodken:
OnePlus 8 5G UW running stock OOS 11.
[Magisk] pndwal:
So far a common factor in this thread, USNF thread, and one issue in MHPC thread, is use of fingerprint spoofing (I'm assuming this based on custom ROMs mentioned).

May be an issue for @Didgeridoohan.

May be Google is detecting mismatches, and may be a tough nut... 😬 PW
[Magisk] pndwal:
Yours may be a different issue.

Did you manually add SafetyNet service to MagiskHide list since it's removed due to latest TJW commits merged in Alpha? If not, please see my notes on this in Latest Alpha Changeling post. PW
[Magisk] Lord Sithek:
My Sammy Tab S5e runs stock A11 without fingerprint spoofed. I'm using USNF thou
[Magisk] dcarvil:
I'm not using fingerprint spoofing on my Pixel 3. SafetyNet was passing before today.
[Magisk] dunderball:
I got the 'device doesn't meet security standards' notification this morning. Safetynet failing all of a sudden. Kind of a bummer. Just using plain Magisk + magiskhide + universal safetynet fix. Any ideas?
[Magisk] pndwal:
I think in your case you are however, because AFAIK this is always needed with custom ROMs and you said you use LOS.

If I'm not wrong, official LOS users will need 3rd party spoofing, MHPC, old SafetyPatcher etc due to LOS anti spoofing policy.

Unofficial LOS devs often spoof a passing fingerprint in ROM... Are you using unofficial LOS? PW
[Magisk] Displax:
So, new layer of HARDWARE detection is here.

SafetyNet failed on devices, where must bee HARDWARE detection. GMS no longer check system response of evaluation type, and force check HW. USNF doesn't work in this cause.
[Magisk] pndwal:
Do you mean MagiskHide itself is on, or do you have MagiskHide Props Config module and custom ROM? PW
[Magisk] dcarvil:
Official LOS with USNF.
[Magisk] dunderball:
I'm on stock android rom on a Pixel 3a. I've managed to just use Magisk + magiskhide module + safetynet fix module, that's all. Now everything's failing.
[Magisk] pndwal:
If you mean MagiskHide Props Config module, is your spoofed fingerprint an exact match for device and Android version? ... If not it may be worth trying closer Pixel 3a print. PW
[Magisk] rodken:
Even after installing Universal Safetynet Fix, 'S/N fails - GPay still functions [for now].
[Magisk] pndwal:
Thats interesting. May be worth installing MHPC module and Terminal Emulator, type 'props' in TE and choose first option to set a different fingerprint...

This does seem to be fingerprint related, but I can't quite put my finger on what's going on yet... PW
[Magisk] dcarvil:
I did that on my 2XL, but it still fails.
[Magisk] zgfg:
Seen the following circulating around (posted to that channel today morning):

Modules Repository | #TeamFiles

All the files you need for customizing your Android device!	#TeamFiles chat:	@fileschat	#TeamFiles announcements:	@teamfilesannouncements	More from #TeamFiles:	@filesfederation	Off-topic Group:	@TeamFilesOT

t.me

Basically as the recent post in USNF thread:
[Magisk] pndwal:
Haha - I couldn't reply till you added that edit - wouldn't load you as recipient with message blank! First time I've seen that. 😜

Yup, realised it wasn't lack of hiding SafetyNet service when I saw you still had basicIntegrity... May have to wait for clarification... Just saw @Displax's post above... PW
[Magisk] Lord Sithek:
Since I use LSPosed for a long time on my Sammy tab, I decided to give it a shot. XPrivacyLua is not new to me, but I've never really need it before. Surprisingly, it worked...
[Magisk] Seehank:
Mi9T Pro - EvoX - Magisk 23
[Magisk] rodken:
It turns out that the 'xprivacylua app' work around is the way to go.
[Magisk] dunderball:
I've tried that module and switching to a Pixel 4a fingerprint doesn't pass either. I think this is a widespread thing
[Magisk] itsmir:
Mi 9T on MIUI Global EEA 12.0.5 Magisk 23.0 using Universal SafetyNet Fix 1.2.0 successfully until today.

CTS profile suddenly started failing this afternoon, basic integrity still passes. GPay no longer working :(
[Magisk] zgfg:
Yes it is widespread. And fix is already know - roll back few posts today afternoon
[Magisk] Displax:
Hm, funny things happening. I was thinking this is upgrade of HW attestation, but it is DOWNGRADE actually. 😄

Remember my old first simple digging into HW?

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83028387

It`s..... working again.

Looks like a temporary solution or just "combo" of old and new methods from Google.

This explains the fact that dirty hack with Xposed-s working now.

So, this current environment may be temporary or preparation for something BIGGER.

In conclusion: in this time to passing SafetyNet you need just my old "hardware_off" module from link above or "MagiskHidePropsConf" with any "BASIC" print with model simulation and kdrag0n-s "Universal SafetyNet Fix".

No ***-posed-s need!
[Magisk] camperbh:
Actually, props config + universal fix wasn't enough. Only after installing your module alongside those two, I was able to pass both checks. You're a king.
[Magisk] Displax:
You need to simulate device "ro.product.model" in MagiskHidePropsConf
[Magisk] Lord Sithek:
Haha true. My Sammy tab is passing without XPrivacyLua.

Let somebody ask John what is really going on :ROFLMAO:
[Magisk] J.Michael:
You can ask, but he is probably not at liberty to answer.
[Magisk] Lord Sithek:
Ofc, just a "dirty" joke.
[Magisk] dunderball:
I don't use Xposed. Any idea how to get safetynet to pass?
[Magisk] Lord Sithek:
You have that just above.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85573141
[Magisk] dunderball:
Thanks, trying the module now.
[Magisk] Displax:
OK. AIO solution. Modded "Universal SafetyNet Fix" module. Just added "model" props.
[Magisk] dunderball:
This worked like a charm.

Pixel 3a, stock rom. Thanks for this.

Gonna reset my google play store and google pay now.
[Magisk] Lord Sithek:
I'm afraid this wouldn't work well on Samsung devices which need to shim keystore instead of replacing... Original 1.2.0 cause interface freezes for my tab
[Magisk] itsmir:
Thanks for the heads-up The XPrivacyLua trick worked for me. SafetyNet passes & GPay working again.
[Magisk] Displax:
Added shim variant.
[Magisk] Lord Sithek:
Excellent, thank you!
[Magisk] rogers11:
Perfect
[Magisk] Chandru123:
Thank you very much @Displax
[Magisk] ttar ttar:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85573473

It worked perfectly. Just flash the USFN v1.2.0-MOD. Thanks!! @Displax
[Magisk] linuxares:
Tried it on my OnePlus 7 Pro with Pixel Experience.

Just flashed it but still same issue with ctsProfile not working. I wonder if Lsposed still lingers round even if I deleted it.
[Magisk] vint2007:
It work on Pixel 4a.

Displax, thanks a lot!!!
[Magisk] Dorisnov:
I'm in PE with my Mi 10T Pro and also not working, maybe is not simulating ro.product.model successfully.
[Magisk] linuxares:
Might be. Any normal Pixel users had success?
[Magisk] zgfg:
Heads-up: Do not use a wrong SN checker (like the one on the first screenshot with volume limitations on the back side - failing when too many users try to test with)
[Magisk] dubble3535:
Tried on my OnePlus 7T pro with Pixel Experience Plus

ctsProfile not working
[Magisk] Dorisnov:
Looks like this is not working for PE.
[Magisk] dubble3535:
Yeah not any success on PE
[Magisk] Dorisnov:
What model is simulating? Because in PE I still hace Pixel as model.
[Magisk] Marlenio:
Not working on Xiaomi MI9T Pro with latest EvolutionX. With latest ArrowOS on the same device works perfectly without magisk modules.
[Magisk] SkRiMiX:
It sets these props, so it's simulating Pixel:

ro.product.model=Pixel

ro.product.system.model=Pixel

ro.product.vendor.model=Pixel

ro.product.product.model=Pixel

ro.product.odm.model=Pixel

Could be the reason why it doesn't work on PE
[Magisk] Fif_:
I've been getting CTS errors on a OnePlus 8T since this morning.

Using @Displax's hardware off module fixes the issue. On my device, just using

resetprop ro.product.model BASIC

does the trick. Until next time of course.
[Magisk] Dorisnov:
Anyway without the module I have my phone's original device.

Im not good at this, any idea de how to fix for pe users?
[Magisk] klemi71:
Working on Pixel 3 latest Android 11 Magisk 23.
[Magisk] Displax:
Using "BASIC" model instead of "Pixel". Does it work for you?
[Magisk] sauaditi:
Not working

Tried safetynet Mod but still not working

CTS profile failed

Evaltype - BASIC

Help
[Magisk] zgfg:
Did you try the other method originating from TeamFiles with Riru, LSposed and XPrivacyLua that was also posted in this thread today afternoon and some users confirmed it working (not sure which phones)
[Magisk] Dorisnov:
I dont, i'll try now.

Nope, CTS still failing. Do I need to do something after flshing this?
[Magisk] Displax:
Nope. Strange things with PE, EVO... Can you post your getprop with this module installed?

su
getprop
[Magisk] zgfg:
You must reboot after flashing any module (also upon manually changing props), to apply the changes - hopefully you did that
[Magisk] Dorisnov:
Sadly yes, I rebooted after flashing the modules or changing props.
[Magisk] pndwal:
It seems this fix isn't working exactly as it used to.

For example, many who were affected previously are not affected now. - I still have full s/n pass on RN8T W/ stock ROM. - And for those with the issue, changing model props don't always work.

I'd say we have more diagnosis to do.

FWIW, here are some notes from December 2020, when most of us were using variations on the @Displax fix. These will no doubt help those currently changing model props and experiencing issues with OEM / device specific functionality, eg with Sammy Galaxy store, HD content / capability, camera features etc, arising from this:

... And more conclusions / theories re. how prop mismatch causes fallback to basic attestation:

https://xdaforums.com/t/module-magi...p-edits-and-more-v5-4-1.3789228/post-83658543

https://xdaforums.com/t/module-magi...p-edits-and-more-v5-4-1.3789228/post-83654739 PW
[Magisk] cater2:
could anyone here tell me how to fixed safenet ? There's a lot up there that's confusing me. thanks
[Magisk] pndwal:
Please check the second link I gave you ( https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85573473 )

One of those two mods should fix it for you depending on your device. Please say model / OS!

You need to replace your original SafetyNet Fix module.

If standard Universal SafetyNet Fix module was working for you before (ie close to AOSP OS), choose the first option, safetynet-fix-v1-2-0-mod.

If you had been using Danny's test module 'Shim the keystore SafetyNet Fix' previously (ie heavily skinned OS, eg Samsung OneUI), choose the second option, safetynet-fix-shim-mod. 👍 PW
[Magisk] cater2:
my model is galaxy m12 android 11

rooted https://xdaforums.com/t/root-modified-magisk-for-galaxy-a21s-r.4271537/

sorry for the stupid question , but i remove .Universal SafetyNet Fix module and install one of those you indicated ?

thanks

note: I installed the first module and fixed SafetyNet |o| many thanks :))
[Magisk] blinoff82:
Both not working on Syberia OS Poco F3 (A11). Which props you need to see mate?
[Magisk] pndwal:
Yup.

Second will be better for Samsung, if it works... PW
[Magisk] kartikb:
Hi, how did you manage to get gpay working. I tried but can't get it to work once i have xposed enabled and setup xprivacylua and check play services in it. After disabling xposed and clearing app data for gpay, then it works but not otherwise. Any help would be appreciated, thanks.
[Magisk] cater2:
worked with the first ...

Looking better , it passed the test app , but on Google Play , it says the device is uncertified , I 'll test the second one .

Note2 : Well... I deleted the data from Google Play and now I have device certified in Google Play (first module installed)
[Magisk] Lord Sithek:
Don't forget to clear store data
[Magisk] pndwal:
Good, but as Danny (dev) said, this is not fully compatible w/ heavily skinned OS's like OneUI.

Sammy devices use modded Keystore AFAIK. Standard fix uses straight AOSP, so you may have instability and other issues... Shim Keystore fix addresses that. PW
[Magisk] Fif_:
That's a very big hammer to use and using all of XPrivacyLua hooks on Play Services is likely to cause issues.

I'm still affected now on a OnePlus 8T.

I've also tried to use MagiskProps Hide Config with OP8Pro and OP7Pro signatures and it didn't work.

Only this works:

resetprop ro.product.model BASIC

See above about using XPrivacyLua.

If you want to still try it, did you whitelist Play Services in EdXposed or added it to XPrivacyLua's scope in LSPosed?
[Magisk] TheKerevas:
POCO F2 Pro with OneOS 21.8.30 (xiaomi.eu) the first module worked but I lost some Xiaomi functions. After installing and configuring everything I uninstalled the module and for now it is working, from experience just do not check more SafetyNet
[Magisk] zgfg:
Read yesterday-today posts in Universal Safety Net Fix thread about how to properly configure things (to 'fix" GPS issues because of improper privacy settings), and with success reports
[Magisk] lordschmaeh:
For me, magiskhideprops and safteynet module 1 don't work. Poco f1.

Is there a recommended fingerprint model i should use? I am on latest crdroid (A11) but for poco f1 you can only choose fingerprints from A9 or A10.

Edit: btw on my Galaxy s5 w Los evrything still works without and modules...
[Magisk] J.Michael:
If it works after disabling xposed and clearing app data for gpay, aren't you done?
[Magisk] MariusWildfire:
Those modded Safetynet-Fixes didnt work on my op6t with pixel experience.

Anything else I can try? Which fingerprint should i set?
[Magisk] pndwal:
Which Xposed? Riru + LSPosed has been fine with GPay for me till now, but NOT Riru + EDXposed (for some time now). PW
[Magisk] wyt18:
the new shim variant didn't work for me i'm afraid ... but sticking with kdragon's v1.1.1 samsungmod + LSposed + XPrivacyLua did

s9, stock 2.5
[Magisk] kartikb:
I have LSPosed but once I disable module in Magisk and clear data for GPay, and after enabling module it stops working even though safetynet passes.
[Magisk] sergio_sant:
Fix not working on mi Xiaomi Mi 10T Pixel Experience
[Magisk] charlessxavier:
Hi, using POCO F1, CrDroid.. I installed the SafetyNetFix Mod and the hardward_off module as well. But SN still doesnt pass. Evaltype is BASIC. Please help.... :(
[Magisk] Newtonsart:
This fixed my safetynet problem

I'm using a Samsung S10 device
[Magisk] Inervo:
Hi,

I'm having the issue as well on my side: google pay stated that my phone is rooted, and deactivate my cards.

I have applied safetynet-fix-v1-2-0-mod, pass again the safetynet check, clear data of google pay, but my cards are still disabled.

I have no fancy magisk module, except magisk props.

Any idea how to solve google pay?

Thank you.