OESF Portables Forum
Model Specific Forums => Gemini PDA => Gemini PDA - Android => Topic started by: Milan on March 19, 2018, 09:43:01 am
-
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
-
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
Mine (unflashed, unrooted, stock ROM) says uncertified.
Rosie
-
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
Did you try to fake device information with Magisk? I found Magisk module (https://github.com/AndroPlus-org/magisk-module-device-faker) for this, but not sure if it can trick Google Play.
-
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
Did you try to fake device information with Magisk? I found Magisk module (https://github.com/AndroPlus-org/magisk-module-device-faker) for this, but not sure if it can trick Google Play.
Yes I did. The result:
CTS Profile: False
Basic Integrity: True
That's why I asked for the Device Certification of the stock Gemini. You can't get CTS Profile: True in magisk if the stock device is Uncertified
I didn't try the module you linked
-
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
Mine is out-of-the-box standard and shows as Uncertified.
-
Mine also says uncertified, though I have disabled almost all of Goggle except Google Play Services and Goggle Play Store.
Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)
Mine is out-of-the-box standard and shows as Uncertified.
-
Google should not just certify the Gemini. Google should consider purchasing them in large bulk to use/sell for Google Fi. They need something completely different in their device lineup.
-
https://arstechnica.com/gadgets/2018/03/goo...rom-logging-in/ (https://arstechnica.com/gadgets/2018/03/google-starts-blocking-uncertified-android-devices-from-logging-in/)
Custom ROMs and possibly the Gemini-PDA Android will require a manual registration via http://g.co/androiddeviceregistration (http://g.co/androiddeviceregistration)
Can someone please confirm if this is already the case for the Gemini-PDA ?
-
https://arstechnica.com/gadgets/2018/03/goo...rom-logging-in/ (https://arstechnica.com/gadgets/2018/03/google-starts-blocking-uncertified-android-devices-from-logging-in/)
Custom ROMs and possibly the Gemini-PDA Android will require a manual registration via http://g.co/androiddeviceregistration (http://g.co/androiddeviceregistration)
Can someone please confirm if this is already the case for the Gemini-PDA ?
Also noted here: https://hardware.slashdot.org/story/18/03/2...from-logging-in (https://hardware.slashdot.org/story/18/03/26/2220259/google-starts-blocking-uncertified-android-devices-from-logging-in)
My Gemini says "Uncertified", and it's as stock as the day it came out the box.
I wonder if we can use that androiddeviceregistration link above, and still use Google services & apps?
Any Gemini users tried it yet?
-
The g.co link opens the Google Account sign in page, as you know.
Therein it asks for a device "Android ID".
What is the Gemini's Android ID number and/or where is it found?
Is it the same number on all Gemini's?
Ifanafi
https://arstechnica.com/gadgets/2018/03/goo...rom-logging-in/ (https://arstechnica.com/gadgets/2018/03/google-starts-blocking-uncertified-android-devices-from-logging-in/)
Custom ROMs and possibly the Gemini-PDA Android will require a manual registration via http://g.co/androiddeviceregistration (http://g.co/androiddeviceregistration)
Can someone please confirm if this is already the case for the Gemini-PDA ?
Also noted here: https://hardware.slashdot.org/story/18/03/2...from-logging-in (https://hardware.slashdot.org/story/18/03/26/2220259/google-starts-blocking-uncertified-android-devices-from-logging-in)
My Gemini says "Uncertified", and it's as stock as the day it came out the box.
I wonder if we can use that androiddeviceregistration link above, and still use Google services & apps?
Any Gemini users tried it yet?
-
https://www.xda-developers.com/google-block...-rom-whitelist/ (https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/)
According to this update on XDA, manual registration for custom ROMs actually requires "Google Service Framework" No. not Device ID (Android ID). Your GSF number can be found easily using the Android app "Device ID" or similar.
-
The uncertified status of Gemini is troubling.
As mentioned by AndyM, I searched Play Store for "Android app Device ID" and installed one of several such 4+STARS rated apps listed.
Specifically, I installed "Device ID Manager" on my Samsung phone.
It shows the following device info on one page:
1) Android Device ID
2) Device Name And Model
3) Google Service Framework ID(GSF)
4) IMEI
5) Android Version and API Level
6) Phone Number
7) Google Account
8) WIFI MAC Adress
9) Bluetooth MAC Address and Name.
Somehow such an app should be installed on a Gemini by someone in OZ, who knows how to get around Google PS, and who might then report their device's info back here, if knowing that helps resolve this uncertified concern.
Ifanafi
-----------------
https://www.xda-developers.com/google-block...-rom-whitelist/ (https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/)
According to this update on XDA, manual registration for custom ROMs actually requires "Google Service Framework" No. not Device ID (Android ID). Your GSF number can be found easily using the Android app "Device ID" or similar.
-
Just I installed a (Google-/Android-Logo) App "Device ID Manager" from Area1:
It says: Device ID: 0123456789ABCDEF
And a second one: Device "Id Manager" from Raw Apps:
It says: Device ID: 0123456789ABCDEF
And a third App: "Device ID" from Evoci:
Android Device ID: 7575672C81Exxxxx. Help: A 64bit number (as a hex string) that is randomly generated on the device's first boot and should remain constant for the lifetime of the device, (The value may change if a factory reset is performed on the device)
Google Service Framework (GSF): 35A8E090AC3xxxxx Help: as before!
IMEI: 3517690900xxxxx
SIM Subsciber ID: 2620130102xxxxx
SIM Card Serial: 894902000008875xxxxx
WI-FI MAC Address: 02:00:00:00:00:00 wrong
Bluetooth MAC Address: 02:00:00:00:00:00 wrong
Devive Build Fingerprints: Planet/Gemini/Planet:7.1.1/NMF260/15173xxxxx:user/dev-keys,release-keys. Help: Brand/Product/Device/Board/Version.Incremental:Type/Tags
I do not think the 0123456789ABCDE is a real existing Android Device Number but a pseudo one
With xxxxx I changed 5 figures in my numbers at their end
-
...
I do not think the 0123456789ABCDE is a real existing Android Device Number but a pseudo one
With xxxxx I changed 5 figures in my numbers at their end
however, this 0123456789ABCDE serial is not only in Gemini: I've a "Nordvision" tablet that has the same serial number...
Salvo
-
...
I do not think the 0123456789ABCDE is a real existing Android Device Number but a pseudo one
With xxxxx I changed 5 figures in my numbers at their end
however, this 0123456789ABCDE serial is not only in Gemini: I've a "Nordvision" tablet that has the same serial number...
Salvo
What a coincidence! You should offer them as a set on ebay for a million dollars!<g>
-
Tried the Device ID app by "evozi".
Seems like the author of that app also distributes the app outside the Google Play Store: https://www.evozi.com/l.php?go=deviceid_no_network (https://www.evozi.com/l.php?go=deviceid_no_network)
Both my Android Device ID and Google Services Framework ID came back looking different to ones wovoja listed.
Sooo - I guess that is good. We can probably can use that GSF ID to register on that Google page...
I don't think I'll try and do that ID registration now. Everything still seems to be working.
Will hang onto those IDs - just in case I get locked out of Google services, and then try to see if it works...
If anyone else does go ahead with the ID registration - please report back here what is involved with the registration (besides entering the ID), and if it works.
Thanks
-
Looks like it might be the IMEI number that is required instead of the GSF number?
https://www.ghacks.net/2018/03/27/google-lo...om-google-apps/ (https://www.ghacks.net/2018/03/27/google-locks-out-users-on-uncertified-android-devices-from-google-apps/)
One of the comments notes - what do you do on a non-phone device like a TV box? That won't have an IMEI number...
-
I can confirm it is the Google Services Framework ID you need to enter.
Before you can do so, you have to convert it from hex to decimal as the registration page only takes decimal values.
Entering your IMEI (as I tried, before converting GSF) will not register your device.
Gemini works without registration. It was only after flashing LineageOS that I needed to register my device using GSF-ID.
After registering my GSF-ID, it took about 15 minutes before I could use GApps.
EDIT: here's a guide (https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/), halfway down the article, on how to do this incl. links to apps and hex-decimal convertion.
-
I never logged in to google, so my device id is still 01234.... as is my serial number. I still have access to the play store through yalp. I don't use google services, so it doesn't have any real effect. If all you want is access to the play store, install the fdroid store (google fdroid - oh the irony), then use fdroid to install yalp.
-
Vader, that 01234... is NOT your device ID, that's your serial number. Every device is given a Google Framework Services ID upon factory reset (or first boot), which is different from your serial.
You'll find that if you use the Device ID app in the link, that your GSF-ID is different from your serial. Your serial number can NOT change upon using (or not using) Google Apps..
-
Vader, that 01234... is NOT your device ID, that's your serial number. Every device is given a Google Framework Services ID upon factory reset (or first boot), which is different from your serial.
You'll find that if you use the Device ID app in the link, that your GSF-ID is different from your serial. Your serial number can NOT change upon using (or not using) Google Apps..
Yep, you are right. I only checked the first device id manager app (with the highest score mind you) which seems to give the incorrect number. I worked my way down the list and eventually got on which showed a proper gsf id. it did, however, get the mac addresses wrong - 02:00:00:00... I checked the iemi it reported and that was correct. I am surprised that you dont get the same values from different apps. The one that reported the 012345... for both had the mac addresses correct as well as the iemi. Go figure....