I just got my phone back from ZTE. A2017U upgraded to Nougat B35. Used AxonToolkit to unlock bootloader, flashed TWRP.
Flashed Magisk v16 in TWRP.
Got root but failed SafetyNet.
SafetyNet Check Success.
ctsProfile: false
ctsBasic: false
I tried uninstalling Magisk and reflashing with the zip from the Magisk Manager, just to make sure it was an official version.
Any suggestions on what to do from here?
Is anyone passing SafetyNet on B35?
Try to uninstall Magisk v16 by using the uninstall zip from here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Then flash v15.3. I have it running on B25 and safety net works fine for me. Some users reported issues with safety net after flashing Magisk v16.
Downgraded to Magisk v15.3 and passed safetynet on B35. Thanks!!
You're welcome boddy
Do you guys know if V.17 of Magisk works with B35 Nougat?
Related
Updated to 7.1.1 Beta. Flashed twrp. I then flashed magisk and then phh. I get stuck in a boot lop. I tried twice but each time I keep getting stuck in a bootloop. Does anyone have a work around? I've looked around and seems like everyone is getting it to work but me and a few others? Any help?
Not sure why you want magisk if xposed isn't supported on 7.0+ ? Just use superSU instead.
Edit: There is a (no longer a) benefit in using Magisk/phh, since magisk hide and using xpropset magisk module is detected by SafetyNet already, but see post below for the latest approach (if any):
http://forum.xda-developers.com/nexus-6/help/help-pass-safetynet-rooted-7-0-aosp-t3486834
suhide is not compatible w/ 7.1.1, so SuperSU is not an option for the 6P on the 7.1.1 Developer Preview
Flash magisk and phh su, works fine, but supersu get bootloop, something like this
7.1.1 with supersu (stable or sr1) boots fine, the problem atm is suhide, flashing suhide causes bootloops
Way possible, but without suhide is not very convenient, banks apps not working properly
So the latest superuser by chain fire works? Cause flashing magisk v8 then phh su just sends me to a bootloop.
I'm using magisk and the latest phh su on 7.1.1 and no issues what so ever even have it passing safetynet
All I did was flash the factory image, then two, then flashed phh su, magisk and then rebooted and installed xsetprop through magisk.
how are you getting this working? I haven't tested, but doesn't the 7.1.1 need a custom kernel to bypass safetynet? Kernel source isn;t out yet?
So my S7 Edge (running 6.0.1) was rooted with SuperSU. I installed Magisk by flashing it and it told me it doesn't pass the safety net check
So i've done literally all i can think of to try and install it
I've flashed the stock firmware back, installed magisk and then get told i have no root to use magisk
i've installed SU on stock then magisk and get Error 1
I've tried upgrading to 7.0 and using CF-Auto root, but that doesn't work ("seandroid is not enforcing" error)
I've tried using Superstock and just get an "integrity error"
does anyone know how to install magisk?
Fixed it
Nevermind i fixed it.
For anyone wondering v12 doesnt install MagiskSU for some reason? find your firmware online, extract the boot.img from it, flash that via TWRP to your boot. then flash magisk v11.1 and THAT will install magisk and let SN pass.
I'm currently running stock rom with Blu_spark kernel. I've been using magisk, lately updated to 14.3 version.
My problem is I can not pass SafetyNet check. Both ctsProfile and basicIntegrity are false.
I tried Universal SaftyNet Fix but it didn't help at all.
Is there any hope to pass it on stock rom?
Do you have Xposed installed?
Thanks, I completely forgot about it
The other safety net problem people are currently having with Magisk is that if you update Magisk within Magisk Manager some scripts needed to pass safety net are no longer installed by default. If you flash Magisk instead through TWRP it seems to install like normal and you don't need to perform additional steps to pass safety net.
As you see in the title, i can't pass SafetyNet on Magisk v16, stock ROM SL!M B10. I flashed bootstack>rom>disable dm verity script>magisk. I don't know what's the problem, i could pass SafetyNet with same setup and flashing process.
I think that somehow nodmverity script didn't worked. I get Not certified on GP too.
Btw it's the A2017G variant.
I appreciate every response to my issue.
Thank you.
Edit: It turns out that it was Magisk 16.0 issue, after i flashed 16.7 SafetyNet pass.
Third screenshot somehow didn't uploaded.
hello,
i have updated my phone global MIUI 11 android Q V11.0.4(QFJMIXM) and i want to root using magisk.
Using TWRP:
Magisk v20.3 fail,
Magisk v20.2 fail,
Magisk v20.1 fail,
Magisk v20.0 fail,
Magisk v19.4 fail,
Using patch boot with Magisk manager:
Stable fail,
Beta fail,
Canary Magisk fail.
please help me how i can root my phone :crying: thank you.
TahaMohammad said:
hello,
i have updated my phone global MIUI 11 android Q V11.0.4(QFJMIXM) and i want to root using magisk.
Using TWRP:
Magisk v20.3 fail,
Magisk v20.2 fail,
Magisk v20.1 fail,
Magisk v20.0 fail,
Magisk v19.4 fail,
Using patch boot with Magisk manager:
Stable fail,
Beta fail,
Canary Magisk fail.
please help me how i can root my phone :crying: thank you.
Click to expand...
Click to collapse
Did you check the existing threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Rooted that way (no TWRP needed) and everything works perfect.
Later flashed official davincie TWRP
(Mine is QFJEUXM v11.0.4.0 but for your it should work the same. Also I used latest Canary but some other prefer stable Magisk)
zgfg said:
Did you check the existing threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Rooted that way (no TWRP needed) and everything works perfect.
Later flashed official davincie TWRP
(Mine is QFJEUXM v11.0.4.0 but for your it should work the same. Also I used latest Canary but some other prefer stable Magisk)
Click to expand...
Click to collapse
yes i was tried but not working.
TahaMohammad said:
yes i was tried but not working.
Click to expand...
Click to collapse
Did you patch boot.img with Preserve Verity and Preserve Encryption, but not with Randisk option - did you then flash it from fastboot (without using/having TWRP)