yashsingh1/xdaforums huggingface dataset:
[Magisk] WhoIsJohnGalt1979:
@zgfg Sorry to hear about the jam that you currently are in. Absolutely knocks me down when things just out of nowhere fall apart. Hope things get better soon for you. Hang in there.
[Magisk] HippoMan:
I understand how it's a very mixed blessing.

I'm optimistic that the problems you're facing with phones, authorization, etc. etc. are going to be ultimately surmounted, but I realize that it won't be without some struggle. I think I don't need to say, "hang in there", because I see you are already doing so.

I hope it all gets resolved quickly!

And also, I do understand the "life much easier" part. I too have been pulling back somewhat from XDA over the past month or so ... but in my case, it's not because of being forced by circumstances. It's totally voluntary. I now have more empty space in my life that I can fill with some things that are a bit more interesting and rewarding ... and also positive.

I'm just looking forward to hearing from you here that things have been resolved!
[Magisk] rodken:
Version a0b8aa4d-alpha-2 (26404)

Jan 07, 2024 at 08:45

12.45 MB

alpha update log

Breaking behavior change: magiskd is now in a separate mount namespace, which is also su's global mount namespace. Most su use cases will not be affected. If you need init to mount the namespace, change su -t 1.

Major behavior change: magiskd internal mount points are hidden from the outside and uninstalled when no longer in use.

New feature: Enhanced security mode. If it cannot boot normally, Magisk will automatically enter safe mode after a forced restart. 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'.

[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

[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

[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

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

[MagiskInit] Avoid patching init files for 2SI devices

[MagiskInit] Check init.rc full path

[General] Asynchronously execute pm command

[General] Delete the image, it is no longer needed for atomic mount

[General] After the magisk tmpfs path is fixed, magic mounting is no longer necessary and makes it optional.

[General] Enhanced security mode

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

Upstream update log

Magisk (65207f96) (26404)

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions
[Magisk] mavrovelos:
I'm on a rooted pixel 7 pro with magisk Delta(Kitsune) installed. How can I move to magisk Alpha? How can I install it? Any help appreciated
[Magisk] rodken:
Refer to this post regarding switching between different forks of Magisk.
[Magisk] Dr.][No_WaY:
I got extensive battery drain after alpha update , any body have custom link for previous versions?
[Magisk] Homeboy76:
That link is also in the OP. :)

Changing/Downgrading Magisk?
[Magisk] mavrovelos:
Changing from Delta to Alpha. So to get it right: I rename the alpha.apk file to zip, I install it as a module . Is deleting /data/adb/magisk.db file and /data/adb/magisk directory contents necessary after that?
[Magisk] Homeboy76:
@pndwal, wrote the detailed description of how to downgrade or change bewteen different Magisk forks from different Devs. Deleting the "/data/adb/magisk.db file and /data/adb/magisk directory contents" were in his instructions.

Therefore, I am referring your question to @pndwal.
[Magisk] pndwal:
I wrote:

I recommend such a wipe any time you suspect Magisk configuration may have become corrupted, when downgrading, if refactoring or test builds/forks (CI/actions run builds etc) mean that the implementations may vary, if moving between official and forks that use customised configurations etc... doing so will effectively give you a fresh Magisk install, like taking the Uninstall Magisk, Complete Uninstall option (which deletes everything in /data/adb) rather than just Restore Images option... Nb. Installing various Magisk builds over another (including Direct Install for updating) DOES NOT provide automatically for a clean install, rather is should be considered 'dirty' and prone to compatibility issues...

The Complete Uninstall option is not necessary however as deleting /data/ADB contents and rebooting achieves a complete configuration rebuild without actually restoring stock/unpatched images...

Nb. Alpha recently claimed compatibility with TJW Magisk configuration (so you can safely swap between the two without configuration issues) but this hasn't always been the case and I wouldn't bet it will remain so always... Forks like Delta, late Custom Magisk (@TheHitMan) etc are very experimental and likely to contain major configuration differences... Back in the day @TheHitMan detailed the requirement to clear /data/adb when migrating to his fork/reverting to official builds...

I detailed how to reset basic configuration but keep modules as well af a full reset, but if you really want to keep DenyList, Superuser permissions and other settings, you could save /data/adb/magisk.db file (where these values are stored) before deleting it from/data/adb along with /data/adb/magisk directory and rebooting to set up Magisk installation directories etc cleanly, next check saved magisk.db file in an sqlite editor, note the names of fields (tables) and values saved, compare these with fields for db file in new installation (eg official Magisk currently has denylist, policies, settings and strings as table names but table names for Delta likely differ), work out how fields in new installation correspond with the old and copy/paste saved values to new db file before rebooting...

Nb my guide was to provide a simple means for users in general to ensure incompatible configurations are removed and reset... I consider preserving settings across different Magisk implementations as described above to be an adventurous (but educational) undertaking...

🤠 PW
[Magisk] mavrovelos:
Thankful for your time and reply, just to be sure, I have to install the magisk alpha from modules section, "install from storage", right?
[Magisk] pndwal:
Only if you wish to use this method... PW
[Magisk] Dr.][No_WaY:
Ok i found the culprit "md5sum" is running all the time , any way to fix that?
[Magisk] WhoIsJohnGalt1979:
I found this latest post in Alpha telegram very informative and educational, fortunately I have been doing what has been suggested all this while. Would thank the developers for sharing this with the general populi. I have used Google translate for the purpose of translating to English. And I quote:

"https://github.com/topjohnwu/Magisk/blob/master/docs/faq.md This documentation is completely misleading.

The system detects the function of long pressing the volume down key to trigger safe mode, which is written in system_server. At this time, post-fs-data has ended, the module has been loaded, and zygote is running.

Many people wait for the animation to appear before pressing keys. They are misled by the documentation into thinking that system safe mode will trigger magisk safe mode. This is wrong, the time is wrong.

For safe mode to be recognized before the module is loaded, magisk must detect keystrokes earlier than the system. If you press the key after the animation appears, you will have missed the detection of magisk and will only trigger the system safe mode. You should press and hold volume down immediately after the bootloader unlock warning, and release it after the animation appears - if you do not want to trigger the system safe mode at the same time.

Safe mode can also be triggered through prop. When the computer is powered on, long press the restart button in the power menu and click OK on the "Reboot to Safe Mode" pop-up window, and the prop will be set. If magisk and the system read this prop the next time they are powered on, they will enter safe mode. Only in this way can we guarantee that everything will be triggered. But it is not practical, or in other words, it is meaningless to save bricks.

alpha now supports automatically entering magisk safe mode. If the device fails to start normally, all modules will be automatically disabled the next time it is started. This new feature is independent of system safe mode and can be forcibly triggered by checking in the restart menu of the magisk application."
[Magisk] pndwal:
Looks like vv responded to this issue:

https://github.com/topjohnwu/Magisk/issues/7702

and finally got back in my old issue here too:

https://github.com/topjohnwu/Magisk/issues/4624

I've been pressing for better explanation in docs/FAQ if keypress detection cannot be made more reliable/predictable for some time.

Instead of "Many people wait for the animation to appear before pressing keys", really 'Many people follow online instructions to wait for the animation to appear before pressing keys to trigger safe mode"... In reality they need to vary the per device safe mode instructions and press keys before post-fs-data has ended etc...

Auto entering Magisk-safe mode per Alpha new commits may also help...

PW
[Magisk] amk316:
i tried to disable magisk for the next boot using:

touch /data/magisk/.disable_magisk and touch /cache/magisk/.disable_magisk

but it did not work, only zygisk was disabled !!!
[Magisk] doclucas:
I can't read Mandarin and am not sure if the translation is correct, so better ask.

Is Magsik Alpha no longer being developed?
[Magisk] ykjae:
Translates to "magisk alpha decides to no longer sync with upstream"

Seems as development will continue but won't push updates to official TJW Magisk?

I might be wrong

Someone please correct me if wrong
[Magisk] xcl1pse:
Still developed, but won't rebasing/synchronizing with Wu's magisk because Wu so slow in merging prs. If there's a problem in original magisk and fix by Wu, just cherry pick that commit
[Magisk] sawdoctor:
Just switched to magisk alpha to test a few things. I get the message "unsupported environment" with latest shamiko so I'm presuming i can only use the previous version?
[Magisk] krakout:
Try v1.01(300)
[Magisk] manan001:
So to conclude magisk alpha will continue with the development but wont have sync with official one.
[Magisk] mavrovelos:
I also use Magisk Alpha, latest. Is it advisable to install zygisk next and disable the one included?
[Magisk] WhoIsJohnGalt1979:
Latest release (Google Translate to English from https://install.appcenter.ms/users/vvb2060/apps/magisk/distribution_groups/public) Download link included.

Version d78ee171-alpha (26405)

Feb 01, 2024 at 12:47

12.47 MB

alpha update log

Breaking behavior change: magiskd is now in a separate mount namespace, which is also su's global mount namespace. Most su use cases will not be affected. If you need init to mount the namespace, change it tosu -t 1。

Major behavior change: magiskd internal mount points are hidden from the outside and 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. Please use for computer debuggingadb shell 'PATH=$PATH:/debug_ramdisk su'。

Magic ( d78ee171-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

[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

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

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

[MagiskInit] Avoid patching init files for 2SI devices

[General] Delete the image, it is no longer needed for atomic mount

[General] After the magisk tmpfs path is fixed, magic mounting is no longer necessary and makes it optional.

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

Changes in changelog from previous version a0b8aa4d-alpha-2 (26404)

(not technical explanation, just a translation of lines added)

[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.
[Magisk] lordmd:
Thanks for the thread. I am on Poco X3 Pro (vayu), EEA version 14.0.1.0 - stock with only the modified boot image for Magisk.

Most apps worked fine without even using specific measures to hide root. Denylist was fin for the few that needed hide mechanisms. Mostly a social security app in my country. But then another app made problems. (Though that one should not need that much security.) It did not seem to detect the unlocked bootloader (worked with back on the stock boot image but with bootloader still unlocked) - must have been some stuff in the normal magisk where even Shamiko did not help.

I was surprised to see Alpha working that fine. I know some people dislike it since it (afaik) is closed source. (But that might also help making it harder forpeople trying to create mechanisms to detect root. And there seem enough people to use it already without problems.)

Everything fine since the switch to Alpha. (Not even Shamiko needed but I still use it.) I think some apps that previously could detect root do not even need to be on the denylist and just can't detect root cause they probably have cheaper/older detection mechanisms.

Some explanations in the opening post helped - though I had guessed most of it myself already: Uninstalling the old magisk and then doing a fresh install with Alpha (patch boot image method) - workded basically like the normal Magisk and did not cause any troubles.
[Magisk] rodken:
Version 2c6adbc6-alpha (27000)

Feb 06, 2024 at 13:34

12.45 MB

Alpha update log

Breaking behavior change: magiskd is now in a separate mount namespace, which is also su's global mount namespace. Most su use cases will not be affected. If you need init to mount the namespace, change su -t 1.

Major behavior change: magiskd internal mount points are hidden from the outside and 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 (2c6adbc6-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

[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

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

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

[MagiskInit] Avoid patching init files for 2SI devices

[General] Delete the image, it is no longer needed for atomic mount

[General] After the magisk tmpfs path is fixed, magic mounting is no longer necessary and makes it optional.

[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] Fix adb cannot connect to lldb server

Upstream update log

2024.2.3 Magisk v27.0

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[ResetProp] Add new wait for property feature resetprop -w
[Magisk] HippoMan:
I just upgraded from 26405 to 27000.

No problems. Works fine!
[Magisk] osm0sis:
It remains pretty f*cked up that Magisk Alpha is being publicly distributed on AppCenter and TG but with no public source code. That's literally in violation of Magisk's GPLv3+ license. 😕
[Magisk] xcl1pse:
In fact all new commit from LSPosed dev in TJW magisk's already have in Magisk Alpha. It's like 50% commit are from LSPosed dev so I don't think Magisk Alpha need to be open source. If it's ready, it will push to main TJW branch. Also it's vv choice after all..
[Magisk] osm0sis:
It's not their choice, it's not legal to violate the GPL. Once it's publicly distributed they're choosing to do something illegal by keeping the source closed. Problem is nobody is enforcing it. 🤷‍♂️
[Magisk] xcl1pse:
It's vv choice tho, Magisk Alpha is open source before vv close the access..
[Magisk] osm0sis:
Go read the GPL. My point is they literally shouldn't have that choice, because they're doing something illegal if 100% of the source for what's being publicly distributed isn't available. End of discussion.
[Magisk] sawdoctor:
Think the point @osm0sis is making is . If a kernel is shared on xda without any sources then links will be removed and the thread closed because of gpl violations. Magisk alpha can do what they want in my opinion but if links /files are shared on xda without source code then xda could be prosecuted/be in big trouble
[Magisk] xcl1pse:
Hmm.. maybe better ask vv for that, I'm just explaining the situation
[Magisk] osm0sis:
I don't really care about XDA's stake in this, just the moral standpoint of developers choosing to violate the license of the code they've forked. :p

I don't need to ask for anything, it's in the GPL. Your explanations suggest you don't understand the GPL.

Again, they have 2 legal options to comply with the GPL:

1) To remain closed source they must only distribute the builds amongst themselves, or maybe via a fully closed TG group (which would be a bit of a grey area/loophole), and definitely remove it from AppCenter (i.e. only private distribution, not public distribution),

or,

2) Upload the full source repos for all of their publicly distributed builds.

Anything else is illegal.

That's all there is to it. ;)
[Magisk] zgfg:
As @osm0sis pointed out, they use source from TJW Magisk project that is covered by GPL, hence they must obey to GPL and provide also the complete source ready for building - even if they would have made just the trivial changes like changing the name and package name for the Magisk Alpha app.

That's from the legal side

And the excuse/explanation is not 'complete'. They really have more than the trivial changes and upstream commits provided from the TJW Magisk GitHub source, eg the serious additions like Telemetry - and afaik, their telemetry source code wasn't published anywhere
[Magisk] HippoMan:
Question: I seem to remember that Shamiko was recommended over DenyList in the past for one or more earlier Alpha versions, and I just want to know whether that's still true, given the new features of Alpha 27000.

I'm running Stock A13 on a Nothing 2 device.
[Magisk] sawdoctor:
It's a case of what works best for you simple as that. If all your banking apps work with deny list on alpha stick with that if they don't then try shamiko. I think shamiko is only going to compatible with stock magisk going forward though
[Magisk] HippoMan:
Oh, OK. Well, I don't use banking apps, so I probably won't see any meaningful difference.

And I haven't seen any difference so far with any other apps.

But since Shamiko is only likely to work with stock Magisk as time goes on, I'll switch to DenyList.

Thank you very much!
[Magisk] devnoname120:
And it looks like Telemetry can't even be disabled. That combined with the fact that nobody knows what it collects exactly is a huge concern.
[Magisk] rodken:
Simply firewall Alpha as a deterrent to the built-in Telemetry.
[Magisk] Wolfcity:
Still not a good feeling if something is closed source and a firewall is needed to stop telemetry from sending things you don't know.

But anyway, better to use a FW.
[Magisk] devnoname120:
Magisk can bypass any firewall it wants
[Magisk] rodken:
Are you suggesting that this particular fork has a built-in VPN or Proxy to bypass?

If that's the case, maybe a simple script that executes a series of IPtables commands on boot in order to block inbound connections not directly related to outbound might suffice.

iptables -A INPUT -j DROP
iptables -I INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
iptables -I INPUT -i lo -j ACCEPT

ip6tables -A INPUT -j DROP
ip6tables -I INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
ip6tables -I INPUT -s fe80::/10 -j ACCEPT
ip6tables -I INPUT -d ff02::/10 -j ACCEPT
ip6tables -I INPUT -i lo -j ACCEPT
[Magisk] HippoMan:
This is quite helpful. Thank you!

On a rooted stock A13 device, where should a script containing these commands be installed in order for it to run properly at boot time?

... or is this device-specific? If so, I'll ask in the appropriate forum for my device.
[Magisk] rodken:
Let me dig in my arsenal of Magisk Modules because I think I stumbled upon one a few years ago that runs at a lower level applying a simple set of 'iptables' rules on boot with no user intervention required.

The only issue is that certain apps that require direct connections to the devices IP might break. Therefore, most users should notice little to no interference on their daily driver.

The anwer to your question is 'no' on device specifity.
[Magisk] HippoMan:
Thank for your answers!

And I'm looking forward to what you might find in your Magisk Modules arsenal.
[Magisk] rodken:
Bear in mind that I am not the author of this module. It's simply something that I stumbled on a few years back.

If you need future info, I'll be happy to share.
[Magisk] amk316:
can any one test this app and see if it work in a rooted phone

it was updated and stop working

it work ok with unrooted phone