Magisk 14-15 not working on Zuk Z1 with LAOS14.1

[Lorenzo Benevento]

Hi everyone,
I'm getting really annoyed by Magisk on my phone.
I'm absolutely not able to make it work. No way it can pass safety net control.

If you need some other information, just ask!

Any help would be appreciated,
thanks in advance,
Lorenzo Benevento.

EDIT: I've just upgraded to the last LAOS build and now it doesn't pass also the basic integrity test!

 

[Lorenzo Benevento]

Bump.
With V15.2 basic integrity works, but I can't pass the whole test!

 

[Didgeridoohan]

Bump.
With V15.2 basic integrity works, but I can't pass the whole test!

So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.

If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).

 

[Lorenzo Benevento]

Okay, thank you for the infos! I will do some research an hopefully go through it.

 

[Lorenzo Benevento]

Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!

 

[Didgeridoohan]

Hi, unfortunately seems like there is no way of getting it to work, I also tried Universal Fix but it messed out everything.
I was discussing about it on discord and they said that looks like my device (Zuk Z1) is not fully supported (and it is plausible since is not this popular).
So, if I can help with the development (boot images, logcats, Magisk Log, trying, whatever), let me know who should I contact and how.
Thank you so much.
I'm having troubles with Magisk since V13, the first I tried...!

Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.

 

[Lorenzo Benevento]

So in other words: MagiskHide is working on your device but Google doesn't recognise it as a certified device.

If you wan't to pass CTS as well, you're going to have to trick Google into thinking you have another device/ROM, probably by using the fingerprint from a stock ROM that is certified. There's some info on that in the troubleshooting guide (which I'm hoping to have some time to update in the next few days).

Well... Since you can pass basic integrity we know that MagiskHide is working. The Universal SafetyNet Fix module might not be your best option... Simply using a resetprop tool script to change ro.build.fingerprint, like mentioned in the guide I linked (under "Spoofing device fingerprint") might be enough.

Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?

 

[Didgeridoohan]

Okay, thank you, I have just a question before trying (and mark this thread as solved hopefully). Will this change in props affect LAOS OTAs?

Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.

I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.

 

[Lorenzo Benevento]

Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.

 

[Lorenzo Benevento]

Changing the fingerprint can cause your phone to be recognised for something it isn't, so it's perfectly possible that it can affect OTAs. It should just be a matter of disabling the script when you need to update.

I have no real world experience with it though... I've just once tested and confirmed that changing the fingerprint can help with passing SafetyNet on a non-certified ROM.

Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.

 

[Didgeridoohan]

Okay, I'm going to try, the only problem is that I can't find the official fingerprint of my phone! Only outdated version, I think I should match at least Android version, isn't it?
Thank you so much for your quick and useful replies.

Actually, when testing I used an official Nougat fingerprint for a custom Oreo ROM. If you can't get a hold of a more recent fingerprint, I'd recommend asking in your device's forum if anyone can provide one.

 

[Lorenzo Benevento]

Thank you so much, I'll ask there.