yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yup... Implementation of Microsoft Appcentre... Put something about that here:

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

... and the moon landing...

If you're paranoid you'll likely disagree... And believe they never got to the moon... 😜

Better avoid Canary also if this pull request matures (currently has conflicts to resolve) / blasts off:

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

Plenty of stuff there from naysayers also. vv's comments here:

https://github.com/topjohnwu/Magisk/pull/5291#issuecomment-1023630285

and:

https://github.com/topjohnwu/Magisk/pull/5291#issuecomment-1023630285

👀 PW
[Magisk] trojblue:
So you're saying anyone who has questions on a literal discussion thread are conspiracy theoriests. Good to know.

Funny how a comment about the privacy thing is a terible stance is literally below your quoted link.

I switched to magisk stable after alpha breaks on 12L btw. So yes, I'm not using canary
[Magisk] pndwal:
Mate, I never said that! The range of views here is broader than in politics: far far left to far far right... and I'm apolitical! 😜...

I said 'if you're paranoid'... My linked point about the moon landing was in regard to Telemetry being essential for that feat... unless one does dispute that it happened...

Really, I was being flippant there; never intended to or implied that you were either paranoid or a conspiracy theorist!... I post alot and like to joke around sometimes when providing technical info...

Mate, that's why I linked / mentioned both vv's stance as well as the 'naysayers'!... Its not funny, just thought you might appreciate seeing the comments contemporary with vv's implementation of appcentre and pull request for Magisk master (in January), both left wing and right!

I'm leaning towards the devs position for reasons I've mentioned, but don't put too much stock in my comments... 😁

Good for you. PW
[Magisk] Homeboy76:
alpha changelog

Magisk (79f0f323-alpha)

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [App] Added crash statistics

- [App] Allow loading zygisk modules

- [General] Signature Verification

- [App] Fixed some cases where su requests do not respond

How to install?

Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool.

By customizing Recovery is not a supported way.

Upstream changelog

Magisk (63a89d9f) (24306)

- [App] Fix incorrect superuser snackbar text

- [MagiskInit] Improvements to sepolicy hijack

- [MagiskInit] Use `LD_PRELOAD` on 2SI init to assist hijack

- [MagiskInit] Support Oculus Go

- [MagiskSU] Fix a possible crash in `magiskd`

Diffs to v24.3

- [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

- [MagiskInit] Introduce new `sepolicy` injection mechanism

- [MagiskInit] Support Oculus Go

- [App] [MagiskSU] Properly support apps using shared UID

- [MagiskSU] Fix a possible crash in `magiskd`

- [Zygisk] Fix function hooking on devices running Android 12 with old kernels

- [BusyBox] Add workaround for devices running old kernels
[Magisk] pndwal:
Canyie (April 7):

"This group name is a bit NSFW bad"...

April 9

She just changed her Alpha discussion group name again, to:

派對咖 西大師 (Party Cafe West Master)...

... another fix incoming... PW
[Magisk] pndwal:
Canyie (April 10) just changed her Alpha discussion group name again, to:

西大師 家家酒

🤔 PW
[Magisk] zgfg:
From West Master Tits, turning out there're no tits (her own words), etc - it speaks everything by itself
[Magisk] HippoMan:
"West Master Family Wine" ?
[Magisk] pndwal:
Seems less a ref. to wine / liquor, more a ref. to a pop song about love not being a 'house game' ...

https://lyricspinyin.com/2020/04/09/jia-jia-jiu-家家酒-by-家家-jiajia-pinyin-lyrics-and-english-translation/ PW
[Magisk] pndwal:
Canyie's group allows pasting / forwarding again... Standard TG client translation should work again... PW
[Magisk] pndwal:
FWIW, she's still only about 18. A bio / blog is here:

https://blog.canyie.top/2022/01/09/end-of-2021/

... bit there about Shana's (LoveSy) split with her sister (EDXposed --> LSPosed saga) also ('soy sauce')... PW
[Magisk] Homeboy76:
<deleted>
[Magisk] zgfg:
TG channel that pndwal refers to is also about that Magisk Alpha by vvb2060 - not about any other Alpha 'fork'.

And afaik, it is the only (TG) discussion/support group for THAT Alpha - or at least the one where the Alpha developer(s) participate

In the old days, the name of THAT TG channel was in English, Alpha was in the name and vvb2060 herself was one of the admins who (rarely but she did) participate in the discussion (but she was probably more busy with other things than to keep up with hundreds of posts a day there)

And Canyie herself (maintaining THAT TG channel for Magisk Alpha discussion/support) is also one of developers helping/participating to vvb2060 in THAT same Magisk Alpha project (not any other Alpha 'fork')

Hence it is all about the one and the same Alpha (that vvb2060 usually releases through her other, but only RELEASE TG channel, and very rarely, only kind of stable versions, through GitHub)

But I agree that discussion about the ever changing name of their TG discussion/support TG channel is kind of off-topic

But anyway, and please don't take me wrong, what is the real purpose of this XDA thread - so far I didn't see a real discussion about using the Magisk Alpha, questions and answers about the issues with, or something like that

Probably because there are maybe only a very few Alpha users here (all the other ones discuss through that TG channel).

But ok, the initiative was good, to off-load the general Magisk thread from posts about the Magisk Alpha
[Magisk] Homeboy76:
Thank you for providing the history of Magisk alpha., I modified Post #33.
[Magisk] pndwal:
But it is the same Alpha Magisk mate!

This is the group know up to two days ago as Alpha 讨论组" (Alpha discussion group), with an invitation link from the main release thread, lately in one of only two pinned messages (ie. the one linking a Rick Astley song, but hidden).

It is also the best source of Alpha information and fix-progress (various) as many devs (LSP and many more) contribute... As OP here you should know this.

Canyie is senior admin there, and this group links all the Alpha builds in the release thread. The earliest Shamiko builds are released there also, which may account for making the group's scope broader than alpha discussion...

I don't know of any other 'alpha Magisk' TG discussion groups; you've got me there 😝. AFAIK, this is the only definitive linked discussion, although it seems to be changing in nature...

Canyie, like vv, is a prolific contributor to TJW Magisk, they often co-author commits, and some Alpha releases often showcase her work; She often (daily sometimes) asks for logs from Alpha users and produces fixes in canyie magisk fork which are also often built in vvb2060 (alpha) magisk before merged by TJW...

It's worth noting that, just as Shamiko is a Canyie initiative now supported by LSPosed Devs, Alpha Magisk is a vv initiative supported by many LSPosed Devs also. There are some 56 contributing Devs besides LS (Shana), but only 5 main Devs including LS, vv and Canyie...

😬 PW
[Magisk] pndwal:
I don't recall bringing that up here at all, but if there are further changes per John's request that the name be changed, are you saying we can't mention it here?! PW
[Magisk] Homeboy76:
That post was edited!
[Magisk] pndwal:
Ok, re 3rd edit:

Has this been discussed here??

If they are interested in the content of TG Alpha Discussion group, why can't members be made aware of which group it is, ie. it's current name?... Are you giving thought to your posts here?? 😬 PW
[Magisk] pndwal:
Yet it still says:

Why? ... Surely if that changes you'll be needing to change the name of this thread to match! 😛 PW
[Magisk] rodken:
Confirmed that the app freezes when initializing.
[Magisk] WhoIsJohnGalt1979:
Thanks for confirming that. Since the source is not open, the developer of that app also has no clue what to fix. I would stay on 26301.
[Magisk] WhoIsJohnGalt1979:
Version bb39a524-alpha (26302)

Oct 24, 2023 at 11:30

12.49 MB

DOWNLOAD: https://install.appcenter.ms/users/vvb2060/apps/magisk/distribution_groups/public

Alpha changelog

Significant behavior change: magiskd is now in a standalone mount namespace, which is also the global mount namespace for su. Most su use cases will not be affected, if you need to mount the namespace in init, change it to su -t 1.

Major behavior changes: The magiskd internal mount point is hidden from the outside world and uninstalled after it is no longer in use.

Magical (bb39a524-alpha)

[App] Delete the backup file after restoring the boot image

[General] does not automatically unlock the device block

[App] does not actively request permission

[General] Keep ROOTOVL temporary files

[Zygisk] Unmount mounts do not skip com.android.systemui

[App] Check for and download updates through AppCenter

[App] 添加遥测 https://t.me/s/magiskalpha/473

[General] Rewrites MagiskHide with logcat implementation. Do not enable this feature on devices with abnormal logging systems.

[General] 移除addon.d支持

[General] Hide and clean up magiskd internal mount points

[General] To remove the writeable exception for /system/etc/hosts, modify /data/adb/modules/hosts/system/etc/hosts

[Zygisk] refactoring loads in a similar way to riru

[MagiskSU] supports removal of powers

[General] supports user restriction of root privileges [applications using older versions of libsu will be incorrectly identified as unrooted].

[App] Update the DoH server

[General] The safe mode no longer mounts su to /system/bin/su, and the adb shell uses /debug_ramdisk/su

[Zygisk] fix fd cleanup logic

ALso, Shamiko has been updated to the attached file in the alpha TG group

This new 26302 update fixed all the issues I was facing using the previous 26302 update @pndwal
[Magisk] pndwal:
Still, I'm now getting extra detection:

Previous Alpha 26301...

Alpha 26302(b)

🙃 PW
[Magisk] malcolmy:
What happened to the Magisk Alpha repo on Github? Why is archived? And why is the telegram channel posting spam about Bitcoin? What happened to the developer?!
[Magisk] sawdoctor:
For all i agree the repo and source code should be published look at it the other way. If we can read it so can Google and then block anything.
[Magisk] malcolmy:
The Alpha dev archived the Github repo, thus breaking another very needed repo we use to build our kernels for out devices:

GitHub - CruelKernel/samsung-exynos9820: Unified kernel tree for S10 and Note10 devices

Unified kernel tree for S10 and Note10 devices. Contribute to CruelKernel/samsung-exynos9820 development by creating an account on GitHub.

github.com

Anyone know the guy or how to contact him?

I can't build a kernel now with the latest Magisk Alpha.
[Magisk] malcolmy:
@pndwal

Thanks a million for the details. I guess Github creating issues for Chinese users explains a lot.

1. This link gives a 404:

https://github.com/LSPosed/Magisk/commits/

2. Kernel:

On my device (Samsung S10) I have two options with a custom ROM: patch recovery or patch kernel. With patching recovery you would have to use key combination to boot into rooted system, with a patched kernel you press the power button like a normal sane person :). Patching the kernel boot.img inside the Magisk apps doesn't work, so you would have to build it and include magisk binaries in the build. All of this is way above my paygrade so I use Cruel:

GitHub - CruelKernel/samsung-exynos9820: Unified kernel tree for S10 and Note10 devices

Unified kernel tree for S10 and Note10 devices. Contribute to CruelKernel/samsung-exynos9820 development by creating an account on GitHub.

github.com

From that repo and other forks I can build kernels for my device that include: Magisk, Magisk Alpha, Magisk Delta and Kernelsu. Along with other kernel modification that are easy to do, even I can do it. I think you can even build a kernel that includes both Magisk and Kernelsu but I haven't tried it yet.

If you know of a simpler way to root that takes care of the following please let me know:

- Can use custom ROM and not limited to official Samsung firmware

- Can boot phone with power button alone without the need to use key combination

I have been using Magisk-in-kernel for years, it's fine. The only problem is updating which has never been straightforward for years anyway.

P.S.

Can you help me get a static link for app-release.apk, I'm trying to include it in a build but I have no idea how to get that link.

App Center

install.appcenter.ms
[Magisk] pndwal:
Yup... Cos it's not public! 😜

Very interesting project...

Obviously with no bootloader support for ramdisk in /boot, regular Magisk other than in /recovery is out of the question...

Please correct me if I'm wrong, but this approach seems to be exactly what KernelSU does, avoiding the need for magiskinit to replace standard init in ramdisk, so it works in boot.img as kernel is patched which resides there...

Guess you could look into using KernelSU... It's build for GSIs, but while

https://github.com/tiann/KernelSU#compatibility-state

Might need to use custom ROM as seems stock kernel is only ver 3.9... are any 4.14+ ported for S10?

Won't need any ramdisk same as Magisk in cruel kernel I guess...

😆

This?:

https://github.com/vvb2060/magisk_files/raw/alpha/app-release.apk

🤠 PW
[Magisk] malcolmy:
Thanks, the last link is the previous version, not the current version (bb39a524-alpha). Anyway what I did was upload the file to my fork and link that in the script. It worked. I was asking about a static link for the download link in the NEW page for Alpha, here:

App Center

install.appcenter.ms

I hope you can find it, or find a way to include a dynamic link for that the update script can find the latest release whenever it's run. (update script as a part of building the kernel)

Re: Kernelsu

It does not support my phone, even though they claim they're a github repo supporting, but I can't use it to build anything. What people are doing is using Cruel's repo and forking it to add support. For example, right now I have a phone that includes both Magisk Alpha and Kernelsu at the same time. Why? Well, why not! (Of course Kernelsu recognizes that and thus disables modules).

The linux Kernel version I see now is 4.14.113

Kernelsu does want to be in the Kernel. How? I'm a noob I have no idea :)
[Magisk] eXtremeDevil:
Hi, today I updated from Canary 26301 to 26302 and I got a boot crash. The boot logo lasted more than usual and then it was like SystemUI couldn't start, but I only got a blank screen, no further errors or crashes. I'm using a Xiaomi 10 Pro, xiaomi.eu ROM with Android 10 / MIUI 12. I have LSPosed and the CustoMIUIzer module, maybe there's some incompatibility. I don't have the time to try versions or submit logs, unfortunately. But I thought of postin here in case other people have the issue or in the case a solution may come somehow.

Thanks in advance.
[Magisk] zgfg:
Please don't cross-post.

Also, if not about Alpha, don't post under Alpha

Btw, if Magisk app was recognizing your phone as Ramdisk No, then the corresponding bug with Magisk update and a solution/workaround was posted couple of times in the Magisk General thread
[Magisk] eXtremeDevil:
I'm sorry, I don't know what you mean by "cross-post".

I thought Canary was alpha.

What is "Ramdisk No"? How can I check that?

EDIT

OK sorry, I didn't realize I post it on the other thread, I thought my post wasn't uploaded.
[Magisk] zgfg:
Please shortly read in this thread, particularly the OP post(s) - following the good XDA rules, you will see that Magisk Alpha is a closed source, an unofficial fork of Magisk (with the built-in telemetry)

And the official support for Alpha is practically exclusively on their Chinese TG channel (being also almost closed for joining)
[Magisk] eXtremeDevil:
In that case I will look for Canary support, thanks and sorry!
[Magisk] ashish1989:
Don't know why its unsupported now, for banking apps with great detection techniques this alpha fork works like a charm rather than the official magisk which is detected easily by the banking apps
[Magisk] zgfg:
Support (contact with developers) is only via the TG channel in Chinese. Here, there are only users
[Magisk] HippoMan:
... and also, as you mentioned above, I think it's worth repeating that their TG channel is almost closed for joining.

Until or unless that changes, we have to treat Alpha pretty much as a black box ... with telemetry that sends info about our usage of the software to who-knows-where.
[Magisk] jimger:
Which country are u at?

For UK made Santander working again (after today's update) but Barclay's still doesn't work
[Magisk] ashish1989:
From India
[Magisk] pndwal:
Join link for discussion group is still in first pinned message in Magisk alpha public channel, if hidden in (Never gonna give you up) music link... Been that way for a few years and people still join...

As I said a few days ago,

... Seems that like many personal projects of LSP Devs, vv's Alpha Magisk fork has become a shared resource... I'm quite sure Shana, Canyie and others are all accessing invaluable Alpha MS App Centre usage data and crash reports etc to fix their early 'bleeding edge' Magisk fixes, innovations, refactoring (changes) etc and to revert regressions quickly... It's simply a no-brainer as I've said before.

Of course this has a knock-on benefit for TJW Magisk users too as PRs generally accompany Metagisk, Alpha, and other commits from LSP associate's test branches...

It's sent via a kosher Microsoft development and Analytics app... Proper protocols checks and balances apply... Here's tech data for analytics for Android use:

https://learn.microsoft.com/en-us/appcenter/sdk/analytics/android

And I posted information re privacy and App Center data collection/tracking in this post:

Post in thread '[Discussion] Magisk - The Age of Zygisk.' https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88542077

Anyway, I don't think they care if you/others don't trust the fork any more; they're got quite enough users for very good data to facilitate quick/easy fixes... Here's some examples of data collected from an apparent 3.6 million Alpha installations 18 months ago:

https://t.me/magiskalpha/473

And she posted (next)

Further, on licensing obligations

https://t.me/magiskalpha/512

FWIW, I mentioned an interesting "case for Microsoft Appcenter telemetry in debug builds" here:

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

... Actually, I wouldn't be surprised If John Wu is also useing the Alpha App Centre data for fixes he integrates directly... Instant logs and relevant device details from hundreds of users w/o the need to field bug/issue reports and educate users about debug logging, how to find/run CI builds etc, etc...

Incidentally, I see John himself is committing the latest LSPosed Metagisk Zygisk branch changes from Shana currently:

Further, after Alpha broke stuff in initial 26302 with:

• Major behavior changes: The magiskd internal mount point is hidden from the outside world and uninstalled after it is no longer in use,

and we got a fixed (later) Alpha 26302, this fix (umount mirror?) was linked in private discussion group:

https://github.com/LSPosed/Magisk/commit/0988734347f0c0d1e5fd4a25575dfc4842102b1a

... Unfortunately LSPosed Magisk seems to be private... I can't see the fix... But I wonder if John's involved there too... 🤔

But if these latest Zygisk Metagisk changes are built in Alpha (per the last few months), seems we'll have John directly contributing not only to LSPosed test branches but also to vv's Alpha testing fork... 👀

🤠 PW
[Magisk] rodken:
This quote alone should clear the air about the telemetry feature built into Alpha and/or any other Magisk forks going forward.
[Magisk] HippoMan:
I personally wish I could see the source code that implements the use of this telemetry.

Also, even in the extremely likely case that the Alpha developers themselves have no ulterior motives whatsoever concerning the telemetry, it might be that they themselves could unknowingly be the targets of espionage by the government of their country ... a country which is one of the world leaders in the monitoring of their citizenry.
[Magisk] pndwal:
Sure... I wish we could see all the source....

... but did you check the stated limits on data collected?... Ie the protection for users that using a proper development and analytics implementation from a company like Microsoft affords?... Eg the linked "App Store privacy report":

With both Microsoft detailing the legitimate analytics (/debug) data telemetry is limited to and the Alpha author stating that "no personal information that could identify the user is collected", I wonder what damage due to espionage by a foreign government (based on a supposed capability of tapping/intercepting your App Centre data) you are imagining!... Or maybe it's the stated limitations from Microsoft that you don't trust in reality?...

Gives a whole new meaning to anal-ytics!

Wow... What other espionage could MS be facilitating with so much proprietary code running on personal machines?... I wonder, do you use one?... And are you sure you're not using other apps/software using MS App Centre? 😜 PW
[Magisk] immortalwon:
I have a slightly offtopic question: What is this new module called Zygisk Next and should we use it?
[Magisk] pndwal:
It's a standalone alternative to native Zygisk first developed for use with KernelSU root but now compatible with Magisk from the developer of HideMyApplist...

It initially used native bridge loading mechanism but has now moved to ptrace with fuse... I'll post some details from a contributor about the latest (not officially released) changes etc shortly...

In short it's plum necessary if using KernelSU, and an alternative that may work better than native Zygisk if using Magisk root... You may want to try it as it's supposedly more hideable than Magisk 26.x Zygisk (who's memory is not anonymous) and Shamiko (also from LSP associated Devs) has been compatible with it for some time...

Nb, looks like John's now contributing to LSPosed/Metagisk native bridge loaded Zygisk himself, and that 27.0 with NB loading (and anonymous memory) may be imminent... At least the focus on 26.x improvements is over, the new focus being on innovations for 27.0 release...

🤠 PW
[Magisk] immortalwon:
Thank you, your answers are always detailed and thorough. I am surprised, it seems you are a security researcher of some sort?
[Magisk] pndwal:
Haha, thanks... Nah... You wouldn't believe what I do...

Put that here for any tech-heads interested:

Post in thread '[Discussion] Magisk - The Age of Zygisk.' https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-89145810

🤠 PW