yashsingh1/xdaforums huggingface dataset:
[Magisk] Homeboy76:
@ashish1989, Post # 3,373 was edited.

Displax's v2.4.0-MOD_2.0 was Fixed by Google:

Changelog: v2.4.0-MOD_2.0

Fix KernelSU support. You still need "ZygiskOnKernelSU".

Fix WiFi calling on some devices (and maybe other related issues) by moving changing ro.product.first_api_level from global namespace to GMS only.

Pass MEETS_STRONG_INTEGRITY[. By default you need device that launched with Android 13+ or custom ROM that manipulate with ro.product.first_api_level (>= 33 / or null / or not present).

If you want to play with it more complex - use separate "-STRONG" build. NOTE: Various system issues are possible on "-STRONG" build! (Fixed by Google)

That is why I asked if you had tried Displax's v2.4.0-MOD_1.3....
[Magisk] ashish1989:
No I didn't try it
[Magisk] zgfg:
KSU does not matter to him = @ashis109

WiFi calling fix in nod 2.0 might even be a benefit to him

About Strong Integrity - that does not matter to him, it was just one prop change that was filtered to affect only DroidGuard service (part of SN/Play Integrity)

Btw, this module helps to pass SN/Play Integrity. If he already passes, that's it. One or the other version won't help him for other detections that his banking apps looks for
[Magisk] ashish1989:
What can more be done now? All other banking apps are working fine except phonepe
[Magisk] sawdoctor:
Depends what that banking app is detecting, some detect unlocked bootloader,some detect xposed mods, some detect twrp. Try removing as much as you can and then enable things one by one. Some people have more luck with shamiko, some with different magisk,some with kernelsu. There's lots of things to try but no one fix
[Magisk] ashish1989:
Ruru shows abnormal environment

TWRP, SU file and magisk file are found
[Magisk] pndwal:
Well since I understand the query now,

- alpha apk = build to install

- alpha zip = source code to fulfil GNU General Public License version 3 obligations

https://github.com/topjohnwu/Magisk#license

(you can examine it, but don't try 'running' it!)

- Shamiko zip is Shamko hiding Magisk module (test builds only so far; public release due tomorrow - 2/2 - along with proper public release of Zy(gisk)-LSPosed).

🤪😗😚 PW
[Magisk] dcarvil:
Set "Update Channel" to this Custom Channel to stay on version 23.

https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json
[Magisk] porotikos:
This is greatly appreciated. Cheers
[Magisk] pndwal:
Set custom channel and leave it blank should hide updates w/ any version too! ... More accurate too as you won't see 23.0 as latest...

May need to select 'stable' etc again to hide the Magisk app, but it's supposed to use stub from package now if no network available... PW
[Magisk] xabu:
but only if you refuse to learn something and don't use water to swim ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
[Magisk] _mysiak_:
A little off-topic, but IMHO it's not worth to have TWRP installed, with A/B devices I always followed this approach:

Initial setup:

1. fastboot boot twrp

2. install magisk (this step takes backup of stock boot image required later)

3. reboot and use the phone

When OTA arrived:

1. magisk manager -> restore images

2. apply OTA, do NOT reboot

3. magisk manager -> install to inactive slot

4. reboot and use updated & rooted phone

Anyway, if you insist in having TWRP installed, you need to "hot boot" TWRP (fastboot boot twrp.img) and then install it with installation script. Sometimes it was required to switch active partition and repeat the process - following the guideline for your device would be the best bet how to get it done properly. :)
[Magisk] zgfg:
Thanks

But my question was really about that second part - if I temporarily boot to (one) TWRP (img) and then, from that TWRP flash (another) TWRP zip - to which partition would it permanently install that TWRP.

I'm afraid that it would permanently install TWRP to Boot, thus overwriting my Magisk
[Magisk] _mysiak_:
According to the installation script, TWRP will get installed to both partitions. However keep in mind that TWRP installation script does not replace the whole boot image, but it rather unpacks it, replaces the recovery part only and then repacks it back. Kernel and Magisk should remain intact.

META-INF\com\google\android\update-binary
...
for slot in _a _b; do
if [ "$recoverycpio" ]; then
ui_print "Running image patcher on $name$slot...";
...
[Magisk] Lughnasadh:
I don't have your device but I can give you a thought based on another a/b device (Pixel 2 XL). Beginning with Android 11 it was no longer possible to have both TWRP and Magisk installed simultaneously (because of the combined boot and recovery partitions). This would lead to a bootloop. The only way to use TWRP would be to fastboot boot TWRP, without installing it. I'm not sure if anything has changed with recent TWRP updates since it is no longer my primary device,

Just wanted to give you a heads up that the same behavior could happen on your device.
[Magisk] AyselEP:
How we find repo module now?
[Magisk] xabu:
Page 1 of this thread.
[Magisk] J.Michael:
You do not *have* to upgrade
[Magisk] pndwal:
Type II (Legacy SAR - SAR by Google's definition) A/B devices dont; they have recovery ramdisk in boot partition.

Yours is newer type IV (2SI ramdisk SAR - not really SAR at all by official definition that considers initial rootdir only. - Type IV has rootfs as initial rootdir, but final rootdir is system, so SAR for Magisk purposes) "USES_RECOVERY_AS_BOOT" device. These have a hybrid ramdisk (dual, recovery + boot compatible). Some Two Stage Init A/B do come with recovery_a/_b partitions. These only use the boot ramdisk to boot into Android. Other (most) A/B Type IV ramdisk can boot into either Android or recovery based on info from bootloader.

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

Yes, TWRP is in the hybrid ramdisk in boot... My guess is that the rare (high end) devices w/ recovery_a/_b partitions will necessarily be the exception as these will incorporate useable recovery ramdisks in recovery partition. Logic suggests TWRP in recovery, Magisk in Boot in these cases.

I believe you simply flash twrp to active slot, normally (follow these official instructions for Renoir; nb use files you located for Lisa however 😬), after flashing Magisk patched boot image:

https://twrp.me/xiaomi/xiaomimi11lite5g.html

The zip cannot be a complete boot image replacement as was tradition recovery image as that would require different zips for every different ROM; this will simply be patching the hybrid ramdisk (swapping out stock recovery / leaving the rest, including Magisk root, as is) and repacking AFAICS.

Don't believe you need this...

So this is wrong; we're patching boot with recovery data, not flashing recovery image...

Follow the official twrp.me instructions above, and after temporarily booting the image file (don't flash), use the Preferred Installation Method: Once booted, navigate to the Advanced > Flash Current TWRP option. I'm assuming this method uses existing hybrid ramdisk, but I'm not certain... (There is also an Alternate Installation Method: Once booted, navigate to the Advanced > Install Recovery Ramdisk option; nb. seems installing recovery ramdisk requires additional step to Fix Recovery Bootloop.)

All best, PW
[Magisk] BillGoss:
Not all A/B have recovery-in-boot. Some, like my OnePlus 8T, still have a dedicated recovery partition.
[Magisk] Mickafromparis:
https://www.reddit.com/r/Magisk/comments/sfhrl3
It worked as designed. Pfff. Spent hours having the same problem as you.
[Magisk] gorman42:
Pardon my ignorance but how can I tell if the modules I have installed in Magisk 23.0 are Riru modules?

I have installed:

MagiskHide Props Config 6.1.2-v137

substratum lite Overlay Helper 0.5.20

Systemless Hosts 1.0

I mainly want/need root in order to be able to use properly CF.lumen. Plus I use the overlay helper for substratum to do away with navigation soft buttons, in combination with FNG.

Currently on LineageOS 18.1 (Jan 27th build) on a OnePlus 6T.
[Magisk] zgfg:
Riru modules are usually named with riru, like riru itself, riru-lsposed and so
[Magisk] zgfg:
Yeah, I was aware of the official instructions for Renoir on TWRP.me (for Lisa there is no official TWRP yet)

(Lisa is little bit newer model than Renoir, with minor differences in hardware and a small diff "NE" in the official names - but it would be OT to discuss the diffs, why Xiaomi ships Lisa now instead of Renoir, and how I ended up with Lisa although I originally ordered Renoir)

So I temporarily booted once again to TWRP (fastboot boot) and tried:

1) Advanced / Flash current TWRP:

It failed (screenshot) complaining that recovery ramdisk was modified (supposidely due to my patching the boot.img by Magisk)

2) Advanced / Install recovery ramdisk:

It flashed successfully but noted me (screenshot) that root was now overwritten.

Indeed, when I booted to System, Magisk app was showing no Magisk installed and I had to flash once again my patched boot.img (with Magisk then overwritomg the TWRP)

All together, I cannot have Magisk and TWRP in parallel, permanently, on my A/B, recovery-in-boot Lisa

(only if I would try patching by Magisk the twrp img file and then flashing that to Boot)
[Magisk] pndwal:
Yup yup yup... I'm learning too. 😜

Patching twrp.img may be correct approach, but you can't flash of course; use TWRP advanced (patching) options (not sure if 1 or 2 will work)...

I read somewhere good guide on this, but couldn't find it briefly last night, so I'm relying a bit on my understanding / recollection as I have no experience with A/B whether Legacy SAR or current 2SI... Have a feeling it was in LOS Doc's / wiki (will search again later - sorry, no time now... Thought twrp.me had something, but didn't find...

I'm Sure someone w/ experience setting up TWRP & Magisk on A/B 2SI w/ recovery in boot partition will pitch in!

A couple of thoughts (no experience!):

Seems you now have added a new recovery ramdisk w/ TWRP in boot. Try taking TWRP backup of boot.img, Magisk patch it and temp. load TWRP again and flash patched boot.img. May also work with standard boot to twrp since you're not using advanced options now... Should also work w/.fastboot

Or you could start w/ stock boot image and load twrp in existing hybrid ramdisk (temp. boot twrp, advanced options, method 1, recommended, boot to twrp), then take TWRP backup of boot.img, Magisk patch it and temp. load or boot TWRP or use fastboot and flash patched boot.img... (this may be better if it works).

If you want to pursue Install TWRP after root, your initial error may have something to do with a need to flash vbmeta ... or even need to disable DM verity and encryption...

😜 PW
[Magisk] zgfg:
Zygisk-LSPosed v1.7.0
[Magisk] zgfg:
Remove TWRP folder, or rename to TWRP.bak - it shall be still good for TWRP and at least Ruru will no more complain about

You can hide Magisk app by using HMA module for LSPosed - there is another thread about Hide My Apps, OP post #1 gives a link to GitHub Guide.

Generally, hide Magisk app and all other modules from Ruru and from the banking app(s) by HMA

Put Ruru (and banking apps) to DenyList. Install Shamiko and don't enforce DenyList

That's for the beginning 😁
[Magisk] zgfg:
If you are concerned about Ruru, use HMA and DenyList also for Ruru

You can try your luck with the modules as on screenshots

Some banking apps may look for Developer Options or USB Debugging

Some may block due to Accessibility options - but IMO, it will be a discrimination against users with disabilities in US and EU

For some banking apps you should switch to Riru instead of Zygisk, some will work with the latest Magisk Alpha

Search on XDA and generally, if the other users discussed about your particular app, what it looks for and what/how to hide

It's about different apps, different developers with different skills, different opinions in their IT and Legal departments what kind of safety is required, even different regulations in different countries...
[Magisk] ashish1989:
App data isolation android 11+ not found, I think deleted from github

And my username is ashish1989, you are tagging wrong guy I think
[Magisk] zgfg:
Nope. It's still on GitHub. Just google properly. My screenshot in the post #3383 revealed "packaged by ...' - you had to use that name when googling
[Magisk] pndwal:
I still think Zygisk detection may be you problem as it is with Sparkasse... Don't know how you can know for sure however... Without trying Native Bridge loaded Zygisk for a while... PW
[Magisk] pndwal:
Have you checked for PI deviceIntegrity? PW
[Magisk] ashish1989:
Let me check

No, how to check?
[Magisk] pndwal:
Play Integrity API Checker... Play Store... Or enable developer options in Play Store and check there...

Should have deviceIntegrity + basicIntegrity but not strongIntegrity... PW
[Magisk] Legitsu:
things detecting magisk/lsposed/riru/zygisk are anti-consumer

those things have nothing todo with a bad actor gaining temp root and stealing data

magisk requires unlocking the bootloader always has always will. the user rooting the device has nothing todo with security

its a bs argument
[Magisk] HippoMan:
Agreed.

Furthermore, banks which cripple or block their apps on rooted Android devices don't make the slightest efforts to cripple or block users' software on desktop computers, all of which are rooted.

And these same banks gladly issue us totally unprotected devices for accessing our money. They are called "debit cards", and they are just as easy to steal as mobile phones.

Banks' development of anti-modding/anti-rooting "protections" in their Android apps are therefore totally wasted and meaningless efforts.
[Magisk] Legitsu:
to say nothing that if your security model relies on trusting the endpoint device

YOU ARE DOING IT WRONG
[Magisk] ashish1989:
Done all, still same problem. Now what to do?
[Magisk] zgfg:
Please re-read previous responses

I can no more guide you for that app since I'm not using the app and I have no idea (and frankly not much interest in) what that apps looks for

Previously suggested hints:

- google and search if other users discussed about the same app and its detections and how to solve

- try with disabled USB Debugging or even disabled Developer Options

- try with Riru instead of Zygisk and/or Magisk Delta (with MagiskHide instead of DenyList) or Magisk Alpha forks

By searching you will find posts confirming that the last two hints/methods helped to spoof certain 'banking' apps where the other methods did not work

Good luck
[Magisk] xk3v1lx:
Anyone see my attestation is how?

I don't know about this app, but my device show:
[Magisk] zgfg:
Search for Google Play Integrity Checker, that's the app to test PI API
[Magisk] J.Michael:
Read a few pages of posts, I've seen other people complain about this, @pndwal has explained the problem. I think the gist is, be patient, work is being done, wait for a new version of Magisk.
[Magisk] pndwal:
🤔??

Why spread poisonous opinions based on untruth? (+ flame valued XDA members/Devs?)

@yujincheng08 (LoveSy, lovesykun, Shana) is not a he, and she is NOT the creator of KernelSU; She is the lead Dev for LSPosed and a principal Magisk collaborator...

Also, while Alpha was originally @vvb2060's personal Magisk branch, it now comes from the LSPosed GitHub magisk repo (not public) but notably builds commits from @yujincheng08's LSPosed Metagisk fork (public but no builds publicly available except as Magisk actions CI builds) combined with some @vvb2060 code for revived MagiskHide (when Zygisk is disabled only) etc... Currently Metagisk commits are from the zygisk branch, and native bridge loaded Zygisk is the WIP.

So you are actually using a Magisk fork who's primary differences to TJW builds are essentially @yujincheng08's in Alpha. 😬 And if you use @canyie's Shamiko or LSPosed, you are relying on her code also...

@weishu (tiann, @twsxtd) is the creator of KernelSU as well as VirtualXposed, Taichi, twoyi etc...

Not sure which Dev you were intending to disparage, but @yujincheng08's NB-Zygisk WIP (combined with Shamiko hiding) is your best bet for hiding Zygisk; it already works but still needs fixes for some conflicts and she's been working on it since March already... Nb. Native bridge loading was also the basis for Riru's inbuilt RiruHide...

In any case, if you don't trust @yujincheng08 you'd better not use Magisk in any form...

😬 PW
[Magisk] zgfg:
Trust her, Shana/she
[Magisk] leejohannes:
magisk canary version

use props to make McDonal's work

make tng work by MIUI second space and shamiko

hope not detect by next update...

or just install root sensitive app in second space since that system is not rooted
[Magisk] ashish1989:
Don't know if this is the right thread to ask. I am using oneplus 6 with OOS 11 stock rom with twrp. I have not rooted my phone with magisk but my bootloader is unlocked and the google play store is saying my device is not certified. Is there any solution for this problem?
[Magisk] zgfg:
Stock Recovery and relock Bootloader

or

Magisk and Play Integrity Fix
[Magisk] ashish1989:
My banking apps are working fine now, so I don't think I would need to relock my bootloader. Hope it lasts long like this.
[Magisk] JAIMASS:
Bro I need an help. Can you provide your telegram or any social media which I can contact you . My telegram I'd:- @Roman_467
[Magisk] VD171:
https://xdaforums.com/t/guide-mtk-how-to-bypass-detection-for-unlocked-bootloader.4419159/
[Magisk] pndwal:
Yup... Root and check in Play Integrity API Checker for PI deviceIntegrity... If you don't have deviceIntegrity fix by applying a working PI deviceIntegrity fix solution, generally @Displax's USNF mod fork...

Once passing, clear Google Play Store + Google Play Services + Google Play Protect Service (if exists per device) data...

Alternative to rooting is to find a custom ROM that integrates a PI deviceIntegrity fix, or maybe this @huskydg solution to add (inject) such spoofing to a custom ROM lacking it (old but maybe useful):

https://github.com/HuskyDG/injectprop, or re-lock B/L with stock as mentioned...

Nb. You don't need strongIntegrity passing and won't be able with B/L unlocked...

🤠 PW
[Magisk] borisSweden:
How do I make Telia Play work with root? I have only found one version bthdt work because it's a React Native app. Telia is using Android TV apk as a base to install the mobile app.
[Magisk] pndwal:
Telia Play:

Should I get this far?... PW
[Magisk] tyler19820201:
Latest Barclays also wont work anymore. I was using it for more then a year now with no issue. Only official magisk zygisk lsposed shamiko combo. But now golden days has finished. 😔
[Magisk] pndwal:
Barclays:

Should I get this far?... PW
[Magisk] tyler19820201:
No. U need to go more far. Tap register for the app and then just give the 5 digit passcode (create it so u can give whatever u want) after that will poping up the errorcode. 00006 or T0020 most of the t

ime. Or AND...
[Magisk] pndwal:
mmm

And... what next?... PW
[Magisk] tyler19820201:
I could not go this far....🤨

Is this the latest 2.82 version?
[Magisk] pndwal:
... I'm using Alpha + Shamiko hiding, so probably detecting Zygisk for you... Alpha has WIP native bridge loaded Zygisk, same loading that allowed RiruHide to work... Nb. Shamiko now supports NB-Zygisk.

Nb. Finished NB-Zygisk was slated for official Magisk 27.0, or that was the aim of LSP Devs back in March at least... 🙂 PW
[Magisk] tyler19820201:
Ok. So u use magisk alpha? Or is that a module? If i am correct u have zygisk enabled but what is NB? 😝🤔 i have only 5 modules in magisk. Busybox, SafetynetFix, Systemless Hosts, Lsposed for Zygisk and Shamiko.
[Magisk] J.Michael:
"NB" is alternately "nota bene" and "Native Bridge", you have to figure it out from the context.
[Magisk] sawdoctor:
Here's the link for the magisk alpha thread on xda but you'll need to follow the telegram group for full details

This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060.

Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk... https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/
[Magisk] tyler19820201:
Thanks. If i am correct Alpha is not the same as Canary, right?
[Magisk] borisSweden:
Is it the Swedish version? Because I'm not sure what it's using to check root, bootloader, DRM or source of install like McDonald. When I check the APK most sites show it as Android TV app. I have a older version that is React Native based.
[Magisk] tyler19820201:
Barclays UK
[Magisk] borisSweden:
Nah I'm talking about a IPTV service my ISP is offering.
[Magisk] sawdoctor:
That's correct it's a completely different version and has lots of "fixes" that will eventually make their way to official magisk . I haven't used it myself as I'm still in the fortunate position of all my banking apps still working on official Canary
[Magisk] tyler19820201:
I see. Thanks for the info. I will dig into that Alpha then...🤔
[Magisk] pndwal:
Seems not; it's the only one I see in Play Store here however...Telia Play LT; Telia Lietuva, Lithuania:

👀 PW
[Magisk] pndwal:
... Looks like you get later versions in Sweden... Apparently these; either with:

I get to here:

or with:

I get to here:

... Please say if you have other version... 🙂 PW
[Magisk] m0han:
CMIIW: Official Magisk and Magisk Delta both have 'Canary'. And, Magisk Alpha is a different project.
[Magisk] tyler19820201:
So if i want install Alpha then do i have to remove stable magisk first??
[Magisk] m0han:
Even if it's possible, it is pointless to have more than one iteration of Magisk running on your system. When I switched to Magisk Delta I removed official Magisk.
[Magisk] borisSweden:
Telia Play - Apps on Google Play

TV, movies and series wherever you want

play.google.com

Also I have no Gapps, LOS+MicroG and install through Fakestore/Aurora

Version 6.0.1 works but not that well.
[Magisk] pndwal:
Ok, Telia Sverige AB, 7.10.0... Can you supply APK as I can't download that here...

Also, do you have Play Integrity deviceIntegrity verdict passing (Ie have 'gmscore' etc for MicroG set up properly and working USNF or PIF)? PW
[Magisk] borisSweden:
Well I have Play integrity fix instead of universal safetynet, hiding root with magisk with shamiko. cant you install a APK of the app instead of me sending a apk? If its possible, can you use Aurora store? But MicroG doesnt support Play integrity, only basic Safety Net,
[Magisk] pndwal:
As you know, I've already found Playstore version showing for me and tested, + 2 other versions that seem to be for Swedish users... I won't further search for/guess about your specific version, but will test if you supply...

As far as I know it still does with correct configuration... Have you read that this is broken again?

... You generally need to enable zygisk in Magisk and configure denylist to hide root from 'microG Services Core', also enable 'Device Registration' and 'Google SafetyNet' in microG settings, use a working USNF/PIF solution, etc... PW
[Magisk] borisSweden:
OK, I will double check all settings and redo passing SafetyNet. 7.10.0(30716) just crashes with my current configuration.

Telia Play Sweden (Android TV) 7.10.0 APK Download by Telia Sverige AB - APKMirror

Telia Play Sweden (Android TV) 7.10.0 APK Download by Telia Sverige AB - APKMirror Free and safe Android APK downloads

www.apkmirror.com

I pass Safety Net in microG, YasNac, Native device registered

So I swapped Integrity to SafetyNet for MicroG, added Magisk Hide that kind of works on another app that didnt work before and microG in DenyList.

Telia Play still crashes, but when I use activity launcher I can get to the log in side for username/password and BankID.
[Magisk] n.p.:
I have a device (a generic Android 6 phone) that I can't get to upgrade Magisk (it currently has 25.2), which I have just tried again after updating the app to 26.2. Whether I attempt "Select and Patch a File" or "Direct Install (Recommended)", the installation appears to work, but after a reboot, I still have version 25.2. Any suggestions?
[Magisk] Arcline:
Hey guys,

after updating 26.1 to 26.2, ramdisk says no. Reverting to 26.1 fixes this.

Any ideas?