Database Develop

Magisk with CM13 and Xposed

Hello guys. I'm tempted to install Magisk on my Zenfone 2 ZE551ML. I have the latest CM13 Nightly + Xposed and I want to ask if Magisk has any problem running alongside these two.
Another question is if I can still use the built in CM13 root.
Thanks for your answers!

Im running on CM 13 (ZenFone 2 Laser ZOOL) stable and it works fine.
The only problem is that with xposed active the safetynet check don't pass. But its just a matter of disabling xposed and rebooting when necessary.
I dont know if the differences are too significant, but hope it helps.

FHC1998 said:
Im running on CM 13 (ZenFone 2 Laser ZOOL) stable and it works fine.
The only problem is that with xposed active the safetynet check don't pass. But its just a matter of disabling xposed and rebooting when necessary.
I dont know if the differences are too significant, but hope it helps.
Click to expand...
Click to collapse
That means Magisk doesn't work with Xposed ? Or I just have to unninstall Xposed and then install again after installing Magisk ?

PedroCaseiro said:
That means Magisk doesn't work with Xposed ? Or I just have to unninstall Xposed and then install again after installing Magisk ?
Click to expand...
Click to collapse
Magisk itself works perfectly with Xposed installed, only Magisk Hide that doesn't hide Xposed.
So if you don't plan on using any app that checks Safety Net (Pokemon Go, Android Pay, for example) You won't have any problem.

FHC1998 said:
Magisk itself works perfectly with Xposed installed, only Magisk Hide that doesn't hide Xposed.
So if you don't plan on using any app that checks Safety Net (Pokemon Go, Android Pay, for example) You won't have any problem.
Click to expand...
Click to collapse
and what about the built in CM13 root ?

I think the newest Magisk auto removes it when you flash it.
But I had manually removed before installing magisk on mine.
But in any case, if I remember correctly you can just remove it thru the SuperSU app before flashing Magisk.

FHC1998 said:
I think the newest Magisk auto removes it when you flash it.
But I had manually removed before installing magisk on mine.
But in any case, if I remember correctly you can just remove it thru the SuperSU app before flashing Magisk.
Click to expand...
Click to collapse
I'll try it then and hope not to **** up my phone. Thanks
Sent from my Asus ZenFone 2 using XDA Labs

PedroCaseiro said:
I'll try it then and hope not to **** up my phone. Thanks
Click to expand...
Click to collapse
No problem. Just remember to make a nandroid backup first if you are worried.

[Module][Marshmallow Only] MultiWindow Enabler.

This module enables the native multiwindow mode of Marshmallow without having to set the build time to Userdebug.
The feature is native to 6.0+, but on 6.0 it was disable due to being not ready to release and having some bugs.
This module enables it by adding the build prop line:
persist.sys.debug.multi_window=true
To disable it, simply disable or delete my module on Magisk Manager.
Download link.
https://drive.google.com/file/d/0B5MjHsFKl11beFdacVNQZVl0WFU/view?usp=drivesdk

Cannot run on redmi note 4 mtk.
I install via twrp and check list magisk but still running

x_boogies said:
Cannot run on redmi note 4 mtk.
I install via twrp and check list magisk but still running
Click to expand...
Click to collapse
Hi, can you see if the mentioned line has been added to the build prop?
What magisk version are you using?
Sent from my ASUS_Z00L using XDA Labs

Yeah i see on system/build.prop as txt file adding persys....
I use magisk v16

x_boogies said:
Yeah i see on system/build.prop as txt file adding persys....
I use magisk v16
Click to expand...
Click to collapse
Can you try this module then? This will change your build to userdebug.
The solution is a little dirtier, you have to flash the module, reboot then enable the multiwindow function in the developer options, then reboot again, then if all goes well you can disable my module to return to the user build.
The multiwindow function will continue to work, even in the normal build.
https://drive.google.com/file/d/1lYmf7EtaYl79LoNmdg3Htyu9OAsx237B/view?usp=drivesdk
Sent from my ASUS_Z00L using XDA Labs

I flashing but still not showing multiple on developer

@FHC1998 Neither of the files you've provided work...
First of all because you haven't set PROPFILE to true in config.sh. That's necessary if you have props set in the system.prop file. And secondly, it'll not install on a current release of Magisk unless you update the module template.
Also worth noting is that there won't be anything added to build.prop with this method, the value will just be loaded. Check by using the getprop command.

Didgeridoohan said:
@FHC1998 Neither of the files you've provided work...
First of all because you haven't set PROPFILE to true in config.sh. That's necessary if you have props set in the system.prop file. And secondly, it'll not install on a current release of Magisk unless you update the module template.
Also worth noting is that there won't be anything added to build.prop with this method, the value will just be loaded. Check by using the getprop command.
Click to expand...
Click to collapse
Thanks, yeah the module is a little outdated, I didn't update it since magisk 12. Wierdly it worked for me (Z00l Stock Marshmallow with magisk 11-13) even though those settings were off. But I will update the module and change those settings. Thanks for the tip.
Sent from my ASUS_Z00L using XDA Labs

[Module] Camera2API enabler

Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Note:
This mod only adds camera2api support in the build.prop systemlessly. This does not guarantee modded google camera hdr+ will work on your device.
Axon 7 Users:
Here's a working GCAM that works on my device. However, I don't see any difference with my stock cam hdr. I just use this for slowmo, panorama, photosphere and lens blur effects.
MGCB_7.0H_C2API_Mid_v.3.6_AllinOne_Full_Manual.apk
Requirements:
Android 5.0 & up
Magisk v15
~2014+ Snapdragon SoCs
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled=1". Check attached screenshot for example.
Or
2. Install Camera2 Probe from playstore to check your device's camera capabilities.
UPDATES:
9-15-17:
-added v1400 template
-added camera2api with slowmo fix for Axon 7 users. (I can't guarantee slowmo on other models will work since I used my device's media_profiles.xml file.)
01-25-18
-updated to v1500 template for C2API - Download this file if you only want the HAL3 enabled.
-updated to v1500 template for C2API+slowmo+ (credits to @j1505243)
Credits:
- BSG (4pda)
- @j1505243

Noob question: how do I check in terminal if it's already enabled because in rom included?

vergilbt said:
Noob question: how do I check in terminal if it's already enabled because in rom included?
Click to expand...
Click to collapse
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"

Like this?

vergilbt said:
Like this?
Click to expand...
Click to collapse
Yes.

Unfortunately it did not activate manuals comtrole on my p8lite with Los 13

youwi said:
Unfortunately it did not activate manuals comtrole on my p8lite with Los 13
Click to expand...
Click to collapse
I think this is for snapdragon devices only.

otaconremo said:
I think this is for snapdragon devices only.
Click to expand...
Click to collapse
Yes, and from SD 820+ right?

otaconremo said:
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
I have a G5 which supports it and if I try the command above it does not show the "persist.camera.HAL3.enabled" property. So can we assume that property is specifically to indicate the magisk module is working?
I used this app to check if it was supported already Camea 2 Probe on the play store.

ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs

Not working on lenovo zuk z2..... Snapdragon 820

I think the OP should mention that this module is for SD820+ .

Thanks for the effort but still nothing for XZ

josephnero said:
Thanks for the effort but still nothing for XZ
Click to expand...
Click to collapse
Works on my XZ

What is the benefit of getting this mod?

otaconremo said:
Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Requirements:
Magisk v13
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
Flashed it on my Lenovo Zuk Z2
Snapdragon 820.
Unfortunately didn't work.
Got really excited for it.
Am i missing anything?

Very noob question is this work on mtk devices

sifatrhmn said:
ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs
Click to expand...
Click to collapse
Remove the module in the Magisk Manager app and reboot.

Ariac Konrel said:
Remove the module in the Magisk Manager app and reboot.
Click to expand...
Click to collapse
it doesn't work with my rom like that..
i have to dirty flash the rom again to solve it ..
Sent from my ONEPLUS A3003 using XDA Labs

CStadler said:
What is the benefit of getting this mod?
Click to expand...
Click to collapse
same question, I see no difference on photos.

Motion Sense (Any country enabled) working on May/June patch?

Hi
I'm using april patch on my Pixel 4 and using a magisk module for activating motion sense on my device and I want to update but first to make sure that Soli can be enabled again, like I did.
There is someone in may or june update and with motion sense working with magisk or another trick? Can you explain to me to make it work?
Thanks you all!

On May update you can use motion sensor. Just edit buid prop..
pixel.oslo.allowed_override to 1..
I don't know about june update, because I didn't get that update yet.

Not working for me on may or june updates . Magisk module not working (1.2) . And i m passing safetynet checks.

Haxxan7 said:
On May update you can use motion sensor. Just edit buid prop..
pixel.oslo.allowed_override to 1..
I don't know about june update, because I didn't get that update yet.
Click to expand...
Click to collapse
ummm, if you can explain how you did it, it would be awesome. I was using the magisk module for the simplicity of it, I don't know a lot about this.
Thanks for the answer!

baleskoil said:
Not working for me on may or june updates . Magisk module not working (1.2) . And i m passing safetynet checks.
Click to expand...
Click to collapse
Thanks for the answer, maybe we'll need to use other ways.

Comdirect photoTAN app detecting root

Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible.
Finding out what exactly is causing the root detection is beyond my technical abilities but I would provide as much information needed to those willing to help.
---
Update: December 14th 2021 - Method no longer sufficient
---
The solution found by @pxrave appears to be working:
pxrave said:
Hey fellas I got it working and others apps detect magisk before.
Update to latest v23
Install modules riru and riru unshare
Remove data from tan app
Go to magisk hide and tick all process to hide included the isolated
Start the tan app and do the activation again.
Problem you need wait 2 days to activate because comdirect use new activation process for photo tan app.
Working fine all version 8.3
Click to expand...
Click to collapse
Link to the Riru Unshare module:
GitHub - vvb2060/riru-unshare
Contribute to vvb2060/riru-unshare development by creating an account on GitHub.
github.com

also stcpay yesterday is updated to 1.6 and started to detect my magisk canary (22105)

I can confirm what swour says.
on Android 9 and 11, my magisk root is recognized, magiskhide is active and the phototan app is added.

Yes this is a serious problem. I used xposed magisk and x privacy... Latest comdirect tan app detect all...

+1

+1 big issue for me

Only solution I found (for now): Go back to version 8.2.1 using a backup or any mirror, e.g. https://downloadapk.net/comdirect-photoTAN-App.html
Unfortunately you need to register again then

I have already applied the update. The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem. I have an absolutly clean Android 8.1 build on the phone for banking. It's crazy that the bank is make it so difficult for us to use a save own build.

allrightlite said:
The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem.
Click to expand...
Click to collapse
Perhaps that is too optimistic. I doubt that one app is of great interest

Asellus said:
one app is of great interest
Click to expand...
Click to collapse
Until the new root detection is also available for other apps, it will be fixed quickly.

Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Thanks, then I will easly wait. No need to reactivate hopefully.

Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.

Asellus said:
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Click to expand...
Click to collapse
I don't think so, there is at least one other app that shows the same behavior.
new root dedction
i updated stc pay yesterday to 1.6 and it found my magisk canary (22105) the think i notes is the (isolated) is added to the app !!!
forum.xda-developers.com
I also noticed the (isolated) thing with me.

I tried with v23 this morning, w/o success :-(

Same here, got v23 and working safetynet-fix, no success. Downgraded photoTAN to v8.2.1 .

+1

I'm not surprised, there is nothing in the changelog that this has been fixed.

Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?

muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I have a ZTE Blade L130 with the old photo tan app, that is my rescue. But you can't activate the old one. But it's keep working.

muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I had to unhide the app in magisk hide and hide it again, after that it worked.