yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Sorry but 2..2.1 is probably the version of USNF module, not the 'SafetNet version'

Best, post the screenshot of your main Magisk app window (to see what is exactly your Magisk app version and Magisk version)

Are you on the Stable, Canary or Alpha Magisk?

Then, do you have Zygisk enabled in Settings - screenshot again (also to show if DenyList is enabled or not - all assuming that you really use the new Canary or Alpha with Zygisk option)

And then the screenshot of your modules to see what is exactly 2.2.1 version and what other modules you might have (maybe in the collision with something - e g., Riru will be in the collision with Zygisk, or if Zygisk is not enabled you must use USNF 2.1.3, not 2.2.1, etc - precise and complete details are very important)
[Magisk] casouzaj:
Since I had given my old Sony Xperia Z5 Compact, running Bernie's unofficial LOS 18.1 build, a hard reset, some time ago, because it was not my daily driver anymore,, it was kept unrooted. Then, I decided to root it. I used the latest alpha build with the latest Shamiko module, along with Magisk's Systemless Hosts module. I configured it to run Zygisk and settled up its deny list (but switched off the 'Force deny' key. After a reboot, YASNAC app showed that both SN tests were failing. Then, I installed USNF 2.2.1 and rebooted. Wow, even Basic Integrity (which is not USNF's aim to be fixed) is passing!

Just my 2 cents!
[Magisk] zgfg:
On one screenshot it says (below the option to enable Zygisk): Reboot to apply changes - and on the other it says Zygisk: No (like it is not enabled since it was not rebooted?)
[Magisk] kramer04:
i rebooted many times but says zygisk not activated
[Magisk] zgfg:
Loks interesting

I'm still on 23018 and not on Samsung

Looks like you have problem with the Zygisk itself (not USNF 2.2.1) - assuming that when you disable all modules and reboot, that Zygisk still shows it is not working
[Magisk] rodken:
Same issue that I've been having with OOS 11 [OnePlus 8] which I suspect could be ROM related or an issue with Zygisk.

Only time will tell as Zygisk moves further in development.
[Magisk] pndwal:
May be a bug.

Did you ever install Zygisk-LSPosed? Either way, may be similar issue (SELinux related?) to this: https://github.com/topjohnwu/Magisk/issues/4961

This Sammy S9 user fixed it by clearing caches:

https://github.com/topjohnwu/Magisk/issues/4961#issuecomment-975821501

(Other issues fixed earlier:

https://github.com/topjohnwu/Magisk/issues/4777 )

Hope it helps. PW
[Magisk] pndwal:
Nb. Issue in my post above was closed by user on assumption it wasn't Magisk's fault...

I'd say it would be worth / helpful to open a similar issue again as it seems it is still affecting various devices... And it appears likely to me that it is a Magisk issue in fact.

Nb. Magisk issues are often assigned / fixed by LSPosed Devs (girls club? 😛) whether in Magisk or LSP. PW
[Magisk] ipdev:
I ran into that issue once.

I do not remember the device or Magisk version.

(Might have been my OnePlus 6T or Poco F2 Pro. :unsure:)​

After updating Magisk, Zygisk would not enable (after reboot) even though it was turned on in settings.

Magisk patched boot image found, patching boot image.​

I wiped Magisk but, that did not solve the problem.

Wiped Data and Cache of the Magisk app and uninstalled it.

Deleted the magisk.db file.

Reinstalled the Magisk app and rebooted.​

I ended up patching the stock boot image clean with the new version of Magisk.

Stock boot image found, patching boot image.​

I am not sure if deleting the magisk.db file did anything to help. :unsure:

Some odd setting that the new version of Magisk did not like?​

Not sure if it will help but, I would suggest patching you stock (current rom) boot image and try again.

Good luck. (y)

Cheers. :cowboy:
[Magisk] zputnyq:
Hi all,

I'm on TJW's canary 23019.

Does anyone know/could explain what is/are the difference(s) with enforce denylist activated and not activated ?
[Magisk] pndwal:
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...

Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
[Magisk] pndwal:
Updated translations just gone in; Italian, Japanese, see PR for French too...

French too hard (French trop dur)?

["The trouble with the French is that they have no word for entrepreneur”.

- George W. Bush

Edit: this may have been mis-attributed to Bush...]

May be stalled on 'missing strings' PR for Catalan, Spanish, Romanian also. 😉

😛 PW
[Magisk] zgfg:
As per Changelog and endless discussion in the thread, DenyList essentially replaces the old MagiskHide. However you have to open Configure DenyList and configure for Google Play Services yourself

1. Enable Zygisk and reboot

2. DenyList and reboot
[Magisk] dohanin:
is it really necessary to add google play services in the denylist? i did not and google services work just fine including google pay and safetynet.

zygisk+shamiko
[Magisk] meric57:
Hello, I tried to make JW with adb I think it must be good. See screenshots put the 2 modules just to know for shamiko you have to do as explained in this topic with explorer root demoted version 72 to 71.

I can flash with odin TRWP 3.6.0_9-0-u3 or I have to modify it with magisk before flashing.
[Magisk] zgfg:
Enable Enforce DenyList and check In Confugure DenyList if gms and gms.unstable processes are checked in. Disable again Enforce DenyList

Maybe enabled from previously, maybe new Shamiko does (or USNF 2.2.1 takes care)
[Magisk] dohanin:
Thanks. In my case, google play services is not checked at all in denylist. And I experienced no differences whether it's added or not.
[Magisk] zgfg:
USNF installed (or some other 'similar' modules)?
[Magisk] dohanin:
yes, USNF
[Magisk] zgfg:
So it takes care
[Magisk] dohanin:
ic. Since I must use USNF to pass safetynet, then I don't need to worry about setting Google play services in Denylist.

Thanks for explaining.
[Magisk] meric57:
Hello dohanin, you are talking about play store certified me it is certified with shimako and safetynet fix 2.1.1.

Just emptied cache and given in application in S10 device parameter, then open play store and these certified.
[Magisk] kramer04:
After many tries and clean all, same issue.

wait until a new update of magisk
[Magisk] dohanin:
yes, zygisk + shamiko + usnf works for me too. and with initrchider, i could pass all tests in magisk detector.

i was clarifying why there is a need to add google play services in Denylist.
[Magisk] pndwal:
... Updated Installation Instruction page... 😛

And French done too!... PW
[Magisk] shadowstep:
It's out now: https://github.com/topjohnwu/Magisk/releases/tag/v24.0
[Magisk] heinhuiz:
</TOPIC>

President George W. Bush said “the trouble with the French is that they have no word for entrepreneur”. Was he joking or being serious?

Answer (1 of 9): This quote attributed to George W. Bush is often cited in discussions about his sense of humor. While it’s widely reported, its veracity is debated. Some claim it was said in jest, highlighting Bush’s reputation for verbal gaffes and humor, while others argue it reflects a seriou...

www.quora.com

<TOPIC>
[Magisk] pndwal:
Just wondering if you tried clearing davlic etc mentioned in issue post?

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86319407 🤔 PW
[Magisk] zgfg:
Show will begin, I tried to put some short help for probably the posts/questions soon to expect

===

Please carefully read Changelog

Study the Magisk documentation available from the official Magisk Github page - particularly about installing Magisk (if you are not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- i.e, not the old school about Magisk zip through TWRP)

Everything bellow has already been discussed in this thread since Canary 2301x started to roll out - hence more details can be found in the older posts in this thread

a) No more MagiskHide. New technology instead (for the same - to help hiding root): Zygisk+DenyList

b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC

c) Modules window does no more connect to the (now frozen) old Modules repository.

You must download module zip files manually and "Install from local storage".

Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository

---

0) Always before upgrading Magisk, go to your Magisk app/manager and if you previously did "Hide Magisk app/mngr", do "Restore Magisk app/mngr"

1) Make sure that both Magisk app and Magisk are installed and updated to the new version. Inspect version numbers on the main Magisk window/page

2) Make sure to uninstall all Riru modules (not compatible with Zygisk)

3) Settings, Enable Zygisk and reboot.

Then check on the main window does it show Zygisk Yes

4) Settings, enable Enforce DenyList.

Configure DenyList, enable filters to Show OS and System apps

Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.

You will have to check in all your banking apps and so as you used with MagiskHide.

Always reboot upon reconfiguring DenyList

5) If SafetyNet does not pass, install USNF 2.2.1 and test again.

Always reboot upon installing a module, also if/when you enable Systemless Hosts

---

Intentionally, I didn't want to complicate with Shamiko for the new Magisk 24 users 👍

PS: See the new thread:

https://xdaforums.com/posts/86321719
[Magisk] meric57:
hello ,updated to 24 more rooting.
[Magisk] kramer04:
Always same issue with magisk 24 canary

Zygisk : no
[Magisk] pndwal:
Guess I can advertise @ipdev's new WIP

[Discussion] Magisk - The Age of Zygisk​

thread now that public 24.0 release is out:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

First 5 posts have a good summation of new Magisk changes / direction / tips. 👍 PW
[Magisk] dohanin:
No, I did not. As said, zygisk + shamiko + usnf works fine for me. I never had to add Google Play Services in Denylist since using zygisk. I'm on Android 12 with stock rom.
[Magisk] pndwal:
Sorry, I didn't correct that post quickly enough; wrong user!...

I meant to ping @kramer04 here:

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

not you. 🤪

But I can add (for you) that before Zygisk based USNF it was necessary to manually add Google Play Services SafetyNet process (and main process w/ Android 11+) to denylist in Canary w/ Zygisk... (Pre Zygisk this happened automatically on toggling on MagiskHide.)

For most users this is no longer needed as Zy-USNF uses its own hiding functions for these processes to target Play Services specifically as explained in USNF GitHub (see changelogs).

It's worth noting that USNF will often fix hiding issues even for devices w/o hardware for HKA (Hardware Key Attestation), ie w/ release versions of Android 6 and earlier, as this solution also adds back mechanism to change sensitive props where needed (formerly handled by MagiskHide). This function is often needed for legacy devices to pass SafetyNet. 🙃 PW
[Magisk] dohanin:
Thanks a lot for the explanation.
[Magisk] pndwal:
Good catch; should be more careful to check sources (don't trust theTelegraph, Mirror UK etc) and be more PC. Clearly the jury's out on that OT quote, so I've edited it...

The French really could use a word for etiquette however... 😬 PW
[Magisk] pndwal:
Latest Official Canary Magisk:

Magisk (e8f31c78) (24001)​

Sync with public v24.0 release

Diffs to v24.0​

None

https://github.com/topjohnwu/magisk-files/blob/caa92b3e43471162a6e84d6419028bbfe661823d/notes.md

👍 PW
[Magisk] pndwal:
Many Chinese Magisk users (incl. TJW collaborators) were expecting new public Beta 24.0 as traditional Chinese New Year present... Looks like John surprised them by releasing this a few days before...

I wonder if public Stable 24.0 / 24.x will arrive by Feb. 1? ...

www.twitter.com/topjohnwu/status/1486284286927859712

😛 PW
[Magisk] pndwal:
One Edit:

👀 😁 PW
[Magisk] vandyman:
Now that there is a new Magisk V24 stable thread.

Will it be it be ruined like this thread?

I really hope not. Who can post the most in the new thread does not count like it does here in this thread.

Sorry for the off topic rant and being an a*s.
[Magisk] pndwal:
Nb. It's a 24.0+ thread, but we haven't yet got stable! 😉

Preventing a new thread from expanding fast has been my concern too, and @ipdev and I have discussed this over the last few weeks (he may have done so with others also).

I can't / couldn't see an easy solution to this for a discussion / help thread... We did discuss a wiki style site / thread to supplement @Didgeridoohan's excellent database of solutions to cover use of new hiding modules and other more loosely magisk related topics / issues... This is what we've got - Ipdev stepped up to maintain it and I salute him for his efforts!

Nb. It will likely help a lot if users read the first 5 posts before asking questions though... The intention is to keep these updated to cover the most commonly needed information...

I don't think that this thread ruined however. It may be burgeoning, but it is / has always been a very valuable resource as a General Discussion thread, especially for those knowing what to search for / how to search... And as long as some who keep up with recent development are happy to help others, it seems to work well for all AFAICS... 😜 PW
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86322549
[Magisk] Homeboy76:
Thanks, I appreciate your help.
[Magisk] RealNBB:
"Updating" from v23 go v24 without any issue. Thank you so much for the new version! :)
[Magisk] heinhuiz:
No, you're right. What might help is when some of the most helpful contributers like @pndwal and @zgfg and others could have rights to simply delete posts.

I mean, what does a post like:

add in the middle of a discussion about hiding Magisk? 🙄

Or would it be better to just report such posts, or (dis)like them with a sad 🙁 or angry 😡 face?
[Magisk] pndwal:
That will be one advantage of the new @ipdev 24.0+ thread; as an active OP he can delete posts / do housekeeping.

With @topjohnwu as OP, this thread relies on moderators to do housekeeping as John is no longer active here... PW
[Magisk] VD171:
I love reports.

But I love more useful discussions.

Just read the description for the latest magisk version and you will see the middle of this discussion.
[Magisk] mrjuniork:
Exactly. People of this thread should report posts, if they deem it necessary and we'll take care of it, as usual.

General info:

No need to make a post about someone else's post being offtopic etc..
[Magisk] pndwal:
Sure... But users should really read OP and subsequent posts from OP (first five in that thread) before asking questions in any XDA thread! Your question indicates that you didn't do this minimum preparation as the basic answer is covered by OP. 😜

Edit: Actually, I may be being a bit tough on you here; It may be a bit unclear in OP's (@ipdev) Opening Posts that Universal SafetyNet Fix is now the defacto MagiskHide(er) solution (allows SafetyNet passing). A better description might help, and you could be excused for not knowing the significance of USNF...

Also, there is no mention yet of Shamiko as a solution to further hide traces of Magisk root including Zygisk, modules, isolated process leaks etc. This may be a supplementary answer to your question. 😜 PW
[Magisk] VD171:
I just want to catch a fire on this, my friend.

If I'm bothering you, I don't care.

Edit: About how hiding root actually?

I've installed Magisk v24.1, LSPosed v1.7.2, Shamiko v0.4.3, XPrivacyLua v1.30 and everything is working perfectly.

I can hide root, xposed and zygisk, using it, please read my reply:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/post-86427499
[Magisk] pndwal:
Edited / reconsidered post above (cos really I do care. - and as mod noted above, there was no need for member to single you out for a mention. And your post was not even Off Topic).

Sorry if a bit tough / quick to criticise. Please check edit. PW
[Magisk] meric57:
Good evening, as I have the blow 2 or 3 times to lose the rooting of magisk following the update.

Is it possible to flash the image of magisk or to create it for flashing, then put the image of the last version on the discussion page on magisk which saw the day yesterday.

How to remove the security message at startup of the smartphone, I can remove it with a patch with TRWP by flashing it, but just with magisk there may be a module that can do it.

Thank you
[Magisk] pndwal:
Latest Unofficial vvb2060 Alpha Magisk

(Chinese Translated):

# alpha changelog

## Magisk (3c7e7921-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [General] Use MagiskHide to hide when Zygisk is closed

- [App] Compatible with Android 12L

- [MagiskInit] Refactor the processing method of two-step startup

- [General] Update to NDK 23

- [App] Added crash statistics

- [App] Fixed some reported crashes

- [App] built-in module_installer.sh

### how to install?

Install and uninstall Magisk through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, you should use the fastboot/odin tool to flash it after patching the image.

By customizing Recovery is not a supported way.

👍 PW
[Magisk] J.Michael:
You can not remove the security message at startup.

Not with a Magisk module.

Not easily.

That message comes from the thing that boots before Android. It is related to the thing that boots Android. It is earlier than anything that can be affected by a Magisk module. It is earlier than anything that can be affected by Magisk.

I do not understand how you can remove the security message with a patch with TWRP. I'm not sure what you mean by "a patch with TWRP".
[Magisk] An68:
Please help me. I want to root my Poco X3 Pro with Magisk 2400, after flash Lineage 18.1 and Gapps,

patch the boot.img, move it not with ADB from SD to the PC, rename to magisk_patched.img,

but after flash and reboot I haven't root .

Where I wrong? Thanks
[Magisk] Rumplestilzken:
I am working on getting the Unihertz Titan up and running with TWRP (from scratch) and Magisk.

I have tried both Magisk v23 & 24. Both show i am rooted by root checkers however both give errors which i need a little bit of help to diagnose.

v23 - In Magisk apk after patching and flashing the patched rom Installed shows N/a. I can run su in adb shell however i get a message saying no daemon is running.

v24 - In Magisk apk after patching with both vbmeta checked and not checked it shows as Installed 24. However, when i used adb shell and try and execute su i am greeted with Permission Denied.

I would greatly appreciate any sort of constructive advice, i have made a lot of progress in the last few days, but i am at a standstill now. TWRP cannot continue development because it cannot mount any partitions and do its thing.
[Magisk] J.Michael:
With version 24 installed, with the Magisk Manager app admitting that Magisk is installed:

What happens if you open a terminal emulator and type "su" at the command prompt?

I do not believe that there is any connection between successfully installing Magisk, and successfully implementing TWRP. I understand that if you had a working TWRP, you would have another way to try to install Magisk. I am saying I do not understand how a lack of Magisk and it's associated "su" is blocking the development of TWRP.
[Magisk] Rumplestilzken:
From a terminal, i am asked to grant permission and it executes as neccesary. Thanks for that avenue.

TWRP works on the EMMC version of the Titan, but not on the UFS version which was release about a year after launch. EMMC users are free to use it, but UFS devices do not allow you to mount anything, the block devices are not registered. The only thing that i could find of use was the sd card. I'm drawing at straws to try and figure out why none of the devices are active. When i saw that su wouldn't run in 24 in adb but gave a different response in 23 i thought i might have stumbled onto something about the root not taking.

I'm thinking potentially the kernel source will have been updated, they haven't released the source yet but are apparently working on preparing it for release.

I did find an interesting build option. BOARD_BUILD_SYSTEM_ROOT_IMAGE, i think the kernel that they built was before they updated the kernel when the UFS devices came out. I have a hunch that once we get the source this will be put to rest but until then, i would like other options.
[Magisk] amk316:
hi

just update my s20 to A12 with magisk 24001 everything work OK

i added safetynet-fix-v2.2.1 and Shamiko-v0.3.0-73-release and they work OK

p.s. "do not add SmaliPatcher it will boot loop"

the only problem i have is when booting the phone on lock screen the phone will reboot in seconds every time, i have to unlock the phone to stop the reboot.

anyone know what i can do to solve this.

thanks.
[Magisk] zgfg:
Upon updating your system, you must run SmaliPatcher again to create new module zip

Still, maybe all patches do not work for your phone and A12
[Magisk] meric57:
Hello,good me
[Magisk] pndwal:
Does issue persist after reboot with all modules disabled?

Did you take A12 update by downloading complete A12 ROM, patching AP with Magisk in old OS, then flashing w/ Odin: patched AP + BL + CP + HOME_CSC? PW
[Magisk] amk316:
Yes disabled all modules, the same.

And yes i did it on the old OS. And flashed it.
[Magisk] pndwal:
I've never seen anyone use MiFlash to install Magisk! 🤔 - Why are you doing that rather than following official instructions (install ADB drivers and flash with Fastboot command)?

Tip: on Xiaomi devices, generally Recovery mode option should be unchecked if it appears as Xiaomi bootloaders are compatible with ramdisk in boot partition and magisk will install one even when OEM hasn't. 😜 PW
[Magisk] jons99:
connect your phone to a pc restart your phone then do adb logcat > logcat.txt in powershell let it log till your phone restart then share your log here you'll have a better chance of resolving your issue
[Magisk] pndwal:
Latest Public STABLE Official Magisk:​

Magisk Changelog​

v24.1​

[App] Stability improvements

🌈👏🎊🥳

👍 PW
[Magisk] SlimShady08:
What happens if you freeze magisk using Link2SD or another app? Will you have to reinstall it from TWRP?
[Magisk] pndwal:
Latest TJW debug Canary Magisk:​

Magisk (32fc34f9) (24101)​

Sync with public v24.1 release

Diffs to v24.1​

None

👍 PW
[Magisk] zgfg:
Please distinguish Magisk app from Magisk itself (patched into the img, data saved under /data/adb)

You can even uninstall Magisk app, Magisk will continue to work but you will not be able to grant new root requests and manage other things like modules, etc - but what was configured will continue to work.

And you can later reinstall/unfreeze the app and continue to use it for managing
[Magisk] SlimShady08:
Oh! Thank you so much for educating me and clearing it up. Cheers.
[Magisk] pndwal:
'Stable' Canary!

😄 🐦 PW
[Magisk] amk316:
her is a logcat during the reboot

thx