Related
Ah safetynet, the thorn in the side of every technical android user who wants to use Android Pay.
It's even worse on a xiaomi device, because once you've been granted a bootloader unlock after waiting for days, you don't want to re-lock it for fear of locking yourself out of the device and having to wait another 30 days before you can get a new unlock permission!
There is a lot of old information around about hiding root, custom kernels, installing things in particular orders and I'm pretty sure I've tried them all - including compiling kernels from scratch with a few different versions of the unlocked bootloader hiding patch.... never getting past the dreaded CTS Mismatch
But all of a sudden I happened on a little known secret found by @kyasu that the build fingerprint is also checked : https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Also, conveniently, Magisk (since v9) patches the ro.boot.verifiedbootstate and related props that SafetyNet checks.
This now gives us two options to enable safetynet regardless of bootloader state.
You will need either a kernel with bootloader state hidden OR magisk, as well as a method of changing the build fingerprint.
This also assumes you've got TWRP installed and are comfortable using it.
Tested on Mi5 Lineage OS 14.1-20170206-NIGHTLY-gemini and various xiamoi.eu 7.2.X and 7.3.X versions:
NOTE: Magisk Hide on MIUI currently does not work (21st July 2017)
This has been widely reported and there are a number of open issues:
https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open miui
A fix may have been found, not ready to test however:
https://github.com/topjohnwu/Magisk/issues/298#issuecomment-316687923
Magisk:
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
From TWRP install Magisk v13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Restart and Magisk Manager app should be installed.
Hit the test safetynet button in Magisk Manager, if it passes stop here! Latest lineage roms don't need my magisk fingerprint module anymore, they just work.
Otherwise, download this magisk module on your phone: https://gitlab.com/alelec/magisk-ge...2bbf9dc8/magisk-gemini-safetynet-props-v3.zip
In Magisk Manager, go to modules and install the magisk-gemini-safetynet-props zip just downloaded. It should prompt to restart to enable module, do so.
After restart, fire up Magisk Manager and "tap to start SafetyNet check", fingers crossed it comes up Green!
Note: After each rom update you will need to reinstall Magisk in twrp, but the safetynet enabling module above should stick just fine and not need reinstall.
Custom Kernel:
I don't test this as often, as I prefer the Magisk method, however this is an option for people who don't want any kind of root on their phones.
I also don't maintain any patched kernel for miui based roms as the one's I've tried are just too buggy.
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
Install gemini-safetynetpass-stable-fingerprint-20170217.zip
this package is based on gemini-safetynetpass-20170213.zip by @kyasu but only changes the build prop fingerprint, the old custom kernel has been removed:
Install a patched kernel, you can either use my autobuild of a patched latest LineageOS kernel for Mi5 (includes fingerprint fix):
https://gitlab.com/alelec/android_kernel_xiaomi_msm8996/tags (LineageOS-gemini-safetynet-kernel_XXXXXX.zip links)
or recent DragonXia kernels appear to be patched
https://forum.xda-developers.com/mi-5/development/kernel-brand-kernel-cm13-alpha-1-0-t3480663 (LineageOS)
https://forum.xda-developers.com/mi-5/development/kernel-dragonxia-kernel-v1-0-t3546619 (MIUI)
Note: Both the kernel and fingerprint zip above will need to be re-installed after each rom update.
On a related note, if you want to use Android Pay on MIUI based roms, make sure the HCE wallet configuration and permissions are set correctly.
See the following for more details: http://en.miui.com/thread-405166-1-1.html
Once you unlock it once, you can unlock it again without waiting. I just unlocked and relocked my Mi5 about 3 times in a couple days.
Sent from my MI 5 using Tapatalk
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
coronafire said:
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
Click to expand...
Click to collapse
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
I'm not sure on kernels, haven't messed with them on Xiaomi devices.
Sent from my MI 5 using Tapatalk
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
the_poolee said:
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
Click to expand...
Click to collapse
Drats. If basic integrity is failing that's something else triggering the issue. Before I changed the fingerprint I only had cts failing, basic was usually fine. Sometimes a replacement kernel would cause it to fail basic, but I never narrowed down exactly what the cause was.
Works on LOS. Anyway my bank doesn't support android pay yet.
Ulver said:
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
Click to expand...
Click to collapse
Looked into it some more to confirm - I'm quite sure you can't re-lock the bootloader if using anything that's not an official xiaomi rom, ie if using lineage, or even the xiaomi.eu rom, you can't lock bootloader without having a bootloop.
And yeah, I've confimed this method doesn't work on xiaomi.eu rom 7.1.20 or 7.2.16 on mi5. It gets both failed basic integritry and failed cts profile match.
I've also tried on Global Stable 8.1.4.0 with unlocked bootloader and had no luck at all, same error.
This was a clean install, factory wipe, install magisk v11.1. Initially the check couldn't work at all, I had to get google play services updated for anything to work. Then the check operates, but fails on both counts.
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Ulver said:
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
As described by @Ulver if you're on official builds, you should be able to re-lock the bootloader and avoid this issue (although without root I guess).
Aside from that, you definitely shouldn't need the zip I made for the build prop change, as you'll already have a stable build fingerprint
It turns out there's lots of versions of official rom that don't pass safetynet even when cleanly flashed with locked bootloader - xiaomi themselves keep breaking it!
A little search finds lots of references, such as this entire thread, and this post in particular: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=273319&pid=7515203
This certainly complicates things....
Turns out you can't always re-unlock....
To test more thoroughly I decided to flashtool wipe and lock my mi5 to stable release that's reported to pass safetynet; global_images_V8.0.2.0.MAAMIDG
My plan is to verify that it passed when locked (it did), then unlock and just install magisk to see if that worked to hide.
Well, MiUnlock has told me I can't unlock, I logged back into unlock web site and it now says my unlock request is rejected (on same account as I originally unlocked on). So now I have a locked device on global stable and have to wait for re-application to unlock.
FWIW I then allowed MIUI to OTA update itself to 8.1.2.0(MAAMIDI) and then safetynet helper originally told me no, fail on both basic and cts.
Ran it a couple more times though and now it's passing. go figure... safetynet is somewhat unreliable.
tl;dr don't re-lock your phone assuming you'll be able to immediately re-unlock it, it clearly works some of the time, not always though.
Good news, I've got SafetyNet pass on xiaomi.eu (MIUI) rom with unlocked bootloader
In the end it's basically the same as the original LOS method except that as we've all seen earlier Magisk v11.1 isn't working for MIUI.
This win was achieved with Magisk v9 and phh-superuser-magisk-r266-2 with the current Magisk Manager (4.2.6)
As per the screenshot I'm running xiaomi.eu MUIU 8.3 7.2.24 in Mi5
My procedure was:
* dirty flash rom to clean up prior attempts (Install) xiaomi.eu_multi_MI5_7.2.24_v8-7.0.zip
* Install gemini-safetynetpass-stable-fingerprint-20170217.zip
* Install Magisk-v9.zip
* Install phh-superuser-magisk-r266-2.zip
* Reboot.
Simple as that, Magisk Manager shows SafetyNet passing (after asking for root privs on first launch)
I've added a new card in Android Pay, haven't tested at a terminal yet though.
If anyone's interested I previously got SafetyNet passing on MIUI with a custom kernel instead of Magisk, this gave SafetyNet green without any kind of root.
The problem with custom kernel's at this stage is the capacitive buttons (back and app switch) have reduced sensitivity / only work well when the phone is charging. AFAIK this is only really a problem on phones with LGD lcd's (what I have), the other ones might work fine.
If anyone wants to try my kernel instead let me know and I'll share it, I found it to be a bit flaky though.
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
rafix96 said:
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
Click to expand...
Click to collapse
Which version of which rom did you try?
coronafire said:
Which version of which rom did you try?
Click to expand...
Click to collapse
I would definitely would like to confirm this on the latest miui official global dev
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
rafix96 said:
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
Click to expand...
Click to collapse
That's annoying, 7.2.24 is what works for me. It's been my daily driver since, and I've used android pay at a terminal no worries.
Do you definitely have Magisk v9 and phh-superuser-magisk-r266-2.zip ?
Magisk v11 cannot be installed else a dirty flash will be needed.
Oh, I just remembered I've also installed the 'phh's SuperUser' app from Play Store. This is probably needed
After that I opened Magisk Manager, which asked for root permissions the first time (which has to be granted).
@coronafire
Yes i tried everything but i have another one idea, when i come back to home i did MiFlash and then install eu 7.2.24 maybe will work.
Wysłane z mojego MI 5 przy użyciu Tapatalka
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
hklam0 said:
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
Click to expand...
Click to collapse
Just to note, this is only for LineageOS, not MIUI.
Personally I find it easier to not need to replace the kernel and just install magisk, if root isn't wanted it can be disabled in the magisk app.
But yes it's true you can replace the kernel with a patched one, avoiding installing any kind of root.
I've experimented with this quite a bit myself, however to update it requires at a minimum applying a patch/commit to a fork of the kernel source you're starting with and compiling it.
I've got a fork of the MIUI kernel from @Shaky156 with the appropriate patch:
https://github.com/andrewleech/Mi5-...mmit/66cbe734eb15d2508a5c80157a8af38d59373535
and example build script:
https://github.com/andrewleech/Mi5-MIUI8-Nougat-Kernel/blob/master/build.sh
Or there's the original patch by @Sultanxda which usually works as well, I did test this on a LineageOS kernel but this is pretty out of date too by now, and I started from a different forked kernel anyway.
https://github.com/andrewleech/andr...mmit/f8314c10146971979ad26c881be9bd17603c1e7d
A catalogue of errors I've been through to get this phone working.
I basically tried a custom rom, didn't like it, tried to go back to stock and been stuck in this limbo ever since.
I've managed (after 2 days of trying) to get into a stock rom now. Bootloader is still unlocked.
However, I fail the safetynet check, cts profile match false.
I've tried stock firmware, flashing in fastboot, you name it. Nothing seems to work.
I think part of the problem is while all this has been going on, my build number shows something very odd.
It shows,
8.0.0.046(0ECN)
Click to expand...
Click to collapse
Wtf is that? And no matter what I flash, that never changes. Is that a real build?
I was smart enough not to make a note of the original build details before I messed with it.
Any ideas? I'm so fed up with this, I really need Google pay working again.
All I want is to wipe everything out and put a stock proper image on this device and use it.
for me on 3 huawei phones (p9, p20 lite and honor 8) safety net isnt working all time. only when i rooted with magisk, then i got success message. without magisk all time are failed. Even clear stock flashed are failed.
adn about "8.0.0.046(0ECN)" see here : read post 4
Flash Magisk 16.4.
Also, it seems like it doesn't effect apps. Google Pay and Snapchat works fine even SafetyNet fails CTS profile.
Flashed the MIUI EU 11.0.6 and cts profile is false but basic integrity shows true. Also, play store shows "device not certified"
I've already used Magisk hide for Google Play services. Tried to re-flash magisk but still the same.
ROM: MIUI 11.0.6 EU Q
Kernel: Sesh 5.1 71Hz
Recovery: Official TWRP recovery
Magisk 20.3
Solution:
https://forum.xda-developers.com/poco-f1/themes/guide-edxposed-miui-11-0-4-android-q-t4050773/page3
MasterFURQAN said:
Flashed the MIUI EU 11.0.6 and cts profile is false but basic integrity shows true. Also, play store shows "device not certified"
I've already used Magisk hide for Google Play services. Tried to re-flash magisk but still the same.
ROM: MIUI 11.0.6 EU Q
Kernel: Sesh 5.1 71Hz
Recovery: Official TWRP recovery
Magisk 20.3
Click to expand...
Click to collapse
Google changed cts from their end. No matter what rom you flash on any phone you use, it'll fail CTS now. Wait for magisk to be updated.
Daruwalla said:
Google changed cts from their end. No matter what rom you flash on any phone you use, it'll fail CTS now. Wait for magisk to be updated.
Click to expand...
Click to collapse
Just read the article. Thanks anyways.
Xposed installed? If yes you should try this module for pass the safetynet
https://forum.xda-developers.com/showpost.php?p=81982121&postcount=80
Works for me
vjbenn said:
Xposed installed? If yes you should try this module for pass the safetynet
https://forum.xda-developers.com/showpost.php?p=81982121&postcount=80
Works for me
Click to expand...
Click to collapse
I found that out some days ago. I forgot to edit the OP.
FYI this module only fakes the status of the CTS profile. You can check your "true" status by using an app called safety net checker from play store.
Tried every one of the exposed module and all fail so that is no good for me...... anything else that will work..... even stock ROMs with unlocked bootloader with out root come up as device uncertified have a realme 5 with locked bootloader and it is fine have LG v20 it's fine and a Asus Zenfone 3 ultra locked no issues have pocof1 unlocked bootloader and it fails...........
It appears it is bootloader unlocked is what the issues is......the problem is you can't lock bootloader if you want custom recovery the problem is if you have a locked bootloader and you get jacked by someone you can't recover your device.......
Or maybe that's what Google wants to happen......
stinka318 said:
Tried every one of the exposed module and all fail so that is no good for me...... anything else that will work..... even stock ROMs with unlocked bootloader with out root come up as device uncertified have a realme 5 with locked bootloader and it is fine have LG v20 it's fine and a Asus Zenfone 3 ultra locked no issues have pocof1 unlocked bootloader and it fails...........
Click to expand...
Click to collapse
Mine passes the CTS check now even without the edXposed module.
stinka318 said:
It appears it is bootloader unlocked is what the issues is......the problem is you can't lock bootloader if you want custom recovery the problem is if you have a locked bootloader and you get jacked by someone you can't recover your device.......
Or maybe that's what Google wants to happen......
Click to expand...
Click to collapse
MasterFURQAN said:
Mine passes the CTS check now even without the edXposed module.
Click to expand...
Click to collapse
Flashed no gravity kernel and my problem went away as well I believe it has something to do with how Google receives information about the bootloader in the kernel.......
It was working ok for me till today. I had the problem with cts profile : false, then it clears from itself (google change something or revert the changes) , but now I checked randomly in magisk manager and this time I got both cts profile false and basic integrity false , so think google change the things again and even more restrictive than previous time , anyone else can confirm ?
I had Stock Android 9 with Magisk before without TWRP, but somehow it automatically downloaded the OTA and it started asking to restart my device to update the Android version. I tried to uninstall Magisk through the manager but I messed up since it forced restarted the device. It bootlooped afterwards. I tried to install stock firmware for 9, then 10, both didn't work. Other threads say that I should change the active partition, it worked but now the Manager says the ctsProfile is false. I tried to hide the Magisk through its settings but it didn't work. I also tried to reflash with stock firmware but it didn't work as well. I don't know what to do next. Any advice for what I should do?
The only guaranteed way how to pass the SafetyNet test is to have 100% stock phone (stock ROM and locked bootloader).
Unguaranteed way (possible until Google deploys HW verification which can't be spoofed) is to root phone with Magisk and enable Magisk hide and reboot the phone (default options should be enough). Some modules will automatically break Safetynet (e.g. Xposed).
Edit: I am failing CTS profile test too, so I'd say that Google started with improved SafetyNet deployment again and we're out of luck. You can search main Magisk support thread for further info (e.g. https://forum.xda-developers.com/showpost.php?p=82935207&postcount=40370)
Thank you so much! It seems that the only way for me to pass Safetynet is to relock the bootloader, and I'm worried that it will fail since it is a risky move. Glad that it worked and it prompted me to factory reset, and now updated again to A10 . Guess I will stay in stock for now.
Its very easy! Just have to flash some zip
Sami Devo said:
Its very easy! Just have to flash some zip
Click to expand...
Click to collapse
Congrats, you just earned yourself a bounty for breaking the TEE (about $100.000). You just need to provide this "some zip" and demonstrate the mechanism.
_mysiak_ said:
Congrats, you just earned yourself a bounty for breaking the TEE (about $100.000). You just need to provide this "some zip" and demonstrate the mechanism.
Click to expand...
Click to collapse
???
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just use magisk flash modules
https://drive.google.com/folderview?id=1-D9RKn9bWYQLbm3ODX_xZ_0Xe9mJmROi
And in magisk. Use system hide . Etc
Once its okk pass all cts okk.. u will find Netflix in play store ??
Sami Devo said:
[emoji1787][emoji1787][emoji1787]
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just use magisk flash modules
https://drive.google.com/folderview?id=1-D9RKn9bWYQLbm3ODX_xZ_0Xe9mJmROi
And in magisk. Use system hide . Etc
Once its okk pass all cts okk.. u will find Netflix in play store [emoji1787][emoji1787]
Click to expand...
Click to collapse
Yeah, sure.. Just read a bit about HW Safetynet test, you can't spoof it.
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
d_g_m_2000 said:
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
Click to expand...
Click to collapse
Currently it does not (well on some of the custom ROMs I tried, do t know about stock) but Google are implementing hardware attestation which was mentioned in the comment above which will allow safety net to see an unlocked bootloader status and automatically fail safety net.
It's completely ridiculous but it's happening now. I dont know what this means for custom ROMs but for rooting it's a disaster
d_g_m_2000 said:
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
Click to expand...
Click to collapse
As far as I know, Google is staging the rollout of HW Safetynet test to random people, but it will most probably reach all phones eventually. I am already on "BASIC,HARDWARE_BACKED" type. It should not matter if you have stock or custom ROM, you will fail the CTS test right away with unlocked bootloader as soon as you are migrated to HW test.
garylawwd said:
Currently it does not (well on some of the custom ROMs I tried, do t know about stock) but Google are implementing hardware attestation which was mentioned in the comment above which will allow safety net to see an unlocked bootloader status and automatically fail safety net.
It's completely ridiculous but it's happening now. I dont know what this means for custom ROMs but for rooting it's a disaster
Click to expand...
Click to collapse
_mysiak_ said:
As far as I know, Google is staging the rollout of HW Safetynet test to random people, but it will most probably reach all phones eventually. I am already on "BASIC,HARDWARE_BACKED" type. It should not matter if you have stock or custom ROM, you will fail the CTS test right away with unlocked bootloader as soon as you are migrated to HW test.
Click to expand...
Click to collapse
I thought it only break magisk hide but i see now that it does hurt a lot more. thank you guys for your replies.
d_g_m_2000 said:
I thought it only break magisk hide but i see now that it does hurt a lot more. thank you guys for your replies.
Click to expand...
Click to collapse
Magisk hide actually still works fine, Safetynet is independent from it. My banking app doesn't use Safetynet (yet) and Magisk hides root successfully, so I can use it freely..
_mysiak_ said:
Magisk hide actually still works fine, Safetynet is independent from it. My banking app doesn't use Safetynet (yet) and Magisk hides root successfully, so I can use it freely..
Click to expand...
Click to collapse
My banking app is outrageous. It recognises root, gives me a warning and I'm allowed to proceed with my login as normal. Sorry for ot
garylawwd said:
My banking app is outrageous. It recognises root, gives me a warning and I'm allowed to proceed with my login as normal. Sorry for ot
Click to expand...
Click to collapse
That's exactly how I imagine an ideal banking app. Give a warning or two, maybe request some extra acknowledgement that you are aware of risks and let you use the app in an unrestricted mode. I can't fathom why some apps are so "afraid" of root (especially those which don't work with sensitive personal data or money). But well, eventually I'll have to carry two phones (rooted + stock) or stop using such apps.. [emoji846]
Hi to all, this is my first post here on XDA.
I Was doing a little of research to get Safety Net pass on custom rom's (I Have tested this fix on Z Rom V6, Illussion OS 1.7 and Z Rom Lite v2) And by now, here is the solution, It's not a fake screen telling you that you have passed Safety net like the one you get when you use the Hidden Core Method. This is a real fix.
So now, we're using 2 Magisk modules.
1.-safetynet-fix-v1.1.1
2.-MagiskHidePropsConfig-v5.4.0
Ok, after the download of the 2 zips you need to flash through Magisk, (You need to enable MagiskHide) we'll need to use a terminal emulator to get the safety net pass, then after downloading a terminal emulator we need to follow this tutorial:
After that we need to set the new fingerprint of our device to be ''Samsung Galaxy A20 A205W'' After selecting that fingerprint we need to finish the setup, and then Reebot. after that.... Voila, now our device pass Safety Net on custom roms.
Credits to all of the creators of the modules.
Thanks for this info, will try it out once I rooted my phone again.
I cannot find safetynet-fix on magisk modules.
Did they removed it?
In theory magiskhidepropsconfig alone should do the job, sadly i cannot pass ctsProfile test on my phone that has a custom ROM (Xiaomi Mi note 10).
Not out of the box at least.
It has instructions on how to manually change the fingerprint and the security patch date so to pass the ctsProfile test but they are...complicated
I even followed the instructions on the video but still no dice.
Nadaaaaa said:
I cannot find safetynet-fix on magisk modules.
Did they removed it?
In theory magiskhidepropsconfig alone should do the job, sadly i cannot pass ctsProfile test on my phone that has a custom ROM (Xiaomi Mi note 10).
Not out of the box at least.
It has instructions on how to manually change the fingerprint and the security patch date so to pass the ctsProfile test but they are...complicated
I even followed the instructions on the video but still no dice.
Click to expand...
Click to collapse
You should use the .zip file attached to this thread bro, SafetyNet fix is for hardware attestation and unlocked bootloaders, That's why you should use MagiskHidePropsConfig + SafetyNetFix. Google play services must be enabled and not frozen in order to have SafetyNet working. Check if there is a specific fingerprint for your device. And yes, the module has been removed from magisk repository, You can find the latest version here: https://github.com/kdrag0n/safetynet-fix
@PhillipVilla , i am sorry but could you elaborate a bit more?
I have flashed Havoc 4.6 and Magisk v23 onto my Samsung S8+. I have downloaded the two files you attached. But what do you mean by "flash through Magisk"?
My Google Play Store is working fine my problem is no Netflix in Play Store and my TV provider app is not working. So i am trying to get SafetyNET to pass and possibly hide the fact that the phone is rooted.
TheGeneral said:
@PhillipVilla , i am sorry but could you elaborate a bit more?
I have flashed Havoc 4.6 and Magisk v23 onto my Samsung S8+. I have downloaded the two files you attached. But what do you mean by "flash through Magisk"?
My Google Play Store is working fine my problem is no Netflix in Play Store and my TV provider app is not working. So i am trying to get SafetyNET to pass and possibly hide the fact that the phone is rooted.
Click to expand...
Click to collapse
Magisk is an app you should install. You can search in this forum
I have a Moto G6 and I'm having trouble getting the SafetyNet to go green. Installed Magisk v23 and the SafetyNet Fix and the MagiskHidePropConfig and still no dice. Any suggestions?