yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Did you end up getting DEVICE_INTEGRITY Back?... Assuming you did and bank(s) require it... Please say...

Actually a strange issue... PIF actually hides root from GMS process(es) (only the Droidguard, ie. unstable process, needs root hidden before A11 generally) itself, and if manually added to active DenyList Zygisk PIF functions will be broken (as DenyList reverts Magisk modifications and PIF is trying to inject fake keystore registration data into GMS DroidGuard process as well as feed it the spoofed print/prop/field set)... However, adding GMS w/ DenyList disabled and proper hiding like Shamiko is generally compatible (and necessary for some using system font modules as Shamiko has a fix for that whereas USNF/PIF hiding breaks system with these installed), takes precedence over PIF hiding and doesn't break stuff...

So it's strange... But don't know why it's breaking bank app with just that added either... Is Shamiko latest version? ... Maybe strange custom kernel behaviour? 🤔

However, you don't need PIF functions on your device as it doesn't use hardware key attestation anyway and spoofs aren't needed to bypass hardware backed evaluationType enforcement as Google won't do that for J7 Prime...

Please let us know if you have DEVICE_INTEGRITY with PIF... Also, is Superuser menu item accessable or greyed out in Magisk App?

Wondering why you don't upgrade to A9 Pie... Also, quite interested know if removing PIF and just adding GMS unstable process to denylist w/ Shamiko (only this module active) using list as hidelist (DenyList disabled) is enough to get DEVICE_INTEGRITY... (Guessing you may need to revert to stock kernel however)...

🤠 PW
[Magisk] ashish1989:
But the problem is not literally related to hiding, the app can not start, the app has stopped problem always comes, whenever I add my banking app in denylist
[Magisk] pndwal:
27.4 would be a public stable or beta build and nothing beyond .0 yet... But yeah, a few extra fixes in 27002 Canary... Should get 27003 (or 27100/27.1, 28000/28.0?) any tick of the clock...

Good to test Canary for issue, but would need to install Debug for that (verbose logs)... PW
[Magisk] ashish1989:
Yes, I am getting device integrity now, with latest Clark print

Using latest Shamiko

By the way, did you check my logs?

Accessible
[Magisk] pndwal:
That's what many apps do if root/mods are detected... They don't always say why... Many just freeze... PW
[Magisk] ashish1989:
Should I do a complete uninstall of magisk first and install it again?

And should I add gms and gms unstable processes in denylist with latest Shamiko only, no PIF I mean?
[Magisk] pndwal:
To try w/o PIF? - No need... If you suspect corrupted Magisk configuration, just delete everything in /data/adb and reboot to rebuild config clean (assuming no unusual modules that should be uninstalled via their 'remove' routines; most don't need that), then install Shamiko and configure DenyList (disable)...

Of course if you suspect kernel and revert to stock kernel, you'll need to reinstall Magisk...

Yes, No, add just GMS unstable process as explained... 👍 PW
[Magisk] ashish1989:
In my case, Shamiko was the culprit. I uninstalled it and installed Zygisk Assistant. I am passing both basic and device integrity. My bank app is also working fine, its even added in denylist too.
[Magisk] pndwal:
Very interesting, if strange... Assume you still spoof stuff in GMS with PIF?... I would have recommended Zygisk Assistant for passing w/o PIF too, but it's less likely to work that Shamiko for hiding root from DroidGuard as it only has a very limited list of sensitive props to alter. (I have recommended to Dev to include all old MagiskHide sensitive props.)...

If you still want to try that, substitute Zygisk Assistant for Shamiko in method I gave... If it doesn't work, install old MHPC module in addition (no need to configure; it adjusts all old MagiskHide sensitive props by default)... Advantages include keeping native print/props (Google account/Find device will see proper device fingerprint etc), and when Clark print gets "banned" you'll still be laughing with your native one... Why play that game when you don't have to? 😜 PW
[Magisk] ashish1989:
Well as I said Shamiko is breaking zygisk on my phone, I don't know why. With Zygisk Assistant everything is normal now and why play a new game when everything is working normally
[Magisk] pndwal:
I know... Just giving you the insight you may need to do it without PIF however... Zygisk Assistant + MHPC should be a working alternative to Shamiko... PW
[Magisk] ashish1989:
Ok, will install MHPC too now, thank you for the insight
[Magisk] pndwal:
But no point (redundant) if using PIF... It hides all sensitive props AFAIK. 🙃 PW
[Magisk] ashish1989:
I installed it anyways, as per your advice
[Magisk] pndwal:
If you did it with PIF enabled, I don't think you're understanding why or following the logic... 🤷 PW
[Magisk] pndwal:
Uninstall from Magisk App should be fine...

Restore Images will remove Magisk but configuration data incl modules will remain in /data/adb and used next time you install Magisk... App will remain too...

Complete Uninstall should remove everything.

Restore stock ROM with also restore patched boot image and possibly vbmeta (if verity was disabled) to stock thus removing Magisk but leaving config. files.

LineageOS update may preserve Magisk on your device if addon.d survival script is working... If you remove that, update should restore stock images but not configuration files unless you do a clean install (ie factory reset/wipe /data).

Note: This only works because LOS OTA's are full OTAs... Won't work for most stock ROM OTAs which are 'delta' as opposed to 'full', ie incremental 'differential' updates (only containing updated blocks, not full images) and require restoration of current stock images before OTA will work.

👍 PW
[Magisk] Rienquejefourretago:
A big thanks for the explaination i doesn't know the difference between complete uninstall and restore image before you explain

Why the config files survive the reinstall of stock rom/los ?

Maybe because when we install stock rom/los, the partition is not formatted ?
[Magisk] J.Michael:
Yes, the contiguration data is in a subdirectory of /data, so if you don't wipe data, it just sits there.
[Magisk] pndwal:
Welcome.

Because configuration files are in /data/adb... If you dirty flash ROM they'll remain but if clean flash (with /data wipe, /data format or factory reset) they'll be gone. 👀 PW
[Magisk] Spookymyo:
Is there a fix for not being able to hide the magisk app? Normally it's a simple process, tap hide, rename it, and done. But now no matter what I try, it keeps failing.
[Magisk] Nergal di Cuthah:
Hiding is broken in canary, should work in beta and stable.
[Magisk] markdewet:
Hi all, firstly I am not sure if this is the right thread, so forgive me if I am wrong here.

Ok, so I installed LineageOS 21, and Magisk on a SM-G955F.

1: Google Wallet simply will not work, no matter which Magisk module I install. I tried Shamiko (Play Store and Wallet simply would not open with that module installed). I currently have the playintegrityfix v15.9.9 and playcurl v10.6 installed , along with AutoPIF Next (FP Downloader seems not to work).

I also have YASNAC installed and the CTS profile match always fails. I am not sure if this is the issue why Google Wallet will not work but I simply cannot get it to pass. Any assistance with this would be greatly appreciated.
[Magisk] zgfg:
If using PIF Chiteroman - pls read his instructions and do not mess up with other modules (playcurl, autopif next), whatever

THERE IS ONLY A SINGLE ONE publicly available FP good for Device Integrity and Chiteroman PIF already installs that Sailfish prints with its pif.json

All your other modules will not provide you any different FP (all other publicly available prints are banned)- however, they may not up-to-date with the PIF v15.9 changes and pif.josn they install might not be read correctly by PIF module and you won't pass Play Integrity

Uninstall them, reboot and forget them - you will only need autopif.sh script from Osm0sis if you use Osm0sis PI Fork module insead of Chiteroman PIF (but autopif. sh will also pull the same Sailfish prints - however in the proper file name and format for PI Fork module)

Make sure you manually remove any json files that were installed by those modules and methods you used.

Then reinstall Chiteroman PIF and reboot

Also, forget YASNAC - SN was deprecated a year ago - please follow the PIF thread and find instructions there...

Test Play Integrity, you have to pass Device Integrity. Then, you will probably need to wipe Wallet Cache

However - you will find details in the PIF thread - maybe your Kernel name is banned and/or maybe your LOS is not properly signed - new reasons (new Google checks) that cause Play Integrity failing
[Magisk] markdewet:
Good day,

Thank you for your reply, however, as I am a complete noob to things like Magisk, I would like to request the following:

1: Could you please provide a link to the thread you reference about "PIF Chiteroman"?

2: How would one go about finding and removing said json files from my system? Can I use the File manager included in TWRP?

3: What integrity test app would you recommend to test with?

Thanking you.
[Magisk] zgfg:
Search on XDA to find Play Integrity Fix thread. Read few last pages there and find Most liked posts - that will lead you to FAQ and instructions , and pose further questions there

Since you use PIF module, go to Chiteroman's GitHub project and read also his I Instructions there

If you uninstall the mentioned modules together with PIF, they should remove installed files, but you can also check with root explirer like MiXplorer or with TWRP if preferred

However, it's becoming more and more tough to use Wallet, RCS, etc with unlocked BL, custom ROMs, root - some don't want to bother (every week or so something new comes, one must constantly be up to date, search, read and adjust) and they go back to stock and relock the bootloaders
[Magisk] markdewet:
If you are not willing to provide a new, inexperienced person with even the most basic of information, as politely requested, then I politely request that you offer no further advice or assistance.

1: His Github page shows NOTHING about what I requested.

2: I have found his XDA webpage and it is 700-odd pages. I am certainly NOT going to read all that.

Thank you.
[Magisk] Pixel86:
If you are inexperienced, then rooting/Play Integrity check mitigation is not for you IMO.
[Magisk] markdewet:
Wow, so in other words, do not bother trying to GAIN experience by trying new things??? What an antiquated ideology. I'm 62 and NEVER stop trying new things to gain experience.
[Magisk] zgfg:
Screenshot of my previous answer is bellow - did I ever tell you to read 700 pages?!

"If you are not willing" (your own words) to follow the head-start you were given (last pages, Most liked posts, ask PiF related questions there), then how do you expect the others will be willing to waste hours spoon-feeding you, and with that attitude - we will see 😁

Thousands were able to make their Wallets working by reading, learning and proper use of the PIF module, hence good luck
[Magisk] markdewet:
I NEVER once asked to be "spoonfed". Firstly, I asked three basic questions, one of which was a recommendation by yourself as to which integrity checker you would suggest to which I received no reply. (I do, however, see you have since edited your reply to respond to one of my questions, so for that I thank you.)

Secondly, while I do understand the value of doing a search, I have been at this issue for two solid days now and getting a little piqued at the constant failures. Yes, I realise that Google are constantly changing their goalposts and it makes it downright difficult for the developers to keep up. By the same token, it gets extremely frustrating when a fellow user posts that his phone is working perfectly with the same setup as mine, albeit a different make and model and my stupid Samsung cannot achieve the same result. Hence I sometimes just want to be able to click on a link and see a POSSIBLE alternative, new solution to the ones I have tried over and over again.
[Magisk] jons99:
how would you gain experience if you never root were you already a pro first time you root your phone?
[Magisk] zgfg:
You're welcone to help the guy

And how would he gain experience if he doesn't try what he was given for the beginning but wastes his time on arguing and so

Those who take a seat and start their homework eventually do solve their problem, gain experience and later help the community

Those who post endless questions, argue, etc, do not - at least, that's my experience gained from XDA
[Magisk] BarackMitzvah:
Dang... only one available FP? We're already almost totally SOL then?
[Magisk] Nergal di Cuthah:
Never sol xda figures a way
[Magisk] zgfg:
Only ONE 'publicly' available - meaning that all those methods will give you that single one, Sailfish

(Unless they give you the old, banned ones, Clark, Griffin, etc)

Install Chiteroman's PIF and open pif.json.

Install playcurl and check which FP it downloads from Xiaomi eu.

Run Osm0sis autopif script - you will get the same Sailfish from Xiaomi.eu

Yes, there are more private ones (but no more hundreds) but one must download build props from Net, test - depending on the sources, about 0.01-0.1% will pass

Xiaomi.eu last week wrote that all they had (200) were banned . Now they'share from PIF v15 9
[Magisk] jons99:
you are absolutely right and I think having a good attitude is the best way to get help I just don't like the way some people treat rooting your device as some exclusive club reserved only for the proest pros it's a very exclusive attitude and against what this forum is for I think
[Magisk] vMAC:
Interesting, I didn't know it was broken in latest canary. Would this be why I'm seeing the following in my logs?

--Magisk Logs---
81658d45 (27002)

06-21 23:57:49.502 878 878 I : Magisk 81658d45(27002) daemon started
06-21 23:57:49.504 878 878 I : * Device API level: 34
06-21 23:57:49.514 878 880 I : ** post-fs-data mode running
06-21 23:57:49.514 878 880 I : * Mounting mirrors
06-21 23:57:49.544 878 880 I : * Initializing Magisk environment
06-21 23:57:49.553 878 880 I : * Running post-fs-data.d scripts
06-21 23:57:49.555 878 880 I : * Running module post-fs-data scripts
06-21 23:57:49.556 878 880 I : * Loading modules
06-21 23:57:49.556 878 880 I : hosts: loading mount files
06-21 23:57:49.575 878 880 E : mount /debug_ramdisk/magisk32 -> /debug_ramdisk/.magisk/worker/system/lib/libzygisk.so failed with 2: No such file or directory
06-21 23:57:49.575 878 880 E : mount (null) -> /debug_ramdisk/.magisk/worker/system/lib/libzygisk.so failed with 22: Invalid argument
06-21 23:57:50.897 878 880 I : ** late_start service mode running
06-21 23:57:50.897 878 880 I : * Running service.d scripts
06-21 23:57:50.897 878 880 I : * Running module service scripts
06-21 23:57:50.922 897 897 I : zygisk64: replace nativeForkAndSpecialize
06-21 23:57:50.922 897 897 I : zygisk64: replace nativeSpecializeAppProcess

I wonder if this same bug is the same reason I'm having trouble with Lsposed installation?
[Magisk] Nergal di Cuthah:
Sorry no idea
[Magisk] pndwal:
Should be OK with Debug if you still want latest officially built commits (or can try a CI build from actions; fix was pushed months ago)... Issue was with gradle. 🤠 PW
[Magisk] minmod:
Hi, Im curious can you test if your setup is still working for tng and rhb because 2 days ago I tried rooting my Pixel 5 because I cant access 5g and volte without 5g module. My setup was Magisk 27.0 stable, zygisk, tng on deny list, hidden magisk, PIF module and https://xdaforums.com/t/mod-magiskm...supported-countries-pixel-4a-5g-5-5a.4547909/ this 5g module thats all. I tried opening tng I had no problem but when I tried to log in it says I have breached their t&s so its basically useless I cant log in can you help me with this or maybe you already found a way to fix this error please share.
[Magisk] zgfg:
Currently Shamiko and LSPosed are not on the Alt-Repo (Fox Mmm app only connects to Alt-Repo):

Magisk Modules Alternative Repository

An alternative to Magisk-Modules-Repo with fewer restrictions. Now larger than the original! - Magisk Modules Alternative Repository

github.com

but some users who did put their modules to the Alt-Repo are pulling off now (unhappy with the host)

Nevertheless, once you have Shamiko and LSPosed installed, you will easily see in the Magisk app, Modules, from Update icon - icon will be no more grayed out and you could tap and read ChangeLog and update the module

It's only a problem that there are still many other modules, neither on Alt-Repo, nor that they were adapted for the new update.json in Magisk v24, to indicate the availability of their updates in the Magisk app

(Module does not need to be on any Repo for that update.json mechanism - developer can use his own Github project and his own releases there to make the updating mechanism work)
[Magisk] Prof_Shekhar:
You are right. No matter what I do, it simply wouldn't hide. Only creates a dummy app with the desired name and puts on the home page.

Also thought of migrating to 24.1 version by going for update route (direct install) but it fails due to unable to check signature) error.

I thoroughly checked entire data base using ADB for any traces of previous Magisk but didn't find any.

Just to ensure I deleted the entire OS alongwith the deletion of every bit of data on the handset, reinstalled the fresh firmware with the Magisk patched file vía ODIN. Reinstalled the Magisk 23.0 again. Regained the root but still not able to hide the Magisk app or upgrade to 24.1.

Super frustrated now.
[Magisk] DaOldMan:
Why upgrade to 24.1. Why install 23.0, can't install 24.1 alone ? What Samsung do you have ?
[Magisk] Prof_Shekhar:
I have tried to install 24.1 unsuccessfully twice in the past 24 hours using Magisk patch method. However, it fails every time giving error unable to check signature.

Now I shall try once more tomorrow for the last time to directly install Magisk 24.1 with a clean slate. Will update though highly doubtful about the success.
[Magisk] zgfg:
Frankly speaking it is a known issue that was repeatedly reported by v23 users since the day when v24 Stable was released

More important, solution WAS POSTED (sorry, I'm not using v23 and I'm not search engine to search for the others) and it had been repeated couple of times to others who asked the same - it was about setting the Update channel to Custom, pointing to json for v23 Stable (exact URL was also provided in the solution post) - check in this thread and the old Magisk general thread
[Magisk] Prof_Shekhar:
Thank you for showing me a glimmer of hope.

I'll uninstall the Magisk 23.0 again, try to root with 24.1. Hope I am as lucky as you were. Even, I am also using two devices, one to keep all financial apps and other for all other apps.

Thanks once again to all for keeping my moral high despite multiple failures in installing Magisk 24.1
[Magisk] szazs89:
Be aware if you try to update from version 23, then the app might need to be installed with NO internet access. (IMHO, when you have internet access you cannot hide the app itself -- for 22.1-23.0 versions)

See my earlier post.
[Magisk] digger16309:
Thanks to everyone for this thread with all of the easy-to-follow instructions! On a Pixel 5 running A11, I successfully updated from (Magisk 23 + riru LSposed) to (Magisk 24.1 +zygisk LSPOSED + zygisk USNF) and I am passing safetynet with all bank apps working. No bootloops or lost data. :D
[Magisk] Syoenth:
Lsposed and Shamiko can be downloaded in Telegram

Lsposed: {Mod edit}

Shamiko: {Mod edit}
[Magisk] danbest82:
They can also be downloaded from GitHub if you prefer.

Lsposed: https://github.com/LSPosed/LSPosed/releases

Shamiko: https://github.com/LSPosed/LSPosed.github.io/releases

Edit: a bunch since nothing wants to work for me tonight...
[Magisk] pndwal:
Thanks for confirming that this works for you.

I posted the same suggestion but wasn't sure it would work. Reasons here:

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

Others might like to confirm this works, or if using proper JSON fixes app hiding... Seems from your previous post, improper link to latest stub has been an issue in earlier versions too... 👍 PW
[Magisk] DuskGolem:
Hello, I am trying to install latest stable magisk 24.1 on Galaxy A8 2018 running latest stock PIE rom (CLEAN INSTALL FROM ODIN) but I am unable to get even the core detected by the magisk app. I have tried installing using the in app patch boot image file method (direct install does not show up for me) and also tried installing from the recovery first by flashing magisk.zip and then installing the manager itself. Everytime I get the "INSTALED: N/A" in magisk app (magisk not installing or installation not being detected).

I don't have any installation logs at the moment (will provide later if needed) but I don't see any error on the console while installing, just a warning message when I try to flash from the recovery like this dude over here on github. Seems to me magisk is trying to install as system-as-root whereas uptill v23 it has been working fine for me without system as root. Any help will be appreciated. Also, i checked the init.rc file and for me there is no "persist.sys.zygote.early" in it.

EDIT: I will be trying to patch the whole AP.tar.md5 file from the stock rom zip and install magisk that way later today. I will report back any changes.

EDIT 2: Nada, just tried patching the AP.tar.md5 and still the result is the same, magisk app says "Installed: N/A" and I cannot enable zygisk since the option is not shown in the manager. My situation is the same as @Prof_Shekhar , installing v23 manager only shows v24.1 magisk installed but v24.1 does not work.
[Magisk] Oswald Boelcke:
I've removed the links from your above post. Telegram is not accepted as filehost on XDA.

XDA Forum Rules (excerpt):

Spoiler content hidden.

Regards

Oswald Boelcke

Senior Moderator
[Magisk] Prof_Shekhar:
Thanks. Will try it today after uninstalling Magisk 23 completely and applying Magisk 24.1 patched boot image. Let's see how it goes.

Today, reinstalled Magisk 24.1 using Magisk patched boot image file and ODIN.

Now if I install Magisk app 24.1, it doesn't show Magisk installed (screenshot attached).

However, if I install Magisk app 23.0, it clearly shows device installed with Magisk 24.1 but fails SafetyCheck.

Can't upgrade to 24.1 due to "Unable to check signature" error.

Now I think I have tried every permutation and combination, every possible hack to get Magisk 24.1 to work.

Still can't figure out why this unable to check signature error keeps cropping up. Have checked every nook and corner of the device for any possible remanants of any other Magisk app, but found none.

Does anyone know or has come across this situation ever in the past? If so, please suggest me a way out of this nightmarish puzzle.
[Magisk] xabu:
@Prof_Shekhar Wow this is great, you installed the Magisk Manager.

This is the most difficult part and then ..... the app won't update ?

Just click on update and be sure you have an internet connection....all must be fine then. (Reboot might be very helpful)

For safety net you need the fix. You should have read about it here in the thread.

Been in your settings yet ?

Don't give up now ...you are very close to the solution !!!