yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
If that's what you meant I guess it's your call... But I didn't mention 'threads' (plural), only the one original 'alpha discussion' group who's name has been changed recently...

Since this is the definitive intended discussion group for Chinese Devs / users and most relevant discussion from Devs effecting changes / fixes / debugging is submitted there, I think you'd be making this thread impotent by ruling that discussion OT... Please don't (continue?) to make this mistake! 😬

It should be noted that both the Alpha release channel and the discussion group are in Chinese, and primary intended for Chinese Devs and users... vv only recommends 'foreigners' try her GitHub hosted releases (occasionally) when addressing TJW Magisk issues... If successful, a PR is generally then made to merge the commit directly from vvb2060:alpha (or a temp branch) to topjohnwu:master. The same goes for PRs from LoveSy (LSPosed:[temp branch]), Canyie (canyie:[temp branch]), etc.

So while Alpha, as a debug build (with telemetry also) is aimed squarely at a Chinese audience, testing with debug feedback is occasionally done by 'foreigners' through TJW issues... As vv, Canyie, Shana and others collaborate, Canyies discussion group seems to be the primary source of debugging... vv uses TJW issues to recommend her fixes occasionally...

🤠 PW
[Magisk] rodken:
Version ecc74d45-alpha (27002)

Mar 21, 2024 at 02:19

11.05 MB

alpha update log

Breaking behavior change: magiskd internal mount points are uninstalled when no longer in use.

New feature: Enhanced security mode. If it fails to boot normally twice in a row, Magisk will automatically enter safe mode the third time. In safe mode, all functions are turned off and all modules are disabled. Only the Magisk application can use su. For computer debugging, please use adb shell 'PATH=$PATH:/debug_ramdisk su'.

Magisk (ecc74d45-alpha)

[App] Delete backup files after restoring boot image

[App] does not actively request permissions

[General] Keep ROOTOVL temporary files

[App] Check and download updates via appcenter

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

[General] Make blocklist work when zygisk is not enabled

[General] Remove addon.d support

[MagiskSU] Support removal capabilities

[General] Support users to limit Root capabilities [Applications using older versions of libsu will be mistakenly identified as non-root]

[General] Automatically copy files after initial installation

[App] Add backup DoH

[General] Enhanced security mode

[App] The restart menu can be set to enter Magisk safe mode next time you boot.

[Denylist] Enhance uid tracking and automatically delete uninstalled applications from the block list. Improve app startup performance, zygisk no longer scans the application list.

[General] Improve app startup performance, zygisk no longer checks the signature of the repackaged magisk app when each app is started.

[MagiskPolicy] Significantly reduced the number of rules

Upstream update log

Magisk (81658d45) (27002)

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

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

[MagiskBoot] Support spliting kernel images without decompression

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

[App] Use user-initiated job instead of foreground services on Android 14
[Magisk] HippoMan:
These enhancements look quite promising!

Has anyone had any success or failure in upgrading Alpha 27001 to this 27002 version under Android 13?

I'm reluctant to jump in and try the upgrade myself without first seeing any reports of success, because I only have one functioning Android device now, and I need it for my work, and I don't have much free time lately for any re-flashes or re-installs in case of bootloops or bricking.

I'm running stock A13 on a Nothing 2 device.
[Magisk] elmor0:
Upgraded to Alpha 27002 fine (just make sure you unhide & restore the Magisk app back to the original APK if you have applied Magisk hide, before upgrading Alpha).
[Magisk] HippoMan:
Thank you! Are you on Android 13?
[Magisk] elmor0:
I'm on A14
[Magisk] HippoMan:
I now decided to upgrade from Alpha 27001 to 27002 on my A13 device. Just want to report that it's working fine.
[Magisk] HippoMan:
I just want to make sure that I understand something about what is stated in the previous message:

I'm running A13 and Alpha 27002. I use WiFi, and it's working. Would it therefore be safe to upgrade to 27003?

I don't know anything about "sepolicy live patching", and I therefore don't know whether or not it's in use on my device. Can someone point me to some docs about how I can check that?

Thank you very much.
[Magisk] rodken:
The last time that I checked, SEPolicy live patching is not a widely advertised feature and might not be explicitly mentioned in device settings or documentation due to the fact that it's integrated within one's kernel, which isn't typically user-accessible.

You can try:

adb shell logcat -b kernel -b security

Look for keywords or phrases that might indicate live patching activity.

sepolicy

livepatch

security patch - (could be a generic term)
[Magisk] HippoMan:
Thank you!

I ran the following:

adb shell logcat -b kernel -b security | egrep -i '(sepolicy|livepatch|security\s*patch)'

... and I then ran a number of apps on my phone. Nothing at all has been printed from the egrep-filtered logcat output, even though I've been running for around 5 monutes. I therefore assume that it would indeed be safe for me to upgrade to Alpha 27003 (at least w/r/t SEpolicy) ... correct?

PS: 27003 is not yet being offered as an update from within the Alpha manager, so I would just wait until it shows up.
[Magisk] rodken:
The lack of output from your egrep-filtered logcat doesn't necessarily guarantee a safe upgrade to Alpha 27003 regarding SEPolicy even though it's still under development as of this writing. Bear in mind, SEPolicy violations or live patching events might not always generate messages containing those exact keywords.

On the other hand, it's possible that the apps that you ran might not have triggered any SEPolicy checks or live patching activities because it's possible that they don't interact with system components in a way that would require such mechanisms.

The lack of log output is a positive sign, but should not be treated as a definitive confirmation.

This whole SEPolicy live patching scenario can be a head-scratcher.
[Magisk] HippoMan:
OK. Thank you!

I'll hold off on 27003 until I find out more about the SEPolicy conventions on my device.
[Magisk] dknight178:
Hi All. I tried updating from 27001 to 27002 but when I did, it keeps asking me to "upgrade to full magisk to finish the setup". What should I do? Thanks

- fixed by uninstalling old app and reinstalling, pls delete
[Magisk] Bulletro:
Quick question, I was looking at switching to magisk alpha but I want to double check there are no privacy concerns, as in the only telemetry/"spying" is anonymous telemetry of the app such as options, crashes etc. with no personally identifying information. Wondering if there's any other concerns I should look at before switching to Magisk Alpha as I don't mind anonymous telemetry because its apparent in canary too. If there is should I use the firewall module that @rodken has send a few pages back.
[Magisk] pndwal:
Some historical posts/responses of mine:

- https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89142186

- https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89145710

- https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89146034

- https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89148040

- https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89148753

Hope it covers concerns. 👍 PW
[Magisk] Bulletro:
Hey PW, so going over all your posts what I understand is that Microsoft has to follow data protection rules for the custom information that the author can gather and they strictly have to be like "telemetry". since it is closed source you can never 100% say what your running but since other devs may have soemtimes also committed but it should be pretty safe and all good to use since the telemetry that we know of is used is anonymous. Another quick question, is the discussion group still open to join as I was searching the pins and couldn't find any link in the Rick roll link either.

I must thank you for clearing up a lot of the conspiracies as I thought they were all pretty real, obviously there's always some sort of risk regardless but doesn't seem like much of a privacy concern especially because majority are probably running gms on their phone.
[Magisk] pndwal:
Yeah... I don't think there's much potential for abuse using MS telemetry... More simply because it's a root a solution and you must trust the devs...This should be a consideration which is why John made this change in official:

https://topjohnwu.github.io/Magisk/build.html#signing-and-distribution

https://topjohnwu.github.io/Magisk/releases/25000.html#magisksu-security-enhancements

While Alpha is unofficial Magisk, it's Devs are recognised official Magisk developers... That's why I'm more at ease with that than Delta/Kitsune or even less known builds/forks... Also, vv has traditionally used Alpha (and Shana and Canyie have other test forks) as a test base for countless innovations, fixes and compatibility enhancements destined for TJW Magisk, eg many fixes for MTK soc, many changes like refactored Zygisk etc...

Still, any root solution could be a potential liability... I recently but a lot of detail here about why banks in particular view root/mods as a liability, why these can potentially result in 'backdooring', fraud, identity/data theft etc as well as addressing some naive views about the can of worms that root (especially) can be for both users and parties developing code for the Android runtime environment... In case you're interested:

https://xdaforums.com/t/banking-app-starling-detecting-magisk.4576421/post-89454452

No... Unfortunately Join link is not available from Alpha channel now (since January):

... It's a pretty hard slog following that discussion anyway; much discussion of unrelated development(s), general Chinese banter etc etc... But FWIW, link can still be found pinned in MagiskLite channel ('small door')... 😉

Welcome... Many concerns are just hype, many others are real... Understanding root/mod methods and potential (including removal of expected checks and balances) is probably as important a factor in due diligence for modders as it is for corporate players like banks... I say 'if you don't understand this, don't try it at home'!

👀 PW
[Magisk] crypticc:
Do you mean the Rick roll video on alpha, or the one on the thread now asked Rest in Peace that used to give the code as invite to the Magisk Forum?

Of the telegram channels..

Magisk Alpha. (Active but one direction only. Rick Roll Video doesn't appear to have any clues)

Rest in Peace (the Rick roll channel)

URL near video changed now so you don't need code and it reflects to the Unofficial Magisk Forum.

Unofficial Magisk Forum and it's subforum all active. Now linked from Rest in Peace

Weak Body Strong Will (I think this is the true one you were looking for, Magisk Delta developer chat and channel kept getting renamed and then getting muted because of too much inane chatter). This has now gone private and I'd imagine because HuskyDG fed up of the sillyness, ot, and unwillingness to help oneself.

The Weak Prince Boji. (Magisk Delta). Active
[Magisk] rodken:
Version c6f07625-alpha (27002)

May 23, 2024 at 04:17

11.01 MB

[As of this writing - the link is broken to the page to scrape any changelog lingo]
[Magisk] wilsonhlacerda:
Also not available yet for direct update on Alpha Manager (maybe removed due to bugs?) . Let's wait for it.
[Magisk] pndwal:
Yeah, only in private discussion group now...

Seems TJW master commits since 27002 breaks Shamiko... ('It seems that 27003 already exploded".)

FWIW, here's Google translation of changelog:

Alpha update log

Major behavior change: Magiskd internal mount point is uninstalled when no longer in use.

New feature: Enhanced safe mode. If the device fails to boot normally twice in a row, Magisk will automatically enter safe mode the third time. In safe mode, all functions are turned off, all modules are disabled, and only Magisk application can use su. For computer debugging, please use adb shell 'PATH=$PATH:/debug_ramdisk su'.

Magisk (c6f07625-alpha)

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

• [App] Do not actively request permissions

• [General] Keep ROOTOVL temporary files

•[App] Check and download updates through appcenter

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

• [General] Remove addon.d support

• [MagiskSU] Support removing permissions

• [General] Support users to limit root permissions [Applications using old versions of libsu will be mistakenly identified as rootless]

• [General] Automatically copy files after initial installation

• [App] Disable SNI for DoH

• [Denylist] Enhance uid tracking and automatically delete uninstalled applications from the block list, improve app startup performance, zygisk no longer scans the application list.

• [General] Improve app startup performance, zygisk no longer checks the signature of the repackaged magisk app on each app startup.

Upstream changelog

Magisk (81658d45) (27002)

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

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

• [MagiskBoot] Support spliting kernel images without decompression

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

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

👀 PW
[Magisk] WhoIsJohnGalt1979:
From Magisk Alpha TG

c6f07625-alpha 27002

Shamiko-v1.0.1-341-release.zip

The version number has not changed and the update channel is not pushed.

Shamiko is an alpha version. Because the old version has compatibility issues, it needs to be upgraded together. If you are still using the old alpha version, don't upgrade.
[Magisk] dknight178:
I am using OG magisk. I've tried the latest shamiko here but it says I need to install alpha. Any workaround to get this to work to the OG magisk?

Edit: I would have used magisk alpha but it doesn't work with other modules like magic mount. I know both alpha and shamiko are closed source but shamiko was working fine with both magisk alpha and OG magisk so I was wondering if there is a way to make this work with OG magisk, hence my question.
[Magisk] chaoscreater:
I can't seem to get Magisk hide to work on my new phone (OnePlus Ace 3 on A14). It would always show Install Failed when I tried to hide the app. Doesn't matter if I use Magisk or Magisk Alpha, it's the same.

In the logs, it'll just show unable to find the file or directory. Is there a debug app that I can use to provide more logs?

UPDATE:

I got it to work. I found this tool here:

https://luckyzyx.gitlab.io/LuckyTool_Doc/en/

By using that, you can customize some of the settings on how Package Installer installs apps. You can choose settings such as allow app downgrade, etc. I applied some of the settings and then restarted. Then, I tried to hide Magisk app and it worked.
[Magisk] rodken:
Version 47e918bc-alpha 27003

July 2, 2024 at 02:48

12.08 MB

Magic (47e918bc-alpha)

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

• [App] does not actively request permissions

• [General] Keep ROOTOVL temporary files

• [App] Check and download updates via appcenter

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

• [General] Remove addon.d support

• [MagiskSU] Support removal capabilities

• [General] Support users to limit Root capabilities [Applications using older versions of libsu will be mistakenly identified as having no root]

• [General] Automatically copy files after initial installation

• [App] Disable SNI for DoH

• [Denylist] Enhance uid tracking and automatically delete uninstalled applications from the block list. Improve app startup performance, zygisk no longer scans the application list.

• [General] Improve app startup performance, zygisk no longer checks the signature of the repackaged magisk app every time the app starts.

• [General] Support riscv64

• [General] Fixed the problem that empty init_boot device cannot be updated

• [App]Fixed the problem that some device authentication will cause the authorization pop- up window to close
[Magisk] Lubo99:
Trying to update app to 27003 it says it was successful however when i open the app the version is still the same 27002 and it ask to update again...

Since root magisk is 27002 and no update available and only app update 27003 is available doesn't this mean that untill also root version for Alpha 27003 is available this will not work and I mean also shamiko update not app version update
[Magisk] gentano:
Did You unhide the Magisk App before updating? Its the most important step.

After that You can update the Magisk App or (if that fails) update through recovery (rename Magisk.apk to zip file and flash it).
[Magisk] Lubo99:
yep I did it before trying this. i am not going to attempt to do any other installs since pay app and banking apps are working.
[Magisk] zgfg:
You have to update app first, then the Magisk itself (from the updated app)

Magisk app is separate entity from the Magisk itself. You can install the app to a phone with locked Bootloader, but Magisk/root will not be installed
[Magisk] HippoMan:
I had been running Alpha 27002 on my A13 ""Nothing 2" phone for at least a few months.

I recently upgraded to 27003 via the standard "Update" (or perhaps the word is "Upgrade" ... I forget) link next to "App" on the main page of the Magisk app, and I did so without unhiding, and then I went through the "Install" link next to "Magisk" on that same page and applied the "direct" update.

Everything worked, and now I'm successfully rooted under 27003, even after numerous reboots.

... and again, I never had to un-hide the Magisk app.
[Magisk] dr.ketan:
deleted
[Magisk] zgfg:
Only in Chinese. And be ready to be kicked off from the channel
[Magisk] dr.ketan:
No worries. Digging further it seems it takes considerable time if img are packed in lz4, still it works.
[Magisk] rodken:
Version 7c0b25ca-alpha 27004

July 13, 2024 at 02:08

12.05 MB

Known issue: Online update module cannot be installed automatically, download is normal.
[Magisk] HippoMan:
I just now upgraded as follows from Alpha 27003 to Alpha 27004 on my stock A13 Nothing 2 device. Everything is working fine.

Here's how I did it (and I know that it's not the only way) ...

(1) Download the Alpha-27004 APK from the Telegram Magisk Alpha channel.

(2) Un-hide my Alpha 27003 app.

(3) Install the Alpha 27004 APK.

(4) Open the Magisk app and select "Install"

(5) Select "Direct" to install the upgrade.

(6) Select "Reboot"

(7) Test Magisk after reboot completes. It all tested well.

(8) Re-hide Magisk

(9) Reboot just in case.

(10) Re-test Magisk after reboot completes. It all tested well.

When I previously upgraded from Alpha 27002 to Alpha 27003, I skipped the un-hide and re-hide steps, and it worked fine. But this time, I didn't want to take any chances.

And also, I didn't need to manually download and update the APK in the past for 27003. The "Update" button on the main Magisk page took care of that. But this time it's been reported here that the "Update" doesn't work for this 27004 release, which is why I got the 27004 APK from the Telegram channel.
[Magisk] rodken:
Translated from a user from another social medium:

Some brave people were saying that the official 27005 had a small bug with SE rules - root was detected with basic checks.

On the flip side of the coin, root has always been detectable

and the conversation immediately migrated to 27006 which was released on:

Version 0495468d-alpha (27006)​

Jul 25, 2024 at 05:59

12.2 MB

alpha update log

Breaking behavior change: magiskd internal mount points are uninstalled when no longer in use.

New feature: Enhanced security mode. If it fails to boot normally twice in a row, Magisk will automatically enter safe mode the third time. In safe mode, all functions are turned off and all modules are disabled. Only the Magisk application can use su. For computer debugging, please use adb shell 'PATH=$PATH:/debug_ramdisk su'.

Magisk (0495468d-alpha)

[App] Delete backup files after restoring boot image

[App] does not actively request permissions

[General] Keep ROOTOVL temporary files

[App] Check and download updates via appcenter

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

[General] Remove addon.d support

[MagiskSU] Support removal capabilities

[General] Support users to limit Root capabilities [Applications using older versions of libsu will be mistakenly identified as non-root]

[General] Automatically copy files after initial installation

[App] Disable SNI for DoH

Upstream update log

Magisk (0495468d) (27006)

[MagiskInit] Fix regression with sepolicy.rule loading

Diffs to v27.0

[General] Support 16k page size

[General] Add support for RISC-V

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

[Core] Remove unnecessary mirror for magic mount

[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

[MagiskBoot] Support spliting kernel images without decompression
[Magisk] HippoMan:
I just now upgraded as follows from Alpha 27004 to Alpha 27006 on my stock A13 Nothing 2 device. Everything is working fine.

Here's how I did it (and I know that it's not the only way) ...

(1) I un-hid my Alpha 27004 app.

(2) I rebooted (just in case)

(3) I launched Alpha and selected "Update ... 27006" on the Magisk home screen

(4) After update completed, I rebooted (just in case)

(5) I opened the Magisk app and selected "Install ... 27006"

(6) I selected "Direct Install" to install the upgrade.

(7) After the upgrade completed, I selected "Reboot"

(8) I relaunched Magisk, and it indeed showed that 27006 is running.

(9) I tested Magisk after reboot completed. It all tested well.

(10) I re-hid Magisk

(11) I rebooted (just in case)

(12) I re-tested Magisk after reboot completed. It all tested well.
[Magisk] fbirraque:
I also do things step by step like you.

Always the safest way!