yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Xiaomi Mi 9T, Xiaomi.eu stable, A11

Magisk cb436b17-alpha-2

Zygisk enabled, DenyList enforced and configured, SafetyNet passing

Riru installed (plus LSPosed and GravityBox-R)

Everything fine for all as above

---

Then I additionally installed Riru-Momohider and enabled initrc and app_zygote_magic

Both momo apo and Magisk Detector are enabled for DenyList

However, when I open momo app or Magisk Detector, it blocks for several seconds and then it crashes and the phone soft reboots

After that zygisk is no more active (although still shows as enabled in Magisk app).

As a result, SafetyNet fails

Upon full reboot everything is ok again, until I run momo app or Magisk Detector - then as above, crash, soft-reboot, and zygisk inactive again

Tested theee times with momo app and two times with Magisk Detector - always the same

Since I actually don't need, I uninstalled Riru-Momohider for now
[Magisk] rodken:
OnePlus 8 5G UW, OOS 11, A11

Magisk cb436b17-alpha-2

Zygisk 'No', DenyList enforced and configured, SafetyNet Not Passing

Riru installed (plus LSPosed, GravityBox-R, BusyBox, USNF, MHPC, and Universal GMS Doze)

Something does not 'jive' properly.
[Magisk] zgfg:
For Alpha builds with zygisk, zygisk must be enabled for DenyList and SafetyNet

If zygisk not wanted, then better use pre-zygisk Alpha versions (or Stable/Canary)
[Magisk] rodken:
Zygisk was enabled, but still displays 'No' on the Home page.

For now, I'll stick with version Alpha 'b6298f86'.

Each time a new build is release - I have no issues in testing to see if I will hit paydirt down the road with Zygisk.
[Magisk] Ayan Chakraborty:
Hello, i am using a port rom miui 12.5.2. Device poco m2 pro. After I installed riru and lsposed, I am getting SEPolicy not loaded. Is this a magisk bug? Where should I report this? And how to fix it?
[Magisk] Fif_:
Try flashing LSPosed over the existing install and reboot.
[Magisk] samsungFanboy85:
Can i please translsted to humsn what riru is Telling me i should do to fix xpposed right there... But 2 days 3 framewoeks later i still have one reboot and framework Isnt installed...

But good in bad found out there are 3 xposed flavors Not two and one i think on life support but plug is already out meaning rikka says edxposed no more supported
[Magisk] Ayan Chakraborty:
Tried that twice and twice more with riru core too. No changes
[Magisk] samsungFanboy85:
Ps wtf is parasitic lsposed jesus guys... Really good name choice...
[Magisk] zgfg:
Name was given by developer for v1.6.0:

Release 1.6.0 · LSPosed/LSPosed

Happy Chinese National Day! Changelog Parasitize manager into Shell as it is a system app to avoid detecting manager package name as the manager is not installed on the system! Fix crashes caused ...

github.com

Probably helped by Google translation

The point is that upon creating a shortcut, you can really uninstall the app
[Magisk] Fif_:
Mmm.

The LSPosed Selinux policies are copied to /metadata/magisk/riru_lsposed/sepolicy.rule on my system. Do you have such a file or any of the leading directories?
[Magisk] zgfg:
Did you try LSPosed framework instead of Dreamland (uninstall Dreamland first)

Also, which version of Magisk do you use - did you try with the latest cb4361b7-alpha-2
[Magisk] samsungFanboy85:
Yes lsposed goes like said in same fsshion... Post framework flashing reboot its working but modules need reboot too and tjen no framework... Un fact i see dreamland last lsposed for ladt 2 months had... Zero modules added or updated...

As for name... Awful sounding name... Even when chineese to english still it sounds as something bad is in ypur phone consuming lsposed poor thing...

Ok done jokes mode off here...

Does it will repeat if... Recovery reboot magisk unisraller swipoe flash

Repeat all from start update for mr magisk untill happy then riru then xposed then my modules choice... Between all rebooted yes yes....same will hsppen?
[Magisk] samsungFanboy85:
What does it magisk is broken onn this device.... What is the cause of this now totally lost track who what where magisk ? Riru? Xposed? Kernel se policy... Or happens all of them with knowlledge to help are lacking in english skill and dont understand ?

I Got this shortcut lsposed icon but app info shows settings app... That is that parasitic one? Can it be uninstalled no problem? Last time and i give up what is fix is there one do i put all this into chinesee and ask...Thank you all knowing developers for your vast knowledge shsred with users not smart enough

We appriciate any help u might provide but probably not... In other topic all out i got attacked for saying there is zero help anywhere but devs no commitment to user bla bla...

End
[Magisk] zgfg:
Make sure that you indeed have LSPosed manager 1.6.0 installed (install the apk from /data/adb/lspd), create shortcut and yes, you can then uninstall the app (I did, all ok)

But that will not help to pass SN or fix root, or whatever

Hence, no need to bother with that uninstalling the if you don't have a particular banking app or so that maybe finds the LSPosed mngr and bails out (declaring that your phone is 'rooted').

Only helping for that, absolutely nothing else

Like some apps find TWRP folder and/or some find Magisk mngr/app - that's why you then need to hide/rename/repackage Magisk app

Besides SafetyNet, there are various other 'methods' that certain apps combine together to detect (or guess about) root.

Some 'methods' are stupid bcs anybody (without Magisk) can install Magisk app or LSPosed mngr app, but that's the life
[Magisk] zgfg:
E.g, CustoMIUIzern is an app (actually XPosed module) that REQUIRES XPosed/LSPosed but it also uses a strange 'method' to detect if LSPosed is installed or not:

- If I install that 'parasitic' 1.6.0, create a shortcut and then uninstall 1.6.0 LSPosed mngr, then when I open CustoMIUIzer it complains that Xposed is not installed.

However, I click Ok, and I can still normally use the CustoMIUIzer LSPosed module

If I keep the LSPosed mngr 1.6.0 installed, then CustoMIUIzer does not complain - but in both cases it works the same
[Magisk] rodken:
I have such a file, but what are your suggestion(s)?
[Magisk] Fif_:
I ran out of suggestions. 🙁

I was asking about the sepolicy file because I've seen it missing or corrupted. It looks like the module is installed correctly.

Is there anything suspicious in the Magisk log file?
[Magisk] rodken:
Possible Error: 'Illegal Property Name' within the log.
[Magisk] mqbtcm8a4:
Is it possible to disable PIT-file verification on Samsung smartphones using Magisk?

I know that Magisk allows to patch a boot.img to disable system image verification. It seems like Sumsung is using the same verification method for PIT files, so I wonder if it is possible to disable this verification, so I can use my own PIT files.
[Magisk] Ayan Chakraborty:
Thanks for pointing this out. In devices where lsposed is working correctly, that SePolicy.rule file is there. I checked in OOS. But m2 pro with port rom was missing the magisk directory in /metadata. So I copied the files from a working phone to that one and rebooted. Still same condition😏

@osm0sis Please help

Okay Samsung doesn't have SEPolicy.rule in /metadata but still lsposed works fine🙃
[Magisk] donjoe0:
Where can I get this uninstall.zip for Magisk v20.0? Your link doesn't point to a file but goes to an entire forum thread where the word "uninstall" appears only in two very old posts that don't talk about any zip.

Context: I upgraded in-place from Manager v7.3.5 to 22.0 and then 23.0 and that seemed fine, except it didn't show my preexisting Magisk v20.0 anymore because of compatibility. Now when I try to direct-install a newer Magisk the process just hangs at the "Flashing boot image" (after patching supposedly succeeds) and my phone becomes unresponsive. I gave it like 30 minutes and it still wouldn't finish. All I could do was hard-reboot with a 10s press of the power button and then I was back where I started, with Manager 23.0 showing Magisk: N/A. So I'm thinking I need to wipe the old Magisk somehow before I try again.
[Magisk] dcarvil:
https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-uninstaller-20191011.zip
[Magisk] Didgeridoohan:
You already have the link, but for future reference the link I posted (2 years ago) still works. If you check the 1st post it tells you that everything is on GitHub, with a link. From there you can find the releases page and download the file you want from there.
[Magisk] zgfg:
If it would work in your case, there is Uninstall button on the main Magisk app window

Since v23, it is enough to rename Magisk apk to uninstall.zip, and it should work for flashing through TWRP for uninstalling Magisk (as described on Magisk Github)
[Magisk] samsungFanboy85:
Im not more riru or xposed needed as kill app button i learn to live withouT...and after Im no need for **** developer and his products with names like parasitic installer...

Do have one question...

If magisk hidden correctly, safetynet says fine all green, next no lucky patchers and other stuff is play store seeing that i have fingerprint from note9 but truth is s8.. Be anything done to be seen by play Other device Than s8

Not blocked yet twice meet this no is game hidden from me even see in store but xcom 2 just finger channge to s9 and there it is 27euro but wont try buy still not sure might be true s8 cant handle it... But now MtgArena i had already on device last patch see in store... Liall is important in end there was a lie And no more update... No answers and best part... Go to devs its them... Went explained i got game updated beyond store If u had wish for me and rest unsupported guys than u see account in game please ban If really it was your wish.. Guess what ? Nothing happen

But still now im scared of zero shield from now I know it lies from big tech company But why? Be eluding me at all so... Is it possible? Hide device i know u can do it in props module also found safetynet pass not hides anything and at most u can mask all you want and they see it anyway yet still choose not do a flip 1 Switch and Tommoroew all rooted and cina based enemies no more play services... So? Clarification please ?
[Magisk] samsungFanboy85:
Would you say text in red is law broken here if sure Of but no statement from wizards will be ever saying yes we did Or didnt Because expkained this already and may have some contract with g to not be possible deny that it was not them...

Its only this explaining why i can still be to able playing when i went and said my device isnt On supported lisT but pass minimum said list has below stated Also... My id They have no problem to if wish me gone is easy - ban On account .. Never came so conclusion is...Blocked by google cant only see why and why lies? Not them first srcond i knew it after seeing guys help me understand this...
[Magisk] samsungFanboy85:
Or prevent next block

now zero mask Not even hide magisk if i seen a interview somewhere with John Wu and safetynet he said is ready to purge all rooted devices like that switch on bye

and not sure be any sense if that is true then ... Why else hide? No real consecuences i could find beside no warranty for pixels...
[Magisk] samsungFanboy85:
Oh yeah one more... What is up with 0x1 folder working but was all over knox samsung and here 2day search hint how?what changed or again how u unblown my fuse? Semi serious first time asking but longer i cant see anything ... Bye
[Magisk] donjoe0:
Since Manager v23.0 isn't compatible with Magisk v20.0, I wouldn't expect it to be able to uninstall it either. Also, v23.0 doesn't have any Uninstall button on its main page anyway.

That is irrelevant for my case, I already told you I have Magisk v20.0.

The interesting thing now is that TWRP says the zip verification fails for the zip I saw linked above. Maybe I'm missing something about how this verification is supposed to work (like I need an extra file or some certificates?).
[Magisk] Didgeridoohan:
Disable zip verification in TWRP...

Usually the uninstall zip is backwards compatible. But, the v23 app will have an uninstall button if there's something to uninstall. Haven't checked, but IIRC v23 isn't compatible with v20 so it's not recognising that you have Magisk installed and won't display the button (someone will surely come by and correct me if I'm spouting nonsense).
[Magisk] donjoe0:
Well yea, that's why it's showing "N/A" and probably also why it's failing to upgrade it to a compatible version.

Next funny thing: flashed the zip, expected no change in the Manager other than no more warning that v20.0 is not compatible (as v20.0 should be gone now), instead what I got was: the Manager itself (v23.0) is also gone now. :ROFLMAO:

"Upgrading" across major versions of Magisk is always such a b****h, the instructions should just be honest and tell you straight up you need to uninstall completely and reinstall from scratch. Same thing I needed to do from v6 to v7 of the Manager, nothing worked when just pressing "Upgrade". (Maybe it's a LOS thing, I'm not even thinking of upgrading from LOS 15.1 after the horror stories I've seen around here.)
[Magisk] zgfg:
Wrong:

Magisk app (if Magisk is really installed and if Magisk app found it) DOES HAVE "Uninstall Magisk" right below "Check SafetyNet".

And that APPLIES also to v23!

(People usually make mistakes by not unhiding the old Magisk mngr/app before ibstalling the newer, and in that case the new one cannot find Magisk.

One must then go to Settings, Apos and manually delete the old, renamed Magisk mngr/app)

Moreover, uninstall.zip should work for the given but also for (some) older versions of Magisk as well.
[Magisk] zgfg:
Sorry, you complain about the names and translation, but please make your own posts readable and understandable by cutting the thoughts into sentences, separated by fullstop, comma and other appropriate signs.

---

If I understood anything from your post, maybe this can help you:

Model names and that kind of info is stored to props. You can use an app like SetEdit (search on Google Play) to read all props - see the screenshot.

If your system is not read-only, you could even write/change the prop values directly from the SetEdit app.

Alternatively, you can first dump all your props to a textual file, e.g. props.txt in Download folder by executing the following command from a terminal app - you will need to grant root to your terminal app when popped-up:

su -c "getprop > /sdcard/Download/props.txt"

Read the file and find the suspicious props you would want to redefine.

By using grep, you can directly search only for props containing particular strings, like:

su
getprop | grep s8
getprop | grep s9
getprop | grep note9
getprop | grep Note9

(PS: Actually you don't need root and su, just execute getprop .. commands as above from terminal app)

You can see from my screenshot how I find on my phone two market names (Mi 9T and Redmi K20) and the code-name (davinci) for my Xiaomi:

ro.product.model = Redmi K20

persist.sys.device_name = Mi 9T

ro.product.device = davinci

etc.

Once you locate the prop(s) you would like to change, you can use Magisk Hide Props Config (MHPC) module.

Search on XDA for the corresponding thread, read its OP post #1 with instructions about the installation and usage.

By that module you can redefine (or delete) selected props, or even add some new/additional ones (all in the systemless manner).

Be careful because you never know what for and where a particular prop might be used.

Even if your system is not read-only, you should better use MHPC (changing the props in systemless manner) than hard-coding the changes by SetEdit (or a similar app).

If anything goes wrong you wiil simply disable MHPC (and reboot) and you will be back to your original prop values as coming with your ROM.
[Magisk] donjoe0:
Yes, same here, forgot to unhide, but what I did after upgrading to the new one and seeing that it doesn't work was I uninstalled the new Manager and restored the old one from a TitaniumBackup. That seems to work at first, but only until the next reboot, after which all the modules disappear. As for deleting a renamed Manager from Settings/Apps, I see no strange app there that looks like a renamed Magisk Manager, so that's not an option.

To update on my previous direction: after flashing the uninstall zip the new Manager v23 also disappears, I run the Manager apk, it installs instantly, when I run it it warns me again that it can't detect Magisk versions older than 20.4 and will behave as if there was no Magisk installed (which suggests it's still seeing the Magisk 20.0 somewhere, which should be gone by now), and when I press to direct-install a newer Magisk it fails again just like it did before, by freezing at the "Flashing new boot img" step.

Next I think I will restore the Manager 7.3.5 from Titanium again, unhide and uninstall, because that uninstall says something about restoring the original boot.img, which might be necessary at this point.
[Magisk] zgfg:
I would never use Titanium backup to switch between previously used Magisk mngr/app versions

Magisk mngr/app stores only a very limited number of info (language you use, theme, update channel and so).

Only that will be removed when removing the Magisk mngr/app and only that will Titanium recognize as the data corresponding to the Magisk mngr/app

Everything else is stored directly at /data/adb in magisk.db (Magisk database), modules subfolder, etc - anyting there is not treated (uninstalled, backed-up or restored) as part of Magisk mngr/app data or settings

Moreover, Magisk itself is not in Magisk mngr/app, neither in /data/adb but in the patched (boot or recovery) image.

Hence if you want to properly switch between the (incompatible) Magisk versions, you would need to properly back-up/restore on all three sides
[Magisk] donjoe0:
OK, unhide + uninstall in the old Manager did something because I started having problems getting root permission for some applications, but I still couldn't install the newer Magisk version and also couldn't restore everything to the way it was before. And since I wasn't willing to use a PC connection and adb and fastboot etc. etc. just for what should've been a simple upgrade, I restored the whole system from my latest TWRP backup and I'm never touching Magisk's Update button again. It was working fine, I don't know why I even started messing with it in the first place.
[Magisk] pndwal:
New Editor-in-Chief for XDA... Hope John can still fill in the blanks...

Check John's Twitter for link to Mishael's Twitter posts...

I enjoyed many informative XDA News articles related to Custom Modding incl. Magisk over last 6 years (from Android 6 to 12) from the Ed. also...

Many thanks @MishaalRahman, and will look out for you tech pieces in future! PW
[Magisk] zgfg:
Turned back today to Riru-Momohider:

1) By enabling "isolated", Magisk Detector does no more find su in the path.

Strange thing, it does no more report if Magisk Hide works fine or not (without, it always reported that Magisk Hide worked fine).

Everything else is ok (root, Zygisk, SafetyNet, stability, LSPosed, etc) - hence I will keep that configuration (this was the first time for me to succeed masking the su in the path)

Btw, canyie on his Riru-Momohider page recommends against "isolated" but I was kicked to test with by a post on Alpha Telegram channel where the "isolated" option was also praised as good for use

2) I can not prevent Magisk Detector to detect the modified init.rc - even if I enable "initrc" for Riru-Momohider

3) By enabling "setns" in Riru-Momohider, my phone becomes irresponsive upon reboot (it took me 7-10 minutes for weather widgets to load, 3-5 minutes to pass SafetyNet, etc)

4) With "app_zygote_magic" I got system crashes when running Magisk Detector or momo app and upon (soft) reboot Zygisk was no more active

Btw, none of the four options for Riru-momohider make any help for the momo app - it still detects even that Bootloader is unlocked
[Magisk] markd89:
Hi, I have Magisk installed and working. However I want to install something from storage. When I do that, I see "No Items". I can't select the download folder.

I'm running Android 11/LOS 18.1/Edxposed/xPrivacyLUA. Magisk is not restricted.

What might I be missing?

Thanks!
[Magisk] zgfg:
It was mentioned previously that TJW stopped maintaining the Repo. For that reason, Magisk Alpha has no more Repo in the UI

You will need to find and download the modules manually (and install from storage) - and save it yourself locally for future
[Magisk] markd89:
I'm using Magisk 23.0 (21). I actually do want to install a module from storage, but when I do that it does not show any files. That's my question - how to fix Install from Storage not showing any files.
[Magisk] zgfg:
Ok, I'm no more running Stable or Canary (but mAlpha) hence I don't know if modules are still visible in Repo

If they are, you can take Dowload instead of Install (play with the icons), it will download to your Download folder.

Then, on top of the Modules window in Magisk app, you have Install from the storage option
[Magisk] J.Michael:
I'm not sure where you are, but your screenshot says "Recent". Maybe one of the buttons will let you navigate away from "Recent", and then wander to what you call "Storage". (What does the menu offer?)
[Magisk] dcarvil:
Install from storage shows no files for me either, but it shows additional apps that allow me to select a file. See screenshot. Android 11/LOS 18.1/Magisk 23.0/Pixel 3. I think the problem is you are not seeing the additional apps.
[Magisk] pndwal:
Good stuff!

This is actually better; no report means 'MagiskHide' (/'MagiskDeny') is not detected...

👍

Yeah, just saw those posts too... Not sure canyie 'recommends against', but notes pitfalls:

https://github.com/canyie/Riru-MomoHider#background

You may see 'init.rc has not been modified...' sporadically.

Canyie says this result is unreliable (detects 'init.rc modified' even when Magisk isn't installed!):

https://github.com/canyie/Riru-MomoHider/issues/12#issuecomment-907718098

Reflects my results running with Zygisk.

initrc is fine, but I hadn't previously tried isolated w/o setns...

👍 PW
[Magisk] markd89:
Great clue, thank you!!

Temporarily disabling XPrivacyLua in EdXposed allowed me to see those apps and install what I needed.
[Magisk] zgfg:
Yeah, I know that for you init.rc modifications are randomly detected and not.

But for me it's deterministic, Magisk Detector always reports init.rc modifications (and no matter what I tried with Momohider, Unshare or without them).

And believe me, I test SN, Magisk Detector and Zygisk/Riru Detectors every day, sometimes couple of times
[Magisk] BillGoss:
Tap on the hamburger menu at the top left of that screen. You can then navigate to your internal storage (in my screen shot it's OnePlus 8T, as that's my phone)
[Magisk] pndwal:
Have you tried when Magisk is not installed?

... Random / sporadic 'init.rc has not been modified' result may not actually be material.

Canyie seems be fairly certain his module is working to hide init.rc, and that "It's MagiskDetector's issue", stating that it returns 'init.rc has been modified by Magisk' when Magisk is not even installed.

Seems we simply don't have a reliable detector for this.

FWIW, I've only had Passed result for this a few times. IIRC, never when I was actively experimenting / rebooting; only after leaving it entirely alone for some time I'd notice it was suddenly saying 'not modified'.

When I cleared Detectors data and rebooted it was 'modified by Magisk' again and no intervention / efforts would restore 'not modified' other than leaving it for some weeks... 😬 PW