Wtf, this is crazy, I got mine from Orange UK and its getting picked up by courier tomorrow. As its under 12days old im going to be requesting a complete new device not a repair!

Which mobile operator did you lot use? Im begining to think there may be a faulty batch,

i have the same error，and after that,i am unable to download any apps from the market.....>.

Is it possible these phones were network/sim locked? Apparently you shouldn't flash locked phones

Originally Posted by andrewluecke

Is it possible these phones were network/sim locked? Apparently you shouldn't flash locked phones

Not as far as I am aware. I got a firmware update notification from the official KIES software. Kies software still says it needs an update. This is What it says.... <GT-I9000>'s Firmware can be upgraded, please click here to upgrade....


Followed by:
Current Version :PDA:JF3 /Phone :JF3
Latest Version: PDA:JFA /Phone:JFA

When you upgrade it just goes through the motions and then after completion you reconnect and it says the same thing again.

The phone functions normally but i just cant get or make calls because the IMEI is rejected by orange because its that default 0049 one that everyone else with this problem has.

Just thought i would add the other ionfo from 'About Phone' incase any of that is non standard...

Firmware Ver 2.1-update1
Baseband version I9000xxjf3
Kernel version 2.6.29 umts_scm@s1-build05 #2
Build Number ECLAIR


This phone was sold to me in the UK

Can anyone confirm if the software versions are correct for a stock phone straight out of the box? i will update when i get some feedback from Orange UK. They are picking the device up tomorrow to check it out

My recommendations :

- NEVER check Debug / Phone EFS Clear in Odin
- If you're rooted, make a backup of your /efs directory
- If you play with Odin and firmwares, consider rooting to backup your /efs

For research purposes, i wrote the content of the /efs of another Galaxy S into mine.
After a reboot, I got the 004999010640000 IMEI too.

Hopefully, after restoring a previous /efs backup, everything came back right.

Explanation :

/efs/nv_data.bin contains IMEI data in encrypted form (and some more device-specific infos).
If the phone software/baseband can't match nv_data.bin with real hardware values, you get the mock IMEI 004999010640000.

This is the same thing if you wipe EFS. You loose your nv_data.bin and same **** happend.

I suppose that a software exist to re-build the appropriate nv_data.bin.
This software must contain baseband vendor code, and is probably highly confidential.

Originally Posted by supercurio

My recommendations :

- NEVER check Debug / Phone EFS Clear in Odin
- If you're rooted, make a backup of your /efs directory
- If you play with Odin and firmwares, consider rooting to backup your /efs

For research purposes, i wrote the content of the /efs of another Galaxy S into mine.
After a reboot, I got the 004999010640000 IMEI too.

Hopefully, after restoring a previous /efs backup, everything came back right.

Explanation :

/efs/nv_data.bin contains IMEI data in encrypted form (and some more device-specific infos).
If the phone software/baseband can't match nv_data.bin with real hardware values, you get the mock IMEI 004999010640000.

This is the same thing if you wipe EFS. You loose your nv_data.bin and same **** happend.

I suppose that a software exist to re-build the appropriate nv_data.bin.
This software must contain baseband vendor code, and is probably highly confidential.

how would you back that up?

Originally Posted by Daemos

how would you back that up?

Just use root explorer or adb to save the files somewhere.

Originally Posted by supercurio

My recommendations :

- NEVER check Debug / Phone EFS Clear in Odin
- If you're rooted, make a backup of your /efs directory
- If you play with Odin and firmwares, consider rooting to backup your /efs

For research purposes, i wrote the content of the /efs of another Galaxy S into mine.
After a reboot, I got the 004999010640000 IMEI too.

Hopefully, after restoring a previous /efs backup, everything came back right.

Explanation :

/efs/nv_data.bin contains IMEI data in encrypted form (and some more device-specific infos).
If the phone software/baseband can't match nv_data.bin with real hardware values, you get the mock IMEI 004999010640000.

This is the same thing if you wipe EFS. You loose your nv_data.bin and same **** happend.

I suppose that a software exist to re-build the appropriate nv_data.bin.
This software must contain baseband vendor code, and is probably highly confidential.

Thx for the info. The curious thing is i only used Kies for an update, or attempted update. so are you saying that you need to root your device to back up this file? I cant see an icon from within KIES to back up the phone so im assuming that it isnt possible to do using standard Samsung authorised software..?

When i get my phone back its the first thing im gonna do if it is possible to backup this in some way using an app or authorised software

Im not sure i wanna go making changes until i know i can recover from them without invalidating my warranty!