Develop Bugs

Magisk problems in Moto Z2 Play

I can not install magisk modules and my device constantly loses its root without a reason.

I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.

Thanks
romhippo.com said:
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Click to expand...
Click to collapse
Thanks Romhippo.com for responding!
If anyone knows more about it, I'd be happy to know.

Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.

larsdennert said:
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
Click to expand...
Click to collapse
Cool! I hope they also correct here.

Loosing root + possible fix
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U

raphamfc said:
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
Click to expand...
Click to collapse
LoL Many thanks for your help. It's all normal here.

I'm going to agree on conflict issues being the likely cause. Between custom roms having su built in like Resurrection remix, SuperSU and standalone magisk, there are plenty of possibilities for messed up boot images.

In fact, 2 things bother me the most.
1. I can not install magisk modules
2. The magisk does not pass SafetyNet.
I do not know if that happens to you.

My Z2 is a verizon one so this is where my advice stops on that phone. I've Magisk on the 3T and pixel only

anyone have a guide to install Magisk?

Refer the following threads completely. Junior answered all my querries. His Moto Brazil blog has systematic and structured guides as well. Very well done.
https://forum.xda-developers.com/z2-play/help/indian-stock-firmware-xt1710-10-t3711423
http://motozbrasil.blogspot.in/search/label/TutorialZ2Play

Have you updated to Magisk 15.0?

This update seems like a big deal.
If you've installed this update, please relay your experience with it. Thanks!

Well, I reckon I'll be the guinea pig.

Downloaded, installed and rebooted.
Went from 14.0 to 15.0
Checked Safety Net.
Not sure what else to check, opposed to just daily driving it.
All seems to be well.

are you able to install modules in magisk 15.0

Sam_kaks said:
are you able to install modules in magisk 15.0
Click to expand...
Click to collapse
Kinda apprehensive to try, as I'm on travel away from home.
I could not install either Dolby Atmos, while on 14.0.
Let me see if I can find a small module...
ETA, I tried both Dolby Atmos and the Viper for Magisk 14+.
All failed.

If you want to successfully flash modules using magisk 15+ , you have to do a onetime install of the following f2fs workaround module (flash via TWRP)
https://forum.xda-developers.com/ap...isk-official-version-including-t3577875/page1

How do we upgrade from the @juniorpassos Magisk 13.3 listed in this thread? Is there anything special that needs to be done if just booting TWRP temporarily and flashing a Magisk ZIP from the XDA thread? When I open Magisk on my phone, I see is a "Cannot check for updates, no internet?" message even though I'm definitely on WiFi.
Also, anyone that wants to save me time writing a post asking how to pass SafetyNet check wins my internet love.
Update: I just went ahead and did it. Looks like it's working fine and I was prompted to install something that now makes my phone pass SafetyNet.

Oneplus 5T with OxygenOS, TWRP and Magisk 17.1 SafetyNet fail after a few hours

I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.

Try to disable "developer menu" in "settings", then reboot and check safetynet again.

Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...

anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.

yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?

Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.

Try a different play services apk. This was the case with me previously.

Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail

With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.

I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?

floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0

Oxygen OS 10.0.14.HD65AA + Magisk + EdXposed Failing SafetyNet

So I had everything working perfectly, and then I updated to Oxygen OS 10.0.14.HD65AA.
I was greeted with a bootloop after doing the update, so I removed all of my Magisk modules and it booted up.
Next, I reinstalled all my modules. After reinstalling Riru EdXposed, I could no longer pass the SafetyNet check (it passes without EdXposed enabled).
I have tried a few different EdXposed versions, including v0.5.0.6 (4564) canary.
Is anyone else able to pass SafetyNet on 10.0.14 with EdXposed?

Exposed breaks safenet

ChrisFeiveel84 said:
Exposed breaks safenet
Click to expand...
Click to collapse
As I said, it was working fine before the update.
But I also updated Magisk to v21 when I did the OTA, so not sure if that had an effect as well.

TuRDMaN said:
As I said, it was working fine before the update.
But I also updated Magisk to v21 when I did the OTA, so not sure if that had an effect as well.
Click to expand...
Click to collapse
the problem is edxposed. I changed nothing in the last few days and yesterday suddenly safetynet fails. Still did mobile payment with gpay 2 days ago so I'm sure the problem started yesterday. Apparently google do some change in safetynet attestation

TuRDMaN said:
So I had everything working perfectly, and then I updated to Oxygen OS 10.0.14.HD65AA.
I was greeted with a bootloop after doing the update, so I removed all of my Magisk modules and it booted up.
Next, I reinstalled all my modules. After reinstalling Riru EdXposed, I could no longer pass the SafetyNet check (it passes without EdXposed enabled).
I have tried a few different EdXposed versions, including v0.5.0.6 (4564) canary.
Is anyone else able to pass SafetyNet on 10.0.14 with EdXposed?
Click to expand...
Click to collapse
I just had the same thing happen to me this morning. I restored images in magisk, then updated and installed magisk onto inactive slot before rebooting. Then the bootloop. How did you get out of the bootloop and disable your magisk modules without resetting your device with the msmdownload tool?

How can I modify what I perceive as a rooted device?

Hi. I was install LineaseOS 17.1 to xz2c. Then, installed the app that I use.
But, Some apps not work because, Rooting detected from my Phone.
Of course, I didn't rooting. (Wipe and only installed LOS and gapps)
I think I recognize it as a Rooted device due to the settings such as build.prop.
To solve this problem, I've tried Magesk or some other method( LOS Recovery -> pull build.prop and Modify), and there's still a problem.
I want to know which part of build.prop or what elements of something else are recognized as a routing device and how to solve this problem.
How should I fix something?
Previously, I tried to solve this problem with Magisk and Module, but it didn't work perfectly.
I have installed magisk and installed magiskHide Props Config 5.4.0 and universal safety net fix 1.1.1.
But Safetynet ctsProfile failed, and some apps works well, but others didn't.
There are only LOS and Gapps now.( Not Uninstall, Full Wipe and reflashing LOS17.1)