yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Progress also on the other front:

TheHitMan7 (aka MagiskCustom) 95a4a4b8 from yesterday now works with LSPosed

I've tested with GravityBox-R and CustoMIUizer, with some mods there and it works just fine as with Magisk Alpha

With MagiskCustom:

- there is MagiskHide (not DenyList)

- MagiskHide can work with or without Zygisk

- Modules Repo is available

- SafetyNet checker is also integrated to the Magisk app (yesterday it was removed from the latest Alpha).

(All together, more like the old Magisk Stable v23)

Otherwise, it is also based on the latest TJW's commits for Magisk

Btw, to make LSPosed working, you must use TheHitMan7's LSPosed build - he had to remove dependency of DenyList as built into the newer LSPosed (official) builds (since his MagiskCustom has MagiskHide, not DenyList).

Otherwise, his LSPosed build was built based on the latest LSPosed 1.6.2 (6.1.6.7)

However, I cannot make Momohider working - I enable isolated option but MagiskDetector still detects su in the path (on Alpha, that isolated option helps to hide su from the path)
[Magisk] rodken:
These are my findings or lack thereof concerning the 'head scratching' on the OP8 5G UW OOS 11:

I flashed;

8276a077-alpha Magisk

LSPosed-riru-v1.6.2-6168-release

Zygisk: Negatory

After which, I flashed:

8276a077-alpha Magisk

LSPosed-zygisk-v1.6.2-6168-release

Zygisk: Negatory

To finalize; I ended up going back to the ol' tried and true: b6298f86 - alpha Magisk and will keep the TheHitMan7's builds on the radar.
[Magisk] Antonio200:
Good night. I've been reading last pages but haven't found anything... I was affected by September Safetynet CTS profile failure, but in Google Play my device appeared as Certified so I did nothing. Today I checked Safetynet by mistake and it has passed. Tried in Root Checker and passed too. WTF?? Sorry... Could someone explain it to me?

Thank you and regards
[Magisk] 73sydney:
In simple terms (which is the only way i can understand it):

The safetynet issue on the 17th of this month (a day or two ago, depending on your location), looks like it was caused by an expired SSL certificate (attest.android.com) which expired on the 17th....see here:

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

People using the magisk inbuilt safetynet test were still passing according to it as apparently its cached in that test

Other test apps were failing

If you were failing last month, it was for a different reason...
[Magisk] zgfg:
How do you expect anybody can explain anything to you if you don't provide absolutely no info about your phone, ROM, Magisk modules you use, what did you change, etc.

SafetyNet is highly sensitive on all that.

Without detailed info nobody can help you and it will be wasting of time
[Magisk] Antonio200:
@zgfg Redmi Note 9 Pro, xiaomi.eu 12.0.2, Magisk 23. In September CTS profail failed in Safetynet but my device continued been Certificate in Google Play Store and my bank apps worked so, as someone posted here, did nothing (didn't installed Magisk Alpha, nor Displax or kdrag0n safetynet fix). Yesterday I updated Busybox and, not sure why, checked Safetynet, and it passed. Tried with Root Checker and passed too. I have tried right now and keep on passing. Read some pages trying to find someone in the same case and didn'f find anything...
[Magisk] zgfg:
When did you update Xiaomi.eu last time?

Did you use EdXposed (and later disabled/uninstalled)?

Do you use some other moduled like Magisk Hide Config Props and/or Universal SafetyNet Fix?
[Magisk] Antonio200:
@zgfg I don't remember when I updated, at least one year ago. And no, I haven't installed EdXposed, MHCP nor Universal SafetyNet Fix. I didn't touch anything because it worked, I thought it would stop working sometime and then I would have to install Riru+kdrag0n safetynet fix, but now it works, don't know why. All I have installed in Magisk is Busybox and Systemless Hosts.
[Magisk] zgfg:
That's strange because (I think it was) in Sep when Google did changes on the server side, it caused SafetyNet failures

Fortunately, fixes were provided soon in MHPC and USNF modules (mentioned in the previous posts)

EdXPosed also causes SN to fail but you also did not use

Xiaomi.eu provides SN fix (hence no need for USNF or MHPC) but you have all the time the same version

Btw, if you are on Xiaomi.eu Stable, why don't you consider to update to the latest (I believe there must be a newer version). For my Mi 9T, I'm on Stable 12.5 - guys, sorry for OT
[Magisk] Antonio200:
@zgfg Last time I updated, my old Sony smartwach started to remove apps from the watch and sync again the next day. I solved it installing some of them as system apps so I don't mind if the watch sync or not :-)

Thank you for your help
[Magisk] 73sydney:
@pndwal

Well Magisk (abfb3bb3-alpha) just became not my fave magisk version ever, Google Pay just lost contactless....weird

Gone back to you know which alpha by now....
[Magisk] pndwal:
Haha, I wouldn't know; I usually update before deciding I need to downgrade!

I'm on 8276a077-alpha. Made a $250 GPay purchase around 4pm yesterday, all good.

Have there been Google end changes since then? ... Maybe you're just becoming as paranoid as me!

Marvin
[Magisk] peikojose:
Does that latest alpha version will work with P5A and A12?
[Magisk] pndwal:
Well it should.

Alpha has built these commits for a while now (for proper Android 12 support); TJW has yet to do so:

- Target SDK 31

vvb2060 authored and topjohnwu committed on 2 Sep

- boot image header v4

vvb2060 authored and topjohnwu committed on 29 Aug

- Support code injection on Android 12

topjohnwu committed on 11 Aug

... and more!

https://github.com/topjohnwu/Magisk/commits/master

TJW built only w/ commits for Android 12 betas to date...

BUT I expect new Canary build at Any Tick of the Clock! ...

HOWEVER, this issue likely affects your device:

https://github.com/topjohnwu/Magisk/issues/4343#issuecomment-947304715

Contributors there have gained temporary root and tried earlier Alpha builds to gain permanent root, but it seems this is not yet fully resolved...

- You could give latest Alpha a crack! 😜

🤠 PW
[Magisk] m0han:
I'm on 8276a077-alpha myself. But, SN fails for me. I'm attaching screenshots of my setup. Please advise on how to get SN to pass. My device is POCO X3 (non-NFC) and I'm on the latest AICP 16.1 (A11). Thanks.
[Magisk] zgfg:
Generally, with (not-certified) custom ROMs (no matter which device and Magisk version) you first need to spoof fingerprints for e.g. same device but stock ROM (MHPC module - see the corresponding thread)

Then, if CTS still failing, you can further use MHPC or USNF to pass

PS: Assuming (for all people who switched to Alpha) that you have properly enabled Zygisk, DenyList and configured DenyList for GMS
[Magisk] pndwal:
https://github.com/topjohnwu/Magisk/issues/4343#issuecomment-947304715

Thought I'd address this here.

Since the enquiry (re Android 12 & fixes) continues, @osm0sis just responded:

Couldn't agree more.

Additionally, it IS the end of an era according to John...

Aside from farming out Magisk Hide work, the project should become

- More professional!

- It will incorporate better (regression) testing!:

Also,

- It now has a plethora of talented contributors whose contributions have ensured vastly improved compatibliy, stability and fewer bugs already...

I can't imagine that will change anytime soon thanks to John's model:

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

😀😃😄 👍 PW
[Magisk] pndwal:
In addition to @zgfg's advice, please see this:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85792975 👍 PW
[Magisk] zgfg:
I'm not familiar with Pixel and A12, but did you see:
[Magisk] m0han:
please see my screenshots (esp. the 5th) and advise on what is to be done further. thanks.
[Magisk] m0han:
did as i could manage after reading that post yesterday. but, not everything you mentioned there is on my device. please see my screenshots (esp. the 5th). could it be due to the gapps (basic package) i'm using or something else? i could investigate further with a bit of help. thanks.
[Magisk] zgfg:
@pndwall gave you the link for one of the many earlier posts in this thread how to configure DenyList.

You don't need AR services and so but only Google Play Services (you didn't expand to see which services you enabled) - see the screenshot
[Magisk] 73sydney:
Good old Magisk alpha 31....bulletproof

I made a GPay purchase for days and even a few hours earlier...then bang, gone...root detected....

Remove and reinstall alpha 31...all is sane again....

Guess im just going to stay here for a while again until the dust settles, cant keep up with (currently) 3 forks of Magisk :)

...Nigel...
[Magisk] m0han:
expanded and did as you advised. then installed mhpc module and tried the tips suggested in the xda thread and github documentation. upon reboot my magisk returned 'zygisk no'. yasnac reported both basic integrity and cts profile match as 'fail'. next, i tried usn fix module. still both basic integrity and cts profile match were 'fail'. thereupon, i reset everything in mhpc module and rebooted. magisk returned 'zygisk yes'.

with mhpc module and usn fix module still installed, i ran yasnac and it reported both basic integrity and cts profile match as 'pass'.

now, my question is: should i keep mhpc module installed? or, is it enough to have usn fix module installed and keep it updated?

finally, many thanks to the devs of mhpc module and usn fix module for their fine work and to pndwal and you for your great help.
[Magisk] zgfg:
If I understand you correctly, you got it passing without the use of MHPC - in that case you can safely remove the module

You could also just disable in Magisk app but leave it installed

But you can also keep it enabled - if reset and not used, it's dormant and not affecting but it can be handy if you would ever need to experiment something with props (I also don't use it but like to have it installed and enabled)
[Magisk] m0han:
that's how it is, as of now. thanks.
[Magisk] Didgeridoohan:
Correction:

Setting a certified fingerprint for your device is to pass CTS. Sometimes a combination of MHPC and USNF is needed to pass CTS, sometimes one or the other. Neither deals with basic integrity...
[Magisk] zgfg:
Yeah, he had problem with Basic Integrity because he didn't properly configure DenyList
[Magisk] m0han:
then i did as per your advice. yet, basic integrity failed.

i suppose this held good for me.
[Magisk] pndwal:
No, I hadn't.

I'm not across all the issues w/ Android 12 either. I was really just moving the OT (non-issue related queries re. Magisk's future) in that issue thread to this General Discussion forum...

But I see you've brought this information to the attention of early A12/Magisk guinea pigs in same issue. 😁 Looks like it may be quite relavent too.

Hope this helps them / devs addressing that issue. PW
[Magisk] V0latyle:
Folks:

Please realize that the "failure to load/verify boot images" message is not due to a Magisk issue.

Android 12 introduces Verified Boot on some devices, such as the Pixel 5, which will block a modified boot image from loading.

So, if you get stuck at bootloader with the failure message, this is because boot verification is not disabled.

You can find instructions on how to disable it in my thread here (this guide is for the Pixel 5; the instructions may be similar for other devices but it is YOUR responsibility to determine the correct procedure)

As far as failing safetynet, I used the Universal Safetynet Fix on 12 Beta 5 with no issues. I haven't updated to 12 Final yet so YMMV.
[Magisk] pndwal:
I stand to be corrected here, but I think MHPC now changes 'sensitive' props that MagiskHide used to handle to 'safe' (undetected) values by default (even if MHPC is not configured).

This may do no harm of course, but it should be understood that MHPC is no longer 'dormant' when reset or left unconfigured.

Also, as USNF now apparently does this also, this function may be duplicated / redundant, although I imagine this wouldn't cause any real conflict, only increase load time marginally. PW
[Magisk] pndwal:
...But that version (abfb3bb3-alpha) was already dated... did you ever try later 8276a077-alpha? I haven't had issues yet... PW
[Magisk] zgfg:
Didn't know and didn't expect (changes in effect if not activated through the module).

However, my /data/adb/modules/MagiskHidePropsConf/system.prop is empty (besides the header), hence the module makes no props changes through that file for me

Yet, my sensitive props are already ok by Xiaomi.eu ROM and I pass SafetyNet with or without MHPC

Anyway, since I usually experiment (also systemlessly) with changing props directly by manipulating my /data/adb/modules/.../system.prop file, I have now disabled that dormant or not MHPC :)
[Magisk] Didgeridoohan:
The sensitive props changing is active by default, yes, but only ever does anything if a prop is set to a sensitive value.
[Magisk] pndwal:
So seems no effect where prop already changed, which explains your result.

Ref for active setting of 'trigering' values to 'safe' is here:

https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props PW
[Magisk] 73sydney:
wasnt dated by much

i tend not to invite the possibility of more of the same, when i can go right back to stable ...im getting too old for much testing these days Marvin
[Magisk] pndwal:
Yup, only one more TJW commit:

https://github.com/topjohnwu/Magisk/commit/fe41df87bb34926cf2d6b448dd5a2878d90d4dc1

fixing this race condition:

https://github.com/topjohnwu/Magisk/pull/4759

Check the best minds on that: reopened, and just closed again...

Clearly some vvb2060 commit(s) too (esp. removing Check SafetyNet).

The fact that vvb2060 pushed fix so quickly should say something. Others reported abfb3bb3-alpha issues gone too.

8276a077-alpha is all good for me ATM... We'll see...

However, I always try to remember 'you can lead a mouse to water, but you cannot make it think'... 😜 ... Perhaps life on the bleeding edge does require too much of that... so just don't talk to me about life... Marvin.
[Magisk] pndwal:
This'll be fun:

@MishaalRahman (late of XDA) posted (on twitter) he just got WSA (Windows Subsystem for Android) up and running with Windows 11 (yes, you can sideload APKs!).

Of course, John is now pulling out all stops to 'root' it with Magisk! - Magisk for Windows; what a treat!

There's no ramdisk, but he's located 4 stage init (last 2 are Android 2SI)

He says "I found the init, the kernel binary, and initrd.img. Let's get things cooking baby!"... Go John! 😃 PW
[Magisk] arik100:
unfortunately search doesn't work properly for me.

i get error installed N/A

poco X3 pro

installed magisk,

patched boot via magisk

flashed patched boot via fastboot and then via magisk.

i have root but i get this "status"

any ideas?

i run arrow os android 12 (arrowos recovery)
[Magisk] pndwal:
Did you have Magisk installed / working on that device previously w/ App hidden? If so, see:

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

If you didn't update with Magisk App hidden, there are current issues with this symptom, eg:

1) https://github.com/topjohnwu/Magisk/issues/4319

- SU present but not working. Could try this workaround:

https://github.com/topjohnwu/Magisk/issues/4319#issuecomment-851840533

2) https://github.com/topjohnwu/Magisk/issues/4174

- SU working, but this affects devices with Android 6.x, 7.x.

3) FWIW, here's an old one that affected ArrowOS:

https://github.com/topjohnwu/Magisk/issues/4005

I suspect you have hidden app conflict, but there have been very few trials / issues reported w/ Android 12 as yet. 😬 PW
[Magisk] pndwal:
LSPosed guys have Windows 'Root' w/ Magisk! ... and Windows Xposed! 😃

LSPosed Telegram group.

😛 PW
[Magisk] pndwal:
Drooling? 😄

To drool or not to drool... That is the question. 🤪 PW
[Magisk] wilsonhlacerda:
Now they should try installng BitGapps systemless on it, probably it will be not that hard ( https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/ )

Amazon, Microsoft, Google will "love" that.
[Magisk] 73sydney:
It cant run any Google Services or any apps that reply on them...personally i dont see the point in Android on Windows
[Magisk] pndwal:
Perhaps it's just the drool factor. 😜...

But I used to live in the same town as Sir Edmund Hillary, and what did he do?

Spoiler:

Spoiler content hidden.

I can't really see the point of Magisk here either (except for some modules?), but I'll watch the proceedings for sure ... as long as top Magisk / XPosed / Riru Devs are excited about it, why not? (Some watch cricket!) 😃

What do I know... Perhaps they can add GMS / get GApps going! 🤪

Perhaps Google will even add Windows compatibility if this thing flies! ...

Or perhaps pigs might... 🙃 😁 😐

... Until then, Windows users will at least be instantly able to run a plethora of favourite Android apps on their PC's it seems. - That's gotta be Value Added functionality for many users and a selling point for MS! 🙂 PW

{Mod edit: ISPOILER added to upside-down text - Oswald Boelcke, Moderator}

My Edit: Thanks @Oswald Boelcke - good tip! 😛
[Magisk] DiamondJohn:
For devs, virtual android on windows is instrumental, and with easy root is brilliant. There are countless very strong reason for it. Even for non devs, having an environment to test that is not your daily is priceless in itself. Do you honestly think Mircro$oft went down this difficult route solely for bragging rights?
[Magisk] arik100:
1. what do you mean with app hidden?

2. about other options - i don't see any solution... just mentions, but again, i do have root , just that i get N/A and i can't install modules (which is annoying...)
[Magisk] zgfg:
It means Hide Magisk app (option in the Magisk app settings).

In that case you had renamed Magisk app to something else, 'hidden' name like zyWdPSqr app or whatever - you have to find it under your name in Settings/Apps or Apps drawer and uninstall it

That is the most common case when people claim: I have root but my new Magisk app shows Magisk N/A.

And that case has been asked/discussed/answered/instructed tens (add one more 0) of times already in this thread:-)
[Magisk] arik100:
1. there was a setting hide magisk which was ticked, but i didn't rename the app. just tick it.

2. right now i can't access the settings of magisk, and i don't really know how to start searching for the app , to add the fact that android 12 app drawer is quite weird..

3. do you have other suggestions? will full format solve this?
[Magisk] zgfg:
Hide Magisk is one thing (neccessary for SafetyNet) and Hide Magisk app (in the old times: Hide Magisk Manager) the other thing (needed to hide the app/mngr from some banking and similar apps)

Both these options are present in the Magisk app (former manager), they sound similar, and unfortunately many users do not distinguish Magisk itself (kind of 'service') from the app (kind of: user interface) - therefore not distinguishing hiding one from the other

When taking Hide Magisk app, then you don't only rename the app (you can even leave the original name) but (even if you leave the original name) the app will be obfuscated by renaming its package name.

Therefore, after that it cannot be found anymore under the package name com.topjohnwu.magisk.

In fact, new package name will be randomly generated (therefore there is no rule or default package name to help finding it)

You say that you have root. Instead of formatting, use some root explorer (fortunately you used it earlier and granted it root previously) and go to /data and delete adb folder (/data/adb).

Same can be done also from TWRP

However, try first again to find and uninstall (supposidely hidden) Magisk app (or manager if you previously had an older version of Magisk). In those old times default name for renaming/hiding was something like Manager and it used to have some uggly (Android default) icon
[Magisk] pndwal:
If you mean you did select 'Hide the Magisk app' but you didn't select a customised name, default obfuscated app name is usually simply 'Settings'...

Be careful, but you need to uninstall that.

You should be able to find it in device settings, Apps. Nb. It is often difficult to locate elsewhere. PW
[Magisk] pndwal:
Not sure this will help as obfuscated / conflicting app will remain... He'll still needs to find / remove it if present. PW
[Magisk] zgfg:
That's why I said at the end that he needs to find it and uninstall

(But I didn't use Hide Magisk app for long time and forgot that newer default name became Settings)
[Magisk] pndwal:
mmm... but you said 'instead of formatting' remove adb folder.

Removing adb directory solves many issues,. but won't fix this one as conflict is with app which remains.

Formatting / factory reset would solve problem, but removing adb dir. will just lead to frustration of setting up Magisk again only the find App is still unusable...

Correct me if I'm wrong. 😬 PW
[Magisk] zgfg:
At the end of the post I said there:

Now something semi-related.

My MagiskAlpha IS NOT hidden (not obfuscated)

But RootBeer does not detect Root mngmt app?!

It fully passes (when enabled in DenyList)

If disabled in DenyList it detects BB, su, root, Magisk but still does not detect plain com.topjohnwu.magisk package

Did I go insane?
[Magisk] pndwal:
OK... I think I understand that you meant wipe adb dir. only after fixing app conflict... Still not sure why though... Guess possibly to fix other issues...

Insanity is only a contributing factor...

You're on Android 11+ I believe. APIs changed w/ SDK 30.

Momo main screen seems answer your conundrum:

🤠 PW
[Magisk] wilsonhlacerda:
Opengapps:

GitHub - WSA-Community/WSAGAScript: Scripts to install Google Apps into a WSA image. Plus optional root

Scripts to install Google Apps into a WSA image. Plus optional root - WSA-Community/WSAGAScript

github.com
[Magisk] pndwal:
Great progress there!

GApps for Windows already, and can even sign in Google account w/ (use SU in adb shell to set selinux permissive) workaround! - Enforcing fix is bound to come too. 😛 (smelling any cheese now Nigel?)

Thanks for heads-up. 👍 PW
[Magisk] ipdev:
The current version of RootbeerFresh on PlayStore is from February 2019.

The target API/SDK level is 28 (Android 9).

package: name='com.kimchangyoun.rootbeerFresh.sample' versionCode='10' versionName='0.10' compileSdkVersion='28' compileSdkVersionCodename='9'
sdkVersion:'15'
targetSdkVersion:'28'

It conforms to the regulations Google set for Android 9.​

The current version of RootBeer Sample on PlayStore is from May 2021.

The target API/SDK level is 30 (Android 11).

package: name='com.scottyab.rootbeer.sample' versionCode='10' versionName='0.9' compileSdkVersion='30' compileSdkVersionCodename='11'
sdkVersion:'15'
targetSdkVersion:'30'

It conforms to the regulations Google set for Android 11.​

Even on Android 12..

RootbeerFresh will still find com.topjohnwu.magisk.

RootBeer Sample will not find com.topjohnwu.magisk.

RootbeerFresh - PlayStore - Link

RootBeer Sample - PlayStore - Link

Cheers. :cowboy:

PS.

I am not sure why the animation does not run on RootbeerFresh when in split screen. ¯\_(ツ)_/¯

Screenshot from Pixel 5 (Android 12) and Pixel 4a (Android 11).

Both RootbeerFresh and RootBeer Sample are added to DenyList.
[Magisk] pndwal:
Thanks Doc... Fixed my typo: meant SDK 30 of course! ... Your turn; I believe you meant SDK 30 (above) also, not 20. 👍 PW
[Magisk] DiamondJohn:
As I am sure you already understand, the images / layout and theerefore animations are within the APK based on screen resolution. By default, split screen makes the app think its running in landscape and the screen is only half the resolution/density. ie spit screen is two landscape screens of half the resolutioon.
[Magisk] ipdev:
Just keeping you on your toes. :P

I corrected my ytpo.🙃

Google normally refers to changes in Android level by API.

source.android - WebSite - Link

SDK is Software Development Kit.

NDK is Native Development Kit.

Equal to the API level they use.

developer.android - WebSite - Link​

Android 12 = API 31, NDK 31 and SDK 31.

Cheers. :cowboy: