yashsingh1/xdaforums huggingface dataset:
[Magisk] Homeboy76:
You are correct using Magisk to

Restore images

will return the phone to stock.

I think the Pixel 5, 4a5(G), and 4XL members need to flash the dtbo.img if they have a Custom Kernel installed.
[Magisk] Lughnasadh:
Just to be clear, it will only restore the boot image and other partitions that are modified by Magisk to stock. It won't necessarily return other modified images or other modifications done to stock.

And don't forget, in order to take the OTAs you have to make sure you haven't modified /system or /vendor or other read-only partitions in any way, as John points out. "Even remounting the partition to rw will tamper block verification!!".
[Magisk] Fry-kun:
To close the loop on my Pixel 6 Pro issue -- using Canary build fixed the issue.

I'll try to post my exact update process in the future to reduce the back-and-forth ;)
[Magisk] Lughnasadh:
What exact issue are you referring to? I know Canary 24305 solved the issue with compatibility with custom kernels on the Pixel 6 (issue brought on with Canary 24302-4 that custom kernels with these Canary versions were causing bootloops and unrelated to updating via OTA/Inactive Slot method) and the issue with having multiple mods written to the same directory sometimes causing bootloops (including audio mods). Is there another issue, maybe related to updating via OTA Install to Inactive Slot method, that you are talking about?
[Magisk] roshan_shahi:
Yes I did remove the system root. Deleted su files using TWRP. I used the Magisk v6, which was working fine till Google updated the their API.
[Magisk] Captain_Throwback:
Then there may be some other reason that ROM is failing. Is SELinux in permissive mode, maybe?
[Magisk] roshan_shahi:
Yes, it's in permissive mode. Tell me if I tried procedures involving SuperSu, would that work? Should I give it a try?
[Magisk] Captain_Throwback:
SELinux might need to be enforcing for it to work. I'd try that. If it doesn't work now, there's probably less chance that it'll work with SuperSU, since that also requires suhide and RootSwitch.
[Magisk] rfgamaral:
I have an HTC 10. Is that the case or something else?
[Magisk] Captain_Throwback:
That is the case.
[Magisk] embql:
magisk+phh+xposed modules - question (and note reg. snapchat)

( I don't play PoGo, but i use root to get xposed and use modules there,
together with some other apps that needs root to function correctly.
I use Snapchat on multiple accounts, that's a tricky one with all the checking going on!)

---

SO, it seems to work on NX6P 6.0.1 running newest ElementalX kernel with phh r259 SU+app installed via magisk and xposed installed via magisk as well + modules from material design xposed installer - EXCEPT:

1: Android N-ify, which is active, but the module doesn't make any changes to the system. Anyone who knows why this is happening?

2: GravityBox (Daaaarnit) - the system framework is not responding - exiting app without ever opening.

Has anyone else tinkered with this? I've searched hundreds of pages and search combos, but not many are talking about this if at all!

The rest of the modules work fine (neopowermenu, securesettings,stayawake,sudohidetindermods,xinsta,xposedadditions,,YTadaway,YTbackgroundplayback)

I'm not really sure of the order of flashing and installing anymore, i've changed from superSU to phh, had the orig. systemless 86.2 xposed until magisk was required for 86.6.. and a lot of other things going on. my bad.

Thank You-note regarding Snapchat, I have my own account which i never log out of, so it's always working, but together with friends we have a shared snapchat account which are logged into from multiple phones, so naturally I get logged out if another phone has been used. (I switch to another user on my phone where snapchat is also installed) That's where having xposed installed and even root posed a problem in the past - but right now it seems that i can login with everything enabled, fantastic!! I'm not sure if magiskHide, xposedmodule SudoHide (hiding xposedinstaller from SnapChat) or suhide (hiding superuser) is playing a part in this.. Well, hope it'll last!
[Magisk] mrxtc89117:
With this setup, are you able to pass safetynet using the safetynet helper app from the Play Store? Assuming, of course, that the sudohide module can hide xposed from Google Play Services.
[Magisk] mrxtc89117:
I tried the sudohide module to hide xposed installer and it does not pass safetynet. I can, however, disable xposed from the xposed installer and it passes.
[Magisk] sakis_the_fraud:
please update the description of the main thread.

In the installation steps, you should add a step to install the superuser app.

I was trying to enable Magisk Hide from the magisk manager and I couldn't figure out why it won't stick, no matter how many reboots I have done! Then I realized that i don't have an app to manage root rights :P

For me its working now, here is my setup:

Sony Xperia Z5 fw 32.2.A.224

stock kernel (dm-verity off)

SELinux enforcing

-------------------------------------------SafetyNet: PASS but NO root

Magisk v8

phh-superuser-magisk-r259

phh's superuser app (from play store)

MagiskManager-v2.1 app

Magisk Hide enabled

-------------------------------------------SafetyNet: PASS WITH ROOT
[Magisk] embql:
I get SafetyNet request Success,

Response Validation Success,

But CTS profile match False :(

Tried hiding xposed from a bunch of google services to be sure, to no avail.
[Magisk] mrxtc89117:
That's correct. You won't pass safetynet unless you disable xposed from the xposed installer and reboot.
[Magisk] chrisg4:
Guys i'm really confused i read about 40 pages before and still i can't find a way to pass safetynet . Which method do you suggest me?
[Magisk] embql:
Interesting part is that the xposed installer seems to remove itself, at least from the app drawer, so right now I'm having a hard time opening the installer (It's the latest download linked from source http://xdaforums.com/xposed/material-design-xposed-installer-t3137758 ) -- Something fishy's going on
[Magisk] mrxtc89117:
Same version I am using. Maybe you are hiding it from the launcher with sudohide.?
[Magisk] desztan:
May I know the sequence to install?
[Magisk] sakis_the_fraud:
I have them listed in the correct order. If it's a zip, flash it, if it's an apk, install it!
[Magisk] gotAndroid10:
Thanks [MENTION=1162986]Captain_Throwback[/MENTION]

Worked for my bootloader unclocked HTC 10 running LeeDroid's latest ROM.

Passed both SafetyNet helper and playground :D

Captain_Throwback posted the latest version a couple of posts below. Thanks
[Magisk] Captain_Throwback:
Please remove that link - that's not the latest version.
[Magisk] Homeboy76:
I agree topjohnwu instructions does specify that there shouldn't be any modifications to the phone: "make sure you haven't modified /system or /vendor or other read-only partitions in any way, as John points out. "Even remounting the partition to rw will tamper block verification!!".

That is in the instructions, what is not in the instructions is what to do if you had a Custom Kernel, Mod, etc. installed. How to remove them so the phone is stock. That is the information members need !
[Magisk] zgfg:
True, but John is 'respobsible' only for what was tampered by Magisk

If you flashed custom kernel it had nothing to do with Magisk and it is your responsibility to KNOW and UNDERSTAND what you tampered and why and how to restore

Or, putting more clear, it should be in the instructions from those who develop and publish custom kernels to describe to their users what and how would they have to restore before taking the OTA.

Unfortunately their instructions almost never address that side - they only care to describe how to install

Frankly, I would consider putting such off-topic (related to Magisk) instructions into the Magisk documentation as pure spamming
[Magisk] Homeboy76:
You're right, developers of Custom Kernels, Mods, etc. should tell members how to remove the Custom Kernel, Mod, etc. and return their phone to

Stock

. Some, not all do provide instructions to return the phone to stock.
[Magisk] Hallohannes123:
(I'm on the newest Mi 9 Lite Xiaomi EU ROM)

Guys I'm scared

I updated magisk canary but wifi wasn't working

I'm actually not sure what I did then but I think I tried to flash my old patched boot AND recovery.img files

Stupidly, I always patched and installed both files because I have the error that it falsely shows ramdisk as false

now My phone is stuck in recovery/fastboot

I thought flashing the original boot.img would fix this but it didn't!

I tried the command to uninstall all modules and flashed the uninstall zip file but it didn't help :(

I also reinstalled twrp and my OS

I really don't want to factory reset

PLEASE HELP I am really stressed right now

I know this is probably my stupidity but I don't know where to go from here

Also: I tried installing Magisk with the zip again to then uninstall it with the zip, but the uninstall always fails
[Magisk] pndwal:
Sorry... Conversion in Age of Zygisk thread... PW
[Magisk] martyfender:
A new Magisk alpha has been released.

# alpha changelog

## Magisk (b1faa5ee-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [App] Added crash statistics

- [App] Allow loading zygisk modules

- [General] Signature Verification

### how to install?

Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool.

By customizing Recovery is not a supported way.

# Upstream changelog

## Magisk (3dc7d77e) (24304)

Fixed several compatibility issues with `magiskinit`

## Diffs to v24.3

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

- [MagiskInit] Introduce new `sepolicy` injection mechanism
[Magisk] Homeboy76:
New Magisk alpha - Information is from

98874be1.zip

# alpha changelog

## Magisk (98874be1-alpha)

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [App] Added crash statistics

- [App] Allow loading zygisk modules

- [General] Signature Verification

- [MagiskInit] Fix Android8.0-9 not installed after booting

### how to install?

Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool. By customizing Recovery is not a supported way.

# Upstream changelog

## Magisk (704f9154) (24305)

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

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

- [BusyBox] Add workaround for devices running old kernels

## Diffs to v24.3

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

- [MagiskInit] Introduce new `sepolicy` injection mechanism

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

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

- [BusyBox] Add workaround for devices running old kernels
[Magisk] Stillhard:
Ladies... Magisk alpha is not Magisk, please make a separate thread for it

As @zgfg noted

Let's focus on TJW Magisk releases here too
[Magisk] Homeboy76:
Sir/Madam, you want a separate Magisk alpha thread, you got it: [Discussion] Magisk alpha General Support
[Magisk] pndwal:
Public Stable and Beta only, as he wanted?

FWIW, vvb2060 is a key Magisk contributor, one of the few who's efforts are publicly recognised by John on his Twitter from time to to time... And as I've mentioned, many innovations & major fixes in Magisk have come from her forks, not all 'Alpha', including most major fixes for MediaTek Magisk compatibility, late boot image (v4) compatibility for new devices, etc, etc.

vvb2060 forks have been where users have been able, effectively, to test 'early release' Magisk fixes for their devices if they were aware, adventurous and willing... Practically all the properly tested/working fixes there have made it into public Magisk...

This is no doubt why discussion of Alpha builds has been tolerated, even expanded on by some XDA staff here; it is no rogue fork, and Devs make every effort to comply with John's wishes.

That's the reason they actually announced the cessation of MagiskHide to occur commensurate with first official public Zygisk builds (John said he wishes Devs would not fork Magisk to perpetuate MagiskHide, but that "Seriously, spending effort on hide modules is much more productive than forks"... and this has happened; there is no more Alpha MagiskHide; unlike some other 'custom' versions of Magisk, and alpha devs spend time contributing to the Shamiko hiding initiative by Canyie. It's also the reason for the name change; John asked (to make clear that it's not official), and that was undertaken.

Make no mistake, alpha is a fork and not official as was clarified here:

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

It is also mainly for Devs and coders who discuss issues in TG alpha forum, not really for public consumption... unless adventurous / maverick... But let's face it, neither is official Canary for that matter!... But it is more 'bleeding edge' than Canary...

This thread has slowly become what it is named, Magisk General Support / Discussion, in a broader sense than originally intended by its OP, John Wu... But if we really want to get back to OP defined purpose, only public builds (not even debug Canary), should be discussed here...

Personally, I think it makes sense to keep the scope broad and tollerant here, as in "Magisk General Support / Discussion"... Sure, the thread is huge, but having multiple discussions, often regarding the same issues, brings it's own problems. 🙃 PW
[Magisk] Stillhard:
Make more threads, like Magisk alpha General Support / Discussion or Magisk Modded General Support / Discussion or Magisk Personal Forks General Support Discussion
[Magisk] pndwal:
I won't keep up in that case. 😕... Even @ipdev isn't keeping up as new OP for 24+! PW
[Magisk] Stillhard:
But let's all be remember that TJW clearly instructed the author of 'Magisk alpha' to 'change' it's 'identity'
[Magisk] pndwal:
Yup, seems slow to implement, sure...

Give 'em a chance; admin members did recently ask discussion group members to propose/ choose names ... Perhaps they're still working through the hundreds of responses! Or saving up for a suitable prize! 😝 PW
[Magisk] pndwal:
Builds on:

Update BusyBox

topjohnwu committed 10 days ago

Builds on:

Release new canary build

topjohnwu committed 2 days ago

👀 PW
[Magisk] pndwal:
Fun OT:

I Just wanna have fun here... And break all the rules...

ANNOUNCEMENT:

Mods / Staff can now be bribed... Officially!:

Check out prices per:

• Amount of rule violations

• Amount of moderators you may insult

• Amount of senior moderators you may insult

• Amount of commercial websites you may spam

• Amount of projects you may kang

• Amount of members we will ban for you ❤️

https://xdaforums.com/t/fvp-forum-violation-passes-now-available.4424853/post-86670993

Get yours quick: going fast! Apply to:

@Timmmmaaahh!

Forum Moderator

😜👏😁 PW

Preemptive edit: be prepared to pay more, all you spoil-sports n kill-joys!
[Magisk] pndwal:
@Timmmmaaahh!

You made my day mate!... And that's a first here... Please stick around n moderate / do your thing!... Do you take (small) deposits? 😜 ...

What day is it anyway?... PW
[Magisk] pndwal:
@Timmmmaaahh!

It's the 2nd down under now... Is the fun all over? ... I didn't insult any mods yet!... Did you get my deposit... Can I have it back?... Please?... 🤪
[Magisk] Timmmmaaahh!:
No refunds! I almost have enough for a private island 🤑
[Magisk] QuietMountains:
Google pay was working earlier but now I'm stumped on what I did wrong to mess it up. Using Magisk 24.3 (24300), I have Universal SafteyNet Fix (2.2.1), and every time I try to add Google Play Services to the denylist it goes away after a reboot. Anyone experience a similar issue?
[Magisk] Lughnasadh:
1st result when searching... @QuietMountains

https://xdaforums.com/search/389809...ces+deny+list&t=post&c[thread]=3432382&o=date
[Magisk] cmonty14:
Hello,

after running uninstall.zip in recovery, I get this error message when starting Magisk (yes, Magisk is still installed):

"Abnormal condition.

Executing this app as a system-app is not supported. Please transfer app into user-app."

Magisk was working before on this device Kindle Fire HDX7 that is running a custom rom.

Therefore my plan is to

1. remove Magisk

2. reinstall Magisk from scratch

Please advise how to fix this error or how to remove Magisk completely?

THX

Solved after deleting /system/app/Magisk.
[Magisk] Mord0rr:
Have to format phone, installed Magisk 19.4 if not wrong with TwRP.

So far so good.

Then, it failed the tests...so i update as recomended.

Now, i loose options of SafetyNet-Test....they dont exist .what can i do?

Op6 with Pie 9.0.9 + xXx rom unlocked, rooted and last Magisk.

thank you
[Magisk] pndwal:
Read back release notes... Search back here... Read OPs first ten posts in new Age of Zygisk thread.... 👍 PW
[Magisk] zgfg:
There are plenty of changes, didn't you read Changelog

There is a new thread Magisk+Zygisk, with a good and valuable OP posts to read (what to use instead of the integrated SN and many, many more tips)
[Magisk] Mord0rr:
I read, that`s why i ask....for a opinion. Also it falis all tests....

Think i gonna uninstall, and flash other version...
[Magisk] zgfg:
There is DenyList now, you have to properly configure.

As I wrote, new thread for the new Magisk, and everything is advised in the OP posts
[Magisk] pndwal:
Good on you...

For others:

Magisk app as a system app​

Another reported reason for the app crashing is if you've for some reason added the Magisk app as a system app. If this is the case try de-systemising to see if that fixes the issue.

There are two Magisk apps​

...

If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the app like this.

👀 PW
[Magisk] pndwal:
Supposed to as zy-USNF hides GMS processes itself. If SafetyNet passing, check you have Device certified for Play protect in Play Store settings... If not, clear Play Services and Play store data. If Certified, ensure Google Pay is in denylist, clear Google Pay data and try again... Will need to add cards again... PW
[Magisk] pndwal:
Things that go clang in the night!

But after a month of juggling:

https://twitter.com/i/web/status/1509756192821694470

... and he's just pushed 4 new action run builds... Go John! 😜 PW
[Magisk] Mord0rr:
Not everybody has the same know how...me included.

Cant read information regarding fail test, or why it disappear.....

Can you cote that part for me?
[Magisk] zgfg:
I advised you to look for this thread:

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

and read there the OP posts 1-9.

You can then also read the post #14 there

Sorry, I'm not going (or anybody else) to waste now two hours to write an exclusive 'guide' only for you (and every second day similarly for some other newbie) and you will then say again that it's too complicated.

As said, everything you need for the beginning is there, and so many other users were able to catch up with Magisk v24 (and before any comprehensive guides were available)
[Magisk] Mord0rr:
Thanks.

Gonna check it. I understand your point. Shouldnt format my phone. It was working flawless...

Long go the times when thingd were more easy and straight.....

Peace.
[Magisk] QuietMountains:
I've got Google pay working and my phone certified but now whenever I try to add a card to my Google pay, Google Play Services launches then immediately crashes. I've cleared the data on it already and that's changed nothing
[Magisk] SolarPlexus:
Hi.

I have a mysterious problem. It looks like that the magisk app was changed or switched without my interference. I had installed and used magisk since a certain time, and was also able to hide the rood against the Microsoft Security part. Then some weeks ago it looks like the magisk app switched bi itself to Magisk 1.0 (without correct icon, just standard Android icon). Since that time I'm not able to restart the magisk app. But all root used apps and hide is still working. I tried to reinstall an actual Magisk app, but this will be installed beside the Magisk 1.0... so I would like to ask what I could do to bring Magisk back to work, without a new installation of the hole phone from scratch. Phone is pixel 4xl still under Android 11 stock.

Thanks for every hint!
[Magisk] zgfg:
I don't know what do you mean by Magisk 1.0 (and you didn't say what is actually your Magisk version? - you must distinguish Magisk app/mngr and its version from the Magisk itself and its version), but from what you say about the icon:

- seems you did "Hide Magisk app/mngr" from Magisk app/mngr, and you didn't complete that properly (maybe you have Magisk v23 or older and that action cannot be done easily now after Magisk v24 was released)

You must uninstall that app we are talking about (with Android icon, that you say you cannot open).

Please don't ask how to uninstall - it's not part of understanding Magisk but using System, Manage apps, finding that app there and uninstalling it (I don't know why some users of custom ROMs are not familiar with or if Android settings look different for them)

Uninstalling that app will not affect your root, Magisk modules, etc

Later, you will have to install Magisk app again - but be careful, if you have the older version of Magisk you will need to find the corresponding old version of Magisk app/mngr - otherwise you will need to catch-up with the latest Magisk v24 (if you are not familiar with all its changes yet)

Since you have no operable Magisk app/mngr, you can find your Magisk version by the following command from Terminal:

magisk -c

(you can try also -V or -v but -c should give you more comprehensive answer
[Magisk] pndwal:
Have you engaged any hiding methods other than those mentioned here?... only GPay (default com.google.android.apps.walletnfcrel process) in denylist? PW
[Magisk] pndwal:
The 1.0 app is the stub apk for hiding actual Magisk app as mentioned. Just uninstall it, and immediately install the Magisk App corresponding to your current Magisk installation which should now function properly... If you reboot with app not installed, Magisk daemon will restore it, but not if it is present. 🙂 PW
[Magisk] QuietMountains:
Aside from USNF that's all I've used to hide Gpay. I'm hiding other apps on the deny list and they're working fine
[Magisk] pndwal:
So I'm assuming 1 process in GPay and no other Google stuff... PW
[Magisk] SolarPlexus:
Thanks to that explanation. It worked properly. I was a little bit worried just to deinstall it, because I feared that then also the allowed roots and hides could be lost. But now I know it better ;) so thanks!
[Magisk] pndwal:
Previously that's what you would get if you simply uninstall app and reboot; this would call stub to initiate installation of Magisk App... Using Hide the Magisk app function on the other hand gives 'Settings' 1.0 by default. I have:

I just uninstalled this to do my own test (I have latest Canary); rebooted and found daemon hasn't installed stub / doesn't seem to install stub any longer!

I think this has changed the behaviour:

Directly stream apk into install session

vvb2060 authored and topjohnwu committed on 2 Mar

Still not sure of this / what's changed, but it may be good news for those wanting to permanently uninstall Magisk app as reboot would always restore stub app previously... PW