yashsingh1/xdaforums huggingface dataset:
[Magisk] katefrench:
Hi, Need help!

As soon as I reboot my device after enabling Zygisk from the setting it is going into boot loop and my device is not starting.

I am on latest version of Magisk and on a lolipop device.
[Magisk] Lord Sithek:
The problem is that you can't use Magisk app this way 😅 If you repackage Magisk app and then hide it with HMA, then you should be able to use it
[Magisk] xabu:
@pndwal​

Thanks for your patience and knowledge of this stuff. ​

I'll do my best to filter it all ​

in what might be usefull. ​
[Magisk] pndwal:
Did you install Via recovery initially? Then there should be no problem... unless Direct install (to update) set flags for Recovery mode if you updated this way since with Recovery mode set...

NB. Don't confuse flashing via recovery (legacy install method; you don't need it) with patching / flashing recovery image (installing Magisk in recovery partition instead of boot partition - needed for legacy SAR non A/B (type III) devices only). These are two completely different things...

Xiaomi have no OEM ramdisk in boot like other type III devices, but for some time Magisk has added a basic one when patching boot images to accommodate Magisk even when missing just in case this will work... Generally it won't as the bootloader itself is incompatible with boot-ramdisk, but generally Xiaomi type III devices (inexplicably) have compatible bootloaders and it does work... On many, Magisk in recovery ramdisk doesn't work anyway.

In view of this, you should have treated device as ramdisk = yes as John says in Installation Instructions, ie. you should have

deselected

Recovery mode and left it this way and flash boot image as for type I, II & IV devices, not recovery image! The Recovery mode setting sets flags to use special boot-via-recovery for magisk in Recovery ramdisk which is usually needed for type III devices.

So you could try simply Unselecting Recovery mode (in Magisk Install) and rebooting, but I think the flags to use special boot-via-recovery needed when magisk IS in recovery ramdisk are set while flashing, so you'll probably need to re-flash boot image with recovery mode properly deselected. 😜

Android device boot types:

https://topjohnwu.github.io/Magisk/boot.html

Magisk in Recovery / Special instructions for reboot System via Recovery:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Type III device exceptions (yours):

- Top of Installation Instruction page.

👀 PW
[Magisk] m0han:
Default app label in Apps Drawer is Integrity Checker?
[Magisk] zgfg:
There is a typo, it's named Play InteRgrity API checker

It's on Playstore but Early Access - to download find the post from 1nikolas in GPay thread
[Magisk] 1nikolas:
There is a typo on the full app name too? 🤦

I'm so bad.. I fixed only the playstore name. I'll fix that when I get back from vacation
[Magisk] m0han:
no typo in the label in apps drawer. @zgfg was probably referring to this post.
[Magisk] m0han:
light mode for me?
[Magisk] 1nikolas:
The light mode title is already fixed along with the playstore title but Google is painfully slow on approving stuff
[Magisk] m0han:
g00gle gonna take longer, eh? :rolleyes:
[Magisk] bacevs:
I just installed the latest fresh factory image (android 12) on my Pixel 4 XL.

Got rooted via Magisk v25.2 and have hidden Magisk app with fake name.

Modules installed:

MagiskHide Props Config v6.1.2-v137

Shamiko v0.5.2(120)

Universal Safety Fix v2.3.1

YASNAC is passing all two checks.

However all three checks in Play Integrity API Check have failed.

Note: Bootloader is unlocked.

How can I pass the checks in Play Integrity API Check?

Google Pay/Wallet is detecting root or uncertified software.
[Magisk] m0han:
why don't you try the mod version by Displax? install over old version. additionally, delete all google play services data and reboot.
[Magisk] bacevs:
I installed the mod version. However after installing i noticed i forgot to install my banking app "commbank".

After that google wallet is working fine.

However "Play Integrity API Check" still failing all checks.
[Magisk] J.Michael:
Did you put the checker and all bank apps in Magisk deny list, set Magisk to Not Enforce Deny List, and clear every cache you can find before and after rebooting?
[Magisk] bacevs:
Oh sorry, wasn't aware play integrity API checked had to be added to the denylist.
[Magisk] pedritopl:
Because it doesn't have to be there.
[Magisk] J.Michael:
Please elaborate.
[Magisk] zgfg:
Exactly as said. API checker calls GMS (Google Play Services) to execute the test, API checker by itself does not look for 'root'

SafetyNet/Play Integrity API is built-in to the GMS, and USNF tricks the GMS with the spoofed prints
[Magisk] J.Michael:
So what did @bacevs do, in addition to unnecessarily adding the checker to the deny list, that changed his test results?
[Magisk] zgfg:
IDK what somebody else does🤣
[Magisk] bacevs:
Nothing, all I did was add it to the deny list.
[Magisk] m0han:
This would have sufficed? Maybe @bacevs had this already done.
[Magisk] bacevs:
Nope, I hadn't added those google play services to the denylist. Just did now and removed integrity checker from the deny list and passing all but the last check. Not sure how to go about passing it.
[Magisk] zgfg:
When you use USNF, it removes Google Play Services from the DenyList

Below is the screenshot from

/data/adb/modules/safetynet-fix/post-fa-data.sh

that script is executed on each reboot

If you add GMS to your DenyList and reboot, GMS should be removed from DenyList after reboot if Zygisk is enabled and USNF 2.3 module is properly installed

It's because USNF is Zygisk module and it has it hardcoded in the native code to spoof GMS

EDIT:

It removes GMS only if DenyList is Enforced. But USNF nevertheless spoofs prints to GMS, by use of its native Zygisk code, no matter if GMS is in DenyList or not
[Magisk] m0han:
I don't know if it is due to my setup (I am using the latest Magisk Delta). I have 'Google Play Services' added to the Magisk Hidelist, but, MagiskHide is disabled. 'GPS' remains even after reboot. (Not sure if reference to forks are deemed OT here.)
[Magisk] zgfg:
MagiskHide is not the same as DenyList. The two are separated in Delta

Moreover, MagiskHide list is managed by magiskhide applet (no more supported in official Magisk) , while DenyList is managed by magisk --denylist

When you look into my screenshot - or simply open your own USNF module post-fs-data.sh, you will see the command magisk --denylist that applies to DenyList, not to MagiskHide list

I'm not even sure if --denylist option for magisk is supported in Delta, but you can test yourself in your Terminal
[Magisk] m0han:
Fox's Magisk Module Manager updated to 0.6.0
[Magisk] xerel89:
Again down, I can not connect to the internet...

Is it normal that it is down so often?
[Magisk] bacevs:
Does anyone else get 401 error on modules hosted on Androidacy module repo when clicking description button on the module?
[Magisk] martyfender:
Yes, I get that also.

I just tested again this evening and it is now working for me.
[Magisk] samhhmobil:
Me too...
[Magisk] martyfender:
I just tested again this evening and it is now working for me.
[Magisk] meric57:
Hello, on the post bacevs how to correct meets_strong_integrity and what to do.
[Magisk] maakosan:
I also have this problem. And if I turn Zygisk off Magisk reverts to 24.1.

Is there a workaround?
[Magisk] pndwal:
This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
[Magisk] maakosan:
It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).

I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".

No A/B stuff..
[Magisk] pndwal:
Very interesting...

So can I assume 7T has recovery_a/_b partitions as I believe 8T does, and that you also patched either recovery_a or _b in Magisk App some time back?

If this is correct, I'm guessing Zygisk-off somehow causes device to reboot to system via recovery, and you thus have old Magisk since you patched recovery image (which is also a boot image containing ramdisk of course) with that some time ago...

Note: Magisk in recovery and customised protocol for reboot via recovery to system w/o special adapted recovery key combo was designed for A-only legacy SAR devices specifically as these require Magisk in recovery partition as they have no ramdisk in boot... You seem to have used it on your 2SI device and there is no reason it shouldn't work apart from the fact that Magisk in boot partion is far more desirable / convenient...

If I'm correct about a/b partitioning in 7T, your modern 2SI boot type device will of course have ramdisk in 4 partitions, recovery_a and _b, also boot_a and _b... This is fairly unique as most 2SI devices use recovery in boot partition (w/ a hybrid ramdisk) and have no actual recovery partitions.

Again, if I'm right you can test theory by booting from powered down state using recovery key combo with this adjustment: As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. (If you wanted to boot into the actual recovery mode, you would long press volume up until you see the recovery screen.)

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Please reply to confirm (or correct) this! 😛 PW
[Magisk] Dr_Strangelove:
Hello friends .

I have a Redmi 9 (Global) Codename : Lancelot

Installed magisk via custom recovery (twrp and shrp) and root is sucess , but zygisk doesnt work , when I enable it in settings and reboot , in magisk zygisk : no . I used official MIUI 11.0.4. 11.0.7 11.0.9 12.0.1 12.0.4 Android 10 and zygisk still no success , although it worked on Lineage 18.1 Android 11 and Pixel Experience 12.1 Plus but I want to use MIUI and I want it to be MIUI android 10 to be exact because of some complexity of android 11 in Xiaomi devices I avoid android 11 . now back to MIUI 12.5.6 Android 11 to see if works at all or not , then I'm gonna try EEA or Europe MIUI Roms But before that I'm here to see if others have the same problem with their Xiaomi ? If yes , any fixes yet ?

Edit : Fixed by flashing latest Global MIUI Rom ,for almost a week I was looking for a way around Redmi 9 android 10 zygisk but was not successful . Switch to android 11 and it worked like a charm but I lost TWRP decryption , on Android 11 my internal storage is encrypted while in TWRP . Didnt try EEA roms though and will never Since I got what I wanted .
[Magisk] zgfg:
It's of-topic (TWRP and encryption) but:

- Generally, when switching ROMs, it's required to Format Data.

Don't know what exactly you did but you can try that

- Sometimes it may also help to experiment by switching between pin, pattern and no Android unlock screen setting

- Make sure you use the latest TWRP

- TWRP.me does not support A12 encryption yet. However, there are SKKK TWRP versions (for various Xiaomi models) that do support (beta development stage):

skkk/TWRP/A12 • AKR DL

dl.akr-developers.com
[Magisk] pndwal:
I think you just need to Learn to Stop Worrying and Love the Bomb. 😜 ...

The whole point is:

You didn't keep the Machine

a secret; You've told the world!...

... all is NOT lost!!!

In case you still want Android 10 w/ root (downgrade again):

Your issue is very similar to this (but root was lost also for some):

https://github.com/topjohnwu/Magisk/issues/6095

Fix just completed (by Canyie, who incidentally became an adult a few days ago! 😃 ); Affected Redmi Note 4 on A7, Realme 6 on A12, etc...

Root fixed here:

https://github.com/topjohnwu/Magisk/issues/6095#issuecomment-1207255175

Zygisk fixed here apparently:

https://github.com/topjohnwu/Magisk/issues/6095#issuecomment-1207369066

You could try the early test build linked there...

Fix merged in Magisk (still downstream of any releases) here:

52ba6d1 Don't let remote errors crash Zygisk

with a further fix merged for Zygisk loading in:

1735a71 Use ANDROID_DLEXT_FORCE_LOAD to load second stage if possible

You could try the final Actions run trial Magisk build here:

Use `ANDROID_DLEXT_FORCE_LOAD` to load second stage if possible

(build in artifacts .zip at end, need to log in to download.)

...Or just wait for next official Magisk release, most likely Canary...

🤠 PW

"I'm afraid I don't understand something. Is the Premier threatening to explode this if our planes carry out their attack?"

"No sir. It is not a thing a sane man would do. The doomsday machine is designed to to trigger itself automatically."

"But this is absolute madness, ambassador. Why should you build such a thing?"

"There are those of us who fought against it, but in the end we could not keep up with the expense involved in the arms race, the space race, and the peace race. And at the same time our people grumbled for more nylons and washing machines. Our doomsday scheme cost us just a small fraction of what we'd been spending on defense in a single year. But the deciding factor was when we learned that your country was working along similar lines, and we were afraid of a doomsday gap."

"This is preposterous. I've never approved of anything like that."

"Our source was the New York Times."

"Dr. Strangelove, do we have anything like that in the works?"
[Magisk] Vivek_z0o:
How to fix this A12L using magisk hide

magisk alpha
[Magisk] zgfg:
Edit:

Oops, if Magisk Alpha you should better ask in Magisk Alpha thread:

https://xdaforums.com/t/discussion-magisk-alpha-alpha-lite-forks-by-vvb2060-support.4424845/

Alpha is proprietary fork, closed source and they manage a close Chinese Telegram support group

Not many users here

Generally some different settings than in the official TJW, but supposedly they removed the old MagiskHide and in that case you should use DenyList the same/similar way as described in the OP posts here for the official Magisk v24/v25
[Magisk] Vivek_z0o:
Magisk delta ??
[Magisk] Vivek_z0o:
What about delta???
[Magisk] zgfg:
There are separated threads for Magisk Alpha and Magisk Delta.

Simply use search in XDA (top/right on the page) or google for eg: XDA Magisk Delta, and you'll find yourself both
[Magisk] bishoy ashraf:
no matter what i do i can't get all green (magisk deny list ,shamiko,hide my applist)

no twrp folder in (storage),all root app in the template...
[Magisk] zgfg:
Hmm, I always pass all (screenshot).

Make sure that in HMA template, you list Magisk app (I don't rename/hide the Magisk app), HMA module itself and all the other LSPosed modules you may have.

If you have deleted LSPosed app and you only have its shortcut - you cannot and don't list LSPosed itself

I have even the folder TWRP (storage) but renamed to TWRP.bak
[Magisk] bishoy ashraf:
so you say I can't use lsposed as a shortcut and reinstall original magisk app and add it into denylist?!(i added magisk with it's spoofed name).
[Magisk] zgfg:
I say that I don't (need to) rename/hide Magisk app, I just put it to HMA

And that if you let LSPosed to remove its app, there is no more LSPosed app and you don't put to HMA templste

If you keep LSPosed app, you must have it in HMA template

And you must have HMA itself in it's template

And I don't understand where do you have TWRP folder if not on storage. But I had simply renamed it to TWRP.bak
[Magisk] bishoy ashraf:
i don't know what i'm doing wrong,oprek still find magisk module,and now when check api i get this ,i want to mask magisk and lsposed from other apps like banking .
[Magisk] m0han:
check if twrp folder is remaining in /data/media/0/. if so, delete from there too.

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87018679
[Magisk] bishoy ashraf:
thanks 🙏 now i have only magisk module indication red hope u have any idea
[Magisk] Tech = Spy-Biz:
OMG from 2650 pages in old magisk thread to 112 pages in this new thread. Is there an option in xda to add a sticky post like in TGram that tells the visitor for example : Step1 through StepN to bypass SNet for bank apps? (sorry if I appear lazy)
[Magisk] 73sydney:
you appear lazy

most people manage to read the first page of the thread which gets you better than 99% of the way for 99% of people. The rest, and up to date fixes for any current or emerging issue (in any thread) will always be found in the last 5-10 pages, as makes sense. Dig in
[Magisk] Tech = Spy-Biz:
:p

uhh..its been over an year since but I still haven't used the device yet, my backs turned hump now, hurts too coz been just bending over on the PC screen and flashing this and that and GSIs and ROMs then reflashing stock factory image then TWRP for the hundreth time now maybe lol but I've still not managed to get the bank app to run :cautious:. Will it even work with an unlocked bootloader on samsung? maybe one last good try then I'll give up and move to Net-Banking instead perhaps. Magisk is a great program though. Any pointers would be welcome. TIA
[Magisk] J.Michael:
Have you checked the forums for the device?

Have you searched XDA for the bank app?
[Magisk] 73sydney:
No idea which device you have but as for Samsung, i run an S20+ 5G (bootloader unlocked etc) and have 0 issues with any banking app ive ever used. Just to give you hope. And giving hope goes against my central edicts....as does spoonfeeding :)

As for tips :

When in doubt, start with stock ROM....

The next could have been harvested from the last 5-10 pages...you should practice reading the last few pages of a thread, its a good habit as XDA isnt your own personal helpdesk where you only post when you have a crisis - without reading the room, because often its not just you having the issue, and we collaborate to fix issues....

You'll almost certainly need (along with reading the first page of this thread) this:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

Thats currently the best option to deal with the recent (as in last few weeks) change from SafetyNet to Integrity Check, and you should bookmark that thread for any future changes.

And you'll want to check you can pass this (top 2 out of 3 green is good enough)

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com

And thus you have reached the extent of my pity....i now return you to the normal programming from me, which is pure unadulterated indifference to the plight of man as a whole. Enjoy.
[Magisk] Tech = Spy-Biz:
I NVM...yup youre right I am a man ;)

Had done all that (safetynet-fix-v2.3.1.zip) and microG and GSI_certifier zip and spoofs & modules. I was trying 24.2 & 25.1 on Galaxy M21 2021 Edition SM-M215G Android 11 OneUI 3.1, It didn't work on Android 12 GSIs either (i mean bank apps didnt work), 25.2 bootloops so maybe I'm too tired of all this & don't want to install 5 different apps like lsposed & lua n stuff (lua & magisk together? how?) on my phone just to run a bank app when actually all these addon apps could easily spy from within my phone with root privilege on them.

I have a hunch that the bank app I'm using probably isn't even checking root rather its checking with the OEM servers on open BL devices list during device initialization , as easy as that because we have a Local Samsung Phone Manufacturing Plant in my country itself where M215G is also made, but thanks for your pity anyway I can still use 24.2 to add some modules and as for banking net-banking is available and quite secure with OTPs, enough headache with applying all this mods alrready, I can't probably give more time to android as theres other things to do. Thanks anyway. One year not entirely fruitless. I'll finally put the SIM-Card in for the first time in 14 months lol.
[Magisk] zgfg:
New theory. Never heard of (checking through the vendors side for users who had unlocked the Bootloaders)

Maybe they can rather use some Samsung API and check the real status of Knox on the phone
[Magisk] 73sydney:
Also running MicroG is just making your life harder, i will still never get why people want to introduce another level of possible fail....
[Magisk] Tech = Spy-Biz:
As far as I know (without xposed & other such modules on) It's most likely A SURE FAIL with microG on Stock OSes 9, 10, 11 if not GSIs but still people prefer to pm-uninstall built-in Gapps then install microG instead because they hope that a handful more of GSF- Dependent apps might agree to run with microG rather than not having both Gapps nor microG on the device which means GSF-Dependents won't run at all. In countries that disguise themselves as democratic but are really deeply autocratic by nature, introduction of systems like Guugle have already been devastating in many scenarios so the ones who are not in their governments good-books may even face danger or be forced to shut-shop.
[Magisk] Tech = Spy-Biz:
Maybe they do check knox even for ROMs that have nuked-knox but the prior scenario seems to be an easier and affirmative option for the banks logically speaking, also when I had 24.2 running on an A10 older samsung with the older version of the bank app running it worked flawlessly untill a month ago when i upgraded the app and suddenly the number of services within the bank app had jumped to 390 from mere 60-70 if i remember correctly and it refused to run, a few of the new services in the upgraded version seemed to be designed just to sniff out root, so i ran the same upgraded version on two phones of the same model (SM-M215G), one with just BL unlocked and original factory stock running and the other with Magisk 24.2 /25.1 + BL obviously unlocked but the bank app INSTANTLY detected jailbreak on the one with just the BL unlocked, thats raised my suspicion that the bank app had a method to check unlocked BLs too regardless of whether magisk was present or absent. It obviously detected jailbreak on the other one with magisk instantaneously but I knew that would happen coz I didn't follow this threads instructions and install the xposed modules etc. along with magisk. I tried it on a nuked-knox OneUI ROM and the result was the same.
[Magisk] Mepsipax:
Hey guys, here's a challenge for you. I've not been able to hide root from this app: https://play.google.com/store/apps/details?id=de.volkswagen.carnet.eu.eremote

It was working fine up until a couple of weeks ago when I guess an update happened that improved root detection.

Fortunately, it can be tested easily, because it immediately warns about rooted device when opening it for the first time.

My device is a Oneplus 5T running OxygenOS 10.

I've installed Magisk 25.2 via twrp for root.

Things I've tried to hide root:

- Installed the app "Shelter" to isolate WeConnect into a work profile that does not have magisk in it.

- used the Magisk setting to change its package name

- activated zygisk and put both WeConnect processes on the list.

- installed the safetyNet fix module

- reinstalled WeConnect to check if it's a caching issue

- deleted all magisk, twrp and rom zips from my device

I was successful in hiding root from my banking apps this way.

Now I'm at a loss what else to try and get it working.

Any ideas?
[Magisk] J.Michael:
Try without Shelter.

Are you enforcing Deny list?

Try Shamiko, stop enforcing Deny list.

Try Hide-My-Apps. (more involved setup, I think you have to make a dingus specifying the things, like Magisk, and HMA itself, you want to hide. Then a different dingus listing the things to hide from, like the bank app; and some reference to the first list.)
[Magisk] zgfg:
Instead of the old 'official' USNF 2.3.1, try with USNF 2.3.1-mod.

Look into the USNF thread and go through the posts during the last three weeks, posted by Displax

No guarantee that it would solve your case, but simple thing to try first (that version of USNF solves the problem for Play Integrity, that is replacing now the old SafetyNet)

That story about Wallet and Play Integrity is also about three weeks or so old, hence maybe concides with your app and its new/improved detection
[Magisk] Mepsipax:
Shamiko worked! Thanks, dude. You rock!