Database Develop

Restore original Android ID?

I'm currently on Cog 2.2 B7 and have been having some wifi issues. A little reading has me thinking maybe it's the Android ID. I'd like to find out what the original is or how the whole ID thing works in general.
I understand when I bought my phone it had an ID set. Is this actually tied to the phone? As in, if I revert to stock firmware will I have the original ID back? Is there any way to generate that ID without flashing back to stock?
I know how to change it just not sure how to find the original.
Thanks!
EDIT: It appears this is being answered in another thread.
http://forum.xda-developers.com/showthread.php?t=810967

If you flash to stock, the original ID will be back. So far there isn't a way to generate the original with any other rom other than stock.

Someone also told me that if you had an older Nandroid backup file of your 2.1 setup, you could use Notepad++ to view the datadata.img file and find it there buy doing a search for "android_id".
I flashed back to stock and then wrote it down to change via Terminal Emulator. However I also learned that once you make a TiBu of a 2.2 setup, if you had changed your ID number to be the correct one, it will restore it back, so you don't have to keep changing it.

android id has absolutely nothing to do with wifi.
That said, it well be good knowledge for you to know how to do it. Unfortunately, flashing back to a stock rom is the only way to get it, unless you have a nandroid back up from when you were running stock. Somewhere posted in mass of the cog thread someone posted a method for extracting you id right from the back up. If I find that post again I'll post a link to it here.

I was having issues with wifi as well after flashing to cog 2.2 beta 7.
The fix that worked for me was giving my captivate a static IP.
Go into advanced settings in wifi and enter these for static IP.
IP: 192.168.2.4
Gateway: 192.168.2.1
subnet mask: 255.255.255.0
dns 1: 192.168.2.1
dns 2: blank
before doing this I couldn't connect to my home wifi at all. Now it connects just fine.

Demented71 said:
Someone also told me that if you had an older Nandroid backup file of your 2.1 setup, you could use Notepad++ to view the datadata.img file and find it there buy doing a search for "android_id".
Click to expand...
Click to collapse
This worked for me, Hope it is the right ID.

What exactly its the android id used for and is it important that I make sure it's unique on my phone?
Sent from my SAMSUNG-SGH-I897 using XDA App

Demented71 said:
Someone also told me that if you had an older Nandroid backup file of your 2.1 setup, you could use Notepad++ to view the datadata.img file and find it there buy doing a search for "android_id".
Click to expand...
Click to collapse
I had a backup from cwm, so tried this method. However, there are many different values, not sure which ones correct. some are all capital alphabets, some just numbers. Anyone know how to read it correctly?

Try using unyaffs to get it off your old datadata.img:
I outline how here.

[Q] Provision Device without re-flashing

Hi All
Is there currently a way from within android, to change the MDN (My Number)
and the MSID/MIN (Identification number)?
Im about to get my vogue reconnected, and will be having a different number transferred onto it.
Is there a way to change these details without having to re-flash to windows mobile??

ProfessionalGEEK said:
Hi All
Is there currently a way from within android, to change the MDN (My Number)
and the MSID/MIN (Identification number)?
Im about to get my vogue reconnected, and will be having a different number transferred onto it.
Is there a way to change these details without having to re-flash to windows mobile??
Click to expand...
Click to collapse
nothing that i know of to do it, none of the AOSP based builds have the ## codes built into them to allow you to change your mdn or MSID from android so yes you have to flash back

On Windows mobile, the ## codes actually run an executable that modifies all
that info on the phone. It's usually called EPST.EXE I think.
It probably could be done, but someone would probably have to de-compile
it, and then re-code it to run in linux/android.
Not sure if anyone can do that, but that's what would be required.

CDMA Workshop can do this, and I think QPST can also

[Q] Android ID

Hi everyone, I searched a lot on this forum and others and I couldn't find an answer to my problem (or even if my problem is a big deal). I flashed Assonance with the include kernel, my first ROM flash =-) and I did a lot of research before I did it and decided to backup my Android ID...which I did, BUT I only wrote down the number and now when I enter it into "Android ID Changer v1.5" I click "Change ID" and it automatically reboots but does NOT change my ID...yes I have busy box and super user access. Can anybody help me? Is this even a big deal?

on the root of your SD card, create a file name udpate.id (yes, udpate, it's a typo, but that's what the startup script reads) and put only your android id in it. then restart your phone and check if the idea has changed. also it's not that big of a deal, but the problem with these custom roms is that everyone on the same rom ends up with the same android id (i think?) which causes us to queue up for downloads on the market instead of downloading instantly.

slifer315 said:
on the root of your SD card, create a file name udpate.id (yes, udpate, it's a typo, but that's what the startup script reads) and put only your android id in it. then restart your phone and check if the idea has changed. also it's not that big of a deal, but the problem with these custom roms is that everyone on the same rom ends up with the same android id (i think?) which causes us to queue up for downloads on the market instead of downloading instantly.
Click to expand...
Click to collapse
Thanks! Just a regular .txt file? Like make one from notepad?

Endoran said:
Thanks! Just a regular .txt file? Like make one from notepad?
Click to expand...
Click to collapse
Yes, but save it as a .id or save the .txt and rename the extension to .id.

[Q] Things to do/save BEFORE flashing ROM

...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.

efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?

mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.

Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a

I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?

tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy

I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.

Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin

No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.

Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!

OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.

So... let's say that you didn't save your android id before you flashed... will that cause problems?

beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.

Oreo SSAID/Device ID issues

Hi all
I play a game on several Android devices that incorporates the Device ID in the save files. The game devs will port save files for you when you change devices but this takes several days, so normally I root and use Device ID Changer app to keep all my devices on the same id.
Now that I'm using Oreo, I understand that it handles the Device ID in a very different way so that each app instance has a unique id associated with it. Is there any way to find out what this id is for a particular app and then to change it. I have root, and terminal and am not bad on the command line, if a little rusty.
Sláinte
mmidders
==
Xiaomi MIX running Resurrection Remix OS 6 (Oreo 8.1)

I found the solution to the problem in the following post:
https://forum.xda-developers.com/android/general/tool-device-id-changer-oreo-t3768277
Oreo stores deviceids in /data/system/users/0/settings_ssaid.xml so you can either use the tool from the above post to change them, or I presume that you can use a root text editor to modify the file directly. Changes won't come into effect until after a reboot.

I found the solution to the problem in the following post:
https://forum.xda-developers.com/android/general/tool-device-id-changer-oreo-t3768277
Oreo stores deviceids in /data/system/users/0/settings_ssaid.xml so you can either use the tool from the above post to change them, or I presume that you can use a root text editor to modify the file directly. Changes won't come into effect until after a reboot.