yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] surfer675:
Miracle

(didnt read all post so sorry if it is a miss-post)

Somehow, dont know how Miracle has happened, i had 004999010640000 imei, and didnt know what to do, no backups etc, phone not working, this "how to" dindt work even for generic imei etc.

only think to get back original imei for me was to reflash this rom : Ficeto_Deodexed_JVH_I9000 (2.3.3). honestly dont know why it was on my hdd, have great mess there. So I want to ask how is it possible or where did the phone found my imei then?
[Captivate Android Development] EskDroid:
Emei

Wat a story. Do for ones hand for all

BACKUP YOUR EMEI. Take backup pro

It saved a several times my life. My phone is

my life, nog juist a thing toe plat wit.

A tip. Go back tijd xxjvu ten root. You have than

A stock Ron. Go toe the Guus vorm Cyanogen

hand port ics Cyanogem9 on your phone.

My i9000 is running now Smooth for more

thene 4 week. Make first a bakup vorm your

XXJVU (its Gingerbread 2.3.6) myne is Dutch

do shange language in Eng. Hen threre is something ging wrong, onze push on de restore

button from "Backup Pro". You dont have backup pro. Geven me a om, hand i Will put IT in my Dropbox.
[Captivate Android Development] nemesis666999:
'Unable to connect. Try later''

Hi

I had problem 'Unable to connect. Try later''.

Then i realized that my IMEI is messed up.

Followed this tutorial.Inserted my SIM card (not the one that i am using, it was some old prepaid card , same carrier) ....the phone could not read this one....inserted the one that i am using ....the phone successfully logged on the network...but now the pone couldn't read the SIM contacts. i looked in the efs folder and 4 files were in it

nv_data.bin

nv.log

nv_data.bin.md5

.nv_state

then i rebooted the phone, the sim contact were herei .. looked in the efs folder

.android (empty folder)

nv_data.bin.md5

nv_data.bin

nv.log

cryptprop_securewipedata

cryptprop_onetimeboot

cryptprop_applied_result

.nv_state

so the conclusion is the IMEI is stil generic 004999010640000 BUT THE PHONE IS WORKING :D

so f.... happy
[Captivate Android Development] lordxentris:
Thanks bames,

Did as you said in you OP, installed Slim ICS 3.5 and copied back the patched EFS Folder, and tada.. got my IMEI back in order. Thanks a million. :D
[Captivate Android Development] poprocksncoke:
None of these options are working for me :( What if I copy the efs folder from another phone to an sd card and then put the sd card in the non working imei phone and replace the efs folder with the working one?
[Captivate Android Development] Red_81:
That will get you the generic IMEI at best.
[Captivate Android Development] daveshouse:
Thanks to everyone that have contributed all the helpful information in this thread, I have tried everything but with no luck. Unfortunately, I didn't have the foresight to back up the efs folder before I started playing with the thing.

Are there any companies or individuals that can restore the original IMEI on my device from the generic IMEI and with no efs backup, or should it go onto eBay for spares and repairs?
[Captivate Android Development] Red_81:
Go to google and type in Mobile Tech Videos Captivate.

I phrase it that way because we are not supposed to link to pay services. The owner is an XDA member and restored my captivate back to its original IMEI from the generic. It took about 1 week.
[Captivate Android Development] jmtheiss:
I know this will sound weird, but I've been able to get my EFS back in working order by flashing Mosaic 9. I've done this twice already, so I don't think it's just a fluke.
[Captivate Android Development] causticfix:
steps in op worked perfectly for me...

after the carrier wide FCC "stolen phone blacklist" got rolled out a few days ago, my vibrant got blocked from network because of the changed IMEI from all my flashing. found this thread and now I'm back in service.

thanks.
[Captivate Android Development] mletchworth:
Definitely appreciate this thread, even though it didn't actually help me. Somehow during a recent ROM Flash my entire SD card was wiped, including the efs folder. Then when I ODIN flashed gingerbread, it didn't restore the IMEI. Skip to yesterday, when I was running CM9 stable and my phone gets shut off for having a generic IMEI.

Just finished flashing back to JF6 stock, which restored my IMEI. I then made sure it was still there as I flashed my way back to CM9. Now I've got an EFS backup folder just in case!
[Captivate Android Development] andrewdroid:
I never even thought about this whole imei thing until I read the scary stories in the HellyBean thread. (I'm on CM9 now though)

Anyway I quickly backed up my EFS folder and then made sure my IMEI by doing *#06# was the same as the one behind the battery door. Any more things I need to do to protect myself?
[Captivate Android Development] :
This, and other various restoration methods didn't help me. Can't flash to stock becuase my usb port's broken... my cell service got shut off, called in, had them turn it back on calling their claims ludicrous and i'm good to go apparently.

Meh.
[Captivate Android Development] kalda01:
Can someone explain how flashing back to GB might restore the original IMEI id if the actual original EFS folder is now gone from the internal SD card ?

Alternatively, is there a way to extract files from EFS.IMG which I found inside an old nandroid backup folder ?
[Captivate Android Development] :
All in all, you don't HAVE to have your own IMEI number. But if by chance you get blocked by your carrier, call and explain to them that you don't pay for them not to provide their service, and that you in no way called to have your number blocked. They should be willing to work with you.
[Captivate Android Development] XeoNoX:
i have read that using "Samsung Tool 12.7" will fix/repair it without a backup of your EFS. you will have to google instructions
[Captivate Android Development] XeoNoX:
wow 4 hrs later but i got my IMEI back again and this time i am backing it up!!! the oridinal method by the OP didnt work for me but then again i tried it on Jellybean instead of the older build. Long story short i forgot to backup my EFS folder and got the currupts IMEI message. I had to ODIN back to stock using darky rom's " Ficeto_Deodexed_JVH_I897_ODIN " and this fixed my IMEI and it is now back to normal. here is the exact screenshot of the settings i used in ODIN
[Captivate Android Development] kalda01:
Can someone explain how flashing back to GB might restore the original IMEI id if the actual original EFS folder is now gone from the internal SD card ?

Alternatively, is there a way to extract files from EFS.IMG which I found inside an old nandroid backup folder ?

I understand that a generic IMEI might be OK for now, but the error message each time I reboot drives me nuts, so I'd like to get rid of it somehow.
[Captivate Android Development] xdadooder:
Can someone please provide a working link to this Ficeto_Deodexed_JVH_I9000 that everyone is raving about?
[Captivate Android Development] xdadooder:
I don't have an efs folder on my phone. I tried showing hidden files and folders on folder options. Still nothing. So I created an efs folder both on the phone and in the system folder. I put in all the files from efs_backup into both folders and edited the nv_data.bin according to the OP. Nothing changed. Still a generic IMEI. Can someone help me?
[Captivate Android Development] XeoNoX:
here is the file, use the settings exacly how i have in the screenshot above and run ODIN as administrator

https://docs.google.com/file/d/0B0xrnOjLAYJJT0xwSXlQMm8xbk0/edit?pli=1

---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------

i cant explain how or why it works, it just does...i guess it just sends the phone back to "stock" i dunno, i just know it fixed my IMEI problem since i didnt have the EFS folder backed up. reply back if successfull
[Captivate Android Development] kalda01:
If I do nandroid backup before flashing back to GB, just so that I can restore my EFS folder, would I than be able to restore

back to JB from the nandroid backup ? If not, does it mean I have to root and flash CWM and start from the top again ?

Btw, I found an old nandroid backup folder with EFS.IMG included in it. Is there a tool I can use to extract the EFS folder out of the image file back onto the device?
[Captivate Android Development] XeoNoX:
YES u will be able to restore using nandroid if u flash to GB with "odin" HOWEVER when u restore your nandroid copy you will have to make sure that MATCHING kernel and bootloader are installed prior to you restoring your nandroid backup (in other words make sure you install the same bootloader and kernel thats contained in your nandroid backup..in your case since you will just be going to gingerbread you shouldnt have to mess with the bootloader, just make sure the kernel matches the nandroid backup)

EFS.IMG may or maynot contain the right efs information...all i know is that if you want to restore your IMEI then you will need the correct "nv_data.bin" file that is under the EFS folder of your root directory. If you do not have the right nv_data.bin then the files i provided in my previous post shoud work but if you want to test your EFS.IMG file u might want to read this thread http://xdaforums.com/showthread.php?p=21066107
[Captivate Android Development] kalda01:
Once I do the ODIN flash as you have suggested to restore the real IMEI, will it be possible to flash the current kernel back right away, or do I need

to flash recovery first ? (does the JVH rom include CWM ?)
[Captivate Android Development] testomat:
Below is for a cappy. but how should it look like for a vibrant ? Can anybody post it for me ?

00188008|2e|34|00|00|00|00|ff|41|.4....A

00188010|54|54|00|00|00|00|53|47|TT....SG

00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK

00188020|41|41|54|54|00|00|00|00|AATT....
[Captivate Android Development] testomat:
Solved. In sdcard/Backup was a Backup of my imei.

Should look like this

http://imgur.com/JlUSY
[Captivate Android Development] rophiroth:
someone knows what are the default cheated IMEI I want to try them to get blocked in my country
[Captivate Android Development] lordxentris:
Now why would you do that?
[Captivate Android Development] rophiroth:
thieft still keep stealing phones day by day because dumb people can hack IMEI with double click an internet app and re-sell phones. At least if a thieft will steal my phone again I would like him to be a a little less dumb and use another IMEI when hacking my phone :P
[Captivate Android Development] _-mike-_:
I had the same problem after flashing CM10. But thanks to the flashing process which creates a backup of the efs folder every time an updates is applied i had several very old backups -> I choose one of them copied the complete folder to /sdcard/Galaxy_S_Unlock. Installed the Galaxy_S Unlock app and used it's efs-restore feature. Now I again have my 35*-imei!

nice regards
[Captivate Android Development] wangxp:
If you no nv_data.bin backup You never take IMEI recover back ...

:(
[Captivate Android Development] neophyte1983:
Hello does this working on sgs2 with ics because i deleted my efs folder in accident.
[Captivate Android Development] dd807:
we need this info for the sprint note 2- o r maybe its just me...
[Captivate Android Development] kinggame992000:
i tried it before... but it not work......i really want to fix this thing man... does any one suceed in doing this.. if you do.. please have a step by step instruction for people like me
[Captivate Android Development] drummerian:
would also like to know this. I don't have any of the .nv files mentioned in the other articals so i feel this way would work for me insted. Any ideas?

thanks guys
[Captivate Android Development] DamDSx:
If I understand the logic of this fix, what you did was restore the product code.

I know of a galaxy S I-9000T with this problem, in theory I can recover the product code as long as I enter the correct product code here for this particular phone.

Shouldnt be much different right? Im tempted to give this a try since there is no known way to recover imei for that model
[Captivate Android Development] TotallydubbedHD:
Hi there,

Thanks for the guide - however no matter what I did it didn't work.

Thanks for sharing your methods nevertheless.
[Captivate Android Development] Frodo56:
I had to go through this earlier this week. I for lucky and found a backup on my phone from when I rooted it. I was able to Mount the file system as r/w and copy the folder back to the root using EFS File Explorer and after a reboot the phone was detecting my original/correct imei again.
[Captivate Android Development] TotallydubbedHD:
happy days for you dude!
[Captivate Android Development] tallus:
Tried this method but my nv_data.bin doesn't have the line number 00188008.

Any suggestions would be appreciated.
[Captivate Android Development] Mortal Eternity:
i solved my problem today by heimdall one click... it restored my imei number :) but now my root access is all gone :(
[Captivate Android Development] Droid117:
Would this work on the Galaxy S3?Same circumstances to the OP. If so could somebody PM me? Thanks!
[Captivate Android Development] eArmin:
Please help me with generic IMEI problem, I have I9100 and I don't have any efs backup and my nv_data file is completely different. HEX files are not similar and I have something like Not Active in that address. I really get confused. :(
[Captivate Android Development] tallus:
I had the same issue, called Samsung, and they got me to ship it to The Samsung repair centre in Norfolk. (Anovo).

The tech said it was a calibration issue, And I didn't get charged.
[Captivate Android Development] aelmahmoudy:
How did you do that with heimdall ?
[Captivate Android Development] Utkarsh-ezzo:
How to edit the imei no. in nv_data.bin???
[Captivate Android Development] G-Man.:
Try reading the first post in this thread... or using search. Your question has been answered a million times already...
[Captivate Android Development] murph187:
Can confirm that flashing to older firmware (2.3.3) fixed imei number. Backed up from there and am flashing newer Rom

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] kinggame992000:
Are u telling us that u flash back to stock 2.3 and the imei fix?.. maybe I should give it a try
[Captivate Android Development] rahimali:
@OP, could this method be used on other phones as well? I've got a GNex with a lost IMEI problem that I've mentioned here

Thanks a lot!
[Captivate Android Development] gtasmodder:
its wont write the right numbers it keep going back to where it started HELP
[Captivate Android Development] bames:
unlikely. Make sure you select to show hidden folders/files.
[Captivate Android Development] bames:
Come again?
[Captivate Android Development] KALI2000:
Not work. As how I can get my real imei?
[Captivate Android Development] bames:
reflash to stock 2.1

root phone and try the fix.

if it works flash back to rom of your choice (mine has stayed fixed when reflashing various roms---axura, epsyl, assonance, cognition, and chronos)
[Captivate Android Development] DumIam:
Probably a dumb question...

I did back up the afore-mentioned files, so in theory I just need to rename the back-up and copy over the incorrect files? Had no issues until I flashed Darky's Rom 6.02 lol.
[Captivate Android Development] bames:
as long as you have your originals that have correct product codes you should just need to copy them back to the efs folder and overwrite the bad ones.
[Captivate Android Development] rwj5279955:
Confirmed this works, granted my IMEI was still correct, but i updated to jh7 using Kies.

The only thing I did different was delete the corrupt nv_data.bin file because I was using Super Manager which kept giving me not enough space and not writing over the file.

Thanks for this.
[Captivate Android Development] bames:
no problem glad it could help...

i encountered this problem sometime ago and really had to dig.

my hope was this might save someone else some time and headache.
[Captivate Android Development] rwj5279955:
I don't want to clog up your thread, but man I spent a whole week after work trying the various fixes. On one try, I couldn't get inside the efs folder no matter what file manager I used. Root access or not.

I ended up flashing to Auxura, flashing back to stock using ODIN,and hoped the files rewrote from the up and then downgrade. I guess if ODIN doesn't rewrite upon flashing, then no matter how many times you flash stock it won't work.

The upgrade, then downgrage worked first try.
[Captivate Android Development] ~Reaper~:
if i may ask what are the correct product code and imei numbers
[Captivate Android Development] bames:
SGH-I897ZKAATT = product code

your IMEI is specific to your phone your need to look at the label under your battery to find the original IMEI.
[Captivate Android Development] ~Reaper~:
thanks man :)
[Captivate Android Development] bames:
damn typos in the dark...i need a backlit keboard

I897ZKAATT
[Captivate Android Development] quy:
I tried your method and another pulling the nv files and editing via hex workshop. Every time it is saved to the phone, the nv_data file reads (after reboot):

REV__.............Not Active......................................................................................................................................................................................................................00000000000...

as the product code.

I have restored to stock using one click odin and 3 btn fix odin. I am at a loss. thanks in advance for any help.
[Captivate Android Development] rwj5279955:
After multiple tries with three different methods, my data file finally saved after I reflashed Auxura, and then back to stock.

It's not my opinion, because I don't know for sure, but if flashing stock after you prduct code gets messed up doesn't re-write it automatically, try flashing foward, then backward then try it again.

This is the only thing that worked for me.
[Captivate Android Development] ~Reaper~:
ok another ? where do you find the product code ?
[Captivate Android Development] rwj5279955:
Install sgs tool box from the market.

You have to be rooted to check product code option.
[Captivate Android Development] ~Reaper~:
got it thanks

i am running perception 8

here is what it says

product code in nv_data.bin I897ZKAATT

product code in backup .nv_data.bak I897ZKATMB

looks good to me!!!

do i need to back anything up for the next time i flash?
[Captivate Android Development] bames:
if you delete the bak that has the tmb prod code

and reboot it should generate a new bak file with the proper att code.

Try doing that and once your nv_data.bak is correct as well make a backup of the entire EFS folder if you hadn't previous done so.
[Captivate Android Development] Carsus:
Would it be safe to say that the product code is correct if you flashed back to stock and were successfully able to upgrade to ucjh7 through mini kies? I have also verified that my imei code is correct. I have not had to manually change any if these files
[Captivate Android Development] bames:
If you connected via kies your product code should be fine. That was when i first discovered my problem (after flashing stock and trying to connect to kies for jh7).

But it is easy to check...just download SGS TOOLS or SGS TOOLBOX free from market and both have options that will display the product codes from your nv_data files.

When you use SGS TOOLBOX to check your product code you will also generate backups of all 4 nv_data files in a folder on your internal sd that is named PRODUCTCODECHECK. If you had the proper codes you will have successfully generated healthy backups of these files that could be saved elsewhere.

The files will be located in a folder withing:

/sdcard/productcodecheck
[Captivate Android Development] Carsus:
Strange, I checked my product code and it shows SEG-I897ZKAATT. I wonder how the update worked with the code being different.
[Captivate Android Development] bames:
weird thats the first i have heard of the SGH portion being incorrect.

maybe kies is only looking at everything the after the -
[Captivate Android Development] pmd5700:
Thanks for this info! Just did it and it worked perfectly. I comment. I downloaded "Terminal Emulator" from the market and it FC'd every time I opened it. I then downloaded "Android Terminal Emulator" and it worked perfectly.

Thanks!
[Captivate Android Development] bames:
sorry forgot about that...ran into that at first as well....i should have specified to download the version with the higher Star rating (they use to both just be listed as Terminal Emulator)
[Captivate Android Development] ~Reaper~:
ok i did that and rebooted now it shows

no backup.nv_data found
[Captivate Android Development] bames:
easy enough fix...

copy the nv_data.bin to sdcard

rename the copy as .nv_data.bak and move back to efs and you should be set.
[Captivate Android Development] ~Reaper~:
thanks!!!!!!:D
[Captivate Android Development] rwj5279955:
I'm telling you, mine did the same thing

I cursed in three differnent languages until almost a week later while doing some of my best thinking in the bathroom decided to see if they would rebuild without issue by flashing foward and then backward.

It worked.

I think there are really only one set of proper instructions, and when you get frustrated you skup a step or two without noticing. I know I tried every fix on the forum and this was the one that worked for me.

Good luck.
[Captivate Android Development] ~Reaper~:
I am just glad the numbers seem correct
[Captivate Android Development] Carsus:
Well I did a combination of this thread and the one involving the pc and adb. For whatever reason, I could not get the script from the other thread to copy over the right files. I ended up using super manager to delete the bad files and move the right one. Now my code is 100% correct. Thanks so much for this very valuable information.
[Captivate Android Development] novajustin:
worked for me!
[Captivate Android Development] dagnus:
this worked marvelously. btw: to anyone trying to do this off a custom rom, read the OP and flash to stock first. if you dont, lines that you have to edit in the hexeditor dont even exist oO. lol

but yeah. awesome!! thanks for this.
[Captivate Android Development] bames:
no problem...glad it worked.
[Captivate Android Development] rwj5279955:
Related question.

After correcting product code, will this allow OTA updates from AT&T?

Just to see what would happen, I tried looking for updates with my phone and it failed about half way through.

But Kies updated no problem.

Not that it matters anyway, there are too many better ROM's on here.
[Captivate Android Development] novajustin:
i've got a question, when i check my product code with sgs toolbox it shows the current code att back in the backup it shows tmb. i'm assuming its all good?
[Captivate Android Development] Savok:
Delete the bak and reboot and both should then be based on ATT.
[Captivate Android Development] LightningGA:
Got it to work...thanks!
[Captivate Android Development] dizx:
I saw a post earlier where you could copy your current nv_data.bin file and rename it with the".bak", so that both will have the correct product code.
[Captivate Android Development] bames:
correct.

one easy way is copy it to another location and save it as .nv_data.bak

the other method is that if you used SGS Toolbox to check the product code after the fix and had the correct code in .bin but no backup file. This process actually creates a folder on your internal /sdcard/productcode. In that folder it will create another folder containing a copy of your nv_data.bin file. You can goto that folder and rename is as stated above and just move it back to efs.
[Captivate Android Development] GRACO:
Hello there... this procedure WONT fix the 004999010640000 IMEI problem? ... can someone confirm this...

best regards.
[Captivate Android Development] bames:
it did for me without original backups of the files. you need to be in stock.