yashsingh1/xdaforums huggingface dataset:
[Magisk] hossanshihab:
i have issue samsung A10s 7F/DS Baseband S8 Magisk patched boot image successfully flashed. But magisk app show not installed N/A Please help me ANdroid Version 11. Bootloader unlocked.
[Magisk] tenghc:
Hi, do you happen to able to pass the latest pb engage MY app? If you have older version 2.57.0 can you share to me?
[Magisk] CharlieMHz:
I can reach the login screen without any root detection errors. As for older version, I do not have it. I usually get older version APKs from APKMirror or APKPure, but I can't find PB Engage there.
[Magisk] tenghc:
May I know what version of pb engage my you have there? Mine is version (2.60.0). Now mine showing this instead. After I update when I open it crashes and crashes even when I unrooted and uninstalled magisk thru TWRP. Not sure how to pass it now.
[Magisk] rodken:
PB Engage 2.22.0 - link
[Magisk] tenghc:
Thanks rodken, however this version is too old and couldn't run. I guess I have to live with chrome banking then😜
[Magisk] pndwal:
Is Magisk saying Ramdisk = No?...

There were problems rooting A10s due to MediaTek chip; that may have been fixed...

On Samsung it's unlikely that bootloader is compatible with ramdisk in boot on A-Only legacy SAR devices (A9 LV) so boot mode Magisk will probably fail. (Nb it does work with some Ramdisk = No devices like Xiaomi where bootloader inexplicably supports ramdisk in boot however)...

So have you tried recovery mode Magisk? ie follow Samsung (System-as-root) section in official Installation instruction page, but patch AP with Recovery mode checked...

Be sure to read instructions from top of Installation Instruction page to properly understand other device settings that may be needed also, and take careful note of warnings at end of Samsung SAR section.

Nb. You will need to boot via recovery per instructions / key combo in Magisk in Recovery section (if it's now working) in order to get system with Magisk; normal booting will still give Magisk Installed: N/A.

Nb.2. Magisk in Recovery is NOT the same as or even related to Custom Recovery installation method... Unrelated concepts...

Please report results here... 👍 PW
[Magisk] CharlieMHz:
Same, 2.60.0, from Play Store. You tried clearing the app's data or reinstalling?
[Magisk] tenghc:
Yup.. cleared, reinstalled thru Play Store and the crash persists. Installed safetynet fix by Displax Mod and it seems the same.
[Magisk] CharlieMHz:
You're using Delta now?
[Magisk] tenghc:
Yes.. now using Delta (25210), installed module attached below. My Touch N Go ewallet works, now the only problem is PB Engage MY. Magisk hidelist also as attached.
[Magisk] CharlieMHz:
Hmm not sure about that then.
[Magisk] zellleonhart:
I have the same problem starting v2.6.0, I am also using magisk Delta and my TNG ewallet works fine. This only happened with v2.6.0, previously it worked just fine. If you happen to find a fix please let me know.

Just for the record, I have sulist enabled, hide-my-applist, USNF Displax's build. It also doesn't work even when I disable zygisk, so that is not the cause.
[Magisk] pndwal:
Official USNF has intermittent failures/timing issues (mostly affects G Pay/wallet... @Displax's build has fixes... (Some still need his older pre-part-time spoofing v2.3.1-MOD_3.0 build. https://github.com/kdrag0n/safetynet-fix/issues/248#issuecomment-1514450440 )

No need for gps in hidelist... Or anything G other than G Pay/wallet AFAIK....

Might possibly help... PW
[Magisk] tenghc:
Hi.. I found a solution. My method is very easy which I just toggle USB Debugging off in developer options. Now it can run as usual.
[Magisk] pndwal:
Some wanted to add this hiding in USNF... @kdrag0ns's response was 'why?; Users can just switch it off if they want"... 😜 PW
[Magisk] kheldar31:
Hello,

S10 Plus. I always install the weekly updates for LineageOs and re-install Magisk-v26.1.

Today, I updated to lineage-20.0-20230621-nightly phone booted fine then I flashed magisk again, it booted fine.

Then I did direct install in Magisk app and it's on bootloop now.

I can enter lineageos recovery mode though I flashed TWRP now to try and make a backup however turns out i cannot because my device is encrypted.

Any tips?

What I've tried:

1: flash boot.img that I downloaded from https://download.lineageos.org/devices/beyond2lte/builds

2: flash magisk again.

3: uninstall magisk via adb

4: flash lineage-20.0-20230621-nightly-beyond2lte-signed.zip and gapps again.
[Magisk] yongjiunkirito:
mine still not working even when the usb debugging are off in the latest update PBE Engage MY (2.61.0)
[Magisk] yongjiunkirito:
hi, do you found any fixes for it?
[Magisk] zgfg:
Magisk Stables stays also 'stable' with bugs it was released with. Whenever you have problem with Stable, try the newer Canary
[Magisk] yongjiunkirito:
im using magisk delta 25210 and I can't use the latest version of PB Engage MY, it detected the root even I'm on Enforce SuList.
[Magisk] zgfg:
SuList works in the opposite, Whitelist mode - it exempts the listed apps from hiding. Either use MagiskHide mode and list your app there or use SuList mode and do not list your app there

But there are also other detections and hidings. This is just first and the easiest (but must be properly set, not the opposite way!)

Hints: search about Shamiko, USNF, HMA, potentially Sensitive Props, BootLoader spoofe, etc. There are tons of similar posts to find more about
[Magisk] pndwal:
You may have solved this if you installed then fully uninstalled Magisk as it appears...looks like a module likely became incompatible w/ recent LOS update... Nb. w/ zip installation now modules and Zygisk are disabled until you flash w/ system booted to set up module/selinux rules directory, but after doing that modules would have come on line and likely caused issues...

Assuming these have now been removed w/ uninstall, you should be safe to flash Magisk again...

If not, be aware of ways to disable modules in case of issues/bootloop... Basics are covered in official Magisk FAQs page.

🤠 PW
[Magisk] GAGANKXDA:
XPrivacyLua isn't supported anymore, any advise for alternatives..?

I'm on A13 with Magisk 26.1 (denylist enabled & trying to figure out an option to run SBI Yono
[Magisk] pndwal:
Pretty easy it seems... I get this far:

My device:

Xiaomi RN8T stock A11 MIUI,

Latest official Canary Magisk

Magisk App hidden in stub,

Latest Shamiko public release (for proper root hiding),

LSPosed Hide My AppList module configured to hide all apps associated with root,*

OEM unlocking disabled,*

USB debugging disabled, *

Developer options disabled.*

* = confirmed not needed for your app.

Have you taken Hide the Magisk app option?...

You may just need to swap denylist (a development tool) for Shamiko (proper root hiding)... 😜 PW
[Magisk] GAGANKXDA:
XPrivacyLua isn't supported anymore, any advise for alternatives..?

I'm on A13 with Magisk 26.1 (denylist enabled && trying to figure out an option to run SBI Yono

Unfortunately HMA didn't worked either for me.. have Magisk is aready hidden & i'm able to use other two banking apps properly except SBI YONO :'(
[Magisk] pndwal:
Do you have bank denylist, disabled with Shamiko working?... no detections in Applist Detector?... PI deviceIntegrity passing?… All XPosed modules and

any

apps associated with root or modding (not just root apps) hidden from bank app (ie added to a HMA template etc)?...

What device? What does Momo detector show?... PW
[Magisk] GAGANKXDA:
Yes, have already disbled with Shamiko working.. other two apps (Axis & ICICI) are working.... Device integrity too good as rechecked with YASNAC.

Just a question on HMA, i selected only SYSTEM (which is selected by default) & SBI YONO in HMA, do i need to select every app which requires root out there..?
[Magisk] pndwal:
You can't check PI deviceIntegrity with that... It's for SafetyNet API which is deprecated... Use Play Integrity API Checker...

You mean system framework in LSPosed?.. that's all I have...

But I didn't need HMA hiding for Yono... Still you may have something else it detects...

... If it's detecting something you need to hide HMA and all apps I mentioned incl hidden Magisk stub from Yono!... Use blacklist mode and add a template with all the apps... May be detecting any number, I don't know which...

And you didn't screenshot/say Applist Detector or Momo detections... PW
[Magisk] rodken:
Are you flashing boot.img via TWRP or fastboot?
[Magisk] nicholaslimck:
Seems like Singpass has upped their game with version 18.2.1. My setup with Magisk Delta, Shamiko, USNF, MagiskHide Props config and Hide My Applist used to work, but it started being detected after a recent update.

Currently running Magisk Alpha with the same setup to no avail.
[Magisk] wyt18:
Someone on the vkey thread claims to have bypassed 16.2.1 by preventing the app update from being forced. It requires alpha though and I am on delta
[Magisk] sawdoctor:
Anyone had issues with magisk unrooting itself? Just suddenly had no root and magisk said it wasn't installed. Rebooted and then I was rooted again and magisk was installed again. Never experienced it before
[Magisk] pndwal:
Still getting this far with Alpha Magisk (26103), Shamiko and no special settings (SingPass18.2.1):

... Of course this builds new native bridge loaded Zygisk from Shana's Metagisk which is how Riru was loaded since Riruhide was a thing... 🤠PW
[Magisk] ayhamthedude1:
Rooted using latest magisk and tried canary, I also have latest version of twrp, However when I turn on zygisk the phone freezes after a short time and restarts. I can't find a solution but to disable it. That way I lose Safety net fix and face Id mod. LIneage Os 20
[Magisk] beeshyams:
Just as FYI, yono lite works fine without any special tricks-displax USNF mod, regular Magisk (25.x),Hide list enabled and configured hide list yono lite, citibank and PNB

Hope this helps
[Magisk] pndwal:
If you don't have an unstable Zygisk module (I don't know about face ID mod; same with that disabled?) you likely have this/similar known issue:

Opening apps causes the system to crash and reboot sometimes, if Zygisk is used. needs investigation #6569 opened on Jan 27 by MarisaDAZA

Looks like new refactoring of Zygisk to native bridge (WIP since March) should fix this and other Zygisk issues, and should come with next (Beta?) release... This:

yujincheng08 linked a pull request on Mar 5 that will close this issue

Refactor zygisk to use native bridge to inject #6659

And this comment:

https://github.com/topjohnwu/Magisk/issues/6569#issuecomment-1539735636

Nb. This fix seems to replace this earlier PR (with more details):

https://github.com/topjohnwu/Magisk/pull/6920

... Hope it's close now! 🙃 PW
[Magisk] pndwal:
Are you on a custom kernel per chance?... Device, Magisk version, module etc details?... 🙃 PW
[Magisk] chiteroman:
Why use Zygisk when you don't need it? 😜
[Magisk] pndwal:
Passing PI deviceIntegrity? (Many of us need.) PW
[Magisk] chiteroman:
Only device? 😎😜
[Magisk] bizdatech:
Guys. Is been very long thread. Not lazy but the search cant find it haha.

Go to the proper novice method all. Not working

Magisk latest and safety's net and mod.

Specially obvious on tng apps

So finally found this thread for the tng solution.

Fixed and it works.

So now turn into my defaults ewallet unable to use .

Grab apps

The amount RM not showing

When start to hit pay. Cannot send money.

Now currently using magisk delta basic only .

Sulist and hide all the needed.

Boost r working but not yet try to pay.
[Magisk] chiteroman:
KernelSU much better than Magisk :P
[Magisk] amk316:
give us more info please

phone

os

setup

steps
[Magisk] chiteroman:
Everything is in the screenshots 😂 My phone is a POCO X3 Pro using latest Xiaomi.eu ROM, I just flash system rw script (modded) and modify framework.jar with some hooks using Pine.
[Magisk] Sm00thCriminal:
Hey, I was testing some things out when and turned off zygisk and rebooted but now magisk says - "The hidden magisk app cannot continue to work because root was lost. Please restore the original apk." Rebooting leads to the same thing. I have lost all root access and a new app shows N/A next to magisk. What did I do and how do I fix this thanks.

I was using magisk delta btw

Edit: Nvm I had to just reflash. Not sure how or why I randomly lost root but reflashing worked fine.
[Magisk] Sm00thCriminal:
Is shamiko still working for people to be able to hide Zygisk? Momo shows zygisk anytime Shamiko is on.
[Magisk] chiteroman:
Momo uses private methods made by Zygisk contributors. Just try Shamiko in real apps which you will use.
[Magisk] genesis89:
Do these methods still work? I tried the latest magisk and magisk delta but still can't get pass the startup logo. My phone is Poco F3 running LOS20 latest build.
[Magisk] chiteroman:
LineageOS isn't a recommended ROM for daily use, it has a lot of modifications and don't hide nothing. If you want to still using LOS you should try with this Magisk module: https://github.com/Magisk-Modules-Alt-Repo/sensitive_props/releases/latest
[Magisk] genesis89:
The app doesn't work on VoidUI either but I'll try your method. Thanks.
[Magisk] ipdev:
I would suggest you look into the LineageOS project before you make a comment like this one.

LineageOS - [website] - Link

LineageOS Charter - [github] - Device Support Requirements

LineageOS Gerrit - [review.lineageos] - Link

LineageOS GitHub - [github] - Link

:cowboy:
[Magisk] chiteroman:
Yeah, and?
[Magisk] digger16309:
I'm using LOS 20 on a Oneplus device, rooted, with LSPosed, Shamiko, USNF, and all my banking apps work fine.
[Magisk] pndwal:
I would highly recommend LineageOS to anyone as a first choice in custom ROM for Magisk rooted daily use... I have stock MIUI on my phone, Redmi Note 8T, but use LOS on my tablet, Mi Pad 4...

LOS is close to original AOSP, does proper/responsible testing and doesn't spoof or hide any expected signals as a matter of policy (and pride) which means that Magisk solutions, particularly those that spoof props etc like USNF and those allowing OEM specific features on other devices, generally work as expected... For use with Magisk, spoofing is completely unnecessary and a ROM clean from spoofing solutions is important to me.

Many custom ROMs that have integrated SNF and other spoofing to pass Play Integrity verdicts and more work well without root but cause various conflicts with Magisk modules and even with Magisk itself sometimes... USNF has overcome many issues with ROMs building custom PI fixes, but issues persist with some of these... Of course, a number of these ROMs use LOS code/source trees as their base...

Because of their policy (to be Google compliant), LOS is actually in a prime position to submit builds for Google certification and the Google "Tech Lead for Android hardware-backed security subsystems", Shawn Willden, has actually encouraged them to persue this approach although I'm not aware of any further discussions about this with Luca Stefani or others at LOS... If that were to happen with a custom ROM, it would be both a first and an added boon for this community...

Nb. Most (all?) of the device integrity related prop values set in that module are also handled by USNF and Shamiko modules... It will be handy for those trying to pass PI deviceIntegrity on older (pre A8) devices or those with broken keymaster implementations etc without USNF if not using Shamiko however...

🤠 PW
[Magisk] pndwal:
Wannit all? 😆 PW
[Magisk] intel_core_i7:
I have no idea which thread is more appropriate to reply to this message, here or the PI thread. I have seen many strong integrity passing screenshots, all from Xiaomi devices. Perhaps there is a specific vulnerability related to Xiaomi's bootloader? Devices has been passing with a custom rom i have seen: Poco x3 pro (vayu, yours, xiaomi.eu rom), Mi 13 (fuxi, from a member of kernelsu telegram group, also running xiaomi.eu rom) and poco f5 (marble, running evolution x).

I haven't seen anyone reporting this on any other device brand.

I suppose you don't have zygisk on ksu installed, right? If yes then it's a pain in the butt to hide it
[Magisk] zgfg:
Sweer45' LSPosed module

BootloaderSpoofer_v1.1.apk

is only for KeyAttestation (to show BootLoader locked)

For PI API to pass Strong Identify, there is the experimental USNF module

safetynet-fix-v2.4.0-MOD_2.0-test.zip

For both modules, see in the other thread, screenshots were not limited to Xiaomi and not to KSU

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88756031
[Magisk] intel_core_i7:
Never knew that there is an USNF test build that may passes strong, thanks!
[Magisk] J.Michael:
Is there really such a shirt, or did your niece make this picture in Photoshop?
[Magisk] zgfg:
AI
[Magisk] pndwal:
... Someone on TG Alpha discussion posted it... Think it looks real?... Anyway, just thought you might like it... 😋 PW
[Magisk] Keks95:
IT worked great for a few months, but now Google Wallet says my Security dont meet the standarts. I have installed the latest 2.4 saftyfix, reset Data of Google Wallet and rebootet. But it didnt worked.

Galaxy s8 dreamlte with lineage os 19
[Magisk] pndwal:
Latest official?... Nb. that's still largely broken... Use @Displax fork with fixes... PW
[Magisk] Keks95:
Just installed the modded Version Downloader from GitHub. But it also get the Same error
[Magisk] Lughnasadh:
Canary 26104 has been released:

For those on the Pixel 6 series, this does indeed fix the boot patching problem of Canary 26103.

Magisk (d390ca2f) (26104)​

Lots of code is migrated over to Rust!

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation
[Magisk] Keks95:
Now i'm confused... Google Pay/Wallet dont Work but i got These testresults:
[Magisk] BillGoss:
Clear storage of Google Play Services and Google Play Store and then reboot your phone.
[Magisk] Keks95:
Will try that
[Magisk] Keks95:
Yeah Baby, after a few tries i paid successfully via Google Wallet today :) thx for your Help. Lets See how Long it Take to get the next failure
[Magisk] sawdoctor:
Unfortunately anytime any bank apps/wallet fail/detect root for whatever reason it seems you always have to clear play services data which can be a pia. Had to factory reset my watch to get it to pair again when I cleared play services data
[Magisk] Danny94:
cant get xiaomi.eu v11.0.4 A10 working (~2019).

Device integrity always fails...

Tried already MagicHideProps and used certified fingerprint + force basic attestation.

Tried the PlayIntegrityFix.zip USNF which should be able passing strong, but this one causes playstore to loop force close and cant pass none integrity.

Currently im back to USNF2.4.0 which which makes basic pass.
[Magisk] chiteroman:
To pass, at least, basic and device you only need PlayIntegrityFix/safetynet-fix (only one, you can't have two installed at same time), enable Zygisk and remove GMS processes from deny list.

Try again only with one module.

If this don't work maybe the problem is the custom ROM.
[Magisk] pndwal:
Some XisomiEU ROMs integrate SNF badly apparently and conflict with USNF etc... Some are apparently fine... @Displax said this:

😬 PW
[Magisk] fillwithjoy1:
Is there a way to pass the strong_integrity, i.e. say that the bootloader has been locked in the device?
[Magisk] Danny94:
yes i was already trying using only one fix at the time and have enabled zygisk.

isnt there any chance to make it work ? its a rom from Nov 2019.

I got a screenshot from momo.

To make magisk work, i had to extract boot.img and patch it with magisk app (+patch vbmeta)

I cant install other roms like aosp because kernel sources are still not released and therefore a lot of bugs.
[Magisk] pndwal:
Less chance if it's that old... Is there no up to date build?... They generally built their own SNF implementation to pass S/N w/o root... It probably doesn't pass new PI deviceIntegrity verdict and may not even pass S/N anymore so you rely on Magisk module working over old SNF implementation... Seems they didn't even properly follow the @kdrag0n template (in Proton custom ROMs) for integrated SNF which makes it difficult to avoid conflicts with module SNF / PIF solutions...

I prefer 'clean' custom ROMs (w/o inbuilt spoofing etc) for use with Magisk... Then there's no unexpected surprises/conflicts... Eg official LineageOS... PW
[Magisk] Danny94:
There is a miui 12 Rom, but that one is draining a lot and not really newer (2020-early 2021).

We dont have lineage support aswell because of missing Kernel sources :(. K20 pro.
[Magisk] pndwal:
... Maybe ask XaiomiEU to supply a SNF-free build with the sources they have?... Explain the problem? (It'll affect other users too)... PW
[Magisk] Danny94:
I highly doubt they make a change in a 4 year old rom, there wont be other people installing it aswell. Most people stick with latest stuff even If is buggy and bad battery-performance.
[Magisk] pndwal:
Did you say device? PW
[Magisk] Danny94:
Yes redmi k20 pro China.
[Magisk] pndwal:
Pinging IgorEisberg

Any chance you could help?... 🙏 😛 PW

PS. SafetyNet fix / Play Integrity free builds may be a good idea for Magisk users generally, or at least some checks to ensure embedded fixes don't conflict with (often more up to date) USNF, PIF or Partial PIF Magisk modules... 👍
[Magisk] zgfg:
Use PlayIntegrityFix-XIAOMIEUONLY.zip from Sweer45

Posted in another thread, made specifically for Xiaomi.eu

Unlike for other ROMs, for Xiaomi eu you need single, only one prop to spoof: ro.product.first_api_level

That module will do exactly that (spoofing no other prop), via Zygisk - hence targeting only gms.unstable process

You need DenyList and Shaniko (configured.as explained elsewhere) and that module, without any other derivative of USNF (and no MHCP)

Try that, works for me (Strong Integrity) on Xiaomi eu MIUI 12.5 and 14, tested and confirmed by other Xiaomi.eu users

If you use USNF 'generic' versions (specially outdated from this thread), you may expect a mish-mash of spoofs, and no wonder that PI would fail
[Magisk] rodken:
Do you recommend to simply disable USNF or complete removal?
[Magisk] Danny94:
Unluckily this has not been working.

I have installed the module "PlayIntegrityFix-XIAOMIEUONLY.zip" by chiteroman (swer45') and shamiko v0.7.3-174.

Have enabled zygisk, enabled denylist, disabled denylist enforcing, added gms and play store to denylist.

According momo magisk is not visible anymore, but everything else is still detected (post above). Im passing basic integrity only still.
[Magisk] zgfg:
For Magisk it's the same thing (for properly implemented systemless modules. For user it's cleaner to remove modules he will no more use
[Magisk] zgfg:
Btw, no need to add Playstore to DenyList (as mentioned tons of times here and in the related threads)

All apps call PlayIntegruty API though Google Play services (gms)

----

But ask Sweer45 in his thread for further help with the module
[Magisk] m0han:
...need PlayIntegrityFix....enable Zygisk and remove GMS processes from deny list.

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