Did it pass before you rooted it?Thanks so much for your detailed reply. Unfortunately, my device never passed safetynet after I rooted it, so the props method is not an option. I'm not really familiar with how to extract the fingerprint from a firmware download. I see what you mean about 1.1.1 failing. However, i'm using a rooted firmware with 1.1.0 which seems to download from their website just fine. If you are to find it without too much trouble I'd be grateful. Thanks in advance!
EDIT: I'm making progress. I figured out how to identify the fingerprint. Now, I'm stuck because it fails. Based on the documentation, i'm guessing this is because the security patch date is incorrect. I tried to change it to the release date of 12/30/20, but this didn't work. Is there a way to tell this from the package what date to use? Thanks!
If the only modification you did was to root a stock rom, then the fingerprint and security date will still be correct.
Make sure to enable MagiskHide in the Magisk app.
Settings-> Toggle MagiskHide on.
If the device is not Google certified, the stock fingerprint and security date will not be certified.
Using this module to set the fingerprint and security date to the same will give the same result.
You will have to pick a certified fingerprint with the matching security date.
The fingerprints included in this module have the matching security dates if necessary.
I downloaded an took a look at the M11 v1.1.0 OTA.
Used the recovery image from the OTA to pull the props.
It failed SafetyNet for me but.. ¯\_(ツ)_/¯
If you want to try, rename the attached file to
printslistand copy it to
Custom fingerprints list GitHub - Link
A bit OT for this thread but, it would help me narrow something down.
Could you revert the changes you made, no need to unroot, and then reboot.
Then using a terminal app or an adb shell session.
getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' >/sdcard/Download/m11-getprop.props;
Then attach the m11-getprop.props file to a post or send me a link to it.
The generated file should be in your Download directory.
It will help me fix an issue in my mHideGP script.
Even though this device is not on the certified.list, it triggered the certified.list MHIDE print configuration for some reason??
Interesting device for sure.