Tried to find answers for these, but struggled given the enormous replies on some thread with little help from search results.
1- I read that viper 10 magisk doesn't have the theme app or options, so how is it different from stock?
2- Can flash the magisk version directly? I'm rooted with MagiskSU.
3- Does it matter if a magisk rom is pre-rooted? Do I have to disable MagiskSU before flasing a rooted Magisk rom?
4- Why are Magisk roms small in size?
Cheers
aouni_tahech said:
Tried to find answers for these, but struggled given the enormous replies on some thread with little help from search results.
1- I read that viper 10 magisk doesn't have the theme app or options, so how is it different from stock?
2- Can flash the magisk version directly? I'm rooted with MagiskSU.
3- Does it matter if a magisk rom is pre-rooted? Do I have to disable MagiskSU before flasing a rooted Magisk rom?
4- Why are Magisk roms small in size?
Cheers
Click to expand...
Click to collapse
1. I'm not aware of such issues. Search the Viper10 and/or LeeDroid threads for info on that. When I tried the Magisk version of Viper10, the theming worked fine.
2&3. The Magisk ROM isn't pre rooted. Once you install Magisk, which you've already done, you can install the Magisk ROM. The Magisk ROM relies on Magisk...so don't disable it.
4. You're not flashing a full ROM, the Magisk versions of the ROMs install the files needed for it to function as such. The base is what your phone has, rather than flashing the classic/full ROMs that include the base in the installer.
aouni_tahech said:
Tried to find answers for these, but struggled given the enormous replies on some thread with little help from search results.
1- I read that viper 10 magisk doesn't have the theme app or options, so how is it different from stock?
2- Can flash the magisk version directly? I'm rooted with MagiskSU.
3- Does it matter if a magisk rom is pre-rooted? Do I have to disable MagiskSU before flasing a rooted Magisk rom?
4- Why are Magisk roms small in size?
Cheers
Click to expand...
Click to collapse
The magisk version of our rom is a magisk module, about 180MB in size.
You can disable that module anytime in the magisk manager app...so you are 100% stock again within seconds.
That is the whole purpose of the magisk rom, to not touch the orignal system, but stil offer all customizations the classic rom does as well.
To Point 1.) not sure where you read that...thats absolutely not true. It comes with all mods and customizations like the classic rom..
The rom is so small, because it just comes with the files that are modified by us and then gets "merged" with the stock rom you are running.
Viper10 has a LOT of options, from theming to tweaks. I've never used Leedroid myself so I don't know how good that one is for offering customization options, but Viper10 hasn't let me down. Viper itself is pretty similar to the stock ROM in terms of appearance though, but you can change that if you want (I'm personally enjoying some of the new overlays that can be enabled such as the side panel.)
What apps/modifications would you suggest for a rooted OP5T which makes rooting worth the effort?
Any magisk modules as well! Just wanted to get some idea on the best customizations for OP5T.
Ainur sauron, greenify, gcam, lucky patcher
https://forum.xda-developers.com/oneplus-5/how-to/collection-shadowsteps-android-t3832556 @dandrake47
dandrake47 said:
What apps/modifications would you suggest for a rooted OP5T which makes rooting worth the effort?
Any magisk modules as well! Just wanted to get some idea on the best customizations for OP5T.
Click to expand...
Click to collapse
For customizing OOS (debloat, tweaks, etc.) start here: https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
It's a magisk module that's flashed in twrp. It also includes adaway and viper4android as add-ons if you want. Magisk modules like camera mod m no longer work in pie, so you have to do some searching and reading to figure out which ones you like and still function. Youtube vanced can be problematic in magisk, especially if youtube has been updated in the background. New Pipe (from F-droid) is a great alternative and doesn't require magisk.
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this.
Disclaimer: Only tested with RR, PixelExperience, and ArrowOS GSI.
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
4. Fluid NG - App in Google Play Store to have the same recents/home/back gestures from MIUI 10.
reasonablebasis said:
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
Click to expand...
Click to collapse
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well. CTS will fail for obvious reasons
Mackay53 said:
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well.
Click to expand...
Click to collapse
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Can't remember as it was a while ago, possibly OctoOS and descendant and 1 other, omni ROM maybe.
For the ones that come with SU you need to navigate to the xbin folder in the system and remove the SU file.
Then cause Xiaomi EU uses the wrong fingerprint props you need to use the magisk props config module and manually type in the mix 3 fingerprint (unless the module has been updated to include mix 3).
If you installed the Chinese dev vendor then the props will be there ready to be used so the magisk module can make them active without manually typing it. This will sort out both safety net fails.
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Pixel dust gsi too....
reasonablebasis said:
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
Click to expand...
Click to collapse
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Mackay53 said:
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Click to expand...
Click to collapse
Ok, I'll put a disclaimer that this only works on RR, PixelExperience, and ArrowOS. Anyway, I'm sure that the latest stable Xiaomi.EU vendor works without any issues with ArrowOS, else why would I be using it as my daily driver.
[deleted, duplicate post]
Someone know if there is a GSI with gapps and that don't have issue with bluetooth?
SafetyPatch module
reasonablebasis said:
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-...mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Click to expand...
Click to collapse
Mate, I can't find this module via Magisk Manager... Please help!
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
You sure? Try searching for "SafetyPatch"
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Strange....
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
On Arrow ?
Wahoux said:
On Arrow ?
Click to expand...
Click to collapse
Yep! Not sure how to prove that though xD
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Wahoux said:
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Click to expand...
Click to collapse
Dare to try? xD
jonny908 said:
Dare to try? xD
Click to expand...
Click to collapse
ahah no xD
Right now i'm about to flash Arrow, I hope I won't have bluetooth issue . On the non-GSI Pixel Experience, some reported issue with bluetooth whereas it was working fine for me... so let's see :fingers-crossed:
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
Wow good for you. You flashed xiaomi.eu prior to GSI right? enumerate the steps you did, so that we we hopefully can replicate your success. Hehe
I have had Redmi Note 8 Ginkgo since December. From then on, I am waiting patiently for the appearance of refined custom roms. Recently, roms have finally appeared where all camera lenses work! But I miss one thing very much... Since I had the RN4x I have been using the Dolby Plus mod. In the RN8 it clearly improves the sound, has more bass and is louder. I mean the sound on the built-in speaker, not on the headphones. Dolby Plus can handle bass better on the built-in speaker than the Viper4Android.
This mod however requires SeLinux to be permissive. All android 10 roms that I tried have a SeLinux Enforced kernel - for some reason switching between enforce and permissive is blocked. Even some roms do not allow flash another kernel.
How do I unlock the ability to switch Selinux enforced to perrmisive when the magisk SELinux Manager module is not working?
kaem84 said:
I have had Redmi Note 8 Ginkgo since December. From then on, I am waiting patiently for the appearance of refined custom roms. Recently, roms have finally appeared where all camera lenses work! But I miss one thing very much... Since I had the RN4x I have been using the Dolby Plus mod. In the RN8 it clearly improves the sound, has more bass and is louder. I mean the sound on the built-in speaker, not on the headphones. Dolby Plus can handle bass better on the built-in speaker than the Viper4Android.
This mod however requires SeLinux to be permissive. All android 10 roms that I tried have a SeLinux Enforced kernel - for some reason switching between enforce and permissive is blocked. Even some roms do not allow flash another kernel.
How do I unlock the ability to switch Selinux enforced to perrmisive when the magisk SELinux Manager module is not working?
Click to expand...
Click to collapse
Try the following Magisk module. Download and install it via TWRP: SELinux Switch
shadowstep said:
Try the following Magisk module. Download and install it via TWRP: SELinux Switch
Click to expand...
Click to collapse
Please read the last sentence of my post. I used two ways to change selinux, they work on miui, on
other custom android pie roms. Is this module from you unique?
kaem84 said:
Please read the last sentence of my post. I used two ways to change selinux, they work on miui, on
other custom android pie roms. Is this module from you unique?
Click to expand...
Click to collapse
I did read your entire post. I was just offering an alternative, so whether or not you want to give it a shot, is upto you. If it works for you, great. If it doesn't, get in touch with your ROM developer. Over, and out. :good:
SELinux
There's an app called SELinux mod changer, try that. I used that to change permission to permissive on my ginkgo(Android 10) and it works perfectly.
shadowstep said:
I did read your entire post. I was just offering an alternative, so whether or not you want to give it a shot, is upto you. If it works for you, great. If it doesn't, get in touch with your ROM developer. Over, and out. :good:
Click to expand...
Click to collapse
Respect man, this magisk module works!
The few modules that I was using apparently did not work properly with android 10. I thought the kernel was blocked in some way, and this is a matter of choosing the latest selinux switcher.
Here is the link to the source where this magsik SELinux Switch module comes from:
https://github.com/nipunnarang/selinux-switch
Do you know how with some magisk module or buildprop modification to:
- set the back button to close / kill the application
- the appearance of recent applications was like in android oreo?
I found scripts for it once, modules and now I can't. I prefer not to install xposed
kaem84 said:
Respect man, this magisk module works!
The few modules that I was using apparently did not work properly with android 10. I thought the kernel was blocked in some way, and this is a matter of choosing the latest selinux switcher.
Here is the link to the source where this magsik SELinux Switch module comes from:
https://github.com/nipunnarang/selinux-switch
Do you know how with some magisk module or buildprop modification to:
- set the back button to close / kill the application
- the appearance of recent applications was like in android oreo?
I found scripts for it once, modules and now I can't. I prefer not to install xposed
Click to expand...
Click to collapse
Good to know it works. I made it. The link you've provided is my GitHub. Also, no, I don't know if there's a Magisk module for those two things. For the former, you can try using Button Mapper. It requires root, but not Xposed. And for old Oreo style recents, it needs a modification to the ROM, which can't be done via a simple Magisk module.
At this point, there are several ROMs with OOS camera, and a few without. The ones without, there are camera versions you can install but they don't have the auxiliary cameras available. At least not on EvolutionX. I can't seem to find any way to make them work either. I've tried several app versions and obtained a very recent OOS 13 fingerprint and setup device simulation props, and only the primary camera is detected. I even went as far as trying to use an installer for older OOS camera apps with a current OOS camera app, but I can't get it working. Tried looking at the CRDroid files and I can't see what they did either. I'm not a programmer nor an expert with ROMs but from what I can gather, I'd just need the right system or system_ext files, and maybe a particular app version, then I don't see why I couldn't compile a Magisk module similar to others I've found.
I would be interested too, nice question man
+1 from my side!
The final answer is NO.
OOS camera requires tons of OS side changes. Installing just the APK won't work at all. Porting an OOS camera to custom ROMs was already a mess and a complex thing.
The ROMs that don't include the OOS camera require additional commits/changes.