Develop Bugs

Question Magisk Modules

Into my Magisk Manager App the modules have gone. Is that kinda normal and I have to download and install modules from other sources or is there something wrong? In earlier Magisk builds I was used to find some modules into the app.
Thx in advance

Since you're on the Canary builds (necessary for the Pixel 6) you won't be seeing any modules to download. That was removed in build 23010, and you'll find the explanation here:
https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Ok, thank you

Question (SOLVED)Safetynet passing without zygisk?

Is it possible to pass safetynet without zygisk? Because I need riru and it doesnt work with zygisk enabled.
Searching the forum does not reveal any ways to pass safetynet without zygisk and universalsafetynetfix.
Yes, it is possible on the 6 pro with magisk alpha + USNF 2.1.2
1) patch your boot image with magisk alpha from vvb2060
2) install riru, usnf 2.1.2
3) enable magiskhide + denylist, deny all entries of play store + play services

Use the 2.1.2 riru version
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com

gerard_f said:
Use the 2.1.2 riru version
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
Unable to pass safetynet with safetynetfix module and magisk renamed

Not on the Pixel 6 / 6 Pro. Magisk 23010+ is required to patch the P6 boot image; the December update borked this, so now Magisk 23016 is required. Magisk 23001 or older cannot patch the P6 boot image. Unfortunately, Magisk 23010 and newer no longer supports Riru.
So, you only have one option:
Update to Magisk Canary 23016
Enable Zygisk + DenyList
Install Universal SafetyNet Fix 2.2.0
Install MagiskHide Props Config 6.1.2
Configure DenyList to block all components of Google Play Services and Google Play Store
SafetyNet should pass with the above configuration.

Or you use Magisk Alpha 23016 and SafetyNet Fix 2.1.2 without Zygist which is compatible to Riru. SafetyNet passes and GPay is working.

yujinloh said:
Is it possible to pass safetynet without zygisk? Because I need riru and it doesnt work with zygisk enabled.
Searching the forum does not reveal any ways to pass safetynet without zygisk and universalsafetynetfix.
Click to expand...
Click to collapse
In the Alpha version of Magisk (by vvb2060) I think you can disable Zygisk to use Riru. Not sure what version of the safetynet mod people are using with it. Can't really tell you much more because I'm not using the Alpha version, but check in the Magisk and/or Safetynet fix threads.
EDIT: And once again, Ninja'd

Yes, you can disable Zygisk in the options and enable the hide list, which is still directly integrated in Magisk Alpha. To be honest I would rather like to switch to canary but as long as Riru is not compatible to Zygisk I have to stay with Alpha.

stroke55 said:
Yes, you can disable Zygisk in the options and enable the hide list, which is still directly integrated in Magisk Alpha. To be honest I would rather like to switch to canary but as long as Riru is not compatible to Zygisk I have to stay with Alpha.
Click to expand...
Click to collapse
There is a version of Riru compatible with Zygisk. You can download the versions in lsposed's Telegram. They have a specific Telegram channel with the non-Zygisk and Zygisk builds. Edit: The channel name is called "LSposedArchives".

V0latyle said:
Not on the Pixel 6 / 6 Pro. Magisk 23010+ is required to patch the P6 boot image; the December update borked this, so now Magisk 23016 is required. Magisk 23001 or older cannot patch the P6 boot image. Unfortunately, Magisk 23010 and newer no longer supports Riru.
So, you only have one option:
Update to Magisk Canary 23016
Enable Zygisk + DenyList
Install Universal SafetyNet Fix 2.2.0
Install MagiskHide Props Config 6.1.2
Configure DenyList to block all components of Google Play Services and Google Play Store
SafetyNet should pass with the above configuration.
Click to expand...
Click to collapse
stroke55 said:
Or you use Magisk Alpha 23016 and SafetyNet Fix 2.1.2 without Zygist which is compatible to Riru. SafetyNet passes and GPay is working.
Click to expand...
Click to collapse
Lughnasadh said:
In the Alpha version of Magisk (by vvb2060) I think you can disable Zygisk to use Riru. Not sure what version of the safetynet mod people are using with it. Can't really tell you much more because I'm not using the Alpha version, but check in the Magisk and/or Safetynet fix threads.
EDIT: And once again, Ninja'd
Click to expand...
Click to collapse
stroke55 said:
Yes, you can disable Zygisk in the options and enable the hide list, which is still directly integrated in Magisk Alpha. To be honest I would rather like to switch to canary but as long as Riru is not compatible to Zygisk I have to stay with Alpha.
Click to expand...
Click to collapse
zetsumeikuro said:
There is a version of Riru compatible with Zygisk. You can download the versions in lsposed's Telegram. They have a specific Telegram channel with the non-Zygisk and Zygisk builds. Edit: The channel name is called "LSposedArchives".
Click to expand...
Click to collapse
Thank you all for the replies.
Magisk alpha + USNF 2.1.2 worked fine for me without zygisk.
(kinda tired at this point , will update more info when have time.)

Does anyone have a solution for the problem
stroke55 said:
Yes, you can disable Zygisk in the options and enable the hide list, which is still directly integrated in Magisk Alpha. To be honest I would rather like to switch to canary but as long as Riru is not compatible to Zygisk I have to stay with Alpha.
Click to expand...
Click to collapse
Where can I get the Magisk Alpha?

There's a Telegram channel

zetsumeikuro said:
There is a version of Riru compatible with Zygisk. You can download the versions in lsposed's Telegram. They have a specific Telegram channel with the non-Zygisk and Zygisk builds. Edit: The channel name is called "LSposedArchives".
Click to expand...
Click to collapse
which version?

Question Lawnchair quickstep??

Hi,
got into rooting after long time...and i installed ProtonAOSP.
with lawnchair launcher.
what happened to quickstep? i can't find it?
Magisk used to show list of available modules and i used to install that from there but now, it doesn't do that too.
anyone has link to quickstep module?
thanks.

First link I think. Second link is an XDA thread for it, though, so likely would do just as well to start either place, although I would guess the second would have a link to the first.
https://www.google.com/search?q=mag...57j33i160l2.4024j0j7&sourceid=chrome&ie=UTF-8

[email protected] said:
Hi,
got into rooting after long time...and i installed ProtonAOSP.
with lawnchair launcher.
what happened to quickstep? i can't find it?
Magisk used to show list of available modules and i used to install that from there but now, it doesn't do that too.
anyone has link to quickstep module?
thanks.
Click to expand...
Click to collapse
QuickSwitch is an app now that when installed will install the module. 1st 2 links.
3rd link is an app that is a Magisk Repo.
EDIT: Ninja'd by @roirraW "edor" ehT
[Module][3.3.1] QuickSwitch - Quickstep enabler for supported launchers
QuickSwitch - Quickstep enabler for supported launchers QuickSwitch is a Magisk module which systemlessly allows supported launchers to access the recents (QuickStep) APIs. It's future proof, detects which launchers are capable of being a...
forum.xda-developers.com
GitHub - skittles9823/QuickSwitch
Contribute to skittles9823/QuickSwitch development by creating an account on GitHub.
github.com
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 - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com

How To Guide How to install microg on unsupported roms

Hey Guys,
Hope you're doing great
For the people who wanted privacy based roms like CalyxOS or GrapheneOS
you have to
1. install vanilla version from ArrowOS or LineageOS
2. Flash Magisk
3. Then in Magisk go to Modules tab, click top button 'Install from storage' install LSPosed-(...)-zygisk-release.zip (has to be zygisk version)
4. then install FakeGapps.apk like an regular app
5. Reboot
6. Popup will came out that ask you to add shortcut icon to desktop for LSPosed, just add it and open it
7. Go to Modules and enable FakeGApps
8. Go to Magisk and install microG_Installer_Revived.zip as a Module
9. Reboot
10. Open microG Service Core and ensure all boxes are selected. The most important is signature spoofing - this is what LSPosed and FakeGapps is for.
For working push notifications go to microG Service Core app and enable Google devices registration and Cloud Messaging.
For working location at least two apps will be needed - MozillaNlpBackend and NominatimNlpBackend. After installing they need to be enabled in microG Service Core app (Location modules). Sometimes MozillaNlpBackend refuse to be enabled, then you just have to go to it's permissions and select "Allow all the time" for location permission.
For working SafetyNet additional Magisk module may be needed.
SMS and Location in background didn't work for me, reinstalled the microG installer module and it worked
Few Alternative apps that you can use:
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing

How to unlock bootloader for Redmi K40s

try looking into this video also if you have created an new mi account you may have to wait for 1week for getting your bootloader unlocked using miunlocktool you can also download the tool from https://en.miui.com/unlock/download_en.html

Also sorry everyone I forgot the metion the alternative apps that you could have used,
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing

SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...

UniNick said:
SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...
Click to expand...
Click to collapse
Thx a lot for mentioning, note: nevest version of spark is an erofs build so for the who didn't wanted erofs version can download previous versions of it

You can use this guide in every rom just make sure it's an vanilla build and it's has signature spoofing

The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatch.

UniNick said:
The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatching
Click to expand...
Click to collapse
We'll I'll try to get more info about it, if I get any fix for it I'll update the guide

Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it

If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.

UniNick said:
If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.
Click to expand...
Click to collapse
I know, as the official release is not available I'm doing it

Vinc3nt.exe said:
Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it
Click to expand...
Click to collapse
Cant wait for LineageOS for Munch. take your time, King.

Hello Guys
Hope you guys are great
this is to inform you that unfortunately i couldn't build the microg version of lineageOS but i have successfully builded it's vanilla version and it's avaliable on xda

[13] [23-05-09] Unofficial Pixel Experience 13 Plus for OnePlus 5/5T

NOT RESPONSIBLE FOR ANY MALFUNCTIONS. MAKE BACKUPS BEFORE FLASHING!
Dirty flashing over previous OS version (~PE 12) may cause bootloop, clean flashing is recommended.
Formatting data partition to F2FS requires internal storage to be fully wiped!
Regarding KernelSU
- KernelSU module system is not (yet) fully compatable with Magisk's module.
- Installing Magisk over KernelSU-enabled boot image or vice-versa will make device not bootable. If it happens, just flash magisk uninstaller or reflash ROM.
- If you want to use KernelSU, flash boot-ksu_{ID}.img from the link below.
Unofficial Pixel Experience 13 Plus edition build for OnePlus 5/5T
Latest build date: 2023-05-09
Working:
Everything for now
Not working:
Let me know
Changelog
Code:
2023-05-09:
- DeviceSettings is back; DC-Dimming and vibration strength are now adjustable
- Deleted Active edge from settings menu
- Minor adjustment
2023-05-07:
- Revert KernelSU integration; KernelSU will be available for optional boot image
- Dropped cheeseburger build; Official build is available on PE homepage
- 2023-05 Security patch
- Based on AOSP 13_r43
2023-04-19:
- 2023-04 Security patch
- Based on AOSP 13_r41
2023-03-29:
- KernelSU integration
- 2023-03 Security patch
- Based on AOSP 13_r35
2023-02-19:
- 2023-02 Security patch
- Fixed SafetyNet fail issue
- Based on AOSP 13_r30
2023-02-15:
- Added anti-flicker driver to kernel
- Moved volume pannel to left side
- F2FS format support for /data and /cache partition
Changelog for KernelSU image
Code:
2023-06-16
- KernelSU version 11000
- Requires KernelSU Manager v0.6.0
2023-05-10
- KernelSU based on commit f69793d
- Module fix for kernel v4.4
- ksu version: 10852
- Requires KernelSU Manager v0.5.5 or above
2023-04-19:
- KernelSU based on commit 45c229d
- Requires KernelSU Manager v0.5.3 or above
Links:
Download for Dumpling (5T)
Download for Cheeseburger (5)
Download for boot image with KernelSU support (5/5T)
Sources:
msm8998-common
dumpling
Kernel
Known Issue:
- GCam and related patches are not included; No plans to add support in near future.
Original Post

Removed magisk and dirty flashed from previous build on dumpling but modules are not working with KernelSU. Installing them with KernelSU manager but module list remains empty even after rebooting. Tried with a clean flash and same result.
/data/adb/ksu/modules/ subdirectories only contains module.prop and an empty update file.
However, su and root privilege work as expected.
Is there something wrong with my device, KernelSU integration in this rom or KernelSU itself?
I can provide logs from KernelSU manager if needed.

Klbgr said:
Removed magisk and dirty flashed from previous build on dumpling but modules are not working with KernelSU. Installing them with KernelSU manager but module list remains empty even after rebooting. Tried with a clean flash and same result.
/data/adb/ksu/modules/ subdirectories only contains module.prop and an empty update file.
However, su and root privilege work as expected.
Is there something wrong with my device, KernelSU integration in this rom or KernelSU itself?
I can provide logs from KernelSU manager if needed.
Click to expand...
Click to collapse
KernelSU's module system is still in development, and it is changed to store modules in /data/adb/modules just like magisk. Each magisk module's install script might need to be altered a bit for KernelSU.
For more details of module system, check the wiki.
https://kernelsu.org/guide/module.html

Works very well, updating from pe13

KernelSu's module function didn't work, I hope you can fix that in next build
--4/4
I created a pull request from my fork, it fix the module function.

fprhqkrtk303 said:
KernelSU's module system is still in development, and it is changed to store modules in /data/adb/modules just like magisk. Each magisk module's install script might need to be altered a bit for KernelSU.
For more details of module system, check the wiki.
https://kernelsu.org/guide/module.html
Click to expand...
Click to collapse
For kernel <4.14, it requires additional patch for modules to work.
https://github.com/F-19-F/android_k...mmit/3df9df42a659f489091445d813b8c0477215ae3a

At what stage do we flash the flash boot-nksu.img file and how? I'm having some issues with the devices booting with the latest update and the latest magisk.

H1mJT said:
For kernel <4.14, it requires additional patch for modules to work.
https://github.com/F-19-F/android_k...mmit/3df9df42a659f489091445d813b8c0477215ae3a
Click to expand...
Click to collapse
Is this commit made by you or picked from someone else's?

totomo26 said:
At what stage do we flash the flash boot-nksu.img file and how? I'm having some issues with the devices booting with the latest update and the latest magisk.
Click to expand...
Click to collapse
If you want to use Magisk not KernelSU, then
1. Flash ROM zip
2. Flash boot-nksu.img
3. Flash Magisk zip

fprhqkrtk303 said:
Is this commit made by you or picked from someone else's?
Click to expand...
Click to collapse
The given link of F-19-F isn't my account, and yeah he is the author of that commit.

hey the fingerprint reader is not working ...

fprhqkrtk303 said:
KernelSU yerine Magisk kullanmak istiyorsanız, o zaman
1. Flash ROM zip'i
2. boot-nksu.img'yi flaşlayın
3. Magisk zipini flashlayın
Click to expand...
Click to collapse
which one should I choose ?

potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
It works fine for me.

semaru_1988 said:
which one should I choose ?
Click to expand...
Click to collapse
choose boot

potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
Me too

potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
It works on mine.

aromanos2021 said:
It works on mine.
Click to expand...
Click to collapse
apparently it's working for some...

potatat0t0 said:
apparently it's working for some...
Click to expand...
Click to collapse
Does on 5t, doesnt on 5

Just upgraded from stock rom. So far, everything works fine and super fluid! Even the better compressed x265 video files plays smoothly on the phone, they was not with the stock rom.
But I have a problem with playing HDR video files. They are not bright enough even on 100% brightness and backlight, while the normal SDR videos are perfect. I used to play these video files from the internal memory with the stock rom, but they was enough bright. So this is something that the new rom changed.
*Tested with VLC and 2 other video players.

Kepszlok said:
Just upgraded from stock rom. So far, everything works fine and super fluid! Even the better compressed x265 video files plays smoothly on the phone, they was not with the stock rom.
But I have a problem with playing HDR video files. They are not bright enough even on 100% brightness and backlight, while the normal SDR videos are perfect. I used to play these video files from the internal memory with the stock rom, but they was enough bright. So this is something that the new rom changed.
*Tested with VLC and 2 other video players.
Click to expand...
Click to collapse
Solution: set HW acceleration in VLC from "full hardware" to "decode acceleration".
In this way the image brightness is perfect but the movie still fluent. On other players deactivating HW acceleration did result a not so fluent playback.