yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
There is no easy answer.

You might have some luck with a Magisk module named Hide My App List. You might benefit from something called Shamiko. Zygisk might help you.

You really need to read a lot of posts. This is a good thread to start with. Pay particular attention to posts by @pndwal and @zgfg.

Look for a post describing something similar. Do not ignore a post just because it does not name the specific app of interest to you.
[Magisk] kakashikeshu21:
I have magisk installed, with the zygisk, play integrity fix and Systemless Hosts modules, Shamiko I do not have it installed
[Magisk] zgfg:
Shamiko (or alternatively Zygisk Assistant) serves to hide Zygisk.

Zygisk dies not hide itself and many 'banking' apps will exploit that to detect Zygisk/Magisk/root/modded phone
[Magisk] Nergal di Cuthah:
It used to be magisk hide that enabled directv to work (i did a cursory web search) so I'd try shamiko. Some others said bootloader unlock was what caused (older versions of directv) to fail: in which case or in the case of it not allowing custom rom, you maybe out of luck.

Finally if you have an ad blocker (like adaway) turning this off to check if tv works might be advisable (with extra steps to getting it to let directv but still block others).
[Magisk] kakashikeshu21:
Directv works with Shamiko! Thanks!

I have a problem with the Max app (HBOMAX) using the same vontar x4 (s905x4) when I started the app and play any video no sound is heard, I have tried everything and it does not work, the only thing I discovered is that in smartvs In older ones you can not hear this app and in more modern smartvs you can hear it, apparently it is because the HDMI input of older smartv is not compatible with the audio of Max, if anyone knows how to fix it I would greatly appreciate it.
[Magisk] Nergal di Cuthah:
That's kinda out of the realm for this thread. HBO Max works fine on my rooted bootloader unlocked pixels.
[Magisk] casouzaj:
+1
[Magisk] leAndroid91:
I'm on Magisk 27.0 and have an issue when using the deny list.

I select everything i want to hide root for (for example Goolge Play Services but some others, too)

Then i delete cache & data for some apps (for example Google Play Services for Play Integrity Fix).

Then i restart my device.

After the reboot all apps and services are selected on the denylist EXCEPT Google Play Services.

I have to select them again after every reboot.

Am i doing sth wrong?

Thanks and regards!
[Magisk] tom1807:
You should not hide Google Play Services and it is not necessary.

If I remember correctly, this is standard behavior that Google Play Services is re-enabled, I just can't recall what was responsible for that.

Cheers

Tom
[Magisk] zgfg:
PIF removes GMS from DenyList. Mentioned probably also in the PIF GitHub Readme
[Magisk] anova93:
EDIT: feel like an idiot, immediately found the cause after posting this and going to read the Disable Flag Secure By Mehedi H Joy module further down. Leaving this posterity.

Hello, I'm experiencing a weird issue on my POCO F3 where flashing the magisk zip or the patched boot.img immediately breaks the power button function. By broken I mean that it cannot turn the screen on or off or activate the power menu but otherwise still able to power on from shutdown and works within recovery as well as unlock from the fingerprint scanner on the button.

Have tried base stable magisk 27, alpha and kitsune and deleted the module folder and magisk.db. Have clean flashed the custom rom I'm using several times and the button is fixed after reflashing the stock boot.img.

Another issue is that even if I try to live with this the phone will randomly reboot itself (straight to the google logo and skips the phone brand one) after about 12 hours of waketime and then the root patched revanced apps will be deleted (youtube and reddit) while root is still in place.

Since I've already tried clean flashing do I need to resort to even 'cleaner' methods of factory resetting and data formatting to get to the bottom of this issue?
[Magisk] leAndroid91:
oh good to know ... i thought blocking it is required to pass device integrity.

thx!
[Magisk] pndwal:
Well actually it is, but PIF follows USNF in doing the root hiding internally.

That's simply because HideList used to do it in riru-USNF till Magisk 23.0, but wilh 24.0+ while we got Zygisk we only had DenyList for a while and denylist mode used for hiding breaks Zygisk injection in processes which USNF uses to inject fake keystore into GMS DroidGuard/attestation (com.google.android.gms.unstable) process etc, so root couldn't be hidden from same (DroidGuard) process that way...

With hidelist mode hiding modules (that don't revert/deny Magisk modifications including code injection) like Shamiko, these can once again be used to hide root from GMS processes externally; it's only denylist mode (which isn't proper root hiding anyway) that breaks old USNF and new PIF. For that reason USNF and now PIF will only remove GMS processes if DenyList is enforced. If it's not enforced, hiding modules can be used instead of internal hiding.

One particular use case for this is where users have older systems font replacement modules installed. In that case USNF/PIF root hiding breaks system UI, but Shamiko Devs added a fix (allowing system to access to module font files again and not crash) in v7+, so adding GMS main and DroidGuard (com.google.android.gms + com.google.android.gms.unstable) processes to disabled denylist w/ Shamiko installed is beneficial in this circumstance.

🤠 PW
[Magisk] pndwal:
Moving this here:

Please say what you mean by this... Surely PE recovery allows you to flash .zip and .IMG packages?? No? 🤠 PW
[Magisk] pndwal:
Wow... Never heard of that restriction in a custom recovery... Wonder why they'd do that? 🤷 PW
[Magisk] sonek231:
I have no idea but also I don't wanna change it due to wipe all data and new ROM.

For all recovery developers, don't block this option! :)
[Magisk] casouzaj:
Sometimes, when I'm in recovery, installation from storage doesn't show up. Usually, with a new reboot to recovery, it reappears. Try it. If with one reboot to recovery doesn't suffice, do it again.
[Magisk] sonek231:
I tried few times and I didn't show up :(
[Magisk] Mister Floppy:
Hi,

sorry for the delayed response to your suggestions, but I have been ill and am still recovering.

To force the "BASIC" app to capture STDERR, I found out that appending "2>&1" does the trick.

If I enter your suggested command in the adapted "BASIC" program

ls -dl /data/data/android 2>&1

I'm getting

drwx------ 4 system system 4096 1970-05-07 00:09 /data/data/android

If I enter the killer command from Github

su -mm -c umount -l /debug_ramdisk/.magisk/pts/ 2>&1

I'm getting

umount: /debug_ramdisk/.magisk/pts/: No such file or directory

What I don't understand is, why su in this situation is still working in the adapted "BASIC" program:

If I enter any other SU requiring command, e. g.

getenforce

I'm getting

Enforcing
[Magisk] J.Michael:
I'm not clear on what you are doing and where you are doing it.

That "ls -dl /data/data/android 2>&1" was supposed to be a way to see that you do *not* have privilege. If I do it without "su" in front of it, I get "permission denied". Are you saying that you did it in the supposedly non-privileged shell but it let you do it?

From the permissions shown on the ls output, I don't think you should have been able to see it. Try "ls -dl /data/data" to see what that says.

Before entering the umount command, I would have wanted you to check the output of "mount". I have never seen any mention of "pts" in my mount output.

I think the real point of the exercise was to find an environment in which "su" works, see if that environment has the "pts" that somebody claimed somebody else had unmounted to break su, and see if you could duplicate the breaking, after first confirming that it even had a "pts".

So far, I don't think you've ever shown an environment in which su worked, and in which you needed to use su. You have a magic environment in which you don't even need su, and you have another environment in which you need su but you can't use it.

Have you considered my three suggestions for trying to clean the terminal emulator environment?
[Magisk] Untitled_neo:
Hello there,

I will be very pleased if you help me to understand.

I am trying to upgrade my magisk app from 22.0 to 27.0 on Redmi Note 9 Merlin MIUI V12.0.7. It throws me error "/dev/block/mmcblk0p34 is read only.

Next step I tried rename magisk.zip to apk and flash it with twrp.

But I have only stock Redmi-Recovery 3.0. Tried to flash unofficial, but doesn't work. Here I read that for my V12.0.7 will work this recoveries https://xdaforums.com/t/magisk-xpos...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/. But it is stock recoveries, which I already have.

Or I mixed up something.

Can you help me how to flash twrp and then update magisk.

Thanks!
[Magisk] J.Michael:
You are confusing me.

Did you really mean you are trying to update Magisk app? Just the app, not the part that was injected into boot? Why would you want to do this?

If you really want to update the Magisk manager app, it's just an app, you install it from within Android. Maybe you should unhide the current app, then uninstall the current app, before installing the new app. But be prepared for the new app to not work properly with the old injected-Magisk.

You say you "tried rename magisk.zip to apk and flash it with twrp". I think that's backwards. You download a "magisk.apk"; you might rename it to "magisk.zip" to flash in TWRP.

But I think you would be better off backing up and reconsidering.

Why do you want to update Magisk?

How did you install Magisk the first time? That procedure will probably work to install any version.

Where did you get the message "/dev/block/mmcblk0p34 is read only"? Can you tell me if that partition has a more familiar name, like "boot"?
[Magisk] pndwal:
I know some devices, eg Huawei, use read only /boot while booted and don't allow patching boot from system (ie. Direct install is broken)... Hadn't heard of this on an Xiaomi device however.

If that is the case however, you'll need to patch stock/unpatched boot.img from App, then flash separately per instructions for initial installation every time you update Magisk... Direct Install won't work...

?

TWRP too old for your ROM?... Or booted to system after flashing? (Normally must boot directly to recovery the first time to prevent MIUI from overwriting recovery.)

But I'd forget TWRP myself... Update Magisk App and try initial patch image from Magisk App...

👍 PW
[Magisk] BroSjX:
How do
[Magisk] Untitled_neo:
Thank for for the reply. I want to update the one injected Magisk. Because I have an app of 27 version and the img of 22.

sure. I just confused. I am going to rename *apk to *zip. But can`t find proper twrp.

Because zygisk is not accesable and I can not hide magisk from some apps on my device.

It was 3 years ago, as I remember I followed this instruction

[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

Preamble: After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85). The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG)...

xdaforums.com

But it is complecated and I am looking for a simpler one just to update.

Here
[Magisk] J.Michael:
I think @pndwal explained the "partition is read-only" message.

The most reliable path is repeating the steps of the original Magisk installation. Unhide the Magisk app, uninstall the Magisk app (in case this is one of the rare cases where there is a problem installing a new version on top of an old version), install the new Magisk app.

Please be very sure you are starting with the current, unpatched, boot image when you use the Magisk app to patch a file.

If you really dread following the steps that worked before, look at PixelFlasher. It's another set of steps to install it on your PC, but then it automates a lot of the steps of installing Magisk.
[Magisk] badabing2003:
Looking at those instructions, it uses fastboot to flash the patched boot, why are you using recovery to flash?

So much simpler to create a patch with the currently installed Magisk app, then try live booting with the patch, if it works, you can then flash it in fastboot.
[Magisk] RogerQea:
Where is the "Preserve force encryption" in Magisk27?

I am using a chroot linux on my cellphone, so it is important to to disable partition encryption to make sshd and many things work correctly. I see the option exists in Magisk source code, but I cannot find it / use it in the released apk.

Anyone could help me? Thanks in advance.
[Magisk] J.Michael:
Have you tried it yet?

I would guess that the encryption is a function of the operating system. If you have installed this Linux and there is no encryption, I don't think installing Magisk would change that.

When I installed Magisk on my Samsung tablet, I thought the notes said that one of the required data wipes was to reformat /data without encryption.
[Magisk] Mister Floppy:
Okay, I now see it was my mistake to have entered the su command before in the adapted "BASIC" program. If I do it without it, I'm also getting "Permission denied".

If I enter "ls -dl /data/data 2>&1", I'm getting

drwxrwx--x 374 system system 28672 2024-05-29 19:23 /data/data/

I tried all of your three suggestions for trying to clean the terminal emulator environment, nothing did solve the problem.

Regarding that on the Github website the guy who closed my thread for unknown reason has not reported back or she/he/another Github member has even commented my uploaded logs until today, I don't assume that the issue will ever be fixed.

So I finally decided to take the hard way of downgrading Magisk to v26.3 (Magisk v26.4 has another annoying untreated quirk, too, su requests are timing out when User Authentication is enabled). Now everything is working again.

I guess I will stick with Magisk v26.3 forever now. Upgrading to a newer version is not worth the hassle anymore in my opinion.

I really appreciate your support over the last couple of weeks, thank you very much again!
[Magisk] Untitled_neo:
Thanks, I remember it was painful to install initially Magisk. Is it better to roll back Magisk app to 22 version as my img? and for the Pixel does it work on Xiomi devices, in readme it is designed for Pixel™ phones and tablets?
[Magisk] Untitled_neo:
Thanks. I am not sure how to do it? Where I can find detailed instruction?
[Magisk] badabing2003:
Let's start with the most important part.

Do you know what firmware is currently on your device?

Do you have a download copy of it or are able to download the exact copy of it?

Alternately do you have unpatched boot.img of the currently applied firmware, or are you able to download it (it can be extracted from firmware in question 2).

Do you have access to a PC?
[Magisk] pndwal:
Assume means you have DEVICE_INTEGRITY...

Please say the app(s) so members with experience can help...

Generally, taken Hide the Magisk app? Have bank app in denylist (disabled)? Hidden all root-related apps (+ hidden Magisk App and Xposed modules) with HMA LSPosed module? Disabled USB debugging, OEM unlocking and Developer options? Removed TWRP and addon.d directories? Tried ZygiskNext?...

Since works on stock (assuming same Magisk, Shamiko PIF and dentist setup), it's likely that TWRP or addon.d are detected (also, ever had XPrivacyLua installed?) or some additional app installed is detected.

🤠 PW
[Magisk] anastasiszn:
this app is important for me https://play.google.com/store/apps/details?id=gr.cosmote.whatsup&hl=en

i have not install ZygiskNext and XPrivacyLua.

i follow all of your steps.

USB debugging, OEM unlocking its ok because i use nethunter.

must add play store and play services to blacklist?
[Magisk] CZ.Kostra:
I tried to install and it works for me with this:

Poco F5 pro + MIUI 14.0.28.0 (Xiaomi.EU)

Magisk Canary 27002 (hidden)

Chamiko 1.0.1

No ZygiskNext or similar

PIFork v8+latest Xiaomi.EU fingerprint

Device Integrity pass

No Google apps are on DenyList

I put the application on DenyList (I don't enforce DenyList).

Nothing else used.
[Magisk] Renate:
FWIW, getenforce is not restricted. setenforce is.

$ getenforce
Enforcing
[Magisk] tom1807:
Had a similar problem with my bank app.

After an update root was detected, the previous version didn't.

So I downgraded the app to the previous version and detached it from Google Play Store that it won't update or showing up as update available.

Maybe you have the same "luck"?

Cheers

Tom
[Magisk] pndwal:
👍

Someone may try for you... I can't ATM...

Don't install Lua!... May need ZygiskNext (ptrace+fuse Zygisk loaded)... Some apps detect inbuilt Zygisk (native bridge loaded)...

So removed TWRP and addon.d directories... Have HMA and LSPosed... Might have missed hiding some apps in HMA template... Some banks even find detector apps like Momo...

Does Nethunter have 'gadgets' for hiding USB debugging, OEM unlocking from bank apps??... Not sure I'd just trust that... and disabled Developer Options?

In HMA? or do you mean blacklist for Shamiko (ie. denylist)?... Anyway, either way No! and No!... 🤠
[Magisk] anastasiszn:
Can you tell me correct steps to install playintegrity and shamiko? First delete playstore and services data, next install modules and then apps to deny list? Try few methods but not working. A11 oxygen stock rom with magisk works perfect with same modules.
[Magisk] Vision:
I found a huge bug on A11.

Magisk latest Stable.

Every apps I have in DenyList, crash when dummy the boot-framework.art via module, and when remove it the apps start normal but detect the root.

Anyone else can confirm that?

EDIT: With zygisk enable happens this.
[Magisk] Stillhard:
Confirmed, A11 kitsune, SUList
[Magisk] Vision:
Thanks you.

Now, I try to found why happens this.
[Magisk] Stillhard:
Have you try disabling Zygisk? In my device, disabling it will make the system stable enough, a bit of lag still
[Magisk] Vision:
Thanks you.

This works.

EDIT: Now stop working 😂🤣

In you without zygisk or with, with dummy boot-framework.art via module and a app in MagiskHide, the app who add normal open?
[Magisk] Untitled_neo:
Thanks for the questions.

1. I have stock firmware Miui 12.0.7

2. Never did it.

3. I guess I downloaded boot.img from this forum when I first set root on my device.

4. Yes, I have adb installed on my Ubuntu.
[Magisk] awzx:
Guys what the settings and modules work for most banking apps for you?
[Magisk] casouzaj:
My current setup is official LineageOS 21 on Xperia 1 II, rooted by KerrnelSU, with PlayIntegrityFork v9 and latest Zygisk Assistant (for them to work, latest ZygiskNext). All my banking apps work, as well as MS Intune Company Portal. Wallet also works for contactless payments. Regarding RCS, although I see 'RCS with...' in some contacts, media contents fail to be sent.
[Magisk] awzx:
any way to pass device integrity without Zygisk enabled?
[Magisk] Vision:
Read this:

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com

[MODULE] Framework Patcher GO

Framework Patcher GO Based on chiteroman's FrameworkPatch, this module modifies framework.jar directly on the phone, to build a valid system-level certificate chain. This module is compatible with Magisk, KernelSU, and APatch. For more details...

xdaforums.com
[Magisk] awzx:
I installed the

Framework Patcher GO​

and followed the recommended propmat but nothing changed? and all apps for testing Device Integrity are not working now

Phone A22, Magisk Canary latest
[Magisk] Vision:
If you follow the instructions,

Do you have PIF fork script-only-mode and GMS.unstable on MagiskHide or Denylist?
[Magisk] awzx:
I meant to say I'm Magisk Kitsune Canary

Currently I have only FP GO enabled

--

I think I was having PIF by chiteroman, enabled but it say disabled 'cuz Zygisk is disabled
[Magisk] Vision:
Yeah, i have Kitsune Mask, with FP GO enabled and PIF fork script-only-mode and GMS.unstable on MagiskHide.
[Magisk] Iridule:
Not sure what's going on but even though I got the official debug the package name changed when installed and when I try the canary it fails to update. Does Shamiko still need the canary or debug versions?

Though I can report there doesn't seem to be any issues I've noticed. Was just curious. Is the hide app issue ever going to be fixed in the canary release?
[Magisk] badabing2003:
Did you download the firmware at one point? do you still have it? or can you still download it?

This assuming that you never updated / upgraded it since (rooting aside)

Do you still have the boot.img? it could be extracted from the firmware, assuming that you still have the firmware or you can download it.
[Magisk] NoobMonkey:
Anyway to get Google wallet working again? It worked fine until February-March, I think I was on LOS20 then.

I'm on OP 7T pro with LineageOS 21 (latest at the moment).

-Magisk 27 installed

-MagiskHide Props Config and UNSF by kdragon v2.4.0 mod 2.0 installed and enabled

-google apps on denylist

-Zygisk and enforce denylist enabled

-cleared the data in google apps, reboot but still not working.

The wallet spots that my device is rooted and for that reason it doesn't allow to add card on it. One other banking app is also detecting root (this started after banking app updated on Saturday). 3 other banking apps are working just fine.

Edit: Deleted props config and UNSF, installed PIF and got wallet working (although to one banking app doesn't but reading more to solve it). Still reading the PIF thread to get to back on track what Google changed etc. Thnx for pointing to right direction.
[Magisk] zgfg:
Please look to the proper thread about Play Integrity Fix, find FAQ post (look for the most liked posts of all time) and follow what you should do to get Play Integrity passing both Basic and Device Integrity - that is, what's needed for Wallet
[Magisk] samhhmobil:
It's written so many times here, as I cannot remember.

Again:

Both, MHPC and USNF, are dead! Really dead!! And both don't work anymore.

(Google does check PlayIntegrity instead of the old SafetyNet since many months.)

Uninstall both, and install latest PIF (PlayIntegrityFix or PlayIntegrityFork) instead.

Look in the PIF-Thread, and read that all from the beginning.

samhhmobil

EDIT:

Plus... disable "denylist enforce" and use the module "Shamiko" instead!
[Magisk] pndwal:
Just to be clear, MHPC has many uses and still works fine for systemlessly configuring/spoofing props globally... For instance, many still use it to experiment with prop settings to enhance ROMs, eg to improve/fix issues with audio (noise cancelling, volume etc).

Some of its options no longer give a complete solution like they once did, and most users wanting passing PI DEVICE_INTEGRITY no longer need it as PIF sets all the old MagiskHide (sensitive) props and more. However, users of devices launched with Android 7 or earlier and many later devices with broken keymaster implementations like OnePlus can still use MHPC's MagiskHide sensitive props function alone (with GMS in denylist) to achieve this... Alternatively they can use PIF-fork in scripts-only mode, Shamiko or other modules, but where any additional props need adjusting, users can still try/do this easily with MHPC.

👍 PW
[Magisk] pndwal:
This issue:

Can't hide the app v27002 canary app regression

#7921 by andigenn was closed on Mar 23... Fix is Android Gradle plugin upgrade:

Upgrade AGP to 8.3.1, JasonKhew96 authored and topjohnwu committed 3 months ago

... and

fix: AGP 8.3.X, JasonKhew96 authored and topjohnwu committed 3 months ago

... 27003+ is just a long while coming. 😉

... Very latest Shamiko requires Alpha fork IINW...

🤠 PW
[Magisk] Iridule:
What version is latest Shamiko? I am using version v1.0.1 and before that update it required magisk-canary but because of the Can't hide issue. I switched to debug.