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.
Related
Just heard Super Mario Run has came out on android but its not showing as supported for my HTC 10 on the play store?? I tried the app from an alternative store and got an error message after being able to do the first level. Why would the HTC 10 not be supported. would a build prop edit make it work?
Edit: Looks like it might be because Im rooted, going to try Magisk.
Edit 2: seems to be working with Magisk installed, still not available on playstore though.
I installed it through the play store without any problem(root-magisk)
fratorga100 said:
I installed it through the play store without any problem(root-magisk)
Click to expand...
Click to collapse
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
tokuzumi said:
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
Click to expand...
Click to collapse
Yes, it is working for un-rooted users. Rooted users, not so well in most cases.
Ariac Konrel said:
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
Click to expand...
Click to collapse
Yes. I am able to run the tutorial level, then I receive error 804-5100.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
you need magisk SU to be able to use magisk hide and pass safety net. supersu won't work.
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
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
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.
Try safety patch module in Magisk to pass Safetynet
HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same
Hi
Im back to stock after months of struggling with Lineage bugs.
All i need is viperfx, which improves internal speaker so much, whem properly configured !
I guess the only way to get it is by using magisk (i tried with a supersu root and a viperfx flash but it didnt work).
So I just spent many hours trying to get magisk to run properly but failed.
I flashed 17.1 in twrp, seemed to work, but it didnt find any module to install, so i updated magisk manager to latest version.
Then i was unable to run magisk manager, instant crash at launch, fc.
Any tip please ?
Thanks