yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] yanher:
Flash with odin3 process have failed. After reflash again into the JP2. I have purchased some softwares cann't register(Registration required to identify IEMI code). So,I found my I9000's IEMI code has been changed.

I've tried JF7 , JP2 , JP3 ..

IMEI codes have become 004999010640000...

Now, My fw is JP3 . I key *#06# in phone , It shows IMEI code is 00499901064000.

I can not find ways to restore IEMI..
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
Try downgrading to eclair I mean.. JP3 is another alpha firmware..

And what software do you mean was registered to your Imei?
[Galaxy S I9000 Q&A, Help & Troubleshooting] yanher:
I has downgrading to JF7, IEMI code still cann't restore.

Navking http://www.naviking.com.tw/

Purchase and registration code which will check IEMI.
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
So your assumption is that the IMEI code has changed because of 1 software applications? Check the box for your phone and compare it to that. It's more likely that your IMEI code is still the same.
[Galaxy S I9000 Q&A, Help & Troubleshooting] yanher:
IEMI has changed by odin3, I think.

My origin imei code is 35175104185xxx2.

I check in google the 004999010640000 maybe is engineering code.

Another guys have the same problem with me.

Maybe needs to repair by samsung. :mad:
[Galaxy S I9000 Q&A, Help & Troubleshooting] RazvanG:
If you have an IMEI of 004999010640000, you have a crypto failure in your locktables in the seczone and your phone is in "lockdown" mode.
[Galaxy S I9000 Q&A, Help & Troubleshooting] FadeFx:
only software i know to register on imei is wavesecure.
[Galaxy S I9000 Q&A, Help & Troubleshooting] yanher:
How can we solve this problem?

Another guys have same problem ,tell me. His phone back to samsung sevice for 7 days. Back of the phone is replacing a new motherboard and new IMEI code. :mad:
[Galaxy S I9000 Q&A, Help & Troubleshooting] RazvanG:
Send your phone back to Samsung Repair Center/Service. Sorry
[Galaxy S I9000 Q&A, Help & Troubleshooting] stierney:
004999010640000

Same error with IMEI on my phone. Havent used Odin, could be a faulty batch? Currently in negotiations with my supplier to get it replaced.

Originally thought i had a faulty SIMM but mine reports this IMEI eith *#06#
[Galaxy S I9000 Q&A, Help & Troubleshooting] milo76:
I only had my phone for one week when i discovered that my IMEI number was wrong.

Sent the phone back to Samsung an got it back today (4 weeks after) and guess what, the IMEI number is still wrong.

Thank you very much Samsung. :(:(
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
Is it the same IMEI? Or a different one though? Many phone manufacturers replace phones with another unit.
[Galaxy S I9000 Q&A, Help & Troubleshooting] milo76:
Same IMEI

004999010640000
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
Can you tell me a nick of a dev, please?
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Seems that if you are unlucky it can happens.

If the file in the efs folder has been regenerated.

If you put your original files back it might work.

Sent from GT-I9000 Jpm OS kernel with z4mod
[Galaxy S I9000 Q&A, Help & Troubleshooting] Und3rtaker:
first, big thnx for help

you're right :\

i was using ES File explorer(ESFE), but with it, when i taped /efs map, it entered and said, that it's empty...

today i was testing ftp access and saw that i can access folder like /etc, but not /efs.. checked in ESFE, and saw, that directory has only d attribute, but not r...

but now i have a problem with root explorer as well :\

every time i start program i get error, that there is no root access...

it's explained in this thread

"[ROM] [FROYO] Voodoo Doctor Edition v2.0 | Universal Lagfix | CWM recovery"

- known problem .. well have to read 20 pages, if there is solution...

any other way to access these files, to make a backup of them?

p.s. you should maybe delete this post, since i see it's just my mistake or stupid interpretation of ESFE software and will probably not be helping anyone in the future :)) ..
[Galaxy S I9000 Q&A, Help & Troubleshooting] BronzedDroid:
You need root to use root explorer. Root or superuser is basically what would be called administrator in Windows. You can find several guides on how to get it on this forum.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Und3rtaker:
i finaly managed to backup /efs folder..

it went something like this..

root explorer didn't work, since it has problem with voodoo pre4, so i went to recovery console, loaded clockworkmod, mounted system and than through adb copied with busybox command and another through simple linux comand cp -r :))

only one more question.. these nv_data files, do i need to restore them everytime i flash with new rom, or only if phone(imei) becomes corrupted after some bad flashing?

nv_data.bak has inside my operater code GT-I9000HKDMOT, which i would think is my original nv_data file

or do i leave nv_data.bin which has i guess code from flashed rom(JP6 De-deodexed and zipaligned ROM for GT-I9000 with Voodoo and 2e recovery! from Kalpik), GT-I9000HKDXEE ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] aussieak:
Well I just fixed my IMEI form 004999010640000 back to my handset default.

Background

I did the Reg hack to update to JP6 and then decided when it was pulled to revert back to JG4 via odin. All went well when I noticed my product code kept changing to XEE in the registry . But my IMEI stayed the same.

So I tried a few of the nv_data.bin edits but it seems when I read one post to use notepad or word pad to change the product code that all seemed to work that later I discovered my IMEI changed to 00499901064000.

The fix

I was lucky to keep my nv_data.bin file that had the wrong code in it and copied back to efs folder and success my IMIE returned.

I then looked for a real hex editor and used search and replace to edit the file to correct product code.

Copied back and now I have correct product code and IMEI.

I will be keeping my new and fixed nv_data.bin and nv_data.bin.md5 as back up from now that I know these works.

One suggestion is to see if you have hidden nv_data files in your efs folder they maybe able to help you.
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
Can you tel me what files you are talking about? I can place here a screen of the output of the follwing comand

su
ls -la /efs

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] AdamDowning:
You need to send back the file nv_Data.bin
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
You mean to delete nv_data.bin and rename .nv_data.bak to nv_data.bin?

The files are exactly the same size... Renaming it will make any difference?
[Galaxy S I9000 Q&A, Help & Troubleshooting] thmlwin:
Ohh, Thank for your instruction. I also faced same problem with you and now I can recover my IMEI back. Now I can happy even though product code change.
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
Can you help me doing that? Can you tell me, step by step how to do that, please?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] aussieak:
There are plenty of instructions on xda already but what worked for me is

Must have a copy of nv_data.bin that your imei works with. You can check for hidden files in the efs folder to test.(ls -a

You must be rooted and know how do use adb shell.

you must use a real HEX editor. ( I use one that warns me if the file size changes.

Use Kies to confirm changes to product code worked.

I was one of the silly ones that did not back up my efs folder when 1st changing ROM but was luck enough to keep even a incorrect product code but let my imei correct file which I modified.
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
I have 3 backups of /efs folder but i don't know if any of them has the correct product code or IMEI.

My SGS is rooted and i know a bit about working with adb. I use too the terminal emulator that i think is pretty the same as adb.exe.

What i am not understandig is what to do with Hex editor and with all these backep up files.

In all 3 backups i have there are the following files:

.nv2.bak

.nv2.bak.md5

.nv_data.bak

.nv_data.bak.md5

.nv_state

nv_data.bin

nv_data.bin.md5

So what should i do with each one?

Run an Hex editor and do what? And what Hex editor should i use?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] buyslake:
Hi,

I also have the same problem and have the back up files. What do we do with the hex editor?

Which offset do we go to? And what do we write? Original IMEI?
[Galaxy S I9000 Q&A, Help & Troubleshooting] aussieak:
Try overwriting nv_data.bin with .nv_data.bak and delete nv_data.bin.md5

and see what results you get. If you get your imei back but bad product code. then edit that file. If that does not work go to .nv2.bak dont forget if you loose acces to your sim card to chown the nv_data.bin( i will try and find the command again

delete the nv_data.bin.md5 as this gets recreated with every boot.
[Galaxy S I9000 Q&A, Help & Troubleshooting] HorusEyE:
So tell me how can our IMEIs get corrupted or incorrect or whatever you want to call it???

Some says that only part of the IMEI is stored in nv_data.bin, some says that it is all stored in that file. Some says thai IMEI cannot be corrupted, others says that it can be recovered, some says that it can't...

So, does anyone enlights me on this, please???
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
Tell that to all the people who had the files messed up with the IMEI.

Either way, the fact that the IMEI CAN be corrupted by software file changes, means that it isn't perfectly safe..
[Galaxy S I9000 Q&A, Help & Troubleshooting] Aweb:
I had the exact same problem.

I deleted everything in the /efs/ folder except the imei file and folder. Then rebooted, my sim worked but with a test imei, which is bad.

After wiping almost everything in this folder again, I then put a backup of nv_data.bin I had made a long time before in /efs/ and I rebooted.

Now everything works perfectly fine and I have a real imei =)
[Galaxy S I9000 Q&A, Help & Troubleshooting] android.francis:
[SOLVED] Help! My IMEI changed?!?

I recently upgraded to JPA and for some reason, the IMEI changed! I double checked with what I have in the box when I bought it and it is not the same.

What do I do now? :eek:

SOLVED: Apparently, SGS Toolbox creates a backup everytime you check your product code. I was able to rewrite the files in EFS and bingo! EMEI corrected.

That was a close one! whew!
[Galaxy S I9000 Q&A, Help & Troubleshooting] VladaP85:
My phone was on service and they change my motherboard. When I get it back my IMEI was 004999010640000... What can I do? Can they fix this at service? Any confirm?
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
Then they messed up the procedure.. Complain and tell them when they returned your phone the IMEI code wasn't correct.
[Galaxy S I9000 Q&A, Help & Troubleshooting] kiwijunglist:
These are the only instructions I have seen regarding how to backup the efs folder. I am not sure do I need to do all 3 commands or just choose 1. Can anyone point to a more detailed guide to follow for those of us who are not very familiar with using busybox and adb. I currently have a rooted SGS with voodoo lagfix, although busybox on the phone doesn't seem to work, so I think I will need to use adb shell.

Basically I am looking at flashing the latest Doc_Kalpik rom using odin, but want to backup my efs directory prior to the flash. As I've been told it is safe practice to do so.

Thanks in advance

Kiwi
[Galaxy S I9000 Q&A, Help & Troubleshooting] EarlZ:
Still no method if we dont have a backup of the nv_data that contains the original IMEI ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] takato23:
there isn't any fix yet? today i've recived my fixed vibrant, rooted, unlocked and now i see that i can't get registered to the network because of the 0040.. imei
[Galaxy S I9000 Q&A, Help & Troubleshooting] fleau_aut:
there were backups in my /efs: .nv_data.bak and .nv_data.bak.md5...

rename those to nv_data.bin and nv_data.bin.md5... everything will be fine again :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] vrehenriqu:
[HELP / issue report] Dalvik / IMEI report issue

Hi!

I’m currently using Doc’s Froyo ROM v7.6.2 JPO, without any lagfix or tweaks enabled.

The ROM flies and it’s very nice.

I have however an issue that is puzzling me:

Sometimes the IMEI is not reported (*#06# code).

I found this issue also when using official ROM Éclair JM8 version. But in this ROM the IMEI was not being reported only when Voodoo lagfix enabled. Using OCLF lagfix the phone reports IMEI OK.

With Doc Froyo V7.6.2 ROM I found that by wiping Dalvik cache it fixes the IMEI report issue. However, doing a reboot afterwards it will mess up IMEI report again.

One thing I found is that when wiping Dalvik cache on CWM recovery bootloader, it reports “E:Info WrongDALVIK”

Could it be a dalvik issue?

Didn’t find anything special on google…

No strange apps installed besides SuperPower. Uninstalled it but the issue is still there.

Another issue that happened was duplicate photos on gallery. Solved it formatting the internal and ext SD cards…

Besides this, the phone is working fine, I guess… but my impression is that later on I could have issues…

Any help would be appreciated.

Thanks!

SGS I-9000GT, 8Gb, Doc’s Froyo ROM v.7.6.2 JPO, Branded, no Lagix or kernel tweaks, Launcher Pro, AOSP lockscreen, Battery circle Mod.
[Galaxy S I9000 Q&A, Help & Troubleshooting] vrehenriqu:
I found that the issue is related with the PHONE portion of the ROM. When entering *#1234# code it reports:

(With DOC FROYO ROM v7.6.2

PDA: I9000XXJPO

PHONE: Unknown

CSC: I9000OXAJPO

Build Info: 2010. 10

Any ideas to fix this??

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] Candanga:
Why so much agression? Geez.. Old thread :P

Same happened to me bud. I just flashed to Tayutama's ROM and woke up to see the uptime vs the consumption and found out I have a 0000xxxxx w/e IMEI. I think it was due to a "network pin unlock" method that I did, changing stuff in HEX and stuff. I though I needed that unlock to make something else work here, but I didn't.... PHAIL :p

I backed-up my efs folder, so I'll see If I can get it back to work.
[Galaxy S I9000 Q&A, Help & Troubleshooting] buyslake:
Hexadecimal or Decimal for offset?

I am trying to edit the offset in the nv_data.bin file to unlock my phone.

My hexadecimal editor software has a "go to offset" option. But it asks me to decimal or hexadecimal.

which type of number? do I go to to change the FFFFFFFF to 00000000?????

decimal or hexadecimal?

and it seems to be different for the product code vs. the unlock code?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Candanga:
LOL @Buyslake

This thread is not for unlocking. Search XDA for the proper thread. Just FYI, that "hex" procedure to Network Unlock, is the one that walked me-in to get a pwny IMEI after several flashes.

Cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] varanyab:
[Q] No IMEI and Unknown baseband of ddgj4

Hi

Currently i am running Darkys legendary steel edition v4.1.My phone is working smoothly without any problem..But I want to go back to my stock firmware which is ddgj4 as i am from India.But when i flash that with odin i always gets baseband unknown problem with unknown imei..If i flash any other froyo custom rom using update.zip there is no problem and it works fine...

can anybody suggest the solution of this behaviour of my phone.or give me a link for ddgj4 in update.zip format..

Thank u
[Galaxy S I9000 Q&A, Help & Troubleshooting] android.francis:
Maybe it is how you are flashing your phone via Odin. Are you putting the correct .tar files under PHONE, MODEM and CSC?

What .pit are you using? Did you also tick re-partition?

Odin is a great flashing tool as long as you know how to use it. There are threads here that will show you how to use Odin or go to this URL:

www.samfirmware.com

It has a step-by-step instruction on how to flash via Odin and also gives you the proper .pit file you need to use.
[Galaxy S I9000 Q&A, Help & Troubleshooting] varanyab:
i have used odin lots of time.This problem has crept up recently after i have updated to froyo.Are there any logs which can be read to see whats wrong happening after flashing..is there some compatibility issue with nv_data.bin
[Galaxy S I9000 Q&A, Help & Troubleshooting] android.francis:
not sure but the closest thing that this kind of situation happened to me is when the .tar CSC was not compatible with the rest of the files I flashed via Odin.

Where did you get the original firmware from? Maybe those files have some data corruption of sort. Try looking for another copy of elsewhere and try it again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] varanyab:
thank u..i i will try to find another copy of the firmware.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ashwinds:
The strangest thing since Froyo is IMEI disappears occasionally if you reboot with USB connected. Reboot it without USB and its fine.

I guess the baseband modem does not get recognized - maybe some bug to do with USB tethering.
[Galaxy S I9000 Q&A, Help & Troubleshooting] icsssss:
[Q] IMEI corrupted

Hey guys,

I updated my Galaxy S to official Froyo 2.2 yesterday, but the IMEI number was corrupted. Unfortunately I didn't backup my /efs folder.

There is a way to restore my original IMEI? :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] peppecif:
stesso problema . Ho anche il backup , ma non funziona. Provato anche con root explorer e adb , nulla .

A me è successo quando ho seguito la procedura per cambiare il product code da xee a itv.

Same problem for me. I have efs backup and try to restore with root explorer and adb , without success.

I had problem changing product code XEE with ITV...
[Galaxy S I9000 Q&A, Help & Troubleshooting] vinceyeung:
i have also this problem! tho i have backup, and i restore the efs data back to the default folder....the phone just cant recognise the files i put in...i have alredy flash other roms then to c if it works again...but it's not...still no IMEI for my phone and i cant connect to any phone netwoek using different sim...the baseband of the phone is also unknown and the PHONE(by dialing *#1234#) is unknown too! HELP...i m currently using no lagfix and XXZSD
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
Ok I too had the dreaded 0044 IMEI issue and manged to fix it.

so what i did was put back the stock samsung jpo 2.2 rom it's avaliable in the rom section. Did this via Odin.

Rooted the phone and installed root explorer. I did have a copy of my nv bin file on my pc.

if you dont try to use the nv bak file which is a backup of the bin file.

if you have the bin file saved on pc copy it over and delete everything in the /efs dir except the bin file, if you have the bak file delete everything and rename the bak file to .bin instead.

once the only file left in /efs in the nv bin file close root explorer and go to your dialling screen

type *2767*3855#

this will give you a hard factory reset.

Once i did this the phone rebooted and rebuilt my /efs dir from the bin file and my original IMEI number was back.

Thats what worked for me. Your IMEI is messed up now so it wont do any harm. I wouls copy the bak file to your pc just as backup.

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
this worked for me. IMEI back to normal

Ok I too had the dreaded 0044 IMEI issue and manged to fix it.

so what i did was put back the stock samsung jpo 2.2 rom it's avaliable in the rom section. Did this via Odin.

Rooted the phone and installed root explorer. I did have a copy of my nv bin file on my pc.

if you dont try to use the nv bak file which is a backup of the bin file.

if you have the bin file saved on pc copy it over and delete everything in the /efs dir except the bin file, if you have the bak file delete everything and rename the bak file to .bin instead.

once the only file left in /efs in the nv bin file close root explorer and go to your dialling screen

type *2767*3855#

this will give you a hard factory reset.

Once i did this the phone rebooted and rebuilt my /efs dir from the bin file and my original IMEI number was back.

Thats what worked for me. Your IMEI is messed up now so it wont do any harm. I wouls copy the bak file to your pc just as backup.

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
How I fixed the 0044 IMEI issue on my Galaxy

I added this to a couple of threads but have made a new thread so it might be more visible to those with the 0044 IMEI issue. This worked for me but I did have the BIN filed saved on my PC.

Hope this works for others.

Ok I too had the dreaded 0044 IMEI issue and manged to fix it.

so what i did was put back the stock samsung jpo 2.2 rom it's avaliable in the rom section. Did this via Odin.

Rooted the phone and installed root explorer. I did have a copy of my nv bin file on my pc.

if you dont try to use the nv bak file which is a backup of the bin file.

if you have the bin file saved on pc copy it over and delete everything in the /efs dir except the bin file, if you have the bak file delete everything and rename the bak file to .bin instead. Dont forget the .bak file has a . before it so deleted that as well

once the only file left in /efs in the nv bin file close root explorer and go to your dialling screen

type *2767*3855#

this will give you a hard factory reset.

Once i did this the phone rebooted and rebuilt my /efs dir from the bin file and my original IMEI number was back.

Thats what worked for me. Your IMEI is messed up now so it wont do any harm. I wouls copy the bak file to your pc just as backup.

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] vinceyeung:
just tried this method

when i dial *#06#, i still cant c my valid IMEI and my baseband is still unknown
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
worked ok for me, try the hard reset a few times see if it kicks in. also dont forget the .bak file has a . at the beginning so remove that as well when you rename it.

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] grahamrobb:
I had a back-up of my efs folder on my pc and tried this from stock 2.1 with no success. I installed Cognition 2.4.1 and gave it a shot. Worked like a charm ! Thank You !:D
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
Cool we have a success, hopefully it will work for others.

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] lordao:
Had a few replies that this has worked for some people and not for others. Well guess a random fix is better than no fix. Worth trying not like you can make your phone even worse..:D

Lordao
[Galaxy S I9000 Q&A, Help & Troubleshooting] vinceyeung:
[Q] IMEI's missing but i cant restore!

My IMEI is missing after flashing custom rom...

when i dial *#06#...no IMEI number shown and I have checked that I got unknown baseband

when i dial *#1234#: it's the information i get:

PDA: I9000ZSJPD

PHONE: Unknown

CSC: I9000OZSJPD

Build Info: 2010. 10

I have searched for more than 6 hours and try to fix with different solution inside or outside this forum but still I cant restore my IMEI

I DID have the backup of my efs folder before (before it's not working) but I am not able to restore it back. Whatever I try (flashing a new rom 2.1 or 2.2 or reboot), the efs folder seems ignore my newly-copied files and dun let me have my IMEI back. I cant dial with any sim cards and I cant install any IMEI-required app. Anyone can help me please?

I have even checked if there is any samsung repairing centre but seems the available ones near me is all Carphone Warehouse (yes i m in UK), how can I make my phone work again? or how can I talk to the staff to avoid charging me for a new pcb for the phone?