yashsingh1/xdaforums huggingface dataset:
[Magisk] mGforCe:
Thanks @zgfg for your detailed inputs, quite helpful

I missed writing, but yes had tried Reset Sensitive props too when was using Magisk Delta (+ combination above). I didn't try App Data Isolation (new for me) though.

By the way, even for my other phone (NP1 - Nothing Phone 1 which has close to stock A13) TB Checker detects XprivacyLua

My setup here is Magisk Delta Canary (obviously Renamed) + Magiskhide + Reset Sensitive props + USNF Mod + Zygisk Lsposed + HMA + XprivacyLua

Just to see if I can hide XprivacyLua - should I try App Data Isolation ? What else can I try?

PS: Want to experiment on NP1 phone first before doing same on Redmi 10S MIUI Phone
[Magisk] zgfg:
Don't know what for do you need XPrivacyLua (check what you could do by LSPosed modules instead) - try by completely removing Lua and read about manually deleting leftovers from their FAQ:

XPrivacyLua/FAQ.md at master · M66B/XPrivacyLua

Really simple to use privacy manager for Android 6.0 Marshmallow and later - M66B/XPrivacyLua

github.com

Maybe Lua can be used and properly hid - I don't know and (didn't care about so far)

I don't hide Delta app since it already comes with a different package name - but I do hide it by HMA together with all LSPosed modules - TBChecker, Ruru, Oprek must not find anything from them

I need(ed) both App data isolation and Reset sensitive props because of those detectors - don't recall now, when I obtain a working combination I keep it and just retest things upon eg every Magisk Delta update

Btw, I have MIUI 13 (Xiaomi.eu)

Also, use the latest USNF 2.4 by displax (but if using Xiaomi.eu you may not need it)
[Magisk] pndwal:
Some apps will list errors incl. detections in generated logs... Other types of device logging may give indications of what is detected also, but I have very little experience with examining logs...

Other than this, comparative use of detection apps like Momo, VD Info's, Ruru etc can give many clues re. what detectable traces of modified execution environment your device leaks...

So you shouldn't need custom/modded Magisk forked builds restoring MagiskHide/using other tricks for this...

The key trick is basically to add hidden processes to Microsoft Company Portal (Intune) protection app and also for other Microsoft apps like Teams, Outlook etc if needed... Default denied processes (when app is selected in denylist) are not enough for hiding purposes at least for Intune/Company Portal...

Expand Company Portal (Intune)/other app(s) and click check box at top to select All processes...

You will also need to be passing PI deviceIntegrity verdict, take Hide the Magisk app in Magisk App settings to install hidden/obfuscated Magisk app in stub, and use proper root hiding; Shamiko (uses denylist as hidelist when DenyList is not enforced) is recommended...

Here is a tutorial on XDA that covers the basics. (Nb. Some details about SafetyNet, etc clearly need updating):

https://xdaforums.com/t/tutorial-ro...h-magisk-update-q1-2023.4402273/post-86421033

Most likely XPrivacyLua, especially with certain configurations but even with none... See below...

Banks (& Ruru etc) often detect XPrivacyLua even after uninstalling as it doesn't clean up properly... Remove data/system/xlua directory to prevent this detection... (I didn't see this in their FAQs etc)...

I'm not aware of methods to hide data/system/xlua directory from snooping apps if using XPrivacyLua, and it seems there won't be a fix for this from dev as module is now archived/deprecated...

If anyone knows of ways to hide directories like this w/o renaming or removing them, please say!...

🤠 PW
[Magisk] huskydg:
Who told you that logcat would **spoll** their detection?
[Magisk] pndwal:
🤔... Not what I said... Not what I meant... PW
[Magisk] mGforCe:
Thanks PW for the detailed feedback

Yes - I already expanded the apps and selected All Processes

Play Device Integrity, YASNC etc passes without any issues. It is just Outlook app which is somehow detecting root related app.

I have already seen the tutorial as well as posted there. But don't expect much there as tweaks/tricky methods are not discussed there

Noted. Luckily for me, no issues in removing Lua on that phone.
[Magisk] mGforCe:
I need XprivacyLua to work on few bank apps. Also I use it to deny access to contacts to apps like TrueCaller etc

Noted. Luckily for me, no issues removing Lua. But yes I removed not only Lua but all Xposed modules and Xposed Zygisk too.

My Redmi 10S is not supported bu xiaomi.eu. So stock rom, rooted by me. I do have USNF Mod by Displax
[Magisk] manlikesenku:
@zgfg thanks for your suggestion!

Uninstalled lsposed + hide my applist

Uninstalled magisk inside the app

Installed magisk delta through recovery

Open magisk delta:

- Hide the app

- enable magisk hide and configure lost

- enforced su list

Now metro bank, chase and Google wallet are all working again! If I go into the security app it no longer tells me device is rooted.

Huge thank you to @huskydg
[Magisk] mGforCe:
@zgfg By App Data Isolation you mean Storage Isolation right?

From here

Release Assets · RikkaApps/StorageRedirect-assets

Changelog English 简体中文 繁體中文 App v8.7.4 (arm) v8.7.4 (arm64) v8.7.4 (x86) v8.7.4 (x86_64) Enhancement module Changlog v29.0.1 (Zygisk) (Requires Magisk v24+, Zygisk enabled, app v8.7.0+) v29.0....

github.com
[Magisk] zgfg:
Not that

---

I meant AppDataIsolation, now available from:

GitHub - adrianmmiller/AppDataIsolation: An attempt to block apps from accessing other apps' private data on Android 11+ (API 30+)

An attempt to block apps from accessing other apps' private data on Android 11+ (API 30+) - GitHub - adrianmmiller/AppDataIsolation: An attempt to block apps from accessing other apps' priv...

github.com

Without that module Ruru fails for me as on the screenshot
[Magisk] mGforCe:
Thanks - will try that. I had installed Storage Isolation :(
[Magisk] SotYPL:
Thank you very much for this! Since Feb patch I was not able to make Chase app fully work. No matter what I did it was detecting root when trying to add zelle recipient, access rewards or enable fingerprint login. I was using official Magisk with Shemiko and USNF. Everything else including Wallet, Netflix etc was working fine. I followed your directions and now everything in Chase app is working again.
[Magisk] pndwal:
Chase 4.384 is still passing for me like this:

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

🙂 PW
[Magisk] SotYPL:
App was launching and most of the features worked just fine. I just couldn't add new zelle recipient (but sending to existing worked fine) or enable fingerprint login. With Magisk Delta everything works.
[Magisk] pndwal:
Mine opens with this setup:

Xiaomi RN8T w/ A10 MIUI, Magisk Canary, Magisk App hidden, app in denylist (NOT enforced), Shamiko, and Play Integrity deviceIntegrity passing of course...

I'm wondering, have you also tried LSPosed + HideMyApplist XPosed module hiding all root/mod related apps from app?... In case it could help with biometric login etc... PW
[Magisk] SotYPL:
I'm not sure if you have understood my post correctly. With regular Magisk with USNF and Shamiko Chase app was opening just fine and I could login. I just could not add new zelle recipient or enable fingerprint login. With Magisk Delta I can do everything just fine. And I didn't even hide Magisk app for this. I just installed it, enabled MagiskHide and configured the list. No need for Shamiko. I just have USNF installed to pass all checks. Nothing else is needed.
[Magisk] pndwal:
Well I did understand that. 🙂 ... just wondered if HMA might be an alternative way if not already tried... But something in Delta setup / hiding methods/ Zygisk loading may well be needed in this case...

Might be useful to others to know if HMA was tried however... I can't test properly configured Chase app ... 😜 PW
[Magisk] zgfg:
@paradoxxman - use Fox MMM and search for Isolation, you'll find one (screenshot) thanks to @huskydg:

GitHub - Magisk-Modules-Alt-Repo/data_isolation_support: Enable /data/data isolation for old Android version (Android 10 and lower). Require Magisk Process Monitor 1.1+

Enable /data/data isolation for old Android version (Android 10 and lower). Require Magisk Process Monitor 1.1+ - Magisk-Modules-Alt-Repo/data_isolation_support

github.com
[Magisk] zgfg:
With the newer update (MagiskHide module v1 3) it's much better, however Chrome still lags a lot - somebody who's not dependent on Chrome could test, too

It's easy - disable Shamiko (Zygisk and Zygisk modules can be enabled), install MagiskHide module and reboot.

Give it some time to 'stabilize' upon reboot

To switch back, disable MagiskHide module and enable Shamiko if you used it

PS: Not sure, maybe Shamiko can be used together with MagiskHide module but with the given combination I had no problems for TBChecker, Ruru, Oprek, SCheck (also, on Magisk Delta, where the code for this module was extracted from, it was not advised to use Shamiko and is not needed)
[Magisk] paradoxxman:
thank you, much appreciated!
[Magisk] kkyoiori2001:
Be care,

I flash this model, with 1.1 version

Reboot then got data all loss....
[Magisk] korbielow1:
Hi I want to root my Poco X3 Pro and install MIUI CSX but I'm afraid I will face issues with:

-NFC

-work profile

-bank apps, other apps like Mcdonalds.

Can somebody explain me if this can be avoided please ?
[Magisk] Te3k:
I can't seem to get anywhere with Magisk on my Samsung Note 3 N900W8 (hltecan).

I install a custom ROM and the latest Magisk apk. From the ROM zip, I extract boot.img and use the Magisk app to patch it. Now I have the patched img. I can't for the life of me figure out a way to flash this.

I have ADB platform tools installed, and can get "adb devices" to show the device while it's booted into the OS. But, when I reboot to download, "fastboot devices" shows no listed devices. As a result, I can't flash the patched img to boot.

I've tried reinstalling the latest Samsung drivers over and over.

I can flash files using Odin while the device is in download mode, but haven't been able to get the magisk patched img file to flash successfully (after converting to tar).

Yes, OEM unlock is enabled and the bootloader is unlocked.

The only way I've been able to root in the past is by flashing .zip root scripts from TWRP, but these no longer seem to work.

How the heck are you supposed to flash the patched magisk .img file if fastboot can't find your device when it's in download mode? Is there a way to convert the patched boot image into a flashable zip that can be installed from recovery?

Thanks for any clues.
[Magisk] zulu88:
@Te3k Have you tried renaming magisk.apk to magisk.zip and flashing via TWRP?
[Magisk] Te3k:
...

I had no idea that rooted the phone. I thought it merely installed the .apk, and you still had to go through the patched .img process and figure out how to apply it. The final step at the very bottom of the instruction page reads:

"Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK."

That led me to believe, flashing the zip merely installed the apk/Magisk Manager and that's it.

Seems like flashing the zip actually roots the phone. That was super easy. This will be the go-to method, not the whole messing about with extracting a boot image from a custom ROM zip, copying it to the phone, patching it with the Magisk manager, pulling it from the phone, installing ADB, getting fussy USB drivers to work, getting into fast-boot, and pushing the patched .img back over USB. What a waste of a day!

Thanks, man. I knew it was something simple. I'm ready to carry on now.
[Magisk] pndwal:
Is OS still stock 5.0 Lollipop?

It's the traditional method and still works fine for old devices, those still on Android 8 or earlier...

It is deprecated (but still receives limited support) since TWRP introduces many issues due to Dees Troy and team being busy / lagging when keeping up with the countless Google architectural changes, mainly connected with SAR and 2SI system boot changes in modern devices... Nb. Magisk issues are often solved even before public Android updates become available so it's little wonder John wanted to remove dependence on 3rd party custom recovery solutions...

Many devices had no TWRP fo a year or so!... Also, some devices need fastboot flashing, eg legacy SAR A-only devices which don't have bootloader support for ramdisk in boot; we must patch recovery image manually since Magisk zip installer isn't designed to do that...

BTW, do you run stock ROM? Does it supply an AP binary image?... You should probably have been patching that, and flashing it along with other binaries supplied in Odin, but use HOME_CSC to avoid data wipe...

🤠 PW
[Magisk] Te3k:
I'm on a custom AOSP ROM. I'm trying not to be on stock firmware, as TouchWiz is pretty much the worst thing to run (lol). I did consider going down the path of patching the stock AP and using Odin and staying stock, but decided I'd rather be on an AOSP ROM without root than on stock TouchWiz with root.

What you say makes a lot of sense. It would be good to not have to rely on a third-party-dependent method if there's a way to have universal Magisk, so I get that. But, that convoluted method makes it tough in situations like mine where fast-boot just didn't seem to work. This is a big problem with Samsung devices, which I think is why there's a dedicated factory tool (Odin) for handling anything to do with download mode. But, Odin didn't allow flashing of a Magisk-patched boot.img. I wonder if there's a way around this, for those who can't get fast-boot to work or fall back on a custom recovery.

It's also the case a lot of stock recovery menus allow installing flashable zips, so maybe that's a way to work around TWRP issues in certain cases.

Searching around for how to get "fastboot devices" to post an attached unit led to a wide variety of problems, and infinite dead-ends all over the net. It's probably beyond the purview of the Magisk team to address what to do in case fastboot fails, since every device and situation is unique, but it's good food for thought in the pursuit of universality.
[Magisk] J.Michael:
You've solved your problem, so none of this matters, but:

Samsung does not support fastboot. Odin was not written to fill the void, Odin was somehow filched from Samsung as the way to flash images on a Samsung device.

How did you install your custom ROM? Whatever the mechanism, *that* would be your path to installing a magisk-patched-boot.img.
[Magisk] Te3k:
Well to install a custom ROM, it was Odin to the rescue. I used Odin to flash TWRP, and from there simply flashed a ROM zip from recovery. Ultimately, that was indeed how I got root again too (rename magisk.apk to magisk.zip, flash that from recovery, and let it do its thing to acquire, patch, and repack boot.img from within recovery). That's a great feature, and super elegant in application too. Props to the devs.

I love that Odin was exfiltrated from Samsung HQ. It shouldn't have had to be. It's a definitive win.
[Magisk] pndwal:
I'm not a Sammy user, but doing a bit more digging just for fun, it seems Magisk actually has everything in place but Sammy users seem to be expected to know some stuff that's simply not detailed in current Installation Instructions to allow them to use standard in-app patching and flash w/o using .zip installer...

Flashing magiskpatched-boot.img

With TWRP installed, you can flash ROMs and 'addons' as .zip or .img.

This means you should be able to extract the boot.img from your custom ROM, patch it as you did, then flash magiskpatched-boot.img to /boot using twrp... You've simply swapped fastboot for custom recovery to flash a standard partition .img file...

Flashing magiskpatched-boot.img.tar

Basically, Odin uses a fastboot or download mode that can't flash standard images... Everything it seems must simply be in a tarball... This means you probably originally flashed something like twrp-3.7.0_9-0-hlte.img.tar for TWRP, not twrp-3.7.0_9-0-hlte.img...

Flashing magiskpatched-boot.img is similar... You'll need magiskpatched-boot.img.tar...

3 approaches:

1) I'm not sure if you can extract boot image from your ROM as a .tar file, but Magisk App will accept and patch either .tar or .img, so seems you could use an extracted boot.img.tar, Magisk patch it then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...

2) If only boot.img is available you can simply open a Command Prompt/PowerShell window in the PC folder where the file was extracted and TAR the file by running

tar -cvf boot.img.tar boot.img

then using the resulting boot.img.tar, Magisk patch it then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...

3) Further, you could take the boot.img and Magisk patch it then transfer file to PC and open a Command Prompt/PowerShell window in the folder with the magiskpatched-boot.img file and TAR it by running

tar -cvf magiskpatched-boot.img.tar magiskpatched-boot.img

then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...

Nb. Simply renaming a .img file to .tar won't work...

Nb. 2 if you are running A10+ your legacy ramdisk boot type device has been converted to 2SI boot type which is a form of SAR for Magisk purposes... This means that despite official Installation instructions saying "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section", some of the caveats in the Samsung (System-as-root) section may now apply... Apart from knowing you are now using what John defines as SAR device (Google doesn't), it's hard to know which apply... 😬

Hope this helps... somehow sometime. 😜 PW
[Magisk] J.Michael:
@pndwal Point of order: If you have a magisk-patched-boot.img and you are going to make a tar, you meed to rename (or copy) magisk-patched-boot.img to "boot.img" and put *that* into a tar -- it's important for the names in the tar to match the partition names.

And John Wu warned against having less than boot, recovery, and vbmeta in the AP.tar; and against not filling all four slots in Odin -- many people's success stories to the contrary not withstanding.
[Magisk] ipdev:
Giving away secrets again. 🙃

Cheers. :cowboy:
[Magisk] m0han:
I'm sure you didn't mean/imply 'opening a Pandora's box' ;) :D
[Magisk] locolyric:
hi all, any idea to enable core only for magisk delta in twrp terminal?
[Magisk] huskydg:
Rename to disabler.zip and flash
[Magisk] chrbur:
Hello, new problem with We Connect V5.15.0. Pixel 7 Pro, Safetynet passed (checked by 2 apps Rootbeer and Safetynet) but We Connect detects Root. I re-installed Version 5.13.3 and WE Connect works fine. So I hope Somebody has a new solution for that. I installed the following Magisk Modules: MagiskHide Props Config 6.1.2v137 + Sahamiko 0.6 (126) + SafetyNet Fix 2.4.0 MOD 1.2. Instead of We Connect everything works fine 😁😁
[Magisk] zgfg:
First, try without MHPC, but keep the latest USNF
[Magisk] chrbur:
I tried that (Thx) but still the same Problem.
[Magisk] pndwal:
Do you have Magisk hidden/obfuscated in stub? (And of course, app in denylist)...

Have you checked new Play Integrity deviceIntegrity verdict passes since S/N is deprecated?

If still failing, try with LSPosed / HMA module configured to hide all root-related apps from your app incl. already hidden Magisk App... PW
[Magisk] elimiriel:
I think the app detects traces of zygisk has appeared.

Karrot: Buy & sell locally - Apps on Google Play

Sell unwanted items and buy preloved stuff in your local community.

play.google.com

The app denies to run in zygisk hiding environment after first running, but it is reported that deactivating zygisk and replacing it with riru and magiskhide module in the HMM can run that.
[Magisk] pndwal:
@chrbur, @elimiriel

For those using Canary builds

Please be aware that in 25207+ major refactoring (of selinux rule patching) has broken many modules etc... This is likely the cause of issues with hiding using recent builds as Shamiko is affected... Please see discussion in Magisk Discussion thread...

You could revert to 25206 or wait for fixes hopefully in 25211... 👀 PW
[Magisk] chrbur:
Hi. I don't think that this is the problem because first I reinstalled an older version of WeConnect and everything works fine, second I FIRST installed WeConnect with 25206 and WeConnect detected root. All the other apps work fine at the time - no Root detected.
[Magisk] Randomginger:
This maybe of interest or not - but thought I would post anyway!

Following a complete reflash of the OS etc. the Costa Coffee App and Vodafone app kept throwing up errors at the log in screen. If I add them them to the Deny list , clear data for those apps, they work. I can then remove the apps from the deny list and they still work. Unless I log out, then i have to repeat the process to log back into them.

These apps must use some sort of securtiy check whilst logging in that they didn't in the past.

Pixel 4XL, Lineage Recovery, Lineage 20 latest, NIKGapps Core, AA Addon, Magisk Canary installed in Recovery, Shamiko 0.6 (126), USNF V2.4.0 Mod_1.2 Displax. Pass all Safetynet blah.
[Magisk] brackenhill_mob:
Why a coffee shop app cares about root ...
[Magisk] HippoMan:
I predict that more and more apps are going to go down this "cares about root" road, and that over time, rooting is going to get to be more and more of a liability.

Thank you, Google, for making this "desirable" (ha ha) outcome possible.
[Magisk] zgfg:
Probably a loyalty/reward card. They are concerned about every cent a rooted hacker may 'steal'
[Magisk] ipdev:
Hi all. 😊

To put this in to the light (full sunshine).

Companies and their app(s) do not care if you or you device is at risk.

It is no concern to them if harm falls on you.

What concerns them is liable.

The companies that are more secure in how they handle sensitive data, do not care if you are using a 'rooted' device.

or

- They have a legal team that can overpower the litigation.

- They have the finances to payout a settlement.​

Has anyone seen a post about Amazon not working on a rooted/insecure device? :unsure:

Cheers. :cowboy:
[Magisk] martyfender:
I have a strange issue that I can't seem to solve. I always use the cutting edge test builds of lsposed. No matter what I do I can't get the parasitic manager short cut to show up. I first tried uninstalling the module and rebooting. then I reinstalled lsposed and It still doesn't show up. I then went into data/adb and deleted both the lspd folder and the /modules/zygisk_lsposed folder then rebooted. I once again reinstalled lsposed. I had the same result. I can launch the app through the notification it presents. If I then go into settings, the "create shortcut" is greyed out.

Does anyone know how to fix this?
[Magisk] Stillhard:
Try to clear your launcher's data
[Magisk] martyfender:
Thank You

That simple solution solved the problem. I went in the lsposed settings and "create shortcut" was not greyed out.
[Magisk] chrbur:
Has somebody a solution regarding root detecting @We Connect? I still have a root detecting issue within the latest version of We Connect. But the penultimate version still works :-)
[Magisk] roslanhashim:
i feel you bro. had the same issues. not only TnG eWallet not responding, CIMB OCTO detect rooted device. just found 2 solution:–

1: revert back to Magisk 23 (the last version with MagiskHide)

2: install Magisk Delta. i am using this and its work flawlessly.

hope its work for you too.

~kitajagakita~
[Magisk] prokiller1199:
Thanks bro for providing your solution now. Already solved it quite long ago using 2nd solution. Kudos the help!
[Magisk] john9965:
You should uninstall xposed framework and your phone will boot 👍