yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Google believes app Devs have that right...

The bank has the right to do what they want with their intellectual property (code), including offering it with conditions...

Or not at all.

That's beside the point. 😜

But you'd like to see laws to limit what banks are entitled to do with their code. 😉

And you're quite entitled to do that too... 👍 PW
[Magisk] jhedfors:
Fox's Magisk Module Manager in the OP (post #5 actually).
[Magisk] heinhuiz:
There are more things Google (and Apple) consider their right while is is actually wrong.

Up to where they start breaking the law. And I would really like to hear an expert's opinion on that. Especially a lawyer with knowledge of the European GDPR.
[Magisk] lm089:
Yep, I've seen that. Guess I asked the wrong question ;): as far as I understand I can still load modules that are stored on my device, correct? Since the retention script is the only module I ever really used I hope I can get away without installing Fox that way. Or is that a wrong conclusion?
[Magisk] jhedfors:
Yes, you can install any module manually, by selecting "install from storage".
[Magisk] pndwal:
The whole computing industry is going that way as I said... They all must be wrong, including all the soc / processor makers, and wasted a decade of r&d and $billions more in manufacturing chips w/ HKA support...

@ipdev?... PW
[Magisk] ldeveraux:
Man, wake up and smell the coffee. Google and Apple assert their dominance as far as they possibly can without breaking the law. They also go over the line occasionally and have to pay for that. They only "go that way" because it's the direction that makes them the most money. Every other motive is ancillary.
[Magisk] heinhuiz:
That's beside the point 🤪

@ipdev should remove all our posts on this subject for being grossly off-topic.
[Magisk] _mysiak_:
Anyone with Xiaomi phone who has been able to successfully pass Safetynet? I tried probably all the combinations (Magisk hide, Shamiko, Magisk hide props,..), but the best result I achieved is to switch from HW to basic Safetynet attestation and that's it. Everything fails, I can't even hide unlocked bootloader. I am using stock Xiaomi Mi 10T lite, had to rollback to Magisk v23, where everything works without any hiccups.
[Magisk] zgfg:
Xiaomi Mi 9T, MIUI 12.5, A11 - passing always
[Magisk] _mysiak_:
What combination of settings and modules do you use please? :)

I did these steps:

1. update magisk from 23 to 24

2. enable zygisk, enable magisk denylist, added gms + gms.unstable + gms.snet (+mamo and banking apps)

3. reboot, safetynet doesn't pass anything

4. install zygisk version of universal safetynet fix, reboot, HW attestation changed, but still not passing

5. install Shamiko, disable magisk denylist, reboot, no difference

6. install Magisk Hideprops, tried some random fingerprint, no difference

Mamo reports unlocked bootloader and detected magisk, zygisk,...
[Magisk] digger16309:
Questions on upgrading....I'd like to avoid bootloops and such...

Pixel 5, Android 11, Magisk Stable 23, running Riru and LSPosed. Magisk app NOT hidden. NO safetynet. EX Kernel.

Can I safely update to stable 24.1 in the app and then deal with the riru/zygisk changes thereafter? Do I need to re-patch the bootloader with the new version before applying the custom kernel or will my kernel remain unaffected?
[Magisk] m0han:
you answered it yourself, imho (one method): would have to search for the author and chase the module and etc etc.

edit: another method is in the last paragraph of the post above this. ;)
[Magisk] ithehappy:
Yeah the BHIM app does work simply by putting it under Deny list, so does Bank of Baroda's app BoB World, and Payzapp as well. And I don't even pass safetynet (only basic, not CTS). I noticed the Payzapp app refuses to work if basic integrity fails, so I installed the Kdragon USNF and it then works. It's only the iMobile Pay app which has stopped working since the version 14.6 update. Is iMobile working for you as well just by putting it under Deny list (and obviously renaming magisk)?

If this is the way forward, every banking app detecting root every now and then and we are forced to install multiple modules to circumvent that, I fear keeping a phone rooted is going to be a hassle. So either staying on stock on a still supported Pixel or simply moving over to iPhone is the more logical choice. I do not understand how not allowing us to use banking apps on rooted devices have anything to do with security, as most, if not all frauds done do not have anything to do with root, right?
[Magisk] AbdRiz:
Hi, I've been trying to install magisk on my Oneplus 8 running android 11 but it just makes my phone go into a bootloop, I've tried installing through twrp and also through patch image method but it's the same either way, any idea what to do?
[Magisk] rodken:
Reflash your stock boot.img if you are coming from a Custom Kernel or by performing a complete reset of your ROM if your running OOS.
[Magisk] AbdRiz:
Yeah, I have reflashed stock boot.img but I want to root my phone and have no idea how to proceed
[Magisk] rodken:
Install and launch the Magisk Manager app on your device.

Then tap on the Install button situated next to Magisk.

From the Method section, choose Select and Patch a file.

Browse to the extracted boot.img file and select it.

Then tap on the Let’s Go option situated at the top right.

Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.

The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be *magisk_patched.img*

8. Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):adb devices

9. Now type in the below code to boot your device to fastboot/bootloader mode:adb reboot bootloader

10. Next, type the below code to flash the patched boot image file:fastboot flash boot magisk_patched.img

11. Now you may Reboot the device by typing the below code:fastboot reboot
[Magisk] AbdRiz:
Yeah, I know, I've done all of that multiple times and I get into a bootloop when I reboot after flashing the patched image
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86696473 👍 PW
[Magisk] AbdRiz:
I don't really understand what that means
[Magisk] pndwal:
What don't you understand? PW
[Magisk] AbdRiz:
I'm really new to all of this so I've no idea what any of that means sorry, what am I supposed to do?
[Magisk] pndwal:
Did you click the link? PW
[Magisk] rodken:
I wonder if you flashed your patched boot.img to the wrong slot?

:unsure:
[Magisk] AbdRiz:
Yeah, I did, it shows this
[Magisk] AbdRiz:
Yes I flashed both slots
[Magisk] pndwal:
OK; I linked other thread because I answered there... Not sure why you're asking about it here, but that link is the fix. I asked if you use Stable Magisk build... That screenshot is a fix that likely addresses your issue (but no guarantees!) assuming you are currently on public build... It's a downstream fix from latest public Stable, but already built in debug Canary builds; if you want to try it, use download link in Magisk GitHub home page... PW
[Magisk] AbdRiz:
Ok yeah, I'm using stable build, should I download the canary build? Again I'm so sorry if I'm being dumb, I'm really new to all of this
[Magisk] pndwal:
Yeah... Saw you joined yesterday... Welcome!

The busybox regression is just one of a few issues causing bootloops... Just looks similar to your symptoms... So I would download / try Canary in your case... PW
[Magisk] AbdRiz:
I tried canary and sadly it didn't work
[Magisk] ipdev:
Not sure about the 8 series.

From what I read, Magisk works with no issue on the 8 series.

Save for broken fingerprint sensor/reader using the USNF module for some.

This should be fixed in the next release of the USNF module.​

I only have a 5T, 6T and a Nord N200.

All running the latest OOS for the device.

5T is Android 10. 6T and N200 are Android 11.

They are rooted with the most current Magisk build.​

Installing Magisk using a custom recovery (TWRP) was deprecated.

The recovery can (will) interfere with the patching, especially on newer devices.

When you copy the boot image(s) between the device and computer, use adb to push/pull.

It has been noted that copying the boot image using file transfer mode(s) can corrupt the boot image.

Using adb push/pull is the safest way to copy the image(s) between the device and computer.

This is why the Magisk instructions tell you to adb pull the magisk patched image from the device.​

---

A few months ago (when Android 12 was release), we had to do this on the 4a (5G) and newer Pixel devices.

We could boot the magisk patched image.

To install it we had to disable verity and verification in the prior install (and keep it disabled when updating) or disable it and wipe data to install the magisk patched boot image.

It was fixed for Pixel.​

(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img​

This can cause issues on some devices.

I am not sure if OnePlus 8 series is one of them.

The inactive slot is the fallback (failsafe) for A/B devices.

If the inactive boot image is not compatible with the rest of the inactive slot, some devices might halt on boot.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] jesrani:
For some reason BHIM doesn't work for me, not sure why. I tried to uninstall with SD Maid and install fresh but now it immediately crashes when I try to open it. Something seems to be leftover from past installs maybe. I guess I have to work without this.
[Magisk] AbdRiz:
I used adb pull this time and still the same? now what should I do?
[Magisk] AbdRiz:
I used adb pull and it still didn't work
[Magisk] Kurt Krummbein:
Followed these steps also for german VR-Banking apps (which detected app-hooking before and refused to start) ... worked like a charme :-).

Thanks a lot guys !(ThumbUp)
[Magisk] ravidevani:
Thanks!! It worked. Shamiko is not required though for this particular app!
[Magisk] rodken:
Send me a copy of your boot.img by attaching it here and let me perform some 'dogfooding'.
[Magisk] Vurio:
I tried this method and couldn't get Imobile to work. Any help would be appreciated.
[Magisk] jesrani:
Have you added Shamiko and LSPosed modules to Magisk? Have you also added iMobile Pay app to the deny list? This method worked perfectly for me.
[Magisk] Vurio:
I did. I put some screenshots to show the steps I followed. Add Shamiko and Lsposed to Magisk, download HMA app, enable HMA in LSposed. Add iMobile to deny list in Magisk and in HMA. Clear data in Imobile, and reboot and see if everything is activated.

Finally iMobile should work. But I am still getting the rooted message and the app force closing.
[Magisk] jesrani:
Did you reboot multiple times as given in the post? Maybe you can uninstall imobile, reboot and then again do the complete procedure. I am having similar problem with BHIM app, just doesn't work for me whereas for others it is working only by putting in deny list.
[Magisk] kullurumanoj:
It didn't work for me for the first time. You need to add the repackaged magisk manager (which gets installed when you enable hide the manager ) as well in the hma. App worked for me after doing that
[Magisk] zgfg:
FYI, Custom Magisk renamed to Cygisk (and the package name, but to com.thehitman7.magisk)

Stable Release of Cygisk

The name is Cygisk

Version: v24.1

VersionCode: 24102

StubVersionCode: 25

Changelog

* Fixed process handling

* Fixed magiskhide code injection

* Fixed process mount namespace cleanup

* Fixed invalid "SU" response

* Improvements under the hood

This update requires clean flash installation. After installing first enable Zygisk then reboot, following this you can either enable MagiskHide or Denylist, finally reboot for desired effects.

It has Zygisk, MagiskHide, Denylist, SafetyNet Checker, Hide the Magisk app. To learn more about Custom Magisk, visit this link!
[Magisk] GreekPilot:
Strange... No system.prop file, so no ART parameters abnormal in Momo with LSPOSED Zygisk 1.8.1
[Magisk] daemonicvs:
hi,

is there a way to spoof that google play services is installed? i dont use it and i dont use microg or something like that. nothing. so when starting the app "iCard" it says that i have to update google play services to use this app. i dont think that usnf and change props can fix this. i assume that the basic integrity test already fails so everything else may be useless with such prerequisites, right? so is there a way to fix this?

best regards
[Magisk] zgfg:
And the same day (all today), 10 hours later, project discontinued

Btw, Alpha and Custom Magisk were useful before Magisk v24 was released (and until it became pretty stable)

IMHO, now is better to stay with Stable (or Canary), no more needs for those proprietary releases (that are also not accountable in one way or another)
[Magisk] zgfg:
Mentioned last week in the few posts
[Magisk] Stillhard:
In the old days, i used to know the name MenTaL from RageZone, a great person, but now this custom magisk maintainer can have that mentally sick person title :LOL: , it's been like 2-3 times she've been done that
[Magisk] Vurio:
I did that. The jj.oojr.mmwff.y is the repackaged Magisk manager. I still can't get it to work. Maybe it is because I am on the Canary release of Magisk?
[Magisk] m0han:
maybe there is more to it than meets the eye. his BiTGApps project seems popular: https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/
[Magisk] zgfg:
I don't understand your usage of HMA.

If you want to hide an app by HMA (LSPosed mngr, Magisk app repackaged or not) you don't list them under the Effective apps - instead you put them to a Template and then you list/enable the 'banking' app under the Effective apps, by linkinking to that Template with Magisk app and LSPosed mngr

Sorry, I will not further guide/answer again and again how to use HMA. There were posts about (eg, I did post some guides), so please scroll back, find, read and see how to properly use HMA
[Magisk] Denny@83:
Hi,

with device OneplusNord N100, magisk 24300, Lspsed, hide my applist, USNF and Shamiko I confirm that the only way i found to have banking apps working is leaving Magisk DenyList Enforced. If I don't apply denylist and reboot, banking apps won't work.

with this device in order to have banking apps working, i always must leave Denylist Enforced and Shamiko installed
[Magisk] pndwal:
Strange... Shamiko won't do anything w/ denylist enforced... What message does Shamiko give in modules list when denylist is disabled?... It should take over hiding, stating "Shamiko is working as blacklist mode" or similar... And do you have version 0.4.4 (106)? PW
[Magisk] Denny@83:
I tried using the app with Shamiko module disabled and denylist enforcing; the app works. I confirm Shamiko doesn't work with denylist enforcing. The only way I have to use the bank app is lsposed and HidemyApplist.

A couple of month ago at first installation my bank app asked me root access through Magisk app, but i didn't give root permission. Then followed instructions to hide root with Shamiko but nothing worked. Now with magisk 24300, denylist enforcing and latest lsposed+hidemyapplist the app works

(I'm on latest Shamiko 0.4.4)
[Magisk] pndwal:
Yes, but once passing with HMA etc, does disabling denylist (with Shamiko active / working) cause bank app to fail? PW
[Magisk] J.Michael:
Did you try uninstalling bank app, reinstalling bank app, and not running bank app for the first time until after doing everything to keep bank app from seeing Magisk / Shamiko / whatever-else?

I find it disturbing that bank app requested root access. Maybe that's just an obvious first test to see if device is rooted. Maybe you are not really running a bank app.
[Magisk] Denny@83:
yes. i did the test after your previous reply. If I disable denylist, bank app crashes even with Shamiko active.
[Magisk] Denny@83:
at the beginnig i used magisk app (version 23000) installed with a random package name, and bank app worked

I update system, so before updating I restored the original magisk app. After restoring, bank app asked me for root access.... (magisk 24.1)

then I followed instructions on how to hide root with newer version of magisk and installed USNF+Lsposed+HidemyApplist+Shamiko. All the apps worked without detecting magisk except this bank app.

Some days ago I installed Xprivacy LUA but this didn't solve the problem; now i saw a previous post and tried to use app with denylist enforcing and il worked! Maybe it could be XprivacyLua.....

btw, magisk app is not hidden; it is installed with its original name
[Magisk] dejson:
Hi all. I am using intune company portal for a 2 month now and not a single issue since using zygisk. However I would like to know if updates to apps in work profile are safe to perform, company portal at first place. Thank you
[Magisk] J.Michael:
It makes more sense for your current success to be due to XPrivacyLua.

Maybe repackaging the Magisk app was part of the reason for your success before you updated your OS and Magisk.

Is this the first time anyone has seen a bank app request root privilege?
[Magisk] gagan007:
Need some help related to Duo MFA app. I followed the first couple of pages in this thread and then installed apps/modules as suggested in this post. Earlier when I kept enforce denylist off, Duo said my phone is rooted along with SafetyNet attestation fail. Now when I toggled it On, there is only one issue related to SN attenstation thus app doesn't authenticate. (message it gives = Your mobile is not permitted by your admin bcuz it is rooted or tampered.)

I have renamed Magisk, it is 24.3, Zygisk Yes, Ramdisk Yes, latest app installed. Also in modules I have USNF 2.2.1 and Zygisk - LSPosed 1.8.1 (6499) (if I am not wrong, this is Shamiko)

The handset is OP6 (OOS 11.1.2.2), is rooted (:
[Magisk] pndwal:
Sounds like passing SafetyNet (check w/ YASNAC app)... Sounds like you don't have Shamiko module (Here: https://lsposed.org/ )... install, then disable Enforce denylist... See OP posts 1-9 here also... PW
[Magisk] zgfg:
I have the same Duo Mobile and it does not complain about root

But one thing must be clear:

- all 'banking' apps must be listed in DenyList, including Duo

- If you use Shamiko, you have to disable Enforce DenyList BUT STILL apps like Mobile Duo must be ticked in Configure DenyList

That's because Shamiko will take care of DenyList, but it also reads from the same DenyList (although Enforce DenyList is disabled), hence those 'banking' apps (incl Duo) must be in that list

You only don't enable Google Play Services in Configure DenyList because USNF takes care of GMS - but USNF takes care only about GMS

I have also Zygisk-LSPosed but it's irrelevant for Duo and for Safety Net.

And you don't need Hide My Apps (LSPosed module) for Duo

My screenshots (related to Duo) are attached

BUT before playing with Duo, make sure you pass the SafetyNet.

Pls check the OP posts in the new Magisk + Zygisk thread

And general tip: when hiding root from an app (like Duo), as long as you're still configuring, always Wipe Data (Settings, Apps) for that app because the app could detect root once and remember that - to test if the new step (like adding to DenyList) helps or not, you must 'erase' the memory that root was previously detected

And each time you reconfigure or enable/disable DenyList, add a module, etc - you must reboot to apply the changes
[Magisk] mGforCe:
Hi, I am also facing something similar to what Denny@83 shared here.

I have Redmi Note 7 Pro running Custom ROM A11. My setup is following:

Magisk 24.3, magisk manager renamed,

zygisk beta enabled,

bank apps selected in "Configure Denylist",

"Enforce Denylist" disabled

In modules I have USNF, Shamiko, MagiskHide Props Config, Zygisk LSPosed, and Enhancer mode for HMA

Now, this setup works for running most of Indian Bank & Fintech apps including AmEx, CitiBank. But lately apps of Standard Chartered and HSBC are crashing when we try to open with above setup. I tried to disable these apps from finding other notorious apps using HMA too but no benefit.

After reading above comments from Denny, I was curious to try his theory.. So enabled "Enforce Denylist", and just tried opening these two apps without any reboot etc and voila apps open fine, no crash etc,

So what can be the issue here? Is Shamiko not working as intended for these apps? These apps were working like few weeks back, but then we have magisk update, Shamiko update etc etc.

Any tips, ideas?

Tagging @pndwal @J.Michael @zgfg @shadowstep for attention pls, thanks in advance!

EDIT: Problem solved... Thanks to post of @d0a0de5d32 here

While we were talking about Shamiko and enabling/disabling enforcing denylist, but solution came via tweaks to HMA and restricting the options selected to hide detection.

So learning what and how to select in HMA is very important. Look forward to hear from @shadowstep

EDIT 2: It seems, checking things late at night have its own perils.

Yes, while the app can open and is no longer crashing post these changes, post login to account, am greeted with message that device seems odd (root being detected) and doesn't allow logging into app.

At same time, just enabling "Denylist" allows bank app to login.

So back to square one :( Problem not solved

Thanks @pndwal @zgfg @J.Michael for your guidance and inputs
[Magisk] mGforCe:
Thanks for these detailed steps...

We missed you when we had this issue few weeks back when moved from ICICI iMobile v14.4 to v14.5.

After that, something happened at iMobile and guess they got back 14.3 which started working.

I anyways did all that you mentioned above as well as disabled few more things from XprivacyLua like activity, applications, tracking and analytics. May be xprivacy was overdo... it was required for Axis Bank app.

Two Questions:

1) Why in HMA you selected only these hide methods -> Check API requests, Intent queries, ID detections

and not selected "All hide methods"? Trying to understand and learn more

2) How can we find when to use Xprivacy and when not?
[Magisk] zgfg:
When you enable DenyList and reboot - does Shamiko still display as working in Blacklist mode (or displays an error or how)?

Try then also with Shamiko disabled

Btw, you may test with the older versions of Shamiko, they can be downloaded from TG "Magisk Alpha" download only channel (publicly available and in English) - if you suspect that it worked with an older version of Shamiko (while Enforce DenyList was properly disabled,)
[Magisk] pndwal:
FWIW, on RN8T (stock, A10), I have Standard Chartered starting fine with Shamiko (HMA not engaged):

I can't start HSBC India app w/ or w/o Shamiko (HMA engaged)...

Stock, A10 ROM may be reason for differing mileage...

1) This:

https://github.com/Dr-TSNG/Hide-My-Applist#how-did-hma-magisk-module-work

2) Not sure, but much of this is trial and error only as dealing with closed source detection... PW
[Magisk] gd48202:
I have a Samsung Galaxy Note 3 with Havoc Version 2.9 (Android 9). I had Magisk 24.1 installed and working properly. I updated the App portion with no problems. When attempting to update the Magisk portion, I click update leave the options unchecked, choose Direct Install (Recommended), Click Let's Go, the I proceed to get the error "Unable to detect target image".

Is there a way to resolve this issue. If so, Please detail how one would go about to resolve it.

Thanks,

GD
[Magisk] pndwal:
RV Android 4.3!... still old kernel?

Looks like this issue [24201] failing to update Magisk #5544

Related (duplicate) issue readlink -f from busybox is broken for kernel version < 3.6 #5530

Related to Pull Request Replace realpath to BSD implementation #5620

Fixed by commit b1faa5e - Update BusyBox

Built in 24305+...

Give Canary a whirl... PW