yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] adz86:
yes but i saw that you need to install android sdk then windows drivers and many other things its not that easy. i managed to fix the problem just erasing both files. i dont know why but the bak files were old enough to restore my original product code.. :)
[Galaxy S I9000 Android Development] zerocool76:
didn't your product changed after you edited with notepad?? Mine did :(
[Galaxy S I9000 Android Development] mitoradeS:
Same here... :(
[Galaxy S I9000 Android Development] gmarvel:
same here..and i dont remember my product code ,i bought my phone from expansys in july,now i have xxxxxxxxx product code and 0049xxxxxx imei ,i asked the local service and they told me to change the motherboard (that means at least 400 euro)...They are crazy...
[Galaxy S I9000 Android Development] Candanga:
TY mate!

Fixed my fake IMEI with this. I didn't write anything to the file, as doing so may generate an error as before. I didn't have a backup of my original /efs folder, tried accessing the files from a nandroid backup, but that folder isn't backed-up. Fortunately I had a backup of my nv_data.bin, which I made before getting my IMEI screwed! (lucky me). Its a shame that my local samsung "repair" shop knows dck about this, had to find solutions for myself, and it feels 10k times better :cool:

@gmarvel - Mate, if you used KIES b4 getting your PCODE screwed, go to REGEDIT and look for:

HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB

Look withing the DB (folders), 1,2,3, etc.. whatever u have there, theres a key at the right side named "product code", there you go... U can also check some other info under the large string named "DEVCONINFO"

Hope that helps. Cheers!
[Galaxy S I9000 Android Development] bames:
This also works in terminal emulator.

Somone had posted earlier buy listed the second line without busybox at the front of it and it would work (error msg). I tried it with busybox in the line and it worked.

So if you don't have ADB you can execute those exact same commands via terminal emulator from market
[Galaxy S I9000 Android Development] bames:
STILL HAVING A problem when i try this method.

i can have the correct code for my pc in the bak (ATT - i think ATT in USA?)

but when i delete the bin and reboot when the bak is used it messes it up and takes out the whole sgh-i897 line and replace it with the word Active which is what will then show for PC in sgs tools. Anyone solve that?>
[Galaxy S I9000 Android Development] MAKFOTO:
A quick and easy method to restore the original product code is to tap in on your keyboard -

*#272*YOUR IMEI#

With this method your IMEI will not change.

A warning. Make a back-up before hand as this clears your settings and apps.
[Galaxy S I9000 Android Development] CyberT3:
Since i had backup i just deleted my nv_data.bin and nv_data.bin.md5 and rebooted and product code changed but mps_code.dat in "imei" folder still has INU instead of VIP which is for my carrier. Everything works fine but should i change that file, too. Can i just rewrite that file with my original mps_code.dat that i have on my pc?

EDIT: I just copied my backup of mps_code.dat and rebooted and everything works normally but the main reason i was changing my PC back to the original was to fix android market which is not showing all apps available (e.g. google maps, google voice search, ...) and it still doesn't work. :(
[Galaxy S I9000 Android Development] PIRATA!:
I have a brand new Galaxy S and I am about to install last JMU Froyo 2.2.1 firmware.

I would like to set back my original product code, so you tell m that this is the correct and most easy solution, right?

After this, should I need to change also the CSC to the same code??

Thank you.
[Galaxy S I9000 Android Development] ru5t:
Hello, I have a branded italian TIM galaxy S. Original product code was GT-I9000HKDTIM. My actual product code is GT-I9000HKDITV (Froyo 2.2) I tried to restore the original product code using *#272*MYIMEI# but it shows ITV code only and I cannot select the branded product code.

any help appreciated

thank you
[Galaxy S I9000 Android Development] someperson:
Thanks for sharing.

I would like to share my experience with you.

I had the official middle east froyo (JPG) through kies with the registry hack.

I changed my sales code through the *#272*IMEI# and guess what!!

my product code changed too!

I checked it in the kies registry method + *2767*4387264636# method

+ Now I can see that my phone has the latest firmware when I check for upgrade in kies rather than the previous dreadful "This device's firmware can not be updated"!

Conclusion: I changed the product code easily by changing my sales code in (JPG) froyo firmware of the middle east.
[Galaxy S I9000 Android Development] usernome:
When I type the command with "cp" I get "cp not found" .
[Galaxy S I9000 Android Development] usernome:
Can anyone help me, please ?
[Galaxy S I9000 Android Development] gichin:
You should try: busybox cp .....

Best regards,

gichin
[Galaxy S I9000 Android Development] DaveNavy:
WORKED 100% Thanks...Phone gets relocked!!!! But thats fine now I dont Have TELUS canada product code on my T-Mobile vibrant. anymore

THANK YOU SIR!!!!:D
[Galaxy S I9000 Android Development] branuloo:
Hi

I am from slovakia, and yesterday kies allow me to update my galaxy from 2.1 Android jm2 to new android 2.2 GT-I9000_I9000XWJPH_I9000OXXJPA_I9000XXJPP_I9000XWJPH. After flash my imei changed to another 004... and when I try to restore my original imei by copy my backup efs folder to phone... Thats not work to original imei....after several hours I could to change imei to original by downgrade to 2.1 jm2... So whats wrong that after upgrade to 2.2 my imei being changed?
[Galaxy S I9000 Android Development] guy27:
Well, i flashed my phone with this version to I9000JPJG8 using ODIN. It is just PDA file and i ticked re-partition. Phone version was:

PDA: I9000 XWJM2

PHONE: I9000 XXJM1

CSC: I9000 OXXJM2

Now i see a blue circle instead of my network logo. Can you help me?
[Galaxy S I9000 Android Development] bernmc:
Thanks for this - very useful.

Can I suggest you add the 'busybox chown 1001:1001 /efs/nv_data.bin' to the instructions - spent a fair while sweating with the 'no such user' error before I found the solution in this thread - would just be easier to have it in the original instructions.

@guy27 -you need to apply the sim card fix in the original post.
[Galaxy S I9000 Android Development] leofonseca79:
XXX Product Code + Fake IMEI

To me happened exactly the same thing. Help, anyone? :confused:
[Galaxy S I9000 Android Development] surfer675:
product code Multi-combo

Thanks man !!! this is the easy solution I think. But still , it leaves previous P.Code at-least in recovery mode : mps_dat value: KOR . . . this can be solved easily with *272*xxxx method. and after that : tralala : you have warranty proof device ;)
[Galaxy S I9000 Android Development] surfer675:
im lame, stupid blind, i want to hit thank you button for you but dont know where :(
[Galaxy S I9000 Android Development] Dinglehoofis:
Every single one of my settings are correct. The IMEI is correct, SGS toolbox reports the correct product code, I took ownership of nv_data.bin and restored an efs backup. My SIM card will STILL not work. It sees the network but won't let me connect to it.
[Galaxy S I9000 Android Development] geesamsungs:
The OP's directions didn't work.

The directions posted by kaffre did however.

All I did was download the nv_data.bin to my phone and change the KOR to OPS, put it back on my phone and loaded it with terminal.

Deleted nv_data.bin.md5 and restarted the phone and bang. Done.
[Galaxy S I9000 Android Development] dinjo_jo:
I tried to find text like this but could not find it at all in my nv_data.bin

Any help here
[Galaxy S I9000 Android Development] pacinox:
THANK YOU VERY VERY MUCH!!!

I've tried ALL things, like flashing original and custom roms, different modems, ...

I thought my phone is broken forever, but YOU got it back to live!

---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------

The problem is, that it's not sure that you have the same salescode like "KOR". On my phone it was another code, like "XEU".

So first you have to dial following on your phone-keyboard: *#272*XXXXXXXXXXX# (XXXXXXXXXXX = your IMEI number. You can find it when you dial *#06#).

Now you can see which salescode you actually have. Try to find this one and change it the same way like "KOR".

Hope that helps you.
[Galaxy S I9000 Android Development] kathees:
Can you guys refer this and help me. I see it's same thing as your thread!

http://xdaforums.com/showpost.php?p=22547492&postcount=51
[Galaxy S I9000 Android Development] jamz_74:
What i found in nv_data.bin

I found the nv_data.bin file in my internal SD

It was not in any folders.

I opened it and found that it is already XEU but it looks strange

Here is the screenshot:

Anything wrong? How do i fix?
[Galaxy S I9000 Android Development] Methyldioxide:
Mate, the original file is also nv_data.bin.md5

But good to hear it works :)
[Galaxy S I9000 Android Development] Methyldioxide:
No my product code didn't revert like that. Others did also get their product code restored by using my method. If you think it happend cause of the .bak then your wrong! Cause not everyone got .bak files, and certainly not everyone did a backup to. If it was that easy, everyone would have got their original product code back. If you want your phone to restore by itself you MUST have made titanium clockworks whatever backup.

Some people like me didn't make any backups, so this is the only way to restore. And good to see some people do understand this method and got it fixed!
[Galaxy S I9000 Android Development] Methyldioxide:
Correct, i'm confused with the mps_code.dat file where the CSC code is stored. The imei i did find, but since mine was never corrupted or wrong or something like 000000000 i never tried anything with it.

I'll check into it, maybe i find out how to change it back. But this fix doesn't affect your imei for sure ! So for those who worry, dont. Imei is another cake and im glad mine never got corrupted when flashing JPC anyway .
[Galaxy S I9000 Android Development] Muaddib69:
Just a question before doing it... (easy)

I must change the first KOR, the 2nd one, or both?

Thx

More inputs;

In nv_data.bak is stored my original product code, in my case (Spain) the info stored is:

So...
[Galaxy S I9000 Android Development] EarlZ:
openined my nv date with notepad, didnt find any KOR >.<
[Galaxy S I9000 Android Development] akajess:
Clockworkmod doesn't backup /efs as far as i know - since it's a different block device (/dev/block/stl3) and if you make backups using clockworkmod or titanium backup then you must restore the phone manually - therefore it doesn't do it by itself!

Below i've marked with green the devices clockworkmod backs up and with red the efs device.

rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="DarkGreen"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
[COLOR="DarkGreen"]/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
[COLOR="DarkGreen"]/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
[COLOR="DarkGreen"]/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
[COLOR="Red"]/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

# busybox ls -lah
drwxrwxr-x 2 1000 1015 32.0K Sep 11 12:38 .
drwxrwxr-x 3 1000 1015 32.0K Sep 11 12:34 ..
-rw-rwxr-x 1 1000 1015 35.1K Sep 11 12:38 cache.img
-rw-rwxr-x 1 1000 1015 240.5M Sep 11 12:38 data.img
-rw-rwxr-x 1 1000 1015 15.3M Sep 11 12:38 datadata.img
-rw-rwxr-x 1 1000 1015 179 Sep 11 12:39 nandroid.md5
-rw-rwxr-x 1 1000 1015 268.3M Sep 11 12:35 system.img

I had the same issue as you did, after installing JPC i got my product code changed. All i did was to follow the instructions here hxxp://xdaforums.com/showthread.php?t=769400.

However i've read in another thread that when I did that the phone considered them invalid and made fresh ones from the backups (can't post the link because search is down atm)
[Galaxy S I9000 Android Development] Muaddib69:
Another question;

Using md5summer to generate md5 for ORIGINAL(KOR) nv_data.bin, generates a different "number" that the one stored in the ORIGINAL nv_data.bin.md5... (dumb question, maybe... but I'm limited...)

Try PSPad text/hex editor. Free.

Install PSpad

Select file -> right click -> PSPad Hex

Inside Pspad -> Search -> KOR

Voilá
[Galaxy S I9000 Android Development] kaffre:
The only thing that you must have is EDIT nvdata.bin and change the code KOR by your area code. Then delete de nvdata.md5.bin and restart the phone.

The system will create a new md5 file.

EDIT: tried in my own cell phone a few minutes ago
[Galaxy S I9000 Android Development] :
Same here.

@Methyldioxide Try make a md5 of your original nv_data.bin and compare it with your original nv_data.bin.md5. The md5 wont match. And if u change something in nvdata.bin the imei would change in 004999010640000. Try check yours with *#06#.
[Galaxy S I9000 Android Development] :
thumbs up

Holy **** it works guys!!!!!!:)

No IMEI change with this method.
[Galaxy S I9000 Android Development] lpy:
I had the original nvdata files backed up before I went to JPC, but then I lost them. I have other original nvdata files, but because of the dates of these files, I can no longer (ever?) use 2.1 again with a SIM card. JPC works fine however. Does this mean I'll be able to use Froyo official when it comes out, and and updates after that?

I'm not too concerned about 2.1 ever working again, just Froyo when it comes out.
[Galaxy S I9000 Android Development] Muaddib69:
But u changed the first KOR, the second, or both?:eek:

AND:

May I use root explorer to copy modified nv_data overwriting the KOR one with success?
[Galaxy S I9000 Android Development] :
i changed both.

Yes just overwrite and delete the nv_data.bin.md5.
[Galaxy S I9000 Android Development] kaffre:
For spain, first code are XEC and second FOP. Yes, you can use root explorer to overwrite nvdata.bin

I suggest that you modify the file /efs/imei/mps_code.dat too.
[Galaxy S I9000 Android Development] miki4242:
Great find, Methyldioxide!

But please update your first post with kaffre's tip: you don't need to regenerate the md5 file, just delete it on the phone :)
[Galaxy S I9000 Android Development] Methyldioxide:
I tested this, and indeed the phone recreates the md5 file! Really nice :cool:
[Galaxy S I9000 Android Development] Muaddib69:
Then, and as a final resume:

1. Modify 1st and 2nd KOR for you local code/s

(tried to see code list in www.samfirmware.com/WEBPROTECT-i9000.htm but didnt found it)

2. Suggested by kaffre: Modify code in /efs/imei/mps_code.dat (guess with the same you typed in nv_data, but, in case of Spain is XEC or FOP the code to type in mps_code.dat???)

3. Delete nv_data.bin.md5 and overwrite nv_data.bin
[Galaxy S I9000 Android Development] Methyldioxide:
Yes, you can use official Froyo. Prolly also without the product code restored i bet. But for warrenty it's best to have your original product code :cool:
[Galaxy S I9000 Android Development] Muaddib69:
Thx kaffre, but, why I have in nv_data.bak the following codes?

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿFOP GT-I9000HKDFOP

And, my guess is that the code to type in /efs/imei/mps_code.dat is FOP too... right?
[Galaxy S I9000 Android Development] Methyldioxide:
/efs/imei/mps_code.dat isn't always the same as your product code.

Mine is XEU while my product code is XEN, this is cause samsung dropped XEN somewhere in 2.1 firmwares. So my CSC is XEU. This can also be changed with the *#272*hhmm#* method i think. Wich is more safe todo, cause it resets your phone and edditing mps_code.dat doesn't!
[Galaxy S I9000 Android Development] lpy:
Thanks. Yep, product code is the right one, the nvdata files are just too new to work on any 2.1 firmware and 2.2 betas (except JPC).
[Galaxy S I9000 Android Development] Aery:
1. enable usb-debugging

2. adb shell

3. su

4. cp /efs/nv_data.bin /sdcard/nv_data.bin

5. disable usb-debugging

6. connect your phone to your pc with mass-storage enabled

7. open nv_data.bin from your internal SD-Card with an Hex-Editor

8. search for KOR and replace both findings with your original product code, save the file

9. enable usb-debugging

10. adb shell

11. su

12. rm /efs/nv_data.*

13. rm /efs/.nv_data.*

14. cp /sdcard/nv_data.bin /efs/nv_data.bin

15. reboot

Its not necessary to create a new nv_data.bin.md5 file. Just delete the old one, phone will create a new one for you. ;-)
[Galaxy S I9000 Android Development] g00ndu:
thanks, Aery. clear and precise instructions. I don't have this issue yet, but will prove useful for others.
[Galaxy S I9000 Android Development] gues42:
my code SIM card does not work, yet I followed the tutorial!

there is a solution please??
[Galaxy S I9000 Android Development] mark_glh:
If i used this method to change my product code from "VOD" (Vodafone) to "XEU" (Generic UK), would that also trick kies into treating the phone as unbranded? In a similar way to editing the kies registry entries. Or is that something completely different?

Ta,

Mark.
[Galaxy S I9000 Android Development] tokinux:
The same for me, pin code doesn't work.....
[Galaxy S I9000 Android Development] frank191:
The same for me, pin code doesn't work...
[Galaxy S I9000 Android Development] milan2008:
After trying this I can't get my phone off of flight mode.

Please help.

I tried a complete wipe and flash it to jm8 few times but no change. All works but it won't turn off flight mode. When I try to untick it box it tries for a while then becomes ticked again. :(

I tried to change my product code from KOR to XEU as I didn't know what my product was initially. It's a 16GB from Vodafone UK but as far I knew it was unbranded.
[Galaxy S I9000 Android Development] Methyldioxide:
Check if your product code really got changed:

- Connect phone and open Kies, disconnect phone and close Kies

- Open regeditor

- Goto: HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\1

Check here for the product code.
[Galaxy S I9000 Android Development] Methyldioxide:
This fix cannot produce the flightmode bug you describe. And very weird it happens also when you reflash the firmware. Did you try todo a factory reset and clear cache/usersettings before AND after you flash?
[Galaxy S I9000 Android Development] Methyldioxide:
Yes it should, if the product code is unbranded then Kies will also give you generic firmware upgrades.
[Galaxy S I9000 Android Development] milan2008:
I think you are right, this is not related to my issue but strange as I didn't do anything else.

I managed to fix it by flashing to 2.2 (JPC). I don't know how I managed to do it and whether it will still work if I go back to 2.1.

Thanks anyway
[Galaxy S I9000 Android Development] reb73:
I'm on jpc and followed the above instructions, but step 14 is causing a wierd issue..

(a) The amended nv_data.bin on /sdcard is 2097152 bytes (2048 KB exactly)

(b) When copied to the /efs folder, the size changes to 1998848 bytes and this causes the sim card not to be recognized and the gsm signal gone..

Luckily, I had a nv_data.bin.jpc file which I managed to rename and which retained the 2097152 byte size and suddenly, the sim card is recognized again..

Any ideas why the file size dynamically gets set to 1998848 bytes.. Is there something wrong with the way the /efs folder is mounted in my phone??
[Galaxy S I9000 Android Development] gnusmass:
question

I flashed to JPC 10 day ago

I still have .nv_data.bak & .nv_data.bak.md5

the code line in .nv_data.bak =

MP 0.800 ÿKOR GT-I9000HKDXEN

the code line in nv_data.bin =

MP 0.800 ÿKOR GT-I9000HKDKOR

Can i use this method to change both files? Or is that a stupid question?
[Galaxy S I9000 Android Development] Aery:
Two Methods:

a) Delete nv_data.bin and rename .nv_data.bak to nv_data.bin

b) Use my Method to edit nv_data.bin to your needs

Both Methods should work.
[Galaxy S I9000 Android Development] Aery:
I think this is normal. Two different file systems, two different file sizes.

Your Sim Card didn´t work because you´ve probably made an error.
[Galaxy S I9000 Android Development] reb73:
No, I'm pretty sure I followed the instructions correctly and edited the copy of nv_data.bin file in /sdcard directly without moving it to my windows machine.

If its two different file systems, I have a bak subfolder under /efs where I backed up the same nv_data.bin as well, but the copy in /efs/back reporting the correct size of 2048 MB whereas the file in /efs is reporting 1952 MB?
[Galaxy S I9000 Android Development] gnusmass:
If i use Method A this code is still there

MP 0.800 ÿKOR GT-I9000HKDXEN

shouldnt the code be?

MP 0.800 ÿXEN GT-I9000HKDXEN

(i am dutch, The Neterlands > XEN)

And cant i just copie and pas the changed file with "root explorer" or do i realy have to use a adb shell?
[Galaxy S I9000 Android Development] Aery:
Don´t know the correct codes for your Country. Use the search function.

Yes, you can use root explorer. silly question. xD
[Galaxy S I9000 Android Development] Methyldioxide:
If you readed my first post proper you would know you must change both KOR mate. And yes XEN is .nl
[Galaxy S I9000 Android Development] zenkinz:
does anybody knows what's the right product code for phone used in Singapore? I just found out that both my product code and imei has been changed even though I've not used JPC firmware. I wonder if changing the product code would help to revert the f/w or not.
[Galaxy S I9000 Android Development] hardcore:
Singapore's sales code is XSO (for Singtel sets). And the model number is GT-I9000HKAXSO.
[Galaxy S I9000 Android Development] :
Still cant use Eclair Roms -.-. Always says wront pin evens its right.
[Galaxy S I9000 Android Development] tokinux:
Here the solution for WRONG PIN CODE:

- Simply change owner and group of nv_data.bin using this commands:

adb shell
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot

My sim code now work correctly!
[Galaxy S I9000 Android Development] steffe.jst:
I

Love

You

Seriously, I was about to throw my phone out as paper-weight until I read this and got a massive epipheny of "that makes sense".

I ended up reverting to KOR in the processes but atleast now I know how I can get my simcard working when doing these things again. Seriously, thank you veeery much,
[Galaxy S I9000 Android Development] :
Ist this permanent or do we have to do it after reflash again?