yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
PSA:

I recently asked here if anyone had been been surprised by unusual actions in the April 1 release of Magisk Alpha (changelog posted in OP post #2 here) being referred to in the TG Alpha Magisk discussion group as the 'April fools limited edition'.

This was in view of these official notices accompanying the build in the separate 'Magisk alpha' update thread (Chinese translated):

and

My query has been inexplicably deleted from this s thread! 🙁

However, those 'Warning' messages are still up, so, as nobody has responded here (not surprisingly), I have just installed this Alpha build and tested it on a secondary device.

I can confirm that, despite some claims of in-app messages stating that root has been granted to apps despite users denying access, I could not produce / have not seen such worrying behaviour...

So it appears that the Dev's "Warning to developers" notices themselves are the only 'April fools' joke.

Of course there is also NO substance to the assertions either that John's libsu root app solution has or is responsible for such behaviour, or that there are inconsistencies with the magiskpolicy tool (or consequently with SELinux policies) post 24302.

This may allay concerns if anyone translates / reads those 'warnings' in Magisk alpha TG.

Regarding the removal of my initial post regarding this and my posts in general, I accept and understand that some have been off topic, and have said that I agree to stay on topic several times (responses now removed). The OP here has however misconstrued my intentions. For whatever reasons, alpha related posts put up in good faith are now being removed without communication. This saddens me...

I hope this thread can become useful for Alpha users / enquiriors... PW
[Magisk] zgfg:
I saw that on Alpha TG and I was worried about, although I don't use Alpha, since they mentioned libsu

I don't really know if roots grants from the Magisk app go through libsu, but I tested with the latest Canary 24305 and everything was ok:

- I revoked the root grant to the Reboot app (by Petrus).

With the app you can easily reboot, reboot to Recovery or Fastboot.

Obviously, the app requires root grant to work

- I opened Reboot app and chose to reboot, and I was immediately popped-up to grant the root

- I denied to grant the root and I choose again to reboot, but it didn't reboot (correct behavior, without the root grant Reboot app cannot execute reboot)

- Again through Magisk app, Superuser tab, this time I granted the root and then Reboot app worked to reboot

In parallel I was checking in magisk.db, Policies, and everything looked ok (you can see by UID and policy values if the root grant is given/revoked to the particular app)
[Magisk] pndwal:
Yup, since Jan 2018, Magisk Manager / App "uses `libsu` for all root related operations".

Did similar test on Alpha; just wanted to see if it somehow claimed root granted when denied...

I wasn't worried about TJW Magisk as I was certain libsu & magiskpolicy 'warnings' were an 'April fools' hoax, but I wouldn't have put it past Devs to also implement false indicators... (Appears that if done at all, this must have expired after April 1 ?) I didn't find any...

Have to wonder how John views this hoax, especially since, surprisingly, there's been no retraction...

Thanks for confirming.

Nb. As I speak speak, TG Alpha discussion group name is being changed between names w/ sexual overtones by admin Canyie... Kids!

PW
[Magisk] pndwal:
As per Nb. above, Canyie's original "Alpha 讨论组" (Alpha discussion group)" is currently simply named 西大师 奶子... !?

No real idea why; Joking around? Trying to disguise Alpha discussion group? Deter 'foreigners'?

Members there are also asking questions... 👀 PW
[Magisk] pndwal:
... now it's 西大师 live! ... 🙄 PW
[Magisk] OhioYJ:
Thank you. The telegram you linked to is not in English, and from what I can tell appears to only be released? But again it's not in English so I don't know.

There was an Alpha build posted last week on GitHub, is that not an updated build?

I didn't think the general thread was the correct place as I'm not using those builds.

I'll look into the Delta builds some more. Kind of a bummer to have on device on something different. It was nice to have every thing on the same thing.
[Magisk] Homeboy76:
OhioYJ,

I have not posted any telegram links on this thread. Telegram links are not allowed on XDA.

The last Public Release of Magisk Alpha was March 8, 2023: app-release_d52ea1b0-alpha.apk -

25210

If this is the Magisk Alpha Public build you are referring to, Yes.

I edited post # 180: I removed the sentence about Magisk Alpha discontinuing Public Releases. :mad:

There are several questions and answers about Magisk Alpha on topjohnwu's Magisk General Support / Discussion thread.

I think you'll like @huskydg Magisk Delta fork. You might switch "everything" to the Magisk Delta fork after you try it. :ROFLMAO:
[Magisk] huskydg:
Magisk alpha has been made closed source and there are no source code for new version. You should use trustworthy, open source and no telemetry included method (which you can't opt-out) magisk.

What Magisk you should use:

- Official Magisk (25206) recommended

- Cygisk

- Magisk Delta

What Magisk you should not use:

- Official Magisk (25207~25210 is not stable and some changes are broken)

- Magisk Alpha
[Magisk] Homeboy76:
Magisk Cygisk fork added to the OP.
[Magisk] OhioYJ:
I switched to your latest Magisk Canary build on the tablet and no more issues with it. I'll probably switch my other devices over to it as I update them.
[Magisk] huskydg:
hope someone will understand this is just my advice and i don't force you to follow my thought ;)
[Magisk] Homeboy76:
Moved to OP. :)
[Magisk] immortalwon:
If we have questions about Magisk alpha for the developer, is there a place we can communicate with him / her? Do they know english?
[Magisk] rodken:
Refer to the first sentence within this post.
[Magisk] immortalwon:
I did but it doesn't really answer the question.
[Magisk] rodken:
There has been a time when the developer rebuked anyone from reaching out via the GitHub page which leaves the TG group the only viable avenue.

-- You would have to scour the web but not limited to other mediums for the moniker vvb2060.
[Magisk] zgfg:
Closed source might also be counter-peotection from those who try to make sure that they could detect the 'root'. If they see how the code tries to hide and what are the new changes in that direction, they can more easily catch up to detect again)

What bothers more (and probably more users) was the Telemetry (but ok, if that can be blocked by some firewall and similar tricks)

Last and definitely not the least is about the support. On XDA there is only one developer (she is not the lead but still, she is one of them) who reads and sometimes responds - but not in this thread, only in Magisk General thread

You can reach the main developer only in TG channel but:

- invitation link is not public, the clue to find it was posted here and/or in the General Magisk thread

- only Chinese is allowed in the TG channel, post in English and you will be banned

- post anything that they think is out-of-topic (sometimes even that being related to the real problem) and you will be also banned

- even if not banned, you can expect unpleasure communication (or it could just be about the customs cultural differences)

Finally, I don't really see what would be the need to still use Alpha. It made sense (many of us did) when the upcoming changes (Zygisk, DenyList replacing MagiskHide, etc) were provided to test only in Alpha and they have not yet been present in Magisk, not even Canary or Beta

But now - probably those who still use Alpha know better, like some changes are still showing faster (for pre-testing) in Alpha, before they come to the official Magisk versions

But then, there is also Magisk Delta fork, with developer carrying himself about hiding the 'root', with more useful TG channel support, etc

My two cents
[Magisk] Clark Joseph Kent:
Enough Political talks or comments, the thread has run its course in the wrong direction, now please stop, and thread cleaned.

As per the Forum Rules, thanks.
[Magisk] HippoMan:
Agreed.

However, since those who are responsible for Alpha have pretty much locked most people out from discussing any of the aspects their software with them, it seems to me that the purpose of this entire thread about Alpha is now pretty much moot.
[Magisk] Homeboy76:
The

latest publicly released

Magisk alpha

app-release_709f25f6-26101.apk - 12 Apr

Notes:

The [newest] version of Magisk alpha is posted on telegram.

How to download the latest [publicly released] version:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB, Tap Download

'Better late than never' :ROFLMAO:
[Magisk] rodken:
The latest version hasn't been uploaded to the servers as of yet.

-- 83d837d8-alpha 26101
[Magisk] Homeboy76:
What date was it released?

Are you sure it is "26101" and not 26102? They usually don't release two with "26101".
[Magisk] rodken:
Released on April 24th.
[Magisk] Homeboy76:
@rodken

:oops: Ok, you're right. That one has not been released to the public. :)

I edited post #196.
[Magisk] rodken:
As a rule of thumb, a great number of releases by Canyie are usually not disclosed.
[Magisk] kevinco1:
+1
[Magisk] pndwal:
@canyie may be main admin in what used to be TG Alpha discussion as well as a contributor to experimental Alpha, but it's not her fork... vvb2060 releases this!

@canyie clearly has access and forwards various builds incl. debug for proper bug analysis/logs in that TG thread...

She built Bravo (not recently updated), but seems to do a lot of Magisk debugging in general... She has a number of test branches open aside from Bravo and has open PRs for these improvements of her own and she contributes to PRs (changes, reviews) for major innovations often tested in LSPosed (Shana's initiative) Metagisk test branches, eg the current Native Bridge Zygisk loading initiative Refactor zygisk to use native bridge to inject nearing completion...

which are also often further tested /built in Alpha... This one is already working well in latest Alpha builds as I've shown here:

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

and here:

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

... So in this way @canyie does have countless commit contributions in Metagisk and Alpha as well as in official TJW Magisk ultimately...

👀 PW
[Magisk] manan001:
It seems i have strage issue:

When i use HDFC bank application in Magisk hide mode: clicking on bank app url opens which check the root status and shows me warning that root detected.

But similarly when i use HDFC banks payzap app it work. All other banking app work including icici bank app.

2. When i unhide magisk HDFC bank app works but other banks including icici bank app does not work.

module used : USNF version 2.4.0 mod 1.2 by Displax.
[Magisk] HippoMan:
It almost seems like HDFC bank is trying to monopolize the use of their own banking services and no one else's by saying, in effect, "We'll let you use our app under root, and to do so, all other banking apps will be blocked." :)
[Magisk] Homeboy76:
Update

[MODULE] [MOD] Universal SafetyNet Fix by Displax

v2.4.0-MOD_1.3

Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp!

Ignore props changing on Xiaomi.eu. This fixes randomly attestation failings. So strange ROM...
[Magisk] amk316:
is there any way to disable magisk alpha then reboot to activate it like magisk delta?
[Magisk] pndwal:
Please say what you are trying to achieve... May be able to help... PW
[Magisk] amk316:
In magisk delta i can disable the rooting and run some apps that dedicated root how hard i hide it but magisk alpha don't have this feature

Is there a command i can type in shell to disable root temporarily to run the apps
[Magisk] pndwal:
su
magisk --stop

🤠 PW
[Magisk] kevinco1:
You can download Magisk Hide as a seperate module, but I can't confirm that it's 100% compatible with Alpha
[Magisk] amk316:
nop

steel app detect root or zygisk

i use to stop root in delta and it run

if you want to try

https://play.google.com/store/apps/details?id=sa.gov.nic.myid&hl=en&gl=US
[Magisk] pndwal:
Not available in my country...

However, this does do what you asked:

Disabling Magisk (core) may not be enough however ... Some apps have begun detecting Alpha app and may not look for Delta yet... Nb. Hiding the app in App settings may not be enough either, but to check if app detection is the issue (and assuming your Delta method didn't stop working because bank must either not be detecting failed PI deviceIntegrity or you have a custom ROM that passes that natively for this to work), try disabling using Magisk --stop, then uninstall Alpha app and try...

If that works, bank may be detecting both Alpha app and Zygisk (and possibly other traces too).

Suggest you try latest Alpha from Alpha TG discussion (private) group which builds new WIP native bridge loaded Zygisk; this is already allowing many apps that detect Zygisk to work... You'll need to swap denylist for Shamiko to effect proper hiding if you haven't already...

Next, take 'Hide the Magisk app' and further obfuscate it in a Hide My Applist (LSPosed module) template along with HMA and any other XPosed modules and root-associated apps, and enable hiding (w/this template) for your bank app...

Nb. Looks like native bridge will come to TJW Magisk soon also... 😉 PW
[Magisk] first_damned:
Does magisk alpha survive updates on Lineage? With twrp recovery
[Magisk] pndwal:
W/ properly implemented addon.d (eg official LOS) survival script should work if flashing from system and device is A/B (addon.d v2)... If A-only it should work from TWRP (addon.d v1) if data is unencrypted or if using FBE... Original addon.d is still broken w/ FDE due to Magisk limitations AFAIK...

Alpha may possibly have reversed addon.d functionality but I doubt it as it aims to build on official base and simply add fixes/enhancements... Also, @topjohnwu largely addressed vvb2060's concerns with addon.d by moving to enforcing selinux in Magisk for update engine...

(Pinging @osmosis) 🤠 PW
[Magisk] JazonX:
Any clue on how to find and join ?

Thanks and much appreciated !
[Magisk] JazonX:
Ever since I switched to Magisk Alpha, I keep finding this file in my Download folder.

I'm assuming it's a log/or something to do with Alpha because it appeared on 2 phones, and the only change I did was switching to Alpha.

HANYCJLZOEUS_TOKEN2.DAT

Any clue?

File seems harmless, and the content is not readable with NotePad+.
[Magisk] pndwal:
This:

https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/post-88613073

🤪 PW
[Magisk] rodken:
Clicking or accessing links somewhere on some sites, the ad site appears in the background. Some types also automatically download files without clicking anywhere.

-- That particular file has nothing to do with Magisk Alpha.
[Magisk] pndwal:
Latest Alpha

Files:

https://github.com/vvb2060/magisk_files/tree/2606e5031a91b869e654905913347b541c21e2c1

Translated (w/ Text Fairy capture):

alpha changelog

Breaking behavior change: magiskd now lives in a separate mount namespace, which is also SU's global mount namespace. Most su use cases will not be affected. If there is a case where you can only use init to mount the namespace, you need to change to su -t 1.

Breaking behavior change: File frameworks for module mounting are now straight-only, i.e. $(magisk --path)/.magisk/modules and $(magisk --path)/.magisk/worker are both read-only. Can be modified through the /data/adb/modules path.

Breaking behavior change: magisk --path fixed to /sbin or /debug_ramdisk.

Magisk (46770db1-alpha)

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

• [App] Add and test t.me/s/magiskalpha/473

• [General] Don't auto unlock device block

• [General] Delete sepolicy temporary files

• [General] Rewrite MagiskHide, implemented with logcat. The device whose log system is abnormal should not enable this function.

• [App] Does not actively request permission

• [Zygisk] Uninstall Mount no, Jump to com.android.systemui

• [General] Remove addon.d support

• [Generall Hide Magisk internal mount point

• [Zygisk] Refactored loading method, same as riru [under testing, unstable]

• [MagiskSU] Support remove of capabilities

• [General] Support users to restrict Root capabilities

Upstream changelog

Magisk (a8c4a33e) (26103)

Lots of code is migrated over to Rust!

• [MagiskBoot] Support cpio files containing character fles

• [MagiskBoot] Support listing cpio content

• [App] Support patching boot image from ROM zips

Diffs to V26.1

• [MagiskBoot] Support extracting boot image from payload .bin

• [MagiskBoot] Support cpio flles containing character flles

• [MagiskBoot] Support listing cpio content

• [Daemon] Make daemon socket fixed path in MAGISKTMP

• [resetprop] Support printing property context

• [resetprop] Support only printing persistent properties from storage

• [resetprop] Properly support setting persistent properties bypassing property_service

• [MagiskSU] Support -g and -G options

• [MagiskSU] Support switching mount namespace to PID with -t

• [App] Support patching boot image from ROM zips

👍 PW
[Magisk] pndwal:
Re • [Zygisk] Refactored loading method, same as riru [under testing, unstable]:

Native Test:

🙁

Memory Detector:

🙂 PW
[Magisk] ayhamthedude1:
How to install on Samsung devices? thx
[Magisk] pndwal:
It's Magisk... Same way as official...

Of course signature checks will now prevent app installing w/o uninstalling Magisk core, but users can bypass checks (done by Magisk daemon in Magisk core) by installing Debug build first then updating to fork, or simply by flashing Alpha Magisk as a .zip from Modules Install from storage menu...

🤠 PW
[Magisk] pndwal:
Latest Alpha 08bfbb15-alpha-26104

Translated:

alpha update log

Breaking behavior change: magiskd is now in a separate mount namespace, which is also su's global mount namespace. Most su use cases will not be affected. If you can only use init to mount the namespace, you need to change it to su -t 1 .

Breaking behavior change: File frames used for module mounts are now read-only, i.e.

Both $(magisk --path)/.magisk/modules and $(magisk --path)/.magisk/worker are read-only and can only be modified through the /data/adb/modules path.

Breaking behavior change: magisk path fixed to /sbin or /debug_ramdisk.

Magisk (08bfbb15-alpha)

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

• [App] Add telemetry https://t.me/s/magiskalpha/473

• [General] Do not automatically unlock device blocks

• [General] delete sepolicy temporary files

• [General] Rewrite MagiskHide, implemented using logcat. Devices with abnormal logging system should not enable this function.

• [App] does not actively request permission

• [Zygisk] Uninstall mount does not skip com.android.systemui

• [General] Remove addon.d support

• [General] Hide magisk internal mount point

• [Zygisk] Refactored loading method, the same as riru [under testing, unstable]

• [MagiskSU] support removal of capabilities

• [General] Support users to restrict Root capabilities

Upstream Changelog

Magisk (d390ca2f) (26104)...

👀 PW
[Magisk] zgfg:
They are effectively pushing more and more to be read-only

And that's not Google here but the 'gang'

Tine to find KSU and move off from Magisk that is becoming less and less useful
[Magisk] Homeboy76:
The latest Apha

Public Release

is 46770db1-alpha-26103.

Thanks for keeping this thread up to date with the latest Telegram Alpha release. I really appreciate it. :)

I updated the

Magisk Canary

link :)
[Magisk] rodken:
Typo: Alpha 08bfbb15-alpha-26204 should read Alpha 08bfbb15-alpha-26104.
[Magisk] HippoMan:
Sadly, I have to agree.
[Magisk] pndwal:
👍 Thanks... Fixed. 😄 PW
[Magisk] pndwal:
Just saw public Alpha channel note:

暂不更新26104，因为上游问题存在一些严重问题

Not updating 26104 for now as there are some serious issues with upstream issues

Seems refers to these Magisk boot patching fixes needed:

Fix $BOOTMODE set by manager.sh being incorrectly overridden

#7172 opened yesterday by canyie• Review required

Fix MagiskInstaller.patchBoot() error catching

#7171 opened yesterday by canyie• Review required

👀 PW
[Magisk] HippoMan:
I've now done some KernelSU investigation, and I found the following items in the KernelSU FAQ:

Based on these items, it looks like KernelSU is not meant to be a fulll replacement for Magisk.

Unfortunately, I don't understand the inner workings of Magisk well enough to understand which Magisk-supplied functions that KernelSU will not replace, and why, therefore, Magisk would still need to be utilized.
[Magisk] pndwal:
Latest Alpha b191a14a-alpha-26104

Translated:

alpha update log

Breaking behavior change: magiskd is now in a separate mount namespace, which is also su's global mount namespace. Most su use cases will not be affected. If you need init to mount the namespace, change to su -t 1 .

Breaking behavior change: File frames used for module mounts are now read-only, i.e.

Both $(magisk --path)/.magisk/modules and $(magisk --path)/.magisk/worker are read-only and can only be modified through the /data/adb/modules path.

Breaking behavior change: magisk path fixed to /sbin or /debug_ramdisk.

Magisk (b191a14a-alpha)

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

• [App] Add telemetry https://t.me/s/magiskalpha/473

• [General] Do not automatically unlock device blocks

• [General] delete sepolicy temporary files

• [General] Rewrite MagiskHide, implemented using logcat. Devices with abnormal logging system should not enable this function.

• [App] does not actively request permission

• [Zygisk] Uninstall mount does not skip com.android.systemui

• [General] Remove addon.d support

• [General] Hide magisk internal mount point

• [Zygisk] Refactored loading method, the same as riru [under testing, unstable]

• [MagiskSU] support removal of capabilities

• [General] Support users to restrict Root capabilities (Apps using old libsu will be misidentified as non-root)

• [App] remove fingerprint and biometric permission

Upstream Changelog

Magisk (d390ca2f) (26104)...

On GitHub: https://github.com/vvb2060/magisk_files

👀 PW
[Magisk] pndwal:
Nb. These builds can be reissued (rebuilt) with the same base commits to fix minor issues... Latest (topmost) was 7 hrs ago. Original is bottommost:

b191a14a-alpha 26104

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

b191a14a-alpha 26104

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

b191a14a-alpha 26104

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

Nb. Tree is not public so links only work for collaborators etc...

👀 PW
[Magisk] MinhViLuan:
Link dead, u have other? thanks pro
[Magisk] pndwal:
NOT dead... But like I said:

... Original link (post above) works. 🙃 PW
[Magisk] Legitsu:
on ther latest alpha I am now able to run without hidemyapplist and shamiko.

good but I still don't like the direction magisk is headed and I think the end solution is to work on kernellSU and bringing its modules fuctionality up to par
[Magisk] amritpal2489:
Can anybody let me know what's the benefit of using this over official magisk?
[Magisk] pndwal:
Zygisk hooking can't be properly hidden using TJW Magisk ATM, but Alpha just builds commits being developed for official Magisk early...

The WIP is Native Bridge loaded Zygisk.

Native Bridge loading was the basis for Ruru's inbuilt RiruHide, and it makes Zygisk hideable from many banks already in combination with Shamiko... The finished NBZ may be fully hidable; it isn't yet, but it may be that Shamiko that needs improving also...

Devs have been working on this since March, and aiming to publish NBZ with Magisk 27.0 (or earlier canary build?)... We'll have to wait and see... 🤠 PW