Develop Bugs

[Magisk][Module]HTC 10 SafetyNET fix for any ROM

Hello everyone !
As you know this module help you to fix Safetynet by change build fingerprint to Xiaomi Mi 6s
But when you use the original module, Google will show your device as Xiaomi Mi 6s
I made a little modify to change build fingerprint to our HTC stock ROM, it'll show your device as HTC 10
A build will release when the original build release, same time !
Some report said that you can use this module for HTC stock ROM, I can't help you if you got error about this ROM
Download : Move to Download tab
ROM tested : LineageOS (official), RR (official)
This required :
No Xposed and SuperSU, even systemless
Systemless modifications in your system only
MagiskSU
Magisk Hide working properly
Main thread : https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Thanks to : @Deic for his source code
XDA:DevDB Information
HTC 10 (pme) SafetyNET fix, Tool/Utility for the HTC 10
Contributors
hiimpig1
Source Code: https://github.com/piiiggg/xiaomi-safetynet-fix/tree/pme
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-28

Update some screenshot
Tested on : LOS official and RR official ROMs

Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!

azZA_09 said:
Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!
Click to expand...
Click to collapse
Thanks, I'll note it on #1

Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.

tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
I think you have to enable force encrypt when install magisk, try this
Install any kind of root like supersu - download magisk manager - install magisk without disable force encrypt - uninstall supersu - install module
I never use stock rom so idk, I only tested on custom ROM

tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.

lichan said:
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.
Click to expand...
Click to collapse
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?

hiimpig1 said:
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?
Click to expand...
Click to collapse
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.

lichan said:
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.
Click to expand...
Click to collapse
Radio not working on stock ROM because encryption not enable, a guy was taking about this before. Or changing stock ROM bootloader status could cause this problem.

It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix

aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
Sorry, I was sold my device. You can learn how to make new version of this module on main thread

aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
The 13.3 update was released last night, thos should fix.

Magisk SafetyNet fails after awhile

I've been experiencing losing SafetyNet pass with Magisk after the phone has been on for awhile. Has anyone seen this issue before?
I'm on Magisk v14.5 with Magisk Manager v5.4.0, on Android 8.1 (happened on 8.0 too). I already tried flashing a different kernel, but this issues still happens.
SafetyNet passes again after restarting my phone.
Any help will be appreciated. Thanks!

Try updating magisk to 5.4.3 that's the newest one. I'm also on the beta channel you can change it in the setting. And you should be good.
Edit
Link to the newest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

I was on the new magisk 5.4.3, and the failure still happens. I only downgraded to 5.4.0 to avoid the dtbo.img failure right now.

Oneplus 5T with OxygenOS, TWRP and Magisk 17.1 SafetyNet fail after a few hours

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

Oxygen OS 10.0.14.HD65AA + Magisk + EdXposed Failing SafetyNet

So I had everything working perfectly, and then I updated to Oxygen OS 10.0.14.HD65AA.
I was greeted with a bootloop after doing the update, so I removed all of my Magisk modules and it booted up.
Next, I reinstalled all my modules. After reinstalling Riru EdXposed, I could no longer pass the SafetyNet check (it passes without EdXposed enabled).
I have tried a few different EdXposed versions, including v0.5.0.6 (4564) canary.
Is anyone else able to pass SafetyNet on 10.0.14 with EdXposed?

Exposed breaks safenet

ChrisFeiveel84 said:
Exposed breaks safenet
Click to expand...
Click to collapse
As I said, it was working fine before the update.
But I also updated Magisk to v21 when I did the OTA, so not sure if that had an effect as well.

TuRDMaN said:
As I said, it was working fine before the update.
But I also updated Magisk to v21 when I did the OTA, so not sure if that had an effect as well.
Click to expand...
Click to collapse
the problem is edxposed. I changed nothing in the last few days and yesterday suddenly safetynet fails. Still did mobile payment with gpay 2 days ago so I'm sure the problem started yesterday. Apparently google do some change in safetynet attestation

TuRDMaN said:
So I had everything working perfectly, and then I updated to Oxygen OS 10.0.14.HD65AA.
I was greeted with a bootloop after doing the update, so I removed all of my Magisk modules and it booted up.
Next, I reinstalled all my modules. After reinstalling Riru EdXposed, I could no longer pass the SafetyNet check (it passes without EdXposed enabled).
I have tried a few different EdXposed versions, including v0.5.0.6 (4564) canary.
Is anyone else able to pass SafetyNet on 10.0.14 with EdXposed?
Click to expand...
Click to collapse
I just had the same thing happen to me this morning. I restored images in magisk, then updated and installed magisk onto inactive slot before rebooting. Then the bootloop. How did you get out of the bootloop and disable your magisk modules without resetting your device with the msmdownload tool?

[OOS13] IN2023_11_F.13 Patched boot.img

Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F13-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive

Thanks for this. Where can you download the oos13 firmware?

MR0808 said:
Thanks for this. Where can you download the oos13 firmware?
Click to expand...
Click to collapse
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features

Thanks. Looks like I'm getting IN2025, so will have to do the patched boot.img myself.
Time to find my old notes somewhere

Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF

GhostRider86 said:
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
Click to expand...
Click to collapse
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know

Neil_Armstrong_ said:
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Click to expand...
Click to collapse
I keepted mine as well, SafetyNet and gPay are working, but Unlock with Fingerprint Sensor is not. No reaction to sensor at all, not able to register new Finger...
Edit: Working now. Needed to disable USNF module, no reboot, Fingerprint Sensor working, register Fingers, screen lock, test, enable USNF module, enjoy

Neil_Armstrong_ said:
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Click to expand...
Click to collapse
I already have the fil, but I can't install it from system update apk,
am I missing something ?
EDIT:
re-downloaded the file again from Oxygen updater, but still it fails to install nd also "verification failed" in system local update.
Edit 2:
I re MSM back to OOS11 and upgraded directly to OOS 13 F3.

Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works

Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help

VBBoston said:
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
Click to expand...
Click to collapse
I updated from oos 13 unrooted. Lost my root using oos12

I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~

VBBoston said:
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
Click to expand...
Click to collapse
They have already been shared here.

Thank you very much!

stell52 said:
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Click to expand...
Click to collapse
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated

Neil_Armstrong_ said:
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Click to expand...
Click to collapse
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks

MrBloB said:
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Click to expand...
Click to collapse
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know

MrBloB said:
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
Click to expand...
Click to collapse
Flash Universal SafetyNet module in magisk (kdrag0n) and Magisk Bootloop Protector (just in case)
Check your status after a reboot with YASNAC from Play Store
Force the Magisk DenyList, and when configuring it, develop the apps and check all the tick boxes manually (to be sure)
Uninstall Netflix and install the latest .apk from APKMirror, can't help as other app (banking too) works fine

Isn't vanced dead ?
YouTube Premium Argentina is very affordable fyi ....
stell52 said:
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
Click to expand...
Click to collapse

stell52 said:
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
Click to expand...
Click to collapse
Yes i have done this. Tried shamiko as well. M passing safetynet checks, still it doesnt work.