yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Magisk is an open source project (unlike former SuperSU), and as such is very much a community project, with some 201 contributors listed.

Maintenance of official branch has stalled for the moment, with John effectively taking a break... 😛

There are myriad unofficial forks on GitHub however, (3800+, many stale), and some from the 201 contributing Devs.

John put @diareuse in charge of the new material Magisk App some time ago to concentrate more on the Magisk mask itself.

@vvb2060's forks are not new; he's been at the forefront of Magisk development for some time (MTK, 64bit, Samsung, MagiskHide and many other fixes are his).

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85127113

His 'Alpha' experimental builds go back to 2018, and he also has many test / experimental 'Lite' and 'MTK' builds going back at least to May 2020.

These were clearly test builds for fixes later to be merged into official Magisk with feedback/testing provided by Devs native Chinese Telegram community, and Magisk would be completely different if it hadn't been for them. However, until now, Alpha and other forks have gone relatively unnoticed despite their impact.

I brought @vvb2060's builds to the attention of this XDA forum simply because there is presently no better substitute for debug Canary builds with regular updates that I'm aware of, and despite language barrier (@vvb2060 himself speaks pretty good English) etc. His Alpha Magisk works well for those wanting to be on the bleeding edge for now.

Nb. All of @vvb2060's builds should be considered non-stable 'bleeding edge' builds if Canary was 'cutting edge', and users should have contingency plans.

At least you can be an Alpha-tester for now! 😜 PW
[Magisk] pndwal:
Interestingly mine alternates between full pass

and init.rc modification detected.

This hasn't changed however.

If anyone can advise on hiding init.rc modification (or Momo "The environment is abnormal" detection), I'd love to know... I'm stumped. 😕 PW
[Magisk] 73sydney:
Interesting your init.rc bounces between detection and none...i havent seen that...maybe the modules youre running?

fwiw, im using:

BusyBox

Debloater (Terminal Emulator)

Global Optimized GPS File Replacer

Riru

Riru - Momohider (mod)

Swap Torpedo

Universal GMS Doze

Viper4Android (enforcing mod)

And a few small personal/Pixel 2 specific mods not released to the public

As ive mentioned the weird things is font/emoji replacement modules seem to set detection off

I gave up on the Momo, i never saw it do anything but give the report you did...meanwhile everything works...i dont poke the bear when thigns work :)
[Magisk] zgfg:
Did you observe any pattern or reproducibility in bouncing - like full pass upon reboot but later detecting init.rc modifications or anything like that?
[Magisk] pndwal:
Yup; as I reported earlier, I had full pass 0 detections in MagiskDetector after swapping Riru - Enhanced mode for Magisk Hide module for MomoHider, but this soon reverted to Init.rc mod detected w/ no changes to basic configuration, and I wasn't able to fix it then.

Just looked yesterday again after Alpha update when I took that no-detection screenshot. - seemed strange that I had full pass reported again since I hadn't even cleared MagiskDetector data/cache (init.rc result seems to be cached).

Next, I cleared data to get real-time result. - I've had init.rc mod detected since... So maybe an earlier Alpha build was hiding this better?

I've tried a few things to hide init.rc modification since; removed Chainfires Live Boot, disabled MHPC, Log Catcher, Systemless Hosts & Viper4Android FX modules. Only have USNF, Riru-MomoHider, Riru & Busybox for Android NDK active now.

Cleared MagiskDetector, reboot --> no dice. 😕

I've found it useful for several different items, USB debugging etc.

After disabling usb debugging, I only have

Chinese Telegram reports many are able hide Riru / partition mounting etc successfully, but I've only skimmed that stuff (some very recent); didn't have time to translate / dissect it all! 😜

Can't comment since you told me to leave the bear out of it, but I guess he's happy things are working for you at present... Poor thing. 🧸 PW
[Magisk] pndwal:
May have been 'bouncing', but not really observed.

Fairly full description in post above. Please ping me if you need specific details. PW
[Magisk] jons99:
22 was released today no changelog that I can see

Magisk alpha

You can view and join @magiskalpha right away.

t.me
[Magisk] zgfg:
Telegram only again (no Github Alpha), now we know that 20/22 are dates (still wonder when he would update the version number)
[Magisk] PokeRekoP:
I looked into that, too. My "dd" of my vbmeta partition (/dev/block/mmcblk0p46) gave me an image of exactly 65kB ALL being ZERO. That is, there is no vbmeta data structure in there, there is simply "nothing". Hence, it's not a valid vbmeta partition at all. For a moment I thought this might have been (wrongly, silently) handled by Magisk without me knowing (but then it would contain a vbmeta structure, but "cleaned out", not hard-zeroed). So I first confirmed with another Poke3 owner: the stock vbmeta partition indeed is all zeros on these devices, meaning this protection method isn't relevant (i.e. not used) on these devices. Hence flashing a properly made emptied vbmeta.img would likely have no effect at all. Hence: forget about that route for a Poke3 (and possibly other Onyx Boox devices!)
[Magisk] 73sydney:
To be fair its been sometime since i cleared data on Magisk Detector, so ive just done it, and will wait about 3 minutes or so after reboot to take a new reading...

As mentioned I abandoned Momo early on, and will try and do some digging this weekend

The one (actual literal) time i use the phrase "poke the bear" without it being a reference to the Peoples Bear, and you latch onto it :) I was on a zoom call with a new client yesterday and they spotted him in the background on my bed, because we are locked down again as you are well aware yourself, so then i had to tell his origin story. Was totes a professional engagement :)

Edit/update:

Nup, my init.rc is fine, no detection (Alpha 19 -having gotten round to 20, let alone 22 yet)

Make what you will of theses, and yet everything works perfectly, Google Pay, Samsung Pay etc
[Magisk] rodken:
Is MomoHider still a viable module to utilize and what is your take on riru-unshare?
[Magisk] 73sydney:
I use Riru-Momohider (my own tiny mod - just creates he config files on install here) and its the only thing that gets me google Pay. Samsung Pay and my banking apps all working

I was pointing out i had given up on Momo, which is the detection app, so sorry if it perhaps confused you

I previously tried riru-unshare and it did not allow me to use any of the above, but thats for my case, it may work fine for others.
[Magisk] pndwal:
Sorry, but I like to poke the bear, especially when things are working; I'm just that kind of guy. (Not the people's bear mind... wouldn't dream of it.) 😉

Impressive MagiskDetector result. Full pass previously? Pixel 2 XL?...

Momo's curious; did you clear it's data? - looks like MagiskHide was off!

Just checked your module list; guess you have USNF also? PW
[Magisk] timofonic:
Isn't John hired by Google now?
[Magisk] pndwal:
Yup. PW
[Magisk] pndwal:
Early Notice:​

Latest @vvb2060 Magisk Alpha build (July 23, 2021) changelog:​

Skipped a few due to rapid-fire! (This guy's a bit like Jorrit!)

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-23)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Display the modal waiting pop-up window when hiding/restore the Magisk application

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

Edit: New changes since 1eb83ad8-alpha-19

For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection

Rewrite MagiskSU's pty opening logic, no additional sepolicy rules are needed

Fix incorrect signal sending in MagiskHide

Add untrusted_app_30

https://github.com/vvb2060/Magisk/b...e147e578c92/app/src/main/res/raw/changelog.md

My earlier notes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85098469

Current notes:

Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

This build has not been uploaded at the time of this post. Watch this space!

Latest in GitHub magisk_files repo is 1eb83ad8-alpha-20

Latest available from Telegram group is

1eb83ad8-alpha-22

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85229385

Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

https://github.com/vvb2060/Magisk/tree/alpha/docs

🤠 PW
[Magisk] jons99:
👍 tho I don't see the file to download you see pndwal I'm hoping that this version I'll be able to flash on android 12 without disabling verity like we could in older android versions
[Magisk] pndwal:
Interestingly, this pull request is now merged in Alpha, but still pending for Canary:

https://github.com/topjohnwu/Magisk/pull/4507 (see Telegram comment for 1eb83ad8-alpha-22 from canyie).

Here's evidence vvb2060 is attending to at least some issues from John's GitHub. PW
[Magisk] pndwal:
That's why I said:

Early Notice:​

...

This build has not been uploaded at the time of this post. Watch this space!

I'll update asap when available! 😜

Looks like 1eb83ad8-alpha-23 has all changes but:

Rewrite MagiskSU's pty opening logic, no additional sepolicy rules are needed

PW
[Magisk] timofonic:
Isn't time for an "official" Magisk community fork where devs merge stuff in? I see clear conflicts of interest.
[Magisk] rodken:
Interestingly, after your response, I noticed an update for the Non-Alpha version of Magisk v.23.0. Should I be concerned or just pull the switch?
[Magisk] pndwal:
I guess a different 'official' version would require an adoption certificate signed by John Wu, since it's his baby.

He hasn't stated intentions as yet, but if you want to set up a replacement official Magisk, you could contact John on his Twitter etc. 😉

If you mean w/ John's current employer, you may want to read back here discussion since his new appointment with Google... Or other conflict of interest? PW
[Magisk] pndwal:
Well, you're still on quite old (John Wu) 22102 Canary Magisk. 😉

Seems you've changed channel and updated Magisk App to Stable or Beta 23000, but haven't yet updated Magisk (mask) itself, hence notice to Update.

Latest from John was public Stable / Beta 23000, or debug Canary 23001 (this build was synced with public Stable).

So if you want latest from John you can simply update. PW
[Magisk] jons99:
24 is out but I can't use any modules with it

Magisk alpha

You can view and join @magiskalpha right away.

t.me

went back to 22

maybe just need to reinstall all the modules and reenable magisk hide I'll try later
[Magisk] spevil07:
Good morning, tell me do someone know if there is a possibility that the Magisk app is not constantly reinstalled after a reboot?

I usually uninstalled the app for online banking, but it's back after every reboot.

I don't want uninstall Magisk/root completely, only the Magisk app.

I tried to rename and hide magisk for my banking apps but it's not working.

Uninstalling Magisk app works fine but after every reboot it's back again.
[Magisk] pndwal:
That is strange; how did you set up app? - it's not pre-installed w/ ROM or merged as system app?...

You didn't just delete home screen icon? PW
[Magisk] pndwal:
Yup! Thanks a million! 😐 I tried too... no dice of course... tried setting up modules - Modules go to new modules_update folder, but don't show or stick...

Then read note from Dev (translated):

browser: https://t.me/s/magiskalpha/321

Oh the thrill of life on the bleeding edge. 🤪

PW
[Magisk] timofonic:
Can anyone mirror that Telegram content? Please, I refuse to use other thing than XDA.

Or convince developer to publish it here, please.
[Magisk] zgfg:
Now 24 uploaded to Telegram Alpha and also showing in Magisk app as the Latest available

But in Telegram, he advices not to use yet (if translation is ok)
[Magisk] 73sydney:
Weirdly Alpha 24 is on github

But just tested and its nowhere near usable, breaks magisk detection, and module visibility

back to 22

Warning: reverting to 22 still leaves SU being detected in path and magiskhide not working according to Magisk Detector.

time to reflash the ROM's boot.img methinks and start over

note: not even that worked, flashing 24 screwed up something quite badly, su still detected in path/magiskhide not working. time to clean flash ROM...
[Magisk] zgfg:
Yes but on Telegram he posted (translated by Chrome):

"Don't change it yet, the module is not displayed"

?!

Edit:

And under comments on Telegram, few others confirmed that modules are broken with 24

Btw, apk 24 on Telegram is identical to apk 24 on Github (just checked their checksums)
[Magisk] pndwal:
If you went back to 22 from 24, it's all fine, but everything hide-related is disabled; MagiskHide, all modules.

Just toggle on modules and MagiskHide n reboot! (Even Viper4Android working / not affected / no driver reset needed. 🙂)

Also, delete data/adb/modules_update folder if you want to. 👍 PW
[Magisk] jons99:
yes you need to reenable magisk hide after going back to 22 safetynet is passing again
[Magisk] pndwal:
Alpha Users

If your screen looks something like this:

DON'T UPDATE yet!

Skip Alpha-24.

Details above. PW
[Magisk] zgfg:
My screen is similar, but black mode, so should I update 😂🤓🤩
[Magisk] pndwal:
You can for kicks. 🤪

But I should... Forgot Dark mode, ta...

Ah! MUCH better! 😛 PW
[Magisk] zgfg:
Dark mode rules

Btw, when reading Telegram through Chrome (for translation), it doesn't display comments
[Magisk] 73sydney:
Yeah, nup, that didnt work for me, im currently running a Migrate backup and flashing clean...its not the worst thing as i have an updated ABC ROM here i needed to do anyways :)

Magiskdetctor was not going to ever pass the installed ROM again, su in path, magiskhide not working.. plus all my debloated apps are back, so root is broken...hopelessly broken...would have taken more time to figure out why, than backup, clean flash, and restore :)

No, i twigged to that MagiskHide had been toggled off (during both 22->24 and 24->22) early, but while re-enabling it did pass safetynet, Magisk Detector was still finding su in path and reporting Magiskhide was not working, so something was still screwy
[Magisk] 73sydney:
you'd have to be a madman to not use dark mode, who even does that? :P :0 :P
[Magisk] jons99:
for me it always show finding su in path but magisk hide seems to be fine
[Magisk] pndwal:
Yup... Mentioned my method here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85359037 ...

Gotta love CrazyCapoo icecream fail... But I can't copy as gif etc! 😕 PW
[Magisk] 73sydney:
@pndwal

Interestingly clean flash with alpha 22 shows su in path and magiskhide not working??

Going to flash back to alpha 20....
[Magisk] pndwal:
That's sad.

Mine is zachery same:

So is Momo result.

I think you haven't hidden root from MagiskDetector; what results after that? PW
[Magisk] zgfg:
Yeah, but that's manual translation

Two years ago when I joined a small German Telegram group I added a bot translator. Everybody could write on its own language and bot automatically translated (and posted) in English.

But it was annoying to have all posts double

I'll check if Integromat translate bot can be used to translate only to me from Chinese
[Magisk] pndwal:
That'd be good to know; I did briefly look for 3rd party Telegram app w/ translate feature, but no dice.

Telegram seems pretty bare-bones; can't even seem to multi-select a range of posts... PW
[Magisk] 73sydney:
uggh even alpha 20, Magisk Detector says su in path. magiskhide not working

what is going on....

trying alpha 19
[Magisk] rodken:
Factory reset your device and report back.
[Magisk] pndwal:
So do you pass SafetyNet atm? Are you clean flashing w/ full data wipe?

Interestingly, my MagiskDetector results are 'bouncing' it seems... Full hide at present:

PW
[Magisk] 73sydney:
i am clean flashing...can get anymore factory than that :)
[Magisk] 73sydney:
It will pass SafetyNet, but Magisk Detector is showing su in path and MagiskHide not working

im clean flashing again and trying 19
[Magisk] rodken:
Please share your findings when you are able to get everything up and running because I am contemplating on jumping on the bandwagon and flash Alpha sometime tomorrow.
[Magisk] 73sydney:
Well up until tonight my alpha journey was flawless

regret installing 24 thats for sure :)
[Magisk] jons99:
I did

you should hide MagiskDetector
[Magisk] 73sydney:
Update:

I made it back to bliss with Alpha 22. Looks like I had a bad flash with the updated ABC ROM, but upon reflashing that after a very deep clean, i was able to get Magisk Detector back to working as before (no detections)....phew

btw, theres now an alpha 25.

I might let someone else be a guinea pig on that one :)

Early comment on the new alpha is: 已安装。没问题 or Installed. No problem

Imma still wait :)
[Magisk] jons99:
alpha 25 is out and working fine
[Magisk] zgfg:
Actually, 24 is deleted from Telegram
[Magisk] jons99:
well it had issues you know. 25 is good
[Magisk] zgfg:
Yes I know - just wanted to say that 24 was deleted (as bad).

And yes, 25 is good (modules listed and work)
[Magisk] jons99:
you and pndwal and the rest of the contributors on this forum do a great job teaching the way of magisk to new and old users just wanted to say

also here's the apk for that one guy who don't like telegram
[Magisk] rodken:
@73sydney Although, I intend to jump on the bandwagon and flash Alpha. Is it safe to say that the best way to update Alpha would be to simply install the apk on top of the current version?
[Magisk] zgfg:
Please read the older posts about Alpha. In short, install Alpha apk (you might need to uninstall Stable/Canary if Installation complains about diff signature). Then patch the image and flash.

You will not loose modules, etc
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha build (July 24, 2021) changelog:​

Skipped a few due to rapid-fire! (This guy's a bit like Jorrit!)

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-25)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Modify the search order of the module sepolicy location, fix the problem that some devices do not load the module sepolicy

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Display the modal waiting pop-up window when hiding/restore the Magisk application

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

Edit: New changes since 1eb83ad8-alpha-19

For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection

Rewrite MagiskSU's logic to open pty and delete extra sepolicy rules

Fix incorrect signal sending in MagiskHide

Add untrusted_app_30

https://github.com/vvb2060/Magisk/b...ecefa63e8b4/app/src/main/res/raw/changelog.md

My earlier notes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85098469

Current notes:

Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

Latest in GitHub magisk_files repo is 1eb83ad8-alpha-25

Latest available from Telegram group is

1eb83ad8-alpha-25

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85229385

Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

https://github.com/vvb2060/Magisk/tree/alpha/docs

🤠 PW
[Magisk] pndwal:
Nb. I only posted (Chinese) Telegram links here as a recent build was only uploaded there, but most have also been available on @vvb2060's GitHub as is 1eb83ad8-alpha-25. Please see my 'earlier notes' linked with changelogs. PW
[Magisk] pndwal:
Since you are asking about updating Alpha (and I'm speaking about after an Alpha Magisk App has been installed and Alpha channel set; before this you may need to remove older App) I'll add that direct update from App has worked fine for some builds with no initial changes even with hidden App. However w/ App update, other builds have failed to find and replace hidden App, and required that to be removed later from device settings, Apps to restore functionality.

I recommend you Restore (unhide) Magisk App before updating for this reason. PW
[Magisk] xAxB:
Hello, I hope that this is the right thread for general support.

I am trying to use Magisk (tried both v23.0 and Canary) to root my Samsung Tab S4 (Android 10, security patch March 2021) following the Samsung (System-as-root) guide posted here: https://topjohnwu.github.io/Magisk/install.html

1. When I click "Install" there is the option to tick / untick "Preserve force encryption" - What should I do with this?

2. Regardless of whether I tick it or not, selecting "Next" would let me "Select and Patch a file". However, and this is my main problem, I am unable to select the AP_[device_model_sw_ver].tar.md5 file. I can find it, but not select it. It doesn't matter if I put it on the internal storage, or microSD card, everything is just greyed out.

Is there a solution to this problem? Thanks.
[Magisk] zgfg:
Which Magisk Manager/App version do you use - in v23 there should be no more Preserve force encryption option (removed long ago)?

Download the latest Magisk App from Magisk Github

How big is your md5 file? If 32 bytes or so, it would be just a textual file containing MD5 checksum of the ROM file
[Magisk] 73sydney:
Update to Alpha 25 smooth :)

I always unhide, update, reboot, rehide
[Magisk] pndwal:
Yup!

This is a per-device setting (doesn't show for many. I think only on older devices). Generally, these are correctly set; only change if you have issues.

In this instance, I think you'll only need it if you wish to decrypt device (for custom ROM, TWRP etc?), and some devices may bootloop if not checked. That said, if it's off by default, I'd leave it that way...

Not a Sammy guy, [edit: this is wrong] but the install instructions seem to be in error; AFAIK, MD5 (message-digest algorithm) is only used to verify file integrity. Is there also an AP_xxxx.tar file? I'm guessing John ment to specify that... PW