yashsingh1/xdaforums huggingface dataset:
[Magisk] Spookymyo:
I'm on a rooted Pixel 4 running android 12, SP1A.211105.002.A1.

Magisk canary channel.

My module list is empty. I've done the troubleshooting steps I've found online but they don't work or aren't available. There is no clear repo cache anymore. I've uninstalled and re-installed. Cleared app cache. Restarted the phone. Even reflashed the OTA and re-rooted. Module list is always empty. And I can't downgrade to the beta or stable channel so I can look at the module list. I have to uninstall the magisk manager app then reinstall the stable version. Then the modules show up. And I can install them that way. But when I go back to canary the list is blank again, the modules I installed still show up though.

I don't want to have to uninstall canary and reinstall stable just to check for module updates.

Any suggestions?

EDIT:

Shortly after posting I saw the post on the new Fox Magisk Module Manager. It's not an official magisk app but it works.

Release 0.1.2 Update · Fox2Code/FoxMagiskModuleManager

Add Traditional Chinese Translation by @cracky5322 Add fallback support links for a few modules

github.com
[Magisk] zgfg:
Its bern really tens/tons of times commented here that TJW had removed Modules Online section (repo) - it's worth of reading and following discussion in the thread (before asking in surprise)

Alternatives were also mentioned here - particularly there was a post about FoxMM

Anyway, yes, that's the way to go
[Magisk] klemi71:
A bit off topic, though hoping for support.

My device doesn't have a working TWRP (Pixel 3). Is there a way to create a Android backup to fully restore my device after upgrading to official Android 12? The device is end of support and I just don't want to miss being up to date for security reasons. I'm unsure if I should switch to LineageOS right now or stay on official version (which should get an update in February) and wait till LineageOS goes Android 12, expected next spring. I just want to try official version and be able to go back without having to do clean install.
[Magisk] zgfg:
I doubt you could make something like Nandroid back-up, and I've seen a lot of complaints to Titanium

But there is really a good root back-up app Swift Backup (I think somebody posted here long ago and I happily started to use). You can back-up apps, their settings and data, calls and messages, WiFi passwords

Swift Backup is available on Google Play
[Magisk] zgfg:
Thanks, I confirm, it works. I put it yesterday, since then I had rebooted several times, all my LSPosed modules work and Momo does no more complain about the Art
[Magisk] 73sydney:
@zgfg @pndwal

zgfg, Marvin

just reporting in that in a fit of actual progress i decided to test something other than my beloved Magisk Alpha 31, and threw Magisk Custom on here a few days back afetr seeing @zgfg 's post about the latest update. Zygisk turned off, MagiskHide on, hidden app, Momohider with all switches...no drama...all is working my end..but you'd kinda hope so with those settings
[Magisk] sq_dev:
@G996U

On the current Android 12 Samsung G996U firmware, magisk cannot mount the partitions. Accordingly there are bootloops. Does anyone already have an approach?
[Magisk] pndwal:
Have you tried latest Canary? Fixes incl. bump to API Level 31 (Android 12), fix pure 64 bit devices, etc... PW
[Magisk] sq_dev:
Yes. Here logs from last_kmsg (rooted recovery):

<12>[ 74.898366] [7: init: 1] magiskinit: mount /dev/LOQA3/.magisk/block/data->/dev/LOQA3/.magisk/mirror/data failed with 22: Invalid argument
<12>[ 74.898372] [7: init: 1] magiskinit: Setup cache: [sda29] (259, 13)
<12>[ 74.901606] [7: init: 1] magiskinit: Replace [/dev/.se] -> [/dev/.se]
<12>[ 74.901622] [7: init: 1] magiskinit: Replace [xxx] -> [xxx]
<12>[ 74.902779] [7: init: 1] magiskinit: sepol: no selinux
<12>[ 74.902794] [7: init: 1] magiskinit: Restore backup files locally
<12>[ 74.902951] [7: init: 1] magiskinit: fopen: /init.rc failed with 2: No such file or directory
<12>[ 74.902958] [7: init: 1] magiskinit: Inject magisk services: [SRKc4GD5] [RvWNIQ4cJI] [nsW8FAwpUkN]
<12>[ 74.902970] [7: init: 1] magiskinit: lstat /init.rc failed with 2: No such file or directory
<12>[ 74.907948] [7: init: 1] magiskinit: Replace [d30138f2310a9fb9c54a3e0c21f58591] -> [9Ct4688AatFyVj]
<12>[ 74.914131] [7: init: 1] magiskinit: Replace [d30138f2310a9fb9c54a3e0c21f58591] -> [9Ct4688AatFyVj]
<12>[ 74.914310] [7: init: 1] magiskinit: Mount [.magisk/rootdir/init] -> [/init]
<12>[ 74.914346] [7: init: 1] magiskinit: Unmount [/dev/LOQA3/.magisk/mirror/system_root]
<12>[ 74.915456] [7: init: 1] magiskinit: Unmount [/dev/LOQA3/.magisk/mirror/cache]
<12>[ 74.915806] [7: init: 1] magiskinit: SecondStageInit
<12>[ 74.915963] [7: init: 1] magiskinit: Setup Magisk tmp at /dev/YYTyS3y
<12>[ 74.918888] [7: init: 1] magiskinit: Setup userdata: [sda35] (259, 19)
<12>[ 74.919852] [7: init: 1] magiskinit: mount /dev/YYTyS3y/.magisk/block/data->/dev/YYTyS3y/.magisk/mirror/data failed with 22: Invalid argument
<12>[ 74.919858] [7: init: 1] magiskinit: Setup cache: [sda29] (259, 13)
<12>[ 74.922830] [7: init: 1] magiskinit: Replace [/sepolicy] -> [/dev/.se]
<12>[ 74.922857] [7: init: 1] magiskinit: Replace [/system/etc/selinux/plat_sepolicy.cil] -> [xxx]
<12>[ 74.923869] [7: init: 1] magiskinit: sepol: no selinux
<12>[ 74.923884] [7: init: 1] magiskinit: Restore backup files locally
<12>[ 74.924034] [7: init: 1] magiskinit: fopen: /init.rc failed with 2: No such file or directory
<12>[ 74.924049] [7: init: 1] magiskinit: Inject magisk services: [HWu1e0Fx] [D2wiBumMnUWFi] [jSHITzf]
<12>[ 74.924062] [7: init: 1] magiskinit: lstat /init.rc failed with 2: No such file or directory
<12>[ 74.929077] [7: init: 1] magiskinit: Replace [d30138f2310a9fb9c54a3e0c21f58591] -> [qDwS2tmfZpwlk]
<12>[ 74.935290] [7: init: 1] magiskinit: Replace [d30138f2310a9fb9c54a3e0c21f58591] -> [qDwS2tmfZpwlk]
<12>[ 74.935453] [7: init: 1] magiskinit: Mount [.magisk/rootdir/init] -> [/init]
<12>[ 74.935489] [7: init: 1] magiskinit: Unmount [/dev/YYTyS3y/.magisk/mirror/system_root]
<12>[ 74.936597] [7: init: 1] magiskinit: Unmount [/dev/YYTyS3y/.magisk/mirror/cache]
<12>[ 74.936952] [7: init: 1] magiskinit: SecondStageInit
<12>[ 74.937116] [7: init: 1] magiskinit: Setup Magisk tmp at /dev/QfHyJ
[Magisk] pndwal:
Can you supply logs here?:

https://github.com/topjohnwu/Magisk/issues/4949#issuecomment-971542665

Devs need them.

(Trust you are using boot image from the current Android 12 ROM, unlike this case:

https://github.com/topjohnwu/Magisk/issues/4745 )

👍 PW
[Magisk] elong7681:
I'm on A12, Pixel 5, Magisk Canary, Manager ver. (23014) (22) I'm using Zygisk, Enforcing DenyList and Configured DenyList, SNF ver. 2.2.0, I have factory reset my phone and did not restore data and I've set toggles on for Google Play Services and for some reason the toggles turn them selves back off and I can not pass SN. Can someone help me out?
[Magisk] pndwal:
It's by design "because Zygisk modules don't load for apps on the DenyList." This commit:

https://github.com/kdrag0n/safetynet-fix/commit/cd84bf361f1514601a99bcd2fb027528fc16f612

Explanation:

https://github.com/kdrag0n/safetynet-fix/issues/122#issuecomment-971822265

Not passing SafetyNet is unrelated; please say YASNAC results (Basic Integrity, CTS Profile match, Evaluation type), ROM etc.

If ROM is uncertified (China region stock, custom etc) you will need to set certified fingerprint which is out of scope for USNF. Use MagiskHide Props Config. 👍 PW
[Magisk] elong7681:
CTS Profile is false, Basic Integrity passes, Evaluation Type is Basic A12 Stock Firmware
[Magisk] pndwal:
Ok... Some modules (EDXposed, MHPC w/ unnecessary changes, etc) break SafetyNet. Try with all modules other than USNF disabled.

Next, if you had other Xposed, use LSPosed.

Also, does Magisk Installed version match App Installed version 23014? PW
[Magisk] elong7681:
Only Module installed is BusyBox and USNF 2.2.0 Yes Magisk App and Magisk match
[Magisk] pndwal:
Did you flash TWRP? Any mods from TWRP? Custom kernel? Is anything in Denylist?

Also, try clearing Google Play Services data... PW
[Magisk] awshirley:
I need some help with trying to get GPay to work again. A few days ago it stopped working and I saw that Magisk Hide isn't supported any longer. I'm using Lineage OS 18.1 on a Pixel 3 XL..

The installed Magisk modules are:

1. MagiskHide Promps Config 6.1.2-v137

2. Riru v26.1.3

3. Systemless Hosts 1.0

4. Universal SafetyNet Fix v2.1.2

I know there's a canary version of Magisk, but there's not a clean way to install it with Lineage on a 3 XL. I also need to get the reset of the root aware apps working too.

Any help on what to install and the order would be most helpful. It's upsetting that TWRP doesn't work with my phone and every time I try something, it messes it up and I have to reinstall Lineage from scratch again.
[Magisk] knipp21:
This fixed my issue

That being said

Flash uninstaller

Magisk

259

Franco kernel

Safety net fails.. Not a bog deal. But did want to report that it fails with nexus 5x
[Magisk] :
hello, how do i make magisk do this? {Magisk will remove verity / forceencrypt (both are configurable through .magisk file), and patches sepolicy}

i have installed magiskv8.
[Magisk] Captain_Throwback:
How do you make it do what? It does those things automatically, like it says.
[Magisk] Iceyogurt:
Sorry, I said it wrong. What I tried to port is ViPER|Audio_5.4_Stock and there is binary files in it. As for the fix, I'm not much sure whether it works or not. I tried to add the fix in magisk flashable zip once, then I lost root, SuperSU. But using Magisk also make su lost on my device sometimes. Anyway, more tests are needed.
[Magisk] mathy007:
You're doing it wrong first flash kernel before magisk read the official post
[Magisk] Iceyogurt:
Wait a moment, bro. Rootswitch only works with SuperSU since it mount and mount /su during switch. I don't think there is any solution to make it compatible with phh's superuser yet.
[Magisk] BananaYoghurt:
Works fine on LG G5 H850 (stock kernel, stock rom, phh superuser, magiskhide). I hope that it will be possible to hide xposed.
[Magisk] Captain_Throwback:
Not sure how that would be possible. And I'm almost certain [MENTION=4470081]topjohnwu[/MENTION] isn't working on it.
[Magisk] waylo:
WHAAAAA? Hmm. I have the H830 and have had no luck with this arrangement. What method did you use to unlock your bootloader?

Is your /data encrypted or unencrypted?

Can you run this through a terminal:

getprop ro.boot.verifiedbootstate

and tell me the color it returns? Should be green, orange or red.
[Magisk] knipp21:
It's been discussed in this thread that when you flash isn't an issue..

Imagine having to start from scratch every time Franco updates his kernel

Just for giggles..I did that...started from scratch.

SN is blue if I don't hide magisk

Enable magisk hide and it switches to red.

I'm pretty sure its detecting my bootloader
[Magisk] BananaYoghurt:
I decrypted /data (format in TWRP) because Flashfire wasn't working with Magisk. My bootloader is unlocked (via unlock.bin from official LG site) and that prop returned orange, but I'm using xSetProp module (Captain_Throwback posted it) so it's now green.
[Magisk] andrew2432:
How did you flash magisk 8?I am unable to get a recovery on my g2. It's a generation less, idk if there's MM for the g2. Any recommendations?

[MENTION=4540020]AbiDez[/MENTION]

You went from a rooted phone with chainfire superuser? Using twrp? My plan was to use odin to install twrp, skip the cf su and Uninstall step
[Magisk] hokiealumnus:
Sorry, I know absolutely nothing about the G2. I have TWRP and flashed from there.
[Magisk] AbiDez:
Yes, normally I use SuperSu, but for magisk it seems phh superuser is better, specially for hide, because Magisc won't hide SuperSu.

CarHDRom V.24.7 by Carotix S6e
[Magisk] nkk71:
I am using 6.0... only now checked the 7.0 (aosp, cm, omni), and yep, they seem to have added a commit from about a year ago, I neither noticed, nor do I have much to test this on, stumbled on it by "mistake"

my bad, will try to fix over the weekend, hope I can get a small manifest though.... hint hint [MENTION=1162986]Captain_Throwback[/MENTION] :o
[Magisk] Xanderace804:
Need help!

Device: SM-N900P

Sprint Samsung Galaxy Note 3

ROM: Flashed from this thread:

http://xdaforums.com/note-3-sprint/development/rom-twrp-flash-ok2-n9000p-t3301897

Hardware Version: N900P.12

Software: N900PVPUBMI3, running Lollipop 5.0

Baseband: Same as software

Build: LRX21V.N900PVPUEOH1

Kernel: 3.4.0-4453878

Problem:

I can install Magisk, but upon reboot after installation, the phone becomes unstable, constantly notifying me that "Unfortunately, Phone has stopped working," every 2-13 seconds, and also "Unfortunately, Samsung Keyboard has stopped working," which appears less frequently, but both eventually cause the system to soft freeze.

The ROM I am using is stock rooted (see link above for more details), and I am using MI3 baseband for unlocked SIM purposes, however I did full unroot via Chainfire's SuperSU app (Full Unroot option [unrooted status verified by Root Checker app], flashed Magisk via TWRP, reboot, flash phh, reboot, etc. but still causes these issues upon Magisk v6-v8 installation. Any ideas?
[Magisk] Constrabus:
Are you also passing SafteyNet?

I was under the impression that an unlocked bootloader on Nexus devices caused a SafteyNet Failure; is this true?
[Magisk] steveo17:
no. I am not passing safetynet. I'm not as concerned with that as i never use android pay
[Magisk] andrew2432:
[MENTION=7358572]Xanderace804[/MENTION]:

Stock boot may be an issue for you somewhere. Not sure. I haven't tried it yet on my Samsung but go full stock everything, I'm going to. Root yourself with cf auto or Odin flash twrp onto your devilce. If you can get twrp on you can then flash magisk and phh su without ever installing the cf binary.

[MENTION=4540020]AbiDez[/MENTION]:

Final thoughts, tonight I'm gonna try to pass go, grab my 200 dollars, and go out on the town for some PGO, oh and send some snaps again, apparently that's an issue too.

Which phh version...259?

Do I install the phhsu from the app store before or after activating magisk hide? I said 1. Stock 2. Install twrp 3. Flash magiskv8, phhsu259 4. Boot to system, install manager, tick magisk hide, reboot 5. Phhsu app from store.

Some have installed Phhsu app then magisk hide and reboot. Is there a difference?

Anybody: anyone know if lucky patcher has any issues with safety net? I run LP for, well...lots. will it's system patch affect Pgo/safety net?
[Magisk] DeadlyByNite:
Awesome! I didn't want to bother asking you for this module, but I'm glad you shared it here! I'm now passing SafetyNet.
[Magisk] lokogan:
While I have a rooted P3, I am am on stock ROM and not familiar with LineageOS.

However if you are losing GPay access due to Magisk dropping support for MagiskHide, you may want to take a look at Magisk Custom or Alpha.

Both still maintain support for MagiskHide with the former being more stable.

Magisk Custom is available via Telegram channel.

The best approach would be to fully uninstall Magisk, restore Lineage stock boot then install Magisk Custom and reroot.

Alternatively, if you don't mind the risks, just uninstall Magisk apk.

Download and install Magisk Custom apk. Install Magisk (patch boot) using the direct install option.

You will need to clear data for GPay and may need to reconfigure MHPC. Good luck!
[Magisk] kramer04:
hello

just one thong i don't understand , since i installed magisk canary 23014(22) where are modules to download ?
[Magisk] zgfg:
Please search back, it was discussed several times. Fox Magisk Module Manager (Fox Mmm)
[Magisk] elong7681:
TWRP for Pixel 5 A12 isn't available yet, I do have the Cleanslate Kernel installed but Kdrag0n's SNF and tbaldon's kernel work together. I did a factory reset before I installed SNF. I have lots of apps in the DenyList.
[Magisk] pndwal:
Still, worth trying w/ stock kernel... you did say your firmware was stock but w/ that it's not...

Try with nothing in Denylist; I don't know enough about differences, but too many things in hidelist used to break stuff...

Nb. Seems it's working for others:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85917435 PW
[Magisk] pndwal:
One Thong I don't understand either... Much more comfortable with two...

Original repo is still here:

https://github.com/orgs/Magisk-Modules-Repo/repositories

Some modules include release archives. With others you will need to search links (support threads etc) for download packages. PW
[Magisk] pndwal:
Should still work fine with your current setup however if you still have full SafetyNet pass.

Check Google Play Protect in Play Store settings shows 'Device is certified'. Clearing data in Google Play Services and Google Play Store should fix it.

Next, clearing data in Google Pay should fix that. PW
[Magisk] m0han:
just reporting: magisk detector began showing 'init.rc modified' a couple of days after i updated my rom to the 19-nov build. (tbh, i hadn't checked soon after updating, so don't know what actually happened.) on a hunch, i deleted app_zygote_magic config from riru-momohider, cleared cache and data of magisk detector app, added app_zygote_magic config back and rebooted. all seem fine now.
[Magisk] pndwal:
Did you read this?:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85930047 😜 PW
[Magisk] azsl1326:
I accidentally hide the Magisk app from the settings option in the app and am unable to figure out how to get it to show again. I have tried using the following

However, it just returns true.

Any insight on how to get it back. I tried installing Magisk again, however it doesn't show the menu icons at the bottom, which leads me to believe that the original version is still installed based upon what I have read.

Any insight on how to restore Magisk app to be visible again in the app drawer?

Thanks!
[Magisk] zgfg:
This is not pm hiding, it has nothing to do with that

Open that renamed/repackaged app (it's not really hidden, find it in Settings/Apps or in App drawer - default renamed name is Settings until you gave it different name when 'hiding'), open and go to the same place in its settings page and take Restore Magisk app there (opposite from the original Hide Magisk app)

Btw, it was a week ago or so, somebody asked exactly the ssme question, and was given the (same) answer
[Magisk] azsl1326:
Thanks for the reply. It's not in my app drawer or listed in the settings/apps list. Here's what it looks like it I install another version of Magisk.
[Magisk] zgfg:
Please understand how "Hide Magisk app works":

- it asks you for the new name, proposing default new name Settings

- it's not only renaming the app but it also repackages the app, instead of com.topjohnwu.magisk the new package name will be something totally random

That's the point of 'hiding': Magisk app is still there but under the new name (you had to click Ok hence you needed to read and remember that new name) and the random package name - making it hard for banking apps to find/recognize it

That new renamed app has also a different icon - default Android icon

Installing new Magisk app will not help you. That old app (renamed/repackaged/'hidden') as long as present on the system holds control of the Magisk and its database.

That's the reason that your newly installed Magisk app cannot find Magisk - on your screenshot, on top,nit says Magisk: N/A exactly because that old 'hidden' still 'manages' the Magisk - and it will do, until you find and uninstall your old 'hidden' Magisk app

And you cannot do that "Restore Magisk app" from your newly installed Magisk app (where you took the screenshot) but only in that old 'hidden' app
[Magisk] azsl1326:
Thank you for the continued help. I did not give it a new name as the screen disappeared before I could or even hit cancel. It wasn't my intention to hide the app in the drawer. I hit that option by mistake. I will see if I can track it down.

Thanks again.
[Magisk] jenwashere:
My list of installable magisk modules is just straight up missing. I tried reinstalling the magisk app, but that failed, so I tried clearing the magisk cache, but that didn't do the trick, so I tried clearing the play cache, but that didn't work, so I uninstalled and restored images and did an ota update and reapplied to my boot.img to re-root. That didn't resolve it, so I reinstalled magisk yet again. That didn't work, so I switched to the canary build. Modules still missing.

The modules screen:

Device root info:

Anyone ever run into this before?
[Magisk] azsl1326:
Thanks for the tip and help. I was able to find the Magisk app and restore it.
[Magisk] Lughnasadh:
The Module Repo has been removed, as has been discussed in this thread countless times (a quick search will do the trick). You can use this alternative repo though... https://github.com/Fox2Code/FoxMagiskModuleManager
[Magisk] moocow1452:
Checking back in.

I'm kinda stuck on this latest Canary with the Oculus, what happens is that I patch the boot.img and fastboot it, and it refuses to start, giving the old "No Command" error in the black void. But after a reboot, it boots back into home but it still doesn't have root, and adb bugreport doesn't seem to recognize that Magisk was flashed. Could it have reverted to normal behavior after the failed boot? Would an older build be more successful since it's still on Android 7.1, or am I just spitballing at this point?

https://github.com/topjohnwu/Magisk/files/7576728/bugreport-NGI77B-2021-11-21-12-23-47.zip

https://github.com/topjohnwu/Magisk/files/7576730/magisk_install_log_2021-11-21T.log

https://github.com/topjohnwu/Magisk/files/7576733/magisk_patched-23014_Ohbfs.zip

Edit: If I already have adb root as it's a debug build, could I just chmod wherever Magisk is to give it root access, or is either useless or going to cause another bootloop until the main issue is fixed?
[Magisk] m0han:
you've quoted me twice in that post of Nov 12, 2021, where you've also mentioned about false detection in vvb2060 Detector. i like to think you noticed that i was 'just reporting' about how i could get over the false detection.
[Magisk] pndwal:
Sorry... Just wondered why you still seem concerned knowing init.rc will actually be hidden by MomoHider regardless of flawed ("archived") Magisk Detector result... (The detection is fickle at best.) PW
[Magisk] J.Michael:
I don't think there is anything for you to "chmod": Magisk is buried in the boot image. The "set user" capability is provided by magically materialized files -- if you don't have Magisk active, you don't have those files. (Or, at least, those files are not being magically materialized, and so it won't do much good to change their permissions.)
[Magisk] Lu5ck:
I always been wondering...

What is the difference between Magisk Alpha and Canary?

Didn't both of them have magiskhide removed?
[Magisk] zgfg:
It's been discussed a lot. Just go back and read many previous posts about Alpha

In Alpha, you can still use MagiskHide with Zygisk disabled and therefore you can use Riru

In Alpha app settings, if you don't enable Zygisk, then although it is called Configure DenyList, it actually uses the old MagiskHide mechanism, not DenyList

(That is also the proof that Aplha runs MagiskHide - DenyList requires Zygisk and therefore it isn't DenyList but really MagiskHide - but the usage of MagiskHide without Zygisk in Alpha was confirmed in Alpha Telegram chat, to be up to date with Aplha features, subscribe to TG)

Only if you enable Zygisk, then Alpha really turns into the new DenyList

In Canary, there is no more MagiskHide at all, only Zygisk+Denylist

Otherwise, Alpha is in line with Canary, no more Modules online and no more built-in SafetyNet checker.

And Alpha is usually deployed more often, hence it includes more up-to-date commits
[Magisk] Lu5ck:
Are you sure about that?

Unless I am looking at the wrong magisk alpha github, this the commits history

MagiskHide is no more · vvb2060/Magisk@65b0ea7

A Magic Mask to Alter Android System Systemless-ly - MagiskHide is no more · vvb2060/Magisk@65b0ea7

github.com