yashsingh1/xdaforums huggingface dataset:
[Magisk] zapahacks:
Thanks for the answer

So, the steps would be:

1. Magisk V8 (I already have a clean rom/boot.img that passes safetynet)

2. Flash Phhs super user

3. Download the app from the store

4. Install the manager to check that Magisk is hidden

I will give it a try:fingers-crossed::fingers-crossed:

Do you know if any version of xposed would work together with this? And if it does, on which step should I flash it?

Thanks!!

EDIT 1: So I installed following this steps, and root + magisk manager + safetynet work. BUT then I installed Xposed 86.6 using the Magisk Manager and it seems it trigers safetynet.

So I went and read post #5 from [MENTION=4470081]topjohnwu[/MENTION], specially this part "It cannot hide SuperSU, it cannot hide Xposed. If you want to hide any of them, please use suhide developed by Chainfire."

So I interpret it literally and went and flashed suhide 0.55 to see if maybe it could hide xposed but unfortunately not.

So my setup is phh's super user root + magisk WITH working safetynte, but I'am unable to hide xposed (because if I flash Chainfire superSU + suhide, no matter which other method I use, it is not possible to pass safetynet). Does anybody know if have anyother alternative to hide xposed?

Thanks again
[Magisk] thebsgamer:
Google just allegedly pushed an update to SafetyNet that fails any test if your bootloader is unlocked. So it's probably that.
[Magisk] midgarsormr:
Yup, seems like I can't pass using any root method.
[Magisk] H4X0R46:
Alright so I'm really lost here. Now that the magisk manager has removed the option to unmount root, how do you go about hiding phh superuser? Do you use this version https://goo.gl/lwO5vi or this version https://goo.gl/Gt87hl ? Thanks! Any help us much appreciated!
[Magisk] :
I've tried both and fail safetynet with magisk v8 only.

I can easily gain green status by flashing stock 6.0.1 rom or flashing magisk uninstaller.

Aside from safetynet no problems.

The option to hide magisk is in the manager settings. Reboot after checking the box.

On a galaxy s5 g900w8
[Magisk] H4X0R46:
It hides all modules completely? Just wanna make sure. Thanks for replying man, I appreciate it!
[Magisk] hkdoublecat:
I did some research and find examples of when CTS Profile Match will report as false (failed):

Uncertified device (the manufacturer hasn’t applied for Google certification)

Unlocked bootloader

Signs of system integrity compromise (rooting, etc)

Signs of other attacks (Xposed, EdXposed, etc)

So for my case the failure is likely caused by and only caused by unlocked bootloader.

And I thought it is normal because my main device oneplus 7 pro got the same failed safety net and device certified.

I had been able to use google pay before; ~early september google pay start popup i shouldn't use it for security reason yet i could still pay by google pay; late september, could be triggered by clearing cache, the google pay drop my cards and i can no longer add new. Then I install Magisk (app only) and see I cannot pass safety net.

It is an unrooted oneplus 7 pro running on custom rom Havoc 4.6
[Magisk] pndwal:
Interesting... If you clear data for Google Play Services and Google Play Store (w/ failed ctsProfile), does Play Protect still dive Device is certified?

Nb. Custom ROMs like Havoc often include inbuilt spoofing / hiding, but S/N fail should still produce Device NOT certified result.

Also, apparently OnePlus's (in particular) messed up hardware TEE implementation on many devices initially caused Google to turn off enforced hardware TEE attestation for SafetyNet in March 2020... I wonder if certified Device w/ failed ctsProfile may be a symptom of OnePlus's poor coding? PW
[Magisk] pndwal:
Bank app detecting your settings?

Here's John's take / solution:

www.twitter.com/topjohnwu/status/1439204362182488065 🤪

Actually, it's about app detecting Developer Options enabled...

@phhusson weighed in with:

www.twitter.com/phhusson/status/1439144663609450497

vs.

Interesting! 😛 PW
[Magisk] pndwal:
On cue (thick n fast):

"46e8f07-alpha

@vvb2060 committed 7 minutes ago"

It's 46e8f077-alpha, on Telegram now...

Edit:

Wow, lasted about 3 minutes and it's gone again! ... I didn't download it ...

😉 PW
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha (Chinese translated):​

Magisk (46e8f077-alpha)​

[General] Based on 46e8f077, the content that has been merged upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserId

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

[App] Built-in current version update log

[App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

[Busybox] Fix the default shell path

[App] Switch to the modern time API of Java 8

[DenyList] Dealing with suspicious props

[App] Update the SafetyNet extension, update the version of snet.jar to 18

[Sepolicy] Sepolicy with built-in LSPosed

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

😜 PW

Edit: Already withdrawn... See above.
[Magisk] pndwal:
New :

zygisk-detector.apk

https://t.me/magiskalpha/339

😛 PW
[Magisk] pndwal:
Want to understand Zygote?

https://t.me/magiskalpha/339?comment=10059

👍 PW
[Magisk] zgfg:
Unfortunately, you are right

I use XDA app. I receive notifications about the new posts. I go in XDA app to the Alert page, alerts are there. I click on an alert and it doesn't open - page stays empty forever.

I thought first it was an issue on XDA forum side, but it's not:

- In that 'empty' page in XDA app, if I use three-dots on top-right and then Open in Browser, then it immediately opens the particular post in Chrome

- If I go to Magisk app, switch off Zygisk and reboot, after that (with Zygisk off) then there is no problem with XDA app.

I switch Zygisk on, reboot, and again the same problem with XDA app

Btw, with Zygisk on, I can still open Web pages in WebView when I click to the given link (even if it is a link to the particular XDA thread or post)

Preparing now to revert back to Alpha b9268f86, last before Zygisk = last where things (XDA app and its alerts) properly worked - and for the time being to stop playing with further Alpha versions
[Magisk] zgfg:
As you wrote earlier, that release is (no more) available in Telegram

63cfe7b4-alpha is the last on Telegram and the Alpha app itself still declares b6298f86-alpha as the latest released
[Magisk] 73sydney:
Apparently sometimes day sleeping helps you avoid bad Alphas

Im all for it :)
[Magisk] pndwal:
Some installed it. Most comments gone with withdrawn thread. One or two comment in last build thread available...

b6298f86-alpha is of course just the last build uploaded to GitHub repo. PW
[Magisk] zgfg:
Yeah, it still detects Zygisk in 63cfe7b4-alpha, even upon enabling Zygisk detector for DenyList and rebooting
[Magisk] pndwal:
Yup, as mentioned, Alpha merges TJW commits that have already disabled repo access.

Just looking back at missed posts...

Actually, App Latest indicates Update Channel set to Beta or Stable.

Just to avoid confusion, since single package builds (public 22.0), channel is only relevant to updating App; Direct Install or Patch Image will always be updated to match App Installed (as Magisk is no longer sourced from server, but now packaged / 'synced' with App), and works offline.

As shown it will install b6298f86-alpha Magisk (mask) regardless of channel.

To be clear, this is the only reason to change Update Channel in post 22.0 builds; The App (now complete package) can be updated from within currently installed App (from server). App Installed will match App Latest shown from Update Channel set and requires internet access.

As shown, it will install 23.0 Beta / Stable.

Of course, this may initially fail due to downgrading (most systems won't allow Installation of older app versions without first uninstalling the current app), or app signature varying (eg. moving between TJW and vvb2060 builds when app is un-hidden).

Where App install fails, downloaded .apk is still in folder set in settings, Download path. Simply uninstall current App, locate the new .apk and it will now install.

Interestingly, if app is hidden initially (custom signing) moving between different dev's builds doesn't result in such failed installation, but in practice I've found it works flawlessly only 50% of the time. Another 50% of attempts have resulted in dual conflicting apps coexisting due to incompatibiliies despite the fact it's supposed to work. I therefore recommend always un-hiding / restoring App before up or downgrading.

🤠 PW
[Magisk] pndwal:
This:

Magisk alpha

t.me

🤔 😬 ☹️ PW
[Magisk] Stillhard:
The beauty of open source(s) 🤣
[Magisk] pndwal:
Yup!... But if vvb2060 can't ... That leaves John ... Think he'll try?

Perhaps canyie? PW
[Magisk] Stillhard:
TJW once said Riru will get merge into Magisk if i'm not mistakenly recalled my memory, perhaps Riru's Hide can helps

Edited for this:
[Magisk] Stillhard:
He's too busy fighting with /fban in their tg chan/grup lol
[Magisk] Chandru123:
That build is luckily the most stable out of the other recent ones. The latest builds are starting to crash applications after some time and the magisk app tries to restore itself. Not sure the problem is with me doing a direct install over the previous versions.

Do I need to install it afresh with all the modules removed first. Kindly advise the steps needed to install the latest magisk alpha properly.
[Magisk] HippoMan:
Life ... don't talk to me about life.
[Magisk] HippoMan:
I think we should just let zygotes be zygotes.
[Magisk] 73sydney:
i had some issues with downgrading that borked my install completely, only removing /data/adb solved it when downgrading at least...but i did wipe that after doing a complete uninstall form my previously stable one (and one i went back to - alpha 31), in case there was any change in the magisk.db format, on the upgrade too (doesnt seem so as others just upgraded with it in place). Downgrading was more drama...definitely solved by removing /data/adb

(i normally keep my magisk.db across ROM's to lazily apply hidden apps before i restore them...handy with banking and pay apps..install magisk, reboot, copy magisk.db to /data/adb, enable magiskhide, reboot, restore apps - no need to tick anything and no sensitive apps detect root and bork)

Im staying put on alpha 31 again for a while after the recent alpha borkage

If you want a failsafe alpha, my favourite before the latest major changes is attached to this post, one is a zip for TWRP, the other is an APK for install in Android.

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

TWRP (and APK) method:

1) Flash the ZIP via TWRP (this will automatically patch the boot image)

2) Reboot

3) Install the APK

4) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)

5) Test SafetyNet - if no pass seek help

APK Method:

1) Find or extract the boot.img for your current ROM, copy to device

2) Install the APK

3) Open Magisk, click Install, locate the boot.img, patch it

4) Copy it off device to PC

5) At command prompt and with platform-tools (fastboot and and installed), use command (substitute magisk patched_boot.img)

fastboot flash boot magisk_patched_boot.img

OR

fastboot boot magisk_patched_boot.img - if you want to test it will boot first before using the previous command to flash (commit) to it

6) Reboot

7) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)

8) Test SafetyNet - if no pass seek help

You know which method i use, being a lazy bugger and with TWRP for my device...

Note: Same method can be used with current/latest alphas...up to enabling MagiskHide..as its been removed/replaced by Zygote and Deny toggles

So the only downside to using the safe or older alphas/officials is that the bleeding edgers here will now be using new terms like Deny List and Zygote, for the earlier alphas/officials its the traditional Magiskhide...
[Magisk] Compass Linux:
Many thanks for this (saving the file for safekeeping).

I've been browsing the Magisk Alpha GitHub and it seems the older releases aren't available.

Are they removed or I'm mistaken?

Compass.
[Magisk] pndwal:
Consecutive builds should install properly over previous. Modules shouldn't cause issues unless system itself is updated (disable modules for major OTA's etc).

I generally reserve remedial action for when things go wrong (and as pointed out, this is more common in practice when downgrading).

But fair warning; Late Alphas are clearly far from stable, really only for serious testing, currently especially fraught due to early (highly experimental) Zygisk introduction not to mention denylist and MagiskHide component removal, and may even be enough to make you chew your own foot off... PW
[Magisk] pndwal:
They're in magisk_files repo:

https://github.com/vvb2060/magisk_files/commits/alpha

Click a commit (by date), then browse files, then view code. PW
[Magisk] pndwal:
Good tips Nigel!

I just reverted to b6298f86-alpha due to issues w/ app seeing Magisk, and nothing I do will restore Zygisk toggle despite Zygisk being active... I'll remove db in ADB / use Complete Uninstall soon...

“The best-laid schemes o' mice an' men gang aft a-gley [ - go often astray].”

To a Mouse (1786), Robert Burns

... But you can count on mice... 😀 PW
[Magisk] zgfg:
I reverted today morning simply from 63cfe7b4 to b6298f86 in few minutes by:

- disabling Zygisk

- installing Alpha b6298f86 apk (didn't need to uninstall 63cfe7b4 apk)

- flashing my boot img that was previously patched by b6298f86 (I always save and keep my patched images for some time, you never knew previously with Canary and specially now with Alpha which bugs could be camouflaged in the release)

I checked with Zygisk detector and from XDA app (it uses WebView and I had problems with 63cfe7b4) and everything was fine.

I checked also DenyList and SafetyNet (and Device certification) - all was also ok
[Magisk] hfam:
Man, I've been gone for quite a while, last Magisk I installed was v20 on my Pixel 2!! Coming back is like being dropped in the middle of a foreign land, and I could sure use a bit of encouragement and a small assist!

I purchased 2 of the unlocked Pixel 5a 5G devices and they'll be here in a few days. M8 died and P2 battery is just useless at this point! :)

That said, I've spent an hour or so reading the thread backwards from today and I see Magisk Alpha, zygote, MagiskHide is replaced with Deny List, etc...I am having trouble wrapping my head around some of this. I don't want to blow it with the install, so can someone point me in the right direction to get started? Magisk or Magisk Alpha? No TWRP, I just keep it super stock, no OTAs, just updates using full images (remove -w) and flash-all. Anything to look out for in the Pixel 5a that is a major change affecting root, etc?

I'm happy to read until I bleed to get it right, so even a few links on which Magisk to install, where to get it (if it's not on TJW's Magisk github), how to make sure I can hide apps (Deny List replaced MagiskHide?) and pass SafetyNet?

Thanks, and glad to see a lot of the folks who've been here forever still here helpin' out! Any assistance would be appreciated as always.
[Magisk] Didgeridoohan:
@hfam I would suggest going with the latest stable release for now, since the Alpha releases are highly experimental and @topjohnwu will create an official release whenever he deems those changes to be a bit more mature.

The official installation instructions is always a good place to start:

https://topjohnwu.github.io/Magisk/install.html

But I see that there are a few threads on this in the 5a threads as well:

https://xdaforums.com/t/magisk-root-procedure-for-5a-5g.4327361/

It should be pretty straightforward, since it's a Pixel device. Just patch the boot image and flash it to your device.

To pass SafetyNet you'll need to use the new Universal SafetyNet Fix as well (as long as you stay stock you shouldn't need anything else):

https://github.com/kdrag0n/safetynet-fix

Android 12 is gonna need some updates on the Magisk side, but that'll be taken care of in good time...

Everything that's being discussed in this thread over the past weeks/months will probably be made much more clear once John releases his next build.
[Magisk] pndwal:
Welcome back!

Good start. If I were you:

- I'd read John's Release Notes from your 20.x (?) version for best / official summary of changes. Major changes in 21.0 & 22.0:

https://topjohnwu.github.io/Magisk/releases/

- I'd avoid Alpha, especially now that John has returned from limbo (with blessing of big G).

Alpha's are Bleeding Edge test builds, bleeding more than usual presently and especially ATM are only for mavericks keeping pace with all TJW commits / willing to test w/ untold bugs and regressions, and not disposed to chewing off a foot when things go pear-shaped.

- Install latest Stable or Canary from main GitHub page (these are synced / essentially identical currently). If taking direct install / update on old device, be sure to restore (unhide) Manager / App first, and disable modules especially after OTA's.

No Zygisk, Denylist etc. in current TJW builds; (It'll be a big leap when it arrives), so no worries with that stuff till next Beta, and John usually updates documentation at the same time...

- Familiarise yourself with changes to Installation Instruction:

https://topjohnwu.github.io/Magisk/install.html

and FAQs re. fixing issues (new Safe Mode fix for modules causing bootloop etc).

https://topjohnwu.github.io/Magisk/faq.html

For Stock certified ROM, enabling MagiskHide and installing latest Universal SafetyNet Fix module 2.1.1 + Riru should be enough to pass SafetyNet at present. USNF:

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

Many changes in @Didgeridoohan's wiki regarding other issues too. First port of call if having problems:

https://www.didgeridoohan.com/magisk/HomePage

All best. 🙂 PW

Edit: I see there's some repetition here, but shouldn't hurt. 😛
[Magisk] hfam:
@pndwal, @Didgeridoohan, (I see you too @zgfg!!), thank you both SO MUCH for the thoughtful and helpful and comprehensive replies!! So grateful, it's so good to be back and as always, the XDA Magisk family are truly the kindest most willingly helpful folks ever!

Im all over this info, thanks again so much for the timely replies, I'm off to read, get up to date educated and get prepped for the phone arrivals!! I'll be back once I've blasted em with Magisk, thanks again!
[Magisk] Chandru123:
Got confirmation in the telegram channel.

"It is not recommended to use 706a4922-alpha and later versions. Zygisk is in a very early stage of development and has serious problems.

Even if you use it, please turn off the zygisk function.

The current recommended version is the version in the update channel."

The versions merged with the repo are the recommended versions of Magisk Alpha.

The Zygisk versions are bleeding edge builds and not stable at all. Please refrain from installing them.

Just check the latest version mentioned in your magisk app and that is the version you want to be in.
[Magisk] pndwal:
To mods concerned:

Very sorry for my (removed) post regarding John Wu's, Pierre-Hugues Husson's and Luca Stefani's comments re. ctsProfile... I guess they're totally irrelevant here now, especially John's Humorous one.

I'm sorry for my other light hearted response re. 'bad alphas' here too...

Consider me chastised.

Apologies also to Diamond John and to anyone I may have missed... ☹️ PW
[Magisk] jons99:
new alpha working fine for me
[Magisk] zgfg:
SafetyNet ok?

Did you enable Zygisk?

If so, WebView is ok?

And ZygiskDetector still finds Zygisk then?
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha (Chinese translated):​

alpha update log​

Magisk (0ab31ab0-alpha)​

[General] Based on 0ab31ab0, the content that has been merged upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserId

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

[App] Built-in current version update log

[App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

[Busybox] Fix the default shell path

[App] Switch to the modern time API of Java 8

[DenyList] Dealing with suspicious props

[App] Update the SafetyNet extension, update the version of snet.jar to 18

[Sepolicy] Sepolicy with built-in LSPosed

[General] Add an obsolete cgroup v2 path

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

OP's notes:

It is not recommended to use 706a4922-alpha and later versions. Zygisk is in a very early stage of development and has serious problems. Even if you use it, please turn off the zygisk function.

The current recommended version is the version in the update channel.

0ab31ab0-alpha

Don't open zygisk

👍 PW
[Magisk] jons99:
safetynet is ok zygisk was enabled from previous builds and the detector finds zygisk
[Magisk] pndwal:
Also, are you running Riru? If not, can you enable it (w/ no Riru modules), reboot and say if it breaks SafetyNet? Thanks, PW
[Magisk] jons99:
I'm running riru
[Magisk] 73sydney:
Good to know, because without Riru and MomoHider its an absolute non-starter for me
[Magisk] pndwal:
Just installed new Alpha.

Initially disabled Zygisk (after installed App), and S/N failed as expected; seems no way to enforce denylist w/o Zygisk enabled as before.

Enabled Zygisk, rebooted, SN passes w/ S/N Play Services process denied and USNF 1.1.2.

XDA notifications etc are failing, so I guess it means webview is (still) broken with Zygisk. ☹️

ZygiskDetector finds Zygisk in /sbin on my device w/ MIUI / Android 10. PW
[Magisk] pndwal:
New Alpha:

Ok, just enabled Riru, rebooted, and basicIntegrity fails again, so seems Zygisk still breaks S/N at least on my stock Android 10 MIUI RN8T... I'll keep old USNF for now.

Strangely, XDA notification etc are now ok (w/ failed S/N & Riru - Fixes Webview?... Perhaps just the reboot fixed it?... Will check...) PW
[Magisk] zgfg:
Btw, WebView (and Trichrome lib) cannot be filtered in DenyList, even by including System and OS apps (I wanted to see yesterday could that fix WebView)
[Magisk] jons99:
as far as I know webview is working fine for me
[Magisk] 73sydney:
Thanks for the update. Might hold off again for now
[Magisk] jons99:
looks like the only error I get is from ad blocking

(ad blocking have nothing to do with magisk or zygisk it's just for less pro users then zgfg that might wonder why there's errors)
[Magisk] pndwal:
So this is curious; just disabled Riru & rebooted --> S/N good, but I'm back in Chrome XDA page as webview in XDA app is broken again...

So it wasn't reboot that fixed it previously; somehow webview works when Riru is loaded / basicIntegrity fails! ...

Must be a connection but it's eluding me... Can anyone help crush this a little?

Yup, seems to be a MIUI connection... Riru w/ Zygisk works w/ S/N pass for you...

Have an idea.... I'll be back...

Ok, disabled USNF and rebooted w/ none --> basicIntegrity ✓, ctsProfile - , webview / XDA app still broken, so Riru must be enabling webview w/ Zygisk loaded somehow... I'll check this...

And another surprise; Enabled Riru and rebooted --> basicIntegrity ✓, ctsProfile - , webview / XDA app still broken! ... So Riru alone is NOT breaking basicIntegrity! ...

Just tried USNF 2.11 again + Riru --> basicIntegrity - , webview / XDA app Good! ... So any USNF + Riru + Zygisk both breaks basicIntegrity and allows webview to work w/ my miui setup. 🤔 ... PW
[Magisk] zgfg:
I don't understand how could that be related to Alpha, Zygisk, and so

Some adblockers (which one do you exactly use - AdAway?), when they block certain site, they forward request to the dummy Web server on localhost

However, dummy Webserver on localhost (127.0.0.1) does not have proper SSL certificate, hence if it was https request then browser warns you that you are trying to open a Web page with an untrusted certificate

E.g., in AdAway, Preferences, Root based Adblocker, disable Local Webserver