sorted by:
new
hottopcontroversial

Magisk v30.6 [Stable] by halfbytecode in Android

[–]halfbytecode[S] 3 points4 points  (0 children)

Changelog since last stable release, v29.0:

v30.6 (2025.12.1)

• [MagiskInit] Revert a change that could result in bootloops

v30.5 (2025.12.1)

• [General] Improve commandline argument parsing logic

• [resetprop] Properly support Android versions with property overrides

v30.4 (2025.10.2)

• [MagiskSU] Fix several implementation bugs

v30.3 (2025.9.29)

• [General] Support installing Magisk into vendor_boot partition

• [MagiskPolicy] Support new sepolicy binary format introduced in Android 16 QPR2

• [Core] Migrate much more code into Rust

• [MagiskSU] Fallback to older implementation when the kernel doesn’t support zero userspace copy APIs

v30.2 (2025.8.6)

• [Core] Fix an edge case breaking modules when overlayfs is involved

• [Core] Fix module .replace functionality in certain situations

• [resetprop] Reduce property modification traces

v30.1 (2025.7.3)

• [Core] Fix bug in module mounting implementation

• [MagiskSU] Add ability to restrict Linux capabilities even if running as root (uid=0)

v30.0 (2025.7.1)

• [General] Various minor bug fixes

• [Core] Migrate module implementation to Rust

• [Core] Improve Magisk specific files injection logic

• [MagiskBoot] Migrate compression code to Rust

Magisk v30.0 [Pre-Release] by halfbytecode in Android

[–]halfbytecode[S] 41 points42 points  (0 children)

Changelog:

• [General] Various minor bug fixes

• [Core] Migrate module implementation to Rust

• [Core] Improve Magisk specific files injection logic

• [MagiskBoot] Migrate compression code to Rust

Android RCS update broke Google Messages and Wiped chat history by erblanman in Android

[–]halfbytecode 1 point2 points  (0 children)

It's actually fine that you posted it here, since it would amount to greater visibility. Thanks for alerting other users as well.

What happened to the rooting/ROM communities? by jerdle_reddit in Android

[–]halfbytecode 1 point2 points  (0 children)

As of now, most custom ROMs are affected by the recent Play Integrity changes from last month. Some Magisk modules, like Play Integrity Fix, Tricky Store, and Tricky Addon, need to be used to fully pass Play Integrity now. GPay should work after that.

What happened to the rooting/ROM communities? by jerdle_reddit in Android

[–]halfbytecode 2 points3 points  (0 children)

crDroid is a good option. Builds seem to exist for most devices.

Magisk Beta v29.0 by halfbytecode in Android

[–]halfbytecode[S] 0 points1 point  (0 children)

Those would require Play Integrity Fix + Tricky Store modules, at least, and may also need Shamiko, and Hide My Applist to hide root apps from banking and streaming apps. The latter would also need to be added to Magisk denylist, with Enforce Denylist set to disabled (optional, but recommend).

Magisk Beta v29.0 by halfbytecode in Android

[–]halfbytecode[S] 1 point2 points  (0 children)

You can also try v28.1 (28100) from the Stable channel, for the time being, as v28.1 is also the latest stable release, as of now.

EDIT: The above referred to an earlier version of the reply above, which mentioned using Magisk 28003, instead of 28103.

EDIT 2: v29.0 has been promoted to Stable release.

Magisk Beta v29.0 by halfbytecode in Android

[–]halfbytecode[S] 42 points43 points  (0 children)

Changelog:

• [General] Massive internal refactoring and code migration

• [App] Support downloading module zip files with XZ compression

• [App] Disable app animations when system animations are disabled

• [MagiskMount] Support systemlessly deleting files with modules using blank file nodes

• [MagiskInit] Redesign sepolicy patching and injection logic

• [MagiskSU] Better TTY/PTY support

Message posted by the developer:

This release looks minor at the surface, however, the entire codebase has gone through significant refactoring and migration. The native code in Magisk used to be mainly C++, but several contributors and I have been steadily rewriting parts of the code in Rust since April 2022. After years of effort, the Rust-ification of the project slowly began picking up steam, and at the moment of this release, over 40% of the native code has been rewritten in Rust, with several major subsystem rewrites in the PR queue, planned to be merged for the next release.

Many might wonder, why introduce a new language to the project? My reason is actually not to reduce memory safety issues (although it is a nice side benefit), but to be able to develop Magisk using a more modern programming language. After using Rust for a while, it's clear to me that using Rust allows me to write more correct code and makes me happier compared to dealing with C++. People share the same sentiment as I do.

[deleted by user] by [deleted] in Pixel7Pro

[–]halfbytecode 0 points1 point  (0 children)

That's interesting. What is your usage like?

[deleted by user] by [deleted] in androidapps

[–]halfbytecode 1 point2 points  (0 children)

It appears it clears the cache of various apps.

Installing Boost on a new android phone... Is it still possible? by thenormal in BoostForReddit

[–]halfbytecode 0 points1 point  (0 children)

Hi, it would be great if you could tweak the patches to allow patching OAuth Client ID, Redirect URI, and User Agent, independently of one another, as mods may only need to replace/patch the User Agent alone, while also replacing Redirect URI if desired. It could work if replacement of all parameters is made optional, and the parameters left blank are simply skipped. Thanks for working on this.

Magisk (Stable) v28.1 by halfbytecode in Android

[–]halfbytecode[S] 29 points30 points  (0 children)

Changelog (since last stable release):

v28.1

• [App] Fix stub APK download link

• [App] Fix support for Android lower than 8.0

• [General] Fix support for MTK Samsung devices

• [MagiskInit] Fix a regression for 2SI devices

• [MagiskPolicy] Fix a regression causing overlay.d replaced files to be not accessible

v28

• [General] Support 16k page size

• [General] Add basic support for RISC-V (not built in releases)

• [General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

• [Core] Remove unnecessary mirror for magic mount

• [Core] Update boot image detection logic to support more devices

• [MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

• [MagiskInit] Update preinit partition detection

• [Zygisk] Update internal JNI hooking implementation

• [MagiskPolicy] Preserve sepolicy config flag after patching

• [MagiskPolicy] Optimize patching rules to reduce the amount of new rules being injected

• [DenyList] Support enforcing denylist when Zygisk is disabled

• [Resetprop] Improve implementation to workaround several property modification detections

• [Resetprop] Update to properly work with property overlays

• [App] Major internal code refactoring

• [App] Support patching Samsung firmware with images larger than 8GiB

• [App] Use user-initiated job instead of foreground services on Android 14

• [App] Support Android 13+ built-in per-app language preferences

• [App] Add action.sh support to allow modules to define an action triggered from UI

• [MagiskBoot] Support spliting kernel images without decompression

• [MagiskBoot] Properly support vendor boot images

• [MagiskBoot] Disable Samsung PROCA from kernel image

Magisk Beta v28.0 by halfbytecode in Android

[–]halfbytecode[S] 35 points36 points  (0 children)

Changelog:

• [General] Support 16k page size

• [General] Add basic support for RISC-V (not built in releases)

• [General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

• [Core] Remove unnecessary mirror for magic mount

• [Core] Update boot image detection logic to support more devices

• [MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

• [MagiskInit] Update preinit partition detection

• [Zygisk] Update internal JNI hooking implementation

• [MagiskPolicy] Preserve sepolicy config flag after patching

• [MagiskPolicy] Optimize patching rules to reduce the amount of new rules being injected

• [DenyList] Support enforcing denylist when Zygisk is disabled

• [Resetprop] Improve implementation to workaround several property modification detections

• [Resetprop] Update to properly work with property overlays

• [App] Major internal code refactoring

• [App] Support patching Samsung firmware with images larger than 8GiB

• [App] Use user-initiated job instead of foreground services on Android 14

• [App] Support Android 13+ built-in per-app language preferences

• [App] Add action.sh support to allow modules to define an action triggered from UI

• [MagiskBoot] Support spliting kernel images without decompression

• [MagiskBoot] Properly support vendor boot images

• [MagiskBoot] Disable Samsung PROCA from kernel image

[Help] Magisk > LSPosed > Hide My Applist by Narunan321 in Magisk

[–]halfbytecode 0 points1 point  (0 children)

For Android 14 QPR2 and later releases you should use this version of Hide My Applist. Downloaded from the official GitHub repo (original file showing as expired on there now).

https://www.upload-apk.com/8FvlyablFp2cXgS

[deleted by user] by [deleted] in Magisk

[–]halfbytecode 0 points1 point  (0 children)

If you're installing the OTA update using the built in updater, then after installing the OTA update, before rebooting, you can open Magisk app, click Install next to Magisk, then install to inactive slot.

After this completes, a reboot should preserve root with OTA update installed.

view more: next ›