yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
CTS?

So LV Android 8.1...

SafetyNet in microG was only recently fixed; broken since mid 2019. Check you are up to date with new GmsCore. See notes here:

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

I'm not familiar with microG, but I would have thought you'd need USNF (generally Android 8+ launch version)...

Even if one instance of HKA (there are several) is made to fall back to Basic evaluation type (by use of mismatched model prop etc), YASNAC / other checker apps will show Basic evaluation type (this only takes any one instance) although another instance may still be getting a HKA... For this reason, many users find that they cannot pass safety net even with apparent Basic evaluation type without USNF which properly causes several types of HKA to fall back to Basic evaluation.

Further, if your FakeGApps + LSPosed module(s) or ROM itself don't include/spoof passing device fingerprint, I'm guessing you'll also need to set one w/ MHPC if using a custom ROM... PW
[Magisk] IngwiePhoenix:
Yes - CTS. Derp :)

I did later read about MagiskHide Props and that readme had a detailed piece of information about fingerprints, which has given me reason to believe that this might actually be my problem. Because without USNF, I don't even pass the basic attestation. With it, I do and only get the CTS Profile mismatch.

Thanks for your info, I guess today I will be looking into getting a proper fingerprint set up. I am running LOS 18.1 (sadly no 19.x for my device, yet). The readme also mentioned that I could extract a fingerprint from the stock ROM (which is 9.0 with security patch level from feb. 2020).

Again, thanks for your insight! :)
[Magisk] m0han:
you could also consider installing 'magisk bootloop protector' module by HuskyDG. could come in handy later on.
[Magisk] pndwal:
There have been quite a few fixes for Sammy since then.

IMEI issue was also mentioned in this thread by @dronkit:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86407975

I neglected to respond to his query (sorry mate! 😟)... If I had I would have confirmed that this may very well be an issue related to copying files w/ mtp on Sammy; because AP is very large compared with a stand-alone boot image, John's advice to use ADB is crucial; some users got file corruption with every attempt to transfer!

I cannot confirm that this was a file transfer corruption for others, or that it was a magisk issue, fixed or not. Perhaps dronkit will.

Seems no-one made a proper issue report on GitHub (following template) re. this, although this rejected attempt was made:

https://github.com/topjohnwu/Magisk/issues/5449

If it was a Magisk bug / regression, it may well be fixed if it was an additional symptom one of the issues fixed; I'd be trying 23.0 or Canary (includes more fixes) 24303. 24304 is buggy across the (device) board.

There have been further regressions fixed since then to; You can try recent Alpha Magisk (vvb2060 unofficial build), wait for next TJW canary (or other) build, or even try a recent TJW test build that fixes the 24304 issues; I've been using this for a while and it seems good / stable, but no guarantees. Info:

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

Please report whether issue is fixed / what cause was if you have success (or not!).

🤠 PW
[Magisk] pndwal:
& @TimmyP

... And another!... May well be an unfixed regression then... Please see post above... And please say if you used mtp to transfer AP or other files!... 🙃 PW
[Magisk] m0han:
Updates available: Fox's MMM 0.4.0 (35), YASNAC 1.1.3 r59
[Magisk] pndwal:
Interesting that YASNAC on playstore is still 1.1.0 r41. 😕 ... And 1.1.2 was yesterday! ...

Latest YASNAC 1.1.3:

What's Changed​

Show Google Play Services version

Check response time

Update RU translations by @TireX228 in #16

Update RU strings by @Displax in #17

Add UK translation by @TireX228 in #18

👍 PW
[Magisk] m0han:
don't know what 'check response time' does and how it shows
[Magisk] pndwal:
Adds / controls timeout statement. By vv:

Check response time

vvb2060 committed 3 days ago

if (statementTime.isAfter(timeout)) {

throw AttestationException("Attestation response timeout")

😜 PW
[Magisk] hjjiang:
just got into using HMA bc i updated to A12 and smali patcher didnt work, i needed mock location hider from lsposed.

Is it overkill to run both Shamiko And HMA together?
[Magisk] dronkit:
Thanks for your response!

Lately I was able to get a dirty fix by erasing the /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI/ folder as explained here. Maybe the nature of the "fix" is a clue as to if Magisk is the culprit or not.

And I didn't open a new bug report but commented on another bug report, cause I tink it's the same issue affecting mediatek chipset phones.
[Magisk] pndwal:
Thanks; yes, looks like same issue... So your device A-only legacy SAR w/ Magisk in recovery ramdisk?

Also, per @osm0sis suggestion, have you tried 24304 for its improved init compatibility?... Actually, I'd be trying the later actions run test build (a later 24304) to avoid multiple module bootloop regression...

Anyway, if issue is the same it's still WIP... PW
[Magisk] m0han:
greek and latin to me. thanks all the same
[Magisk] locolyric:
i just found out that banking app won't work on premissive kernel ...even on android 11, magisk v23 magisk hide(which work an hour ago on enforcing kernel)

anyway to hide the selinux status ?
[Magisk] zgfg:
EDIT: Try using Magisk Hide Props Config module, see (I didn't test since I don't have a kernel forcing Permissive mode):

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] pndwal:
When running permissive kernel, are you passing SafetyNet and have Device is certified in Play Store Play protect?

Also, you shouldn't really do that; Google's position is that Security-Enhanced Linux with security disabled is only for developers...

And here's John's (year old) thoughts on this:

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

🤠 PW
[Magisk] pndwal:
Here's code interpretation 101... (I'm incapable of anything beyond that. 🤪)

To understand basics of SafetyNet Attestation API, please see the developer.android.com training safetynet/attestation document linked from YASNAC "Learn more". Basically:

Like Magisk, YASNAC is open source. The source for 'check response time' function is the commit I linked:

Check response time

vvb2060 committed 3 days ago

Here we see that this changes 1 file: app/src/main/java/rikka/safetynetchecker/main/MainViewModel.kt

- the changes are highlighted in green, so clearly

val timeout = requestTime.plus(Duration.ofSeconds(10))
val statementTime = Instant.ofEpochMilli(statement.timestampMs)
if (statementTime.isAfter(timeout)) {
throw AttestationException("Attestation response timeout")

has been added so it's new.

We can deduce from the unchanged parts (file is quite small) that there are a number of "AttestationException" messages, ie. fail / error messages including:

- "Requires Google Play Services v13.0 or above"

- "Nonce does not match"

- "Application id does not match"

- "Apk certificate does not match"

So 'check response time' commit adds a new "AttestationException" (error) message to the existing list. The function will control when we see 'timeout' message.

So with this change the message will show when val timeout (the requestTime [time app makes call for a signed attestation 'statement'] plus a duration of 10 Seconds) comes before val statementTime ('EpochMilli', or time a signed attestation 'statement' from Google servers is received via Play Services per 'statement' timestamp in Ms).

I'm not sure what the previous behaviour was in the event that no response came from Google servers; perhaps the app would simply not respond while waiting... 🙃 PW
[Magisk] MECH_TECH:
I used ODIN to flash the stock ROM G960FXXS7CTA1 and was told not to go any higher or I will not be able to root it. I installed Magisk manager 22.1 at the time and rooted with it as per the Github instructions. I got a notifications that there where updates but didn't install them. Just the other day I got another notice and let Magisk manager update to 24.3 then updated Magisk also using the app.
[Magisk] pndwal:
I'd say yes...

If this:

https://xdaforums.com/t/lineageos-1...spoofing-ota-updates-for-s8-s8-note8.4370377/

There is no mention in OP or thread that ROM integrates fixes / spoofing for CTS profile... I'd try late fingerprints for same device or similar first, then Android 12 fingerprints for any device if no dice...

Worth noting other things that are reported to cause CTS profile mismatch in some cases:

- Selinux permissive.

- USB debugging on in Developer options.

- Incompatible ROM (Nb. in some cases this can be fixed by comparing props it a working ROM if persist.sys.root or other is simply set to an incomparable version. In other cases kernel may need a fix or swapped out for a working custom kernel.

Google whitelisting is not required where you don't have errors using GApps / Playstore (and this does NOT include Device not certified in Play protect) and only applies to non-certified devices (usually devices shipped with a China ROM / without GApps); won't fix SafetyNet either...

Not sure if you waited!... Anyway, let us know results... 👍 PW
[Magisk] Prof_Shekhar:
@pndwal @zgfg @ipdev

Thanks for your advice.

I have managed to configure the Magiskhide props and passed the safety net check.

All my banking and financial apps are working fine except one which is still detecting root.

Have even tried Shamiko to hide root. But the moment I disable enforce deny list, my all other financial and banking app stop to work.

Currently using Magisk deny list with enforce deny list and LSPosed Hide my list to get my most of the banking and financial apps running.

Hiding the Magisk app has no effect on the working of any of the banking and financial apps.

Is there anything else I can try to hide Magisk root?

Appreciate your suggestions.
[Magisk] pndwal:
Thanks for responding... I assume you don't have any issues with IMEI, network connection etc...

Seems there may be incompatibilities with late updates... PW
[Magisk] Andrologic:
Haven't read this entire thread but are running LSPosed/Xprivacy in addition to Shamiko? My experience is that it's absolutely needed to fully hide root when it comes to some of toughest apps.
[Magisk] Prof_Shekhar:
@Andrologic ,

Yes. I had flashed the Shamiko after putting all the financial and banking apps under deny list and disabling enforce deny list. Also, I had LSPosed running all the time first with all banking and financial apps selected under the HideMyAppList and later none selected under HideMyAppList. But this caused all my banking and financial apps stop running.

Finally, I had to turn off/remove Shamiko and enable enforce deny list to get my all but one financial and banking apps running again.
[Magisk] pndwal:
Please say how MHPC is configured / which fingerprint selected (for other users)...

Last Shamiko v0.4.4(106)?.... Please try this again w/ denylist disabled, zygisk enabled, and send screenshot of Shamiko message in Modules list...

It is needed for many, but apps are not supposed be detectable from Android 11 although with tricks they could be. Loopholes are supposed to be fixed in bank apps complying with Android 12 requirements.

Basics are SafetNet (USNF), hide root / other traces (Shamiko), hide Magisk (Hide the Magisk app, Android 11-). If still not passing, other techniques can be tried (LSP-XPrivacy Lua, LSP-HMA, other isolation / sandboxing / freezing solutions etc).

👍 PW
[Magisk] m0han:
and i'm incapable of comprehending any of this. it's all aramaic to me now. i'm surprised that you took the time to research and explain here; hopefully others might benefit from your post. good going, mate

p.s.: earlier, there used to be an opportunity to give 'reason for editing'. is it still available?
[Magisk] MECH_TECH:
No issues unless I turn on Zygisk then I have no network connection.
[Magisk] pndwal:
+ @dronkit, @TimmyP:

Ah... Same issue... confrms issue is not fixed (unless in 24304 or later).

So someone still needs to make a proper issue for this in Magisk GitHub.

This issue seems similar and some have reported A32 etc there:

https://github.com/topjohnwu/Magisk/issues/1801

but it seems that this is affecting more than the specified devices w/ Magisk installed in Recovery ramdisk (recovery mode), and other than mediatek devices... PW
[Magisk] zgfg:
Rootbeer and SCheck detect root bcs they are not in DenyList

Install Shamiko, disable Enforce DenyList, reboot and check (screenshot) what Shamiko says in Modules

For the remaining banking app you might need to use (try does it help) Hide My Applist
[Magisk] pndwal:
😕 Are you just playing dumb? - I'm no coder either, but I worked it out, and I've now put it in

plain

English for you... Have you made any attempt?

No C++, java, rust etc, no Latin, Greek or Aramaic, apparently limited English... Please say what language you do understand!! - Esperanto perhaps??... Sorry man... perhaps you just never cared to understand... 🤨

Apparently not... PW
[Magisk] pndwal:
👍

I suspect he disabled Zygisk last time... or didn't reboot...

Actually I'm interested to know if this can help anyone on Android 12+... PW
[Magisk] m0han:
i would've taken the hint and stopped here, if i were you. but, like i said, ....keep up the good work, mate.
[Magisk] Prof_Shekhar:
@pndwal @zgfg

I have reinstalled the Shamiko. Rebooted. Disabled Deny list, rebooted the device. Purged the cache and data of the SBI Card app. As you can see, the Zygisk is enabled throughout.

The SBI card is still detecting root and hence crashing.

As advised by @zgfg , I am continuing to use HideMyAppList for all the remaining financial and banking apps. They are all working fine.

Thanks once again for your time and patience 🙏🏻
[Magisk] asripath:
Updated from 24301 to 24305

both Magisk App and Magisk

through direct install method without issue.

V4A works too...

good update...

fixes 24304 issues.
[Magisk] pndwal:
This is interesting; It's a first for me!

If you've tried toggling denylist (only) on, then off again before checking if Shamiko is active, it may be time for a new GitHub issue ticket!...

If it's a Magisk issue it will be sorted normally, but if denylist status detection is a Shamiko issue it will be relegated to an LSPosed dev for fixing... I've seen this happen before. 🙃 PW
[Magisk] Prof_Shekhar:
Thanks for your reply.

I turned off the deny list first then rebooted device. Flashed the Shamiko. Rebooted the device.

But what puzzles me that the same SBI CC app was working flawlessly earlier with Magisk Canary version and HideMyAppList installed on Samsung Galaxy Note 8 stock firmware.

However, after l switched over to Lineage OS, I am able to get all banking and financial apps working fine with Shamiko and HideMyAppList, with Magisk deny list turned off except this SBi Card app which has so far defied all my attempt to get it going.

Let's hope some solution is found for it in the near future.
[Magisk] pndwal:
You could try this:

Ensure denylist is enforced.

Remove Shamiko &reboot.

Install Shamiko again and reboot.

Disable denylist

Check it Shamiko is working...

Just in case it needs to discover denylist during setup... PW
[Magisk] Prof_Shekhar:
I have followed the steps suggested by you. Unfortunately, the SBI Card app is still refusing to work. Rest all financial and banking apps are working without any issues under Shamiko.

Sorry to ask this silly question, but couldn't resist.

If Shamiko is able to hide the Magisk root, how is the Rootbeer and S.Check is still detecting the root. My little knowledge says that If these two apps can detect root, so can the SBI Card app. But the fact remains that all the other financial and banking apps are working fine without Magisk deny list but only with HideMyAppList enabled.

But if disable HideMyAppList, my other banking apps except Google pay stop to work.

Hope seniors in this forum can shed some light on this question.
[Magisk] pndwal:
Shamiko mileage varies per device... It seems to hide zygisk itself effectively for most, but it's sometimes effective, sometimes not for other traces of root... Don't think of detection of root as yes/no here; there's bootloader unlock, tmp mount detection, init.rc, isolated process leaks, Magisk app itself... It's a WIP!

Yup; Have you put those apps in denylist so Shamiko can hide root from them (disable denylist- Shamiko just 'hijacks' the list), or denylist can (enforced) - as mentioned by others?

They don't trust Google's official SafetyNet attestation (of course), so they get inventive; depends entirely on which traces / indications of root individual app Devs decide to use, as mentioned!

Did you enable Hide the Magisk app function in Magisk app?

And please say, does Shamiko say it's working now? ... I've mentioned your issue/anomaly to LSP Devs already, and they are interested to diagnose if issue persists... PW
[Magisk] Prof_Shekhar:
Thank you so much for a detailed reply.

Thank you so much for a detailed explanation 🙏🏻

I have disabled the enforce deny list under Magisk a long time ago. After your today's reply, I even removed the SBI app from the deny list, rebooted the device to see if any improvement. The app still refuses to work.

I have even tried to hide the Magisk app, rebooted the device. But no luck. The SBI Card app still doesn't want to work. Now I have restored the Magisk app as it's hidden status is not making any changes.

It appears to me that the Shamiko app is working because if it wasn't and with the enforce deny list disabled, none of my banking and financial apps would be working today.

Is there any other way to check if Shamiko working?

Kindly let me know.
[Magisk] pndwal:
You need to understand how things work; I explained clearly above 2 ways to use denylist, w/ or w/o it enforced... Only disable if Shamiko works...

Heep it hidden; the apps detecting root likely need this as well as other hiding methods to work! Don't think bank Devs limit detection to just one sign of root... They're not dumb cats; they want to trap you, the mouse...

Of course... Shamiko message in modules list will say "Shamiko is working as blacklist mode"!... Didn't you report it's message saying 'not working as denylist is enabled' earlier??

No worries; hope to hear it's working! PW
[Magisk] Prof_Shekhar:
Got it.

Magisk app hidden as suggested.

Of course. I didn't pay attention earlier to the message printed below Shamiko module. Yes. It says that it is working as blacklist mode.
[Magisk] mrspeccy:
There are braindead apps around that scan the system properties for the string "Lineage" and stop working when a match is found - even if there is no root access at all. The Danish MitID app is such an example. You could try to adjust all relevant system properties using the Magisk Hide Props Config module.
[Magisk] zgfg:
Some people, when they say 'root' do not think only about Super user privileges - for them, 'root' is already when you unlock Bootloader and depart from the stock Firmware

(Indeed, rooting is among others, to exercise the ownership off the personal computer + communication device in your pocket.

You paid expensive price and you want to be your own administrator.

But then, flashing the custom ROM is also a similar excersize of the ownership over that same piece of hardware)

And they don't need to say 'root', they can declare the 'unsafe' environment

Besides, SafetyNet itself, in the name and when it detects Basic or CTS failure, does not mention root

And when you look to the SafetyNet documentation, there could be various reasons for - one of them being a custom/not-certified ROM.

However, it is known that SN can be spoofed by various means, hence developers of 'banking apps' develop their own proprietary

checks (or even guesses) to detect if BL is unlocked, if custom ROM is installed, etc
[Magisk] Hallohannes123:
Guys I'm scared

I updated magisk canary but wifi wasnt working

I'm actually not sure what I did then but I think I tried to flash my old patched boot/recovery.img files

(I'm on the newest Mi 9 Lite xiaomi eu rom)

now My phone is stuck in recovery/fastboot

I thought flashing the original boot.img and recovery.img would fix this but it didn't!

I tried the command to uninstall all modules and flashed the uninstall zip file but it didnt help :(

I really dont want to factory reset

PLEASE HELP I am really stressed right now

I know this is probably all my stupidity but I dont know where to go from here

I just saw there is a new twrp version, should I try and install it?
[Magisk] pndwal:
Good stuff! 😛 ... Has it helped with remaining apps detecting non-Trusted Execution Environment (modified TEE, 'Root', Jailbreak, suspicious / custom modifications, tampering, malware infested device, wasp nests, cockroaches, other)?

And just for report to LSP Devs, can you confirm that installing Shamiko with denylist enabled was needed to fix incorrect detection of Denylist status? (Ie. Enforced DenyList may be required during Shamiko installation for proper Denylist detection.) 👍 PW
[Magisk] zgfg:
AFAIK, the old Mi 9 Lite should have separated Boot and Recovery, hence what does it mean "patched boot/recovery img"?

You patch only one of them, never both - I never saw any instructions asking to patch both (certainly not here neither in the official Magisk documentation on the GitHub)

In fact, it has been mentioned here many times that although Magisk declares Ramdisk No for many (older) Xiaomi phones, that you should always patch the boot.img

Frankly, it's hard to follow your path, but I would first try to dirty flash your Xiaomi.eu ROM again

Not sure is your Xiaomi.eu ROM the so-called recovery of fastboot ROM

a)

If recovery ROM, flash TWRP from Fastboot and then reflash that Xiaomi.eu ROM from TWRP

b)

If fastboot ROM, take that script (they provide two scripts) that does not wipe Data and flash through that script in Fastboot

But (b) applies only to Xiaomi eu MIUI 13/A12 ROMs (but I don't know if it was released for any model from the Mi 9 series), hence I would assume you will go by (a)

Then, in TWRP, delete also only the /data/adb folder, to bootloops in future if/when you later reinstall Magisk
[Magisk] pndwal:
Nah... Don't reset yet!

Fastboot flashing images should do it... Perhaps you used / enabled a special setting available for your device in Magisk (disable Verity, other)? ... Could be that other partitions were actually modified in this case, or if installed mods apart from Magisk...

So next, ensure you have full ROM package matching the currently installed one (just to ensure no incompatibility in /data) and dirty flash that... Should resolve corruptions w/ userdata intact... 🙂 PW

Edit: further to comments above mine, best to use fastboot type ROM (if EU mob have it available) as this is generally more complete (contains extra partitions from OEM)...
[Magisk] zgfg:
Xiaomi.eu ROMs older than MIUI 13/A12 are never flashed through Fastboot.

They install as zip files, to be flashed through custom recoveries.

With no vbmeta and the stuff

As in my answer, he just needs to flash TWRP from Fastboot, then to flash Xiaomi.eu zip (SAME VERSION) through TWRP, and while in TWRP to delete /data/adb folder to prevent potential issues if/when he would reinstall Magisk

All that assuming he did not have Xiaomi.eu MIUI 13/A12 - but AFAIK, Xiaomi did not release A12 through their beta for any Mi 9 (plain, Lite, T, Pro) yet, hence there are no Xiaomi.eu A12 (so-called Fastboot) ROMs yet
[Magisk] Hallohannes123:
Yeah, I'm sorry I didn't write this that clear, frankly I am not really that sure what I did.

Big mistake I did: Because of the ramdisk error, I thought I had to patch recovery.img but because that wasn't enough I also did boot.img so I always patched both (which somehow worked)

I tried flashing the original boot.img and a TWRP as recovery (both from fastboot), then I reinstalled my OS in TWRP... still not booting :,(