Database Develop

Device ID

In a couple of threads I've seen references to changing or restoring your "device ID". Did a search and couldn't find anything. What is this and how do you do it?

gluvox said:
In a couple of threads I've seen references to changing or restoring your "device ID". Did a search and couldn't find anything. What is this and how do you do it?
Click to expand...
Click to collapse
Basically it's a problem with froyo ROMs. Our phones have unique device ID. Froyo ROMs have the same device id for each device which causes market issues (i.e. downloading apps but it not being able to install often). That's why people want to change their device ID's so that their market problems are gone.
Some of the ROMs (like Cognition, perception, etc.) have random android id generator so that market issues are fixed. Alternatively, you can flash back to stock, use "Android ID changer" from market to find your device ID, flash to one of the froyo ROMs, then use the same app to change your ID.

had same problem. Unless its preventing you from installling market apps its not a big deal and nothing to worry about. If you absolutely want to modify it while on custom rom then the id changer should work. But in all most all instances ODIN one-clicks back to JF6 will restore your device id.
Want you to look at something first as you could have 2 problems. Most froyo roms will change your device id to a generic 004...#. Generally when you flash back to stock it will restore your original IMEI.
It wasn't until i had used an i9000 rom that i had the following problem. Not only was my IMEI changed....it changed my product code to a T-mobile code. What should have been SGH-I897kzaatt was showing as SGH-I897kzatmb. Even flashing stock was not restoring either IMEI or product code. Ended up having to edit binary file in efs folder but it gave me headaches. (can walk you through but want you to make sure your product code is ok first.
To check your product code the easister method is SHS Toolbox (not SGS Tools) from market.
You will need (Root Permission):
1. Install Busybox from Market
2. Install SGS Toolbox from Market.
3. Make sure you also download TERMINAL EMULATOR from market as you may need it to restore your voice and 3G connections later in process. There are 2 versions make sure you get the one with more stars.
Once you have done 1-3 run SGS Tools and select the CHECK PRODUCT CODE. Report the results back here.

I need to change my product code back... can you help?

When I had 2.1, I was able to connect to my College's exchange account, but now that I flashed 2.2 on my phone, I can't get on my email. When I go to my email via laptop, and look under my mobile settings it shows 2 Androids listed, obviously 1 is when I had 2.1 and the other my 2.2.
My problem is that on the 2.2 one, exchange says:
Device ID: Validate
whereas for my 2.1 one, exchange says:
Device ID: droid(and then a bunch of numbers)
How do I "Validate" my device ID?
Is my device ID and my Android ID one in the same?
I dl'd the Android ID Changer, and the ID it shows is completely different from what I had before, can I change it back to what it showed for 2.1 in my exchange account?

WandererTJ said:
When I had 2.1, I was able to connect to my College's exchange account, but now that I flashed 2.2 on my phone, I can't get on my email. When I go to my email via laptop, and look under my mobile settings it shows 2 Androids listed, obviously 1 is when I had 2.1 and the other my 2.2.
My problem is that on the 2.2 one, exchange says:
Device ID: Validate
whereas for my 2.1 one, exchange says:
Device ID: droid(and then a bunch of numbers)
How do I "Validate" my device ID?
Is my device ID and my Android ID one in the same?
I dl'd the Android ID Changer, and the ID it shows is completely different from what I had before, can I change it back to what it showed for 2.1 in my exchange account?
Click to expand...
Click to collapse
Yes you can change it back, just type in the original id and hit save.
Although if you are having issues with it being recognized on your schools email, the tech support staff at your school most likely could fix the validate issue for you a heck of a lot faster than we could since we have no control over it.

DarrellRaines said:
Yes you can change it back, just type in the original id and hit save.
Although if you are having issues with it being recognized on your schools email, the tech support staff at your school most likely could fix the validate issue for you a heck of a lot faster than we could since we have no control over it.
Click to expand...
Click to collapse
Device ID does not = Android ID
Device ID = IMEI
and should match the imei on the label under your battery

once you check your product code you are likely to see it is incorrect.
The link i am going to provide repairs the nv_data files with correct product code for your device (which in my case allowed the IMEI to be restored to original).
Your product code should be SGH-KZAATT (but is likely SGH-KZATOR or SGH-KZATMB).
Flash to stock JF6 2.1 eclair and try what worked for me if you find your product code to be incorrect.
http://forum.xda-developers.com/showthread.php?t=881162

bames said:
Device ID does not = Android ID
Device ID = IMEI
and should match the imei on the label under your battery
Click to expand...
Click to collapse
Eh middle of the night, no sleep and jacked up on cold medicine. Cut a guy some slack for not reading

DarrellRaines said:
Eh middle of the night, no sleep and jacked up on cold medicine. Cut a guy some slack for not reading
Click to expand...
Click to collapse
wasn't being critical toward you sorry.
was just trying to make sure he was clear on the different ID's
but looks like he may have already used android id changer and possibly tried to modify his Android ID to his Device ID which could be a problem especially if he didn't write down his original Android ID that is used for the market/google.

[Q] Bell I9000M: An Unlock Does Not Exist. Prove Me Wrong. [SOLVED!!!]

I have a newer I9000M on JH2 from November and I haven't yet found a way to unlock it that works. Every single strategy I've found on this forum is a dead end. While my handset from September unlocked easily, every newer version I've had cannot be unlocked.
I've upgraded to JK4, downgraded to JH2, tried JPO, gone back to JH2, but nothing works.
It is my belief that everyone with a newer Bell handset is also finding it impossible to unlock. So rather than have us all waste time trying to find a solution that doesn't exist. Let's just admit it:
It doesn't exist.
Right or wrong?
UPDATE:
There is a solution (thanks to the ingenious Happy Hunter) but its not easy and not for noobs: http://forum.xda-developers.com/show...postcount=1202. You can't unlock the I9000M to use on any provider, but you can "change" the lock from Bell to your provider.
It failed for me numerous times until I rebooted my computer and followed the directions literally step-by-step. If you deviate slightly from his method (i.e. use z4root instead of SuperOneClick, or type the wrong text), you will fail.
Still waiting for a universal unlock or automated solution, but am satisfied with this for the time being!

montrealguy said:
I have a newer I9000M on JH2 from November and I haven't yet found a way to unlock it that works. Every single strategy I've found on this forum is a dead end. While my handset from September unlocked easily, every newer version I've had cannot be unlocked.
I've upgraded to JK4, downgraded to JH2, tried JPO, gone back to JH2, but nothing works.
It is my belief that everyone with a newer Bell handset is also finding it impossible to unlock. So rather than have us all waste time trying to find a solution that doesn't exist. Let's just admit it:
It doesn't exist.
Right or wrong?
Click to expand...
Click to collapse
i got a new motherboard after it got back from repaired can back w firmware JK4, and there is no way you can unlock it, the only way to do it is use hex editor and edit the nv_data.bin file to locked to a network your sim card is on, thats the only solution right now.

Try this...
http://forum.cyanogenmod.com/topic/4999-howto-sim-unlock-your-vibrant-galaxy-s/

SGS unlock in market place. Worked for me Just use it, get your key, restart phone with another sim, enter it

windraker said:
SGS unlock in market place. Worked for me Just use it, get your key, restart phone with another sim, enter it
Click to expand...
Click to collapse
You must have an older Bell SGS. The app doesn't work for phones with a newer manufacturing date.

I noticed after I relocked mine that's I couldn't unlock it again. One of the threads noted you can use the unlock code to lock to a different network as needed.

UPDATE:
There is a solution (thanks to Happy Hunter) but its not easy and not for noobs: http://forum.xda-developers.com/showpost.php?p=9810558&postcount=1202. You can't unlock the I9000M to use on any provider, but you can "change" the lock from Bell to your provider.
It failed for me numerous times until I rebooted my computer and followed the directions literally step-by-step. If you deviate slightly from his method, you will fail.
Still waiting for a universal unlock, but am satisfied with this for the time being!

Yeah, I just got my phone back last night after being repaired - I tried to use the app (for some reason my Bell prepaid with $0 on it was able to access data for free), I got the unlock code, but it said something along the lines of "Network authentication error" when I tried to do it.
dawen said:
i got a new motherboard after it got back from repaired can back w firmware JK4, and there is no way you can unlock it, the only way to do it is use hex editor and edit the nv_data.bin file to locked to a network your sim card is on, thats the only solution right now.
Click to expand...
Click to collapse
Anymore info on this procedure?
Edit: You don't have to use a hex editor, but it seems re-locking your phone to another network is the only way.
http://forum.xda-developers.com/showthread.php?t=761045
I did the "no-sim" method and it worked enough that I'm back on rogers.

When to restore IMEI & Product Code...

Hi,
I just had a quick question regarding restoring IMEI & Product code. Im with Rogers and currently on Cog2.3b8. i have flashed a few roms already and so far my IMEI is fine and hasn't been changed. When i check the product code it shows up as I-896xxATT (Not really the code but just to give an idea.), so i know its the wrong product code for Rogers. My question is this, should i fix the product code while I'm currently on Cog? Everything is running fine and no issues. Also, if i fix the product code from my backup to the Rogers one will i have any issues??
I just basically want to know if its worth fixing the product code if everything is running fine, and what is the benefit?
Thanks.

theMaDHakkeR said:
Hi,
I just had a quick question regarding restoring IMEI & Product code. Im with Rogers and currently on Cog2.3b8. i have flashed a few roms already and so far my IMEI is fine and hasn't been changed. When i check the product code it shows up as I-896xxATT (Not really the code but just to give an idea.), so i know its the wrong product code for Rogers. My question is this, should i fix the product code while I'm currently on Cog? Everything is running fine and no issues. Also, if i fix the product code from my backup to the Rogers one will i have any issues??
I just basically want to know if its worth fixing the product code if everything is running fine, and what is the benefit?
Thanks.
Click to expand...
Click to collapse
As long as IMEI is fine, you don't need to fix the product code. Product code is just for your sake. As long as you know what product it is, it should be fine.. (until u sell your phone)

Thank you!
I guess ill leave it be for now. I finally got everything running great, no ATT logo on boot, No SMS timestamp problems, so i just wont mess around with it.
I guess if i ever flash to a stock Rogers rom, or go back to stock before flashing a rom for whatever reason, i can restore the correct product ID at that point.
Thanks again.

If you did want to change your PC and ensure you've got the original IMEI code, check here for instructions

[Q] cannot use *#7465625# after CM9 mod

I just upgrade my Captivate to CM9 ICS from GB. When I enter *#7465625# to check the lock status. Nothing happens. I remember it worked fine when I did this prior to the upgrade. Is it nornal? or did I break anything?
Thanks.

bigboy0723 said:
I just upgrade my Captivate to CM9 ICS from GB. When I enter *#7465625# to check the lock status. Nothing happens. I remember it worked fine when I did this prior to the upgrade. Is it nornal? or did I break anything?
Thanks.
Click to expand...
Click to collapse
You didn't break anything . Pretty much all the special codes I've ever used stops working on ICS and JB. That being said I'm guessing you're wanting to check your GPS lock status. Download GPS Test from the play store and that should show you everything you'll ever want to know about your lock status.

I might not be very clear in my question, Sorry.
I actually want to vertify if my phone is locked or unlocked after the upgrade; like using *#06# to review the IMEI.

bigboy0723 said:
I might not be very clear in my question, Sorry.
I actually want to vertify if my phone is locked or unlocked after the upgrade; like using *#06# to review the IMEI.
Click to expand...
Click to collapse
I wasn't able to find a good solution for this either (did an unlock a couple weeks ago). I had to just try it with a SIM card from a phone on another network.

Once unlocked ---- Always unlocked.
And the reason those USSD Codes won't work...basically from what lil I know...is because they are either Samsung ussd codes or Carrier Specific Codes and therefore you need to be on a Stock Firmware for them to work (like m1batt1 was pointing out). --- Although some may by chance work.

There is a flashable zip that will restore the *#*#2263#*#* code on the Cappy which let's you change modem frequencies but I don't think it restores that code. Browse through the Slim threads. I'm on my phone and cannot link the zip.
Sent from my SGH-I897 using xda premium

[Q] Samsung Captivate unlock issues

Hi,
I have a Samsung Captivate that I am trying to unlock. Its out of contract with AT&T and so I called them to get the unlock code. They provided the unlock code. I have a non-AT&T sim card from an overseas trip few years back. I insert this sim card and restart the phone and it asks me to enter the unlock code but am unable to unlock with this code - keep getting "unlock request unsuccessful".
I also got the unlock code for my wife's Captivate from AT&T. Using the same non-AT&T sim card in her phone, when I entered the unlock code provided, I was able to unlock her phone successfully.
Additional info if it helps:
1. My phone is running the official Gingerbread from Samsung whereas my wife's phone is running the original Eclair (with the one OTA update that was initially provided by AT&T).
2. I had rooted both phones when both were running Eclair. However, I lost root access on my phone when upgraded to Gingerbread whereas her phone still has root access. I have not rooted my phone since upgrading to Gingerbread.
3. When I had rooted both phones on Eclair, I had come across a method to inspect the efs/nv_data.bin file manually on this forum to get the unlock code:
Code:
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
The unlock codes retrieved with above method for both phones are the same as those provided by AT&T recently.
Question is why I am unable to unlock my phone whereas we didnt have any problems unlocking my wife's phone. Would upgrading to the official Gingerbread ROM (non-rooted) from Samsung have anything to do with it?
I had read somewhere that Samsung had encrypted something (bootloader?) with the Gingerbread update for the Captivate that prevented it from being rooted the same way that the Captivate could be rooted with Eclair. Could this be related to why I am unable to unlock my device?
Another thought is whether I would need a different unlock code that works with Gingerbread? I am thinking this is unlikely as my undertanding is that the unlock code is determined by the IMEI number and not the ROM?
Anyway, would appreciate any help/feedback on what I can do to unlock my phone.
Thanks,
-Topper
P.S. Since I tried multiple times to unlock the device unsuccessfully (by entering non-AT&T sim, trying with #7465625*638* code, etc), it shows that I only have one try left to try and unlock the phone.

There are many threads where they describe how to unlock Captivate using manual method i.e. hex editing nv_data.bin file in /efs folder of your phone.
You have to root your phone first if not done so already. Also back up your efs folder on your sdcard and/or your PC. This is a very important step. If you mess up your efs in future(for any reason like while flashing a rom or whatever), you can always restore this folder from your back up. Also back up another copy after you're successful with unlocking that way you can go back to original efs or the unlocked one.
You may use the instructions in this thread to unlock it even though it's for SGS III:
http://forum.xda-developers.com/showthread.php?t=1718665

uhm said:
There are many threads where they describe how to unlock Captivate using manual method i.e. hex editing nv_data.bin file in /efs folder of your phone.
You have to root your phone first if not done so already. Also back up your efs folder on your sdcard and/or your PC. This is a very important step. If you mess up your efs in future(for any reason like while flashing a rom or whatever), you can always restore this folder from your back up. Also back up another copy after you're successful with unlocking that way you can go back to original efs or the unlocked one.
You may use the instructions in this thread to unlock it even though it's for SGS III:
http://forum.xda-developers.com/showthread.php?t=1718665
Click to expand...
Click to collapse
Thanks! I had subscribed to the original thread here but had forgotten all about it. Rooted my phone (still gingerbread) per another thread, unlocked manually as per above thread & confirmed by putting T-Mobile Sim card that both phones work as expected. Glad to see the manual process above still works on sgs iii - so maybe it will work on the exhilarate too.