yashsingh1/xdaforums huggingface dataset:
[Magisk] ldeveraux:
It was a hypothetical question; one we all already know the answer too. The point is many people were upset when this transition was announced because something worked great for them and was changed. Sure I don't have to upgrade, and I won't because magiskhide works 100% for me, as it does for most people. We all know why TJW stopped development of magisk and it had nothing to do with the app. This just seems like a regression or at best a lateral tech shift.

ninjaedit: Why in the world is this still considered a version number upgrade from Magisk when they are essentially different apps? Why not just call it the Zygisk app or whatever you're calling it and offer it as a version 1.0 separate entity? Maybe that would confuse people less and you wouldn't have to answer the same question repeatedly.
[Magisk] nacos:
Could you please check my last post #85 (link below). I would appreciate any suggestions. Thanks!

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86335653
[Magisk] zgfg:
SafetyNet uses Google Play Services (GMS). AFAIK, you cannot substitute GMS with MicroG

Maybe it was possible way ago, but not now - GMS communicates with the Google servers. Communication is authenticated by PKI. MicroG or nobody else could sign with the private key of Google Play Services, hence Google servers would immediately know they don't talk to GMS

API error actually means that SN communication is broken.. I doubt that MicroG even provides SN API (knowing that it cannot spoof Google's backend part for SN). Hence your API error probably means that SN checker cannot find GMS and its SN API
[Magisk] nacos:
Makes sense. The interesting part is that under Magisk v.23, although clearly I also wasn't passing SafetyNet, I was able to use all banking apps that currently no longer run. This tells me that Magisk's previous built-in hiding mechanism worked, while Magisk's v.24.1 external hiding mechanism doesn't - unless it passes SafetyNet - which is likely the only hiding mechanism.

Anyways, I truly appreciate your help. Thanks a lot.
[Magisk] tom1807:
No idea what kind of sorcery this is, but I got yesterday my Pixel 6 and this Zygisk is pretty awesome.

Not only work now bank apps again, which still detected root, despite being properly rooted on my previous mobile and passing SafetyNet, but most amazing, DRM Info shows, that I am in Widevine CDM on security level L1.

Pretty amazing.

Cheers

Tom
[Magisk] mingkee:
How did you setup compared with 23?
[Magisk] tom1807:
I followed this guide, worked like a charm.

Cheers

Tom
[Magisk] bgsdeluxe:
Anybody with Magisk v24 or v24.1 and safetynetfix 2.2.1 and Google Play Services added to hidelist could do me a favour and check, if Play Store is still present in this list after a reboot, please? (Yes, I ticked "show system apps" ;) )

Thanks, highly appreciated.
[Magisk] tom1807:
Yep, still present

Cheers

Tom
[Magisk] bgsdeluxe:
Thank you! I meant to ask for Play Services, not Store.

Are you running A12 or an older build?

Another app (non-system app) I added is still in hidelist only Play Services isn't surviving reboot. That's due to Magisk Hide not enabled?
[Magisk] mkcs:
I received this error even though Zygisk is enabled and UNSF are installed
[Magisk] FlashPlayer13:
Hi,

I am looking for proper setup for my android device with magisk.

My goal is to use remote control on device (like scrcpy) but completely hide this fact from target app. I am assuming that my target app has lot of checks to prevent such things like remote control.

So i need to hide this things:

1. That adb is enabled (and that developer options are on)

2. That usb is connected (and any hint on this like charging)

3. Presence of Magisk

4. Presence of root (if root is needed for my purpose)

MagiskHide looks like one part of full picture, but i am not sure what i need more.

Thank you for advices.
[Magisk] J.Michael:
Have you tried running the target app?

Does it really refuse to run if you are connected to a charger?
[Magisk] FlashPlayer13:
No it doesn't refuse. But this is a bookie app and I don't want to risk my deposit if I am not sure that all is secure this way.

Thats why my questions are here. I am afraid that app will see magisk or root or adb presence and in summary with other flags will block account or restrict it somehow. So looking for a clean way.
[Magisk] Revan335:
Why 24.2 not pushed to Auto Update Notification in the Magisk App?

I have 24.2 from GitHub but in the App is the newest Version 24.1.

F-Droid/Privileg Extension have no Root Notification for Magisk. He is not listed in the Superuser List in the Magisk App.
[Magisk] hjjiang:
Seems like 24.2 is still in beta, if u change to beta updates u will see it
[Magisk] Revan335:
OK, Sorry! That was not apparent on GitHub. There it is listed as Release/Latest Release like the 24.1. Without beta tag.
[Magisk] zgfg:
I see clearly that 24 2 is BETA

Screenshot from Github

Also, in your Magisk app, go to Settings page, and switch Channels update

Put to Stable, return to main view, read that Latest is 24.1

Go back to Settings, choose Beta or Canary, go back to main window, Latest says 24.2.
[Magisk] Prof_Shekhar:
@zgfg @pndwal @xabu

I recently upgraded my Magisk Canary version from 24.1 to 24.2, without any issues except some of the banking apps are now detecting OEM open lock and hence refusing to work. LSPosed and Hide My Applist are still enabled but unable to prevent one of the banking app from detecting unlocked OEM.

Has anyone of you faced similar issues recently? If yes, Would love to hear from you.
[Magisk] zgfg:
Hide My Applist hides applications - neither Magisk (as 'mask' or 'service') nor unlocked OEM are any installed application, hence no use of HMA there

You should put your banking app to DenyList (and reboot) but if it says that it detects OEM Unlock I don't believe it could help

On some phones you could keep Bootloader unlocked (locking BL would cause hard reset on most phones, resulting with uninstalling Magisk or even bricking the phone if you don't manually revert Boot and Recovery before) but by disabling OEM unlock.

Seems that eg I could disable OEM unlock on my Xiaomi by keeping BL unlocked

However, by disabling OEM unlock you also make it impossible to flash from Fastboot. Hence, it's risky - in case of bootloop you could not flash/unbrick and you could not either boot to enable OEM unlock (to be able to flash)

Maybe the app is detecting USB debugging - you could try disabling it but then similarly, you affect adb
[Magisk] Prof_Shekhar:
@zgfg @ipdev @pndwal

Thanks @zgfg for your detailed reply.

You are right. Neither the Magisk deny list (with enforce dent list) nor Hide My Applist is able to prevent OEM unlocked state detection.

Also as you rightly said that if I lock the OEM, the system reboots automatically bricking the device.

Turning off the debugging option doesn't help the situation. I understand it's a catch 69 situation.

But surprisingly, the Magisk was able to hide the OEM unlocked status with its earlier version i.e. 24.1 and hence this particular banking app was working well.

As only one banking app has stopped working whereas other banking apps are still working, I have uninstalled this particular banking app. Will wait for someone is to find a solution for this issue.
[Magisk] zgfg:
1) I said that on my Xiaomi I could disable OEM unlock without relocking Bootloader, without forcing Factory reset and/or bricking the phone

I just disabled OEM unlock and no bomb exploaded. However, I didn't want to test/risk with rebooting - I enabled OEM unlocking again with no problem

But on the other phones disabling OEM unlock may trigger relocking BL, Factory reset, etc

(Also, I would not like to have OEM unlock disabled, even by keeping BL unlocked because if anything, anytime - maybe two months later, for any reason - maybe by my mistske when updating TWRP, Magisk, who knows - goes wrong I'd be in trouble since I would not be allowed to flash/unbrick from Fastboot)

2) Are you sure that with Magisk v23, that same banking app would not detect OEM unlock - maybe their new version now also looks for OEM unlock

On the other side, did you try with USNF 2.2.1 (although I don't believe it could help you for the case)
[Magisk] Prof_Shekhar:
Thanks @zgfg

I agree with you that on sone devices, locking OEM option may not trigger bricking of the device. However, it is stark reality with the Samsung Galaxy Note 8. I have once bricked the device while trying to see what happens after OEM lock is enabled again.

Also as you said, USNF is not of much help here.

As far as your question about the previous version of Magisk 23.1, I had no issues with this HDFC Bank app.

Earlier, when I had this same issue wherein the HDFC bank apl refused to work stating that device OEM is unlocked,, I used LSPosed along with the Hide my Applist to overcome this issue.

However after the recent Magisk update, this workaround no longer works.

Wondering what could have gone wrong.
[Magisk] dohanin:
Hi, I am curious and tried the HDFC Bank app. If I don't do anything, it shows "App doesnot support rooted device" and ends. Then I added it to the denylist (I'm using Shamiko), and then it passed.
[Magisk] zgfg:
Again, HMA hides applications, not the fact that your OEM is unlocked.

Therefore, I don't see any way it ever helped you (with Magisk v23) to hide the fact that OEM Unlock was enabled

Besides, banking apps usually don't say what they detected, they just say that phone is not safe, or phone is rooted, or something

Hence how are you sure that your banking app is really complaining about OEM unlock (there are zillion other things it could be detecting and telling then that phone is not safe)

Plaese post your screenshot showing that your app really complains about OEM unlock
[Magisk] zgfg:
Exactly. Banking apps do not say what exactly they found (it would be counter-productive), and so far I don't recall any app where the verdict was - that app complains exactly because of OEM unlock is enabled)
[Magisk] Prof_Shekhar:
Which version of Magisk are you using? Is it Canary 24.2?

@zgfg

I am attaching herewith a screenshot of the message displayed by the HDFC bank after it is put under deny list.
[Magisk] Prof_Shekhar:
@zgfg , @pndwal , @ipdev , @xabu

Finally, managed to resolve the HDFC bank issue (Hope so).

Turned off USB option and the banking app started working.

Not sure if my device would not throw some more unexpected surprises.
[Magisk] J.Michael:
Did you understand what @zgfg said about the downside of turning off USB-debugging?
[Magisk] heinhuiz:
It's not really a downside of course. You can always turn it on again when needed.
[Magisk] zgfg:
Let's please do not mix USB debugging and OEM Unlock

These are different and independent switches in Developer options - screenshots attached

You can safely turn off USB debugging (it will not affect Bootloader, it won't trigger Factory reset or anyting)

However, without USB debugging you won't be able to use ADB - that's the old 'problem' with
[Magisk] zgfg:
Ok. But

"USB Debugging"

NOT EQUAL

"OEM Unlock"

See also post #1001

Completely different options for different things (you started the story that your bankinhg app detects OEM Unlock and that with Magisk v23 use of HMA spoofed that - now it turned out that it was completely differnt problem and different fix)
[Magisk] zgfg:
So again, app complains about USB debugging (bicycle), not about OEM Unlock (boat)

Bicycle is not a boat. It's important to precisely declare the problem, otherwise we all waste the time - you just needed to read their instructions to disable USB debugging and you would be ok yourself 😔
[Magisk] HippoMan:
I'm sorry ... I couldn't resist! :)
[Magisk] Prof_Shekhar:
@J.Michael

Yes. I am aware of the downside of the turning off USB Debugging. But I don't think that there are any harm of keeping it turned off till the time I need to use ADB commands.

My BL is still turned on.

@zgfg

I apologise to you for mentioning that it was an issue with the BL whereas it was an issue with the USB debugging. It was clearly due to my oversight.
[Magisk] Prof_Shekhar:
@zgfg

Yes. You are right.

I was clearly wrong. Getting old 😁.

Once again, thanks for everything
[Magisk] pndwal:
... and in case you're still getting in a flap, altering some earlier developer options may help too...

😁 PW
[Magisk] VD171:
Deny list is NOT similiar to magiskhide.

Deny list does NOT hide magisk or root.

Deny list does NOT "unload" magisk by itself, you need enable enforce deny list too, but it's totally NOT recomended.

Enforcing deny list just doesn't apply magisk changes to the app/process.

Even with "magisk unloaded" there are ways to detect magisk and root.

So, yes, yet there are things to hide.

This is wrong:

The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
[Magisk] exis_tenz:
If any one might want to help... I'd appreciate any! I am using the CUPRA Connect App (Version 1.6.2). It's the same app as Volkswagen Connect, SEAT Connect and probably other apps from the VW car group.

Basically it gives your phone the option to control your car from remote (for example: open, heat, cool, lights off, close, that kind of stuff). Unfortunately this app keeps detecting that I am rooted (had a Volkswagen before wih the same "problem" and now my Cupra/Seat is the same). Allthough you are rooted they let you use the app, but with very limited possabilities (just many options not available).

I don't care what they think, I want to be able to use the app. Anyone who wants to try can freely download the app from the store, because the root-warning appears way before set-up of the app. If asked for a modell it's a Leon and it's after December 2020. The set-up for my phone is:

- Stock A10 (OnePlus 7 pro)

- Rooted with Magisk

* Zygisk

* Cupra app on deny-list but deny-list not enforced / activated

* Shamiko running

* Universal SafetyNex Fix 2.2.1 installed (I -DO- pass!!!)

* Zygisk LSPosed

--> in LSPosed have XPrivacyLua activated and blocked add-info and whatever more sounds reasonable

Turning off USB-debugging doesn't help either. I've tried HMA but it didn't help (so removed). My banking apps work without trouble, this is the only app making problems.

Does any one have any ideas how to get along this (tough) app, happy to hear!
[Magisk] pndwal:
Wouldn't hurt to upload / link it...

... Thought we were ahead down under.... Perhaps it's a Volkswagen bug...

Also, did you select Hide the Magisk app?... PW
[Magisk] exis_tenz:
Hi PW, here's a link (fetched the file with APK-extractor so I hope it works): Cupra App

No, the only thing I did NOT do is hide the Magisk app. Things is (using Apex Launcher 3.5.something) that creating shortcuts does not work, so I've always tried to avoid that. Just like LSPosed, I am not able to create any kind of accesability to it via my appviewer or homescreen whatsoever. Of course, if that is the solution I will.
[Magisk] Stillhard:
119.0 MB for an app? amazing
[Magisk] zgfg:
With DenyList, HMA and even with Magisk App frozen, Cupra detects.

I didn't bother with Hide Magisk app

But I see, the app offers "Do not ask again" and "Continue anyway" hence I'm not sure if that root detection is really a showstopper for using the app (I don't have Seat and cannot judge further)
[Magisk] VD171:
Before:

After:

About how hiding root actually?

I've installed Magisk v24.2, LSPosed v1.7.2, Shamiko v0.4.4, XPrivacyLua v1.30, Universal SafetyNet Fix v2.2.1 and everything is working perfectly.

I can hide root/xposed/lsposed/zygisk and fix safetynet, using it, please read my reply:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/post-86427499
[Magisk] pndwal:
After what?

I get this too by continuing after 'root' detection... Detection occurs even w/ Magisk app uninstalled, so there's a more sophisticated detection occuring...

I'd install Momo (put in denylist also) for clues re. traces etc detected. Eg, we get 'Bootloader unlocked' on MIUI, while users of other devices can bypass this detection easily...

He said:

Sorry not much help, but may give clues... PW
[Magisk] VD171:
About how hiding root actually?

I've installed Magisk v24.2, LSPosed v1.7.2, Shamiko v0.4.4, XPrivacyLua v1.30, Universal SafetyNet Fix v2.2.1 and everything is working perfectly.

I can hide root/xposed/lsposed/zygisk and fix safetynet, using it, please read my reply:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/post-86427499
[Magisk] Stillhard:
Magisk + Good old Shamiko v0.2.0-59 + USNF + LSPosed + own xposed module

Result:
[Magisk] pndwal:
Yes, most here are well aware of all these measures and use them in some combination.

However, we are able to get your 'after' screen even after 'root' is detected, so this is no proof of bypassing detection for this app...

Please say if you managed NOT to get this as initial app screen:

If so, how? 🙃 PW
[Magisk] VD171:
Does NOT exist shamiko version 2. It is beta only, so there are only version 0.

Like v0.4.3 and v0.4.4.
[Magisk] VD171:
Did you see my attached screenshots?

The root detection can be bypassed easily.

I did it easily, just see the attached screenshots.

And read my explanation and good luck.
[Magisk] pndwal:
Yes, just wasn't clear if this was 'after' selecting 'continue anyway', which gives same result... PW
[Magisk] Stillhard:
Oh yes, sorry, missed the 0, Shamiko v0.2.0-59

Thx for the correction, post corrected
[Magisk] VD171:
No, I didn't selected 'continue anyway'.
[Magisk] pndwal:
Well done...

Just downgraded Shamiko to 0.2.0 (59) and still not working on Xiaomi Redmi Note 8T... What is 'own xposed module'? PW
[Magisk] VD171:
Downgrading any Magisk module is TOTALLY NOT RECOMENDED.
[Magisk] pndwal:
Thanks, n well done too, but what is your device?

Why not for experimental / testing / debug purposes? PW
[Magisk] VD171:
Xiaomi Redmi Note 9 using MIUI V12.5.3.0.RJOMIXM.

I mean for daily usage.

Modules like shamiko, you should use the latest version only.
[Magisk] pndwal:
Ta. So seems one or other LSPosed module may be the answer for user...

Out of curiosity, are you able to bypass 'bootloader Unlocked' detection in Momo?

Ah... Ok. But this is not about daily use of course... It's about testing a fix for a Magisk user... PW
[Magisk] VD171:
You can bypass "bootloader unlocked" on mediatek devices just following this:

1. Unlock bootloader.

2. Backup the partition seccfg.

3. Relock bootloader (or just erase the partition seccfg).

4. Backup anything you want to backup and then, Format data.

5. Flash the partition seccfg with unlocked bootloader.

Done, now your device is unlocked but the system thinks it is locked.

(Yes, I did it.)
[Magisk] VD171:
Screenshots for proving it:
[Magisk] pndwal:
Many thanks for the useful tips! 👍

Can you say why this works? Is seccfg initially seeing bootloader still locked?

Are you able to get 'Totally Happy' Momo app result with this? PW
[Magisk] VD171:
Once you unlock the bootloader, many settings are written to the userdata and nvdata.

But, Seccfg is read at the moment of the boot, only.

After the device is ready, no one can read seccfg again.

So, if you use the "locked nvdata" and the "unlocked seccfg", your device keeps unlocked and the system keeps thinking it is locked.

(SECCFG for mediatek devices and DEVINFO for snapdragon devices.)

What is this? Please, send the link.
[Magisk] pndwal:
I'll try to get my head around this! 😜

Any recommended documentation?

"Momo is the strongest detection app known." Canyie.

Canyie's Shamiko follows vvb2060's Momo...

And I posted this in Shamiko early days:

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

👍 PW
[Magisk] VD171:
Yes, the replies I've sent :-)

I discovered it by myself.

This is a just debug app and not an app for usage.
[Magisk] pndwal:
Ah... Nice share 👍

Yup... Please show your result! 😜 PW
[Magisk] VD171:
You are welcome. Please, enjoy.

It was not the intention but I discovered it by myself and works perfectly.

Android mix and splits settings too much, so, you can backup/restore unlocked seccfg for mediatek devices (or devinfo for snapdragon devices) and you can backup/restore locked nvdata too.

Obviously it detects everything, because this is the porpoise of the app.

The app has same developer of LSPosed.

He is just saying "be careful, it can be detected".

But detections are not so clear, it just see something wrong, I mean, different than the original created by Google.
[Magisk] beeshyams:
Thanks @VD171

And how exactly does one go about it please?
[Magisk] vandyman:
WOW!

After reading the last two pages to keep up with all the rant. I have learned not to buy a Volkswagen. And if I want may phone clean and smelling good. install the shampoo module.

Thanks... Keep the good info coming.. Lol..
[Magisk] dr4go:
Uhm, very interesting, although I doubt that would work on a Samsung... maybe I'll get the hands on a second one so that I can try it there... (I don't want to reinstall everything just to try, unlocked bootloader, encrypted data)
[Magisk] pndwal:
👍🤪

Well, one of... Main Dev seems to be Shana... Many in this club... Some boys?? vv is Main Alpha dev & prolific Magisk contributor however...

She

Sure. But banks may (do) use same (especially Momo) techniques to detect... If bootloader unlock is properly hidden, Momo should not detect this either if added to denylist... In fact it doesn't for many OnePlus, RealMe and other devices w/ Shamiko, out of the box ... Seems to be an especially difficult feat for MIUI devices however... PW
[Magisk] pndwal:
Need to ask VD171 if unsure of anything; it's not my method. 😜

See:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86539769 PW
[Magisk] VD171:
It works on mediatek devices which are locked/unlocked using the seccfg partition.

Paid softwares just cracks the seccfg to allow instant unlocking.

(SECCFG for mediatek devices and DEVINFO for snapdragon devices.)
[Magisk] VD171:
Now I'm sure they should use photos instead of animes ♥️

Some detections are excessive.

This means that you can decrease the goal for less than 10% of people, if you apply them.

If banks apps applies new detections, then the excess becomes plausible.

As @topjohnwu said, it's a cat-and-mouse game.

Root is God.

And Linux Kernel is open source :cool:
[Magisk] VD171:
The goal is simple:

You just need the device "clean and smelling good", I mean locked/unrooted.

And then flash the "unlocked seccfg".

The device will be unlocked, but inside the system, it keeps locked.

Just see the screenshots :)

PS: The unlocked state resides in seccfg if read by the bootloader. But, the unlocked state resides in nvdata if read by the system. Nvdata includes too: baseband, IMEI, MAC and other settings like developer settings. I suggest a clean nvdata instead of just relocking bootloader. I don't suggest you to play with nvdata, because it is really confusing.

PS: The partition is SECCFG for mediatek devices and DEVINFO for snapdragon devices.

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86539817
[Magisk] VD171:
More screenshots for proving it:
[Magisk] J.Michael:
If "The unlocked state resides in nvdata", then why does flashing the seccfg captured during unlocked state accomplish anything?

How is it you are able to flash the seccfg captured during the unlocked state while the bootloader is locked?

Are "nvdata" and "seccfg" partitions in your device's firmware files? (I don't see any sign of them in a Samsung release.)
[Magisk] HippoMan:
s/Some/Most/

OOPS! Correction:

s/Some/All/
[Magisk] VD171:
I'm sorry.

I mean, the system reads the partition nvdata to check if bootloader is locked or unlocked.

(It is just like checking if some string is true or false).

While bootloader checks the partition seccfg for mediatek devices and devinfo for snapdragon devices.

(Here, the device can apply some restriction if it fails to check the unlocked state.)

Using spflashtool.

I mean, writing directly to the EMMC.

I'm not sure Odin can do that.

Obviously, no. Nvdata, seccfg and devinfo are sensitive partitions.

I will reply with Samsung partition's table.