yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
1) I just said / meant I believe it doesn't do any hiding itself... Seems it intercepts magiskhide settings and checkboxes likely allow you to set new apps / processes for hiding in AM UI, but MagiskHide still does the work / is needed.

I'm guessing here too; never got is working, probably because of incompatibility / lack of testing w/ Alpha in MagiskHide mode, but that's how it appears to work to me... If so it won't get us 'MagiskHide with the new Magisk'... And actually I do hope I'm wrong...

2) yup, actually I've noticed I can even stay in same screen; just minimise / restore (hit square 'overview' nav. button twice) and functionality returns to the expected...

And yes, as I mentioned I did delete all but modules in /data/adb and can save you the trouble, it doesn't fix... Seems something in app environment is skew-whiff... Guessing Installing standard (TJW) Magisk just may help, but suspect I need factory reset now... PW
[Magisk] m0han:
in fox mmm, when you click on the download link it

starts the installation process

, can't save the download. that's a (-), imho.
[Magisk] m0han:
i'm on the latest alpha. even after closing magisk app and reopening (and repeating this and even rebooting), i can't seem to get Configure denylist access
[Magisk] m0han:
i have run into a new problem. after updating to lsposed-v1.6.5-6315-zygisk-release (released on tg a few hours ago) and rebooting, i can't access the modules tab successfully anymore. when i tap on the modules tab, the app just closes. (i had disabled viper4android module for testing and now i can't enable it.) force-closed the app, cleared cache, rebooted several times etc., but to no avail. what can i do to rescue my device without losing my setup?
[Magisk] pndwal:
Zygisk shows Yes on home screen? ... What device / ROM? PW
[Magisk] zgfg:
Go to:

/data/adb/modules/zygisk_lsposed

and place an (empty) file named disable

You could use TWRP, Advanced, File manager

But since you don't have bootloop, you can do that by root explorer like MiXPlorer, then reboot

It will disable Zygisk-LSPosed.

Then you can uninstall it from Magisk app

(If you put uninstall file instead of disable file, then Magisk will uninstall the module on reboot)

This trick with putting disable or uninstall files is the same that Magisk app does. Then Magisk on next reboot disables or uninstalls that module
[Magisk] m0han:
yes. poco x3, aicp-19nov (a11)
[Magisk] zgfg:
Use Fox Mmm and Disable or Uninstall Zygisk LSPosed (and reboot)
[Magisk] m0han:
thanks, i'm aware of these steps. my concern is whether i would lose my lsposed settings and have to set up things from scratch.
[Magisk] zgfg:
If you uninstall Lsposed you will loose LSPosed settings

I don't know could you install an earlier version of LSPosed over that newer (without uninstalling first) and would it fix your problem
[Magisk] Lord Sithek:
the same here, and I noticed that the crash happens only when connected to the net, otherwise I can access modules list. Anyway, no big deal since I use FoxMMM and no issue there
[Magisk] pndwal:
Sounds like Magisk installation itself may be borked since it seems issues existed before you updated LSPosed...

You may want to try (assuming you still have working root):

- Uninstall / reinstall Magisk(Alpha) app.

- remove from /data/adb magisk, post-fs-data.d & service.d folders + magisk.db file and reboot to reset / restore magisk. - This will leave modules intact but you'll need to note / reconfigure superuser list, denylist etc. 😶 PW
[Magisk] yujincheng08:
It's Magisk's problem. I have proposed a patch to fix this issue: https://github.com/topjohnwu/Magisk/pull/5227
[Magisk] m0han:
not sure what gave you that idea. i said 'after updating....'

well, turns out it was lsposed-v1.6.5-6315-zygisk-release module that was at fault - at least for me. i removed the module, installed lsposed-v1.6.5-6314-zygisk-release and all is good. just that i had to configure gravitybox module from scratch. and, i'm richer by the experience. thanks everyone for your help.
[Magisk] yujincheng08:
Every single module can trigger this issue. It's Magisk's fault who cannot handle the update JSON correctly and crashes. It's LSPosed that triggers this issue. Your attitude is like fixing a bug by killing the person who found the bug. Bruh.

And simply delete the `updateJson` line in LSPosed's module.prop can fix this issue. No need to reinstall LSPosed
[Magisk] pndwal:
And I said 'issues'... You said

then

... so seemed you had issues before LSP update... sorry if not...

LoveSy's fix is likely the proper answer... PW
[Magisk] m0han:
whoa, whoa! hold your horses. i have no idea who 'found the bug'. i never meant to slight you or anyone else. in fact, i just reported my experience and i also thanked everyone who chipped in with tips/suggestions. btw, i'm not the only one who had issues with that lsposed-v1.6.5-6315-zygisk-release module. and, i'm not knowledgeable enough to figure out

it is a magisk fault

, to be able to comment on your attitude.
[Magisk] pndwal:
Thanks... I didn't have same module issue, but had denylist access issue described above and saw you built with very recent commits including "Allow modifying denylist without enforcement" of 4 days ago, so I installed your test build from artifacts here:

https://github.com/topjohnwu/Magisk/actions/runs/1719359020

this fixed my issues / allows denylist access any time... 👍

Nb. For those affected:

This test is most likely good for those w/ module JSON issue (can't access modules etc after installing a module) whether w/ late LSPosed or other modules...

I see John is also building your fix as we speak. 😛 ...

Probably VERY close now anyway! PW
[Magisk] pndwal:
As issue fix indicates, 3rd party module jsons can break Magisk. The real fix prevents these small code / script errors from killing Magisk functions... PW
[Magisk] m0han:
so, can it be inferred that 3rd party module lsposed-v1.6.5-6315-zygisk-release had

json that broke magisk

whereas 3rd party module lsposed-v1.6.5-6314-zygisk-release

did not

?
[Magisk] pndwal:
Yup... but such a formatting error could occur in JSON from any module as LS mentioned... Many modules are produced by amateur coders too ("script kiddies"?). These format (protocol) errors are very likely to be encountered by every module user sooner or later, and certainly shouldn't break Magisk itself...

Nb. A JSON is often only a means to point to URLs / files / release notes / doc's etc for module installation / updating etc, and in this case the LSPosed build is the first with a JSON supporting John's new "Support modules update" commit.

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

... formatting errors are probably excusable, possibly even inevitable on the first try. 😜

A minor formatting error is probably of no real consequence anyway, and no good reason not to use latest versions with bug fixes, improvements etc.

(LSPosed devs fix many Magisk bugs... don't blame the LSPosed build for what is really Magisk bug!.. Don't shoot the messenger... 😜 😝)

🤠 PW
[Magisk] zgfg:
I had some older version, 6303 or so, and there was no json line in the module.prop

Btw, just installed this latest 6515 and then deleted that last, json line from module.prop - no issue afterwards

(Alternatively, you can unzip 6515 and delete json line from module prop.

But then you must also adapt the sha256 checksum in module.prop.sha256 file.

Zip 6515 again and install)
[Magisk] pndwal:
... Or use the test build from LoveSy...

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

or John's brand new one with ALL master repo commits till now:

https://github.com/topjohnwu/Magisk/actions/runs/1722755293

until we get imminent TJW release w/ fixes and more.

Nb. This LSPosed build is the first with new JSON supporting "Support modules update" commit.

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

If you keep JSON intact you see update in magisk with 'Support modules update' and fix for JSON:

... Also, formatting errors are probably excusable, even inevitable on first try... 😜 PW
[Magisk] pndwal:
Latest Official TJW Canary!

Magisk (5f4cd50c) (23017)​

[MagiskInit] Fallback to default fstab if dt fstab contains errors

[MagiskInit] Skip loading Magisk when detecting DSU

[DenyList] Support listing, adding, and removing processes from the denylist regardless of enforcement status

[Zygisk] Add new APIs (not finalized yet, please wait for actual publication)

[App] Support user configuration of boot image vbmeta patching

[App] Add DNS-Over-HTTPS option back

[App] Restore the ability to install Magisk on the other slot on some A/B devices

[App] Partial module update checking support (not complete, still WIP)

[App] Many bug fixes

Diffs to v23.0​

[General] MagiskHide is removed from Magisk

[General] Support 64-bit only systems

[General] Support Android 12

[General] Update BusyBox to 1.34.1

[Zygisk] Introduce new feature: Zygisk

[Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes

[MagiskBoot] Support patching 32-bit kernel zImages

[MagiskBoot] Support boot image header v4

[MagiskBoot] Support patching out skip_initramfs from dtb bootargs

[MagiskBoot] Add new env variable PATCHVBMETAFLAG to configure whether vbmeta flags should be patched

[MagiskInit] Support loading fstab from /system/etc (required for Pixel 6)

[MagiskInit] Support /proc/bootconfig for loading boot configurations

[MagiskInit] Better support for some Meizu devices

[MagiskInit] Better support for some OnePlus/Oppo/Realme devices

[MagiskInit] Support init.real on some Sony devices

[MagiskInit] Skip loading Magisk when detecting DSU

[MagiskPolicy] Load *_compat_cil_file from system_ext

[MagiskSU] Use isolated devpts if the kernel supports it

[MagiskSU] Fix root shell if isolated mount namespace is set

[resetprop] Deleted properties are now wiped from memory instead of just unlinking

[App] Build a single APK for all ABIs

[App] Switch to use standard bottom navigation bar

[App] Downloading modules from the centralized Magisk-Modules-Repo is removed

[App] Support user configuration of boot image vbmeta patching

[App] Restore the ability to install Magisk on the other slot on some A/B devices

https://github.com/topjohnwu/magisk-files/blob/69888a73b561f9a8b103fb138dd032815e3c4259/notes.md

🎉🎊👍😋 PW
[Magisk] pndwal:
Latest Shamiko:

Nb. Only supports Magisk 23017+

# Shamiko

こっっ…　これで勝ったと思うなよ―――!!

[This ... I don't think I won with this --- !!]?​

### Introduction

Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

Shamiko read the list of apps to hide from Magisk's denylist for simplicity but it requires denylist to be disabled first.

### Usage

1. Install Shamiko and enable Zygisk and reboot

1. Turn on denylist to configure denylist.

1. Once denylist is configured, disable it to activate Shamiko

### Changelog

#### 0.2.0

1. Support font modules since Android S

1. Fix module's description

#### 0.3.0

1. Support whitelist (enable by creating an empty file `/data/adb/shamiko/whitelist`)

1. Always unshare (useful for old platforms and isolated processes in new platforms)

1. Request Magisk 23017+, which allows us to strip Java daemon and change denylist regardless of enforcement status

1. Temporarily disable showing status in module description (need to find a new way for it)

1. Support module update since Magisk 23017

https://t.me/c/1414270883/36746

Wow! Whitelist mode here! 😝👏 PW

👍 PW
[Magisk] traversone:
I cannot access this TG group!!!

I would definitely need this release...it seems developers have taken into account some discussion of ours here...
[Magisk] pndwal:
If you mean whitelist, I had a feeling Zygisk might overcome stability / other issues and allow this...

Others (associated with LSPosed groups / collaborators) likely had in mind Zygisk's power to revive vvb2060's experimental whitelist in Lite builds... PW
[Magisk] traversone:
I meant "Always unshare (useful for old platforms and isolated processes in new platforms)" as well...

but if vvb2060 does not release this version on this channel:

Magisk alpha

You can view and join @magiskalpha right away.

t.me

I cannot use it
[Magisk] pndwal:
... This is breaking Momo for me... at least w/ Momo in denylist.

May need new Momo... hope she's happier than the last! PW
[Magisk] Eng.Raman:
Shamiko-v0.3.0-72-release ( Github Direct Download LINK ).
[Magisk] pndwal:
Great share!...

https://github.com/LSPosed/LSPosed....c3006d6a62b3c1d2fcefe07/releases/shamiko.json

👍 PW
[Magisk] traversone:
same at my end..
[Magisk] vandyman:
I do not know what makes a Canary build go to a stable build. EX; Canary 23016 to stable v24.

It would make versions less confusing for new and intermediate users.

Maybe version 23017 that was released will go to stable V24.

Stable, beta, Canary, and 20+ alpha builds. Take your pick and hope for the best.

For me, I always used the Canary builds with the Pixel line up.
[Magisk] traversone:
I really want to thank all the Developers Team working on Magisk, Zygisk, Shamiko, etc..etc... this Canary/Shamiko releases SOLVE all the previous issues in my systems:

- Post-fs-data.sh error in some (not perfect/old Android 9) ROMs

- Magisk/Zygisk incomplete hiding in Hades ROM Android Q

- Boot patching error in some LOS 17.1+ with Am7 architectures

Really impressed by their competencies and support willingness!

Thank you!
[Magisk] pndwal:
This:

www.twitter.com/topjohnwu/status/1463404273186721794

But seriously, he still needs to address the general lack of support for real world devices. It's pitiful, and John is attuned to the desperate pleas...

www.twitter.com/tjh/status/1463405139763466247

Note to Bob the chicken from North Island NZ:

John will respond to reasonable requests only. For example, he's running test actions on a wide range of sofas as we speak in preparation for 24.0 Beta... However any suggestion of expanding compatibility to embrace animal companions will be taken with a grain of salt... 😁 😜 PW
[Magisk] vandyman:
Thanks.... Zygisk looks like the best way going forward. It is cleaner with less module clutter.
[Magisk] zgfg:
For the matter of fact, updateJson field is supported also in Alpha 23016 (latest, Jan 17)

Dirty test:

Since Alpha is not updated to 23017, I must use Shamiko v0.2.0 (59).

Hence I copy/paste updateJson from Shamiko v0.3.0(72) to /data/adb/modules/zygisk_shamiko/module.prop

Then Magisk Alpha apk correctly shows that Update for Shamiko is available.

I can take Install - it downloads and starts installing but correctly fails noting that new Shamiko requires Magisk 23017+ (mine is Alpha 23016). So far so good

BUT if I take DOWNLOAD instead, it downloads Shamiko v0.3.0(72) zip but then Magisk (Alpha) app always CRASHES

I've tested several times, Install and Download download the same zip to /Download folder, Install correctly continues with installation but Download crashes

I experimented similarly with my own module (I added updateJson to my module.prop and json file to my Github page), Install installs/updates my module but Download downloads and then crashes

Could somebody with Canary 23017 test that Download option - I don't know is this crash something specific to Alpha 23016 or general issue
[Magisk] Regys:
Hi,

I have an important issue on the security of an application.

In Magisk it is possible to make an application invisible to hide it from root.

But does Magisk make him only invisible or then he unooys the application ?

In other words, is the application secured ?
[Magisk] pndwal:
This is as expected; LoveSy 'Do not trust format of 3rd party json' fix is only two days old, committed yesterday in Magisk master and is not in last Alpha.

'Support modules update' PR was from vv module_update branch

https://github.com/topjohnwu/Magisk/pull/5216

and was that Alpha. See last commit here:

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

But because it doesn't have LoveSy fix, JSON with format issues will still break Alpha... 😜

Try today's new 761a8dde-alpha! ... It has an extra fix for showing Changelog too...PW
[Magisk] zgfg:
Did you please read my post and looked to the screenshots?!

Alpha 23016 did not break with 3rd pty json (if formatted correctly) and it installs correctly through the json (it downloads and instals the updated module)!!!

I said that if you choose Download only (not Install), it again downloads but then crsshes. Hence it has no problem with correctly formatted updateJson and json file (it doesnt crash when opening the Module page, doesn't crash when it has to find the module zip - it crsshes when job is done and the zip is already found, downloaded and saved

And it doesn't crash if it has to do one more step (to install the downloded zip).

It crashes only when you choose not to install but download only

Nevertheless, since you have that latest Canary, plese test Download only through the json. Supposedly, you have the latest fixes
[Magisk] Dr.][No_WaY:
Sorry

I tried to search for my q. ,but couldn't find answers.

I have note 20 ultra exynos and I'm on android 11 with one ui 3.1 and latest canary version 23001 f822ca5b which using magiskhide, I want to upgrade to android 12 one ui 4.0 stable release, can i use same magisk version that I'm using now through custom channel? Any limitations?Or it is not compatible at all? If yes ? Only new canary magisk 23017 with zygisk can be used? And update is in same usual way before through the app and batching process or need special steps?

Your help much appreciated
[Magisk] zgfg:
Did you try:

- Does it show Update icon based on json

- Does LSposed v1.6.5(6315) (latest from TG, that worked fine with previous Alpha) work with Shamiko (or reports incompatibility), and with which version of Shamiko

- Does the accompanying latest Shamiko v0.3.0(73) (published together today on Alpha TG channel) show the status

Asking for the 'second opinion' - I had all those issues and I had to go back to Alpha 76ddfeb9 (23016) with the accompanying Shamiko v0.2.0(59)
[Magisk] Eng.Raman:
Yes, it works fine with the latest shamiko-v0.3.0-73.

No, It still doesn't show the status, BUT I have fixed that by creating Shamiko Mod flashable zip v0.3.0-73 ( Fixed showing the status, screenshots attached ), Tested and worked fine with the latest TJW Magisk Canary build 23017 . :) (y)
[Magisk] m0han:
posting screenshots here; please draw your own inferences. don't get me wrong. it's just that i'm not entirely sure about what you're asking. i don't use systemless debloater (replace); couldn't find it either.

edit

: with the latest alpha, 'configure denylist' is accessible with/without 'enforce denylist' enabled.
[Magisk] dohanin:
What's the trick to pass all checkings in Momo? The closest I got is still showing "Suspicious traces • Bootloader unlocked". I'm using Stock Rom + Magisk 23017 + Shamiko + Universal SafetyNet Fix
[Magisk] traversone:
on official Canary and latest Alpha, when Momo is in denylist, it crashes on startup.

I remember it does not happen to me only
[Magisk] zgfg:
On your screenshot, Enforce DenyList is enabled - shouldn't be disabled when using Shamiko?!

For me, whenever I enable Enforce DenyList, then Shamiko reports it does not work - of course, for the versions of Shamiko where status works out of the box

(Maybe something is strange with your modding for the status)

Check by the old Native Detector does your Shamiko really work and successfully hides Zygisk
[Magisk] Eng.Raman:
I have uploaded 2 screenshots for Enforce DenyList status:

1. When Enforce DenyList is enabled: shamiko status shows [ Shamiko doesn't work since denylist is enabled ] , Momo shows: Found zygisk.

2. When Enforce DenyList is disabled: shamiko status shows [ Shamiko is working for 8 denied processes ], Momo is happy. ( which means zygisk not found )

Of course with Native Detector also "Zygisk not found" , I believe Momo is strongest than any other detection app.
[Magisk] zgfg:
Yes, but my point is - when I used Alpha 23017 yesterday night (I already reverted back due to all the troubles)

1) On my phone, Alpha 23017 DID NOT SHOW Update links based on json - however Alpha 23016 (last but one Alpha) does show and they work

2) I updated to Shamiko 0.3.0 72 and 73, but with either of them Zygisk LSPosed1.6.5 6315 (latest) DID NOT WORK - it reported incompatibility - as clearly showing on the screenshot.

I was able to make LSPosed WORKING ONLY with DISABLED Shamiko
[Magisk] Eng.Raman:
Switch to Canary. I'm on Magisk Canary since build 23016 and I doesn't have any troubles even with the latest build 23017 ( It shows Update links based on json, screenshots uploaded above in my previous post) , Also shamiko-v0.3.0-73 ( release one ) and LSPosed worked fine with it.
[Magisk] zgfg:
Ok, I'll try - my post yesterday evening was about the Alpha 23017 and issues there, hence I was puzzled when you quoted me and said that for you everything is ok

I was also thinking about Canary 23017 (nobody complained here since it was released), but I thought that Apha 23017 would be more or less the same as Canary 23017 (maybe with some newer fixes)

I will try if/when time permits (still happy with Alpha 23016 76ddfeb9) - I have now new pet (Xiaomi 11 Lite 5g NE) must go for unlocking BL, etc - you can imagine
[Magisk] Iradj:
Any solution for this little problem ?
[Magisk] Artim_96:
Suhide send to be the reason

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

Yes, trying from beginning could be a solution.

If you need a different ROM search this thread, maybe someone has already posted results to a ROM you can use
[Magisk] eberhardweber:
I don't want to derail the discussion, but is there currently a working update path from Magisk v7 to v8 for the Tab S stock MM 6.0.1. (chagallwifi)? One poster mentioned the need for a custom kernel, but didn't specify which one or whether this was true for Magisk v7 too (which I am currently running fine.). I tried flashing the backup stock boot image and then going through the standard install path (supersu, suhide, Magisk) in TWRP but the device gets stuck at boot. Anyone gotten lucky with this configuration yet? :) Would phh's superuser work (doesn't matter to me which superuser I use)?
[Magisk] lahceneamine:
Does anyone got Unicon to work with the v8 of magisk ?
[Magisk] Rhoban:
Magisk only installs the driver, not the app.

So you have to manually install the app.
[Magisk] edyny1:
Not sure why but I'm trying to uninstall xposed 86.2 but when flashed the unistaller is still there as active. I have tried a few times even doing it thru the xposed installer app and nothing, does not want to uninstall.
[Magisk] Artim_96:
If you tried the one from the OP, it's too new. You have to search it, the proper one was posted about 10-20 pages back or so
[Magisk] wasim9283:
Oh thanks
[Magisk] Papote3:
Check this out

http://xdaforums.com/showpost.php?p=68859212&postcount=23811

I even made it into a magisk module; just copied the xml file to SD card and deleted the "deep buffer" entries from all of them. Then I made it into a magisk module, so it mounts it systemless.

I didn't even change the SE Linux status

*I'm on the Nexus 6P running latest stock and now viper4android works on everything.
[Magisk] senthilrameshjv:
Hello [MENTION=1016795]loserskater[/MENTION], I am not able to root using magisk with Nexus 6p running 7.1.1. I did more than one time, and both the time TiBu and Magisk manager reports no root.

Here is what i did.

1. Fastboot flashed twrp and rebooted into twrp

2. Flashed magisk V8 from the official thread and the phh's superuser in one flash.

3. rebooted back to system and no root.

4. Flashed uninstaller and flashed SuperSu 2.78SR1. Bootloop.

5. Formatted data and flashed factory image.

6. Did steps 1 to 3 again and same result (obviously).

Can you help. I have no problem with safetynet pass as I dont use AndroidPay or Pokemon or Snapchat and other things depending on SafetyNet

All i need is root to disable ads and give root permissions for Nova double tap to sweep ;)