Magisk General Support / Discussion

[heinhuiz]

"The trouble with the French is that they have no word for entrepreneur”.
- George W. Bush

</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 6): Pasted from SNOPES: Claim: President George W. Bush proclaimed, “The problem with the French is that they don’t have a word for entrepreneur.” Status: False. “George W. Bush is dumb” story has been taken up by those who like their caricatures drawn in stark, bold lines. Accord...

www.quora.com

<TOPIC>

 

[pndwal]

After many tries and clean all, same issue.
wait until a new update of magisk

Just wondering if you tried clearing davlic etc mentioned in issue post?
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86319407 PW

 

[zgfg]

It's out now: https://github.com/topjohnwu/Magisk/releases/tag/v24.0

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:

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread

forum.xda-developers.com

 

[meric57]

hello ,updated to 24 more rooting.

 

[kramer04]

Always same issue with magisk 24 canary
Zygisk : no

 

[pndwal]

Guess I can advertise @ipdev's new WIP

[Discussion] Magisk - The Age of Zygisk​

thread now that public 24.0 release is out:

[Discussion] Magisk - The Age of Zygisk.

This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...

forum.xda-developers.com

First 5 posts have a good summation of new Magisk changes / direction / tips. PW

 

[dohanin]

Just wondering if you tried clearing davlic etc mentioned in issue post?
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86319407 PW

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.

 

[pndwal]

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.

Sorry, I didn't correct that post quickly enough; wrong user!...

I meant to ping @kramer04 here:
https://forum.xda-developers.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

 

[dohanin]

Sorry, I didn't correct that post quickly enough; wrong user!...

I meant to ping @kramer04 here:
https://forum.xda-developers.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

Thanks a lot for the explanation.

 

[pndwal]

</TOPIC>
https://www.quora.com/President-Geo...reneur-Was-he-joking-or-being-serious?share=1
<TOPIC>

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

 

[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

 

[pndwal]

Latest Unofficial vvb2060 Alpha Magisk
(Chinese Translated):

# alpha changelog

## Magisk (54ee63a4-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

### 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.

# Upstream changelog

It has been a while since the last public release, long time no see! A personal update for those unaware: I am now working at Google on the Android Platform Security team. Without further ado, let's jump right into it!

### MagiskHide Removal

I have lost interest in fighting this battle for quite a while; plus, the existing MagiskHide implementation is flawed in so many ways. Decoupling Magisk from root hiding is, in my opinion, beneficial to the community. Ever since my announcement on Twitter months ago , highly effective "root hiding" modules (much **MUCH** better than MagiskHide) has been flourishing, which again shows that people are way more capable than I am on this subject. So why not give those determined their time to shine, and let me focus on improving Magisk instead of drowning in the everlasting cat-and-mouse game .

### Sunset Magisk-Modules-Repo

Due to lack of time and maintenance, the centralized Magisk-Modules-Repo was frozen, and the functionality to download modules from the repo is removed in v24.0. As a supplement, module developers can now specify an `updateJson` URL in their modules. The Magisk app will use that to check, download, and install module updates.

### Introducing Zygisk

Zygisk is **Magisk in Zygote**, the next big thing for Magisk! When this feature is enabled, a part of Magisk will run in the `Zygote` daemon process, allowing module developers to run code directly in every Android apps' processes . If you've heard of [Riru](https://github.com/RikkaApps/Riru), then Zygisk is inspired by that project and is functionally similar, though the implementation is quite different internally. I cannot wait to see what module developers can achieve using Zygisk!

### Documentation

For developers, details about `updateJson` and building Zygisk modules can all be found in the updated [documentation](https://topjohnwu.github.io/Magisk/guides.html#magisk-modules).

### v24.0 Full Changelog

- [General] MagiskHide is removed from Magisk
- [General] Support 64-bit only systems
- [General] Support Android 12
- [General] Update BusyBox to 1.34.1
- [Zygisk] Introduce new feature: Zygisk
- [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
- [MagiskBoot] Support patching 32-bit kernel zImages
- [MagiskBoot] Support boot image header v4
- [MagiskBoot] Support patching out `skip_initramfs` from dtb bootargs
- [MagiskBoot] Add new env variable `PATCHVBMETAFLAG` to configure whether vbmeta flags should be patched
- [MagiskInit] Support loading fstab from `/system/etc` (required for Pixel 6)
- [MagiskInit] Support `/proc/bootconfig` for loading boot configurations
- [MagiskInit] Better support for some Meizu devices
- [MagiskInit] Better support for some OnePlus/Oppo/Realme devices
- [MagiskInit] Support `init.real` on some Sony devices
- [MagiskInit] Skip loading Magisk when detecting DSU
- [MagiskPolicy] Load `*_compat_cil_file` from system_ext
- [MagiskSU] Use isolated devpts if the kernel supports it
- [MagiskSU] Fix root shell if isolated mount namespace is set
- [resetprop] Deleted properties are now wiped from memory instead of just unlinking
- [App] Build a single APK for all ABIs
- [App] Switch to use standard bottom navigation bar
- [App] Downloading modules from the centralized Magisk-Modules-Repo is removed
- [App] Support user configuration of boot image vbmeta patching
- [App] Restore the ability to install Magisk on the other slot on some A/B devices
- [App] Allow modules to specify an update URL for in-app update + install

PW

 

[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? ...

John Wu, 3h

Published Magisk v24.0

Available on the public beta channel. Will wait for a few days, and if all is good, I'll release it to the stable channel.

Oh and BTW, I have revised the installation guide with additional info and updated instructions.

www.twitter.com/topjohnwu/status/1486284286927859712

PW

 

[pndwal]

One Edit:

John Wu, 1h

Magisk changelog:

Support 64-bit only systems

!= Only support 64-bit systems

I guess I have to change the wording a bit, people are freaking out...

This is better

PW

 

[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.

 

[pndwal]

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.

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

 

[pndwal]

January 26, 2022
New
54ee63a4-alpha

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86322549

 

[Homeboy76]

https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86322549

Thanks, I appreciate your help.

 

[RealNBB]

"Updating" from v23 go v24 without any issue. Thank you so much for the new version!

 

[heinhuiz]

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.

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:

Any magisk hider, please?

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?