yashsingh1/xdaforums huggingface dataset:
[Magisk] AndreSantoro84:
No! That was before. I took a chance, updated Magisk to 24.3 and put the safetynet you passed. Apparently it worked.
[Magisk] AndreSantoro84:
The problem came back. It was this CTS profile match failing that the incompatibilities came back. How do I fix this permanently? :(

(The app is in Portuguese, I'm from Brazil)
[Magisk] 73sydney:
Have you completed all the steps here (click on spoiler):

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86320343

Especially enabling Zygisk and rebooting...
[Magisk] AndreSantoro84:
I followed yes. I removed the fix, restarted, added it again, restarted again, everything was ok but the incompatibility continued, I cleared the cache and data from the Play Store twice and it worked again. I'm starting to think that unlocking bootloader and rooting is not being more advantageous, a lot of bureaucracy and problems.
[Magisk] AndreSantoro84:
In fact, I was a little confused by the guidelines of the other topic, a lot of information to translate and try to follow, it was kind of dispersed in the comments. If the problem reoccurs, what should I try?
[Magisk] Captain C:
I am currently on EvoX custom ROM running Magisk 24.3 with universal safetynet 2.2.1 and Shamiko v0.4.4. Everything is working with my denylist apps not detecting root. (except for the new Momo detecting zygisk). When I install the latest Shamiko v0.5.0 module Momo does not detect zygisk anymore but my banking app stops working. It just opens and then closes immediately.

Any advise as what the problem could be.
[Magisk] pndwal:
That's surprising (*see below), but I'm not sure why you're following this procedure on S7; seems it launched with Android 6.0 Marshmallow...

The instructions outlining your method are prefaced with the comment:

https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

Actually, patching AP is specifically for SAR / 2SI (variation on SAR) decices, generally launched with Android 9, as noted above, so it seems you should extract and patch the boot image. However I believe Magisk handles lz4 and several other compression formats fine; I'd try patching it as is...

Also, it seems pre-SAR Sammy phones had standard fastboot mode, so my guess is that you can follow the generic instructions here:

https://topjohnwu.github.io/Magisk/install.html#patching-images.

(Samsung users may know if Odin is actually required on S7...)

Normal on old devices...

I'd try proper official method first... GitHub Issues for S7 users all seem to be resolved currently (no-one reported your issue AFAICS) except this one if kernel is old:

Pinned issues

[Wontfix] Zygisk cannot activate on some old Samsung devices with old kernel (3.19-)

* AFAIK Ramdisk yes should never change unless OEM ramdisk is corrupted or replaced with a custom (modified) ramdisk (which can still work; Magisk ramdisk no doesn't actually mean no ramdisk in boot as most Xiaomi rooters know, but really 'no stock / OEM ramdisk in boot')...

Ramdisk no is only expected on A-only legacy SAR boot type devices anyway; yours is legacy ramdisk, unless updated to A10 / 2SI booting if available.

It could be that patch AP corrupts ramdisk for some reason because non-SAR/2SI devices were not considered with its implementation The method (with need for full data wipes to root) derives from the special / edge case presented by 'Modern' Samsung SAR devices with 'Vaultkeeper' etc...

Hope this helps. 🤠 PW
[Magisk] pndwal:
So USNF module is not causing fallback to basic attestation...

Assuming you have USNF 2.2.1 and Zygisk enabled, is Magisk App reporting Zygisk-Yes (after reboot)?... You're not losing root entirely? PW
[Magisk] pndwal:
vbmeta fixes coming...

www.twitter.com/topjohnwu/status/1525034917670756353

👀 PW
[Magisk] pndwal:
FWIW, Purpose of Magisk; Dev perspective:

www.twitter.com/bakwas247/status/1525035786621575169

👀 PW
[Magisk] Stillhard:
It's out now in the latest Canary released
[Magisk] pndwal:
Latest Official TJW debug Canary Magisk:

Magisk (c11ccbae) (24310)​

[MagiskBoot] Fix vbmeta extraction implementation

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

[MagiskBoot] Fix vbmeta extraction implementation

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/379a6f08e9c5736a3f810d44d444ef13533d4b12/notes.md

👍 PW
[Magisk] amk316:
can we have parasitic magisk manager like LSposed?
[Magisk] pndwal:
😍🥳 PW
[Magisk] zgfg:
For issues, change requests, etc, you have to report to the Magisk GitHub page - that's the only way to reach developers (here we are users like you)
[Magisk] mbangi:
any fix for this?
[Magisk] pndwal:
Latest Shamiko fixed Found Zygisk for me [Redmi Note 8T] but I note reports that Zygisk is still detected on some devices after Shamiko update.

I still have Bootloader unlocked, but had that w/ previous MOMO also. PW
[Magisk] pndwal:
Since there are inconsistencies with changes for Shamiko module listed here:

https://github.com/LSPosed/LSPosed.github.io/releases

and Shamiko's Readme.md file, I'm posting a 'readme' with overlooked changes appended:

Readme.pw:

# Shamiko

こっっ…　これで勝ったと思うなよ―――!!​

### Introduction

Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

Shamiko read the denylist from Magisk for simplicity but it requires denylist enforcement to be disabled first.

Currently, system apps (with uid%100000=1000) cannot be hidden even it's in the denylist. This issue comes from Magisk.

### Usage

1. Install Shamiko and enable Zygisk and reboot

2. Configure denylist to add processes for hiding

3. *DO NOT* turn on denylist enforcement

#### Whitelist

- You can create an empty file `/data/adb/shamiko/whitelist` to turn on whitelist mode and it can be triggered without reboot

- Whitelist has significant performance and memory consumption issue, please use it only for testing

- Only apps that was previously granted root from Magisk can access root

- If you need to grant a new app root access, disable whitelist first

### Changelog

#### 0.1.0

1. * Hide Magisk root

2. * Hide Zygisk and Zygisk modules

#### 0.2.0

1. Support font modules since Android S

2. Fix module's description

#### 0.3.0

1. Support whitelist (enable by creating an empty file `/data/adb/shamiko/whitelist`)

2. Always unshare (useful for old platforms and isolated processes in new platforms)

3. Request Magisk 23017+, which allows us to strip Java daemon and change denylist regardless of enforcement status

4. Temporarily disable showing status in module description (need to find a new way for it)

5. Support module update since Magisk 23017

#### 0.4.0

1. Add module files checksum

2. Bring status show back

3. Add running status file at `/data/adb/shamiko/.tmp/status`

#### 0.4.1

1. Add more hide mechanisms

#### 0.4.2

1. Fix app zygote crash on Android 10-

#### 0.4.3

1. Fix tmp mount being detected

2.* Hide modified traces of init.rc

Note: Hiding some system apps won't work since 0.2.0. It is a Magisk's bug, and it has been fixed since 24102+.

#### 0.4.4

1. Fix module description not showing correctly

#### 0.5.0

1.* Better hiding Zygisk

#### 0.5.1

1.* Support Magisk 25+

#### 0.5.2

1.* Enhancement

### 0.6

1. Hide more trace of Zygisk

### 0.7

* Requires Magisk 26000+

1. Support Magisk 26.0

2. Fix font loading

3. Hide more traces of Magisk

4.* Support zygisk loaded by native bridge

### 0.7.1

* Requires Magisk 26000+ / KernelSU 10818+

1. Merge Magisk and KernelSU branch

2.* Fix xiaomi crash issues

### 0.7.2

1. Fix a bug causing Zygisk on KernelSU failed to unload

2. Abandon a useless fix leading to more detection

3. Clean service.sh

4.* Fix the bug of incorrectly determined as corrupted.

### 0.7.3

* Requires Magisk 26000+ / KernelSU 10940+

1. Follow root profile on KernelSU

* Appended

🤠 PW
[Magisk] pndwal:
Nb. Latest Shamiko (from Magisk alpha TG) is Shamiko-v0.5.0-112, as opposed to Shamiko-v0.5.0-110 if downloaded from GitHub (linked above)...

Could those with Shamiko 0.5.0 and Zygisk still detected confirm issue exists in latest Shamiko-v0.5.0-112?

👍 PW
[Magisk] 73sydney:
yep, i tested both in other thread :)

still detects

Samsung S20+ 5G

Oh, and Ponkles to you good Sir
[Magisk] zgfg:
For me it was fixed with 0.50 from GitHub - actually I update through Magisk app when it shows that update for the module is available (hence I don't manually download from TG or GitHub)

It's good for me but on two Xiaomi phones, don't know about other phones
[Magisk] pndwal:
Actually, now you mention it I recall I did the same and v.110 did fix Zygisk-after-Momo 4.1.1 - then manually updated to latest v.112... no change / Zygisk fixed...

Could just be a Sammy thing then 😜

I think minor fix must be for edge-case crashing someone on TG reported...

Rhubarb... PW
[Magisk] mbangi:
Yes using it but still facing this problem
[Magisk] martyfender:
I have 2 Onn 8 first gen tablets with Android 9. One has a newer Android patch date. They both are on the latest magisk alpha. They both have the latest shamiko, lsposed, USF and hidemyapplist. With the latest two momo updates the newer tablet reports: found zygisk and bootloader unlocked. On the older tablet momo reports: found zygisk and TEE broken. Both devices are playstore certified and pass safetynet with evaluation type basic.

Does anyone know what TEE broken means and if there is a solution for it? I do know TEE means trusted execution environment. DRM info Shows Widevine security level at L3 on both devices.

Thanks
[Magisk] pndwal:
People are lately reporting this on TG for various Meizu and OnePlus, Xiaomi Lavender, also aware of Infinix, Xiaomi Poco, and now Onn...

We knew OnePlus messed up keymaster implementation:

www.twitter.com/topjohnwu/status/1237656704537395201

and seems many more OEMs did...

Seems Onn may have patched this issue with an update for your device if both you have are identical...

Some are reporting still having L1 widevine security, so I'm guessing actual TEE OS itself may be ok while HKA to TEE (uses the key pairs) is broken; test for those users will be to decode HD video in Netflix etc; seems OnePlus w/ 'broken TEE' can still do this (uses OS in TEE).

Since L1 security depends on certifying for widevine DRM w/ Google as well as soc compatible w/ HDCP (High-bandwidth Digital Content), you device likely never qualified for L1 anyway.

It could be that Momo is misreporting; the test is new after all, however I've seen no reason to suspect it's not good as yet...

Assuming the MOMO test is good, the sheer volume of devices with bad OEM TEE (attestation only?) has probably contributed to the long time it's taken for Google to get the 'critical mass' of devices w/ keymaster 3 (Android 8+) working properly in order to fully deploy HKA... Ie your broken key attestation is probably what's keeping MagiskHide solutions alive for all of us! ... So thanks mate. 👍 PW
[Magisk] xdMatthewbx:
Are there modules for hiding files/folders from apps (scoped storage changed nothing I tried it)? I'd like to not have TWRP files found in Momo but renaming the TWRP folder has the issue of now when I boot TWRP my saved settings are gone. I'd prefer to hide it, not delete it. This would also be ideal for hiding custom ROM. Note that overlayfs does not work as a solution since that not only causes Momo to detect overlayfs itself but also Zygisk (using latest Shamiko 0.5.0 112, UNSF, Zygisk without enforce, Momo on denylist).
[Magisk] pndwal:
Sounds like the domain of Rikka's 'Srorage Isolation' (formerly StorageRedirect)

https://sr.rikka.app/

(See guide in menu), or 'sandboxing' apps like Island, Shelter, Insular...

Nb. I haven't used any of these solutions myself. Those with experience may be of more help.

Seems mileage for hiding Zygisk w/ Shamiko varies with device...

👀 PW
[Magisk] pndwal:
Out of interest, if you disable USNF on both devices and reboot, does 'broken TEE' one still give Basic evaluation type in YASNAC? (expected as bad keymaster implementation should cause SafetyNet to fall back to Basic attestation type)... And Basic also on the other one?...

- I'm curious if both use Basic type w/o USNF as I expect Google will have removed this device from the list of devices (whitelist) that are known by Google to support HKA (Hardware backed cryptographic Key Attestation) after testing failed, but may have restored the listing once a patch/fix became available... This is is a different fall-back* implemented using model prop(s).

Please report if you do this test.

* Nb. Either of these fall-back types, (1) keymaster failure and (2) no Model prop match, will result in Basic attestation reported in apps like YASNAC, but Hardware attestation may actually still be enforced by its counterpart. Where this is the case, passing CTS Profile match may be impossible even with Basic attestation reported.

- I believe this is a shortcoming of Safety net checking apps. - Really they should only indicate Basic for Evaluation type when both fall-backs are triggered since only then will Basic attestation work and HKA be fully disengaged...

- In any case, USNF overcomes this by both registering a fake keystore provider that causes Play Services to throw an exception resulting in (1), and appending a space character to model prop value causing a mismatch with whitelist resulting in (2).

🙃 PW
[Magisk] martyfender:
If I disable USF module, both basic integrity and cts profile match fail. Evaluation type is BASIC. The device still shows certified in the playstore. This was on the older device:

ONA19TB002, security patch level 2019-04-05.

Although the hardware appears to be the same reported in AIDA64, with the same Android version and kernel version, the model number is 100005207, with a security patch level of 2020-03-05.

I get the same results with safetynet in YASNAC on the newer device.

If I recall correctly, both of these devices passed safetynet, way back in the past, before google changes with Magisk installed, without the USF module.
[Magisk] Fry-kun:
Successful upgrade on Pixel 6 Pro

from: raven-sp2a.220405.004

to: raven-sp2a.220505.002

Procedure to reduce # of steps & time spent:

* Latest canary Magisk already installed (24310)

* raven-sp2a.220505.002 (Factory/full) downloaded & extracted

1 Modify flash-all.sh (since I'm on Linux) to remove "-w" from the last line to avoid erasing my user data

2 Extract boot.img from the inner .zip

3 adb push boot.img /sdcard/Download/boot.ini

4 (still on the old image) Patch Magisk to this boot.img

5 adb pull /sdcard/Download/magisk_patched-****.img (full filename is printed in magisk after patching)

6 adb reboot bootloader

6.5 (sanity check) verify flash-all.sh doesn't have "-w"

7 ./flash-all.sh

8 watch the output and when it finishes, hold volume down on the phone as it reboots -- this will take the phone back to fastboot mode without a full system boot with stock kernel

9 in fastboot mode: fastboot flash boot magisk_patched-*.img (same as pulled in step 5)

I've used this procedure a bunch of times (on earlier versions), and it only (kind of) failed once when I wasn't using Canary Magisk (was at the time apparently necessary for Android 12).

Hope it helps; IIRC, a bunch of tutorials have you boot into stock kernel, and patch the boot image from there -- it's really not necessary if the Magisk version is the same before & after. Also, I haven't needed to re-patch vbmeta since original rooting (no need for --disable-verity --disable-verification either)
[Magisk] zgfg:
Long ago (mid of last year when we started to play here with Magisk v24 prereleases and Momo etc) I 'hid' TWRP folder by renaming to TWRP.back and TWRP 3.6.1 finds its settings with no problem. Simple and working fine for me
[Magisk] badabing2003:
Considering that you'd have to watch and time when you have to press the volume key, you can replace the

-w with --skip-reboot.

If I'm not mistaken in one the several reboots that flashing does, the phone is placed in fastbootd mode, and you probably don't want to press the volume key when that is happening.

Easier yet you can use PixelFlasher that does all the steps above.

By the way I think auto-corrector played a trick on you, it's boot.img not boot.ini.
[Magisk] Fry-kun:
Nice tip, thanks!

Lol oops!
[Magisk] pndwal:
Latest (not really... 24312's out...) NEW Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (dc65a2b8) (24311)​

Introduce new debug channel. Canary builds are now built in release mode, and debug builds are now required for bug reports.

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

[MagiskBoot] Fix vbmeta extraction implementation

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/40582aaa15e6a5031f847a5f594c0703099cbcf2/notes.md

👍 PW
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (756d8356) (24312)​

Introduce new debug channel. Canary builds are now built in release mode, and debug builds are now required for bug reports.

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

[MagiskBoot] Fix vbmeta extraction implementation

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/eb166b87765ad8755df859e1e6d8749a28cc06cb/notes.md

This includes minor fix:

Show canary channel option on canary builds

👍 PW
[Magisk] pndwal:
I'm guessing that this paves the way for John to integrate this rather controversial debugging tool c/o vvb2060 -

Add appcenter #5291 otherwise known as Microsoft AppCentre aka telemetry (ie debug-Magisk phone home)*...

Rather nice solution allowing users wanting to be on the leading (cutting) edge of Magisk to continue updating Canary without app 'phoning home' with magisk logging data, as well as builds being more compact (lacking verbose (debug) logging Canary had previously, while implementing a great tool (timesaver / data collection for speedy fixes) in separate Debug builds...

This will mean users must migrate to latest Debug build before submitting bug reports (making GitHub issues), and other users experiencing the same issue will be able to help without even commenting on GitHub simply by installing.Debug build themselves to allow automatic data collection...

* Watch this space! 👀

What's not to like? 😛 ... 😬 PW
[Magisk] pndwal:
Yup, old MagiskHide fixed Basic Integrity on many devices as well as CTS Profile...

Your results show that your tablet is not seemingly on Google whitelist for HKA enforcement meaning the second fallback (model mismatch) is not needed. Incidentally, my Redmi Note 8T w/ 'working' TEE isn't either...

Thanks for your efforts... PW
[Magisk] xdMatthewbx:
Yeah I tried Storage Isolation it doesn't even want to let me enable it for Momo since it doesn't use the storage permission (yet still has file access? that part confuses me) and even if I enable it for Momo it still detects :/. Plus it's a free trial I'd have to pay 30$ for nothing (no thanks on subscriptions, lifetime license please), pass.
[Magisk] KingCoder:
Is anyone having difficulties with their banking apps? Have the latest Magisk, Shamiko, Lsposed installs which have worked great but all of a sudden HSBC app will not open, tried hiding Magisk name, putting HSBC in denylist etc nothing working, does anyone have any ideas? Thx
[Magisk] Captain C:
Yes I have the same issue. Since the Shamiko v0.5 update my banking App won't open. If I revert back to v0.4.4 my banking App works fine again and doesn't detect root, etc.

Are you possibly on a custom ROM? I have EvoX on two devices and both have this issue with Shamiko v0.5. However, I have one device one stock Samsung ROM and my banking App with the latest Shamiko works on that.

Can't figure out what the issue could be.
[Magisk] tomoya12302:
I used odin to put magisk_patched.tar in the AP section and tried to flush it but it failed.

It failed only after "recovory.img" was displayed in the log.

I referred to https://topjohnwu.github.io/Magisk/install.html#before-installing-magisk

File transfer was done with ADB command

Is there a solution?

Galaxy A30 SCV43

Android10

windows10

odin 3.14.1
[Magisk] KingCoder:
Aah right wouldn't have even thought about reverting Shamiko.

I'm using OnePlus 9 Pro on stock ROM I'll try and revert Shamiko though and see if that works many thanks!
[Magisk] KingCoder:
Nope didn't work for me :(
[Magisk] Killuminati91:
How would I disable dm-verity with magisk nowadays? The newer app doesnt have any options.

Managed to get it running on my Vivo x70 Pro Plus.
[Magisk] J.Michael:
Search the two Magisk threads, there's a command line option. There is also advice that you do not normally need it. I do not remember whether you do not need the function, or whether you do not need to ask for it because it is done automatically.
[Magisk] Webexplr:
After installing the newest version of a banking app, I encountered this error every time I tried to launch the banking app. Is this related to Magisk/Shamiko?

(Also, sorry if this is the wrong place to ask)

EDIT: Lineage OS 19.1 Android 12 on Sony Xperia XA2
[Magisk] svendsvin:
I have the same problem. I'll guess it has something to do with this: https://issueantenna.com/repo/LSPosed/LSPosed/issues/1943
[Magisk] Thfaro:
Surprisingly I found out what these numbers and letters are. I am from a pretty long time ago, and only recently tried again to root. This is what I found when flashing (I should have seen this earlier tbh):

C:\Users\Cash America\Desktop\platform-tools>fastboot flash boot magisk_patched-24300_Z6OMY.img

(bootloader) is-logical:boot_a: not found

Sending 'boot_a' (17661 KB) OKAY [ 0.491s]

Writing 'boot_a' (bootloader) Image signed with key

(bootloader) 80012A99-867FDA48-4E357816-0E549F1B-B067FBD5

OKAY [ 0.342s]

Finished. Total time: 6.552s

Followed from: https://topjohnwu.github.io/Magisk/install.html#patching-images

I did notice that the phone had "vbmeta_a" and "vbmeta_b", but didn't know what to do with them. No "vbmeta" I saw though.
[Magisk] pndwal:
AFAIK vbmeta images will be essentially identical, but named for dual partitions... I believe you won't have "vbmeta" on A/B device... PW
[Magisk] rogers11:
Good morning, I've updated my Samsung Galaxy Tab S5e today via OTA (LOS 19.1, MiindTheGapps, Magisk 24.3).

Although there is an addon.d script for Magisk, only the GApps were reinstalled, not Magisk. I had to do it again via adb.

What could be the reason? File-permissions of the script are fine.