yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
You could go to Magisk GitHub and check for commits from the Alpha team

Look into the tons of posts in General Magisk thread and you could find posts discussing their names and 'roles'

It doesn't take years (everything will be obsolete by then). They test in Alpha and commit to Magisk but it then depends on TJW would he accept and when he would release the next Magisk Canary

Look again to Magisk GitHub and see how often usually he releases Stable versions (like two or three a year) and how often Canary releases go (like every month or two)
[Magisk] Mepsipax:
Awesome, thanks!
[Magisk] pndwal:
Alpha was open source for many years; don't know exactly why source is not scrupulously supplied any more, but vv doesn't seem to be actively encouraging daily use of Alpha... It's always been her test bed for major improvements in Magisk along with her other test branches like MTK (she gave us most MediaTek compatibility fixes), Lite (testing methods for hiding isolated process leaks etc) and so forth... It now seems to build commits from other LSP Devs like Shana's (@yujincheng08) Metagisk etc (you can see GitHub commits for this), so Alpha is now effectively a POC/testbed for upcoming Native Bridge Zygisk loading for instance...

At the beginning of last year vv introduced telemetry (Microsoft Appcenter, and she did publish the protocols, checks and balances) to Alpha and this has helped tremendously in analysing crashes, bugs, fixes, refactored functions etc etc in record time, and is clearly a real asset to Magisk Devs... (The paranoid are recoiling reading this, I know... and yes, it's in both release and debug builds apparently.)

The Chinese Alpha community is aware of this and don't seem phased, but I think the strong anti telemetry opinions expressed in her PR for it in Canary Magisk (She opened that in Jan last year, locked it for OT commenting several times and apparently some heated comments were removed... John didn't move on it and she finally seemed to resign and close it in Dec) may partly responsible for making Alpha more of a closed shop affair...

Sure, telemetry could be abused, but Appcenter is a properly implemented bit of kit and clearly a no-brainer for serious debugging and Magisk progress... I can also understand how, while even XDA users have felt alienated by Devs attitude at times, the reverse can happen; By vocally opposing beneficial changes these same users (incl other devs at times) seem to have pushed LSP Devs (especially) to far...

This is not the only occasion... Strong adjectives used regarding a different issue recently had Shana saying 'Im scared of this (Magisk) community now'...

These Devs are enthusiasts like us folks, and I've seen no evidence of skulduggery but actually many commits from LSP Devs designed to enhance security for root users as well as warnings about 'traps for young players' (eg re Selinux, USB debugging etc)...

The fact is that they are sometimes met with a hostile instead of thankful userbase however...

Sadly, opposition over telemetry and other issues seems to have pushed Devs like vv to (understandably) close ranks somewhat... It seems a shame, but it maybe a strategic move, that we no longer have open source Alpha... PW
[Magisk] hemfreitas11:
I'm a somewhat of an outsider and the only thing i know about the situation and the extent of the telemetry being used is what you just explained, but it seems a little odd that they would get offended by people opposing this telemetry.

People have bank apps, documents, private stuff on their phone. Whatever benefits it may have to development, it is vey hard to justify it given such a massive invasion of a persons privacy.

Magisk and Xposed are no joke, the alpha devs should have understood why people were complaining about it when they did. Ignoring it and then making it closed source is a bit of a red flag in my opinion
[Magisk] pndwal:
Of course they understand... Seems those that don't are the paranoid... And nobody's saying you can't be paranoid if you want!... 🤪

If Add Apcenter were implemented in Canary Magisk, Magisk code would still be open source and easy for other Devs to test what's sent to Appcenter MS servers...

Those same Bank apps etc you mention are closed source, and many are also using MS Appcenter and the like for telemetry to improve their apps, but it doesn't stop you using them!... Those apps could be collecting all sorts of data for all you know! ... Except that Microsoft says:

https://learn.microsoft.com/en-us/appcenter/gdpr/faq#app-store-privacy-report

and you don't give telemetry a second thought...

But really, the naysayers here simply don't trust anyone including Microsoft to keep faith, and like many idealist protesters they might not know which side their bread is buttered on and really just be spoiling things for others.

Anyway, there we have it; LSP Devs getting slammed for not understanding user's complaints and for a "massive invasion of a persons privacy" because they want to use a legitimate debugging and development tool that the users understand less than they understand Magisk itself...

"You can't use that nail gun! It's dangerous... Here, I've found your old hammer!"

"You'll need to clean the windows from a distance of 8 feet (American parlance)... for privacy reasons!"

"Can you paint our house in 3 days?... course you'll need to do it blindfolded because I might be getting dressed... Sign here"

How about "You guys will need to land the lunar module on your own; were pulling all the telemetry because we might be tempted to release your bowel and bladder movements to the viewing public."

... Like fun!... "Hook us up; we trust you Huston!"... "Paint you own house then; we have plenty of reasonable customers".

Might just be a creative way to refine your userbase!... vv and others just want to get the job done; Why not put off the wingers, complainers, and those casting aspersions... Why not actually give them some incentive to vote with their feet?... That's what I meant by "strategic move"...

The former 'Alpha Discussion' group currently has a Healthy 1137 mainly Chinese users and there's likely many more among LSPosed discussion's 7745 member base, I imagine quite enough for some meaningful measurements. 🙃 PW
[Magisk] hemfreitas11:
Well yeah, i wouldn't mind a company using something like that in their apps. Bank apps are made by banks, there is a name behind them, there's someone accountable, and most important of all they dont have the kind of access that either Magisk or Xposed do, so in my opinion it is pretty much safe to trust them
[Magisk] pndwal:
Sure... So you can vote with your feet in any case, but remember this is not about vv's Alpha fork where Appcenter implementation is simply vv's decision... She's free to implement test and debug it in her fork... The objections discussed were to her PR for telemetry in official Canary Magisk which, of course, you'll always have source for.

Microsoft can ensure private data isn't compromised/abused with Appcenter as it uses their back end, but Magisk is also open to scrutiny by coders in general anyway... Bank apps will need skilled reversers to prove that they're acting honourably.

So would Jorrit's (chainfire's) SuperSU for that matter, but most rooters in that era wouldn't have given a second thought to the possible (very serious) security breaches they were permitting with closed source root!

As for Alpha fork, vv has always used it as a test bed for experimental fixes and never promoted it as an alternative Magisk for daily use; it was only ever for those wanting to test innovations or fixes, or as a stop-gap solution until her fixes are merged in Magisk... It seems apparent to me that, with telemetry data continuously coming in, she no longer needs many testers and may be actively discouraging Alpha takeup as a 1100+ Chinese userbase delivers ample data for her prolific contributions to Magisk.

FWIW, vvb2060's Magisk commit production has been second only to John's (who merges most commits including those of others) for several years now... Just in recent months Shana has been at the top of the leaderboard however, but there's clearly much collaboration also:

vv's fixes, and her changes have been at the forefront of Magisk development for some years now... So many major innovations in official Magisk have been developed in vv's Alpha fork and her experimental branches.

Just to mention a sampling I posted more than a year ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, Renamable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

Alpha is thus no rogue fork, much less a vehicle for stealing data or scamming any of us and many members here know that the evidence of vv's beneficent motivation is more than anecdotal...

Whether I choose to do early testing of upcoming Magisk innovations with Alpha or not, I'm certainly not suspicious, rather I'm happy it exists as I am that other test forks and Magisk benefactors are contributing so much to this essential staple modding solution. 😋 PW
[Magisk] HippoMan:
Irrespective of the fact that most of them probably have valid, understandable reasons for wanting to keep their source closed and to be difficult to communicate with in their TG channel, the fact that this is the current reality of Alpha is enough to motivate me not to use it.

I don't hold it against those developers personally, and I respect their feelings and priorities and decisions about this.

It's just that if I have a choice (and in this case, I do), I prefer not to use this kind of software that is provided under those constraints.

As for telemetry, given the way that the current Chinese government utilizes similar telemetry aganst not only their own citizens, but also against others in other countries, I have more fear than usual about this particular telemetry. Even if none of the developers are knowingly working with the Chinese government, it's still possible that people from that government might be able to access the fruits of this telemetry.

I have as much right to be paranoid about this telemetry as do any of the Alpha developers have a right to be paranoid about discussion-group participants.
[Magisk] wangdaning:
The thing that has been pounded home here is Alpha does not need you either. The fact that nothing they give is translated should be enough for you to understand they test and receive feedback from Chinese users. TJW will be able to evaluate the feedback. There is simply no need for English speaking users in alpha testing new features and fixes.

As for trusting banking apps, remember banks have been known to freeze accounts based on a person's personal choices. They are not prevented from doing this. They often get permission to storage, files, phone, contacts...They require these permissions or the app wont work. I would not be so trusting.

All that said, I use stable magisk as I am not interested in testing, nor do I have the ability or time to give constructive feedback to any alpha project.
[Magisk] pndwal:
Well put...

This discussion began because we mentioned that Alpha allows Volkswagen app to run and a member wondered if Alpha is trustworthy...

Alpha solves the issue because it builds Shana's test branch commits and she's got native bridge Zygisk loading working to the point where it's quite useable (but still unfinished)

over the last few months...

The test branches for vv (Nangong Xueshan, @vvb2060), Shana (LoveSyKun, @yujincheng08), Canyie (@canyie) and others are open source, so you could easily build any of their experimental fixes yourself (it's not hard using a GitHub action run), or simply run one of the test branch CI (continuous integration) builds...

For example, the last collaborative published Refactor zygisk to use native bridge to inject commit was authored by Shana and committed in LSPosed/Metagisk Zygisk branch by 3 weeks ago, and an associated CI build is here:

Refactor zygisk to use native bridge to inject Magisk Build #61 pushed by yuijincheng08

That might work fine but many CI builds don't; they're simply test runs with varying usefulness and even successful functioning... Alpha release builds on the other hand, are built using selected commits and have been checked at least for basic functionality by vv, so there's a greater level of reliability despite being bleeding edge stuff.

I personally haven't used Alpha since John was producing viable Zygisk but not releasing any Canary builds (vv's Alpha served as a Zygisk testbed and POC for many months at the time) due to his mandatory period of restriction on creating/contributing to personal open source projects and Google review of his Magisk Android mod project... The new Zygisk refactoring that is native bridge loading simply made current Alpha builds too tempting for me! 😜... I'll be back to TJW Canary just as soon as we have N/B Zygisk, which Canyie has indicated should arrive with public 27.0 (or perhaps in an earlier Canary build).

I may be tempted by some other off-the-chart innovation LSP Devs introduce in future and hop on the Alpha bandwagon again, but I'm really eager to see what official Magisk delivers...

-----------
​

FYI: For anyone interested in what changes / innovations are in the works for Magisk or just being tested,

vv's test branches currently include:

resetprop

test

addon

reproducible

unshare

Shana / LSP project have:

su

gids

payloadapp

zygisk

nbpassthrough

Canyie has:

cxx

restart

lollipop

ptrace (Nb, commit from here for anyone desperate/pining for Magisk with Android 5.0 Lollipop is built in Restore and fix Android 5.0 support Magisk CI Build.

prop

In TJW (official), @osm0sis has:

fix/recovery-preinit

🤠 PW
[Magisk] djcsurf:
I've had Starling Bank app working previously, was just forced to update and now root detected. Using Magisk Delta 25210 I've tried switching to SU List which another user had it working with but maybe I'm doing something wrong. I also have the firebase host blocked. USNF Displax (latest) installed on Pixel 7 Pro stock FW. I have Enforce SU List on and all apps requiring root selected as well as Magisk app hidden. Am I missing anything?
[Magisk] Stillhard:
Starling Bank app checks Zygisk, just disable Zygisk in Magisk Delta will make the app happy
[Magisk] djcsurf:
Thanks for that, sure enough it works. The only draw back is it disables the USNF module.
[Magisk] spida_singh:
The only difference is that I'm running Linesgeos on my Pixel 6.

You could try to rename '99-magisk.sh' to something else removing Magisk in the title. It will still work fine.

It's located in root/system/addon.d
[Magisk] djcsurf:
Thanks, I shall give that a try later & report back.

Edit: I can't seem to locate that file, using MiXplorer.
[Magisk] J.Michael:
Did you check your modules?

find /data/adb/magisk -name 99-magisk.sh
[Magisk] aillez:
Anyone would like to try to hide root/magisk from this SCB bank app?

SCB EASY - แอปพลิเคชันใน Google Play

SCB Easy ให้คุณใช้ชีวิตได้ง่ายกว่าเดิมกับครั้งแรกของไลฟ์สไตล์แบงค์กิ้งแอพ

play.google.com

Since the latest version, I can't find any combination to make it work.

hopefully, someone can fully hide it.
[Magisk] makeyourself:
Without which Google Pay/Wallet doesn't work. So disabling Zygisk isn't a solution for me personally
[Magisk] djcsurf:
I can't locate the file.

Reading up on it I found out that the file is only installed when Magisk is installed through recovery.
[Magisk] Nekromantik:
hopefully the magisk devs can take a look at this or there is a module to hide Zygisk.
[Magisk] ipdev:
Interesting. 🤔

The app does not care if the `addon.d` directory exists?

It is a sure sign you are running a custom rom since factory roms would have no use for the backup and restore of system modifications.

Manufacture would just make the modification and release it built-in to factory roms.

If you rename it to `99-su.sh` the app is happy and works?

Cheers. :cowboy:
[Magisk] ipdev:
Besides currently only installing the script via recovery.

This might become an option like the systemless hosts module.

Magisk - [GitHub] - issue​

You also need to be running a custom rom that supports addon.d scripts. 😉

Cheers. :cowboy:

PS.

I did a little testing the other month.

See Post # 3,128
[Magisk] Nekromantik:
Its not relying on that as on stock Pixel firmware with root it still fails.

unless they check for root AND custom ROM.
[Magisk] pndwal:
Do you mean that that's needed to make Starling work for you with your LOS setup? PW
[Magisk] spida_singh:
No. I don't need to rename this to work. It was just a suggestion as I've seen this work before for other apps.

But then realised addon.d isn't on stock ROMs. It's visible on custom ROMS 😊
[Magisk] DineshValor:
Till yesterday night, it's working fine and today morning phone is run out battery and fully dead later charge it and start, then it's show each time Play Integrity failed.
[Magisk] pndwal:
Please give details of device and run Play Integrity API Checker and click <> at top to screenshot raw JSON response... PW
[Magisk] DineshValor:
Thank you for you reply and I fixed it yesterday.

Edit:- probably after battery run out, some modules got corrupted so simply remove them and re-installation solve the issue.
[Magisk] pndwal:
Actually yes, I have had a similar issue; usually clearing Google Play Services data will reset issues with passing verdicts, but I recall at least one occasion where I needed to disable USNF, reboot, enable and reboot again... 😋 PW
[Magisk] DineshValor:
Clearing Google Play Services data was not helpful rather than that next time will try disable and enabling USNF.
[Magisk] DaOldMan:
Anyone has any cl;ue about this issue ?

Tnx guys.
[Magisk] chiteroman:
Magisk Alpha vvb2060 + Shamiko can't hide zygote injection in new NativeTest

App: https://t.me/nullptr_dev
[Magisk] zgfg:
Hence no better choice than Delta (and without Shamiko)😁
[Magisk] chiteroman:
Yeah, Magisk Alpha also has hide :)
[Magisk] CharlieMHz:
The latest update 1.7.99.1 of TnG (Touch n' Go eWallet) app has started detecting Zygisk. I was able to get it working by turning off Zygisk, but USNF stops working so other apps detect root. For now I'm having to use an older version of the app (1.7.99 or older).

I'm on Magisk Delta latest stable (b8694c99-delta (25206)), with MagiskHide on, no other hiding modules installed. USNF 2.4.0 MOD 1.2 by Displax.

EDIT:

A workaround I discovered was to turn on Enforce SuList and add apps that need root to the SuList (guide below). I had to uninstall, reboot and reinstall USNF for other banking apps to work.

Link to post describing how to switch to SuList: https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-88269135

And the link to the post containing the attachment for sulist-auto-whitelist module: https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-88272583

Touch 'n Go eWallet - Apps on Google Play

Spend, Save, Earn, and Invest conveniently - all in one app!

play.google.com
[Magisk] zellleonhart:
Hi, I enabled Sulist and I can't boot into my OS anymore, now trying to fix it. Is there any steps I need to take if I enable SuList?
[Magisk] CharlieMHz:
Not that I know of, but I'm no expert on Magisk. Have you managed to get your OS to boot, perhaps via uninstalling/disabling Magisk? I'm sorry if you had to go the hard way of clean flashing again.
[Magisk] prokiller1199:
Hey, I had this problem with this version as well. Do you mean turn on the toggle of "Enforce SuList"?
[Magisk] zgfg:
To enable SuList in Delta it is not only turning on it's toggle

Please, there is Delta thread here on XDA, read the posts there about properly setting SUList (all root apps must be enabled in SuList and use sulist-auto-whitelist module)
[Magisk] CharlieMHz:
Thanks, was not aware that there was extra steps needed for SuList, I've updated my post with the relevant info.
[Magisk] rudzik12:
I have a problem with the zygisk module in the Sony XZ1 Compact (G8441) phone - after enabling it, the phone restarts after a while. Same after startup.

Magisk 26.1.

Previously I was using magisk version 21.X and everything worked (except cts profile - the phone didn't pass the test).

I tried to run zygisk without any exclusions - still after starting and several seconds the phone freezes and restarts.

Do you have any ideas?
[Magisk] XtraWater:
Since the latest version, on A12, magisk says suddenly it's not installed. After a reboot magisk is installed and works for a few minutes and then again, it's not installed. What can cause this?
[Magisk] J.Michael:
Can you find any kind of log file?

Maybe, after Magisk stops being installed, you can go into a terminal emulator and see what "dmesg" has to say. (I don't remember if you need privilege to use "dmesg".)
[Magisk] scareferatis:
I'm having issue bypassing root for HTTP Injector and NapsterNetV apps on both Black Shark 2 and Samsung S22.

BS2:

- Android Pie

- Latest Magisk Alpha with Universal SafetyNet Fix MOD (passes flawlessly) and latest Shamiko. Both apps are added to Shamiko's DenyList. HTTP Injector crashes itself, while Napster says Rooted users are unable to use this config.

S22:

- Pixel Experience Android 13

- Latest Magisk Delta with SUList enabled and all root stuff hidden.

Injector doesn't crash, but detects root while importing config. Same goes for Napster.

Here's a dummy NapsterNetV config with root block. Change the extension to .npv4 and import through the app to replicate my problem. Unfortunately, I can't give you an .ehi HTTP Injector file, because my S22 is currently bricked after failed restore.

UPDATE: Cleaned HTTP Injector's cache and reinstalled. Still detects root, but at least it runs. I've managed to create a dummy file. Change extension to .ehi and import.
[Magisk] zgfg:
At the beginning you said "passing flawlessly" - does it refer to SafetyNet (deprecated) or Play Integrity (but without Strong Integrity - that's what is relevant)

Are you using the latest USNF but from Displax (not the 'official')

Have you tried with Hide Magisk app

Disable LSPosed (if you have) and all other irrelevant Magisk modules and try again, but always Wipe Data (not just cache) for those apps you are testing

If still not passing, install/enable LSPosed and try with Hide My AppLlist (with other LSPosed modules disabled)

If you had XLua, you must manually delete its remaining folders

Must not run SELinux Permissive mode

Some apps may even look if Developer Options are enabled - there is an LSPosed module to hide

Etc - unfortunately, hiding is not only about SafetyNet, DenyList/Magisk Hide and Shamiko (on top of above, some apps may even look for TWRP folder)
[Magisk] m0han:
Re.: Shamiko update

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88608361
[Magisk] astrogrilsz:
Help please. I was accidentaly uninstalling magisk and get unrooted when i check it using root checker. Is it possible to root it again without wipe data? Im using samsung a52. Please tell me the method if there is any method
[Magisk] pndwal:
Not familiar with Sammy devices, but seems you're not facing the critical issues requiring data wipe mentioned in installation instruction page if you can still boot!

In Magisk App what do you see for Magisk Installed?... If N/A, type magisk -c and magisk -v in a terminal emulator app to be sure Magisk is not installed.

If really uninstalled, I'd be backing up all your personal data in case of issues at this point, then patch AP from current ROM in Magisk App and Odin flash it along with BL + CP + HOME_CSC. This should get you rooted again without wiping data. 🙂

Might pay to wait for further advice from Sammy users... 😉 PW