yashsingh1/xdaforums huggingface dataset:
[Magisk] heinhuiz:
Can't find where exactly, but I do remember someone mentioning that Santander only detects Magisk 26+. Might be worth trying to downgrade to 25.2 again.
[Magisk] ipdev:
Hi all. 🙂

I am not sure if anyone is interested..

The other week, I decided to use the built-in OTA updater in Lineage (19.1) on my Pixel 3aXL.

Mostly to test osmosis' addon.d update.

Magisk - [GitHub] - commit

I got mixed up and thought this also included addon.d support for non-recovery Magisk installation.

Magisk - [GitHub] - issue

---

Long story short, I made a module that copies the addon.d script and overlays it into system.

This allows the magisk survival script to be found and used during a system OTA update.

Magisk Survival Module - [GitHub] - Link

Please read all of the readme if you decide to use it.

- This only works with addon.d-v2 (A/B slot devices).

Cheers all. :cowboy:
[Magisk] ChillDuder:
fyi, for the hide&dev pros here:

german comdirect bank's authentication app phototan is always dedecting root regardless of delta/mods/whatever.

Member srothe found out, that maybe traces of root/magisk are in /proc/ (without root it's seems kinda a view/overlayfs) and build a firda script which solved root dedection for that app.

link: https://xdaforums.com/t/comdirect-phototan-app-detecting-root.4274825/post-88365303
[Magisk] hemfreitas11:
I had this issue with Santander as well, i uninstalled official Magisk and installed Magisk Delta 25210 and the issue was fixed. In Delta i have MagiskHide enabled, Zygisk enabled, installed Shamiko, installed universal safetynet fix, and magiskhide props config to change my device figerprint to an Android 10 device to pass safetynet and play integrity. Google Wallet also works normally. Some other bank apps like C6 bank and Digio can still detect Zygisk though.
[Magisk] pndwal:
I posted about the pending implementation of Riru style Zygisk loading (using Native Bridge) in Magisk several times... I also put something here in relation to Native Detector's ability to detect Zygisk and how NB loading can hide Zygisk memory from /proc/maps string scanning:

Expect this major change, which will also fix several related Zygisk issues, to arrive with 27.0... Shana's PR is still being tested... Check Magisk Actions runs going back more than 2 months now...

I put information here:

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

and here:

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

and linked earlier posts...

Then, as mentioned here:

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

I got tired of waiting and tested early implementation in current Alpha Magisk (really this is a testbed for LSPosed Devs Magisk enhancements):

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

Aside from success bypassing detections for bank and detection apps mentioned there, I can now fool Sparkasse pushTAN again:

(I discovered Hide My Applist XPosed module fixed earlier updates, but seems they soon started detecting Zygisk and it failed to open again until now.)

Also your Comdirect photoTAN:

My device:

Xiaomi RN8T stock A11 MIUI,

Latest @vvb2060 Alpha Magisk (unofficial)

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.

😋 👍 PW
[Magisk] pndwal:
... Bit more Native Bridge Zygisk testing...

Santander:

Singpass:

Nb. Root detected (before adding to denylist w/ Shamiko) locked me out completely... After adding user can use app but gets this warning due to 'compromising' app(s) being detected:

After configuring Hide My Applist LSPosed module for this app there are no more detections at all. 🙂

We Connect (VW)

C6 Yellow:

Digio:

Revolut:

(Denylist enforcement disabled 😉)

Citibank SG:

Nb. Needed Hide My Applist configured in whitelist mode (system apps excepted) for this app... My blacklist wasn't sufficient...

BNA+:

... I didn't need Hide My Applist at all for this one...

--------
​

... Please see my post above regarding this POC for official Magisk 27.0+...

🙃 PW
[Magisk] wyt18:
Thanks! How did you get these results and Native zygisk bridge ... Magisk Alpha? Or wait for 27.0?
[Magisk] pndwal:
Yes, that's what I said... Be aware that proper implementation has has already been a 2+ month project by Shana and other LSP Devs... Alpha implementation works but should still properly be viewed as a POC/WIP at this stage...

There will no doubt be further work / debugging before we see it built in TJW Magisk, likely in 26.x Canary or in a 27.0 public Beta release...

So even when this comes to official Magisk there will most likely still be work to do and potential issues... Most should probably wait.

🤠 PW
[Magisk] mrjuniork:
@pndwal

7 pictures fully sized in one post 🤯

You gotta be kidding me 😂
[Magisk] pndwal:
Oh... Answered 5 members in one post... Thought I was doing well! 😉

But good point... probably a bit much... Wait... Downsizing... 👍 PW
[Magisk] mrjuniork:
Very economic way of answering several questions indeed 😅

Thx a lot, it's so much better now. Phone doesn't overheat any longer swiping through that page 😉
[Magisk] spicediablo:
Would you explain further how to get citi app working? Do I need to install additional modules for delta?
[Magisk] spicediablo:
Would you explain further how to configure magisk delta to work with citi? I had citi included in hidden list
[Magisk] pndwal:
You'd need to ask a Delta User for that information... I've never installed it sorry... 🙃 PW
[Magisk] gallegonovato:
Good afternoon:

First of all I apologize for taking time to respond, but I was busy.

I put without problems the connection in Adaway's allowed. And Magisk seems to be working fine.

I'm still looking for the source that blocks it. But now that connection is in allowed

Best regards and thanks for your help and time :)
[Magisk] Reator:
Can you help me with CItiBank TH?

Citibank TH - Apps on Google Play

An easy way to view your account, make payment and find privileges from Citibank

play.google.com

I have Magisk 26100

HMA

MagiskHide (Module)

Shamiko

USNF

but this bank still detected.
[Magisk] pndwal:
Did you read the comment at end of my post? PW
[Magisk] Reator:
I'm sorry, which one?

Or the Citi SG one? Cause I already try CitiSG (HMA in whitelist mode) but it still detected.
[Magisk] pndwal:
The last one... The 'post above' explains it's a proof-of-concept for Magisk 27.0+ in Alpha Magisk fork... Clearly you'd need that to try it, but better for most users to wait till refactoring project is complete and released in 27.0... 😬 PW
[Magisk] Darkmasterhk:
Turning zygisk on causes my phone to stuck at the boot animation (Asus Zenfone 9), anyone an idea what to do? Magisk 26.1
[Magisk] zgfg:
Do you have some modules installed and which ones?

Particularly, you should not have Riru modules - Zygisk and Riru are not compatible

Disable all modules and try again
[Magisk] Darkmasterhk:
Thanks, no I don't have any modules installed. I started from a clean flash, not even all my apps are installed.

Also it worked a few month ago, with an older version. Because it's a fresh install I even cleared data a couple of times, switched kernel, but still the same result. :/

A few month ago I switched from stock rom to a custom one and returned to stock yesterday. Now it doesn't work anymore.

If I remember right, version 26 brought some bigger changes, could it be related to them?
[Magisk] jons99:
works fine on my zf9 I'll tell you what you can do first flash magisk 25.2 in twrp then turn on zygisk reboot once and then update with direct install
[Magisk] pndwal:
When returning to stock I assume you clean installed (factory reset / data wipe)... Also, did you flash recovery or fastboot type ROM? ... And did you extract and patch boot image from current ROM? PW
[Magisk] Darkmasterhk:
Hm maybe I try this, just finished setting up everything, afraid of having to wipe again

As mentioned, I wiped data / factory reset more than once by now.

It's a recovery type.

Yes, did patch it, else magisk shouldn't work at all anyway. Also tried using a custom kernel no difference. :/
[Magisk] pndwal:
Fastboot is a more complete ROM generally... When something is messed up by custom rom, Fastboot is sometimes needed to restore all partitions...

I meant are you sure it's boot.img from current ROM; eg if you took an OTA update you'd need to download new full ROM to get boot.img (or use TWRP backup dump of new boot.img)... 🙃 PW
[Magisk] m0han:
Riru modules. Ruru is 'that app'. (Pretty sure it was a typo.)
[Magisk] zgfg:
Yes, and it's actually due to the stupid spelling checker - corrected now
[Magisk] mmbaknnba:
Hello, greetings.

Pardon any mistakes in my English.

I'm using Nord AC2003 (Global), OOS12, build F.18. Just want to share my Magisk's setup for apps detection:

1- Started with the latest official Magisk (26.1).

2- Zygisk + Enforce DenyList enabled.

3- Changed to Magisk Alpha (26101).

4- Randomized the Magisk Alpha app's name.

P/s: Use the Alpha at your own risk. Already tested the Magisk Delta, have some issues with my modules, specifically with font module, besides I'm not really a fan of the GUI. Official Magisk's GUI is better for me.

Tested with Applist Detector, Momo, SafetyNet Test & TB Checker.

My modules: Busybox, Kill GMS Font, Product Sans A12, Systemless Hosts, Systemless Host - Unified, Official USNF & VoEnabler.

I'm from Malaysia. So basically my daily apps with pay function are Hotlink, Celcom, Yes, TnG EWallet, Shopee, Pos Malaysia & HSBC Malaysia. When I was on official Magisk 26.1, only TnG wasn't working. With Delta & Alpha, all apps are working flawlessly.

8 screenshots.
[Magisk] pndwal:
Official Universal SafetyNet Fix is broken and most use @Displax's modded build, but I think you don't even need it for your Nord...

I'd be interested to know if you pass deviceIntegrity in Play Integrity API Checker if you just remove/disable USNF, add Google Play Services attestation/droidguard process com.google.android.gms.unstable and main process com.google.android.gms in denylist, install Shamiko module, deselect DenyList enforcement (ie. unenforced, so Shamiko can use it as hidelist) and reboot...

Also, installing LSPosed and configuring Hide My Applist XPosed module should remove Magisk stub detections...

🤠 PW
[Magisk] m0han:
Shamiko update (v0.7.1) available

Spoiler content hidden.
[Magisk] mmbaknnba:
I did the test again with both builds on 25.2, 26.1 & Alpha. Surprisingly, Basic/Device integrity & SafetyNet passed. Before this, I remembered I installed the modded build and failed, but I'm not sure on what Magisk's version. So, I decided to use the official one.

Failed. Any words on this?

Thanks for this information. I didn't know how to configure HMA before, so I tried again, and success in hiding the stub. Was my setup correct? Btw, what is 'PM Intent Queries'?
[Magisk] pndwal:
With USNF disabled (reboot), do you see BASIC as evaluationType in YASNAC?

An app detection method used by some apps... Seems you're on an old version if seeing that option... I don't have it in 3.x HMA... PW
[Magisk] mmbaknnba:
Yes.

Not really, I'm on the latest version 3.1.1, downloaded from GitHub.
[Magisk] pndwal:
Yup, so OnePlus's broken keymaster implementation causes fallback... You should be able to pass ctsProfileMatch and deviceIntegrity without USNF...

You could try with the two gms processes in denylist, keep Shamiko and install MagiskHide Props Config module but don't configure anything in that; MagiskHide sensitive props will adjust by default... (If you didn't fully uninstall that previously you may need to reset it's settings)

So where did you see PM Intent Queries reference? PW
[Magisk] rodken:
YMMV - after trial and error on the OP8, the modded USNF was and still is a requirement.
[Magisk] pndwal:
With USNF disabled (reboot), do you see BASIC as evaluationType in YASNAC on OP8? PW
[Magisk] rodken:
Negatory.
[Magisk] pndwal:
So I'm not sure keymaster implementation is actually broken in your device... Usually that causes fallback to basic evaluationType (without USNF triggering this with fake keystore registration)...

Nb. Basic evaluationType seems to relate only to what verdict type server end enforces. This is different from attestations being supplied by droidguard on device and fallback required to force basic attestation, so some devices will give 'BASIC' only while still using hardware backed attestation on device... PW
[Magisk] beeshyams:
Requesting folks to guide:

I just bought and rooted Pixel 6a. Cat & mouse with banking apps will continue and my fear is at some point when Integrity API kicks in some apps may refuse to work.

In such a situation, I plan to unroot BUT will am unlocked bootloader be still a red flag for such apps?
[Magisk] jons99:
you can also lock the bootloader if you like (after you unroot)

it's not a samsung you don't burn any fuse by unlocking a pixel
[Magisk] beeshyams:
True but data loss, which is a pain
[Magisk] pndwal:
Play Integrity API is already current and adopted by most banks... SafetyNet is deprecated and largely abandoned already...

Guess you mean when banks move to enforcing PI strongIntegrity instead of only deviceIntegrity...

In this case you'll certainly need a locked bootloader. 😜 PW
[Magisk] beeshyams:
Thanks for confirming my worst fears 😉

Now that I've rooted let's see how far I can keep up with this game 🤞
[Magisk] sn00x:
You can root and still have a locked bootloader. You can even switch between root and unroot without losing data.

However, you need to build the ROM yourself to be able to sign a patched boot image.

See here
[Magisk] pndwal:
& @beeshyams

But this won't help with PI strongIntegrity...

Only green state B/L will allow passing... You'd go from orange to yellow, but with custom keys strongIntegrity verdict will still fail. 🙃 PW
[Magisk] shoey63:
Can confirm. Tried on Pixel 6. Verified bootstate=yellow and can't pass strong integrity.
[Magisk] spida_singh:
Im using the latest 'Magisk Delta' build and USNF 2.4.0 MOD 1.2, as well as blocking the following URL using PCAPdroid:-

firebaseremoteconfig.googleapis.com

I found when i blocked this URL, it didnt trip finding root.

Magisk Delta uses an SU List function whereby instead of hiding apps from root, you only add apps that require root.You could try that and report back.

Im using LineageOS on my Pixel 6.
[Magisk] Homeboy76:
Answered in other thread.
[Magisk] Mepsipax:
Hey guys , I'm using this car control app: https://play.google.com/store/apps/details?id=de.volkswagen.carnet.eu.eremote

I haven't been succesful in hiding root from it. I'm on a pixel 6.

- got magisk 26.1

- systemless host

- zygisk enabled

- use different app name for magisk

- added the app to denylist

- tried with and without force denylist

- installed shamiko

- using displax modded safety net fix to pass integrity (except strong)

- Tried shelter to install the app on a work profile

Any idea what else could work?
[Magisk] pndwal:
Native bridge based Zygisk loading to properly hide Zygisk and module memory... It's a WIP, expected in Magisk 27.0+ but current Alpha fork is a POC and I have the Volkswagen app opening with it:

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

🤠 PW
[Magisk] chiteroman:
Use Magisk Alpha: https://t.me/s/magiskalpha
[Magisk] Mepsipax:
Wow, very cool. Thanks guys, I will give it a try!
[Magisk] zgfg:
Try InitRcHider for initrc, and Shamiko for Zygisk
[Magisk] mahaseno:
to any one like to downgrade to 23 and hide magisk

select custom channel

and paste this link

https://raw.githubusercontent.com/mahmoud32xn/magisk-files/c30d83189a44d6964df83e3cdbf064f3526dcb84/stable.json

and then you will be able to hide old version 23
[Magisk] Szabi01:
My bank app could easily tell my phone was rooted, no matter what I did, didn't work even with Zygisk. If any of you still have a hard time, install "Island", which is a cloning app that can clone apps to Work profile with root access and repackage Magisk Manager, now it's working fine.
[Magisk] pndwal:
Did you have rsmdisk= no previously? ... Did you notice if that changed with OS update (also, w/ stock MIUI or EU custom?), or Magisk 24.x? Ta, PW
[Magisk] JazzieBoi:
Do you know if I should install the alpha Shamiko Magisk & the Shamiko magisk manager as well?
[Magisk] pndwal:
No, just install the delta variant of obfuscated mask to temporarily repress Zygisk beta's suspicious traces while we look for a proper fix... Don't, use the Shamiko manager; invoke the dashboard and set the whitelist switch to really confuse any bank apps detecting shadow mistress Yuko herself. 😜 PW
[Magisk] shadow460:
I have the old version 23 in an archive. My phone, like the Barton 3200+ equipped desktop in the next room, runs a JBOD configuration: eMMC, SD card, SIM card, and, when needed, one of two USB OTG devices.

The old ways are still the best ways. If the OS crashes on the phone, I pop the SD and SIM cards and reload from an archive. Once I put in the SIM card, I can re download any apps that work with my root solution, then create weblinks in place of those that don't. I put in the SD card and there's my data. The USB OTG devices are stuck into either a Yamaha synth or my Ford truck, but they fire right up in the phone.
[Magisk] JazzieBoi:
When you say "delta variant" you mean the actual Shamiko module though correct? Right now I have Shamiko installed and it says it's working. I have version 4.9.1 (95).
[Magisk] pndwal:
Nah, I was just joking too; thought I'd make some stuff up and see who could make sense of it also... see how far we could push it! 😜

Sounded good didn't it?... Bit like your 'alpha Shamiko Magisk' & 'Shamiko magisk manager'! ... Very funny!!! 😂 PW
[Magisk] zgfg:
On my old Davinci (Xiaomi Mi 9T) I still have Ramdisk No - also Magisk Alpha 24101

On Lisa (Xiaomi 11 Lite 5G NE), Ramdisk Yes is from the beginning, but phone is brand new (I got it ten days ago)

Lisa is new model, from September 2021, and it ships originally with A11, A/B

Both run MIUI 12.5, A11 but Davinci was originally shipped in 2019 with MIUI 10, A9, hence without Dynamic partitions and so

That's why boot images are different
[Magisk] porotikos:
hi there guys.

i am intimidated by the new changes. they had to happen, i understand that.

eventually i will try to upgrade my magisk, but i wont try that unless a great noobfriendly guide shows up. yes i know about my noobiness (if that is a word).

My question is this.

right now, in magisk 23 that i am, all seems to work.

if a new update in xiaomi comes and i have to upgrade miui, i will lose root. if i try to flash magisk 23 will it work or once i lose the current root and magisk i have installed, i will be forced to go to version 24?

unless magiskhide stops working in version 23, and bank apps start to recognise it, i think i should stay as i am... even though i would like to evolve. but i am terrified...

(now if someone with a xiaomi (i have mi note 10 pro, (not redmi)) has a nice guide to follow that is tested, please shoot)
[Magisk] meric57:
Hello, would it be possible to put on the first page of the topic the update of certain module with the link. more recent updates

thank you
[Magisk] xabu:
If you want to learn to swim, you'll need water ...

Read the start of this thread again and again, follow its links, and filter out what you need for your specific phone. Don't wait till this thread also has more than hundred pages.

It is very rewarding and you learn a lot about your apps and phone.

Hope you'll have a nice day :) !
[Magisk] Zuikkis:
Well, not if you don't know that requirement. :D

I have Android 12 (LineageOS 19) on Samsung Galaxy S7, with Magisk v23.. All my bank apps work, safetynet passes, play store is certified, google pay NFC works.

I'm interested in Magisk 24 but afraid I might break my current configuration.. :) "If it works, don't fix it"
[Magisk] Spartacus500:
I try module InitRcHider for my Samsung Galaxy S7 edge Custom Pie 9.0 Rom, but not working, init.rc & SELinux polisy is modified 😔
[Magisk] JazzieBoi:
I was just tryna make sense of why in the Telegram channel there are 2 different zips and an APK... You could've just said there's no such thing in the first place instead of typing all that jibberish.
[Magisk] m0han:
clear cache and data of magisk detector app (if using that), open the app once, reboot and check
[Magisk] zgfg:
Sorry, I'm still new with A/B devices:

Is it really true that A/B devices do not have Recovery partition and that custom recovery (TWRP) must be flashed to the boot (being it boot_a or boot_b, depending on which slot is currently active)?

What if I want to have both Magisk and TWRP:

- I flash Magisk patched boot.img to boot (active slot)

- And then I have to flash TWRP to the opposite/inactive slot Boot?

Then, when I want ti boot to TWRP, I have to force booting to the inactive slot, or how?

---

I'm on Xiaomi 11 Lite 5G NE. It is A/B device and I have already successfully installed Magisk by patching and flashing to the active Boot

Now I would like to add TWRP. I tried and I can permanently boot to TWRP - but when I wanted to permanently flash TWRP to recovery, it failed on the remote side, not recognizing target recovery

And indeed, there is no recovery when I look to:

/dev/block/bootdevice/by-name
[Magisk] Spartacus500:
I've done it and it doesn't change anything
[Magisk] hemfreitas11:
Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
[Magisk] J.Michael:
From what I've read in the Magisk threads, Yes, it's an excellent idea.

It's not for everyone. The people who know what they are doing can identify which situations make Alpha or Delta worth trying. The "full control over your phone" is no greater than that possessed by the "regular" Magisk.

As for not bothering to provide English translations, why should she? She has a big enough fan base that I keep seeing references to her releases. Use it or don't. She doesn't charge anything, and you get your money's worth.
[Magisk] shoey63:
See the devs below @topjohnwu down the bottom?

They are the Alpha devs. Also massive contributors to the main Magisk branch.

You can trust their software.
[Magisk] hemfreitas11:
Not trying to start an argument here, just sharing what i think is a pretty genuine concern.

It's not the full control part that i see the problem with, but the person that is being trusted with it.

I see the alpha devs are contributors to the official Magisk, I might be wrong on this, but as far as i can see there is no GitHub for alpha with the changes that they made to the official one, and the only way to install it is to download the pre built apk they provide from their 100% chinese Telegram, so I don't know, kind of rubs me the wrong way.
[Magisk] J.Michael:
That's understandable. And prudent.

As I understand it, Alpha is not meant for widespread use. Its developers are not looking for lots of users. Its a testbed, meant to be used by a few of their friends, and even then only to address specific problems.

The rest of the world should wait for the changes to bubble into the official Magisk release.
[Magisk] Mepsipax:
I had the same thoughts right now. I don't even understand how you verified the bold part to be true. I don't see any way to connect that telegram account to any github accounts.

So I guess, consider me rest of the world, because I'd rather wait considering that my use is non-critical personally. Do we know how long these things usually take to get into magisk beta? I know, no ETAs are prolly given, but is it weeks, months, years usually?