yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Some apps detect 'signs' of modified environment and declare 'device is rooted'. Detecting apps like Magisk, Titanium etc is sometimes enough.

[In the case of Magisk App, you have the option of cloaking the app by reinstalling with different name / signing key... You should try it...]

Edit: I just tried this on an unrooted device, and was surprised that the option is not available. I had assumed that this ability was separate from MagiskHide, but it seems it's not available before Magisk (mask) is applied. PW
[Magisk] rudim12f:
For cloaking or signing i realy dont understand otherwise mobile jkn publish by goverment is for health data citizen
[Magisk] pndwal:
I just edited my reply above. 😬

...

The issue here is that many bank and other apps developed with strict security considerations use their own detection means (as Google's SafetyNet API attestation has been patently unreliable for some time 🤪) for 'non-Trusted Execution Environments' (read modified / insecure environment for running code).

Further, such apps also commonly (erroneously) declare that 'root' / 'Jailbreak' has been detected, and then restrict app use. Ie. their devs often use the term 'root' VERY loosely.

So even when NO 'Modified Insecure Environment' exists, such apps will claim to have detected root etc.

In reality, rather than root in the real sense, the app is likely detecting unlocked bootloader or possibly other 'mods', or even simply the presence of TWRP, Magisk app/manager or sundry root-capable apps on a blacklist using their own methods...

And I'm sorry that it now appears that you cannot easily even hide Magisk App w/o applying Magisk root (mask). PW
[Magisk] rudim12f:
Ok thank you for your explaination

And understood what you meant

Thank you for your attention

Case is closed
[Magisk] jons99:
maybe magisk hide is out?

Update README · topjohnwu/Magisk@d93c4a5

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] Didgeridoohan:
That's expected. If Google's gonna let him keep working on Magisk they can't really have him working on circumventing their security... The community is gonna have to pick up that part.
[Magisk] Depressed T.Bear:
Am I surprised? No. Can we blame him? No.

Google is now giving him the checks and provides the bread on his table. Of course, he cannot and must not work against himself.

He can't professionally install fire alarms and put out fires while privately dousing houses with gasoline and setting fires.

There are a few people who have continued to develop Magisk, in John's absence. Hopefully they will at least try to continue fighting on the Magisk Hide front. Personally, however, I don't have high hopes for this. With John, Google has an incredibly talented developer with an extremely deep understanding of the subject.

Only time can tell how things will evolve. But I would get used to a future where rooting will be possible, but no longer undetected. You can imagine what that will mean. Yes, I'm pointing at you, Samsung. How could anyone come up with the idea to disable the cameras on rooted devices...

These are just my depressive thoughts.
[Magisk] Didgeridoohan:
John was working together with a couple of people on changing MagiskHide to use zygote injection rather than ptrace (would likely have made a huge difference). There are a few commits on GitHub from early this year in preparation for that for whomever is interested in looking closer. It's very possible that they continue with that project and release it as an Xposed/EdXposed/LSPosed module. We can always hope...
[Magisk] pndwal:
And of course, we've been on borrowed time here in any case,,,

With full Hardware TEE rollout / implementation, whenever that comes, all bets will be off on the non-userspace MagiskHide front, unless even John's missed something.

I know such insight may be unwelcome here, (John's own tweets in March 2020 provoked some bitter responses / conjecture) but it seems to me that John will only be reminded of this fait accompli now more than ever; after all it's his department. 😬

John has been more aware / resigned to this than most of us for a good while even before his Google appointment. So just looking through his eyes, 'why prolong the enviable with the writing on the wall?'...

He may now even be aware of ETAs!

Sorry if this dose of reality is hard to swallow for any... but that's where we live...

FWIW, a bit here if any think Google opposes root / views Magisk as an overall threat to device security:

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

Ref:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85322543 PW
[Magisk] 73sydney:
And so just when the conspiracies theories had all died down, John has to go and poke the bear and start a new batch off :) :P
[Magisk] pndwal:
🤔 What bear? PW
[Magisk] zgfg:
For those who stayed on Stable/Canary, be aware before updating next time
[Magisk] zgfg:
Already in effect on Github:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] dcarvil:
I know you already know this, but you were a bit cryptic for those new to this forum. If you don't want to risk losing Magisk Hide due to an accidental update, create a custom update channel with the following URL (Magisk 23 stable).

https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json

If you are on an earlier version of Magisk, the URLs for stable are:

v20.4

https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json

v21.4

https://raw.githubusercontent.com/t...d863d3a15c6a2276b1061a280ece80ed7/stable.json
[Magisk] pndwal:
... may want to watch this space:

https://topjohnwu.github.io/Magisk/tools.html#magiskhide PW
[Magisk] ipdev:
I am pretty sure I know the answer but, I hope I am wrong. :cautious:

Is MagiskHide part of the Magisk core (mask) or the app (manager)?

Could we duplicate MagiskHide using a Magisk module?

Cheers. :cowboy:

PS.

If it can be incorporated into the app instead of the core.

Then split Magisk into a core and manager again.

A third party app (by diareuse) could be used to manager Magisk. ;)

- Similar to the way we managed the older phh's SuperUser with PunchUp's manager app.

EDIT:

PPS.

Just to clarify..

A third party app would have no direct involvement by John.

Using this mythical app to patch a boot image, it could include more than just the 'official' Magisk patches.
[Magisk] ipdev:
Also keep an eye on the commits. ;)

Magisk - GitHub - commits - Link

Cheers. :cowboy:
[Magisk] Didgeridoohan:
MagiskHide is core stuff, but like I said an Xposed module would be much more likely (I doubt a Magisk module could do that)...

But, as always, John is keeping us on our toes and until he spills the beans we're all just guessing. There are some very interesting commits going live on GitHub.
[Magisk] pndwal:
If the object here is simply to disable update notices, just changing Update Channel to Custom Channel (with nothing set for URL) will do this. App Latest will always show N/A. PW
[Magisk] pndwal:
Original details (/magisk/.core/magiskhide/ functions):

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-70363391

Major stability issue overcome, mounts in Zygote namespace, passive MagiskHide daemon timing/reactions:

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-70363391

Im guessing (way out of my depths), but it seems in depth understanding of isolating mount namespace, Zygote, passive MagiskHide daemon timing/reactions etc may allow a Dev to recreate MagiskHide as a seperate mod of some kind.

It appears that @vvb2060 for one has at least the basics down, and is also a major shaker in both Magisk and LSPosed implementation; I'm not sure who else is as qualified, or has their finger on the pulse.

From even a brief consideration of John's rudimentary notes on MagiskHide progress in the (old) Announcement thread, it is and will continue to be a complex business, but here's hoping! 😛

Incidentally, I hope that thread remains unedited / intact for posterity.

Also, as noted above, this conjecture may well be premature depending on which / how many beans John spills on the current state of play for Magisk... but I really think it isn't. PW
[Magisk] pndwal:
Yup! - And it seems John's actually been actively committing over the last 29 days. Somehow they've been hidden, and are just appearing today.

Some 38 since 16 may at this point, and counting! Expect major changes.

This one may be a clincher:

https://github.com/topjohnwu/Magisk/commit/003fea52b1857015bfc3988de56eb1a6d3049a7f PW
[Magisk] jons99:
State of Magisk: 2021

Ever since my employment at Google, crazy speculations has been spreading like wild fire all over the Internet. The out-of-context private…

topjohnwu.medium.com
[Magisk] pndwal:
"Hi, Zygisk"!

www.twitter.com/topjohnwu/status/1431889845199147008

So, just when many thought conflict of interests was crippling Magisk, we get modules-made-powerful by Magisk in Zygote!

Regarding the implications for enabling some 3rd party root hiding mod here, it's far from clear to me as I'm unsure whether Zygisk will actually embody much of John's original concept / plan to "hook into zygote to alter some code" as a '*real* solution" for hiding isolated services'.

www.twitter.com/topjohnwu/status/1298468244596985856

I note that John is still characteristically uncommitted to further cat-and-mouse hiding games, but I'm happy that he is, at least, supremely confident others will create 'hiding modules' as a trivial exercise!

www.twitter.com/topjohnwu/status/1431896770351489029

Further, I don't really understand the function of the upcoming denylist, or of reverted changes as described:

If any with insight into such mechanisms could clarify these new functions / John's remarks, I'd appreciate it...

Beta testing results will be interesting! PW
[Magisk] HippoMan:
Android is dead.

Long live Android.
[Magisk] J.Michael:
I think a lawyer was involved in rewriting the program description.

It used to be you had Magisk running, but you asked Magisk to "hide" Magisk changes from a particular app.

In the future, you will have Magisk running, but you will ask Magisk to create an environment that does not possess any Magisk changes, and then run a particular app in that de-Magisked environment.

Potato, hereinafter referred to as "Potato-of-the-second-part".
[Magisk] zgfg:
Incl. twit from osmOsis:

https://twitter.com/i/web/status/1431948577627119618
[Magisk] 73sydney:
Imma just sit back and watch people work themselves into a frenzy over nothing because they cant read :)
[Magisk] Depressed T.Bear:
State of Magisk: 2021

Ever since my employment at Google, crazy speculations has been spreading like wild fire all over the Internet. The out-of-context private…

topjohnwu.medium.com

John said all he needs. Most important things for us: MagiskHide is dead unless someone else creates an external solution.

Magisk Module Repo is dead until someone chosen by John maintains an external repo. Sounds like a hassle for devs and users to keep modules up to date until Magisk gets an update check somewhere in far future.

As many ppl rely on banking apps these days, root might no longer be an option.

Especially if you live in Germany where banks are actively using the code of f.e. Momo to detect all sorts of root, xposed (no matter if lsposed, edxposed or others.), etc.
[Magisk] 73sydney:
Theres already someone well conversed in hiding root that has been maintaining and adding to magisk in John's absence,and also has a hand in riru and lsposed...this has been noted already.

Who needs a module repo?...my main module was never on there, and had somewhere north of 29,000 downloads last i checked...only linked by the odd post and my signature...oh and forked a few times

Most of the modules i use, apart from one or two that are legit updated like @Didgeridoohan 's tireless work on MagiskHide Props Config, i havent updated in eons, ive been using local files when installing...

Why are people so quick to catastrophize?

Something doesnt go someone way in post 2000 and the world is ending. Im 50 i didnt get this far in life by being a pessimist....
[Magisk] Didgeridoohan:
Talking of which... As soon as I saw tihs commit I started working on implementing all the prop values that MagiskHide has been changing up until now into MHPC. I'll push that out there sometime next week in preparation for MagiskHide disappearing from Magisk.

I'm fairly sure that the community will create MagiskHide as a module fairly soon (and now that we will have Zygisk it will probably be a Magisk module rather than Xposed), and it's perfectly possible that all those props will be in there by then... But just in case.
[Magisk] Depressed T.Bear:
I do know very well about the contributions of vvb and yujicheng, don't worry. However, we should wait what comes and how things evolve.

Regarding your question who needs a repo: Noone. Who needs a smartphone at all? Noone. Is it convinient to have a module repo / or a smartphone? Yes.

Only because you explained why you don't "need" a module repo, it doesn't reflect the opinion of many others.

It's just a hassle to check dozens of sites every day for finding updates etc.

I'm not 'catastrophic' at all. Why should I? I'm old enough to be very relaxed I guess.
[Magisk] zgfg:
From my user's perspective:

- I'll stay on Alpha 31. If vvb2060 would have to adopt MagiskHide-less changes, I will stop updating Alpha

- I always keep locally the Magisk (Alpha) apk, my patched boot.img, and zips for all modules I use (five of them are from repo but rarely updating, one is my own, one I built by SmaliPatcher, and one I make for myself from YT Vanced root components)

- I have stopped updating Xiaomi.eu A11 weeklies (actually I even downgraded a month back) because there are not many useful updates/improvements anymore (generally and particularly for my Mi 9T)

All together, my only updates for the last two months were Magisk Alpha updates (plus few modules).

It was already boring (not much to flash, no adrenaline if something would go wrong, etc)

Seems it will become now even more boring if I would have to stop updating Magisk (Alpha) - but I don't foresee any other problem for me/my phone

However, by the end of year I plan to move to the new phone.

By that time, things should clean up - would there be a viable new Magisk with a module for MagiskHide, or Magisk and modding would no more apply for my biz phone/daily driver

PS: I like the modules repo because it makes updating easy (for those modules I use from repo).

Hence, there will be a little hassle now when the offcial repo dies and new repo comes (?) if I would have to stay on the old Alpha (pointing to the old repo)
[Magisk] Soumy1234:
Didn't John Wu say at some point he'd add the option to enable custom repo sources like how F-Droid can for example? Personally I think this would be the best alternative for Magisk Repo's shut down...
[Magisk] zgfg:
Somebody will have to maintain the new repo (ok, np if that would be F-Droid or so), and you would have to update Magisk to the new version (with all other changes the new Magisk will bring)
[Magisk] Soumy1234:
If MagiskHide becomes a separate, unofficial module then I'll gladly update. For now, I'd like to hold off and see what happens personally
[Magisk] zgfg:
TJW working in a high speed. Many fixes/improvements originate from vvb2060/Alpha
[Magisk] Depressed T.Bear:
It's not that he didn't look into the forked alpha by vvb and the changes made by him during his "absence".

Simply spoken, he just wasn't 'allowed' to touch anything during the process of approval or denial by Google.

So he can now cherry pick all suitable changes, which makes it seems fast.

As always if something 'drastic' is about to change: Lean back. Grab a good cup of tee or coffee, relax and jugde afterwards. (at least if you're not in the position to change anything ;) )
[Magisk] pndwal:
Direct link:

www.twitter.com/osm0sis/status/1431948577627119618

Yup, he's got a unique way of providing perspective / clarity! 😉 Great inclusion, ta.

This says it all:

"Zygisk" is a "hooking API a la Xposed".

Seems Magisk modules will now be armed with powers akin to Xposed modules. 😛

Great stuff / great start!

Ah yes,

https://www.growveg.com.au/guides/grow-potatoes-for-a-christmas-crop/

It is now apparent to me that John's current employment has allowed and perhaps even assisted him in making exactly the transitions he has long had on the drawing board. And collateral damage may actually prove to be zero to boot! 😜 PW
[Magisk] zgfg:
All ok. My points were:

- New Magisk is just around the corner

- For those who were sceptic to use Alpha during the last months, they can see that Alpha, its author and his fixes/improvements were a viable alternative

Btw, seems TJW (?) is also monitoring the Alpha Telegram channel:
[Magisk] Depressed T.Bear:
I didn't mean to say anything against your points mate :)

And yes, John is and was always taking a close look, I'm pretty sure.

BTW: For those who are interested, Greenify is alive again. Zygisk might be awesome news to Mr. Feng.

I wish the devs of Titanium Backup would rise again, but unfortunately I know from a 'close' Swiss source that they won't be back in buisness :(
[Magisk] pndwal:
Actually, many of those were pull requests in the queue since May.

@vvb2060 has always generally tested these in his Alpha first, then made pull requests...

John is now reducing the inbox stack from the top... PW
[Magisk] pndwal:
Yup, John's 'supremely' confident a new MagiskHide mod is inevitable...

I'd say that although it will no longer be strictly his baby, he will be elated when someone signs adoption papers... and he'll be sure to stay in touch...

Also, vvb2060 is a key Magisk colaborator. PW
[Magisk] zgfg:
For 'political' reasons, don't involve TJW into the upcoming MagiskHide module
[Magisk] pndwal:
😐 Well, speak for yourself!

You reported John's words, I just mentioned his confidence for the benefit of nay-sayers. - How does this involve him further?

No out-of-context private messages floating around here, no speculation fueled! - It's an opinion he's now happy to express in any forum!

www.twitter.com/topjohnwu/status/1431896770351489029

Sure he's watched as he appreciates, but he's passed muster already, and clearly feels free to make such helpful observations (re. other's efforts) now!

So don't fret, his nose will remain as clean as his code does! 😀

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458 PW
[Magisk] pndwal:
Interestingly, while official TJW Magisk now has some 52 recent commits (and counting), @vvb2060's Alpha branch still lacks all of these (ie is 52 commits behind) but is 32 commits ahead.

However @vvb2060 now includes new numerically numbered branches. Eg, latest is 2 commits behind (he hasn't merged 2) and 1 commit ahead...

https://github.com/vvb2060/Magisk/tree/5

Could be worth watching. PW
[Magisk] HippoMan:
It looks like it would require a Merging Marathon to try to get them in sync. Do you think that could be a worthwhile effort?
[Magisk] stevezlk:
Hi!

I couldn´t find a solution to my issue in this monster thread, therefore my post:

I´ve been trying several settings on my rooted Poco F3 (Europe) running the current Pixel Experience ROM, but I can´t get the SafetyNet check to succeed... MagiskHide is set, basicIntegrity is fine, evalType = basic (therefore the SafetyNet-Fix workaround shouldn´t apply here, right?) - just the ctsProfile check is failing.

I´ve tried 10+ fingerprints - of course including the matching one for the F3 & several Pixel ones - but no success.

I´ve read about the requirement of matching security patch dates, but these should be set automatically when using preconfigured fingerprints - at least that´s what I read in the FAQ. Am I missing sth? Thanks!

If logs are necessary, I´ll of course upload what´s required!
[Magisk] pndwal:
Sorry, wrong, and there's the rub. See below.

Yup, tested prints should be fine, but I believe issues can occur if print was made for earlier Android version.

So, you will need USNF module since Jan 2021 due to this:

... Google is cunning!

You'll also likely need MHPC module in addition (for fingerprint only) as you have a custom ROM (try matching print again), unless this is already spoofing a certified fingerprint.

Further, on late MIUI (Android 11 etc) you would likely need experimental SNF module that will "Shim the keystore service instead of replacing it" from here:

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

or its successor (Riru module):

Universal SafetyNet Fix · 2.0.0​

Changes since 1.2.0​

Added support for heavy OEM skins (One UI, MIUI, etc.)

Added support for Android 12 Beta 4 and future versions

Fixed broken Play Services features other than SafetyNet

Fixed rare system freezes caused by Play Services breakage

Android 12: Fixed face unlock on Pixel 4 series

Added support for Android 7.0 and 7.1

Rewritten as a Riru module

https://kdrag0n.dev/patreon/safetynet-fix/v2.0.0?utm_source=github

Nb. This will no doubt also interest Android 12 as well as Android 7 users (yes, there are Android 7 devices supporting Hardware TEE in the wild!; Standard USNF module supports Android versions 8-11), but requires an 'early access' payment. 😉

... But I'm guessing standard USNF module should work fine w/ Pixel Experience ROM.

🤠 PW
[Magisk] pndwal:
I'm only able to guess, but I imagine @vvb2060 will update Alpha in due course as previously, but is probably distracted like the rest of us at present. - He has till a few days ago been doing much on the recent Riru_LSPosed 1.5.2 release.

As for his new Magisk branches I have no further clues, but something may be afoot...

👀 PW
[Magisk] pndwal:
& @ipdev & others

Please could someone outline what MagiskHide daemon (and any other critical parts of MagiskHide) does (at present).

I understand this alters sensative props, isolates mount namespaces (switches these) and hides unmounts (in order to hide all Magisk modules, files and mounts including root from target processes, e.g. Safety Net).

Please say what I've missed.

It would be good to have a basic appraisal of all functions occurring / needed in any discrete solution. 👍 PW
[Magisk] stevezlk:
Many thanks for

Many thanks for your detailed explanation!

I already had busybox + MHPC installed. After a clean reinstallation of PixelExperience I just added Riru + USNF v2 modules (bought it couple minutes ago). Changing the fingerprint to the the preconfigured Poco F3 Europe doesn´t do the trick, yet.

Is there anything I´m missing? Do I need to get a more up2date device fingerprint for a Poco F3? Read your post like 10 times now :D
[Magisk] Didgeridoohan:
Did you enable MagiskHide?

Since you're using Riru you have an Xposed type mod installed... EdXposed or LSPosed? From what I've seen reported EdXposed is much more likely to trigger SafetyNet.
[Magisk] stevezlk:
MagiskHide is enabled, yes. I got https://github.com/RikkaApps/Riru/releases installed. I just added LSPosed, so far no difference..
[Magisk] Didgeridoohan:
If MagiskHide is on, you have USNF and are using a certified fingerprint with the correct security patch date (I just verified that the F3 Europe print included in MHPC works fine) and still fail CTS you've likely got something else that's causing issues.

Could be the ROM itself, could be a module you have installed, or it could be something else, etc...
[Magisk] pndwal:
Please try this:

- disable all modules and reboot.

- disable all processes in MagiskHide list.

- toggle MagiskHide off, then on again in Magisk App settings.

- enable MHPC module and Poco F3 Europe fingerprint.

- install (sideload) / enable standard USNF module v1.2.0

- clear Google Play Services cache.

- report Check SafetyNet results.

👍 PW
[Magisk] pndwal:
I think he only had Riru and Danny's new USNF v2.0.0 (for Riru) modules installed initially, no Xposed. PW