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!
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Lorenzo Benevento said:
Bump.
With V15.2 basic integrity works, but I can't pass the whole test!
Click to expand...
Click to collapse
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).
Okay, thank you for the infos! I will do some research an hopefully go through it.
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...!
Lorenzo Benevento said:
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...!
Click to expand...
Click to collapse
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.
Didgeridoohan said:
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).
Click to expand...
Click to collapse
Didgeridoohan said:
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.
Click to expand...
Click to collapse
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?
Lorenzo Benevento said:
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?
Click to expand...
Click to collapse
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 said:
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.
Click to expand...
Click to collapse
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 said:
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.
Click to expand...
Click to collapse
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.
Thank you so much, I'll ask there.
Hello,
I have installed LineageOs on my rooted Huawei P9 Lite.
I am trying to install Gapps on my phone with twrp but when i swipe to install it twrp crashes en restarts.
It keeps on crashing.
Can someone tell me how to fix this please?
RobinWijns said:
Hello,
I have installed LineageOs on my rooted Huawei P9 Lite. I am trying to install Gapps on my phone with twrp but when i swipe to install it twrp crashes en restarts. It keeps on crashing. Can someone tell me how to fix this please?
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3649152
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi i want to room my phone with superSU. i just installed ViperOS 3.1.1 on my J5 2015 FN and i dont have root now. does anyone know how can i root it without any problems?
Thanks
Secyto said:
Hi i want to room my phone with superSU. i just installed ViperOS 3.1.1 on my J5 2015 FN and i dont have root now. does anyone know how can i root it without any problems? Thanks
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device variant.
https://forum.xda-developers.com/galaxy-j5
The following thread information is your best bet in obtaining some information and member guidance for your specific device and Firmware installed.
The following thread is specific to the Firmware you installed.
https://forum.xda-developers.com/showthread.php?t=3610145
The following is just a few of the guides for rooting your specific device.
https://forum.xda-developers.com/showthread.php?t=3502292
https://forum.xda-developers.com/showthread.php?t=3209783
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi, I have spent many hours on this forum and others trying to learn how to root this android 8.0.0 head unit, I have read a lot and tried several ways including pushing SU apk to it with wifi (would never connect on port 5555), if someone could just tell me what (if any) method will have best chance of rooting? Link would be awesome. HU Details below.
OR please advise me what is the most easily rootable similar Android head unit? So frustrated am willing to just buy another head unit for root ability. Anyone have a similar pre-rooted one they want to sell? I'd pay more than list price for it. Thanks.
Pumpkin ND0286B-A08
px5-userdebug 8.0.0
MTCE_KLD_V2.94e_1
8-core 64bit [email protected]
Kernel Version 4.4.93+
Patch Level October 5,2017
Use Hal9k! It has a modinstaller.apk which roots, installs recovery and installs the rom. Just sideload the apk.
philicibine said:
Use Hal9k! It has a modinstaller.apk which roots, installs recovery and installs the rom. Just sideload the apk.
Click to expand...
Click to collapse
Hi sorry for late reply, I almost gave up. But am going to try this. If this works I will gladly donate to both you and the author of the rooter. Thank you!!!!!!!!!!!!!!!!!!!!
Glad you got it sorted!! Thanks for the beer tokens!! ?
Hey guys,
So the last Samsung device I owned was S7, So I'm pretty familiar with Odin and flashing to Samsung.
However still quiet new, I was reading in forum that after rooting S21Ultra, Knox would be a huge headache. And Samsung pay would not work.
So just wanted to know what all are things that break after I root. And will my phone be able to pass the safety net with additional modules? Like safety net fix.
Thanks for your reply.
Also if someone could link a thread to unlocking and installing twrp and rooting it. That would be great, as I'm unable to find it. I' have the snapdragon variant
No Problem,donʼt worry it is true that after unlocking bootloader banking apps will not work (also MyJio app) but you can fix it by safetynet fix and magisk hide or zygisk for further help you can contact me on telegram @the_arxyn
the_arxyn said:
No Problem,donʼt worry it is true that after unlocking bootloader banking apps will not work (also MyJio app) but you can fix it by safetynet fix and magisk hide or zygisk for further help you can contact me on telegram @the_arxyn
Click to expand...
Click to collapse
Thanks for your prompt reply. Im unable to find links to telegram groups for S21 Ultra. Do you have any ?
I will later send u on telegram