Afaik, I updated my Pixel 4a to November 2020 update, Play store showing that 'device is not certified'. Anyone facing same?
It is certified for me
Mine was certified until I unlocked the bootloader.
When I rooted I was able to install a Magisk module and it showed certified. I decided to unroot and update to December patch and stay stock. It now shows uncertified. Unlocked bootloader, maybe no way to certify without locking.
Related
Hello Forum People,
I have my bootloader unlocked, build MHA-L29C432B198, TWRP recovery and I use Magisk v14.5 however I cannot seem to pass SafetyNet with Magisk failing on ctsProfile and basicIntegrity and "SafetyNet Test" (from the Play Store) passing Safety Net Request but failing Response Signature Validation ("Response Payload Validation Failed").
I have a suspicion that this is due to the unlocked bootloader as I have removed Magisk and anything else I think might have tripped SafetyNet but always the same issue.
Can anyone confirm if this is the cause or otherwise and if having my bootloader unlocked is 'causing SafetyNet to fail then is it safe to relock after re-installing Magisk and returning recovery back to stock or is there some kind of work around?
Muchos appreciated in advance!!
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
ante0 said:
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
Click to expand...
Click to collapse
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
beejkitsune said:
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
Click to expand...
Click to collapse
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
beejkitsune said:
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
Click to expand...
Click to collapse
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
beejkitsune said:
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Surfinette said:
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Click to expand...
Click to collapse
Thanks for the reply. My solution ended up being to. Rebrand and then update to the Oreo release MHA-L29C432 8.0.0.361. Play Store now certified and passing SafetyNet with no issues. I'm still not 100% sure what tripped SafetyNet originally, nothing seems to be consistent with other people's experiences but I have now a resolution albeit not the desired approach, nor solution.
guys, here netflix is showing L3 widevine and with that it supports maximum SD. The device shows L1 in DRM INFO. someone else experiencing the same problem?
Im using last Android 10 January security patch. Bootloader Locked, No Root... ALL STOCK.
That's how it is. Netflix doesn't only require L1, but it also only let's the devices they whitelist to stream HD. Your device is L1 and netflix app is lying about it.
Everything works perfect in the Disney+ app. You'll get beautiful HD and it's clearly using the DRM.
hawkdown77 said:
guys, here netflix is showing L3 widevine and with that it supports maximum SD. The device shows L1 in DRM INFO. someone else experiencing the same problem?
Im using last Android 10 January security patch. Bootloader Locked, No Root... ALL STOCK.
Click to expand...
Click to collapse
So, good news. I recently installed the a11 update and netflix is now working in HD.
(I updated with the "Rescue and Smart Assistant" tool from lenovo for motorola phones, it offered the 11 update as a rescue image. It wipes the phone but atleast i got it in europe before the schedule)
- it was strange thought that play store didn't want to install netflix or disney+, i had to sideload them from apkmirror.
I have a (non-essential) app that I can not make to work on my new phone with the following error message:
Integrity check failed
Modifications on your phone have been detected. The app can not be used due to security reasons.
Details: The device is checked for signs of root access, respectively if the bootloader is unlocked. For these checks only local elements are used, no data is submitted to external services.
Click to expand...
Click to collapse
This is on a POCO X3 NFC with unlocked bootloader, custom ROM (ArrowOS 11) with microG (instead of Google Play Services) and stable Magisk (v22.0) with MagiskHide applied to that app. I have also already tried to freeze Magisk with AirFrozen, which is a trick that works on a problematic banking app, but that did not change anything.
The strange thing is, that the same app (and same app version) does not show that error on a OnePlus 6 with unlocked bootloader, custom ROM (LineageOS 16 for microG) and Magisk with MagiskHide applied to that app.
I have no idea what the difference may be any and how this is possible.
Any ideas?
https://github.com/kdrag0n/safetynet-fix check and download from release section if you want
etahamad said:
https://github.com/kdrag0n/safetynet-fix check and download from release section if you want
Click to expand...
Click to collapse
If you are replying to me, it's definitely not a SafetyNet issue, because my devices haven't passed SafetyNet since it stopped working with microG about a year (?) ago.
A strange thing happened to me:
I received an automatic update yesterday. Everything went normally, everything worked normally.
Later in the store I saw that Google Pay does not allow payment because firmware is Root (it is not) or illegal firmware is installed. And Google Play has shown that the device is not certified.
I tried resetting to factory settings ... without success.
It wasn’t until I installed the older August firmware via Odin that the phone became “legal” again.
This is the firmware INS 20211030.
Has anyone else had such problems?
Edit: it was October Update
darko150 said:
A strange thing happened to me:
I received an automatic update yesterday. Everything went normally, everything worked normally.
Later in the store I saw that Google Pay does not allow payment because firmware is Root (it is not) or illegal firmware is installed. And Google Play has shown that the device is not certified.
I tried resetting to factory settings ... without success.
It wasn’t until I installed the older August firmware via Odin that the phone became “legal” again.
This is the firmware INS 20211030.
Has anyone else had such problems?
Click to expand...
Click to collapse
As you said this is strange, I did not receive any updates in November. All I got was the October 2021 security patch update.
Do not update to F721BXXU1AVIF fw
Google Pay stops working. "Your phone isn't certified or doesn't meet security requirements"
Waiting for new firmware.
I have US unlocked U1 version, directly purchased from Samsung web site. I update VZW-F721U1UEU1AVIA by Odin. I have no issue after upgrade.
Not sure what is the different between F721BXXU1AVIF, probably vendor specific.
BTW, I am using US Mobile which is VZW MVNO.
VIF is in F721B International model, at the moment only for INS CSC.
VIA on your model F721U1 - US Unlocked model.
I don't think it has nothing to do with the new firmware update. It has to do with Google Pay last update. I had this problem two weeks ago, but was fixed quickly in a later update See if there is an update to your Google Wallet app.
Are you rooted? New firmware can mess with magisk/zygisk modules that hide root. Phone not certified usually means you aren't passing safety net