yashsingh1/xdaforums huggingface dataset:
[Magisk] huskydg:
LSPosed released new Shamiko which fixed Found zygisk for latest Momo but the banking apps that won't run with zygisk enabled like Livin by Madiri still not open.

Magisk Delta is dead

You can view and join @magiskdelta right away.

t.me

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] traversone:
...ItsMe unfortunately still detects root
[Magisk] huskydg:
Shamiko only hide "found zygisk" for Momo 4.3.1, it cannot comepletely hide
[Magisk] pndwal:
Latest Shamiko Changelog

### 0.5.1

- Support Magisk 25+

Nb. Rikka has removed Shana's note stating "Some modules like "storage-isolation-enhanced" will reveal the existence of Zygisk", since release, so seems she's fixed issue in her Storage Isolation app enhancement...

Update shamiko_changelog.md

RikkaW committed 2 hours ago

👀 PW
[Magisk] huskydg:
Shamiko already cannot hide zygisk
[Magisk] Stillhard:
'The girls squad' attacked Rikka too now?

Go go power Rikka

Ponkles love Riru
[Magisk] pndwal:
Not sure how to test, but basic rule is Any launched with Android 10+ and Legacy ramdisk devices updated to/running Android 10+ and Pixel 3/3a series devices. Those launched with Legacy SAR (generally Android 9), apart from Pixel 3/3a series which were "retrofitted" by Google and the exception, are "stuck" as Legacy SAR boot type devices... PW
[Magisk] pndwal:
Aww... She's in the club for sure... Momo dev...

and remember Momo and Shamiko are rivals with secret wishes to help each other... Not going to delve any deeper into the mythology there though... There's plenty here to keep us occupied... PW
[Magisk] zgfg:
Sorry, I didn't decipher

It's Xiaomi Mi 11 Lite 5G NE, launched with MIUI 12.5, Android 11 - I didn't upgrade to A12, and running stock firmware (only Magisk and custom Recovery)

It's A/B device, with Recovery integrated to Boot, Magisk recognizes as Ramdisk Yes

2SI or not?
[Magisk] pndwal:
For sure! ...

With a number of exceptions, the 3 boot types are:

• Legacy Ramdisk, RV < Android 9

• Legacy SAR, LV Android 9

• 2SI "SAR"* LV > Android 9 & LV < Android 9 w/ RV > Android 9

Key:

LV = Launch Version

RV = Running Version

* If this is SAR is debatable... John Wu says it is 'for Magisk's purposes'. Some Google docs say it's a form of System As Root, others say it's not as Initial rootdir is rootfs despite Final rootdir being system. 🙃 PW
[Magisk] huskydg:
Rootfs -> Ramdisk Yes

A-only SAR -> Ramdisk No

A/B SAR -> Ramdisk Yes, 2SI (two stage init)
[Magisk] CrazyCypher:
Any changes in safetynet? I was able to Pass it today morning but after that I am unable to... I use HTC 10 with stock rom, ElementalX, Magisk v8, Xposed 86.6 and SuperSU with suhide. Also root switch latest version. Because it was not working anymore today I also installed xsetprop, but no avail.

Any suggestions?

Thanks, I appreciate it
[Magisk] Captain_Throwback:
If you were passing without xsetprop before, I'm not sure why you think you'd need it now. The log in Magisk Manager will tell you if it's actually doing anything.

But to answer your question, SafetyNet still passes fine for me. I'm just using Magisk & phh's Superuser Magisk module with Magiskhide enabled, though. I can't speak to your root/hide method.
[Magisk] CrazyCypher:
Weird, it seems I was unable to pass it because I've made cache magisk module to remove boot sound. Now that I disabled this cache module I can pass again :)

I have a module to remove system apps and there is no problem, but this one it seems it triggered something...
[Magisk] edyny1:
I have 86.2 installed as a system mode but don't remember what i did to make install as system mode. Can you refresh my memory please??
[Magisk] mew1033:
So I'm struggling here. All I want is root and Android Pay. Once I get that working, I might consider trying to get Xposed working.

Nexus 5X. Anyway, install Pure Nexus Rom, and safetynet doesn't pass. Then I install a kernel with the modified code here: https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5 Reboot and safetynet passes. Sweet.

Then I reboot to recovery, install Magisk v8 and phh superuser. Reboot and adb install magisk manager 1.2. I go into the settings and tick magiskhide then reboot. Safetynet no longer passes. I get the blue screen on safetynet helper.

Funny thing is that I go back into magisk manager and magiskhide is unchecked again...

Any ideas?

Edit: I fixed it. I was a genius and forgot that I also needed an app for superuser access. I was just used to SuperSU that installed the apk along with the zip.

Long story short, it's working just fine. Just needed to install superuser.
[Magisk] mrxtc89117:
You are losing root too, right? I've seen posts of this happening. It happened to me too on My Moto X Pure. I had to use the magisk_v8_mod2.zip. Search for it in this thread. On my LG G3, the magisk_v8.zip works fine.
[Magisk] tecnicalk:
Magisk v8

Magisk V8 seems to break auto rotate on my Samsung Galaxy S5 (GM-900F) and my phones screen will rotate fine at first the stop working. [Bug]
[Magisk] Vipriel:
Even though the app says that, it is in fact able to hide Xposed 86.2. I believe it does not work with 86.6 however. In some instances, Root Switch will show Xposed in the toggled off state when you open it after installing Xposed. In this case, try toggling to On first, and then toggle it back to Off (app will make you soft reboot between toggles). As the OP stated, you should see the status of Xposed as yellow within the Xposed installer app if the toggle worked properly.

If the above doesn't work, try wiping Dalvik and Cache. In my case, I couldn't get things to work after doing the above but after wiping Cache and Dalvik, I got Green on SafetyNet helper. So when in doubt, always wipe Dalvik and Cache (and reboot).

---------- Post added at 04:36 PM ---------- Previous post was at 04:33 PM ----------

Thank you!!! This does in fact work. I was running with just Magisk v8 on a flat S7 and I was able to hide Magisk without needing Mod2. One thing I could never get to work was Xposed. After reading your post I once again installed Xposed 86.2 and then installed the latest version of Root Switch (1.3.3.2). Initially, even though I toggled Xposed off and got a yellow result in Xposed installer, SafetyNet kept coming up blue. However, after wiping Dalvik and Cache and rebooting, it did pass successfully and showed green. :)
[Magisk] justmiike:
How did you manage to install Xposed 86.2? It won't install for me if Magisk v8 and pph superuser is installed. Followed OP's message, but couldn't do it. Did you do something differently?
[Magisk] yochananmarqos:
It sounds like Magisk Manager does not have root access. Did you install the phh superuser app from the Play Store?
[Magisk] adrman:
I went through roughly the same procedure and issue with Franco Kernel on my 6p. I had to reflash the kernel again after Magisk & phh259. I'm passing SN now and made two AP transactions this afternoon.
[Magisk] Vipriel:
Just flash Xposed-v86.2-sdk23-topjohnwu.zip in TWRP (if you are on Marshmallow).

---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------

So I am replying to my own post here because even though I can pass SafetyNet with Xposed installed and can play PoGo, at least some of the Xposed modules are in fact not working. For instance, Snorlax won't work for me.

To [MENTION=4577747]zapahacks[/MENTION], what version of Snorlax do you have? When I have Xposed toggled off through RootSwitch (and it's yellow in Xposed installer), it won't run. I am using the latest version (same version I used to use in the past before the latest SafetyNet update).
[Magisk] duowing:
Quick question. I see the Magisk V8 mod2 and see it's mentioned to use this if you're losing root? So should I flash this. After some random amount of time it seems like root will stop working for some things. Greenify and Titanium lose root, but Terminal Emulator could apparently still obtain root. I'm on a HTC 10 US unlocked. S-Off, locked status. Stock rom 1.96.617.20 running ivicask pnp19, and clean slate 1.7.3. I have magisk V8, superuser r259 magisk version, xsetprop, and magisk hide enabled. Should I just flash this mod2 file?
[Magisk] Captain_Throwback:
No. Do not flash the mod2 file. Just reboot the device, and root should return. This is a random bug - especially on the 10.
[Magisk] mrxtc89117:
I have tried it and it works on one of my phones. However, it is not the official version and it can cause inconsistencies and apps behaving strangely. So use it at your own risk.
[Magisk] st3venhall:
I also am wondering about this... Although I don't care about Android Pay. I have had troubles with viper room and unrooting SuperSU and installing magisk+phh, i continue getting FC's with the settings app. apologies if it's been discussed but I keep getting referred to different threads by people, and questions about the HTC 10 continue getting overlooked within this thread it seems. Thanks!
[Magisk] duowing:
Thanks for the reply. I've been loosely following this thread and must have missed your input.
[Magisk] justmiike:
That's the issue, if I flash it, it won't install. Because it was designed to work with SuperSU, not pph superuser. Or maybe it's Samsung, but I'm not understanding how 86.2 is installing for people using pph superuser.
[Magisk] Captain_Throwback:
What makes you say that? The post you quoted was hundreds of pages ago. Both [MENTION=4470081]topjohnwu[/MENTION] and I use Magisk on our HTC 10s - and I'm one of the most active people in the thread.

To answer the question you quoted, you don't need stock kernel to flash Magisk, but it can't be pre-rooted. Viper ROM is heavily modded, but they don't usually include a custom kernel. I do think their boot.img is rooted/patched though, so that *could* be a problem. But you may need to ask in that ROM thread rather than here.
[Magisk] henderjr:
I am using a Samsung (note 5) as well and flashed 86.1 by wanam because 86.2 wouldn't work. See recent posts, past two days, by me for more detail.
[Magisk] pndwal:
Also A/B SAR (Ramdisk Yes) can be single stage init, and 2SI (Ramdisk Yes) can be A-only... PW
[Magisk] huskydg:
Yup, A-only can be 2SI if we remove skip_initramfs=1 from cmdline
[Magisk] pndwal:
I mean some 2SI devices are A-only out-of-the-box; (these don't share boot ramdisk with recovery like A/B do).

More importantly, A/B SAR & Ramdisk Yes does not mean @zgfg's device is 2SI... Some are Legacy SAR (eg Pixel 1 & 2)...

Launch version Android 10+ is what indicates 2SI. PW
[Magisk] dr4go:
Is your mod still available anywhere / could you provide me a link? Thanks a lot in advance.
[Magisk] pndwal:
Sometimes I wonder if people can read ... Or think about what they're reading...
[Magisk] dr4go:
Related to which post exactly? In case it was mine, I read and understood every part of it.
[Magisk] vMAC:
Where can I find the latest v25101? If I go to the github site and download the latest canary it doesn't tell me what the version is, but I assumed it was the latest v25101.
[Magisk] rodken:
Sometimes, you have to dig deeper within Github to get results?
[Magisk] J.Michael:
To be fair, github is a maze of twisty little passages.

I have found the download links in the past.

Other times, where I am, there seen to be no links to what I want, or to unwind my state to let me wander down to the download links. Maybe if I actually read the flowery manual...
[Magisk] m0han:
incompatible! with what? does anyone know?
[Magisk] zgfg:
Is Zygisk enabled and Enforce DenyList disabled in Magisk app
[Magisk] zgfg:
OMG

In Magisk app you have DIRECT LINK to TJW GitHub

On that main GitHub page, scroll to DOWNLOAD and click on Magisk Canary (to download the latest Caneay) - how else

That's the page that looks like any Web page and one does not need to know anything about Github

True that the name of downloaded app does not Canary and version number - if unhappy with, complain to developer
[Magisk] m0han:
yes. no option to disable 'enforce denylist'. i'm on the latest delta. the only change to the setup i had shamiko 0.5.0 on is usnf was updated to 2.3.1.

p.s.: that was my post you quoted, but the name is seen as vMAC and not m0han. how come?
[Magisk] zgfg:
I don't use Delta.

Delta is special mod, ask how to use Delta and Shamiko in the Delta thread
[Magisk] casouzaj:
I was using Denylist Unmount v0.2 along with USNF V2.3.1.. Momo v4.3.1 detected Zygisk. Replaced DLU by the new Shamiko (v0.5.1). Momo doesn't see Zygisk anymore.
[Magisk] m0han:
i disabled dlu and rebooted. still incompatible.
[Magisk] casouzaj:
I'm running Magisk Delta. Zygisk enabled and Deny list properly configured, but not enforced.
[Magisk] m0han:
i'm on the latest delta. i see no option to disable 'enforce denylist'. well, i 'removed' dlu and shamiko, rebooted, installed shamiko 0.5.1 afresh. now momo 4.3.1 does not find zygisk. but, init.rc is modified.
[Magisk] martyfender:
I have one of my devices on the delta. I believe there is no option to disable enforce denylist because the delta includes magiskhide and with it the denylist must be enabled. I asked @huskydg this twice to clarify, but he never responded, if I recall he responded with something else.
[Magisk] casouzaj:
Turning Magisk hide off acts like disabling enforce.
[Magisk] zeppelinmad4:
I am not sure where I am supposed to post this. I have a google pixel 6 pro rooted on android 13.3. I accidentally hit 'reboot to recovery' in magisk and I am stuck in a bootloop. I am able to get into fastboot mode but adb does not recognize my device. Device manager recognizes it as lemobile android device>android bootloader interface. I searched on here, the pixel 6 forum and just google but am not too sure what I should do. I don't know if I have a rogue module but I do not know how to uninstall it since I cannot find a twrp for the pixel 6 pro.

edit: I didn't realize it was 'fastboot devices' instead of 'adb devices'. I downloaded the android 13.3 factory image and am now installing via the 'flash-all' script. Hoping I don't run into any more problems.
[Magisk] martyfender:
I had tried that and rebooted, but shamiko still showed as not working because of denylist being enforced. I will try again, with the new shamiko though.
[Magisk] m0han:
funny thing is 'shamiko doesn't work....'.
[Magisk] martyfender:
I disabled magiskhide in the delta, installed the new shamiko and rebooted and shamiko now shows as working. Onn 8 first gen, Android 9 tablet. The latest momo only reports init.rc modified.
[Magisk] casouzaj:
Have you read my post above? I had this error notice from Shamiko, but after I switched off Magisk hide and rebooted, all was fine.
[Magisk] m0han:
ditto
[Magisk] zgfg:
Now reading all these recent posts about Delta, everything is pretty logical

Keywords: Delta, Alpha, old MagiskHide, DenyList missused for MagiskHide - all in all, no place for Shamiko in that context

That's why I suggested to move that discussion how to use work with Delta to the Delta specific thread
[Magisk] Homeboy76:
Read

notes.md

it will show you what version of Magisk Canary is available.
[Magisk] zgfg:
True, but for that one must be somewhat familiar with GitHub, while newbies usually are not, and then they ask how this/how that/where is what, what to click, etc

Alll downloads (Stable, Beta, Canary, Debug) are easily, on TWO CLICKS, directly accessible from the Magisk app - see post #52425
[Magisk] pndwal:
Just to clarify:

Shamiko basically restores MagiskHide (hides root traces from apps with reverting Magisk modifications) for Zygisk Magisk builds and needs Denylist Enforced disabled so Magisk modifications are not reverted/denied for listed apps... Since Delta integrates the same function and has already 'hijacked' the denylist for hide purposes when MagiskHide is enabled (read 'In Use'), there's a conflict... Shamiko hiding and Delta hiding are not compatible... PW
[Magisk] zgfg:
For me (recently I learnt it's 2SI device - whatever it means😁 - ok, 2 Stage Init), nothing changed

Latest Momo with latest Shamiko (latest USNF, DenyList disabled) on latest Canary still detects su, Magisk and Zygisk

As TJW named, mast..tion device👍
[Magisk] pndwal:
Haha 😝... Suitably cryptic comment about fish prices...

It was in relation to

I answered and detailed the hallmarks of each Android boot-type (Legacy Ramdisk, Legacy SAR & 2SI "SAR"):

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

Next post:

... Just don't understand what this has to do with the price of fish... It tells me nothing...

Perhaps you could explain?... 🤪 PW
[Magisk] J.Michael:
Too late to be of help this time, but

I have seen people talk about using the "flash-all.bat" and they either add or delete a "-w" switch in order to *not* erase data.
[Magisk] zeppelinmad4:
That would have been good to know. I will definitely remember that in case I mess up again.
[Magisk] Bouls:
Bro, I formatted my data and everything and flashed disable dm verity force encrypt. After patching this file, I wasn't able to patch magisk.zip (I got the same error that I talked about in this thread."Unsupported boot image extra"). So I re-formatted my phone again and flashed magisk.zip only in twrp and it worked. But I want to disable force encryption in my device because I'm not able to access internal storage in twrp. Please I need help
[Magisk] J.Michael:
Search the threads again. I think, after installing TWRP, you use TWRP to wipe data. And somewhere in there you say "do not encrypt".
[Magisk] Bouls:
Ohhh really?? Yes that's what I did I formatted my data using TWRP but I didn't noticed there is an option to check do not encrypt
[Magisk] Rcedude:
Hello. Can someone help me downloading latest Momo please? https://t.me/magiskalpha/517

I am on computer and i dont want to make a Telegram account :/.

Thanks.
[Magisk] Homeboy76:
True, but the XDA Members wanted to know what version of Magisk Canary he was downloading.

The link I provided gave the version information.
[Magisk] huskydg:
If shamiko only can hide zygisk for momo, but really can't for the banking apps such as livin by madiri, instapay egypt, itsme,... then I don't know what is the "core value" mean of using shamiko to hide zygisk?
[Magisk] 73sydney:
About every device ive used requires a zip file flash to disable dm verity. forced encryption.....

For my S20+, after the bootloaderin unlocked, and TWRP is flashed via ODIN, i have to format /data, and then flash an encryption disabler zip

I would check your devices forums for similar to see if similar is needed
[Magisk] vMAC:
zgfg

I don't know if we are having a language barrier or if we are going round and round because we are just saying the same things. Let me try to make it clearer.

I have downloaded the latest canary from TWJ Github

Intune does not allow me to install any unknown sources to my personal profile, nor my work profile

I cannot use the magisk manager app to update since it is from "unknown source"

I have attempted to go around this by installing the latest canary from TWJ Github using "adb install"

After doing this it STILL states that I am not on the latest Magisk Manager

Is this normal is the question? Is there any other way to update with the limitations that I state above without removing Intune doing the upgrade and then reinstalling Intune?

Last question is if I uninstall Magisk, then use the "adb install" to reinstall if that works, would I be able to hide Magisk Manager again or would that be blocked due to "unknown sources?"
[Magisk] m0han:
some devices have modded twrp available that has an option to 'disable forced encryption' and many other 'features'. i think it's the equivalent of using the relevant zip/script(s).

btw, it has been reported by several users that that twrp for poco x3 (surya/karna) can decrypt /data on A12.1.
[Magisk] 73sydney:
Cheers, yes, i was speaking generally because i wasnt aware of the OP's device, but yes you can get custom TWRP for some devices that includes, ive never personally seen or used one on any of the flagship devices ive used....Pixels/Samsung over the years, its always been a zip :)

Also recently with the S20'+, someone had to update the zip we used after yours truly (im so lucky) became the 1st person to go around in circles with the previous zip after Samsung changed the paths used internally, fun times :)

Can i get a #ponkles ?

.... Ive been watching too much Jimmys World on youtube...#clearprop
[Magisk] zgfg:
I asked you about downloading to make sure that you are really downloading the Canary 25101.

My APK is 10.71 MB and see my screenshot with hashes to double check do you have the same/correct 25101 apk

Second, I asked does your adb installation ends with an error or not?

(If it ends with an error, maybe bcs of Intune, then obviously you would not have the new 25101 installed after your 'update')

Third, I asked you to unhide or even delete your old 25001 APK before installing the 25101apk

All those questions were to help to see why after your adb installation of the new 25101 you still open 25001 aok

If you don't understand these questions or you don't want to do so (deleting your old 25001 APK WILL NOT uninstall Magisk itself, your Magisk modules, end so on) then sorry, I can not Help you better

You asked me "is that normal". How do I know is it 'normal' - it could be that Intune does not allow you even to install via adb - that's wh I asked you does adb report an error

Many users have 'problems' installing the new Magisk app (normal way, nobody installs by adb - I didn't see any post from another user with Intune doing that way) IF THEY DIDN'T NOT unhide or uninstall the previous hidden version of Magisk app.

We have had tens and tens of such cases here (without Intune, maybe you didn't follow and read discussions here, it's not specific to 25101, it's repeating through months:

Without unhiding or deleting, after updating they have both apps, old hidden and new.

Maybe you also have both, but you don't 'see' the new 25101 APK and you are opening that old hidden 25001

That's why I asked you to unhide (or even delete) your old 25001 APK.

But I cannot answer you would you be able to hide again. How do I know for sure if I don't have Intune and cannot test myself?!?!?!?!?!

Maybe somebody else with Intune can tell you about hiding the Magisk app with Intune.

Btw, if you were able to hide 25001, then you should be also able to hide 25101 as well

---

EDIT:

To avoid the case that after your adb installation of AP 25101 you still open the old/hidden/repackaged 25001, test as on my second screenshot (I used terminal app but you can do through adb with adb shell)

Ie, your old hidden 25001 is repackaged and has a different package name (random)

Test do you have installed the package: com.tophognwu.magisk

If it shows that package is installed, it means that you have in parallel the old hidden (random pkg name) 25001 and New not-hidden 25101 (com.topjohnwu.nagisk) - common problem for users who do not unhide before updating the Magisk APK
[Magisk] m0han:
drawing inspiration from @casouzaj's assertion that he has always updated magisk app, including the latest one, keeping it renamed/hidden....and just the updated renamed/hidden app shows up in the apps drawer, i did a dirty update (see screenshots there). i don't recall having hidden the magisk app after that; it showed up as renamed app, just the way i named it. ymmv, though. and, i hope i don't run into trouble in the future. :D ;)
[Magisk] zgfg:
See and test as in EDIT part of my post #25459, to make sure that you don't have in parallel both, hidden old and not-hidden new
[Magisk] m0han:
you probably meant #52459, right? i run delta now; don't have any other magisk packages on my device atm.
[Magisk] zgfg:
I don't know about Delta and its package name and updating while hidden.

Still my questions/suggestions for vMAC remain (he uses Canary, not the special Delta)

Also, if you (or somebody else) have Intune, welcome to help him
[Magisk] dr4go:
I thought your post would have been related to mine and the fact that I was asking for a mod, which had been removed upon request. Thanks for clearing up the fish market! 🦈🐟🐠🐡