[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

[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

 

[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

 

[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

 

[casouzaj]

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

When magisk is installed, does your phone pass both SefetyNet tests? Is it shown as certified in Pay Store > settings > About?

 

[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

 

[kleptonez]

When magisk is installed, does your phone pass both SefetyNet tests? Is it shown as certified in Pay Store > settings > About?

SafetyNet-yes. Certified-yes. App still detects.

 

[Stillhard]

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

No problem here, Magisk v23 + Riru + Riru-MomoHider + Riru-USNF + Riru-LSPosed + Own module

 

[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

 

[Stillhard]

Ok alpha didn't work for you, but Magick 23 did. So, why are you complaining about Magick alpha.

looks like you missed quote or didn't catch my post

 

[Homeboy76]

looks like you missed quote or didn't catch my post

I did, I deleted my post.

 

[dr4go]

@Homeboy76: Although appreciated, I still think / believe that this is the wrong thread for Magisk updates.

 

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

 

[Homeboy76]

Nothing against those intentions, but there is a Magisk General thread, a Zygisk thread and the Alpha thread. Just sharing my opinion, of course.

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

 

[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

 

[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

 

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

 

[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

 

[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

 

[inunxelex]

@Stillhard
try this https://play.google.com/store/apps/details?id=com.bankmandiri.mandirionline&gl=ID

 

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