yashsingh1/xdaforums huggingface dataset:
[Magisk] rodken:
The latest Magisk Alpha Release

-- bbf9756b-alpha 26203.

Magisk Changelog v26.2

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

-- [MagiskBoot] Support cpio files containing character files

-- [MagiskBoot] Support listing cpio content

-- [MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

-- [Daemon] Make daemon socket a 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

-- [MagiskPolicy] Fix patching extended permissions

-- [MagiskPolicy] Support more syntax for extended permissions

-- [MagiskPolicy] Support printing out the loaded sepolicy rules

-- [App] Support patching boot image from ROM zips

-- [App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

Spoiler content hidden.
[Magisk] immortalwon:
New magisk alpha 26.3 now fixes the problem with one plus devices. Working good on android 11.
[Magisk] WhoIsJohnGalt1979:
New update

(Google Translate to English of attached changelog)

Significant behavior change: magiskd is now in a standalone mount namespace, which is also the global mount namespace for su. Most su use cases will not be affected, if you want init to mount the namespace, change it to su -t 1.

Magic (7826d752-alpha)

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

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

[General] does not automatically unlock the device block

[General] Delete the sepolicy temporary file

[General] Rewrites MagiskHide with logcat implementation. Do not enable this feature on devices with abnormal logging systems.

[App] does not actively request permission

[Zygisk] unmount mounts do not skip com.android.systemui

[General] Removes addon.d support

[General] Hides the magisk internal mount point

[General] To remove the writeable exception for /system/etc/hosts, modify /data/adb/modules/hosts/system/etc/hosts

[Zygisk] refactoring loads in the same way as riru [unstable in testing].

[MagiskSU] supports removal of powers

[General] supports user restriction of root privileges [applications using older versions of libsu will be incorrectly identified as unrooted].

[App] Remove fingerprint and biometric permissions
[Magisk] Elsrougy:
Same here. Working fine OP8Pro OOS11
[Magisk] genesis89:
Anyone here using official Lineage? Do I need to dowload and patch the new boot every week or can I just use existing patched boot? I know it only takes a minute to patch it but I'm lazy sometimes lol. Do the lineage maintainers update/modify the boot files every week? I'm using LOS20 on my Poco F3. Or is there a better way to do flash the patched boot without PC? My phone loses root access after every weekly update.
[Magisk] pndwal:
A benefit of MS telemetry for China users:

https://install.appcenter.ms/users/vvb2060/apps/magisk/distribution_groups/public

从 7826d752-alpha 起，可以通过网页直接下载，由 Azure 边缘网络提供文件分发支持

GitHub文件仓库同时停止更新

从下一个版本起，应用内更新使用 appcenter API，屏蔽 api.appcenter.ms 将无法检查更新，屏蔽 *.azureedge.net 将无法下载apk

-----​

https://install.appcenter.ms/users/vvb2060/apps/magisk/distribution_groups/public

From 7826d752-alpha onwards, direct download via webpage, supported by Azure edge network for file distribution

The GitHub file repository stops updating at the same time

From the next version, in-app updates use appcenter API, blocking api.appcenter.ms will not be able to check for updates, blocking *.azureedge.net will not be able to download apk

-----​

内部测试，改成了 appcenter 的应用内更新，位于中国大陆的可以试试能不能不翻墙完成下载。

--------

For internal testing, it has been changed to appcenter’s in-app update. If you are located in mainland China, you can try to complete the download without going over the wall.

-----​

... Previously, Chinese users had to use vpn to update from github source...

👀 PW
[Magisk] mGforCe:
Why do you need to reflash all modules? Are they not saved when you just update?

PS: I am new to Alpha. Have been using Magisk Delta for quite sometime, but after reading a few posts from @pndwal about Alpha and its NB-Z, am thinking to explore.

Will I have to clean flash? Like restore old boot.img, patch boot.img etc. Mine in A/B slot device (Nothing Phone 1)

Or from current Magisk Delta, I just flash Magisk Alpha? Thus have all modules saved too
[Magisk] rodken:
Clearly an OCD moment for me to ensure stability. No - you do not have to reflash all of the modules.

Refer to the OP regarding converting from another fork of Magisk.
[Magisk] zgfg:
Generally, you can convert between Magisk forks by Direct Unstall, and that will preserve modules

However, some issues may occur (just warning you, I don't use Alpha but I eg converted from official Canary to Delta)

- Delta saves UnmountModules list to different 'tab' in memory than where official Magisk saves DenyList

- When I converted from official Canary to Delta, it correctly moved DemyList to UnmountModules list but I don't know how would it work when you convert from Delta to Alpha (I bet that Alpha cares how to convert from official Magisk DenyList, but not sure about Delta UnmountModules) and specially don't know how would it go if you are concerthing from Delta SuList (white mode for UnmountModules)
[Magisk] WhoIsJohnGalt1979:
This is my dumbed down version of this post https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-88851739 two pages back, which allowed me to transition from Stable Magisk to Alpha without having to reflash any modules etc.

1. Put the phone in airplane mode.

2. If you have hidden current magisk, unhide it.

3. Rename alpha.apk to alpha.zip

4. Flash alpha.zip with current magisk. Don't reboot.

5. Delete the magisk folder from data-adb. Also remove magisk.db file from the same location.

6. Uninstall the current magisk application which you had unhidden in step 2.

7. Reboot

8. Remove airplane mode to complete magisk installation

9. You would be prompted to reboot when you enter the new magisk alpha app. Do that. Once rebooted, open Magisk and do a direct installation to be doubly sure that magisk is properly installed with root.

10. Make sure that in all this process do no open play store or any of the applications that you had in Deny list.

11. You will find that all the apps in deny list would be unchecked. Re-check the same applications once again

12 Reboot

13 Profit
[Magisk] mGforCe:
Thanks WhoIsJohnGalt1979
[Magisk] supermansaga:
Thanks. Have you guys heard the Intune Company Portal 5.0.5981 issue yet? Is Alpha still better in terms of hiding? Can it tackle Google One VPN on rooted phone? Thanks
[Magisk] supermansaga:
I finally tried Alpha. But it seems Shamiko can't enter whitelist mode any more per the old trick at https://magiskcn.com/shamiko-whitelist. How can I fix this? Company Portal 5.0.5975 and a Bilt banking app is totally detecting root. I am hoping whitelist mode can help me. Thanks
[Magisk] supermansaga:
I finally realized the Shamiko that came with Alpha simply can't have whitelist mode, unless mistaken. So I removed it and re-installed one on my own and this time I could find it in the usual path and whitelist mode can be enabled, though at this point, Intune Company portal 5.0.5975 can no longer work and we are forced to update to 5981 which at this point, none could handle.
[Magisk] WhoIsJohnGalt1979:
It is an alpha version because only alpha has compatibility issues (translated using google translate)

Shamiko-v0.7.3-183 released in alpha TG group

@westruk I am merely updating the forum that the alpha magisk group has released a new alpha update for Shamiko. If you are interested in "what it means" kindly reach out to the developers who released it
[Magisk] westruk:
Since you decided to post it here, please explain what it means.
[Magisk] kevinco1:
This is what you get when you have an insular community who won't dare reach out or let anyone contact them if you aren't from the mainland
[Magisk] mGforCe:
I switched from Magisk Delta to Magisk Alpha today as couple of bank apps from India were giving a hard time.

Apps those were hidden with Magisk Delta (refer this post for details on my setup) continue to work as usual.

But apps like IndusInd Bank (link) still detecting root. BHIM app (link) still crashing.

So that way no changes observed.

PS: My setup with Alpha has been as below:

Nothing OS Android 13, boot-loader unlocked & rooted

Magisk Alpha Latest 26301, renamed Magisk Manager

Magisk Modules like:

USNF v2.4.0MOD_1.3

SafetyNet Sensitive props v3

Zygisk LSposed v1.9.1 (6990)

Shamiko v0.7.3 (183), the latest one for alpha

Under Magisk settings, have configured Unmount and all these bank apps are selected there.

Within LSposed I have following modules active:

BootloaderSpoofer 1.2

IAmNotADeveloper 1.1.0

Core Patch 4.2

Guide 1.1.2

HMA 3.2

Pixelify GPhotos

All good in TB Checker, Rootbeer, Ruru etc.

So really lost why these 2 apps are still not working.

PS: I am able to use other Indian bank & finance apps like

iMobile, Kotak, IDFC, HDFC, Paytm, Payzapp, PhonePe, HSBC, CitiBank, Axis
[Magisk] WhoIsJohnGalt1979:
Hello,

IndusInd bank works fine on alpha. Only suggestion: kindly disable Developer options. I can't test BHIM as there's no compatible version for A14 QPR1 which am on currently.
[Magisk] asripath:
If you are on 7826d752-alpha 26301 alpha

Try shamiko alpha version
[Magisk] mGforCe:
As I mentioned, am using Shamiko v0.7.3 (183), one for alpha only.
[Magisk] mGforCe:
Hmm. For me, the app opens for 1-2 seconds (ask for login, as already registered from earlier) and then open browser with error "rooted".
[Magisk] mGforCe:
In Magisk Alpha, after initial setup, now super user access prompt is not coming.

Apps are straight away denied access. Any idea?

This is for Xposed Module apps like HMA, Pixelify GPhotos etc

PS: I have not changed anything in app settings. Automatic Response is as Prompt

EDIT: Solved. The renamed Magisk Manager (stub) was wrongly hidden in HMA. So I corrected it and now requests are coming. But HMA still not getting Root access.
[Magisk] zgfg:
If you are switching from official Magisk or Delta, did you delete their Magisk apps (and reboot)?
[Magisk] mGforCe:
Yes, had deleted Magisk.db and Magisk folder under data/adb. Followed WhoIsJohnGalt1979's post for switching

Further, as I edited above, the issue was because the renamed Magisk app was hidden wrongly in HMA. Corrected it and now prompt is visible.

:)
[Magisk] MarkLev:
So between Magisk Alpha and Magisk Delta, which one is better in term of hidding root? Which one is recommended?
[Magisk] Slim2none4u:
Tastes Great!! ................Less filling!!!!

Come on man lmao!!

Hundreds of people use these and you wanna ask which is "better" and or "recomended"

Just stop.
[Magisk] MarkLev:
so which one?
[Magisk] westruk:
Delta in my opinion
[Magisk] Slim2none4u:
Clearly just a troll
[Magisk] MarkLev:
Yeah, and you still miss the main point which is "which one?"
[Magisk] sawdoctor:
Which one is the one that works best for you. There's no "universal best for hiding" depending on phone/which apps you want to hide/which mods you have installed you will have different luck with all 3 variants of Magisk. For me official Canary with just deny list enforced makes all my banking apps work but other people with the same apps need shamiko or HMA. One thing i will say it's quite often an lsposed/xposed mod that triggers root detection
[Magisk] supermansaga:
In that regard, we should really not use LSPosed/Xposed. It appears to be an outdated technology. But damn. GPS Setter could still be using it.
[Magisk] sawdoctor:
Lsposed is actively maintained, it's always been modules that got detected for me. App settings reborn and gravity box got detected for me
[Magisk] HippoMan:
What non-outdated technology do you recommend as an alternative?

And as you know, it's already been mentioned above that LSPosed itself is still actively being worked on.
[Magisk] supermansaga:
As a layperson, I would wonder if they can just do Magisk modules instead of LSPosed modules
[Magisk] HippoMan:
Quite a number of problems have been reported in these threads about the existence of certain Magisk modules causing root-or-mod detection, and possibly even boot loops.

So Magisk modules in and of themselves are not necessarily panaceas, either.
[Magisk] Lord Sithek:
I'm not an expert either, but I know that both work differently and generally they can't be exchanged
[Magisk] WhoIsJohnGalt1979:
Reaching out for some guidance. While trying to flash magisk-overlaysfs in magisk, it fails/aborts with Setup ext4 image failed, abort message. Not sure whats going wrong. I have a feeling something around here in causing it to fail.

if [ ! -f "/data/adb/overlay" ] || ! test_mount_image; then

rm -rf "/data/adb/overlay"

ui_print "- Setup 2GB ext4 image at /data/adb/overlay"

ui_print " Please wait..."

if ! create_ext4_image "/data/adb/overlay" || ! resize_img "/data/adb/overlay" 2000M || ! test_mount_image; then

rm -rf /data/adb/overlay

abort "! Setup ext4 image failed, abort"
[Magisk] rodken:
Seems like a possible free space issue?

Have you tried to redownload a fresh copy > disable all other Magisk modules > reboot before flashing magisk-overlaysfs?
[Magisk] rodken:
Update

Magisk 15e13a8d-alpha (26302)

No changelog as of this writing.

This version abandons riru compatibility because it hides internal mount points.
[Magisk] HippoMan:
Thank you!

I'm just wanting a slight clarification in order to help my understanding: what is "it" in this case? Is riru the entity that hides internal mount points, or is Alpha itself the internal mount point hider?
[Magisk] rodken:
Bookmark this site which should shed some light once updated.
[Magisk] zabhi:
Memory card not visible in MT manager after update to "15e13a8d-alpha".. is there any way to downgrade "7826d752-alpha" version?
[Magisk] immortalwon:
Uninstall the apk and install the version you want. You will still have root because the boot.img was modified.
[Magisk] zabhi:
I already tried. Unfortunately not working. 15e13a8d-alpha isn't open after installation
[Magisk] immortalwon:
Which version are you trying to install? Verions in the 26.1 to 26.2 range were buggy and did not work.
[Magisk] zabhi:
I want to install Magisk-7826d752-alpha(26301)

Butt after install app isn't open.
[Magisk] immortalwon:
Which device are you using? I would suggest to flash 26.3 and install the 26.3 apk of magisk.

App Center

install.appcenter.ms

EDIT: Actually v 26.3 is not on the link because they recently just moved to appcenter hosting. I will try to upload apk of 26.3

EDIT2: I believe I made a mistake, 26301 is the earliest 26.3 version that worked for oneplus. Maybe it has something to do with samsung devices.
[Magisk] zabhi:
In new new version magisk alpha only MT manager are not showing memory card. Why am facing this issue?

Samsung s10plus android 12

Edit

I don't want to flash my phone :(
[Magisk] solar666:
Same here with root explorer.

But in oder to see my sdcard content again I just closed the tab in root explorer and re-opened it using the shortcut provided by root explorer, not sure if this helps for you as well.
[Magisk] zabhi:
Nope :(
[Magisk] rodken:
There is always a method to downgrade but not advisable when it comes to the Alpha version.

You might need to reboot again or you need to start from scratch and Uninstall MT Manager > reflash the boot.img that hopefully you backed up before flashing any version of Magisk.

You don't need to reflash your phone, just the original boot.img or you can change the name of the Magisk.apk to uninstall.zip and try to sideload it to uninstall Magisk if you don't have a Custom Recovery, but remember to remove all of your modules, if any before proceeding.
[Magisk] pndwal:
Some relevant posts from official TG discussion:

重大行为变化：magiskd内部挂载点对外隐藏，部分系统挂载点不会被镜像。 列表是："/apex", "/dev", "/proc", "/storage", "/sys", MAGISKTMP

--------

Major behavior change: magiskd's internal mount points are hidden from the outside, and some system mount points will not be mirrored.

The list is: "/apex", "/dev", "/proc", "/storage", "/sys", MAGISKTMP

Zap! | 把你的聊天记录给我看看喵！:

alpha合并代表着next magisk大概率要合并（）

--------

Alpha merge means next magisk has a high probability of being merged ()

陰角Tomorin與陽角Saki的樂隊革命:

如果很多app都烂了，估计不会

--------

If many apps are broken, probably not

只是我不理解，这些挂载点为什么会有人依赖

--------

It’s just that I don’t understand why anyone relies on these mount points.

我其实想在开机完成后把整个mirror卸载

--------

I actually want to uninstall the entire mirror after booting.

很多app会扫描mounts，条目太多影响性能

--------

Many apps scan mounts, and too many entries affect performance.

颜 小雅:

怎么解决

--------

How to deal with it

陰角Tomorin與陽角Saki的樂隊革命:

用官方magisk

--------

Use official magisk

Zap! | 把你的聊天记录给我看看喵！:

这下坏了，

--------

It's broken now,

陰角Tomorin與陽角Saki的樂隊革命:

preinit还需要研究，我想想有没有更好办法，之前的符号链接其实不错

--------

Preinit still needs to be studied. I wonder if there is a better way. The previous symbolic link is actually good.

... So many in Alpha discussion are rolling back ATM... 👀 PW
[Magisk] rodken:
Very interesting...

I always like to share with folks that whenever a new version of Alpha is released, tread lightly and remember to clear the cache and data of the Magisk app after flashing any new version of Alpha whether or not one is running a Custom ROM.

A reboot is not required, but will not hurt after clearing the cache and data of the Magisk app.

The same treatment should apply to LSPosed whenever a new nightly build of LSPosed is released, but the LSPosed nightly build treatment should be followed by a reboot.

Small disclaimer: Maybe, Alpha is more compatible with Custom ROMs on different devices and Android versions which of course, would make it easier to unroot a device if needed.
[Magisk] pndwal:
Clearing cache and data of full Magisk App will do practically nothing for compatibility unfortunately as no configuration data resides there (other than the odd app setting, perhaps only the hide flag for Magisk download source notice which will be reset)... It's similar for Magisk hidden as data in stub; clearing data in this case will force complete Magisk binaries to be called again to populate stub data, but this contains no configuration files/data... The configuration remains intact (warts and all) in /data/adb.

To restore Magisk to initial (clean) installation condition is simple however, and should be done especially if downgrading or changing between official and various forks (by using existing root); simply clear all data in /data/adb, reboot and configuration will be rebuilt clean... Of course you'll need to set up modules, Superuser permissions, denylist etc again... To retain modules but reset the basic configuration settings, clear all data in /data/adb/magisk as well as database file, /data/adb/magisk.db ...

👀 PW
[Magisk] rodken:
Therefore, the need to delete /data/adb/magisk.db should allow Magisk to regenerate magisk.db on restart which might fix any underlying issues?

Possibly, backing up magisk.db and reinserting it after installing Magisk could be another method?
[Magisk] pndwal:
Yup... I'd also wipe the rest of the configuration in /data/adb/magisk directory to force proper rebuild however...

Well, not issues in a build, but configuration incompatibilities between builds...

I wouldn't... That will potentially restore issues... Configuration will rebuild as expected for a build simply by deleting and rebooting; incompatibilities from mismatched builds with effectively be removed also... PW
[Magisk] pndwal:
For any wanting to downgrade:

You can use Direct Install to install official Debug App and Magisk which will bypass magisk.d daemon version (and signature) checks, then you'll be able to take Direct Install again to install older Alpha Magisk etc...

A simpler method also using existing root for downgrading is:

Rename older Magisk.apk to .zip and flash from App as a module... (Allows downgrade by down-dating Magisk daemon that performs version checks before installing the App)...

To avoid unexpected issues, delete /data/adb/magisk.db file and /data/adb/magisk directory contents and reboot... Magisk configuration files will be rebuilt...

Before opening, uninstall App and install older version...

🤠 PW
[Magisk] rodken:
@Homeboy76 Maybe, you can insert the following quote into the OP?
[Magisk] tyler19820201:
Today i did update alpha to 26302 but i did downgrade back to 26301 as some app does not work which requires root access. I use AppManager https://github.com/MuntashirAkon/AppManager which does require root to work fully. With the 26301 i have got no issue at all. However after updating to 26302 the app can not get root access.

Of course i did try reinstall the app and delete app data but does not work. Also i did reinstall Alpha from scratch but does not help at all. The only thing does work is to go back to 26301.
[Magisk] Homeboy76:
Added this to OP.
[Magisk] Steps Parku:
unfortunately, i flashed boot.img instead of init_boot. device went into boot loop, then i tried to flash stock boot together with init_boot all stocked. but it still won't fix boot loop. now i managed to change the active slot to b but still it bootloops. can anyone help me get out of this situation?
[Magisk] Homeboy76:
Can you boot fastboot mode?

What device/phone?

What command did you use to flash the boot img?
[Magisk] Steps Parku:
Device is oneplus 11. and yes i can fastboot. it keeps restarting and going into fastboot automatically
[Magisk] Homeboy76:
Ok, how did you flash the magisk_patched....img:

fastboot flash boot magisk_patched...img ?
[Magisk] Steps Parku:
Exactly..
[Magisk] Homeboy76:
If that is all you flashed, this command should fix it:

fastboot flash boot --slot all boot.img
[Magisk] rodken:
Magisk bb39a524-alpha (26302)

Changelog:

Magisk (bb39a524-alpha)

[App] Delete backup files after restoring boot image

[General] Do not automatically unlock device blocks

[App] does not actively request permissions

[General] Keep ROOTOVL temporary files

[Zygisk] Uninstall and mount without skipping com.android.systemui

[App] Check and download updates via appcenter

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

[General] Rewrite MagiskHide and use logcat to implement it. Do not enable this function on devices with abnormal log systems.

[General] Remove addon.d support

[General] Hide and clean magiskd internal mount points

[General] Cancel the writable exception of /system/etc/hosts, please modify /data/adb/modules/hosts/system/etc/hosts

[Zygisk] Refactor the loading method, similar to riru

[MagiskSU] Support removal capabilities

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

[App] Update DoH server

[General] Safe mode no longer mounts su to /system/bin/su. Please use /debug_ramdisk/su for adb shell.

[Zygisk] Fix fd cleaning logic

Spoiler content hidden.
[Magisk] WhoIsJohnGalt1979:
@rodken thank you for sharing the update. Could you kindly check something for me while you are on this new version. Please download the APK from https://github.com/MuntashirAkon/AppManager and install the latest version. Would request you to check if the app opens after assigning root privileges. The 15e13a8d-alpha 26302 version had broken the app where the app froze on the initialize page.
[Magisk] trojblue:
Magisk Alpha's telegram group literally says "带遥测"(with telemetry) and "无隐私协议"(no privacy rules).

Given that it has control over pretty much everything on the phone I'm concerned about this