yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
It looks like you have probably tried changing Magisk App either previously or with downgrade without unhiding (restoring hidden App), and now have the typical conflict between two installed Magisk Apps that often results.

Steps to resolve:

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

Hope that helps. 😛 PW
[Magisk] toolhas4degrees:
Magisk hide props config works now for latest, you need to to denylist with play services and play store. Don't know if the have fingerprint for pixel 6 yet though
[Magisk] pndwal:
It's complex with a number of issues extant.

If it turns out to be same as this issue with init.rc:

https://github.com/topjohnwu/Magisk/issues/4319

fix from @canyie is already merged and will be built in next release.

If this is same:

https://github.com/topjohnwu/Magisk/issues/4394

some found old 21.4 works.

This one has a hexpatch workaround for AVB flags:

https://github.com/topjohnwu/Magisk/issues/4447

Could be a completely different issue too; you need to connect the dots or wait I guess! 😜 PW
[Magisk] pndwal:
Can use 23.0 public release. That was synced with 23001. Only dif is debug logging:

https://github.com/topjohnwu/Magisk/releases/tag/v23.0

If really want canary:

https://github.com/topjohnwu/magisk-files/find/4f737b70868eb3f8b71e48518f919819cbf5ad63

Re. .zip installer:

https://topjohnwu.github.io/Magisk/install.html#custom-recovery

What device? 👍 PW
[Magisk] pndwal:
In the past this has occurred when kernel was 'too old'. I'm guessing it could be connected to kernel issues in your Arrow build also... PW
[Magisk] pndwal:
Latest kdrag0n

Universal SafetyNet Fix Changelog:

• v 2.2.0

Changes since 2.1.1:

• Ported module to Zygisk

• Fixed screen-off Voice Match in Google Assistant

• Fixed poor microphone quality with Voice Match enabled on Pixel 5

• Fixed At a Glance weather display on Android 12

• Fixed At a Glance settings on Android 12

This version only supports Zygisk (latest Magisk Canary). See v2.1.2 for a Riru version.

Download

This version is currently only available to early access supporters. (Pledge now to get access or purchase one-time access.)

https://kdrag0n.dev/patreon/safetynet-fix/v2.2.0

👍😛 PW
[Magisk] toolhas4degrees:
I ditched riru since latest lsposed zygote doesn't require riru with zygote, maybe kdragon can alter his to do the same
[Magisk] pndwal:
That's what this means... 😬 PW
[Magisk] hfam:
Well, another reading Marathon tonight and I can't find a definitive answer:

Can I update my Pixel 5a on stock A11 and Magisk 23 to stock A12 and still use v23, or do I need to go canary?

My intention was to do as I have forever and update by blasting full 12 system image (del -w) and re-patching boot.img with Magisk 23.

Am I out of luck, or will the old tried and true method using Magisk 23 work?
[Magisk] Didgeridoohan:
Magisk v23 should work on A12 (for the Pixel 5a), but if you're not already aware this could be important reading:

https://xdaforums.com/t/rooting-android-12-with-magisk-on-pixel.4354083/
[Magisk] toolhas4degrees:
Misread the 212 part lol.
[Magisk] hfam:
As always, thanks for the quick and super helpful reply!! That link is VERY interesting and absolutely relevant, saved my bacon, again, eternal thanks. I've got some studying to do for sure! There's some reference links in there I'm going to go read through to understand in detail, but as far as I can tell, the cleanest way to proceed is to do a full image overwrite, wiping /data, but

In the meantime I've got a couple clarifying follow ups to that thread if you'd be so kind, some things I'm not familiar with:

When they say "flash vbmeta" in recovery, is vbmeta.img part of the factory image

<Ugh, my entire reply just shat itself. Let me retype it all clearly, damn it...gimme a few>
[Magisk] Didgeridoohan:
It is, but as far as I can see the instructions talk about flashing vbmeta with fastboot not recovery.
[Magisk] danielxpa:
Thank you. I understand. I tried to look for /data/adb, but I cannot see the folder. The folder \Android\data\com.topjohnwu.magisk\files is empty.

Is it a hidden folder?
[Magisk] zgfg:
You need root explorer like MiXplorer for /data, with root granted

On A11, Magisk working for me (I'm on Magisk Custom, 23011) but /Android/data/com.topjohnwu.magisk (Internal mem) has two folders cache and files but both are empty - and btw, Msgisk does not install things here but to /data/adb
[Magisk] danielxpa:
Ok thank you. I have tried to open an explorer which are able to use root. Unfortunately it says that the root access is not complete.

Edit: I have an backup from 23th October with Titanium Backup. Would a reset of the phone help out of it?
[Magisk] hfam:
Sorry brother, I was all over the place, trying to edit, clean it up and destroyed a bunch of it.

You are correct. The vbmeta line is indeed with fastboot. I got a few issues tangled, let me clarify:

It seems that the issues outlined can be avoided by a clean flash of the A12 system image using that 2nd fastboot line in the thread, the -w wipes /data. From there, once the system is done setting up, install Magisk v23, patch the boot.img, flash the boot.img (just like before) and it will take thebimg and give root

The problem then becomes monthlies. It's stated that:

"The only workaround, discovered by @HumorBaby , is to sideload the OTA via recovery, then immediately enter fastboot without rebooting, and flash /vbmeta with disable flags, then /boot. This does not always work and sometimes results in the device going into Rescue Party anyway."

I have absolutely no idea what that is or how it's done. I understand what's happening in a general sense: load the OTA to avoid clean install and wipe, then somehow catch fastboot before it reboots into the update, then in fastboot flash /vbmeta with appropriate flags to disable verity etc so the boot.img isn't rejected, and /boot. How does one patch the boot.img from the OTA *before* you boot back in rootless and use Magisk to patch it? For that matter, how does one side load an OTA from recovery? That caveat at the end about not working and going into rescue party sounds bad, is there any fixing it if that happens, or are you back to a clean flash/overwrite situation?

I've only ever done the "flash-all" method on full images. When they discuss flashing vbmeta and boot (except the lines needed to flash the patched boot.img) outside that process I have no experience with that so I get uncomfortable pretty quickly and completely lose confidence in myself when I'm reading and learning. As always I'm happy to do the legwork, but it's still hit and miss. I understand the why, but some of the procedures are uncharted territory.

So, I think I understand that a clean install is required to begin the migration to A12, and if I use that fastboot line in the thread, I can then install magisk 23 and patch the boot.img, flash it, etc, and I'm on A12 rooted.

What I do once the monthlies start rolling out is another story entirely. Can anyone clear that process up, including steps for "sideloading an OTA via recovery". Does it require a custom recovery? I just need a bit of direction on how that will all work and what exactly do I need to do to install future updates.

Sorry for the wall, and I appreciate the help and patience more than words can say. Thanks,

hfam
[Magisk] Didgeridoohan:
@hfam I believe the important part of that "workaround" is to install it by sideloading through adb from recovery (described on Google's full OTA page) and then reboot directly to bootloader/fastboot after applying the update.

I wouldn't be surprised if you'll have to do that on every OTA from then on, but that's just me guessing...

If you've got further queries and questions I suggest you ask in that thread. You'll have a much better chance of getting an answer from someone that actually know that they're talking about (rather than someone like me who only make what could be called "educated" guesses).
[Magisk] Nightf0x_007:
Mi 11
[Magisk] Homeboy76:
@hfam

AFAIK: This only works when upgrading to Android 12 from Developer Preview Beta 5.

[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**

[GUIDE] Upgrade Beta to Android 12, *keep* root and data (no wipe!)
[Magisk] Lughnasadh:
We'll probably find out tomorrow when the new factory images are released. Those currently on .019 can upgrade to .036 (or higher if they release a higher version) and see if the sideloading of the OTA method works without having to wipe.
[Magisk] Qnorsten:
Thank you both for your updates, hadn't had time to try some of your suggestions until today.

I had already tried latest magisk alpha with magisk hide enabled, togheter with riru and riru-momohider configured to pass all momo checks, without any luck with Freja eid.

I tried to activate Riru-LSposed and Hide My Applist and configured it to hide all my root applications from freja eid. I am still unable to use any version of the freja eid newer than 8.5.0 (That still work fine even without magisk hide enabled for it). So I can just keep using that for now, but it won't work forever.

Which version did you try zgfg? if you used the latest I guess I just need to keep trying to figure out what it detects on my phone.
[Magisk] shoey63:
Here's what I would do:

- take ota update

- use magisk to patch boot image on opposite slot after ota

- use DD command in terminal to flash a Verity/verification disabled vbmeta.img to opposite slot

- reboot

- profit ????
[Magisk] zgfg:
I tested with what was the latest on PlayStore that day
[Magisk] Nekromantik:
I think the theory is you flash OTA via fastboot/recovery and then reboot back to fastboot to disable verity so that it dont boot with a changed image.
[Magisk] Soumy1234:
Does anyone know what happened to TheHitMan's MagiskCustom build? The telegram group got deleted and I think there was an announcement but I didn't get to see it.
[Magisk] J.Michael:
What are you doing? @pndwal suggested you look for, and remove, previously hidden copies of Magisk Manager app. That does not involve manually deleting files. You should be examining your apps drawer, trying to spot apps which are really renamed versions of Magisk.

I've never done this. I assume you can pick out the copies by icon or name. I assume you can confirm by looking at the app info. Failing all that, I would uninstall the Magisk Manager app you *can* recognize, then try running any app that might be a renamed Magisk Manager. If it comes up looking like Magisk Manager, uninstall it.

When you've removed all Magisk Manager apps, and rebooted, you can install one Magisk Manager app and see if your problem is solved.
[Magisk] zgfg:
Unfortunately, he announced that he was closing.

He released one more, saying it will be his latest to stay as Stable

I was out, just read that and wanted to download when I come home - but now, all is gone, his channels and GitHub page.

Sad, because it was (for some of us who used) currently the best and most useful version of that new Magisk
[Magisk] Soumy1234:
Damn. Looks like I'll have to switch builds yet again...
[Magisk] oldbear3:
Hi. Sorry if my question has already been asked many times before :I upgraded my Pixel 3a to Android 12 recently via an OTA update. I have put the root back on Magisk in the latest version (version 23011) and my phone indicates at startup that the bootloader is unlocked. I changed the kernel to ElementalX in last version. I uninstalled Riru and USNF as I read that it didn't work anymore since Zygisk. However, when I checked if my Android passed SafetyNet by installing the YASNAC application, it said "Fail" for both "Basic Integrity" and "CTS Profile". It said "HARDWARE_BACKED" for the evaluation type and "RESTORE_TO-FACTORY_ROM, LOCK_BOOTLOADER" for Advice.

After reading some elements on this forum, I added both com.google.android.gms and com.google.android.gms.unstable, and added MagiskHide Props to come back to Basic evaluation type.

But, for the moment, CTS Profile Match remains in Fail.

How do I pass the SafetyNet? Did I make a mistake?
[Magisk] bradical711:
Well in the screenshot, it says you are using a "nexus 5".. you said you have a pixel 3a... That would cause a CTS profile to fail. Another thing is I would downgrade from canary magisk (23011) back to stable magisk (23000) and reinstall riru + USNF. You don't need canary magisk to root A12 on the 3a because they didn't change the bootloader format. That only applies to the 5a series and above. I would also assume you have Magisk Hide Props Config and used that to change your device model. So just change it back to your original device with MHPC and all should be good.
[Magisk] hfam:
Thanks @Didgeridoohan, I'll read up on that link and take your advice. I suspect you're right on future OTAs, though if there ends up being a process that does work consistently I'm ok with it as I've always updated via ADB and full images anyhow. Just never used OTA so I'll need to get caught up on that process.

Thanks also to the folks who weighed in as well, I will take all the suggestions and figure out what works in the end as well as keeping a close eye on and participating in this thread for the foreseeable future. I'll share my results, and thanks again all.

hfam
[Magisk] danielxpa:
I have not access to the specified hidden folders which are described. I have checked the apps drawer, deleted there the user files, the cached - uninstalled the version and reinstalled it new. Afterwards I patched the boot image and flashed it with fastboot. Unfortunately no difference.
[Magisk] pndwal:
Did you look in device settings, apps, manage apps or equivalent for an app named 'Settings' that is actually Magisk App? PW
[Magisk] J.Michael:
I do not know where you read about hidden folders. The "hidden Magisk Manager app" is an app, you do not use a file manager to find or delete it.

I do not understand deleting "user files" or "cached" in the apps drawer.

"uninstalled the version and reinstalled": version of what? If Magisk Manager app, I do not think you should immediately reinstall. You should uninstall every instance you can find. And tell us if you find more than one. And reboot.

All of this was based on the assumption that you had Magisk installed and working, then installed another Manager app. You should not reinstall Magisk -- meaning no new patch and flash. If your problem was caused by a hidden and forgotten Manager, the fix is removing all Managers, then eventually installing one Manager app. At that point, we expect the already installed Magisk will become accessible to the Manager, and you will be back in business.
[Magisk] pndwal:
Universal SafetyNet Fix GitHub page explains the aspects of fallback to Basic attestation that you need and how it is achieved.

My notes on passing:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85825005 👍 PW
[Magisk] Eng.Raman:
I have downloaded the latest custom magisk stable version 23.1 (23100) before he decide to delete the telegram channel. If anyone want to try it ( in attachments ).
[Magisk] zgfg:
Did you try it? Before releasing he mentioned that he would change the package name
[Magisk] Eng.Raman:
Yes but the package name still the same (com.topjohnwu.magisk) and it is really stable.
[Magisk] Eng.Raman:
However, it can no longer be used because he also deleted the github page therefore you cannot hide the magisk app with a random package name. or download the snet api.
[Magisk] zgfg:
Yeah, every time I open the integrated SN checker it asks me to download and then reports the API error. However, the SN passes by all other checkers

So I made a mistake, even if I go back now to his previous cb3a210d it would be the same - but if I stayed on cb3a210d (where I already had downloaded FOSS) its SN checker would continue working
[Magisk] Eng.Raman:
But you cannot repackage the magisk app with a random name.
[Magisk] zgfg:
I never need that (if I need to hide I could use HMA)

But now upon 'updating', I cannot even downgrade back to his version that worked fine (I mean, I can but cannot 'restore' its integrated SN checker)

After all I think I should better switch tomorrow to Alpha and forget the episode with Custom
[Magisk] Eng.Raman:
Yes i think the better magisk version available now is the magisk alpha with magisk hide support and denylist ( it will serve as a real hidelist when zygisk disabled and denylist when zygisk enabled).
[Magisk] zgfg:
Custom was better because it still had Repo and SN checker integrated. Plus I never needed DenyList - but now is gone

Actually, he announced that he was stopping development due to the lack of time (sad but understandable) but that he will release a final, Custom Stable to stay (where else than on Github?)

Apparently he changed his mind when he deleted not just three TG channels but also his Github project

Don't know why but seems he wanted to fully erase everything about
[Magisk] pndwal:
I think there may be more to it.

I wondered about 'Custom' Magisk's purpose (again) when I read this:

I have also noted the reason we lost @ianmacd custom Magisk builds back in September 2019:

https://xdaforums.com/t/unofficial-...magiskmanager-snapshots.3521901/post-80310793

Seems likely there's been some communication re. / rethinking propriety of this fork also.

Still feel (hoping) 'Alpha' (with name implying test builds only) may be viewed by John in an entirety different light, but I've been wrong before! (All is sure to come out in the wash.) 😬 PW
[Magisk] zaczatowany:
Hi guys, how to enable MagiskHide?

I installed MagiskHideProps 6.1.1 config and enable it, after this i rebooting my Phone, now try to enable MagiskHide in MagiskManager settings but... when i leave Magisk Manager settings and back to settings, Magisk Hide still disabled.
[Magisk] pndwal:
Please give screenshot of Magisk home-screen, and say device / ROM... PW

Edit: ok, seems you have Samsung Galaxy S20?

And screenshot showing old Manager and no Magisk mask installed... Please give current details / status...
[Magisk] 73sydney:
that dude had issues, whenever any of us reported a bug, we would be met with:

"fix it in your own build"

im not surprised he scrubbed everything

its actually good news, one less fork, and one less to test
[Magisk] zgfg:
Nobody force you to use alternative builds

Stick with the official if better for you

If you didn't follow the TG channel you don't know but if there was a problem, hitman asked for logs, tried himself and fixed
[Magisk] zgfg:
Unfortunately, I was also thinking there might be something like that (and I would not be surprised if G is involved somehow)
[Magisk] m0han:
Magisk Custom chat no longer accessible

edit: is the one here cb3a210d?
[Magisk] zgfg:
Not exactly, read the subsequent replies between @Eng.Raman and me

You can still install that one or the right cb3a210d (all in those subsequent replies) but now with caveats:

- integrated SafetyNet checker will return API error

- you can not do Hide Magisk app

That's because the aurhor (voluntarily or not) deleted his Girhub project (while both features as above require connection to the Github)
[Magisk] miss:
magisk 23, safety passed everything correct, hidden application, hidden magisk, bank applications ok I can pay without problem. but the application my bmw detects me root and does not start ,,,, it says root device. any idea thanks
[Magisk] Didgeridoohan:
No issues starting it here. Although I used Canary build 23011 and the Deny list. Could be that the app is detecting something else than Magisk:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Eng.Raman:
Worked for me just by adding it to the denylist of magisk alpha-a3eafdd2, install riru-momohider and make sure you are passed all the tests of magisk detector especially the first one ( su file does not exist in PATH ).
[Magisk] danielxpa:
Yes at the moment there is only magisk shown. Maybe I was a little bit confused some days ago with the Magisk manager since it had not worked and I tried to install the Magisk Manager. But I uninstalled the Magisk Manager again.
[Magisk] danielxpa:
I tried to delete within the app drawer as much as possible from Magisk in the app drawer. At the moment I only have the Magisk version installed and not the magisk manager. I had installed some days ago the Magisk Manager since I hoped that it could work with it. But since no effect was there I uninstalled it again. So at the moment I have magisk 23011 installed.
[Magisk] zaczatowany:
I have S20 Ultra (G988B) and BeyondROM v3.7

Magisk Manager v23 , Magisk v23010 and active modules as on the screen. I don't know how to permanently enable MagiskHide because it's turning off everytime i leave Magisk Settings menu.
[Magisk] Soumy1234:
Try doing a complete uninstall of Magisk and install it again.
[Magisk] pndwal:
Ok, you have updated Magisk (mask) to later (but not latest) debug Canary build, but have old public Stable/Beta Magisk App. Nb. new Magisk does NOT have MagiskHide (this is why it's not working in mismatched App); it's been replaced by Zygisk and denylist. This can still pass SafetyNet using updated methods.

Not sure how you got there, but the two should match.

Normally you'd update App first then take direct install to update Magisk to same version, or download and install the App you want, then Patch / flash boot image for initial installation. Both methods result in matching App / Magisk.

You need to change channel to Canary to see latest matching App then update that, or simply install Magisk (mask) again from the App (as shown, with Stable or Beta set) using Direct install to downgrade to old Stable version matching current App (this will restore MagiskHide). 👍 PW
[Magisk] heinhuiz:
Is there any good reason to update to a canary or alpha build if stable 23.0 does everything you want from it - apart from curiosity to where Magisk is heading with zygisk?

I'm surprised seeing so many people installing unstable builds and running into problems.
[Magisk] pogo-airsupport:
I believe newer devices like Pixel 6/Pro will need the canary/alpha builds to work.
[Magisk] Didgeridoohan:
There are way too many people that update just for the sake of updating...
[Magisk] manyone:
get in trouble with Magisk installation.

last time i am using the TeamEyKings android8 image and the included aromainstaller and i think Magisk cames automaticly with this but it's a long time ago and i'm not sure if i remember right.

Now i want to install LOS17.1 (with root that makes me trouble too) and Magisk but i dont understand the installation instructions.

Isnt there any easy to install package ?

my Problem is, i want to install it on S7 and within the description it tells me to download an original FW Image but for S7 i can't download Original Images with Android 10

So i have no Idea what i can do, can anyone tell me a solution ?
[Magisk] rodken:
Wasn't there also the fact that the reason why @ianmacd jumped shipped was due the cease and desist letter that TJW sent to @ianmacd?
[Magisk] zaczatowany:
Now i have Magisk 23011 and Magik Manager 23011. And working Zygisk and DenyList. But still Google Pay not working. I picked Google Pay in DenyList configuration. What can i do to SafetyNet passing?
[Magisk] J.Michael:
Have you installed LOS17.1?

Does it give you root?

Do you have some other reason for wanting Magisk?

Once you have installed LOS17.1, then, for your purposes, LOS17.1 *is* your "original firmware image". In instructions for installing Magisk, "original firmware image" means "firmware that is running and into which you want to inject Magisk".
[Magisk] Didgeridoohan:
"Cease and desist" makes it sound much more dramatic than it was...

https://xdaforums.com/t/unofficial-...ager-snapshots.3521901/page-165#post-80310793
[Magisk] rodken:
I guess that I was putting a bit too much icing on the cake on that issue.
[Magisk] ultimatepichu:
Been reading for the past few hours and I still don't really get it - what is the updated method? kdrag0n's USNF v2.2 which is locked behind patreon? Is that it?

Yea, sorry I was one of them. Went to check the new stuffs, be a coolkid wannabe. Not sure if DenyList is just like MagiskHide - toggling some checkboxes to prevent detection. But GooglePay failed to work, probably because SN failed. Now I'm back with the camping guys :D