Actions
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 8.3K Forums
- 9.9K Products
- 100 Axon 10 Pro
- 15 Specifications
- 6 News & Reviews
- 6 How-To Tutorials
- 2 Shot On Axon 10 Pro
- 3 Axon 10 Pro Developers Thread
- 17 Blade 10
- 3 Blade 10 Specifications and Owners Manual
- 1 #ShotOnBlade10
- 6 Reviews & News
- 4.9K Axon (A1P & Axon 7/Mini)
- 270 Developer's Lounge
- 4 Blade A7 Prime
- 2 Blade A7 Prime Specifications and Owners Manual
- Blade A7 Prime News and Reviews
- 99 Blade MAX VIEW
- 1 Blade Max View Specifications & Owners Manual
- 10 Blade Max View Reviews
- 2 Shot On #BladeMaxView
- 1 Blade Max View How To Videos
- 622 Other Products
- 32 Visible R2
- 30 Blade MAX 2s
- 403 Blade Z MAX
- 159 Axon M
- 207 Quartz
- 7 Sync Up Drive
- 99 SPRO
- 135 Blade X MAX
- 107 MAX XL
- 222 Blade V8 PRO
- 816 ZMAX [Series]
- 102 Grand X [Series]
- 18 Sonata [Series]
- 17 Trek [Series]
- 24 Warp [Series]
- 32 Accessories
- 200 Rumor Mill
- 105 Mobile Education
- 4 Announcements
- 2K Labs
- 1.8K Beta Lab
- 161 Consumer Lab
- 326 Blog
- 6 Site Help
Featured User of the Month
Moderators
Device Certification - "Uncertified"
C_U_T_W
Pacific NorthwestPosts: 4 ✭✭✭
Hello all,
I was just wondering if anyone else has, or has had the same problem with their Axon 7 as i ?
When I click on the Google Play Store icon from my home screen and go into settings, I scroll all the way down to where it says 'Device Certification' and notice that the application is recognizing my phone as "Uncertified".
As I read Google's advice on what to do about the issue, I quickly realized that it seemed very essential in more ways than one that the device be certified.
I will add a few screenshots, any helpful advice would be much appreciated. Thank you.
0
Comments
When you go into your phone settings, go to the "About phone" section. What is the "Build number" in that section?
They should be, unless someone obtained a build file from elsewhere that they shouldn't have and installed it on their consumer device.
(would have replied sooner but didn't get any notif.)
Build # - A2017UV1.1.0B25
The phone doesn't have any custom roms, i have not attempted to root either, any changes would have come from MiFavor, under "system update" in Settings.
The problem is most likely related to an other more worse off type situation i have recently been trying to deal with, and with only a little knowledge about how things work i'm not exactly possitive on what to do. But an overview of my phone that i saved earlier today should answer any questions that were asked above, and also give a little insight as to what the current status is and what i'm looking at. To me it obviously doesn't look good.
No not a replacement. I bought it brand new from Zte\Amazon on 6/2/17
If possible, try a factory reset, and set the phone up as a new device. The certification is largely based on the ROM, and if anything causes any of the security mechanisms in the google play store or other services, it will become uncertified as a way of preventing the use of things like android pay.
If the issue still remains, you can try re-flashing the stock ROM.
The factory reset worked, I finally get my notifications straight and end up having issues with my email after the reset haha. Thanks guys.
Thats awesome news great to hear @C_U_T_W
I have this same issue with my Axon 7 Mini. I am running the official Nougat release. However, I also participated in the Beta program, so could this be an artifact of that?
That being said, I would have hoped that the 'official' build (B12) should have updated that attribute. I really don't want to have to "factory reset". FWIW, Android Pay works fine so I don't really know that this is affecting anything.
The device certification process can sometimes become undone if the google services finds any configuration or software that it does not like.
If you were previously running a number of beta builds, then you may have used a few builds which never had a focus on being certified. If you have had a number of beta builds, sometimes it is better to just factory reset, as ROM updates are not always 100% clean, especially if test builds are involved.
After a ROM update, clearing the app cache, as well as the cache partition is always good, but from an uncertified build, to a certified one, it is often best to do a factory reset.
Ok, thanks. I'll keep it in mind and do a reset when it is convenient sometime. I don't seem to be suffering any ill effects from it at the moment.
I've run into this before and clearing cache for Play Store fixed it on a Galaxy S3. Here's a good list of things to try without a factory reset.
https://www.androidpit.com/google-play-not-working
I got the September software patch this morning for my mini and it now says it is certified again.
We are happy to see that your issue has been resolved. Thanks for letting us know.
