yashsingh1/xdaforums huggingface dataset:
[Magisk] Homeboy76:
alpha changelog

Magisk (a609e0aa-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

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

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

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] Homeboy76:
alpha changelog

Magisk (13450819-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

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

- [App] Fix root shell initialization too late

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

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] eienkisu:
These bank apps still are detecting magisk alpha despite in denylist, and hide magisk, zygisk, shamiko, universal safetynet fix. The apps only works with magisk uninstalled and phone unrooted.

POSB digibank - Apps on Google Play

POSB digibank (mobile) – virtually invisible mobile banking.

play.google.com

Singpass - Apps on Google Play

Your trusted digital identity

play.google.com

this app detects magisk on zygisk, but not on riru.

myENV - Apps on Google Play

Access real-time information on weather and enable notifications for features.

play.google.com
[Magisk] casouzaj:
When magisk is installed, does your phone pass both SefetyNet tests? Is it shown as certified in Pay Store > settings > About?
[Magisk] Homeboy76:
alpha changelog

Magisk (a32c4561-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

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

- [App] Fix Arabic environment cannot hide app - [Scripts] Fix boot image v1 signature

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

Magisk (cc79a96f) (24307)

- [App] Update libsu with 100% new I/O layer

- [MagiskInit] Mock enforce file with regular file to prevent possible race condition

- Switch normal NDK with ONDK, preparing the toolchain to introduce Rust

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] kleptonez:
SafetyNet-yes. Certified-yes. App still detects.
[Magisk] Stillhard:
No problem here, Magisk v23 + Riru + Riru-MomoHider + Riru-USNF + Riru-LSPosed + Own module
[Magisk] Homeboy76:
alpha changelog

Magisk (71e9c044-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] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├

- [App] Allow loading zygisk modules

- [General] Signature Verification

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

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

- [App] Fix can't open app without root

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

Magisk (42e5f515) (24308)

- Several minor bug fixes

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] Stillhard:
looks like you missed quote or didn't catch my post
[Magisk] Homeboy76:
I did, I deleted my post. :mad:
[Magisk] dr4go:
@Homeboy76: Although appreciated, I still think / believe that this is the wrong thread for Magisk updates.
[Magisk] dr4go:
Nothing against those intentions, but there is a Magisk General thread, a Zygisk thread and the Alpha thread. Just sharing my opinion, of course.
[Magisk] Homeboy76:
@dr4go

After, @pndwal post # 79 stated the

Upstream Changes

in Magisk alpha matches the changes

in Magisk Canary

. I understand your concern about the posting of Magisk Canary Updates in this thread. It will be rectified.
[Magisk] pndwal:
NB. Upstream Changes section in Alpha changelog duplicates Canary changes on every release in any case as Alpha aims to stay in sync latest Canary.

Latest available is 071ae79f-alpha, building this commit:

Release new canary build

Latest Canary built the one before:

Extract vbmeta from footer

👀 PW
[Magisk] Homeboy76:
alpha changelog

Magisk (071ae79f-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] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├

- [App] Allow loading zygisk modules

- [General] Signature Verification

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

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 (c11ccbae) (24310)

- Pixel 6 Android 13 Beta 2 support is here!

- [App] Support requesting root from non app process

- [App] Fix deadlocking a background thread on non-root devices

- [MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

- [MagiskBoot] Fix vbmeta extraction implementation

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

- [MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

- [MagiskBoot] Fix vbmeta extraction implementation

- [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] Homeboy76:
Update

"May 15, 2022

Magisk alpha

Magisk officially changed the canary channel to release mode, and introduced a new debug channel to replace the old canary channel.

Issue reports require the use of the debug channel version, the canary channel is available for general use.

alpha is unaffected, there is no change. In addition, 24311 and 24312 only add update channels, so alpha is not released"
[Magisk] Homeboy76:
alpha changelog

Magisk (edb76503-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] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├

- [App] Allow loading zygisk modules

- [App] When there is no module, it will prompt whether it is because of skipping loading the module (safe mode, etc.)

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

Magisk (8dfb30fe) (24313)

- [App] Fix Debug channel preference not sticking

- [App] Update the stub dynamic resource loading implementation to use official APIs on API 30+

- [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks

- [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature

- [DenyList] Fix DenyList on shared UID apps

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

- [MagiskInit] Support Android 13 GKIs (Pixel 6)

- [MagiskBoot] Fix vbmeta extraction implementation

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

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

- [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks

- [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature

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

- [DenyList] Fix DenyList on shared UID apps

- [BusyBox] Add workaround for devices running old kernels
[Magisk] Homeboy76:
alpha changelog

Magisk (d7776f65-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] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├

- [App] Allow loading zygisk modules

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 (bf04fa13) (24314)

- [App] Fix language switch

- [MagiskSU] Handle `system_server` restarts to prevent UID reuse abuse

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

- [MagiskInit] Support Android 13 GKIs (Pixel 6)

- [MagiskBoot] Fix vbmeta extraction implementation

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

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

- [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks

- [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature

- [MagiskSU] Handle `system_server` restarts to prevent UID reuse abuse

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

- [DenyList] Fix DenyList on shared UID apps

- [BusyBox] Add workaround for devices running old kernels
[Magisk] inunxelex:
@Stillhard

try this https://play.google.com/store/apps/details?id=com.bankmandiri.mandirionline&gl=ID (y)
[Magisk] infernix:
So I updated to the latest alpha (d7776f65) and updated shamiko to 0.5.0 as well. magisk is hidden. YASNAC shows I pass basic and CTS. MOMO only reports that debugging mode is enabled. I have at least 5 banking and other root detecting apps that all work fine (e.g. denylist is not enforced but they are all checked on it so that means shamiko works).

But Microsoft Intune (aka Company Portal) says I'm rooted. It did not do that on the previous version of shamiko (i think 0.3.0 but could be older) and magisk alpha (24.1 or .2).

I have all microsoft apps hidden including every single expanded option. No idea how they're pulling it off. Downgrading to a previous version of Intune doesn't help either.
[Magisk] Homeboy76:
@infernix

<Edit> See post #83

pndwal said and this post

: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86980351
[Magisk] pndwal:
You may be confusing the purpose of USNF. 😜

infernix already said SafetyNet (incl. CTS profile match) is passing; USNF is not designed to do more than allow this (bit like old MagiskHide), so apparently it's working perfectly...

Hiding 'root' further is the domain of Shamiko, even Xposed-HideMyApplist etc (bit like old riru-MomoHider, LSPosed-hide etc). PW
[Magisk] Homeboy76:
alpha changelog

Magisk (cae58c87)(alpha)

Changelog.md not in zip file

:oops: ? ? ? ? ? :oops:
[Magisk] Homeboy76:
I do believe Magisk alpha has commits that are not merged into official Magisk and they could be unstable/

bleeding edge

commits.

What I didn't know was Magisk alpha implemented an appcenter tracker.

When was the Magisk alpha appcenter tracker implemented?
[Magisk] pndwal:
FYI

Magisk Alpha channel description:

3rd party version of Magisk with telemetry and signature verification, less stable than Canary channels, no security guarantees, no availability guarantees, no privacy protocols.

- Chinese Translated.

Shortly before this PR for TJW Magisk:

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

😛 PW
[Magisk] Homeboy76:
Thanks, I read the 3rd party information, but I missed the appcenter change. :(
[Magisk] pndwal:
Here, telemetry = MS Appcenter. PW
[Magisk] Homeboy76:
I think Magisk Canary app-debug and Magisk alpha have the MS appcenter.
[Magisk] pndwal:
🤔 Official Canary doesn't, unofficial Alpha does; did you check vv's PR I linked?... It has not been merged, but that's what it's for...

Also, while current Debug is built with Canary, there is no more Canary-debug; only Canary-release and Debug-debug build types.

I think John's addition of Debug Magisk as debug builds paves the way for telemetry in Debug, and it may well be merged in due course... With Canary debug's change to Canary release builds (ie not even verbose debugging any more), I doubt telemetry will come to Canary... [Could be wrong; see next post...]

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

That move should also satisfy the telemetry naysayers* as users [may] be able to continue to use the frequent Canary releases (as well as Stable/Beta) as daily drivers if they wish without telemetry (which also produces a performance hit on older devices) or the fear of 'big brother' collecting their data (illegitimate in my view after looking at the checks and balances / scope of controls on data collection in any case).

*see comments in PR. See here for my take on telemetry:

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

Additional information:

"... a case for Microsoft Appcenter telemetry in debug build":

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

Changelog for Feb 17 Alpha w/ addition of telemetry:

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

Telemetry added to LSPosed in Feb:

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

👀 PW
[Magisk] pndwal:
Just checked, and I see vv's Alpha builds on TG are all built as release as designated... I see these are around 11mb, whereas debug builds (I can only find these in her actions runs) are around 18mb, so I'm assuming telemetry exists in release builds in Alpha... I see the size (in Add appcenter) is only a few kb (Can't see build tree for Alpha on GitHub any longer; can only for WIP and stale branches... Can you confirm / point me to Alpha build tree, or is this no longer public?)

I guess this may mean that my assumption that John can or will simply exclude telemetry in release builds using build-type flag may be wishful... This difficulty may also account for the long delay merging... PW

PS.

1) Is this working well?:

block normal apps from obtaining bootloader status (committed 6 days ago)

2) Does this merge TheHitMan7 or 'cygisk' commits?

3) Love your work, especially Magisk BootloopSaver

👍 PW
[Magisk] ipdev:
I tried it a few days ago when I saw the PR.

Momo still found unlocked bootloader on Pixel(s).​

Even if it works for some it will not be added to USNF.

kdrag0n closed the PR. Comment
[Magisk] huskydg:
TEE can be broken on locked bootloader.

I add some denials to block user apps not to obtain bootloader status.

But kdra0n is right, I can't deny that there are still some reason to use hardware attestation to not fake it broken
[Magisk] Homeboy76:
<Edited> :rolleyes: Wrong post.
[Magisk] pndwal:
Guess it may break Widevine L1 certification / HD decoding in TEE OS too then?... Tested w/ Netflix or other steaming service? PW

Sorry. 😬 PW
[Magisk] dr4go:
Same on the Galaxy S10.

I agree with @Homeboy76 that we don't have enough Magisk threads. 😂

@huskydg Using your canary build now, works perfectly. And thank god @canyie for the recovery fix, which also works flawlessly.
[Magisk] Homeboy76:
Suggestion

Create a

Discussion Magisk Custom HuskyDG Fork thread

, or

Magisk Custom HuskyDG Fork / Discussion Thread

. There are a lot of XDA Members that liked using

MagiskHide and some of them have Android 9/10 devices

. The XDA members with Android 9 / 10 devices would appreciate having a

Magisk Custom HuskyDG Fork discussion thread

.
[Magisk] shoey63:
Why not make this the discussion thread for ALL Magisk forks?

At any rate there is always ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├ for Husky DG Magisk Delta
[Magisk] Homeboy76:
Nope! @huskydg's App makes MagiskHide available for most devices. It is perfect for older devices that are still using Android 9 and 10. AFAIK, the alpha fork does does not support Android 9 and 10. Additionally, there are several XDA Member that do not use

Telegram

. They rely on XDA for help with their devices. Further, huskydg not only post his information on XDA but also responds to questions on XDA. Finally, a

Magisk Delta huskydg Fork thread

would provide a place where XDA Members that

do not use Telegram

can ask specific questions pertaining to his fork rather than posting them on the Magisk General Support / Discussion thread, [Discussion] Magisk - The Age of Zygisk thread, etc., that were not created for huskydg Magisk Delta fork.
[Magisk] Homeboy76:
"...Magic alpha

Telemetry data public

https://openapi.appcenter.ms

owner_name vvb2060

app_name Magisk X-API-Token

34e45ff8c41acb07f58cdb271454e85c80622f11

A question was asked about GDPR compliance for telemetry, since no personal information that could identify a user is collected or correlated, GDPR Articles 15 to 20 do not apply. This can be confirmed via the source code tarball or the public query API.

This information is issued in fulfillment of a notification obligation.

Art. 11 GDPR – Processing which does not require identification - General Data Protection Regulation (GDPR)

If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify the data subject for the sole...

gdpr-info.eu

https://docs.microsoft.com/en-us/appcenter/gdpr/does-it-apply-to-me/

General Data Protection Regulation (GDPR)

Art. 11 GDPR – Processing which does not require identification - General Data Protection Regulation (GDPR)

If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify…"
[Magisk] Homeboy76:
alpha changelog

Magisk (4eb71830-alpha)

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├

- [App] Allow loading zygisk modules

- [MagiskInit] Fix stub cpio's missing folder caused the failure to boot

- [App] Reduce file size

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

v25.1

- [MagiskBoot] Fix ramdisk backup being incorrectly skipped

- [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation

- [Zygisk] Change binary hijack paths

- [App] Fix incorrect recovery mode detection and installation

- [MagiskInit] Fix config not properly exported in legacy SAR devices

- [General] Enforce the Magisk app to always match or be newer than `magiskd`
[Magisk] huskydg:
<deleted>
[Magisk] Homeboy76:
LSPosed Shamiko Update

See OP -

Useful Links