Database Develop

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

Magisk SafetyNet Failure

Hello ,
I Use Magisk 14 And SafetyNet Check Failure And i uninstall it and install Magisk 14.5 and still same problem and i try to fix this problem same : Disable (Usb Debugging - Oem unlocking ) Hide root from all google apps by Magisk and Enable and disable (Magisk Core only mode) and problem still please any one help me to fix this problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Start by reading here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

I Try all and dont fixed
But i got this pop-up and when i click yes get nothing
Please Help me

HassanSalah120 said:
I Try all and dont fixed
But i got this pop-up and when i click yes get nothing
Please Help me
Click to expand...
Click to collapse
You can't have read through the whole thing, because you clearly missed the part about providing logs...

If you changed your SELinux to Permissive, SafetyNet check will fail. Change it back to Enforcing (no need to reboot, it should immediately pass the next time SafetyNet is checked).
Obviously if you did not change it this is unlikely to be the issue.
You may also wish to check any root apps you use and see if they might be doing anything which would trigger Safetynet failure.

The MAZZTer said:
If you changed your SELinux to Permissive, SafetyNet check will fail. Change it back to Enforcing (no need to reboot, it should immediately pass the next time SafetyNet is checked).
Obviously if you did not change it this is unlikely to be the issue.
You may also wish to check any root apps you use and see if they might be doing anything which would trigger Safetynet failure.
Click to expand...
Click to collapse
MagiskHide can hide a permissive SELinux. You might have to restart the Magisk daemon though...

What can I do to it work ??

Are you have a custom kernel?
If yes then i think the SafetyNet will always fail.

Eng.Raman said:
Are you have a custom kernel?
If yes then i think the SafetyNet will always fail.
Click to expand...
Click to collapse
Not the case... SafetyNet works fine with custom kernels. Of course, knowing the multifaceted, fractured Android world, there's probably going to be a few cases where a custom kernel will trigger SafetyNet. YMMV...
SafetyNet checks if your device is a recognised, certified device. If it isn't, you can't pass CTS, but you can still pass basic integrity.
It then also checks if the device is rooted, have Xposed installed, if the bootloader is unlocked, if SELinux is permissive and possibly a few of other things. If any of this returns true, SafetyNet fails.
Magisk can hide itself and most modules (depending on what they do), an unlocked bootloader and a permissive SELinux. It also changes a few prop values to recognised safe ones.

Eng.Raman said:
Are you have a custom kernel?
If yes then i think the SafetyNet will always fail.
Click to expand...
Click to collapse
No I don't have custom kernel

Didgeridoohan said:
Not the case... SafetyNet works fine with custom kernels. Of course, knowing the multifaceted, fractured Android world, there's probably going to be a few cases where a custom kernel will trigger SafetyNet. YMMV...
SafetyNet checks if your device is a recognised, certified device. If it isn't, you can't pass CTS, but you can still pass basic integrity.
It then also checks if the device is rooted, have Xposed installed, if the bootloader is unlocked, if SELinux is permissive and possibly a few of other things. If any of this returns true, SafetyNet fails.
Magisk can hide itself and most modules (depending on what they do), an unlocked bootloader and a permissive SELinux. It also changes a few prop values to recognised safe ones.
Click to expand...
Click to collapse
I unlocked bootloader what can I do

HassanSalah120 said:
I unlocked bootloader what can I do
Click to expand...
Click to collapse
MagiskHide hides the unlocked bootloader state. That's not your issue.... Go back to the link I provided earlier and take a look at the "Asking for help" section.

Didgeridoohan said:
Not the case... SafetyNet works fine with custom kernels. Of course, knowing the multifaceted, fractured Android world, there's probably going to be a few cases where a custom kernel will trigger SafetyNet. YMMV...
SafetyNet checks if your device is a recognised, certified device. If it isn't, you can't pass CTS, but you can still pass basic integrity.
It then also checks if the device is rooted, have Xposed installed, if the bootloader is unlocked, if SELinux is permissive and possibly a few of other things. If any of this returns true, SafetyNet fails.
Magisk can hide itself and most modules (depending on what they do), an unlocked bootloader and a permissive SELinux. It also changes a few prop values to recognised safe ones.
Click to expand...
Click to collapse
A device that has a custom kernel, Google play store certification status will be uncertified. Is that right?

Eng.Raman said:
A device that has a custom kernel, Google play store certification status will be uncertified. Is that right?
Click to expand...
Click to collapse
Not necessarily. I have three different devices right here. All with custom kernels and all pass SafetyNet and are Play store certified.

Now its success after refalshing rom
but when enable Xposed its failure is there any way to enable xposed and Safetynet Success ?

Well, I've got the same problem. Magisk 15.3 on IronMan 1.1.0 for S7 edge.

georgedao123 said:
Well, I've got the same problem. Magisk 15.3 on IronMan 1.1.0 for S7 edge.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

HassanSalah120 said:
Now its success after refalshing rom
but when enable Xposed its failure is there any way to enable xposed and Safetynet Success ?
Click to expand...
Click to collapse
Seriously? No. Just, no.

i also having this problem. before i install xposed for API27 (I use Oreo AOSP rom) my safetynet status is true. after I install xposed Magisk version, i got false. i thought it will works but it gives me this problem...

Bootloop after installing Xposed via Magisk

I've got the Google Fi variant of the Moto X4 (XT1900-1). It's running stock build OPW28.46-18 (Android 8.1). TWRP 3.2.1-1. I was able to install the latest Magisk no problem and I have working root access. My issue arises when I try to install the Magisk variant of Xposed Framework. When I do this and reboot, the phone seemingly gets caught in a bootloop. I've let it sit for 15-20 minutes to see if it would recover and it does not. To exit the loop, I reboot to fastboot then to TWRP and flash a ZIP that allows me to uninstall Magisk modules right from TWRP. Reboot and phone works fine.
I've tried both versions of the Xposed Framework in the Magisk downloads section (the smart version that automatically chooses the proper framework, and the explicit SDK 27 version), as well as downloaded the ZIP and tried to install it from TWRP. Similar result in all cases. I have only tried the "systemless" Xposed that works with Magisk thus far.
Has anyone else run into and dealt with this issue, or have any suggestions? I'd really like to get Xposed working so I can get XPrivacyLua going and switch over to using this phone as my daily driver.

how are you flashing Xposed? from Recovery or magisk?

abhi212b said:
how are you flashing Xposed? from Recovery or magisk?
Click to expand...
Click to collapse
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.

I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.

Neffy27 said:
I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.
Click to expand...
Click to collapse
There's been a beta version for Oreo 8.0/8.1 since maybe January (t's on beta version 3 now I think). I'd tried it on my OnePlus 3 with success. I thought maybe it was a Moto X4 issue and I might as well check here first to see if anyone else with this phone had already run into this and fixed it. I'll go ahead and ask the question in the Xposed section of the forum. Thanks!

Seems the OP of this thread has Xposed working: https://forum.xda-developers.com/moto-x4/help/oreo-magisk-xposed-modules-reboot-t3745612 - Maybe they could help.

Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for posting that

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).

I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.

dcdruck1117 said:
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).
Click to expand...
Click to collapse
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!

solara1973 said:
I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.
Click to expand...
Click to collapse
Thanks for the info. You're correct about SafetyNet and Android Pay; I gave up on Android Pay years ago for that reason, because Xposed is too important to me to give it up. Perhaps I'll try starting from scratch again with this phone. I'm hesitant to flash ROMs on this phone, stock or otherwise, because of the scarcity of factory images available should something go terribly wrong..
abhi212b said:
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!
Click to expand...
Click to collapse
Thank you. I think I'll try to start over and see if I can get it to work. Or maybe I will try using the regular version of Xposed (not the Magisk version).
If you know of a repository of factory images for the Android One version, that would be helpful. I'm finding some images for the retail version but not much love for the A1 version.
Edit: I just found this post which seems like it may contain what I'm looking for, "Latest Project Fi Firmware (Android 8.1)": https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

I flashed back to stock using the files from the link in my previous post. The weird thing there is that SafetyNet fails immediately now, clearly some side effect of flashing back the stock images. Anyway, I again installed TWRP, then Magisk, then Xposed, and again ran into the same boot loop. I don't know what else to try other than to wait for maybe a new Xposed beta, or maybe try an even older Oreo build on this phone and see how that works.
I've run Xposed (and more recently, Magisk+Xposed) on every Android device I've owned since Xposed has been in existence, and this is the first phone to ever give me trouble.

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.

AvenidaDelGato said:
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.
Click to expand...
Click to collapse
Thank you, that's good to know because I'm also on 8.1, so it sounds plausible that it's not just me, but a larger compatibility issue between Xposed and 8.1. on this phone.

Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!

dcdruck1117 said:
Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!
Click to expand...
Click to collapse
I've been putting off unlocking bootloader due to my recent concerns with these ota patches being released.
If safetynet fails, what can you not use besides Pay? It's to my understanding safetynet is now being incorporated to several applications and failing, will result in a sometimes inoperable app altogether?

dcdruck1117 said:
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.
Click to expand...
Click to collapse
Use EdXposed, works for me, and pass Safetynet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Csprofile false still not getting resolved!

Phone: Redmi Note 7 Pro (Violet)
Bootloader: Unlocked
Issues: Magisk ctsprofile false
Troubleshooting:
I'm caught up in a very weird tough situation.
All was going good until I installed edxposed and gravitybox and some modules and since then Magisk kept returning ctsprofile false.
So I flashed stock MI rom using MIFlash tool and also re-locked BL.
So at this time the phone is just like a factory one..no magisk/xposed etc.
Then UL Bootloader and re-flashed twrp and same rom.
This time it should had worked but again Magisk kept returning ctsprofile false.
This is so frustrating.
I tried other roms as well like pixel exp. without any xposed crapp etc. but all showing ctsprofile false.
Tried updating magisk to latest and even downgrading but to no vail.
I even tried MagiskHidePropsConf-v4.0.3 but it didnt worked.
Tried magisk hide but no luck.
All safetynet check apps fail test.
Tried SafetyPatch-v3 and it worked but keep giving very annoying error on system boot about some huawei thing and have to ok everytime.
Any valuable suggestions to fix this for good??

If Safetypatch works, then MagiskHide Props Config should work as well. Did you set up a certified fingerprint after having installed the module? It's not a flash-and-forget module, it takes a bit of setup as well.
Safetypatch uses the same method, but doesn't let you pick a fingerprint, which is why you might get the error you're seeing. If you really want to use Safetypatch, you can get around that by editing the module boot script and replace the default fingerprint with one of your own, and also enabling editing of the vendor fingerprint (that's disabled by default in that module).
More info on SafetyNet, with tips and tricks can be found here:
https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Didgeridoohan said:
editing the module boot script and replace the default fingerprint with one of your own, and also enabling editing of the vendor fingerprint (that's disabled by default in that module).
Click to expand...
Click to collapse
Hey thanks for the reply.
Can you please post a noob guide as to where to/how to find or define my own fingerprint and also edit vendor fingerprint?
Also, as I described, initially all was good but after xposed all screwed up. Even stock miui rom and then unlocking of BL isn't helping.
May I know the actual reason behind it as why reflashing different roms even after starting from scratch isnt helping to CSprofile True.

Those ROMs likely don't have a certified device fingerprint. It's also possible that Google tightened up something about that recently, so that fingerprints that did work without a correspond safety patch date now don't. That's pure guesswork on my part though, don't take it as fact.
The noob way of doing it would be to use MagiskHide Props Config and pick a fingerprint from the included list. Unfortunately I don't have a violet print in there at the moment... Luckily you can use whatever print that is certified, but if you really want a print from your device you can take a look a little further down in the docs for instructions.
If you find a matching print, you can use it in the module (by entering it manually), but also submit it in the module thread for me to include it in the list. Of course, you could also use it with Safetypatch by editing the module files found in /data/adb/modules/safetypatch (just replace the Huawei print with yours).

Didgeridoohan said:
Those ROMs likely don't have a certified device fingerprint. It's also possible that Google tightened up something about that recently, so that fingerprints that did work without a correspond safety patch date now don't. That's pure guesswork on my part though, don't take it as fact.
The noob way of doing it would be to use MagiskHide Props Config and pick a fingerprint from the included list. Unfortunately I don't have a violet print in there at the moment... Luckily you can use whatever print that is certified, but if you really want a print from your device you can take a look a little further down in the docs for instructions.
If you find a matching print, you can use it in the module (by entering it manually), but also submit it in the module thread for me to include it in the list. Of course, you could also use it with Safetypatch by editing the module files found in /data/adb/modules/safetypatch (just replace the Huawei print with yours).
Click to expand...
Click to collapse
Just wanna know what if I reflash stock miui rom and just extract its fingerprint from build.prop and after flashing back Havoc rom and rooting, use this original fingerprint with SafetyPatch-v3.zip, will this work?
And currently most of the suers have already flashed SafetyPatch-v3.zip which uses huawei fingerprint, will it be possible google might blacklist/block that as well?

nri_tech1183 said:
Just wanna know what if I reflash stock miui rom and just extract its fingerprint from build.prop and after flashing back Havoc rom and rooting, use this original fingerprint with SafetyPatch-v3.zip, will this work?
Click to expand...
Click to collapse
As long as that ROM is CTS certified it should work just fine.
And currently most of the suers have already flashed SafetyPatch-v3.zip which uses huawei fingerprint, will it be possible google might blacklist/block that as well?
Click to expand...
Click to collapse
Possible but very unlikely.

Nice.
So I finally found 3 fingerprints from stock redmi violet from earlier updates.
10.3.5.0
10.3.7.0
10.3.13.0
What now I plan is to edit post-fs-data.sh file in SafetyPatch-v3.zip to replace the Huawei fingerprints with redmi ones.
But before that how to remove existing SafetyPatch-v3?
Shall I reflash it from recovery to get uninstalled or simply delete from magisk module list to reset it so I can then flash the edited SafetyPatch created properly from twrp?
And most importantly, after flashing redmi fingerprint will the CTSprofile return True value or is it a hit or miss?
And will I still get this similar alert later on as well? Actually want to get rid of this alert on every boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do we need to edit vendor.img for this??

You don't have to remove anything... Just edit the file as it is in the module directory under /data/adb/modules and reboot.
To get rid of the warning message, just make sure to also remove the # in front of the vendor prop (and replace all the fingerprints with your own).
It is not certain that the prints will work for you, since you might also need the security patch date from the release you're using. Or the prints aren't actually certified. Only way to know is to test.
Would you mind posting the prints (and security patch date) so I can test them and add to the list included in MagiskHide Props Config?

Didgeridoohan said:
You don't have to remove anything... Just edit the file as it is in the module directory under /data/adb/modules and reboot.
Click to expand...
Click to collapse
Do I need to do it from the twrp terminal, adb, or simply can be done from the OS itself using some file explorer?
Didgeridoohan said:
To get rid of the warning message, just make sure to also remove the # in front of the vendor prop (and replace all the fingerprints with your own).
Click to expand...
Click to collapse
You mean that inside SafetyPatch-v3, edit "post-fs-data" file
and remove "#" resetprop ro.vendor.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys' right?
I hope it wont result into any bootloop.
Or is there any other seperate vendor.prop file (which I didnt found in roms nor in my phone).
Didgeridoohan said:
It is not certain that the prints will work for you, since you might also need the security patch date from the release you're using. Or the prints aren't actually certified. Only way to know is to test..
Click to expand...
Click to collapse
True, we need to keep experimenting but I wonder how come some other devices fingerprints helps us to pass ctsprofile safetynet test?
For latest devices can we use old devices fprints like redmi note 3 or nexus or pixel? I think pixel will be too good as its google device and spoof free!
Didgeridoohan said:
Would you mind posting the prints (and security patch date) so I can test them and add to the list included in MagiskHide Props Config?
Click to expand...
Click to collapse
Surely mate I will message you all of them. I found those fprints in prop.default file so will share the file contents with you.

nri_tech1183 said:
Do I need to do it from the twrp terminal, adb, or simply can be done from the OS itself using some file explorer?
Click to expand...
Click to collapse
From OS works fine. That file is only run during boot.
You mean that inside SafetyPatch-v3, edit "post-fs-data" file
and remove "#" resetprop ro.vendor.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys' right?
Click to expand...
Click to collapse
That's exactly it.
True, we need to keep experimenting but I wonder how come some other devices fingerprints helps us to pass ctsprofile safetynet test?
For latest devices can we use old devices fprints like redmi note 3 or nexus or pixel? I think pixel will be too good as its google device and spoof free!
Click to expand...
Click to collapse
Some print are certified by Google, others are not. And old (before March 2018) certified prints don't need the safety patch date to match. Everything about SafetyNet is pretty thoroughly explained in the links I've posted here previously, so I suggest you also take a look there.

Didgeridoohan said:
From OS works fine. That file is only run during boot.
That's exactly it.
Some print are certified by Google, others are not. And old (before March 2018) certified prints don't need the safety patch date to match. Everything about SafetyNet is pretty thoroughly explained in the links I've posted here previously, so I suggest you also take a look there.
Click to expand...
Click to collapse
Hey I succeeded in removing the Huawei warning error prompt.
In your file "post-fs-data.sh"
you stated:
resetprop ro.vendor.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys'
#The above caused issues (critical services not starting) on my Honor
What do you meant by #The above caused issues (critical services not starting) on my Honor
What all services failed to or were not running in your Honor?
I didnt find anything unusual on my phone, but would still like to verify if any critical services arent running.
How to check them out?

That's not my statement... I'm the creator of MagiskHide Props Config, not Safetypatch. I don't know what he was referring to.

Didgeridoohan said:
That's not my statement... I'm the creator of MagiskHide Props Config, not Safetypatch. I don't know what he was referring to.
Click to expand...
Click to collapse
How to share redmi note 7 pro stock fingerprints with you? Shall I pm you?

nri_tech1183 said:
How to share redmi note 7 pro stock fingerprints with you? Shall I pm you?
Click to expand...
Click to collapse
That works. Thank you.

Didgeridoohan said:
That works. Thank you.
Click to expand...
Click to collapse
Have sent you fingerprints.
Also wanna ask, now that I'm using huawei fingerprint with SafetyPatch-v3 and ctsprofile is reporting true, can I still install edxposed and yet retain ctsprofile values to true?

nri_tech1183 said:
Have sent you fingerprints.
Also wanna ask, now that I'm using huawei fingerprint with SafetyPatch-v3 and ctsprofile is reporting true, can I still install edxposed and yet retain ctsprofile values to true?
Click to expand...
Click to collapse
Thank you. Received.
As far as I know (I don't use EdXposed) Google can't detect (or doesn't yet look for) EdXposed so you should be good to go.

Didgeridoohan said:
Thank you. Received.
As far as I know (I don't use EdXposed) Google can't detect (or doesn't yet look for) EdXposed so you should be good to go.
Click to expand...
Click to collapse
Asking as installing exposed kills the cts thing and makes it false.
In short if you installed Xposed then there is no possible way to pass safety net.
If you can research and do let me know it will be great as I really need some exposed modules to run which aren't yet available in magisk modules.

nri_tech1183 said:
Asking as installing exposed kills the cts thing and makes it false.
In short if you installed Xposed then there is no possible way to pass safety net.
If you can research and do let me know it will be great as I really need some exposed modules to run which aren't yet available in magisk modules.
Click to expand...
Click to collapse
You're talking about different things now...
It's true that Xposed will trigger SafetyNet, no matter what, but from what I've seen EdXposed doesn't (although I might not be up-to-date on that).
Note the difference in names. They're very similar, but work slightly different.

nri_tech1183 said:
Have sent you fingerprints.
Also wanna ask, now that I'm using huawei fingerprint with SafetyPatch-v3 and ctsprofile is reporting true, can I still install edxposed and yet retain ctsprofile values to true?
Click to expand...
Click to collapse
Didgeridoohan said:
Thank you. Received.
As far as I know (I don't use EdXposed) Google can't detect (or doesn't yet look for) EdXposed so you should be good to go.
Click to expand...
Click to collapse
@nri_tech1183 / @Didgeridoohan can you pls send me too the device fingerprints for violet?
I am using xiaomi.eu ROM on my Redmi Note 7 Pro (violet) and recently updated to xiaomi.eu MIUI 11 and Playstore is not ceritifed. It seems xiaomi.eu has been using lavender fingerprints which is not the best case. And also works on & off.
PS: Happy to test out if required.

Didgeridoohan said:
You're talking about different things now...
It's true that Xposed will trigger SafetyNet, no matter what, but from what I've seen EdXposed doesn't (although I might not be up-to-date on that).
Note the difference in names. They're very similar, but work slightly different.
Click to expand...
Click to collapse
Now that all is working good I wanna risk running Edxposed on my phone.
Just let me know what all backups do I need to take inside TWRP before flashing Edxposed so that if safetynet check fails later I can restore my phone toe earlier state.

booting to black screen with Mar 2020 update and Magisk stable/beta

any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!

dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?

Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?

dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126

Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!

dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d

Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time

dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?

EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!

dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?

So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?

dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.

EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.

dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.

Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?

EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.

Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be

dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.

EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.

1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.