yashsingh1/xdaforums huggingface dataset:
[Magisk] ashish1989:
I also need to know, same problem with me too. And how to revert back to v26.1 stable?
[Magisk] westruk:
which device?
[Magisk] ashish1989:
Note 5 pro miui
[Magisk] Arcline:
XZ1 Compact
[Magisk] Spartacus500:
Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE

I don't see any differences in the new version, applications still detect zygisk...
[Magisk] sawdoctor:
I'm no expert and still absorbing all the information but if you need zygisk and need it hiding i think you need to use magisk alpha for now as official magisk isn't using NB yet. I do apologise if I've got this wrong
[Magisk] tramp20:
The same here on my old Sony Z1c.

After updating only the app complete Magisk is broken, I had to restore my TWRP backup
[Magisk] westruk:
Sadly, NB zygisk is also easily detectable in alpha. If it is indeed a native bridge of course
[Magisk] sawdoctor:
How about kernelsu? It seems to be gaining more and more support
[Magisk] pndwal:
Thanks for link!..

Confirming this won't seem to run with my setup... Strangely I can't get a shortcut to appear after installation either, but if I run immediately it crashes too...

Do you mean @Displax USNF mod build for MicroG? Did you check for Play Integrity deviceIntegrity verdict?... Nb. YASNAC isn't enough... Use Play Integrity API Checker etc...

Maybe others could try to run your linked 7.10.0 Telia build... 🙃 PW
[Magisk] pndwal:
Neither of these devices should be detected as Ramdisk = No... Are you (erroneously) seeing 'recovery mode' option in Install menu?; If so, don't flask/patch with it checked...

Only A-only legacy SAR (ie. A-only Android 9 launch version) devices lack OEM supplied /boot ramdisk and may need Magisk installed in /recovery ramdisk (ie. Recovery mode Magisk)... Your legacy ramdisk boot-type devices definitely support boot mode Magisk (magiskinit injected in a ramdisk in /boot partition).

I was going to suggest opening a Magisk GitHub issue for this strange behaviour, but I just checked and it appears a fix may be merged upstream already... A number of fixes for detection issues incl. LEGACYSAR=true/false, vbmeta patching etc here:

Fix device detection scripts and logic

topjohnwu committed 7 hours ago

... So hopefully this and other strange issues will be fixed with a maintenance update or Stable build soon... 🙂 PW
[Magisk] ashish1989:
Yes I have seen and checked that before installing. Now what to do?
[Magisk] J.Michael:
Do not check it.

@pndwal was saying you should not even see that option. If you do see that option, make a point of making sure it is not checked.
[Magisk] m0han:
But, having done that, what are the options left for him? I'm interested to know too. @pndwal

Spoiler content hidden.
[Magisk] ashish1989:
Me too
[Magisk] borisSweden:
Well Play integrity Check doesnt work because.....no Gapps, I only have fakestore. So the Token issue is still present. Funny thing is, I cen get to the child section and play kids shows but not regular TV.

About the Universal Fix, yes it Displax.

Well I think Telia like McDo uses install source as a check, Magisk Hide and DenyList has no effect on the app not finding out about root or bootloader. I will have to install Google Play Magisk to test my hypothesis. If it doesnt work, 6.0.1 is my only option and its broken as f because of React Native.

Edit: replacing Fakestore worked

GitHub - sn-00-x/fakestore2playstore: Replace FakeStore with (patched) PlayStore for license verification and in-app purchases with microG

Replace FakeStore with (patched) PlayStore for license verification and in-app purchases with microG - sn-00-x/fakestore2playstore

github.com
[Magisk] pndwal:
If you took direct install with this option checked, Magisk will most likely have patched your /recovery image (need to boot via recovery with proper key release timing to use Magisk in /recovery ramdisk)... If you tried again with option unchecked you will have patched latest Magisk to /boot image also...

Also, when unchecked, the app is also erroneously checking it again (depending on what is done in the app)... When this occurs and you reboot, Magisk will reboot via recovery to initialise Magisk in /recovery ramdisk, so you need to check its still not selected...

To fix this, you should restore unpatched recovery.img and ensure Recovery mode is unchecked (ie. installing normal Boot mode Magisk) if taking direct update again... Can also force configuration cleanup by deleting magisk.db file and magisk directory from /data/adb...

As mentioned, a fix seems to have been merged already for device detection issues... You could try this Beta again, but may be best to revert to Stable build (just flash patched boot.img and unpatched recovery.img) while waiting for next Stable or Beta... 🤠 PW
[Magisk] n.p.:
I have yet another device that Magisk does not work properly on (a Teclast T10 tablet running Android 7). In this case, Zygisk doesn't work. I have it checked (and rebooted a number of times), but Magisk (26.2) still says "Zygisk No". How can I track down the problem?
[Magisk] dipseeet:
i need help please!!!

this app here is not working anymore on my phone, it crashes when i open it

https://play.google.com/store/apps/details?id=com.wizzair.WizzAirApp

my phone:

samsung galaxy note9 crownlte

noblerom 2.c android12

magisk 26203

they updated their app and since then it's only(?) working without root

newest app version is 7.9.0

last working app version is 7.8.6

with root it's running without crash

but it asks me to update

this app is only(?) working with google play store installed

bcos when i tried to hide to update with HMA it complains about not having the store installed

would be really nice if sum1 could test if this app is working with root
[Magisk] westruk:
Works using latest magisk alpha + shamiko
[Magisk] shoey63:
No problem here

ROG Phone 3 (Omnirom 13 official)

Magisk Alpha 26103

Shamiko

App in deny list and deny list disabled

Play Integrity fix 8.4

Edit:

The following apps also tested and working.

- CIB

- In Tune

- Instapay

- 8 ball pool

- Uber Driver
[Magisk] J.Michael:
You say it works without Magisk but "it" asks you to update. The WizzAirApp? Did you update it? Did it stop asking you to update? Did you try installing Magisk after that?
[Magisk] borisSweden:
Is not using Google Play store imported OP? Just use the FakeStore2PlayStore module if you use Aurora store.
[Magisk] dipseeet:
:)

i try to explain:

WizzAir WITHOUT root

7.8.6 (works but needs to update)

7.8.7 - 7.8.9 (works but needs to update)

7.9.0 (newest version and works)

WizzAir WITH root

7.8.6 (works but needs to update)

7.8.7 - 7.8.9 (crash b4 it says to update)

7.9.0 (crash)

without root in every version before 7.9.0 the app opens and it says i need to update

with root the last version where i get NO crash when i open the app is 7.8.6

but i have to update

when i update i get constant crashes
[Magisk] dipseeet:
:(

i tried with shamiko and alpha 26203 but still not working
[Magisk] dipseeet:
i only use GooglePlayStore
[Magisk] ipdev:
Pixel 3aXL

Lineage 19.1

OpenGApps (Nano)

Magisk (26302)

-Renamed Magisk App.

Shamiko v0.7.3(174)

USNF v2.4.0 MOD_2.0

---

Installed from PlayStore and added it to the denylist.

It opens just fine.

If I remove it from the denylist, it crashes on opening.

All I have to do it add it back to the denylist and it will open again. 🙃

---

If you can not get v7.9.0 to work, then install an older version and hide it from PlayStore.

I use "Hide My App" to keep some apps from being updated by PlayStore.

[Hide My Applist - A Brief Guide] - [xdaThread] - Link.

- Post #235 is an example.​

Good luck. (y)

Cheers. :cowboy:
[Magisk] dipseeet:
:)

i appreciate all your efforts to help me

thank you very much

i have now version 7.8.6

and WizzAir is NOT on the denylist

and i get this message:

after i configured HMA

i get this message:

iam already using HMA to hide other apps i have

and it's working great

if i put WizzAir in denylist or not

the app itself is crashing from version 7.8.7 on

back then (couple months ago) i hoped it will be fixed after an update

4 updates later and it's still not working

i can post a log of the crash

no matter what version between 7.8.7 - 7.9.0 i use i will get the same fatal error in logcat

Generated by AppErrorsTracking
Project Url: https://github.com/KitsunePie/AppErrorsTracking
===============
[Device Brand]: samsung
[Device Model]: SM-N975F
[Display]: NOBLE2.CF_N975FXXS8HWF3
[Android Version]: 12
[Android API Level]: 31
[System Locale]: en_US
[Process ID]: 10055
[CPU ABI]: arm64-v8a
[Package Name]: com.wizzair.WizzAirApp
[Version Name]: 7.9.0
[Version Code]: 1973
[Error Type]: JVM
[Crash Time]: 2023-09-03T11:32:44.451
[Stack Trace]:
java.lang.SecurityException
at com.wizzair.app.WizzAirApplication.f(Unknown Source:2)
at f.c.onReceive(SourceFile:239)
at androidx.localbroadcastmanager.content.LocalBroadcastManager.executePendingBroadcasts(SourceFile:60)
at androidx.localbroadcastmanager.content.LocalBroadcastManager$1.handleMessage(SourceFile:12)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8663)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
[Magisk] simplydat:
Stop wasting your time on older version of of Wizz, you can't use it anymore.

Instead spend your time understanding why 7.9.0 isn't working.

I also tested Alpha 26201 + Shamiko 0.7.3, after putting the app in denylist, it will run fine without crashing.

You MUST have Shamiko, and you must DISABLE enforce denylist. You must also rename your Magisk app.

It's working for everyone else with the same setup. You have to figure out the difference between you and everybody else. BTW, I also have Play Integrity Fix.
[Magisk] tyler19820201:
I also use shamiko so if i disable denylist in order to get Shamiko work, it does not matter what is thicked in the denylist as it will be ignored anyway. Am i correct? 🤔
[Magisk] zgfg:
No, IT DOES MATTER, bcs Shaniko then reads the DenyList

And if your DenyList is empty it will not work

Pls, these are things that have been instructed/answered to other users many times, here or in other related threads. Hence when asking for help and when others provide instructions, please follow their them (and if something is not clear like this, search and read, to understand why they instructed that way). Cannot answer the whole Bible for every new question
[Magisk] tyler19820201:
I see....i have six banking apps now but only one does not work. Barcalys UK. The rest are working properly. I have shamiko lsposed module and Zygisk Lsposed module activated... DenyList disabled but the banking apps are all marked.

Anyway thanks for the info. 👍
[Magisk] dipseeet:
ok, thank you

i will try it again ... do i HAVE to use alpha or can i try with the new 26300 one?
[Magisk] J.Michael:
You are free to try anything.

A new version of Magisk is a good choice, it might work where others failed.

Failing that, why not try exactly what other people report works. Then ask how many things you can do differently. (But mention that you tried what other people reported working. And mention whether it worked for you. And if it worked for you, part with a few words explaining why you are determined to find a different solution.)

[Do a lot of reading. Alpha and Delta are not just other versions of Magisk, at least one of them puts a different spin on the problem, and it does not always make sense to just swap one Magisk with another -- sometimes there are specific modules that must also be changed, or the approach to hiding Magisk from other apps is different. Like I said, read a lot.]
[Magisk] pndwal:
If apps detect standard Zygisk (many do), WIP native bridge loaded Zygisk can bypass this with Shamiko hiding (bypassed for many banks but not all); Alpha showcases prototype developed in LSPosed Metagisk ATM... May be ready for TJW Magisk 27.0...

Need NB-Z for this one:

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

🤠 PW
[Magisk] n.p.:
Still have this problem with the 26.3 Magisk app. Whenever I start the Magisk app, I get the message:

"Requires Additional Setup

Your device needs reflash Magisk to work properly. Please reinstall Magisk within app, recovery mode cannot get correct device info."

Again, I have tried both "Select and Patch a File" and "Direct Install (Recommended".

Does some other installation method exist?
[Magisk] tyler19820201:
So if i am correct alpha can be used as magisk hide enabled and no zygisk OR magisk hide disabled and zygisk enabled. But only if zygisk enabled will use its native bridge? 🤨🤔
[Magisk] pndwal:
Yup...

Native bridge loading is what @canyie introduced for Riru and is hidable as it's memory is anonymous... Still needed RiruHide (inbuilt) to hide it... Official Magisk has no inbuilt root hiding, and Alpha has none with Zygisk enabled... Nb. Denylist is NOT designed for hiding root... It's a developer tool really... Proper root hiding is now done by third party modules, and Shamiko already supports NB-Z being from the same team (LSP Devs) asthat WIP... 👀 PW
[Magisk] tyler19820201:
Noice. I have got Alpha now with Shamiko and finally Barclays does work again. 😎

But Zygisk and Magisk Hide options should be next each other....So where is the Magisk Hide option?? 🤔
[Magisk] n.p.:
On the tablet I installed 26.3, but zygisk still does not work.

The install log:

Parsing boot image: [/dev/block/mmcblk0p7]
HEADER_VER [0]
KERNEL_SZ [6907780]
RAMDISK_SZ [2571708]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [7.0.0]
OS_PATCH_LEVEL [2017-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c4752e06b055ba9885ada108ab7bf25d912b40d7000000000000000000000000]
KERNEL_DTB_SZ [56332]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Target image: /dev/block/mmcblk0p7
- Device platform: arm64-v8a
- Installing: 26.3 (26300)
- Unpacking boot image
AVB1_SIGNED
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
Loading cpio: [ramdisk.cpio]
- Magisk patched boot image detected
Extracting entry [.backup/.magisk] to [config.orig]
Restore [.backup/fstab.mt8173] -> [fstab.mt8173]
Restore [.backup/init] -> [init]
Restore [.backup/verity_key] -> [verity_key]
Removed entry [.backup]
Removed entry [overlay.d]
Removed entry [overlay.d/sbin]
Removed entry [overlay.d/sbin/magisk32.xz]
Removed entry [overlay.d/sbin/magisk64.xz]
Removed entry [overlay.d/sbin/stub.xz]
Dumping cpio: [ramdisk.cpio]
- Patching ramdisk
- Pre-init storage partition: userdata
Loading cpio: [ramdisk.cpio]
Add file [init] (100750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add file [overlay.d/sbin/magisk32.xz] (100644)
Add file [overlay.d/sbin/magisk64.xz] (100644)
Add file [overlay.d/sbin/stub.xz] (100644)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Found fstab file [fstab.fat.nand]
Found fstab file [fstab.mt8173]
Remove pattern [,verify]
Remove pattern [,forceencrypt=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/metadata]
Found fstab file [fstab.nand]
Loading cpio: [ramdisk.cpio.orig]
Backup [fstab.mt8173] -> [.backup/fstab.mt8173]
Backup [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/stub.xz] -> [.backup/.rmlist]
Backup [verity_key] -> [.backup/verity_key]
Create directory [.backup] (0000)
Add file [.backup/.magisk] (100000)
Dumping cpio: [ramdisk.cpio]
Loading dtbs from [kernel_dtb]
- Repacking boot image
Parsing boot image: [/dev/block/mmcblk0p7]
HEADER_VER [0]
KERNEL_SZ [6907780]
RAMDISK_SZ [2571708]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [7.0.0]
OS_PATCH_LEVEL [2017-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [c4752e06b055ba9885ada108ab7bf25d912b40d7000000000000000000000000]
KERNEL_DTB_SZ [56332]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
AVB1_SIGNED
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [6907780]
RAMDISK_SZ [2580556]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [7.0.0]
OS_PATCH_LEVEL [2017-04]
PAGESIZE [2048]
NAME []
CMDLINE [bootopt=64S3,32N2,64N2]
CHECKSUM [78bf6b604d37518aaec8bcaae172b17ef41eafb6000000000000000000000000]
- Flashing new boot image
- All done!
[Magisk] Catani:
Can I get a little help here? My banking app has started to detect magisk after the last update. It's an Italian banking app Banca MPS . And since you can't really rollback banking apps I'm stuck...I have zygisk shamiko and magisk 26.3 . Everything has been working fine for the last 12 months or so
[Magisk] skia16:
Same situation for the same app
[Magisk] spicediablo:
After the latest update of Hong Leong banking app, it is detecting root even after adding to unmount list as well as hide my apps. Anybody knows the workaround?

Thanks!
[Magisk] WhoIsJohnGalt1979:
Magisk Alpha 26301, HLB Connect in Deny List, Deny List not enforced, Play Integrity Fix 8.4, Shamiko 0.7.3(174), HLB connect using my blacklist template in HMA, USB debugging disabled (temporarily). (this is my default catch all setup while testing any new app). Works fine for me. I dont use the app. Also, you can get success by using any of the above options or all of it together (thats for you to test)

@Catani @skia16 Same setup as above, the app works I think, I dont understand the language
[Magisk] spicediablo:
May I confirm if hlb connect version is 1.1.52? Is there anything I need to set in shamiko after installing it in Magisk?
[Magisk] WhoIsJohnGalt1979:
Yes that the version that I downloaded from the playstore. Shamiko works out of Deny list, there is nothing specific that needs to be done.Play Integrity fix helps you to take care of the google side of the story (play store certified, wallet etc) and then shamiko takes over with the rest in the deny list. Please dont add any google systems apps like gms or playstore in the deny list. Just wallet if you are using it (for it to work)
[Magisk] spicediablo:
Thanks again. I have installed shamiko and using magisk 26105,it is using unmount. I added hlb connect as well as disabled usb Debugging when hlb is launched(using Tasker).Added hlb in HMA too. I confirmed that I uncheck Google systems like gms or play store in unmount list. No luck still...
[Magisk] WhoIsJohnGalt1979:
Could you kindly try a different USNF the one by Displax v2.4.0-MOD_1.3 https://github.com/Displax/safetynet-fix/releases and check.

Also I don't see you using a lot of zygisk specific modules, you can disable zygisk and just use Magisk Hide->unmount modules and check if that helps with the the banking app, disable lsposed and safety net while doing that. People have had relatively better success with zygisk disabled for difficult banking apps. you wont be able to use google wallet but then its a toss up whether this bank app is more important or the former.
[Magisk] spicediablo:
Thanks. Finally it works after installing the usnf mod from the link you provided. No need to disable usb Debugging.
[Magisk] WhoIsJohnGalt1979:
Happy to know!
[Magisk] spicediablo:
Much appreciated for your help! I also tried disabling zygisk+play integrity mod. Most of my banking apps work except uob.
[Magisk] m0han:
Just an FYI

Spoiler content hidden.
[Magisk] Catani:
Thanks for the answer but it didn't work. Root was detected even after I tried everything you suggested. But your answer to another user about turning zygisk off and turning on magisk hide worked. Didn't realize the option "magisk hide" came back. It was removed a couple of years back and didn't really kept up with the updates since I use root mainly for ad blocking. Thank you... you've been really helpful.
[Magisk] spicediablo:
Hi,

Anybody faced touch n go app showing blank after the welcome screen? I have hid the app with HMA and using usnf mod 2 with the latest magisk delta 26301.

Update:fixed it by disabling shamiko. This means I need to enable shamiko when using some app and disable it while using others.. If you have any better ways, I'm all ears 😁
[Magisk] dipseeet:
:D

"you must also RENAME your Magisk app"

yesterday i was testing my 4 apps where i need to "hide" root:

S-PushTan

Sparkasse

Tan2Go

Wizzair

>> S-PushTan & Tan2Go <<

both are working with and without Shamiko

don't need to hide Magisk

at least they require a Module like PlayIntegrityFix or SafetyNet Sensitive Props

>> Sparkasse <<

not working with Shamiko

not working with hiding Magisk

it ONLY requires ENFORCE Denylist without any Modules

>> Wizzair <<

this fckng (sry) app is ONLY working when Magisk is hidden

no Shamiko required

no Modules required

no HideMyApp(ss) required

ONLY hide Magisk

:D

thanku a lot
[Magisk] skia16:
Can you show me the exact configuration of HMA? the banking app si checked in the deny list of magisk?
[Magisk] dipseeet:
:)

iam always reading on XDA since i had my first galaxy s2 ^^

i rarely post or ask something bcos here are already solutions or ways to bypass something and i could fix almost every problem i was facing with my phone and apps by only reading and understanding and try&error

this part with hiding Magisk i was honestly ignoring bcos i thought "no, this couldn't be the fix"

at the end this was the ONLY solution (for the Wizzair app)

i only tested now with

Magisk 26300

so i think no matter if aplha beta canary or delta

all should be working
[Magisk] dipseeet:
what is the name of your banking app?
[Magisk] skia16:
MPS. It stands for Monte dei Paschi di Siena
[Magisk] pndwal:
Turn off Zygisk and have a look... 🤠 PW
[Magisk] skia16:
Man...I have tons of apps that need to be hidden...how can I hide the apps? Even Google wallet needs zygisk and isn't to work...I can try but it will cause me a lot of other collateral problems
[Magisk] skia16:
I tried right now. It doesn't work and wallet and all other apps hidden don't work
[Magisk] pndwal:
Why do you want to hide apps?...G Pay/Wallet doesn't look for any apps, although some banks do...

You need to hide root from G Pay/Wallet and banks etc, also it requires Play Integrity deviceIntegrity level verdict... Clues in series of opening posts by OP... 🤠 PW
[Magisk] skia16:
Sorry...I use wrong words...I use the word hide because I refer to the old hide from magisk Wich now Is zygisk...as I said before I have a moltitude of apps that won't work without zygisk
[Magisk] skia16:
Here it is the list
[Magisk] zgfg:
Man, there are tons of similar questions and answers in this thread, Magisk General thread, USNF and Play Integrity threads

If user A asked and was given answer/it was discussed about hiding root from his app X, then user B should read that and try to apply and test similarly for his app Y

Nobody here have time and nerves to endlessly repeat the same instructions to every new user for his new app

New user B should take first his time to search, read, study, apply and test.

And then, if those 'known' methods do not work for his app, it makes sense for him to ask and for others to try to help him

Also, various apps use different methods to detect 'root'. For some, special forks of Magisk might need to be used. Hence please search also for your given app name (not just generally about "app"), if that particular app was already discussed and does that app require certain special or additional step

Only when general methods do not help and when no solution for the particular app can be found, then it makes sense to ask - but then also by providing the link to PlayStore that others could try with that specific app for which he already tested and found that standard methods do not help