yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
See the section: Deployment in the official Magisk documentation. A system install is not supported and I believe would go against it's systemless nature.

Installing the apk as a system privileged app, I believe, is not supported for the same reason. I use a module: App Systemizer (Terminal Emulator) to do this for another app that has extra functions when used as a system app, but I don't believe the Magisk apk was designed with this use case in mind.

Why do you think you need to do this?
[Magisk] ManOfP:
I uninstalled Magisk and reinstalled via TWRP changing the extenstion from .apk to .zip. The 'Install' option is still there but the logs show a different set of results, not mentioning 'request rejected' as before. I'll attach a screenshot of the results below.
[Magisk] ManOfP:
I've redone the installation on the same stock ROM. I'll attach the results from the installation and logs. The logs this time are different without events indicating rejected requests.
[Magisk] pndwal:
Confirm says don't here:

https://www.didgeridoohan.com/magisk/ManagerIssues#

and here:

https://xdaforums.com/t/install-magisk-manager-as-a-privileged-system-app.3859637/

👀 PW
[Magisk] Artim_96:
Well, when you had both systmless (XPosed in v86.x), as least uninstall SuperSU from within the app, delete su.img in /data (when it's still there) and other stuff in root directory "/" that is called SuperSU or su from within recovery and at least flash your stock boot.img. That should remove all changes made by SuperSU... XPosed doesn't make that many changes since it relies SuperSU.
[Magisk] Jacob_K:
Changing DPI systemlessly

I cannot for the life of me get the script in the third post to work..

#!/system/bin/sh
setprop ro.sf.lcd_density 540

I save that as bootscript.sh, boot phone into recovery, mount system as rw

then

adb push .\bootscrip.sh /cache/magisk/post-fs.d

It still isn't changing the dpi.

I've even tried copying a whole altered build.prop into /cache/magisk/mount/system

Any help?

Running LG G4 H815 android Marshmallow, magisk v2, phh v2, 86.3 systemless xposed
[Magisk] topjohnwu:
May you post the /cache/magisk.log ?
[Magisk] Jacob_K:
I would do, but apparently this file does not exist..

Any suggestions as to how I can actually get a log for this and figure out why it's not working?
[Magisk] topjohnwu:
That mean Magisk is not running correctly.

New update should come soon, please try after the update drops, thanks :)
[Magisk] FPSUsername:
Do we need that other root method to be able to enable/disable root in magisk or will there be supersu from chainfire fixes?

Im curious if horizon go will work when root is disabled on a custom rom
[Magisk] KaMyKaSii:
[MENTION=4470081]topjohnwu[/MENTION] this is also valid for files that do not exist in system? And what are the necessary permissions for folders and files?
[Magisk] Artim_96:
... With the first question: do you want to ask if you can use that method to add files which you normally would put under /system, like apps that need to run as system apps? That would be great and I think it should work.

On permissions under /system: folders seem to be drwxr-xr-x and files -rw-r--r--. At least that's what solid explorer shows me.
[Magisk] gkillerx:
Android pay works! I'm a bit shocked though that horizon go (TV app) doesn't work it still sees xposed lol (using system less xposed and system less super user (the ss version)

Running Android 6 stock oneplus 3 ram
[Magisk] gohamstergo:
did you actually pay for something? adding a card means nothing. i doubt youll be able to buy anything with xposed enabled, seeing as OP has specifically said it wont work without disabling and rebooting.
[Magisk] KaMyKaSii:
Yes, add new files in /system as if they were actually there. I tried here with the GLTools app files but all I got was bootloop and an unreadable log
[Magisk] sansnil:
(deleted - apologies all, wrong thread post)
[Magisk] danielcr12:
Broken sensors.

yeah i had no time to get logs. here there are though. seems like the system is falling to initialize all my sensors, and cant change its satate. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] YzRacer:
Thanks for the development! Just want to share my experience:

Nexus 6P - Fresh update to August build

Flashed Magisk

Flashed phh's SuperUser with Android Pay Support

Installed phh's SuperUser app from Play Store

All seemed good, and while I didn't make a purchase I was at least able to add a card in AP.

I wanted to make some edits to build.prop (Tethering and HWKeys) so I created a script and added per the OP - Reboot

Changes to build.prop did not take effect. Magisk log showed phh's SuperUser script and my build.prop script listed, which I suspect means they attempted to run?

Attempted method 2, replacing the whole build.prop using /cache/magisk/mounts/system and this ends with not being able to boot

Deleted build.prop from magisk, and did the build.prop edits manually. I am not booted and everything seems to be working. I can add cards to AP, but will have to wait until I reach a store with AP to test a transaction.

This is farther than I was getting with SuperuserSU and systemless root, which as we all know isn't working anymore. I appreciate the efforts!
[Magisk] topjohnwu:
Would you share your script, and the location you placed them?

Also to replace the whole build.prop, you have to make sure the permission and se contexts are correct in the cache file you're about to bind mount
[Magisk] kraoc:
Hello,

I'm on i9505 LTE using JDCTeam Optimized Cyanogen 13 with Magisk v1 and Xposed v86.3 and phh superuser magisk v2.

How do I proceed to upgrade to Magisk v2 and Xposed v86.4 ?

I tried to:

- Full wipe

- Install rom

- Install gapps

- Install magisk v2

- Install phpsuperuser

- Reboot

- I pass device boot logo

- I go to rom boot logo and then I have a black screen

I need to hard reboot to recovery to re-flash all up to Magisk v1 and Xposed v86.3.

Am I doing something wrong ?

PS: I'm using Xposed for years and latest Magisk dependancy seems to open great possibiliyties but cause some trouble to me... :)

PS.2: keep working hard on it guys :)
[Magisk] FPSUsername:
Which error do you get with horizon go?

I get error 4101. I can't disable root with this app (supersu by chainfire) and I tried only with permissive and enforcing. Do you know if horizon works on a rooted device without xposed or on a device with a custom rom (with and without root, xposed)
[Magisk] gkillerx:
Yep same error, I fixed it by using the systemless xposed and disable it then reboot and it will work (even with root)
[Magisk] FPSUsername:
That's nice, it works with xposed disabled. Maybe somebody can write a module to fake xposed status for apps like horizon go
[Magisk] g2uzer:
**to remove Magisk restore your boot image, then delete / data/ magisk.img **

I restored my back up, rebooted to TWRP, file manager but I couldn't find Magisk.img to delete.

Restoring my back up automatically deleted it or im I looking in the wrong place?
[Magisk] jcrompton:
Thank you.....I should have mentioned that I had already done that from the beginning ....PoGo works but I've been trying to get SN so I can use AP (not that I use it that much .... I guess it's the principle of not being able to ....... I feel like I'm on an iPhone)
[Magisk] 09eric09:
The zip file that used to be linked in the OP?
[Magisk] Iradj:
Hallo guys

Can someone tell me why everytime when i reboot my phone that green screen with "Android is upgrading" appears did i something wrong ?

Samsung Galaxy S7 Edge

Magisk V8

SuperSu 2.78 SR1

Suhide V.0.55

xPosed 86.6
[Magisk] loserskater:
Add the xsetprop command to /magisk/xsetprop/post-fs-data.sh
[Magisk] knipp21:
Using android N on a nexus 5x running pure nexus and phh root.

Still failed SN and root stopped working until I deleted the module.
[Magisk] waylo:
It's harder to drill down to the cause on any non stock ROM, but few of us here on XDA are ever satisfied with stock[emoji6]

Agree, I don't use AP nearly as much as my efforts to get this to work might suggest, but it's the principle of the matter.
[Magisk] nkk71:
It's not supposed to survive a reboot. It's meant to override any property at any point in time (depending on the usage) without triggering a property changed event.
[Magisk] jcrompton:
OK. My thanks have reached a limit!

I just followed your instructions to a T except I didn't do the stock.IMG step because I couldnt find one that wouldn't boot loop with Res Remix N6 ..... And voila it worked!!!!

Thank you
[Magisk] requiiiem:
V4a magisk 2.5.0.5 dont work, Nexus 6 7.0 stock,.

Processing: No. [MENTION=4470081]topjohnwu[/MENTION]

Magisk v8 with phh su
[Magisk] putridfoetus:
/system/vendor/etc/audio_effects.conf is likely the culprit. It contains ”helper” functions that seem to only cause problems. Removing those functions made v4a work on my N6 running stock 7.0.
[Magisk] requiiiem:
in the version that is not systemless if I delete it works, but in this version also I have to delete it? I remember in the previous version of systemless not delete anything and worked.

Edit:

I delete it, still does not work. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] justmiike:
Does xSetprop v0.2 work with the Galaxy Note devices?
[Magisk] hungdinh1:
Just curious, are you able to login to snapchat?
[Magisk] qwerfaseeh:
All things are working fine for me like phh systemless root, magisk, systemless viper and systemless xposed

But i have problem with some apps which need root like link2sd, titanium backup, es file explorer they ask for root and i grant them but after granting root access there is error of device not rooted. ES explorer shows sorry test feature not working but Root explorer is working fine. I want to delete system apps but unable to do that

Android 6.0

QMobile Z14

Amogo OS
[Magisk] FreeTheWeb:
Sorry i never used this so i have no idea
[Magisk] voltaek:
Uninstaller ZIP not working

So I've been doing some testing that requires flipping between having Magisk installed and not installed, and I can never get the uninstaller ZIP to work properly.

Every time I run it from TWRP, I lose root completely, and re-flashing the SuperSU 2.78 SR1 ZIP from TWRP results in it failing at the "calling user ramdisk patch script" step of the flash. I have figured out how to get things working again, however, so I think it's just a matter of some cleanup adjustments to the uninstaller ZIP to do whatever it is I'm doing manually to get this to not lose root and also block re-rooting.

Basically, since I end up losing root anyways, when I go to remove Magisk I just remove both it and SuperSU root by doing the following:

1. Run the Magisk Uninstaller ZIP from TWRP. Don't reboot, though.

2. Use the TWRP file manager to delete these files: /data/su.img, /data/stock_boot_<lots of hex characters>.img.gz, /data/custom_ramdisk_patch.sh

3. Use TWRP to reboot to bootloader, erase boot and cache, flash clean stock boot.img and cache.img.

4. Use volume keys on phone to select to boot back into recovery, flash SuperSU ZIP, and boot back into system.

I think the main culprit is likely to be the /data/custom_ramdisk_patch.sh file not getting cleaned up, but I'm not sure about that, hence the full manual un-root and re-root.
[Magisk] wasim9283:
Magisk is active, and module of viper4android also but viper not showing anywhere?
[Magisk] ghitus:
Hi guys, sorry for the noob question, but how can I change the SElinux state under Magisk? SElinux changer doesn't work.

Thanks, Gaetano.
[Magisk] Artim_96:
Depends on your device. If you have a Samsung device you can't. At least not without flashing a kernel that supports that
[Magisk] Xanderace804:
Thanks for your reply. I already have the latest version of TWRP on my device. Gonna try reflashing the ROM now, but I guess I should just try a different one if that doesn't work. Will reply with my results later

---------- Post added at 11:27 AM ---------- Previous post was at 11:21 AM ----------

Thank you for your response!

I did wipe dalvik/cache twice, only to lose an hour of my life and have the problem continue =(

Looking for unsu.zip now before I try it again. As far as I know, root was built into the ROM I'm using but I'm not sure how they pre-rooted it. If running unsu.zip fails to alleviate this issue, should I try restoring the stock boot, reflash it altogether, or flash a different stock ROM entirely?
[Magisk] J.Michael:
Take a screenshot of the opening screen when you run the Magisk Manager app in Android.

Stop worrying about the "Install" button. Scroll through the last thousand posts in this thread to find where someone else posted a screenshot of the Magisk Manager app.

Here. The "Install" button is normal, and does not mean what you think it means. What's important is where it says "Installed:": If it identifies a version of Magisk, then you have already, and successfully, installed a version of Magisk. Stop trying to install Magisk until you can say what you think is wrong with your current installation of Magisk.
[Magisk] ManOfP:
I did what you advised and also checked the 'how to install' guide here on XDA. Everything seems to be fine now. Apologies for the rambling of the 'Install' button.
[Magisk] lolvatveo:
This happens for all users with certain models. such as for all j5 users, of course even if the installation starts with Stock ROM. Then i flashed supersu in twrp, it detects boot.img then patch & overwrites magisk patched boot.img in rom. then supersu can take root from boot.img on boot, and magisk can't. no matter how do I install, the current magisk version cannot get root. exactly is magisk can't get root from patched stock boot, supersu can. canyie's custom magisk version only allows magisk to detect patch installed, it has no root permission. old magic version like 18.0 can root without any problem.
[Magisk] lolvatveo:
can someone please tell me if zygisk deny list is similar to magisk hide list or not?
[Magisk] lolvatveo:
zygisk is supposed to be more powerful than magisk hide but it made 1 of my apps not run properly. i guess it doesn't hide root strongly, because while using magisk hide for this app to work i had to put it in the hidden root list and it can run successfully
[Magisk] ahpekriderzbmx:
Want To Ask?Before This I Use Magisk v23.. I Uninstall It Using Recovery.. Than I Flash Magisk Cannary.. Then After i Using Magisk Hide.. My Magisk Not Open.. It FClose.. Why?
[Magisk] pndwal:
If you already had root / working magisk, it is recommended just to install canary APK, then use Magisk, Install, select direct install within app (with update channel set to canary)...

There is NO MagiskHide in Canary since 23001... Do you mean Hide the Magisk app feature?

Did you previously have app hidden? Did you restore or remove it first? Otherwise it may still be there causing conflicts...check in device settings, apps for magisk app named 'settings' or a name you assigned... PW
[Magisk] pndwal:
Zygisk is NOT a substitute for for MagiskHide and doesn't hide root strongly or otherwise; It has nothing to do with hiding.

What it does is allow zygote injection and use of xhook like riru. By using these powerful functions hiding modules can potentially be more powerful / better equipped to hide just as modules for completely different purposes are made more powerful by use of Riru or Zygisk core functions.

Universal SafetyNet Fix and Shamiko are examples of powerful hiding using Zygisk...

We always needed to add apps that detect 'root' to hidelist... Now we need ta add them to denylist unless a 3rd party module does the hiding separately. (NB. Shamiko does this; denylist is NOT enforced and Shamiko simply 'hijacks' the list but preforms the hiding itself. The result is hiding better than former Magiskhide.)

Nb. denylist does preserve some of MagiskHide's functionality. PW
[Magisk] J.Michael:
Certainly, similar.

Based on what I've read in this thread, only a lawyer would claim there is a difference: Magisk Hide maliciously concealed information from a helpless app; Zygisk Deny helpfully removes from the environment things that might disturb a delicate app. Potato, zucchini.
[Magisk] pndwal:
Denylist preserves parts of Magiskhide & hidelist that don't 'manipulate ' non-Magisk signals (read spoof, subvert, substitute). So it still does 'portions' of the heavy lifting needed for hiding purposes.

The 'manipulating' parts needed are offloaded to the user (eg simply adding Google Play services SafetyNet process to denylist manually) or to 3rd party hiding modules (eg USNF, Shamiko).

Nb. What denylist does can also be achieved solely by 'hiding' modules.

www.twitter.com/topjohnwu/status/1445598597521633285

🤠 PW
[Magisk] traversone:
how can it be explained that on my S8 Hades ROM A10, although Shamiko is working without error, the root is not completely hided? Maybe Shamiko has some trouble with isolated process (in my app it is the case)? If switching to classic MagiskHide, all gets working 100%
[Magisk] pndwal:
Working with MagiskHide alone? Or with help from modules like riru-momohider riru-unshare etc?... I believe MagiskHide never effectively hid isolated process mounts / leaks... PW
[Magisk] traversone:
on latest alpha-3 (not working on armeabi-v7a architecture, as per my previous post), NO other module is needed to hide root to isolated process !!

on 23.001 canary official, i had to use unshare (or momohider) on the same ROM

edit: it frequently happens root is lost on this alpha-3 release, a reboot is needed
[Magisk] pndwal:
But you said working with 'classic MagiskHide'... You mean in Alpha w/ vvb2060's extra commits and w/ Zygisk off / MagiskHide on it works w/ zero modules installed?

Canary 23001 had classic MagiskHide (purely TJW approved) and you needed isolated process hiding modules as you said!

FWIW, it does seem shamiko performs better for some devices than others. Eg some can get completely 'happy' Momo detector (realme etc), but I haven't seen anyone achieve this on MIUI (I get several Suspicious traces no matter what)... unfortunately we don't have MomoHider for Zygisk. PW
[Magisk] traversone:
condition a) MagiskHide ON in Canary 23.001 --> Unshare is needed

condition b) MagiskHide ON in latest alpha-3 --> no other Riru-related module

condition c) Shamiko ON both in Canary 23.016 and alpha-3 --> root is detected from my app

on LOS 17.1 for Samunsg A3 and S4 Shamiko hides 100% and Momo is not happy

on LOS 18.1 for Samunsg S4 Shamiko hides 100% and Momo is 100& HAPPY!
[Magisk] Hot-Proton:
I get this. How can solved? I use latest Magisk Alpha 23016.
[Magisk] pndwal:
You're not getting a valid response with that checker... Try using YASNAC... Use Shamiko to hide Zygisk. PW
[Magisk] pndwal:
So hiding module IS needed w/ classic MagiskHide!! ... Possibly vvb2060 does something smart in his her 12 extra commits in Alpha (he she is king queen of detection, many bank apps utilising his her Momo methods 😶), or possibly some general fix has fixed some leak since 23001.

Are you saying app detects root w/ Shamiko / Zygisk even when Momo detects nothing?

Please say / link the app. 👍 PW
[Magisk] traversone:
"hiding module" (to me) was Unshare or Momohider needed in 23.001 but not more needed with alpha-3, of course w/ classic MagiskHide.

Same app (Sky Go Italy: it.sky.anywhere) works well w/ Shamiko /Zygisk even if Momo detect abnormal environment but only on LOS 17.1+. On Hades it fails hiding.

just for sharing I added the info that, on LOS 18.1, even Momo is happy with same alpha-3 configuration (of course root hiding is perfect!)
[Magisk] Hot-Proton:
i have install Shamiko 0.1.2-47 in magisk but Momo say found Zygisk?
[Magisk] pndwal:
Disable Enforce dentist per instructions. PW
[Magisk] Hot-Proton:
what you mean? i have only install the shamiko zip in magisk. there is no instruction.
[Magisk] m0han:
Disable 'Enforce DenyList' ;)
[Magisk] pndwal:
Ok, seems this may be an issue with ROM / kernel allowing leaks... (Hades is synonymous with DEATH, after all. 😉)...

Out of interest, I'm guessing you only get L3 security level for DRM Widevine in both of these Sammy devices?

So you are correct re. isolated process detection in SkyGo app. Specifically it detects the Digital Rights Management related VGDRM Helper service.

Nb. This service can.simply be blocked (working for a number of TV apps incl SkyGo):

- Download AppManager

https://github.com/MuntashirAkon/AppManager

- Open and check Services tab for your app, and block the VGDRM Helper service (click on the crossed circle icon) and click 'apply rules' in top (3 dot) menu.

- Thanks to @Longhorn87 for this solution! 👍

https://xdaforums.com/t/skygo-app-detected-root.4128933/post-84688731

Again, some later commit has likely stopped the leaks detected while using MagiskHide / Hades... Of course we won't see the effect in Canary even if commit is in common as there's no Magiskhide...

No idea why Shamiko solution fails per ROM either, except that it's effectiveness / mileage does seem to vary greatly accross devices / OSs... Some configurations untested / unaccounted for?

I'd be interested to see your Momo results for Hades ROM with Alpha / MagiskHide / SkyGo working, and w/ Alpha / Zygisk / Shamiko / SkyGo detecting... 😛 PW
[Magisk] pndwal:
Instructions were given with first preview release. See here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86052061

Instructions are also included with module zip archive; extract and view readme.md. PW
[Magisk] pndwal:
How are you settling props in MHPC?

USNF includes everything you need unless ArrowOS doesn't spoof certified itself... If it does, you can disable MHPC altogether; you don't need Force basic key attestation either, and this uses basic model prop mismatch trick which can cause issues... Sounds like it's a prop change that's triggering Compatibility Test Suite (CTS) profile match failure anyway.

Only if ArrowOS doesn't spoof certified itself use MHPC to set a certified fingerprint; that's probably what those you report are 'using pixel 6 pro props to pass CTS profile match' are doing in reality; ONLY a passing certified fingerprint needs configuring for CTS pass in addition to USNF changes. 🙂 PW
[Magisk] pndwal:
Latest Shamiko:

Shamiko-v0.1.3-51-release.zip

Translation: zh-CN-en

Alpha will remove magiskhide once all popular Riru modules have released zygisk version and magisk stable version has officially released zygisk.‌‌

https://t.me/magiskalpha/406

👀 PW
[Magisk] traversone:
no changes from my side, the hiding feature is still not perfect.

furthermore, they have removed some "module notification" (i.e. number of impacted processess or denylist enabled, etc..etc..)
[Magisk] traversone:
here you are.

Anyway, I knew and successfully tested the Longhorn's advice but I would have preferred a cleaner environment (and 1 app less in the system) !
[Magisk] lolvatveo:
why i already ROOT but i am still a restricted user?
[Magisk] zgfg:
Yeah, unfortunately that useful info is removed now

Yuko Yoshida only thinks she has won now (これで勝ったと思うなよ)

Yuko Yoshida

"Don't think this means you've won!"Yuko Yoshida (吉田 優子 Yoshida Yūko)/Shamiko (シャミ子) is the protagonist of Machikado Mazoku. She is a 15 year old high school student of Sakuragaoka High School who, one day, wakes up with horns and a tail. Upon learning from Seiko Yoshida that she is a descendant...

machikado-mazoku.fandom.com
[Magisk] zgfg:
How are you 'restricted' and where?
[Magisk] traversone:
Shamiko successfully hides root from Sky Go on LOS 17.1, even with MOMO status below. As said before, unfortunately it does not work on Hades ROM
[Magisk] Eng.Raman:
I have created a modified version of the latest Shamiko-v0.1.3-51-release.zip to restore this useful info but i can't share it due to the copy rights.
[Magisk] Master Cylinder:
Does the latest Canary build 23016 have the feature to test safety net? I have nothing to select to test. Same thing for me with 23015. What am I doing wrong?
[Magisk] zgfg:
Nothing wrong except that you had to pay attention to Release Notes (and what was discussed here) 🥸

SN checker removed, use some from Playstore like YASNAC
[Magisk] zgfg:
Nice idea
[Magisk] lolvatveo:
My case has been explained in https://xdaforums.com/t/editing-sys...and-flashing-our-modifications.4196625/page-4