yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Magisk Alpha

Ok, I've updated mine.

All went fine for me.

Don't expect 'Update' notice in App as mentioned, even for Magisk (mask) after App update as version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

[After App update, you will notice different Release Notes Changelog in Chinese for Install Magisk (mask) and Install App. Expect Install App Changelog to be updated when release package (plus json) is pushed to GitHub repository.] It's now pushed / in sync with latest.

[At present, latest package file is still not pushed to GitHub repository.] It is now available from GitHub also.

I now understand this is often released earlier to Magisk Alpha Telegram group, and sure enough it's there! (It seems Chinese community there is more aware / informed of these builds than XDA community):

https://t.me/magiskalpha

Web based preview:

https://t.me/s/magiskalpha

Nb. See this for Devs notes also.

Nb.2. In Chrome, web based preview can be translated into English.

Magisk Lite

For anyone interested in this (those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes), this is released to Magisk Lite Telegram group also, but latest is unavailable as yet. 😕 :

https://t.me/magisklite

Web based preview:

https://t.me/s/magisklite

Nb. See this for Devs notes / working theory / difference with respect to standard Alpha / technical details re use, functionality etc.

Eg. Dec 4 build "restores the module function and can install a separate lite module.

Requirement: After the boot is complete, zygote and its child processes will no longer read any files mounted by the module.

(Otherwise, the mobile phone will have various inexplicable problems.)"

👍 PW
[Magisk] pndwal:
Since I'm unwell presently, I've been killing time checking recent commits in Alpha that may help with device compatibility issues.

One is "Support bootimg v4 format" which has been refined again in current build.

Within the commit I found interesting information on the various ramdisk types. Thought I'd share:

https://github.com/vvb2060/Magisk/commit/2bdd553f03a0e3989c277332e64d3f4b24f2f396

🤓 PW
[Magisk] zgfg:
Hopefully, you are doing better (must not be that bad since you are playing with Chinese Alpha👍)

Thanks for the info. Updated also my Alpha (app and Magisk) to that June 23 build from Telegram, everything as you described

Mixed filings:

- good there are updates

- good there is a support group (although only Telegram and on Chinese)

- hoping he will update to his Magisk Repo

- hoping there will be better updating scheme in the future (updated version number, updating via Alpha channel, notifications)

- hoping there will be a Github Issues tracker or so
[Magisk] pndwal:
Re. MagiskHide / bank apps / isolated processes, John Wu said in Aug 2020:

www.twitter.com/topjohnwu/status/1298468244596985856

So there's a tip for you MagiskHiders - try Servicely! (Controls for rooted phones.)

Among other functions, "You can also disable/enable permanently any service on your device. It's useful if you have services that tend to auto-restart and keep your device awake, or if you have games sending you never-ending notifications."

https://play.google.com/store/apps/details?id=com.franco.servicely

...And we've all heard of this Dev's (@franciscofranco's)

'Franco Kernel Manager'... And he just may need some love from XDA members ATM...

Gotta love Kernel Franco's response to that Twitter post too! 🙂

I don't think we ever got 'disable services with isolatedProcess' feature, and while John did have ambitious plans to (b) 'hook into zygote to alter some code', who knows where we're at with that now?!

That leaves (a) 'Magisk-lite, aka hide by default, mount if whitelisted', which 'will not be officially considered since this will break some modules'...

This was clearly a reference to the Magisk-lite project @vvb2060 had been working on since May 2020.

In Lite, with Magisk in whitelist mode, all applications are hidden by default and only checked applications can obtain super user permissions.

It has to be said that despite the fact builds since Dec. restore "the module function and can install a separate lite module", there are still significant problems with this. As the Dev makes clear (Chinese translated):

https://t.me/s/magisklite

So it seems a way to have our cake and eat it too (ie to hide isolated process leaks from bank apps detecting them, and have normal Magisk Module functionality) is a long way off yet... However, there are still a number of things desperate bankers can try before resorting to guns! 😜

And hopefully this clarifies a few things regarding Magisk Lite. 😷 PW
[Magisk] zgfg:
One more observation. With Aplha (both Jun 23 and previous May 29 builds), I can manage Magisk Hide for com.miui.security.center (MIUU Security app) through the Magisk app

It used to work also in Canary, but since v22 or v23, TJW disabled for some system apps (it was possible only through Terminal by magiskhide add/rm/ls CLI commands)

Btw, does Netflix need to be enabled in Magisk Hide?
[Magisk] handy1977:
[HELP] Google pay won't work s9 plus I installed magisk on s9 plus. It won't let me use Google pay says your phone is rooted. Anyway to get the app to work. Android 10 magisk 23.

I have enabled hide and installed props config latest still i am getting phone is rooted on Google pay app.

Cts failed Eval basic Basicintegrity pass

Screenshot-20210623-114529 hosted at ImgBB

Image Screenshot-20210623-114529 hosted in ImgBB

ibb.co

[URL unfurl="true"]https://ibb.co/tDC4jq0[/URL]

Screenshot-20210623-114737 hosted at ImgBB

Image Screenshot-20210623-114737 hosted in ImgBB

ibb.co

[URL unfurl="true"]https://ibb.co/GJhZNKX[/URL]

Here some images show my settings and safetynet test EvalType Basic
[Magisk] handy1977:
Hi how do we download file. I see no links on the page
[Magisk] pndwal:
Feel lousy but panadols help. Had lite cold but still got pfizer round II... Probably a bad move. Thanks for asking. 😷

Yep, best thing. 👍

Might need to learn Chinese... at least it's Simplified Chinese! 😃

I'm sure he will, but probably not a priority. Seems Telegram may be his official Release medium.

Well he recently fixed commit for that:

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

So it appears he wants it to work.

The explanation for it not occuring now seems to be that he has named builds for the last commit synced from John Wu's master branch each time he builds.

These have all differed untill recently, but the last of John's commits was

https://github.com/vvb2060/Magisk/commit/1eb83ad812e75e775d8cd178a7a3832029cc9607 (Update Android Studio), and this has remained static since mid May.

The first 8 digits of this, 1eb83ad8, appended with '-alpha' has predictably constituted the version code for the last 3 builds, but I'm certain he could alter this protocol easily.

I imagine he will, but don't know why he hasn't yet.

Yeah, but I don't know about the propriety of (or the need for) that as long as these are unofficial builds.

Actually, @vvb2060, along with @osmosis and others, have been responding to official Issues on John's GitHub since John's gone AWOL... Of course, he actually designed aspects of it, including the auto-close bot!

I'm also sure people will continue to submit issues here for the meantime, and @vvb2060 will continue to comment, create fixes and test them in his own builds as well as implement pull requests from John's GitHub in his own just as he has been doing for a year or so now.

I don't think the fact that fixes aren't presently being merged in John's builds is a real problem. Many fixes (for MTK etc) were working for / tested by users in @vvb2060's builds long before being accepted / merged into John's.

@vvb2060's close-issue bot may be a problem; users will need to report latest Canary build to get a foot in as things stand. 🙁 ... Perhaps he could tweak that?

And pull requests can still be submitted for merging in John's... And we can still hold our breath! 😛 PW
[Magisk] pndwal:
Like I said,

But what good will Lite do you? It breaks modules as explained... And it's entirely unnecessary for G Pay.

G Pay detects only Play Protect certification (ctsProfile/basicIntegrity SafetyNet API) currently, certainly not Isolated process leaks.

If you want to update later than official Magisk, use Magisk Alpha. PW
[Magisk] zgfg:
In today's posts from @pndwall (above) find a link to the Llite Telegram channel:

Magisk Lite

白名单模式的Magisk，所有应用默认隐藏，只有在SuList勾选的应用才能获得超级用户权限。 adb shell自动具有超级用户权限。 使用日志系统监听进程启动，如应用未检测到su，强行停止后重试。 移除机主控制功能，应用需要与UID完全相同才能获得超级用户权限。 由于Magisk app已经失去弹出授权窗口作用，移除其隐藏功能。如被检测，请直接卸载magisk app。 模块功能不受支持。 第一次使用需要手动打开SuList，开启后不可关闭。请在此之前做最后的检查。 内部版本，不公开公布，请进群下载。

t.me

Open in Chrome, translate, locate the post with app-release.apk from May 15, click on (it will open Telegram app) and then Save to Download (just checked, checksum is the same as when I previously downloaded directly from vvb2060's Lite Github page - link and download instructions were also in an pndwall's earlier post from the beginning of June)

Since Jun 2, I did couple of tests by installing the Lite and testing the modules with (additional tricks to make many modules to DO work, but some did not) and posted about 3-4 times here to the Magisk XDA thread

Currently I'm back to Alpha (latest from the Telegram, Jun 23 build)
[Magisk] pndwal:
Failed SafetyNet and Play Protect 'Device is not certified' (PlayStore Settings) is your problem, aside from far too many processes hidden (search here; this causes instability).

Assuming your ROM is stock, a SafetyNet Fix module should be all that is needed, aside from toggling off all unnecessary apps in MagiskHide list, toggle off Google Play Services too, then toggle off and on again MagiskHide in App Settings and recheck Google Play Services in Hide list (only one process should be selected now, com.google.android.gms.unstable SafetyNet process). Only that and hide Google Pay app is needed to fix GPay detection. (Don't add extra processes within apps). Also, clear data in Google Play Services, Google Play Store and Google Pay after that.

Back to initial setup:

Universal SafetyNet Fix Magisk module

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

will probably fix ctsProfile fail and work for you, but most Sammy users have issues with it. It's probably not the best available solution for 'heavily skinned' OS's like One UI as it will most likely break biometric authentication or other functions, and destabilize system because customised Keystore has been replaced with AOSP one.

A newer (experimental) fix from the same dev (shims the keystore service instead of replacing it) is now working for Sammy users (confirmed to fix S20 issues) and others with:

- some 32-bit ARM devices

- Heavy OEM skins

- Samsung One UI

- MIUI (needed for some variants only)

- Broken biometric authentication in apps

- Unstable system (i.e. rebooting and/or crashing)

Link (read OP here):

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

S9 users still report problems with this, but additional working module variations for several specific devices are found in the closed issues mentioned / linked from PR thread above. I think you'll find a modified fix for your Sammy in this post or elsewhere in this long issue thread:

https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-764129632

Be aware, these solutions use Keystores from specific OneUI versions.

Happy reading! PW
[Magisk] pndwal:
This I'm unsure of.

Seems many use sideloaded package for Netflix, and I got confused about claims re. split apks using (cloning?) Play Services, non- detection, etc. I suspect the reports vary due to many unorthodox setups.

All I know is that my PlayStore loaded Netflix shows, installs and opens fine with SafetyNet / PlayProtect passing on my setup on stock Magisk Alpha rooted RN8T (w/ Riru-MomoHider and Universal SafetyNet Fix modules), and root is NOT yet hidden from Netflix in MagiskHide list.

I don't have a subscription so haven't tested further, but I doubt (I'm guessing of course) I'd have issues.

Further, my understanding is that since Netflix 5.0, the real issue may be Widevine (DRM) TEE, a different TEE to the one SafetyNet uses. Netflix said at the time:

I just checked DRM Info app, and it's reporting Widevine CDM security is L1 for HDCP 2.3, so happily it seems that's not seeing bootloader unlock etc, and I'm good for 4K streaming! PW
[Magisk] bradical711:
I have used Netflix for a year plus now with no issues and I've never once hidden Netflix in magisk hide itself. (Although I do have the magisk app hidden and pass safetynet). My Netflix app shows 'L1' meaning I can stream Full HD as well as download my shows. So hide doesn't need to be enabled for the app itself but you do need to be able to pass safetynet as well as have the specs for "L1" AKA 'HD streaming' or more so 'DRM'. If Netflix appears in your playstore (because of passing safetynet), that's all you need to run and update the app. Nextflix just wants money and that's why you can also sideload the app, not have proper DRM management (L3) and still watch Netflix in low resolution.. obviously no downloads of shows/direct updates but that's at the cost of Netflix not knowing the device is secure. My device is a Pixel 4 XL, A11 June Stock ROM with custom kernel, magisk, 9 modules and passing safetynet. But no Xposed variants in my module selection.
[Magisk] zgfg:
For my Mi 9T with Xiaomi.eu A11 weeklies, DRM L1 certificate was already supported (screenshots)

Also, USNF is built-in to the ROM (to force eval type Basic, to let it pass CTS Profile attest), hence I don't need/use any particular module to pass SafetyNet (my Magisk Alpha app is also not repackaged)

Device is Certified (and Play Protect is ok), therefore I just regularly downloaded and installed Netflix from the Google Play

Before running the app I enabled MagiskHide for Netflix and then I configured the given Netflix account

Actually, I have a shared account with Standard subscription, hence without Ultra HD 4K support (my Mi 9T screen resolution is 1080x2340 hence also less than 4K)

Streaming works fine and Netflix Playback Specification shows L1, Full HD (screenshot)

Edit:

Thanks, I have removed Netflix now from MagiskHide, and it continues to stream with L1, Full HD
[Magisk] pndwal:
Interesting that he's talking about Magisk again (with director of LOS and others).

www.twitter.com/topjohnwu/status/1408334301763051522 😐 PW
[Magisk] 73sydney:
Let the conspiracy theories begin (again) :)

I liked you better when you were just being an awful Magisk Alpha tease a few days ago :P :P :P
[Magisk] pndwal:
Who's teasing?... But I'll bite.

👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸👴🏻🧸

I try to stick to facts (especially those fostering any sort of hope), as that was... And up to date Magisk. 😛

Why stir? There's plenty doing that... and better ways! 😜

And this is not PlaySchool mate! PW

Nb. Any perceived likeness to individuals depicted here is regretted, and the author is truly sorry... for the bear concerned, that is.

🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻🐻
[Magisk] 73sydney:
Hehe, my bear is a little smaller...has to be to fit into the baby harness :P

We should really get a coffee one of these days...
[Magisk] Thisisanacct:
I was directed here from the main help thread.

I am failing SafetyNet again, on a rooted OnePlus 8 (Global, 11.0.7.7.IN21AA). I have Magisk Hide and EdXposed blacklist as well as hiddencore set up and updated, and it suddenly stopped passing SafetyNet a few days ago, and I cannot figure out why as it used to work. Disabling EdXposed fixed it, but I need it for things such as GravityBox. Any tips?
[Magisk] justDave:
I had the same. Switched to lsposed today and it's passing SN again. Since you mention gravitybox, I should mention that I did have to uninstall and reinstall it to get it working after the switch.
[Magisk] pndwal:
Yeah, seen many reporting this recently. Many are moving to LSPosed w/ similar reinstalling. PW
[Magisk] pndwal:
I'm turning Japanese

I think I'm turning Japanese

I really think so...

www.twitter.com/topjohnwu/status/1408880903883935744

Yep, Fate can be a cruel mistress... especially when she's using a Google Algorithm!...

Fate... Destiny... Dark side... 😬... Nah!

You didn't Google Sammy phones too did you John?

https://twitter.com/i/web/status/1103848464457351169

www.twitter.com/topjohnwu/status/1103848464457351169

You're just a hard number to crunch! They've probably got you pegged as a Chinese Japanese Korean!? ... Watch out, they might actually have you connected to the Google algorithm tweaking Machine already!... (Like that conspiracy theory Style Messiah? 🤭 )

But chin up! Even Google can't force anyone to lose their identity John... John? 👀

😜 PW

🏯🎎🇯🇵
[Magisk] DiamondJohn:
I dont think you realise what those lyrics are a euphemism for...
[Magisk] pndwal:
I am now aware of this popular myth about 'Turning Japanese', ☹️ but really, are they?

I''m not sure you realise that while the inference that such a euphemism was intended is popular, most commentators regard the view as erroneous and as a misinterpretation, and I don't intend to foster it (although you could easily have ruined a pop song for me 😮 ).

Songfacts (songfacts.com) introduces it as "One of the more misinterpreted songs of all time" for that reason.

The Wikipedia article for the hit indicates that the inference was largely an American reaction to the British band's lyrics, and an 'eroneous allusion' on their part 'to the Asian facial features people get at [a particular] moment'. That, to me, is a sad indictment of society at that time, not of the song or its writer.

David Fenton himself strenuously asserts that the popular interpretation was plain wrong and unwarranted.

I'm sure other Brits would not have thought this way either, much less Japanese, Chinese or Koreans, and would regard it as a most unfortunate viewpoint.

Turning Japanese was a memorable international one hit wonder. (It got to No. One in Australia.)

I must say it's a bit like the Magical Hit Number John Wu 's given us, and recent public speculation about his motives seems to me to be reminiscent of the bad press Fenton got that may ultimately have caused the premature demise of his band!

That said, thank you for your concerns. 👍

FWIW in case anyone else takes it too seriously (for whatever reason), the post above was intended to be a trivial / light-hearted take on an equally trivial Twitter comment by the OP. 😬 PW
[Magisk] 73sydney:
Im starting to think someone knows too much about me, detective :)
[Magisk] pndwal:
No sleuth! But I'm finding my way around GitHub now, where you add a style all your own. 👀

You seem to have a menagerie! 😉 PW
[Magisk] zgfg:
Magisk Alpha app-release.apk, Jun 23, now updated also to vvb2060 Github:

GitHub - vvb2060/magisk_files

Contribute to vvb2060/magisk_files development by creating an account on GitHub.

github.com

Just downloaded and checked - same checkusum as for the previous download from his Telegram channel:

Magisk alpha

t.me
[Magisk] pndwal:
Yep, Alpha updated on GitHub including json, so full Changelog (Chinese) is now showing w/ Alpha App version >> Install App.

If you already have Alpha Magisk App, you can now update via App w/ this channel set.

Nb. Update notice is still not appearing as version number has again not changed (same last 3 builds) as it is automatically generated using string from John's last synced commit with -alpha appended, John's main branch has been static (for that duration), and @vvb2060 has not altered this protocol as yet. (Previously, constant updates to Magisk main branch ensured new version numbers for alpha, and builds included latest commits for Canary + @vvb2060's Alpha.)

To install manually, follow links from here:

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

Nb.2. Still no sign of new Magisk Lite build. (Experimental MagiskHide functions to hide isolated processes. - Magisk Lite has only SU function and does not provide full/normal support for modules. In Magisk in whitelist mode all applications are hidden by default, and only checked applications can obtain super user permissions.)

I'd say that's because Dev may be testing / having issues with this new functionality:

https://t.me/MagiskLite

👍 PW
[Magisk] zgfg:
You may like it or not, but it's Magisk Lite (pls, correct the typo) 🥸
[Magisk] tech_head:
There is something in the 11.x.7.7 OnePlus releases that breaks SafetyNet with EdXposed installed.

Same issue with a 9 Pro after 11.2.7.7 update 11.2.6.6 was fine.
[Magisk] systemizer99:
Hello, we have Android One smartphone on Mediatek MT6761 running Android 10 with unlocked bootloader. We need to install Magisk. The main problem is 32 bit System and Hybrid RAM disk (recovery inside boot). We have tried such things:

Install Magisk Manager (different versions)

Patch boot image

Reboot bootloader

Flash empty vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)

Flash Magisk_patched

After these steps we have always bootloader mode after rebooting. I cannot find any solution how to install magisk to have a root. Help me, please!!!
[Magisk] 73sydney:
I was waiting for Magisk Luke Edition, but i would be suspicious of where it was forked from
[Magisk] Stillhard:
Oh shyt! You're a mind reader now...
[Magisk] 73sydney:
I wasnt sure anyone would get the forked (Luke, i am your father) Star Wars reference :)
[Magisk] pndwal:
Is that a low-ram device? Please say device! PW
[Magisk] Thisisanacct:
Thank you. Lsposed works nicely.
[Magisk] ipdev:
If only :rolleyes: was an option under the Like button.

The cat and mouse game has always been..

Cheers. :cowboy:
[Magisk] systemizer99:
Nokia 2.3, 2Gb Ram, 32 Gb EMMC
[Magisk] pndwal:
Ok. Not the issue I had in mind; that's 64 bit SOC, why do you think you have 32 bit system?

Hybrid ramdisk shouldn't be a problem. Could be a MediaTek peculiarity.

Is Ramdisk yes? Patching boot image extracted from downloaded ROM package exactly matching current ROM? Tried with Magisk App

restored

(from settings) if previously hidden? Copied patched image file to PC with ADB, not MTP? PW

Edit: This confirms it's 64 bit:

https://nerdschalk.com/32-bit-and-64-bit-android-phones-list/
[Magisk] systemizer99:
Yes, it is stock boot image from original ROM

Initial (first) install of magisk manager

Yes, using ADB
[Magisk] pndwal:
Ah, then it may be a similar issue to the one I recall; I read re. another device OEM put 32 bit system to reduce overhead due to low (1gb) ram. Device ran go edition.

I can't find that issue now, but I think John had commented about a mismatch with bootloader, that it was a 'stupid' decision or such, and that he wouldn't fix.

Of course, this may not be the same, just appears similar. 😜 (Could also be an MTK anomaly, as I said.)

I'm not sure what resource (app?) you showed w/ 32 bit. Please could you confirm kernel architecture using cpu-z?

You could also consider opening a new GitHub issue for this following issue template. It should get attention, but may not be merged to a build of John's any time soon, although it is likely vvb2060 would merge any fixes in his Magisk Alpha. PW
[Magisk] ipdev:
I have run across it a few times across threads.

Some were even attempting to update the kernel to arm64 for custom roms/recoveries.

- Not sure if anyone has yet?​

I think the previous time in this thread was.

Post # 46,032 - Link | Post # 46,045 - Link

Hope it helps joggle the memory of the issue you were trying to find for reference.

--

AIDA64, I have used a few times.

Same with Device Info HW.

AIDA64 - PlayStore - Link

Device Info HW - PlayStore - Link

The one I use the most is DevCheck.

[APP] DevCheck 1.19 - System Information - xdaThread - Link

DevCheck Hardware and System Info - PlayStore - Link

I do not use CPU-Z too much any more. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Thanks... That second link was mine!... But I do remember an issue commented on by John w/ details as above, and I'm guessing it's in GitHub closed issues but I can't find it.

Yep, ta, I'd used Device Info HW but not AIF64

Thanks, DevCheck looks useful! PW