I'm referring to those #74*67885*1# type codes that show system parameters and perform special functions.
Where would I find them, and what are they called?
http://forum.xda-developers.com/showthread.php?t=905194
Thank you!
Edit: This thread was originally started as a help thread, but I'm pretty sure it's a real bug now, so I've entirely edited the content of my first post to summarize the problem (for clarity).
After flashing 4.4.2 with MOP and rebooting into download mode to flash the bootloader with desktop Odin, some users were reporting Samsung keyboard force closes.
If you reflash the firmware with MOP and reboot normally, your keyboard will work, but handwriting recognition will not, and if you call *#1234# you will not have a CSC number.
If you reflash and reboot into recovery, your keyboard and handwriting recognition will work, and you WILL have a CSC number. However, if you were to check your call logs or messages, you will see contact numbers, but not names, even though the contacts are on your phone.
Let me illustrate with a fictitious contact: John Doe, 12345678. You will see a message from 12345678, not John Doe, even though you have a contact named John Doe with the number 12345678 in your contacts.
This problem has been verified by one user already: http://forum.xda-developers.com/showpost.php?p=51155409&postcount=722
Fix found: Remove Google account, reboot, and re-add Google account.
In my settings, i have multiple multiselectlist preference items where the user can choose different courses. So now i changed the array that is associated with the preference item but i saw, while manually viewing the shared prefs xml file, that the old selected value, which doesn't exist in the entries-array of the updated version, is still saved in the particular string set inside shared prefs.
When i view my settings from inside my app, the multiselectlist item has now all entries unchecked, although there is still that old item saved as mentioned before. Even checking new entries doesn't help, it just adds them to the old value inside the string set xml-item.
This is fatal for my app's behaviour, how can i solve that without the user having to clear all his initially saved settings?
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
sm-a500fu, rooted, 4.4.4
My wife got a new sm-a500fu like our daugther has. To save work (after rooting) I restored the data and systems partitions (with Flashfire) of my daughters a5.
I deleted all my duaghters accounts and logged into google with my wifes account.
Still both phones have the same GSF and Androide ID.
I know that the Androide ID can be set like this:
Code:
adb shell ettings put secure android_id nnnn
- But which should I use ? Can I use the one of here old phone ?
- And what about the GSFid ?
Hoping for help now ...
What I found out so far:
android_id: *#*#8255#*#*
/data/data/com.android.providers.settings/databases/settings.db
its name in the database is android_id, value is HEX
gsf id: *#*#GCM#*#*
/data/data/com.google.android.gsf.gservices/databases/gservices.db
its name in the database is android_id too, value is decimal
Theese questions remain:
1 Is it necessary to change both or would GSFid be enough ?
2 If I change the IDs in the databases of the cloned phone to its original, what apps do I have to reinstall ?
3 Or is it cleaner to reinstall GSF and GAPPs ?
3a But would I get another ID this way ?
I realize this is an old thread which I found by searching for more information on changing the GSF-ID, where I'll just point people who may come here to a new method I found which changes the GSF_ID using basic Windows tools on a non-rooted Android phone without having to Factory Reset the darn thing (which is kind of nice indeed).
As you may noticed since last week google wants us, the custom rom users to manually register our android_id to the link https://www.google.com/android/uncertified/
It looks simple isn't it?
But there's a catch. Each google account can register up to 100 ids. So if you keep registering new ids after every clean install you'll more likely to hit that 100 ids limit soon. That's even worse for fhe rom developers as they may flash up to 20-30 roms a day.
I'm figuring out that in a different way though. The procedure I'm following is:
A. BEFORE ANYTHING
If you're doing this first time:
1) Copy this database from /data/data/com.google.android.gsf/databases/gservices.db
2.1) Open the database with a sql editor or from adb shell or a terminal emulator in sqlite3, see android_id with this sql command:
SELECT *
FROM main
WHERE name="android_id";
2.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "SELECT * FROM main WHERE name = \"android_id\";"'
3) Then save the value you're seeing to somewhere else, and register to your account at https://www.google.com/android/uncertified/
B. THEN FOR EVERY CLEAN INSTALL
1) Backups and wipes.
2) Flash rom (pt roms with vendors have the firmware included).
3) Flash gapps.
4) Optionally flash a custom kernel.
5) Reboot and configure your device.
6) Flash magisk, reboot.
THEN THIS PART IS IMPORTANT:
7.1) Again copy this database /data/data/com.google.android.gsf/databases/gservices.db and open in a sql editor (or with sqlite3 in terminal emulator, or adb shell) and execute this sql command:
UPDATE main
SET value=XXXXXXXXXXXXXXXXXXX
WHERE name="android_id";
7.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "UPDATE main SET value=XXXXXXXXXXXXXXXXXXX WHERE name = \"android_id\";"'
Note: XXXXXXXXXXXXXXXXXXX is your android_id as you've learned and registered to your account before (You can see the android_id s you've registered at the same google link).
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Deleted
Deleted
muff99 said:
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Click to expand...
Click to collapse
Yes that works too but this is the manual method for the gsf android_id. Wifi only devices doesn't have IMEI for example.
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
G4B33 said:
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
Click to expand...
Click to collapse
Yes so now we don't have to do that much of hacky-wacky stuff just to get gsf certified status anymore. #YayGoogle? ?
What if you don't do that?
seems not working. After rebooting, it went back to previous id
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
ccelik97 said:
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
Click to expand...
Click to collapse
I think the display will always stay on "not certified", but you are atill able to use the Google services (which unregistered custom ROM users are not any more, if I understood correctly).
This is just a guess on my side, I have not tested this (and I can't since I added all kinds of IDs to that registration page ...).
All in all the information flow from Google on this topic has been spectacularly bad, imho.
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
image45 said:
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
Click to expand...
Click to collapse
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
muff99 said:
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
Click to expand...
Click to collapse
Do I need to convert it or is that an accepted way to submit the information please?
If I try to resubmit it advises already registered.