Database Develop

[Solved] Device not certified (G Play store)

...

cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
Upgrade to the latest version or install persona's b632 if you have kirin 620

..

cmmx said:
I already have the latest, b632.
I can't see how a custom rom could succeed where the stock one fails, though. Still I rather keep the phone stock ftm, at least until I get to decide what changes are applied and how.
Just reset and updated the app and no change. Phone isn't rooted.
Click to expand...
Click to collapse
I still get this problem some times if i switch from custom rom to stock, and i just reinstall rom again with a clean install and all is good, device get certified by google
Enviado desde mi hi6210sft mediante Tapatalk

...

cmmx said:
Never noticed this, so don't know if it's recent or not, but in the play store app's settings, it says my device is not certified. Haven't noticed any issues due to it yet, though.
Any input?
Click to expand...
Click to collapse
If You have root! Best Way to bypass It root Your phone with Magisk root

...

cmmx said:
I don't have root, and can't see why that would affect it, because what it says is the certification is for the device's hw (not sw), so it shouldn't matter if it's rooted or a custom rom or whatever (and I'm on stock Emui, anyway).
And it has nothing to do with Safety net either, because Magisk Manager (now) says it passes both cts and basic integrity (a week ago, the same version (other install) only passed basic integrity, and a couple months ago (other version) it didn't pass either one, with someone on Magisk thread even telling me that's because Magisk itself wasn't installed - guess what: it still isn't, yet it now passes both...).
Either way, I haven't noticed any problems from it, so far, so I'm just puzzled.
Click to expand...
Click to collapse
Bugged Google Play,just wipe data for gplay app.

...

Google Pay

I need advice with GPay to be working after Bootloader unlock.
I have new MI9, like long user of Mi series (last Mi Note2) I unlocked Bootloader, uploaded TWRP (the only one that worked was TWRP 3.3.0-0423 for Mi9 by wzsx150 - big fight with TWRP ...) and uploaded MIUI xiaomi.eu_multi_MI9_9.5.1_v10-9.zip.
Everything works fine for me, only Google Pay is a problem. Anytime I try to add an card in app, I got message that phone is either rooted or modified and cant proceed due to safety reasons.
I checked all forums and nothing works or I do something wrong. I tried this:
1) delete in DATA / DATA / com.google.android.gms - the folder will appear again after successful deletion
2) Magisk manager install - App is working correctly, GPay has been added to Magisk Hide and all Google Play Services folders, but still GPay not working
3) follow guide on https://forum.xda-developers.com/Mi-9/how-to/xiaomi-mi-9-firmware-twrp-recovery-root-t3922158 and install PrebuiltGmsCore.apk and then Google pay Patchfix. I stopped , because PrebuiltGmsCore.apk cant be installed
I do test with SafetyNet Test and it does not detect any problems.
I tried several times to delete Google Pay data as described on some forum. This does not help also.
Does anyone know how to get out of it? I don't want to go back to stock ROM and lock the bootloader ...
Thanks for any advice

Did you 'clear data' for all the Google Play/Pay/Framework services apps after you installed and configured the Magisk GPay module & MagiskHide settings and rebooted ?

Yes, I try many combinations. Like install GPay and Magisk then, reverse, delete data of GPay and install Magisk etc..
Odesláno z mého Mi Note 2 pomocí Tapatalk

I have the same problem. Please someone help!

Install Magisk and add Google Pay and/or Google Services in Magisk Hide list??

All done
Odesláno z mého Mi Note 2 pomocí Tapatalk

Hi
Any update for this issue ?

I've also tried to solve this problem in every conceivable way, failing miserably at it. It seems that you may or may not get GPay to work after deleting the gms folder, but the problem always reoccur after a while. It seems impossible to get GPay to work permanently with an unlocked bootloader on the Mi 9. Sad but true.

MrDeacon said:
I've also tried to solve this problem in every conceivable way, failing miserably at it. It seems that you may or may not get GPay to work after deleting the gms folder, but the problem always reoccur after a while. It seems impossible to get GPay to work permanently with an unlocked bootloader on the Mi 9. Sad but true.
Click to expand...
Click to collapse
I set up google pay on my girlfriends phone 2 weeks ago and it's still working fine. You must be doing something very wrong.

i opened my bootloader and cant get google pay to work. I am using the PFAEUXM stock rom

Just for the fun of it, I took the steps that Xiaomi demands in order to await bootloader unlock. There is no lack of warnings to make you understand that there may be a risk that sensible things like GPay will stop working.
I didn’t unlock.

found a way to completly disable apps like breeno

so i was just searching in xda and i found a thread for realme x2 pro that makes all the Chinese app go away for good and make coloros CN version tolerable.
I TRIED IT AND IT WORKS ON REALME X2.
and below is the link to that thread which is made by kkarnaout and im personalty thankful.
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-removal-china-related-apps-making-t4010019

Is the fingerprint scanner still working after the process?

Can you remove com.oppo.market and com.nearme.themestore ?

nothing happen to fp. everything works just fine.
well i couldnt remove the market and didn't try it with theme store.

Hi
Hi. Does it work on realme UI or only colors version?

This seems interesting. Please confirm whether this works on realme UI.

maxs8007 said:
This seems interesting. Please confirm whether this works on realme UI.
Click to expand...
Click to collapse
Yes it works on m X2 CN

You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.

maxs8007 said:
You can use debloater magisk module and remove all the Chinese apps including theme store, market, phone manager etc. Everything works fine without any issue.
Click to expand...
Click to collapse
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.

nickyip123 said:
If it's stock rom + magisk module, will the safetynet check break?
It's returned to stock rom now.
I plan to unlock again and flash the recovery, then delete the .apk files in recovery. Finally relock again.
I think the safetynet check would be okay after this. Hope I'm correct.
Click to expand...
Click to collapse
Please avoid unlocking relocking bootloader multiple times. It may get hardbricked anytime.
Stock rom with magisk modules will not break the safetynet unless you flash xposed.
Just make sure you hide the magisk manager from settings and hide all banking apps or all those apps that detect root and you'll be good to go.
I'm on stock with magisk +modules and debloated all Chinese apps.

com.coloros.assistantscreen - breeno feed
com.heytap.speechassist - breeno voice , long power click
com.heytap.quicksearchbox - global search cant be change to english[?]
any fix to this problem ?
130|RMX1991CN:/ $ pm uninstall --user 0 com.heytap.market
Failure [DELETE_FAILED_INTERNAL_ERROR]

How to root OSS and still pass safetynet checks (2022)

So I just bought a OnePlus 7T Pro McClaren Edition and its great
But I would really like to have it rooted.
I currently finally have stock rom installed again (after many frustrating hours) and am now passing the safetynet check.
I can:
1. Install Magisk (as an apk),
2. Patch boot.img
3. Unlock oem
4. Flash the patched img file
This works and I can have root access.
So far, unless I flash the original boot.img and wipe data again, I cannot lock OEM again (without seeing the corrupted data message).
Also, without locking oem, I'd keep getting the boot warning about bootloader being unlocked (which I guess is not so bad).
Seems like unless I have stock rom flashed, the safetynet check CTS test fails.
Anyways, I'm trying to find a way to root OOS and still pass the safetynet checks.
Thanks.

You need to enable Zygisk in Magisk, configure DenyList (walletfcrel, walletnfrćrelrimes_lifeboat and gapps and gservices), clear all data from Play Store, Play Services and GPay and reboot

Hi, Gpay updated to Google Wallet this method no longer works.

slapman said:
Hi, Gpay updated to Google Wallet this method no longer works.
Click to expand...
Click to collapse
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services

DartGerion said:
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services
Click to expand...
Click to collapse
At the time it didn't, and I had to find the the updated safetnet fix especially after updating to Android 12 and I custom ROM crDroid 13.

What Android version /oos version are you using ?

Question Mi 11 Ultra reboots to recovery mode several time before rebooting to Miui

Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot

Backup your data, then do a factory reset.

Thanks, I've tried that multiple times actually. Unfortunately it doesn't fix it

Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?

hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
I have this exact same issue.....
I dont know why this happend and how to fix this annoying issue!!
Which ROM do you have installed?

Oceanone said:
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
Click to expand...
Click to collapse
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.

Same issue, same topic:
Phone-Root boots into the Miui recovery with root (NON-TWRP)
Hi, Im testing my phone without, NON-TWRP. After root, and shutdown/restart the phone, the phone boots automaticly to Miui recovery instead of starting the phone normally... After 10 min, the phone starts in the normall mode with root. How to...
forum.xda-developers.com

aygul12345 said:
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Click to expand...
Click to collapse
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.

I'm smashing my head around....
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
I'm smashing my head around this... Exact same issue....
Flashing the latest EEA from, and installing 2 modules to hide that I'm being unlocked the boat loader, from that point if I restart than occurs the recovery boot loop.
Same moment not 30 days later.

Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).

hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com

aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.

aygul12345 said:
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
Click to expand...
Click to collapse
I didn't text that, because I need to use both Android Auto and Google Pay. To use AA, I have to unlock bootloader. To use google pay, I have to install a module to hide root.

Oceanone said:
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
Click to expand...
Click to collapse
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?

aygul12345 said:
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
Click to expand...
Click to collapse
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.

Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.

aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs

Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for the confirmation!!

aygul12345 said:
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
Click to expand...
Click to collapse
I saw your post on Github. Thanks for the effort! https://github.com/kdrag0n/safetynet-fix/issues/216

hympe said:
Thanks for the confirmation!!
Click to expand...
Click to collapse
hympe said:
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Click to expand...
Click to collapse
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
The cause of this issue is being logged on to the author github:
Xiaomi Mi 11 Pro - Installing this module boots into the recovery continuously · Issue #216 · kdrag0n/safetynet-fix
Describe the bug A clear and concise description of what the bug is. After having Root enabled by TWRP OR Flashing Magisk_modified_boot.img, there is no problem with Root on this device. But after ...
github.com
@Oceanone
@hympe Don't need to update, if it happens below then it also is happening on the latest version.
But @hympe can you confirm when you disable the Safetynet fix module, the phone reacts normally and boots normally?