yashsingh1/xdaforums huggingface dataset:
[Magisk] Immortalis:
For me, after disabling root with Root Switch, I pass SafetyNet, but after enabling it my root disappears and I have to reboot the phone in order to make SuperSU work again.

What should I do?
[Magisk] Captain_Throwback:
Post in a thread dedicated to Root Switch? That certainly doesn't seem related to Magisk...:rolleyes:.
[Magisk] hgoldner:
Frankly, that sounds like a feature, not a bug, and, by the way, [MENTION=1162986]Captain_Throwback[/MENTION] is right, you're in the wrong thread.
[Magisk] Immortalis:
If I don't install xsetprop, root is ok, but I fail SN, because it is detecting my unlocked bootloader.
[Magisk] edyny1:
Everything good so far I'm also using Alexis Rom. Now im trying to get this xposed 86.2 installed but like you said its tricky. Now do you install 86.6 then 86.2 uninstall xposed then fash 86.2 all at once in recovery or you do a reboot on each of the installs??
[Magisk] andrew2432:
[MENTION=1162986]Captain_Throwback[/MENTION]

Safety net passes

Snap chat logs in

Pgo does not login

Technically, magisk v8 has done it's job. I can pass safety net, I can possibly use android pay, I can send weiner pictures to cute girls again. Searching through threads in order to appropraite thanks. But pgo does not login for me. What thread should I be posting this in, I think I've done it in all the magisk threads I'm in now...
[Magisk] Captain_Throwback:
Please stop mentioning me.
[Magisk] andrew2432:
I do mentions because I thoughts quotes were more annoying
[Magisk] Captain_Throwback:
They are equally annoying, when you're mentioning/quoting me for no reason.

I get notified when there are responses to the thread, just like everyone else that's subscribed.
[Magisk] Fedroid:
Doesn't work either [emoji26]
[Magisk] andrew2432:
I don't get a notification unless someone quotes or mentions me, in my subscribed threads tab it pops up with a differnet color but no notification. I assumed it looked like mine!! I was just trying to find out where to go with this, it seems this is a strange problem. I thought I'd bring it up.

There was a reason...where can I take this question. Magisk seems to be doing its job, tested with: the safety net test you offered green->also means android pay should work but I don't use it, snap chat logs in again, a positive, Magisk hide works, no pgo. Just attempting to find where to go
[Magisk] rfgamaral:
I'm also having this same issue. Has anyone found a fix for this?

I'm trying to uninstall it because I can't get it to work... I have this module and the pixel launcher installed but I don't know how to launch the assistant...

Save​
[Magisk] J.Michael:
@facet_: "ponkles"?
[Magisk] facet_:
Magisk hide promps Config

Systemless hosts

but before the activation of the zygisks they were also active and nothing happened. I have the impression that activating enforce denylist ruined everything. Or even adding a denylist to configure.

several banking applications added, including revolut and google services ending with gms and gms.unstable. Do you think any of the selections are causing the problem? Previously, the same ones were marked on 23 and nothing ever happened.

I just removed all modules and in configure denylist I only gave revolut. I clicked on some application and restarted again.
[Magisk] facet_:
unfortunately I do not understand
[Magisk] pndwal:
😝🤔

No issue, but zy-USNF will remove Play Services (gms) processes on each boot as it hides root from SafetyNet process itself...

So you removed systemless hosts also? PW
[Magisk] 73sydney:
Theres only so many mysteries that can capture your imagination...

Is there life after death?

Are we alone in the universe?

Who shot JR?

What are Ponkles?

Not even google knows....
[Magisk] Izzy2004:
I just wanted to give a shoutout to the level of pure **** that the devs of V24 must have been submerged in to go and turn v23 into what-ever you call this. Gratz.
[Magisk] facet_:
sorry i meant i did a trial and tested what is causing the problem.

So you removed systemless hosts also? PW

can you write more because I don't know what's going on.
[Magisk] facet_:
Sorry for my translated english. I meant the words "I made a test"
[Magisk] aleMarvel:
i not understand sorry...

my problem is play services removed automatically from playlist.. i don't want.. i want playservices ALWAYS denied.. how can i do ? you give me this two links but in not understand
[Magisk] pndwal:
Did you check the links?

They show that Zygisk-Universal SafetyNet Fix removes Play Services (gsm) processes from denylist on boot, and why...

If you want to deny Magisk modifications to gms using denylist you can, but you'll need to uninstall zy-USNF to prevent it from removing gms from the list and doing its own root hiding for the SafetyNet process... 🙃 PW
[Magisk] 73sydney:
Please dont apologise,your post created a word which amused us for almost a day, and we dont get much amusement in here :) :)

Ponkles forever!!
[Magisk] 73sydney:
GMS (play services) automatically disappearing confuses many, so dont be alarmed, nothing is broken, all is working as designed, and you shouldnt fixate on trying to tick GMS (play services), because you wont be able to.

Very simply:

The moment you install the (Zygisk compatible) Universal SafetyNet Fix module, it will automatically remove GMS (play services) from the Deny List, and will do the same thing anytime you try and (re) enable it. This is by design and is coded in the (Zygisk compatible) Universal SafetyNet Fix magisk module, to stop users causing issues on their devices
[Magisk] 73sydney:
a post without details or a log is a whinge, and you also deprive people of the ability to help you. At this point youre your own worst enemy, and not the magisk devs....

24 works for quite a lot of people, you might have a device with an edge case, at which point the thing to do is at least post what device youre on, or not....
[Magisk] pndwal:
Since you said

I wanted to confirm you also disabled / removed inbuilt Systemless hosts module also.

This is because it traditionally caused stability issues like yours with devices that had the f2fs-loopback-bug in the kernel... I thought "your device, being of 2018 vintage, may have this bug since many OEMs were in no rush to fix it..."; my thought may also be way off the money...

Hope you have fun translating all that... And this too:

We all love your 'ponkles' (one member here told me "it is literally all i care about now") and 'hide promps' here... We're submitting a petition for a 'Magisk - the Age of Ponkles' and a promp hiding module!... Nb.Only this paragraph is entirely superfluous with respect to the issue you face...

🤠 PW
[Magisk] J.Michael:
@aleMarvel Z-USNF removes some Google processes from the denylist because Z-USNF *always* does something special for those processes.
[Magisk] zgfg:
To avoid any mystery about what and how USNF removes from DenyList, I will repost the same screenshot as recently posted to the USNF thread (the same has been posted by others and in one or another form, eg pointing directly to the USNF GitHub, in all our threads about Magisk, USNF, etc - where the other users come and cry why the GMS 'dissapears' from their DenyList)

USNF removes and only GMS = Google Play Services from DenyList

Screenshot attached from the USNF installation folder (equivalently, from the unzipped USNF module installation archive) showing the content of its post-fs-data.sh script (script will be executed on every reboot by Magisk, when USNF module is installed and enabled) calling the Magisk command line that removes GMS (GMS only) from DenyList

DIY Test:

Add Google Play Services (and as many other Google or non-Google apps, just for the purpose of this test) to DenyList

Execute from Terminal:

su
magisk --denylist rm com.google.android.gms
exit

Reopen DenyList, and Google Play Services (that and only that one) will be disappeared from DenyList

The same way it disappears upon every reboot (if GMS was added to DenyList) bcs the same "magisk --denylist rm ..." command being executed from the USNF post-fs-data.sh script when Magisk initializes the USNF module
[Magisk] Red Valdes:
Crash Magisk 24.3, version 23.0 work good, Android 5.0.2
[Magisk] dimm0k:
I had magisk installed and running without any issues on my OG Pixel, but recently decided to wipe the device to start things from scratch. the boot image should still be rooted, but when I install and run magisk all that happens is I see the magisk logo and that's it. any suggestions?
[Magisk] moocow1452:
Hi all,

After working with the Magisk GitHub community, a new patch was integrated into the Canary builds that allows root access for the Oculus Go. Super fantastic, and I would like to thank them and all of you for your help, but now that root is available, what would be the best toolset for trying to disable Facebook login, or install Google Play Services without getting the launcher stuck? Is there any resources for something like this available or am I pretty much on my own?
[Magisk] pndwal:
What kind of wipe? PW
[Magisk] pndwal:
I don't have vr headset, but please say what you are trying to achieve. Why disable Facebook? Does installing GMS freeze launcher? What launcher? PW
[Magisk] dimm0k:
a complete wipe through Android Settings... did I do it wrong?
[Magisk] pndwal:
No... So factory reset...

I'm guessing at an issue; are you running recent Canary build (freezing on logo)? PW
[Magisk] dimm0k:
Yep, trying to install/run 24308. unfortunately I don't recall the version I had running prior to the factory reset
[Magisk] pndwal:
Confirms my theory...

I was asking about wipe type as this issue occurs when root is lost... It may occur with root if app cannot detect it too, eg you installed Magisk app, ran Hide the Magisk app function, subsequently updated the app or manually installed another and it didn't detect / remove the hidden (obfuscated) one and subsequently you have a case of DCAS* which results in Magisk Installed = N/A

[*Dual Conflicting App Syndrome]

Since you indicated you had rooted boot image and factory reset (?) only, root loss does seem unlikely, but could be explained by DCAS if you did in fact play with Hide the Magisk app, or actually flashed images since factory reset, or even ran Magisk in-app Uninstall before doing f reset / wipe...

However If my deductions are correct you seem to have this issue:

Magisk app ANR on non-root devices #5787

Fix is already merged but not built yet:

0ac19e3 Fix app running without root

I mentioned this here:

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

If you think I'm right, until next Canary release you can either 1) locate and uninstall conflicting hidden app ('System' or whatever you renamed it) in device settings, apps [if this accounts for Canary app not finding root], then 24308 should work, or 2) install either this test build: https://github.com/topjohnwu/Magisk/actions/runs/2285778144 (extract from artifacts), 24306 or earlier Canary, or 24.3 Stable [if hroot has really been lost / boot image restored etc], then use working Magisk App to do initial patching again...

Hope I'm on the money...

🤠 PW
[Magisk] dimm0k:
your deductions are INDEED CORRECT!! thank you! I went with the test build and now all is well. I've been jumping between devices that I don't recall if I did or didn't hide magisk on this device prior to the wipe, but it would be the most likely scenario. thank you for explaining as well!
[Magisk] moocow1452:
The Oculus Headsets come with the Oculus Home Launcher, with an Oculus Guardian that is labeled the device administrator. On the Quest, there's a way to disable Facebook stuff after initial login, but on the Go, if you try it, the Home Launcher just gives this three dot prompt in a black void, presumably it wants to phone home and refuses to operate until it does. Same thing happens when I try to push Google Play Services onto the device, and I'm assuming something permissions related is happening.

Ideal goal would be able to load the Oculus Go up with a bunch of streaming services and watch all the movies and shows in them. Unfortunately, a number of them require Google Play Services to run, so I'm at a bit of an impasse until that's worked around. Other people in the circles I run with wanted to be able to disable Facebook login from out of box experience, so I figured if the GPS issue can be worked around, that one can be too.
[Magisk] J.Michael:
Weenie way around logins: Make up new Facebook and Google accounts, replace device account, let Oculus log into useless Facebook account.

If privacy is your concern, maybe remove Google account from device, spoof device fingerprint, attach new useless Google account to device, before connecting to useless Facebook account.

Does [pico][nano]gapps implement Google Play Services?
[Magisk] pndwal:
If it's actually the Guardian component that freezes with unexpected environment changes, I'm guessing you may need to turn it off...

On the new Quest 2 this is apparently "easier than justifying a second bowl of ice cream on a hot day... like a defiant teenager, you’ll be breaking boundaries in no time."

https://stealthoptional.com/how-to/...uest-2-how-to-disable-oculus-guardian-system/

Seems you just need a developer account. from developer.oculus.com, then you'll have a 'developer mode' in Advanced settings w/ Developer Options where there is a toggle for turning off Guardian...

I don't have any idea if this option is available for Oculus Go, but it might be an avenue you'll want to pursue... Unless you're no longer the defiant teenager you once were... or you just hate ice cream... 😝 PW
[Magisk] 73sydney:
Play Services is common across all Open Gapps formats at least, be a bit insane not to be:

Package Comparison

The main repository of the Open GApps Project. Contribute to opengapps/opengapps development by creating an account on GitHub.

github.com

Ponkles...
[Magisk] rexmako:
Hello all. I've been searching for where to download magisk modules. Any quick and direct link(s)?
[Magisk] m0han:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86836101

not direct ;)
[Magisk] 73sydney:
direct-er-er:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86320335

...Ponkles
[Magisk] dobi3:
Go to

GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it

A module manager for Magisk because the official app dropped support for it - Fox2Code/FoxMagiskModuleManager

github.com

Install

Fox's Magisk Module Manager​

Enjoy 😁
[Magisk] m0han:
direct-er-er-er: https://github.com/Fox2Code/FoxMagiskModuleManager/releases

directest: https://github.com/Fox2Code/FoxMagiskModuleManager/releases/download/0.4.5/FoxMmm-0.4.5.apk
[Magisk] Roxbox:
Hello. I have a problem with the Safety net. I have a clean stock rom, root done, clean magisk installation with no modules. I have a problem with the SN all the time and I don't know how to fix it. HTC U11

I have version 22.1 because on the newer I don't see the menu and there are no modules to be installed.
[Magisk] 73sydney:
1. thats a very old version and you should immediately uninstall it, because frankly thats madness

2. you should then read the opening page of this thread, and install the current version

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

3. the magisk repo (the ability to download and install modules from within the app) was removed for a reason, amongst them its no longer maintained by the creator of magisk - by design

4. the first page of the above thread will have modules suggested to pass safetynet (try Universal SafetyNet Fix first), and also a link to an app "Fox's Magisk Module Manager" to install modules. This is now the correct (and only easily manageable) way to go.

5. if you do it properly, you'll also get support from the thread - that newer thread - whereas going about it backwards is unlikely because we've moved on from this thread largely to that newer one...

...selknoP
[Magisk] Roxbox:
Thank you, I will check everything.
[Magisk] 73sydney:
Good o, you'll find that first page has all the info in one spot thats up to date, laid out well and not scattered to through 2,590 pages of his thread :)

Note: You'll also need YASNAC - Yet Another SafetyNet Attestation Checker (also on that first page), to check for SafetyNet, as SafetyNet check was also removed by magisk dev from the magisk app...
[Magisk] zgfg:
You forgot your new signature

And it would be better like this:

...ƨɘlʞnoᑫ
[Magisk] Roxbox:
I have uploaded the latest version of Magisk via TWRP and Yasnac shows this message .
[Magisk] zgfg:
What about installing USNF 2.1

Pls carefully read all posts in that Magisk+Zygisk thread, on its first page
[Magisk] 73sydney:
As i (and @zgfg) posted, try Universal SafetyNet Fix first, if that fails, let us know
[Magisk] Roxbox:
My mistake. I've already installed USN and everything works as it should. Thank you very much :)
[Magisk] zgfg:
Your post was #58152, the same was answered today in #58149 and #58150. Pls read sometimes before asking...
[Magisk] m0han:
lufpleh; very, like this one.
[Magisk] Roxbox:
Everything is done now. I got tips where to look and it's ok
[Magisk] rexmako:
Many thanks. This is helpful...
[Magisk] dohanin:
Glad to report that after updating Shamiko to v0.5.0, Zimperium ZIPS can no longer detect App Tampering.

:)
[Magisk] zgfg:
And Momo v4.1.0 does no more report Zygisk found
[Magisk] pndwal:
Latest Official TJW debug Canary Magisk:

Magisk (985249c3) (24309)​

Pixel 6 Android 13 Beta 2 support is here!

[App] Support requesting root from non app process

[App] Fix deadlocking a background thread on non-root devices

[MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[MagiskInit] Support GKIs with no ramdisk (Pixel 6 Android 13)

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/56da1fe5430b2c04701ce73d1658ba698ee92283/notes.md

👍 PW
[Magisk] pndwal:
Latest Shamiko:

Shamiko v0.5.0​

0.5.0​

Better hiding Zygisk

👍 PW
[Magisk] zputnyq:
Hi all,

I'm using canary 24309 & never hide it before.

I have two problems after hiding the magisk app.

The problems are

1. After hiding the option to unhide & some option in setting are dissapear.

2. The magisk app creates 2 icon one of them is untappable.

Anyone know how to unhide magisk app on canary 24309 ?

My device is xperia m4 (6.0.1)
[Magisk] zgfg:
Uninstall the hidden app (APP ONLY) and install the app again. It DOES NOT uninstall Magisk, modules, whatever
[Magisk] Fooking Rekt:
Either I am incredibly stupid, or something's wrong with Magisk, but I cannot seem to root my Galaxy S7.

When I install Magisk on a fresh rom, it will say "Ramdisk Yes". I then select the AP.tar file and patch it. After flashing the patched file + BL + CP + CSC the phone boots up like normal, when I open Magisk it suddenly tells me Ramdisk No. My phone is not rooted, nor can I proceed further after this. Trying to patch any files now doesn't work. Inside the AP folder there is a boot.img file, but it has an .lz4 extension. Am I supposed to decompress this .lz4 file and then patch the result?
[Magisk] 73sydney:
patch the boot img (and vbmeta too if your AP has it) file itself, patching the entire AP is a long long process and can fail

1) Extract the boot.img.lz4 and vbmeta.img.lz4 from the AP file using 7zip (right click on AP file and Open Archive, select the files and extract)

2) Use 7zip to create a new .tar file containing the boot.img.lz4 and vbmeta.img.lz4 file (with 7zip installed, select boot.img.lz4 and vbmeta.img.lz4, then right click on selected files, then 7zip, Add To Archive...then change archive type to tar, then OK)

3) transfer new .tar file to phone

4) open magisk app

5) select the new .tar file and patch

6) transfer patched file back to PC

7) flash in ODIN in AP slot (phone in download mode of course)

Same process as i use for my S20+
[Magisk] AndreSantoro84:
Hello. I did this way to fix my safetynet (first file, version 1.2.0) and it worked fine, but my native Samsung apps (Galaxy Store, Bixby, etc) stopped recognizing the device (error 2300:1004:128fdddaa000). I verified via the Yasnac app that my safetynet is recognized as a Pixel (d2s) model. Is there a way to keep safetynet fixed and get Samsung apps working again? I'm working with Magisk 23.0 and my device is a Galaxy Note 10+. I appreciate any help.
[Magisk] 73sydney:
you should be using the most recent verison of Universal SafetyNet Fix....not the ancient one, it will not work in magisk 23/24 due to underlying changes in magisk. Ideally you would move to magisk 24 too

and using a modded device id is not the answer unless youre REALLY stuck...faking being a pixel will cause issues with Samsung apps, separate from running the wrong SafetyNet Fix version

remove that module and install the v2.2.1 (Zygisk) version from here:

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

then take a trip over the following link because that thread covers everything else you need to know in the first page

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

bookmark that page and post any support questions there, as this topic is old

add any Samsung apps or other apps that complain about root or misbehave to the Deny List in Magisk Settings, and its advised to leave the enforce Deny List toggled off, and install Shamiko (which requires that toggle off and is linked on first page of above thread). do not do what some folk do and add every google and samsung app to the deny list, only what is absolutely needed - banking apps etc

also be aware that once rooted, you cannot use Samsung Pay, Samsung Pass and even Samsung Health beyond a certain version (6.19) will not work correctly. galaxy store works fine (does NOT need to be on Deny List) as does Bixby i believe (ive never even tried that thing in all these years, i always remove it)

S20+ and Watch 4 here...thats how i know about the Samsung Apps status and especially Samsung Health beyond 6.19 not working 100% :)
[Magisk] pndwal:
USNF is much improved since 1.2.0.

Re latest Zy-USNF (2.2.1):

https://github.com/kdrag0n/safetyne...ails.md#how-does-universal-safetynet-fix-work

For you, I believe that latest riru-USNF (2.1.3) will do much the same thing (using Xhook in Riru instead of in Zygisk and leaving SafetyNet process and sensitive prop(s) hiding to MagiskHide)...

Using latest riru-USNF should fix device (OEM) specific functionality... 👍 PW
[Magisk] 73sydney:
Well he got two answers, lets hope he chooses just one and doesnt mix and match :)

...Ponkles
[Magisk] pndwal:
Yup... Nb. He's currently using pre-Zygisk era Magisk... (Roast Kumera, not raw Zukini...) 🙃 PW
[Magisk] Fooking Rekt:
I don't have a file called vbmeta.

At step 5 instantly says "Installation failed!" regardless of what additional boxes I check or leave unchecked.

I am using Android 8.0 and bootloader version 4. Should I try downloading a more recent firmware? (I think the S7 goes up to BL version 8)
[Magisk] AndreSantoro84:
Hahaha thanks for both answers! Another question, if I update the root to the latest version, I can use this version 2.2.1, right? I ask because my problem is the following: Since updating to version 24, hide has been weird (although the deny list works well), so several apps I use started to be not compatible in the Play Store (I think because of the bootloader , because even without root they are still not compatible), so the only thing I would like is for this feature to work again and these applications are normally able to install as it was until version 23 of Magisk.
[Magisk] 73sydney:
Are you still spoofing your phone as a pixel? That might explain the incompatibility....