yashsingh1/xdaforums huggingface dataset:
[Magisk] zentis:
Ha! actually when reading earlier in this thread after my comment, I saw your post about that, got vanced and detached youtube from the playstore :) Thanks!

So actually my two main reasons for rooting my phone are:

- privacy. I'm very sensitive in reducing the amount of telemetry that gets sent to companies

- backups

For privacy, the first thing I installed is xprivacylua so I do need LSPosed anyway and at that point, HMA is the best way to hide this (better than using multi user)

For backups, I use titanium backup pro and I know that some bank apps detect that to find rooted phones so HMA is also good for this.

Now, the only thing I wish is if there was a way to patch the knox fuse blown detection (like smali patcher did from what I read) so that I could use managed user profiles to completely isolate certain apps and secure folders. I understand why Samsung would want to have a fuse blown so that they can guarantee in a corporate environment that rooted phones are identified as such but it's really inconvenient.
[Magisk] osm0sis:
Old device (A-only) addon.d is fixed in 24305. It was broken by a busybox regression from compiling it against newest NDK. (My busybox module builds are immune to that since I use old NDK for compatibility and follow an "if it ain't broke..." stance. 😉)

`readlink -f` from busybox is broken for kernel version < 3.6 · Issue #5530 · topjohnwu/Magisk

Device: Nexus 7 (2013) WiFi (flo) Android version: Android 11 (lineage 18.1 - lineage-18.1-20220228-nightly-flox-signed) Magisk version name: 7cfce9f Magisk version code: 24201 I patched the boot.i...

github.com
[Magisk] Root 6.0.1:
I have rooted with magisk but I still have no idea what zygisk does.
[Magisk] ithehappy:
The discussion taking place here is way over my head. I have a taimen, running on LOS 18.1, rooted with latest magisk 24300 and Zygisk enabled. An Indian banking app, namely iMobile and its latest release i.e .14.6 doesn't work despite adding it under deny list. I pass safety net if that matters.

So may I ask what's the easiest way to get around this? Should I simply go back to magisk 23?
[Magisk] pndwal:
Search here, also General Magisk Discussion thread, read State of Magisk 2021 blog from John (see OP)... If still Clear as mud, search for GitHub Riru (depreciated); it does that, only w/ better integration... 😜 PW
[Magisk] pndwal:
Guessing you have USNF then?... The new riru-Momohider is zy-Shamiko; Try that... Plenty more tips here & in General thread if that doesn't help... PW
[Magisk] Lughnasadh:
"Zygisk is Magisk in Zygote. This will run parts of Magisk in the zygote process to make Magisk modules even more powerful. This is also a very important part of the philosophy of Magisk “getting out of the way”. When a process is on the aforementioned denylist, Magisk will cleanup the memory space of the process to ensure no modding is applied (P.S.1). Zygisk is still WIP, and more details will come once the implementation is ready for beta testing."--John Wu

"Zygote is a special Android OS process that enables shared code across Dalvik/Art VM in contrast with Java VM where each instance has its own copy of core library class files and heap objects. Efficient and fast app launch is achieved due to the fact that Zygote starts by preloading all classes and resources which an app may potentially need at runtime into the system’s memory. It then listens for connections on its socket for requests to start new apps. When it gets a request to start an app, it forks itself and launches the new app. It serves as a parent to all Android apps. This forking feature comes from Linux kernel implementation of copy-on-write resource management technique. Forking involves creating a new process that is an exact copy of the parent process. It doesn’t actually copy anything, instead it maps pages of the new process over to those of the parent process and makes copies only when the new process writes to a page. All processes started from Zygote use it's own copy and only one copy of the system classes and the resources that are already loaded in system memory. Zygote is designed not only to respond to fork requests by new apps, but there is one process that the Zygote actually starts explicitly and that is the System Server process."-- Miso Ivanisevic
[Magisk] Mord0rr:
Few days ago i have to format my OP6.

Now, try install Magisk, and cant pass CCT test....and doesnt even show the test....

Phone OP6, with Pie 9.0.9 last rom official, unlocked and with TWRP.

Already try different versions of Magisk, since 16, until last one....nothing.

Sorry im not power user....so a simple way fix this is welcome. Is necessary nuke phone rom, i can do it...
[Magisk] ipdev:
Everything SafetyNet is removed.

This includes the SafetyNet check that was incorporated into the Magisk app.​

To test SafetyNet, use the YASNAC app.

YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​

Download links can be found in Post #4.

OnePlus 6 ?

Android 11 is the current OOS version for the 6 series.

Stock OOS can be downloaded directly from OnePlus.

Software Updates - [oneplus.com] - [WebSite] - Link

To pass CTS, see Post #5.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:

PS.

My OnePlus 6T, OOS v11.1.2.2 is passing just using the USNF module.
[Magisk] Mord0rr:
Hi.

Sorry the confusion. I prefer Pie over 10 or 11. Than add xXx rom = Perfection

Already using YASNAC app, fails.

Already FULL Nuke rom, gonna install TWRP and then maybe Magisk 20.....

Thanks!

Edit*

Solved: Nuke rom, install v20.0, update to 22, and now pass test...

Something from old Vancer version leflovers, problably were making conflits.....nothing like a Nuke.

Thanks!!
[Magisk] pndwal:
@Prof_Shekhar

Further re. addon.d script, please see:

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

👀 PW
[Magisk] shadowstep:
The old version is working fine, the newer version is the one with issues. I've reverted to the old version till I find a working way to hide whatever the latest version of the app is detecting.

App detects root even after all of the following for me:

- SafetyNet passing (using USNF)

- No TWRP folder present in internal storage

- App added in Magisk's DenyList (DenyList not enforced) with Shamiko installed

- All root apps (Magisk, LSPosed, LSPosed modules, etc.) hidden using HMA

- Hide methods API requests, Intent queries and ID detections enabled in HMA

- If I enable any of the other two hide methods, i.e. File detections or Maps scan, the app straight up refuses to open and crashes
[Magisk] pndwal:
Tried uninstalling Magisk App to diagnose / be sure if it's app or other traces?... PW
[Magisk] shadowstep:
Yep, uninstalled both Magisk & LSPosed apps, rebooted, cleared the data of the banking app, it still detects root, unfortunately...

EDIT: My bad, it's working now. Issue was the app somehow got removed from the DenyList. No idea how did that happen, but cheers! 😬 Still needs HMA though.
[Magisk] ithehappy:
OK. Glad to know that it's working for you. I am bit confused, could you please clarify which magisk modules are exactly needed to make it work? I have Zygisk enabled, the app put under deny list and I have USNF by Kdragon installed. So I just need to install this HMA thing now?

Regarding older versions, yes I did try that method. I kept a backup of 14.1 version but upon installing that as it goes through the verification process it throws a pop up saying I must update to latest to continue transactions. So your older version which still doesn't detect root must be higher than 14.1, I suppose.

What a mess man, I am now thinking about ridding of all these root stuff and stay on outdated stock ROM. Really no time to fiddle with these.
[Magisk] pndwal:
He has Shamiko module (denylist disabled) too. (Also, TWRP folder removed / renamed.) 😜 PW
[Magisk] shadowstep:
I made a full backup (including data) so it was working fine for me even after restore. ;) Nonetheless, try the following and it should work:

Clear iMobile's app data

Add app to Magisk's DenyList (make sure the Enfore DenyList toggle is off in Magisk's settings)

Download and install the latest version of Shamiko via Magisk

Download and install the latest version of LSPosed module via Magisk (also install the LSPosed app from the Play Store)

Reboot and open the LSPosed app to make sure it is working correctly

Download and install the latest version of Hide My Applist (HMA) app

Enable HMA in LSPosed

Reboot and open the HMA app to make sure it is working correctly

Follow the following steps to configure hiding in the HMA app:

Select Effective Apps -> Tap on com.csam.icici.bank.imobile -> Toggle Enable hide

Under the Preference head, tap on Select hide methods -> Check API requests, Intent queries, ID detections -> Tap OK

Under the Template config head, tap on 0 additional apps invisible -> Check Magisk, LSPosed and HMA

Tap on the save button on the top right corner of the app

Reboot and open iMobile, it shouldn't complain of root anymore!
[Magisk] m0han:
Updates available: Fox's MMM v0.4.2 (37), YASNAC v1.1.5-release
[Magisk] jesrani:
Thank you so much and thanks to @asripath for pointing me to this thread. I had this same problem with imobile app and I have followed your steps and it is working now. I don't really understand the technical part but happy to get it working. I assume a similar process needs to be followed for any other apps detecting root inspite of being in the Zygic DenyList.

I had enabled the DenyList toggle after selecting the app in Configure, is this correct?

Shoud I use this procedure for all apps which I want to hide from root or only those which are detecting inspite of DenyList?
[Magisk] Prof_Shekhar:
@pndwal @zgfg @J.Michael @ipdev

Happy to inform all that I finally updated my Lineage OS 19.1 with an OTA update.

I was little worried that I may lose the Magisk root or my update may not be applied automatically as I am using TWRP recovery.

But my all worst fears were put to rest as the OTA update installation went like a fine tuned machine. The Lineage OS update automatically booted into TWRP recovery, applied the update patch, reinstalled the Magisk root and rebooted the device.

Checked the Magisk root and LSPosed. All settings were perfectly in place. Nothing amiss.

Would recommend anyone who has TWRP recovery with Magisk to apply the Lineage OS update without even thinking twice.

My experience was much better than the samsung ota update process.
[Magisk] jesrani:
This method worked for the imobile app but later I installed the BHIMUpi app and followed same process but the app still detects root. Is there any workaround for this app?
[Magisk] shadowstep:
Depends on the app. Some apps are happy with being in Magisk's DenyList with Shamiko installed. Some need more heavy duty measures.

Do you mean the Enforce DenyList toggle? If yes, then it must be off for Shamiko to do its magic. So if you've turned it on, it's not correct.

Like I said, you can try. Different apps look for different things, it's a trial-and-error approach.

Maybe that app is looking for something else. Even stuff like custom recovery folder (TWRP, etc.) in internal storage can trigger the root check in an app.
[Magisk] jesrani:
So I need to add apps to the DenyList but keep the toggle off, is that correct?

For BHIM UPI app is there anything I can try to get it working?
[Magisk] dr.ketan:
BHIM upi India? If yes,

Most of Indian app simply works by hiding (renaming) magisk app from magisk app settings

Most of works with this trick even without adding to deny list, though you can add it to deny, it won't harm
[Magisk] m0han:
and, if that app has (bits of) code like oprek detector has, it could flag 'custom recovery files', even if there is no twrp folder on the device. that could queer the pitch further.
[Magisk] jesrani:
Hello Dr.Ketan, thanks for replying I think I used your ROM's / MOD's for my first android i9003 :)

Yes, I meant Bhim UPI India. It didn't work with Magisk Hide and doesn't work with above method also with Zygisk/LSposed/HMA. It activates upto PIN but then says device is rooted and exits. Can you suggest any other method. Even imobile ICICI app had stopped working with just being in denylist but now works with LSPosed/HMA.
[Magisk] dr.ketan:
Tried renaming magisk app?
[Magisk] Prof_Shekhar:
@dr.ketan

I beg to differ on this.

I have been using all the tricks available under the sun except islanding to make my SBI Card app to work after its latest update. The success is still eluding me.

Majority of the other Indian and international apps can be hoodwinked to get them working but this above mentioned app is proving a tough nut to crack.

But I am sure, one day someone in this forum will get this cookie to crumble. It's only a matter of time.
[Magisk] jesrani:
There is no custom recovery on my OnePlus7T HD1901

yes, it's renamed since installation otherwise many apps don't work. Am using lot of banking apps and all are working except BHIM. It gave problem in previous Magisk version also and even in new 24.x version with LSPosed/HMA it's detecting root :(
[Magisk] jesrani:
Are you able to get BHIM UPI working? Please let me know the process if you are able to.
[Magisk] dr.ketan:
Just tested and working fine. Installed BHIM

Add to deny list and renamed magisk app that's it
[Magisk] jesrani:
Please see attached screenshots. I have done all this but as soon as I enter the passcode or detects root.
[Magisk] dr.ketan:
Why you have desabled enforce denylist? are you using shamiko? In that case I don't use it. Also make sure you have SafetyNet passing

I didn't do anything other than said above
[Magisk] Prof_Shekhar:
@jesrani

Yes. As I said I am to run almost all apps without any issues except those detecting Custom ROM.

You may see the screenshot of the BHIM app attached herewith for your perusal.
[Magisk] jesrani:
BHIM works upto this level for me too and also goes through with Mobile activation and setting of PIN. However once I try to log in with PIN I get the message that device is rooted. Have you tried it?
[Magisk] jesrani:
Yes, I have installed Shamiko and that is why denylist is disabled. Earlier, even without Shamiko and with denylist enabled it was not working. Have you tried loggin in with PIN? I am able to activate and put the PIN but it fails when logging in. Used to work some years back and then stopped.
[Magisk] dr.ketan:
Yes, I was able to complete registration and added acc successfully
[Magisk] Prof_Shekhar:
As I no longer use BHIM now a days, I have uninstalled it.

As I am not staying in India, I am not able to test the OTP. Sorry mate.
[Magisk] jesrani:
Are you also on OnePlus 7T? Any idea why it won't work for me?
[Magisk] dr.ketan:
No, I have tested on Note20 ultra
[Magisk] pndwal:
FWIW, BHIM app:

gets past initial detection (immediately detects root if not in denylist) for me on Redmi Note 8T. (Shamiko installed)...

However many bypasses succeed only on a per device basis.

For example, I got German Sparkasse PushTAN app working after many failed for months using HMA method:

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-964222271

After an update, I can no longer pass w/ S-PushTAN, but others (OnePlus users etc) still can!

Nb. My Momo results shown in above issue thread have improved, but still not enough for S-PushTAN. Now:

Some users of OnePlus and RealMe are able to get completely happy Momo; this seems to elude MIUI users, and likely the device/ROM differences this highlights also account for the per-device mileage variation. 😬

If anyone can get S-PushTAN to bypass detection on a MIUI device, just for kicks 😁, I'd be all ears! 🙉 PW
[Magisk] jesrani:
Thanks. I tried everything once again but still getting same error. Am at complete loss. Maybe something to do with the device.
[Magisk] jesrani:
I tried the options you gave but not working. In Momo app I am also getting "Partition mounted abnormally" and "ART parameters abnormal"
[Magisk] J.Michael:
How many years back did it stop working?

Have you tried uninstalling bank app, then reinstalling, to try to ensure it has no memory of previous failures?

Have you tried to log in with a browser, to make sure the bank account is set up correctly?
[Magisk] jesrani:
It stopped working more than a year back. I had uninstalled it and now tried it again but still getting same error. It's a banking transaction app but there is no website, it's a purely mobile app
[Magisk] ChicoDeGoma:
I've read the changelog after not updating for a while and learnt that the centralized repo function was removed.

I've seen the Fox manager an stuff but I was wondering, is there an "agreed" repo or something alike? Because I'm feeling that if I wanted to update my existing modules (I have one or two tops) I would have to search for the author and chase the module and etc etc.

Is Fox's manager the only thing closest enough to what centralized-repot was?

What if I still lack modules after installing Fox's app too?
[Magisk] zgfg:
There is no "agreed" repo bcs TJW clearly announced that he doesn't want to maintain the repo or anything about - he provides Magisk with the mechanism for the modules, but how developers develop and distribute the modules is no more his business

As you can see, Fox lists the modules from three repositories. For the modules whose devs did not submit to any of them, Fox does not search around through the private GitHub projects

Btw, modules can use json update mechanism - that way any installed module, even if not installed through a public repository, can note you about the update: you can read it's changelog and you can easily download or update that module - all through the Magisk app, Modules tab

Of course - developer of the given module must implement the json update notification mechanism
[Magisk] m0han:
i once had to take up issue with him for removing one of my links

Spoiler content hidden.
[Magisk] heinhuiz:
Seems like I'm in exactly the same boat with you. I'm not skilled enough to work out a solution for myself, but hopefully one day someone else will do that.

In my opinion, all these root checking methods should be forbidden by law. It's just spying behaviour without any obvious reason. Even if it's for fraud prevention. It should be illegal to deny someone a service just because that one has tools that *could be* used for illegal activities. Although it's technically much easier to prevent fraud than to actually detect it, these methods breach people's privacy rights.
[Magisk] heinhuiz:
Haha, those needles could be easily found if the search function actually worked 😂
[Magisk] Robbo.5000:
So had my banking app suddenly detect root a couple of weeks back after years of MagiskHide working fine.

Decided whilst trying to fix it that I may as well move to Magisk 24 and try and fix it at the same time.

Anyway, done everything necessary and got SafetyNet to pass.

However after hiding Magisk Manager and adding the banking app to the deny list, the app still detects root. So installed the Shamiko module and disabled the deny list, but still had no joy.

So searching around for more info on the Hide My Applist module I found this thread and specific post.

https://xdaforums.com/t/how-to-bypass-lloyds-and-santander-root-detection.3837206/post-85988021

Gave it a try and it worked for me. Froze Magisk Manager, cleared data in the banking app and relaunched it and hey presto. No longer getting redirected to a root detected page, but the app fully launched successfully.

For those still having problems, give this a try.

For those that might be interested, the root detected landing page URL was a sub domain of the banks main site named app-shield, so I guess the bank app is using these guys for security

Mobile App Shielding | #1 Mobile App Security | VERIMATRIX

XTD Protect provides mobile app security and monitoring for Android and iOS apps. App shielding, anti-tamper, code obfuscation, and environmental checks.

www.verimatrix.com
[Magisk] pndwal:
In reality, hardware backed attestation to TEE is becoming the norm for allowing developers of apps requiring a high degree of security to have assurance that their code is, in fact, running in a Trusted Execution Environment. Even SOCs / processors for pC etc now have the hardware required, and it seems that soon even your PC will rely on these attestations rather than traditional malware detection etc...

Examples of such code include Google's own Google Pay.

The issue is quite simple; bank app devs / corporations who could be sued / banks who now are faced with replacing more and more of your funds obtained by fraud to maintain good faith with customers (eg GPay partner banks when a customer's phone is lost or stolen and thieves are able to unlock the phone & use your GPay because you loaded TWRP, decrypted, left USB debugging on etc etc) want to know the platform is secured (read 'is a TEE') as thieves basically cannot get you data / money in that case, but it is often a trivial matter otherwise.

However, since Google have been taking their time to implement HKA properly, the banks are simply covering themselves by investing in their own methods of detection; they already view IOS as the preferred mobile OS for security as it is basically impenetrable while Google has NOT delivered... 😬 Google can't afford to let that continue either!

While we can, Google is allowing us to 'subvert their security model' quite knowingly, but only because they view the Magisk / modding / custom development community as largely 'White Hat' rather than nefarious as they've said... But there are nefarious hackers etc out there, increasing in number by the minute...

So you are thinking only in terms of your privacy... What about your right to know stuff? What about the banks right to know their code is secure?... Really, by manipulating signals (spoofing CTS profile match etc) that legitimately attest to TEE, say to hide the fact that a chain of trust is broken (read device no longer has Verified Boot (AVB) ie. bootloader is unlocked), you are effectively misrepresenting these details (read lying)... You are verifying what has not been verified, attesting to the trustworthyness of what cannot be trusted...

What should really be illegal?...

Of course there'll be no litigation over this either way, but If they were forced to let you run their code in unsecure (non-Trusted Execution Environments) banks would simply stop viewing Android as a safe / viable platform for their apps and cease to produce them, so you'll loose the ability to bank unless you get an IPhone in any case, and Android would slowly become untenable...

It doesn't take a genius to work out which way this'll go... 😶 PW
[Magisk] heinhuiz:
The right to know stuff? That does not even exist. Nobody has any right to know what I do with my personal belongings, and that includes my bank and even the government. I am entitled to do whatever I want with my phone, as long as I don't break any laws.

This genius is already considering to buy a PinePhone and work from a browser.
[Magisk] lm089:
Sorry for a silly remark / question: as I no longer have a repo in Magisk 24+ I guess it's a good idea to do one last d/l of TWRP A/B retention script module before upgrading? I made it a habit to simply delete the module after use then d/l it again after the next OTA. Anything else that changed in Magisk in regards to OTA behaviour for A/B devices?
[Magisk] lm089:
Honestly I never liked the idea to have sensible stuff like a banking app on a device I'm carrying with me everyday, that I can lose, have it stolen or whatever. Esp. since banks started bringing all their services back into a single app after they found that using true 2FA was too expensive.

So I dedicated one of my older phones running LOS 17.1/A10 to be my sole banking device. It's unrooted now so no hassle with root detection etc. As long as the banking apps support A10 devices I'm more than happy with that solution