yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
Just a thought ...

To get around this package-name detection, is there a quick-and-dirty (or better yet, quick-and-clean!) way to change the package name of an app to something of our choice? Or to clone a given app to an identical version with a different package name?

When Magisk hides itself, it does something similar, although I don't know whether the new package name is hard-coded, or somehow determined in an ad hoc fashion at the time that this hiding takes place. It would be ideal if we could specify our own package name, so that these annoying banking apps don't figure out the package name that is used for the clone and then check for that, as well.
[Magisk] zgfg:
But with HMA it should hide without the need for repackaging

Eg, Ruru, TB-Checker also look for Delta, hiding in Delta app does not help but with HMA they can no more detect
[Magisk] Hirs_E_Fruit:
Since the Magisk 25.2 delta 5 and onwards when I install/flash this version after the reboot the Google Play Services/Store keeps crashing!

With Magisk 25.2 delta 3 or below I have now problems.
[Magisk] huskydg:
I guess you have shamiko
[Magisk] huskydg:
No shamiko support, ok 👌
[Magisk] zgfg:
Btw, for the latest Delta 0b2d2ed3 (25206), is the app_process_wrapper necessary for Zygisk?

I tested with Wrapper and without, in both cases the phone boots, Delta app shows Zygisk Yes and Zygisk-LSPosed (with four its modules) all work fine

Of course, I don't have Shamiko, I don't need USNF for my Xiaomi.eu, I don't use your ReVanced hence LSPosed is my only Zygisk module and it can still works fine, hence my Zygisk works fine without the Wrapper
[Magisk] huskydg:
That is for Bluestacks to prevent bootloop if running Zygisk btw
[Magisk] huskydg:
Dear users,

I no longer update MomoHider and the latest Delta no longer supports MomoHider (still work but buggy)...
[Magisk] huskydg:
New way to hide Magisk app

GitHub - Magisk-Modules-Alt-Repo/frozen_magisk_app: Dynamic freezing Magisk app

Dynamic freezing Magisk app. Contribute to Magisk-Modules-Alt-Repo/frozen_magisk_app development by creating an account on GitHub.

github.com
[Magisk] huskydg:
Tool for run scripts when specific app is running, i hope other people will use it to make some useful modules

GitHub - Magisk-Modules-Alt-Repo/magisk_proc_monitor: A Magisk/Zygisk module allows user to run script whenever app process start

A Magisk/Zygisk module allows user to run script whenever app process start - Magisk-Modules-Alt-Repo/magisk_proc_monitor

github.com
[Magisk] AboAnas25:
I can't hide last update for this app

Absher | أبشر - Apps on Google Play

Absher is the official individuals eServices Mobile Application in Saudi Arabia.

play.google.com

I am using magisk delta canary version with activated zygisk and hide my app list

All banking apps working properly except this one
[Magisk] famaTV:
Hello friends!

After installing the latest beta6 app, I can no longer install it in LDPlayer9. Your guidance is truly appreciated. Many thanks in advance!

Edit: I fixed the problem by Enabling / option 1 then restart and then option 2. I think somehow with Magisk Delta App update, root was affected.
[Magisk] famaTV:
Hello bro,

I hope you are doing so well!

Have you found a solution for this? It's not only banking apps that now stopped working, but games like Match Master and entertainment streaming apps like Shahid.

I kind of overcame those on my phone but couldn't do it with LDPlayer9.

Thanks in advance,
[Magisk] zgfg:
Upgraded from Magisk Delta Canary 4dbd8358 (25206) to 64faa31a (25206) and now https://play.google.com/store/apps/details?id=com.hce.compliance.checker

reports Error Detection

With 4dbd8358 (25206) and all previous Delta versions I had always fully passing with the same S Check

Actually, that was the reason/advantage I originally switched from Magisk TJW to Delta (with the official TJW Magisk S Check was also reporting the same Root detection and there was no way to make it passing that Root detection in S Check)

I double checked by flashing back my previous boot.img patched by Delta 4dbd8358 and then S Check happily passes

Once more I installed the latest Delta 64faa31a, and S Check again reports that Root detection

Always the same settings (Zygisk, S Check in MagiskHide, no SU List, no Core Only, no Shamiko, hiding Magisk app and LSposed modules from S Check by HMA)

Staying back with the good previous 4dbd8358
[Magisk] 73sydney:
Good to know, because i literally just downloaded 64faa31a thinking id finally get around to seeing if Delta fixed my Opal Card app issues, so ill give that a miss and try the earlier one...

Your sacrifices in testing do not go in vain
[Magisk] Nicols0Mart:
Can confirm this myself. Also, my oneplus 7 pro was able to pass safetynet/play integrity just by putting gms and gms:unstable in magiskhide with previous canary builds. With latest 64faa31a build I had to install safetynetfix module to pass device integrity
[Magisk] zgfg:
But USNF does not help you with Delta 64faa31a to pass that Root detection by SCheck?
[Magisk] Nicols0Mart:
No, root detection fails just like you. I installed USNF because of device integrity failing even with play services in magiskhide list
[Magisk] zgfg:
I tried both USNF 2.3.1-mod and 2.4, no help for Delta 64faa31a - S Check always detects Root

However, otherwise I actually don't need (and don't use) USNF, my Xiaomi.eu passes SafetyNet/Play Integrity just with MagiskHide (Xiaomi.eu custom ROMs include the needed USNF spoofs)
[Magisk] martyfender:
I have a similar Magisk configuration as you and I get the same results with 64faa31a (25206).
[Magisk] m0han:
Thanks to you guys, I won't be taking the plunge with 64faa31a-delta (25206) (34). Hope @huskydg would address the issue with a quick fix.
[Magisk] huskydg:
MagiskHide no longer spoof/alter/manipulate any non-Magisk related signals or traces to circumvent any device state detection, but it can be done by third-party module
[Magisk] m0han:
Well, I didn't have to use the attached module. My device does not have NFC. TB Checker also passes everything (except Strong and Virtual Integrity, ofc). GPay works too. 😄
[Magisk] martyfender:
This module solved the above issue. I actually found your post 1st on your telegram channel.

Couldn't this also be done in the now discontinued Magisk Hide Props Config, or is this module different in some aspects? I haven't compared them.

Thanks
[Magisk] zgfg:
Thanks for clarification. Now with that additional module reset-sensitive-props the latest Delta 64faa31a passes again Root detection in S-Check

(In fact, I played more and modified your module zip to exclude everything, ie manipulation of sensitive props and left only customize.sh and its copying of oem.rc to initrc.d - and that's exactly what's needed for the Root detection check in S-Check (my props were already spoofed correctly)

But then I also tested with the official TJW Magisk - it also passes S-Check now with that module (ie, with its oem.rc).

The other checkers were already passing, hence with this module (regarding to checkers) I have the same situation now both with Delta and the official Canary

One more thing, could you maybe include to your module the spoofs from App Data Isolation module from @Stillhard (if he agrees) - those spoofs are needed for Ruru:

GitHub - stylemessiah/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 - stylemessiah/AppDataIsolation: An attempt to block apps from accessing other apps' priva...

github.com
[Magisk] 73sydney:
you mean these?:

persist.sys.vold_app_data_isolation_enabled=1
persist.zygote.app_data_isolation=1
[Magisk] zgfg:
The module AppDataIsolation.v1.0.zip

makes also some (systemless) changes to

/system/etc/compatconfig/services-platform-compat-config.xml

But yeah, only those two data_isolation props from the system.prop are essential for my clean Ruru check
[Magisk] 73sydney:
yup, im aware of the xml edits, thats my module and implementation (xmlstarlet binary thanks to @Zackptg5 ) of the method proposed and linked to me by @Stillhard :) :)

as noted it only has one glitch for me at least, i have to remember to disable it, and reboot, before doing a backup run with Migrate :)
[Magisk] zgfg:
Ok, so the module is on your GitHub repo, but module.prop says v1.0 by Stillhard?

The script uninstall.sh attempts to clean through the folder:

/data/adb/modules/.compatconfig-files

but I don't have that folder - is it something wrong on my side

Also, that small change in the XML file - is it really important (since for me only the two props from system.prop make a difference for Ruru)?
[Magisk] 73sydney:
Stillhard asked me make the module. And i decided since he dropped it in my lap to credit him, also in case there were issues :) :)

uninstall.sh inside the module is a largely static file (its part of the MMT-Extended template by Zackptg5)

Spoiler content hidden.

with any custom uninstall script added to the top of it - for this module there isnt (and i dont think ive added any to any module ive released since the GPay module - i think that was the one and only - to undo the db changes etc). id never seen that path until you mentioned it, and i just flashed the module and checked the uninstall.sh post flash and it indeed has an added line with that path under an INFO variable, which ive never noticed before. I'll have to ask Zack....

Its clearly visible during the install phase and contained in common/functions.sh

# Set variables

[ -z $ARCH32 ] && ARCH32="$(echo $ABI32 | cut -c-3)"

[ $API -lt 26 ] && DYNLIB=false

[ -z $DYNLIB ] && DYNLIB=false

[ -z $DEBUG ] && DEBUG=false

INFO=$NVBASE/modules/.$MODID-files

My guess is it maybe stores where files are placed for later removal during uninstall?

PM'd him for clarity

Its obviously not a critical function as uninstall works without it

as for the xml file edits, the values it changes only appear in Adnroid 11+ and they are supposed to ultimately enforce isolation on the /data folders. i havent tested whether the prop values are enough, as again i was just asked to create the module based on the linked article. i know @huskydg made his own method for -A11 and that it uses a different method as those xml values do not exist predating A11. So i assume they are needed for enforcement....but not tested. Again i tend not to test everything in every module to a granular level, but as ive always said, i admire people who do and have the time to do it.
[Magisk] 73sydney:
@zgfg

Okay update to last post, it is what i thought, i just managed to use the wonders of the forum search on the MMT-Extended thread and a single result that wasnt just "info" coughed up this post

Paraphrasing:

"The default functionality in uninstall.sh leverages an '$INFO' file which tracks files outside of the module's root folder and removes them for you"

Mystery solved.
[Magisk] huskydg:
For some reason, i don't like MMT-Extended template
[Magisk] zgfg:
1) Magisk itself uninstalls modules by removing their folders from /data/adb/modules

However, some modules may leave something outside (or make some hard changes that must be reverted), and then you need uninstall.sh script to clean those things (you can read TJW GitHub page, Magisk Docs, Dev part, describing the modules architecture and what for are particular scripts like uninstall.sh)

In your case there is nothing external to remove/revert, hence you don't need uninstall.sh script

2) You use Zack's template and his installation script (common/functions sh) expects uninstall.sh file to dynamically prepend paths like $INFO to the uninstall.sh template, to delete from that outside folder that you don't really have

Simply remove uninstall.sh from your zip and there will be no uninstall.sh script installed to /data/adb/modules/compatconfig

Actually, you can also remove Readme.md file from the zip (not processed by either Magisk app nor Fox MMM and not copied to /data/adb/modules

Of course, .gitignore and .gitatributes files are of no use in the module zip installation file😄
[Magisk] 73sydney:
I just find it easier to have a base to work from
[Magisk] 73sydney:
i know i could remove this and that, but i find it easier to just have a similar base, and in the past as i mentioned i used to use uninstall.sh

i am a creature of habit and as mentioned plenty of times, also quite lazy :)
[Magisk] zgfg:
That was my actual concern, that (systemless) changes in the /system/etc/compatconfig/services-platform-compat-config.xml

related to the CTS_SYSTEM_API

Something I would actually expect to be part of modules like USNF (?) - and something that I actually found not needed for my hiding the Libc and Syscall File detections in Ruru
[Magisk] 73sydney:
Im not sure what youre trying to say there
[Magisk] zgfg:
IMO, potentially too sensitive changes to be covered by a disclaimer:
[Magisk] 73sydney:
Im still not sure i understand your point, and im sorry

im just the mug who was asked to create the module exactly as outlined in the article referenced in the README, i just found a method to make the changes, i have no flipping idea of what the internals of the changes mean :)

All i was told was it does what it was supposed to do :)

Its also a magisk module thats reversible....
[Magisk] kusakhan:
s9+ oreo TW bootloop issue after enabled zygisk
[Magisk] huskydg:
how can i help you with only this???????????
[Magisk] kusakhan:
possible run latest magisk on oreo verion s9+ with zygisk
[Magisk] huskydg:
And then you only say "xxx is not working", "xxx cause problem", .... bla bla again without any information and i don't know how to help you 🙃
[Magisk] huskydg:
Please record logcat with **debug** build and send here!
[Magisk] coolkid3245:
Indomaret works with :

Magisk Delta Canary (7583eb16-delta (25206))

Magisk app not hidden

Zygisk off

MagiskHide + Enforce Sulist on

However, using either zygisk or riru makes it not work again. Does anyone know a workaround for this? Thanks in advance.
[Magisk] huskydg:
Because it detects resetprop, riru and nb zygisk both use resetprop, which will be triggered. And original zygisk is also detectable.

If you can find a way to inject zygisk lib without change native bridge then you can use zygisk 🙂
[Magisk] famaTV:
Hello friends,

Any way to overcome this problem with this game? After a recent update, it stopped working on almost all PC emulators. Not sure if it's Magisk related or if possible to use Magisk Delta module to fake / trick the game into thinking it's running in a regular device?

Thanks
[Magisk] zgfg:
Don't know about emulators and would it help to your game but since the last ten days ago, you have to use for hiding:

GitHub - Magisk-Modules-Alt-Repo/sensitive_props: Reset sensitive properties to safe state, take from MagiskHide code

Reset sensitive properties to safe state, take from MagiskHide code - Magisk-Modules-Alt-Repo/sensitive_props

github.com
[Magisk] famaTV:
Hi friend!

Thanks for the guidance. Indeed, I already tried it earlier with no luck. I am using latest canary version of Magisk Delta in addition to HMA for hiding but it could be the need to either/both hiding is required or spoofing the emulators info fed to those apps/games making them think they are running on a real device.

I was able to overcome the issue in a real device but not an emulator.
[Magisk] huskydg:
@famaTV MagiskHide's goal is not hiding emulator. Emulator detection has nothing to do with Magisk!
[Magisk] famaTV:
From your experience, would you be able to direct me to a place to further investigate? Truly appreciate it! Thanks bro.
[Magisk] xabier-bo:
Hi, @huskydg

I follow this thread despite I'm using "standard" Magisk at the moment.

I've seen you are the developer of the magisk module "Advanced reset sensitive props"

I've come to it because for the first time, for me, I have found that a bank app complains that the device has developer options enabled. (First it complained about being rooted, but after including the app in the denylist it only complains about developer options).

Despite installing the module, the app still detects that UserDebug is activated

I post the question here, just in case any of you have found any procedure/strategy to prevent apps detecting Developer Options activation

At the moment I have stock Android 12, Magisk 25.2, kdrag0n USF v2.4.0, Zygisk, and Enforce DenyList enabled for critical apps

Thanks
[Magisk] onimorza:
Use Delta canary, toggle on magiskhide, add troublesome apps to hide list, add USF module, add ARSP module, add zygisk lsposed module, add HMA lsposed module, configure HMA (many good tuto's available), and change magisk name.

Maybe need to reboot between every step, don't remember.

Maybe after all this you also need to force stop the troublesome app and clear its cache and/or data.

This setup works like a charm for me.
[Magisk] xabier-bo:
Thanks onimorza

I'll give a try, but I'd prefer to "hide" that Developer Options are toggled on.

The app doesn't (no longer) complain that the phone is rooted, only that they are on.

You mean that using Delta Canary and the following procedure, developer options won't be visible for the bank?

Thanks!
[Magisk] onimorza:
Yes, I used to have a separate module for that in the past but think Delta does that now out of the box.
[Magisk] egar3427:
What is ARSP Module?
[Magisk] zgfg:
AFAIK, it should have better been referred to as

RSP = Reset Sensitive Props

as it shows in Magisk app (screenshot), entitled on Repo:

GitHub - Magisk-Modules-Alt-Repo/sensitive_props: Reset sensitive properties to safe state, take from MagiskHide code

Reset sensitive properties to safe state, take from MagiskHide code - Magisk-Modules-Alt-Repo/sensitive_props

github.com

and named when downloaded:

reset-sensitive-props.zip
[Magisk] onimorza:
Nevertheless, mine is ARSP and also pops up as Avdvaced in the modules, see attachment print screens.

@huskydg is there any difference between these 2?
[Magisk] zgfg:
Provide the link you downloaded from, to compare with my link
[Magisk] Sander9847:
Hello,

My device is stuck in a sort of boot freeze on the MI logo since updating with magisk delta direct install. This freeze of the MI logo happens on normal boot and on recovery boot (so I cannot enter recovery either), I am able to boot fastboot screen but then device is not recognized by my pc command fastboot devices. Anyone have any ideas as to what might be happening? I cannot find anything similar online.

Xiaomi Mi 9T android 12, I was using normal magisk manager and updated to magisk delta by installing the latest APK from github and doing the reccomended direct install in the new magisk delta app. It finished and prior to pressing reboot button I went ahead and deleted the old magisk app (cause?). Rebooting after this caused the freeze for the first time.

After reading online I cannot think of any way of restoring except for EDL testpoints? Although that is something I have no experience with...

Any help at all or a direction is much appreciated!
[Magisk] zgfg:
It's not really recommended to switch from Magisk 'normal' to Magisk Delta just by doing Direct install

Since there are so many differences, and supposidely you are new to Delta and its differences, you better had to uninstall the official Magisk and then to clean install Delta

Also, it is always recommended to patch the boot.img and to flash (by saving the old, previously working patched boot img) - then, if anything goes wrong you simply flash your previously working patched img

In fact, instead of permanently flashing the patched boot img, you can always one time temporarily boot to the patched img, and then if all ok, do direct Magisk update

All these techniques have been extensively discussed in Magisk General, Magisk Zygisk and/or this thread - it is worth to read and get informed before flashing

Now, suggesting you to use TWRP and to delete:

/data/adb

/data/unencrypted/MAGISKBIN (if present)

then to flash your not-patched boot.img

Reboot, install Magisk Delta app, and then install Magisk Delta from scratch by patching and flashing the boot.ing - patching and flashing method is described on the official Magisk GitHub, under Documentation
[Magisk] pndwal:
Trying to understand this properly...

Did you previously see device from PC as fastboot device?... Seems like that may just be a driver / ADB setup issue...

Unsure what this means... You said you installed Delta .apk... That would have replaced Magisk App... So what did you 'delete'?

I'd be trying to establish fastboot connection... Doubt it's hard bricked... Xiaomi Qualcomm devices are pretty hard to hard brick, but MTek Xiaomi devices are very fickle and historically so easy to hard brick that development ceased for many devices...

AFAIK, Xiaomi still requires an 'Authorised Account' to be used for EDL, meaning a connection w/ an authorised agent connected via TeamViewer etc (and independent authorised Xiaomi agents are like hens teeth now, also XDA won't allow publication of paid agent details here) must be established while flashing... Or you'd need to take phone to Xiaomi service centre...

It may be possible (though doubtful) to bypass authorised account requirement using EDL via test points, but my recollection is vague on that... You'd need to research per device requirements in any case...

Will wait for more info/questions from you... Sorry can't help more ATM... PW
[Magisk] Sander9847:
Thank you both for the responses! I managed to get into recovery by letting the phones battery die out completely. Then once in recovery I could get it booting again by flashing normal magisk once more. If I switch over in the future I will definitely be making a backup and flashing clean.

And you are indeed correct, fastboot wasn't bricked either but it seems my usb cable is broken for data.... I only found this out later when setting over a backup also didn't work.

It was the hidden magisk app with different package name thats why it didn't overwrite.

Seems all I needed was a nights sleep and some encouragement after looking for it way too far. Thanks again.
[Magisk] amk316:
Thank you huskydg

i tried magisk delta last night and it rooked.

two of the my banking apps(Albilad and Bouki) did not work with official and Shamiko but it worked with magiskhide.

grate work....
[Magisk] martyfender:
Can you please clarify what all of this means, in particular the second change listed?

I'm sure you will eventually update your documentation concerning this on github, also.

80855189-delta

- [Zygisk] Introduce new way to load Zygisk

- [Zygisk] Hide magisk modules from maps

Thanks
[Magisk] huskydg:
These are for advanced users only!
[Magisk] martyfender:
Yes, I agree but that still doesn't tell me what: tbis does:

Zygisk] Hide magisk modules from maps

Does this do similar things as riru?

Thanks
[Magisk] huskydg:
It is to hide the module file that is loaded into app process memory such as font module
[Magisk] m0han:
How is that 'these are for advanced users only!' when a lot of people use font modules? Hope to see Riru supported so Riru users can try.
[Magisk] m0han:
New Delta

5885e7b6-delta

- [Manager] Move "Disable Magisk" to reboot option
[Magisk] huskydg:
Disable Magisk also will restart your zygote to erase riru/zygisk
[Magisk] huskydg:
Documentation about New Zygisk Loader and Hide Memory fron maps will be added soon
[Magisk] huskydg:
Riru MapHide soon
[Magisk] huskydg:
Riru New Loader v2
[Magisk] huskydg:
The purposes of The new loader: Doesn't need to change native bridge and avoid using resetprop which is detected by this app. https://play.google.com/store/apps/details?id=mypoin.indomaret.android
[Magisk] m0han:
Waiting. BTW, Just noticed that a telegram group called 'Magisk Delta Modules' has been created by @huskydg, where modules for Zygisk as well as Riru are available. Hoping he would make

all modules

available

for both Zygisk and Riru

.