yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tbong777:
I don't have an EFS folder and a search in Root explorer finds no nv_data.bin.

Apparently I flashed too many ROMS...lol
[Captivate Android Development] KALI2000:
So ... As I can get my imei?
[Captivate Android Development] alphadog00:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.

EDIT - apparently my statement is incorrect in regards to the captivate. I had been researching fixing my unlock that got relocked and many on the Vibrant forums have the generic IMEI with no way back. As of Jan-3-2011 - bames testing shows that changing the product code, does indeed fix the IMEI - I have to assume that the encrypted IMEI in the nv_data.bin is tied to the product code (maybe a pad or salt) and the phone can't read the IMEI if the product code changes.

Still, the best solution, before any modding, is to back up nv_data.bin.
[Captivate Android Development] bames:
from my own experience you are either mistaken or my result was an anomoly.

I had NEVER backed up my efs (had never used root explorer and didn't know the folder was even there prior to researching a fix) folder prior to having my imei, product code, and nv_data files messed up. (Once it was discovered and started researching a fix i used hex editors to view my nv_data files and both the original and BAK copies were messed up).

I ran the fixes and in fact my original IMEI and product codes were restored and in fact have remained in tact for each of the 4 or 5 times i have flashed new 2.2 roms after completing the fix. Right now i am running Chronos and still have my original IMEI (not a generic).

Once i saw the fix worked and i had healthy proper nv_data files the first thing i did was back up the entire efs folder in multiple places.
[Captivate Android Development] NikAmi:
Personally, I would backup the efs folder, flash to stock, delete the nv_data files, and let the phone rebuild them on reboot. That would probably get you a better file to work with than what you have currently.
[Captivate Android Development] quadzilla500:
I deleted the efs folder itself - next I rebooted in download mode - then I used ODIN One Click Restore - when the phone booted up it still had the same 004999....IMEI :(
[Captivate Android Development] brendel:
I have read that as well. I have used my Captivate with another SIM in Taiwan and didn't have any problems with it. Somebody else reported they couldn't use SIMs in India since their networks there doesn't allow generic IMEIs.
[Captivate Android Development] quadzilla500:
I would like to know what is creating the IMEI or where it's being pulled from.

Like I said above, I deleted the entire efs folder and everything in it.

After flashing to stock and rebooting the old IMEI still shows up. (see post 182)
[Captivate Android Development] opcow:
Maybe a serial EEPROM in the modem.
[Captivate Android Development] jonski89:
Guys, i did everything in the OP... got the product code to come up on SGS tools... but i have question though... i have a rogers captivate... I896... as per this thread, the product code will be I897ATT... would someone post an original NV_data.bin from rogers i896? i just want to check what product code i should have.

so far, after everything i did, i still get the generic IMEI.. 00XXXX....... but my phone is working with the network... (from the Philippines) but i would really like to get back my original IMEI... please help guys... i already edited .IMEI file in efs folder with the original IMEI i have but it still gives me the 000XXXXXXXX

Help pls....

Thanks.
[Captivate Android Development] bubba9004:
Does anyone know how to keep the SV part of the IMEI to stay the same. It changes every time I flash a different Rom, Kernal, or Modem and I really need it to stay the same for a few of the apps I'm running.

It doesn't matter if I keep reinstalling my old nv_data.bin, the SV part still stays the same as whatever it got changed to with the flash.
[Captivate Android Development] bames:
i dont have an original rogers nv_data file but i can tell you that the rogers captivate product code = SGH-I896ZKARWC
[Captivate Android Development] jonski89:
This is good news... but i don't know how to fix the nv data file with ascii.... :(

i tried to restore my nv_data file as well using this method...Repair

but still i get the generic IMEI...
[Captivate Android Development] bames:
did you get the correct product code back?
[Captivate Android Development] dwillMUFC:
Thankyou so much for this :)

With mine since about the 2nd month after i had it and flashed JPC my IMEI changed but since yesterday it didn't have any effect, but yesterday I think Tmobile may have seen it as though I stole it :/ ( I have the receipt if anyone doubts me ;) ) but they disabled my phone, i could get an internet connection but calling and messaging were not working and when people rang me it said that my phone had been disconnected. All hope was lost and was ready to send it back to CEX for warranty repair. But tried this method and although my IMEI was the same silly 004*********** number I now have a fully working phone with texts and calls. Thanks again

Ps - I have an international Galaxy s Gt I 9000 - didnt read this was for captivate !

Maybe i should read before but hey Im bot complaining :D

Dan
[Captivate Android Development] punixx:
Hi, I have a i5800, my nv_data.bin is corrupt, the Hex editor dont find line 0188008

I Haven't a backup...

Someone could send me a clean i5800 nv_data.bin?

thanks
[Captivate Android Development] bames:
glad it helped this was a nightmare for me the first time it happened to me.
[Captivate Android Development] bames:
are you using the android app hex editor for your phone?
[Captivate Android Development] punixx:
Yes I use HexEditor, If I jump to address 0188008 the message is "file has only 524288 byte"
[Captivate Android Development] flapane:
Same thing on i5700, the file ends at line 0007fff0 and is 512KB, so they're probably using the same kind of nv_data encoding (after all, i5700 and i5800 are almost the same phone).

Any hints on these two phones, please? :)

bames if it helps, I can send you my corrupted nv_data, and a firend's good nv_data from another i5700. Would you be so kind to help us?
[Captivate Android Development] godpancho:
someone please help me.get at&t back

i was able to mod the .bin file was able to reboot with terminal emulator. but cant get at&t to connect even though it has the correct at&t info in the efs folder.. i have imput the generic codes but nothing happend after reboot. is there another way to get at&T back on. i tried the steps over and over. after the reboot is the process done. or are there more steps. becuase when i reboot with terminal emulator nothing change even though in the .bin in the efs folder has the correct

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

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

00188020|41|41|54|54|00|00|00|00|AATT....

as stated in this forum

after reboot efs file shows

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

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

00188020|41|41|54|54|00|00|00|00|AATT....

but i still dont get a imei number or able to connect to at&t.

if anybody can help. please do. on 10 hours now
[Captivate Android Development] D-FUSE:
If you don't have any hardware damage and you have had you phone for less then a year I would send it to Samsung for a reflash. That will fix you number.to tell you the truth that was the only way I got my fixed
[Captivate Android Development] d34thp1ng:
So I had a problem after running many different roms, where my imei and product code were wrong, I flashed back to stock 2.1, and tried to run this but my results were a bit different.

I was trying to do the upgrade with Kies Mini, and kept getting unregistered device, I followed your directions but deviated a bit after seeing your OP showing the following table.

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....

I edited my nv_data to match and now I am able to use Kies to upgrade. I also found my imei backed up from before I started flashing in the first place. Once the upgrade is complete I will see if I can just copy it directly over and see if it will correct it. Thanks for your post I was able to get the upgrade to work after never having tried the official 2.2. That being said I am sure it will only be on the phone for a day or 2 and I will be back to a custom rom LOL!!!
[Captivate Android Development] 340865669:
all lines stated in this post on my phone is incorrect, including 00188018...interesting

REF:Original text on the right

_.......

......No

t Active

........

not active...interesting

after correction, product code works and IMEI code is...

004999010640000

too bad it is not working for me
[Captivate Android Development] xpeppyx:
This did fix my product But i still have a generic IMEI number, oh well. thanks for the guide man. 1 fix is still better than no fix.
[Captivate Android Development] xpeppyx:
Mine siad the same thing in the lines.
[Captivate Android Development] :
I love you!
[Captivate Android Development] albertobom:
In my nav file (galaxy s GT-I9000) this file below is in blank how to setup it?

00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
[Captivate Android Development] bames:
can you clarify?
[Captivate Android Development] xThe Enforcer:
Thanks a bunch.
[Captivate Android Development] welchertc:
Ok, so I don't have a credit card hooked up to my google account, so I can't use Root Explorer. Using Android mate however, nothing shows up in my efs folder. please help?

***edit***

Hooked up a credit card and root explorer did the trick.
[Captivate Android Development] bames:
i believe there is a setting in android mate to "show hidden" files or something to that effect that you may need to select. Check through the AndroidMate settings.
[Captivate Android Development] montrealguy:
What he means is that he has a I9000 (not a Captivate). I have a I9000M.

What do I put for this line:

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

I see that at the end it says i897Z. What numbers and letters do I put for an I9000M???
[Captivate Android Development] bames:
there are two I9000 M's

Bell = GT-I9000HKABMC

SaskTe) = GT-I9000HKABWA

Does anyone have the same model with a healthy NV_Date.bin? If so can you use hex editor to open and post a screen of lines 0188000-0188020?
[Captivate Android Development] kobz1973:
Genius ... all i can say is pure genius ...

I have just followed this step by step and worked on a Galaxy S UK version running CM7 ...
[Captivate Android Development] bames:
thanks

glad it helped
[Captivate Android Development] Barsky:
Thanks for the fix. Took me a couple tries to get it right, and when I did have the right MIEI and product code, I initially had no ATT service. But, I hooked up to kies mini and it finally recognized my phone. Did the update which brought me to froyo and ATT service.
[Captivate Android Development] dude_uuk:
Hi Guys, will this worked for any SGS series? I have tmobile's SGS4G right now and seeing that the IMEI contains all weird characters and no numbers as to usual IMEI numbers. Thanks in advance...
[Captivate Android Development] bames:
should work at least for product code. Just need to know your edits for your specific devices product code.
[Captivate Android Development] sifulee:
Thanks bames this worked like a charm! :D
[Captivate Android Development] bames:
glad it helped
[Captivate Android Development] georgem106:
product code ok but...

I was able to fix the product code but what do I do to fix my IMEI to match my phone? I have an at&t captivate phone.
[Captivate Android Development] bames:
were you on stock or a custom when you tried the fix?
[Captivate Android Development] The_Zodiac:
alright so long story short i had no idea i had to back this up, ive flashed a lot of roms on my captivate.

flashed it stock jfk and tried to use mini kies to update to froyo, its saying device not recognized

but i dont think my imei has been changed?

any way to fix it now?
[Captivate Android Development] georgem106:
I flashed back to stock and it gave me some generic IMEI.

Any suggestions?
[Captivate Android Development] ashvincj:
My Samsung galaxy s 4g is also showing weird characters for IMEI.. :( the phone was unlocked using NSPRO app i think.. what should i do?? please help!
[Captivate Android Development] khoanguyen2512:
After flashing some Modems (BUJS1, BVJJW2) i lost my IMEI...it changed to 004999... and my sdcard has a file named nv_data.bak, size 20mb. I flash my phone to Stock 2.3.3 but i can't restore my IMEI.

So, can i try this method?
[Captivate Android Development] khoanguyen2512:
I try this fix on custom rom (Con 6.1) which i have problem. And now i restored Product code,but my IMEI still 00499901064000...
[Captivate Android Development] lildoggs:
Nice tutorial.
[Captivate Android Development] shaheerali:
I found that my .nv_data.bak contain the same characters as shown in first page of this thread,

ie,

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....

I renamed it as nv_data.bin & put it into my efs folder (replaced original/corrupted one). Then i deleted .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. But my IMEI still Generic one (00499901064000)..:(

All these steps were done on Stock 2.1 (JF6)

Any suggestions?:confused:
[Captivate Android Development] jaimebmg:
Unfortunately some of us had the same problem, if this process don't work the only way I can found is by restoring using a box, sad to said but so far there is no an ultimate solution to the problem
[Captivate Android Development] RainesX:
If i have a correct IMEI is it ok to just copy the nv.data.bin and the nv.data.md5.bin.

So that if they get messed up i only have to paste back?

Or do i have to edit?

Sorry for not being being a bit stupid but this guide is only for messed up IMEI's right? So i should be able to only make a backup?
[Captivate Android Development] mahatma:
Tutorial is grate but it kind of not working for me but I do not know if my problem is the same. My IMEI is unknown and baseband is unknown. My EFS folder is Read Only and I cannot change it?
[Captivate Android Development] :
I open up my nv_data.bin in hex editor and it says: "this file has 0 bytes", and shows nothing in the editor just 00s
[Captivate Android Development] shaheerali:
First root your device...
[Captivate Android Development] :
I did. I have used this before and it works, but now (got the file to open) after I edit the hexes they won't stay after I save it.
[Captivate Android Development] toori88:
work on an sgs2

Hi,

Could anyone confirm is this procedure will work on the european galaxy s2.

Many Thanks
[Captivate Android Development] RainesX:
I dont know if this works or not.

But a say that if you have a healthy efs do a backup of it.

Im using nitrality to do a backup of my efs folder.

Also i have the backup on thre more locations just to be sure ^^

if you have broken your efs i wish you good luck :)
[Captivate Android Development] toori88:
I may have, O2 are asking for £45 to fix the problem cause the phone is no longer covered by warranty, I am going to try this method if this doesn't work, O2 will be getting some money off me :(
[Captivate Android Development] RainesX:
If you anage to fix it in one way or another, dont forget to back efs up.
[Captivate Android Development] SMN™:
is this work for nexus s?!
[Captivate Android Development] vako86:
It did not work for me, IMEI is the same Generic :( I tried 2 times. My phone is rooted. I followed the steps.

Mine is SG2.

Any ideas?
[Captivate Android Development] owlkind:
Thanks for an useful tool
[Captivate Android Development] LightsCameraAction:
hi, will this work for a nexus s? somehow i managed to wipe the IMEI number and i didn't save the EFS folder,,,, i'm not sure what to do any suggestions?
[Captivate Android Development] bames:
haven't tried it with nexus s.

did you try the fix again deleting the proper nv_data files and making sure your product code was correct in your nv_data.bin? Then reboot?
[Captivate Android Development] iamtheculprit2:
You sir, have earned my eternal gratitude! I kept getting unregistered error until I did this, and it worked right after that! Thank you!
[Captivate Android Development] micheleovernet:
I guys,

when i try to do this guide, i have no problems or error,

but after reboot the imei is still the same as before!

How is that possible?

I'm running original 2.3.3 vodafone rom, with root

please help me,

thank you!
[Captivate Android Development] tennyleaz:
Thank for the method.

But after doing everything, I found my IMEI is still 0049990........

Product code: SGt ActiveAATT

I've check nv_data.bin in /efs, the 3 lines are exactly the same

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

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

00188020|41|41|54|54|00|00|00|00|AATT....

I'm on stock JF6 2.1, can anyone help please?
[Captivate Android Development] lyrad12:
why is my Product code is SGH-I897ZKZKOR then my IMEI is perfectly matched the numbers under the battery? is this ok? >.<
[Captivate Android Development] krish_nank:
I want to try on my huawei ideos x5 but unable to find EFs folder...but i got efs log.txt and NV log.txt under data/hwvefs/
[Captivate Android Development] pupochek:
I have 2 Captivates. One has a good screen but a bad main board (won't read a SIM). The other one has a good main board, but a bad screen. I want to make one good one, but I want IMEI of the main board to match what the case is saying. What's the best way of doing this?
[Captivate Android Development] lilmo22:
forget what everyone says!!! it worked!!!

i was going mad because my network was blocked on the doggy imei and it voided my warranty... i came across tihs and it saved my life!!! thank you!!
[Captivate Android Development] dinjo_jo:
Is going back to stock mandatory ?
[Captivate Android Development] jackdowsan:
Would this work on a Samsung Galaxy S 4g?
[Captivate Android Development] UkHardcore23:
Hi, im in some need of some serious help, A brief update on what i have been doing...

Last year i rooted the phone and didnt back up the files so my IMEI number changed to 004999010640000 but phone worked fine until 2 days ago when T-Mobile blocked the phone due to having a different IMEI.

So i was following these instructions (i was running 2.2) and all went well, i had changed all the values then deleted all the BAK files like the video said, phone restarted but i was still unable to make calls however i noticed i missed out this part...

All my values in the Hexedit had changed to 00, so i decided to start all over as i had not known i missed the last bit out. However today when restarting nothing that i tried last night seemed to be working ie: Phone wouldnt root using Super One Click, tried a few different things and the phone would no longer turn on and would just vibrate.

Next step i have flashed Gingerbread on it and phone is working again.....but now im completely baffled as the phone wont root either using One Click or Galaxy S click root and now i feel im just going round in circles not know what im doing....

HELP PLEASE!
[Captivate Android Development] kayotiic:
Will this work on I9000
[Captivate Android Development] boborone:
No reason why not

sent from my ppc through win97 servers bypassing exchange security
[Captivate Android Development] CoBfan1987:
When I try to skip to a line I always get the error

"File has only 262144 bytes"

Any reason or solution for this?
[Captivate Android Development] CompuTechnoPro™:
HELP !!!

I only have cryptprop_es in the efs folder & nothing else !!!

What to do now ???. PLEASE HELP...:confused:
[Captivate Android Development] bahaa89:
Does this works with Galaxy s 2 ?
[Captivate Android Development] kcokla:
would also like to know if this works on galay nexus
[Captivate Android Development] mattsternc:
This one didn't work for me. I believe I had corrupted files to start with after flashing so many ROMs in the last year or so.

Curious question though. Does the CSC need to be valid in order for this to work? If so, how can I fix it? Mine shows unknown, no matter what ROM is on it now. :confused:

Please advise.
[Captivate Android Development] Red_81:
Try this and see what happens:

Type *#272*imei# (replace imei with your actual IMEI number, the 0049 one)

I get only one option for ATT. What do you get?
[Captivate Android Development] mattsternc:
I get no options actually. I see a blank entry window and then a blank dialog underneath, with a radio button out to the right side. :confused:

Sounds like I'm pretty well hosed, eh?
[Captivate Android Development] Red_81:
I think you just need to flash your csc through Odin. I'm not sure where you get it from though.
[Captivate Android Development] mattsternc:
I was wondering about that. They seem to be tied with the ROM somehow, at least in versioning. I don't recall that I've seen a KK4 CSC file anywhere in my travels through the various ROMs that use that as a base.

Any ideas?
[Captivate Android Development] Red_81:
You sir are in luck. Here is the CSC folder pulled from a KK4 full wipe rom. I can't guarantee this will work, but try to replace your /system/csc with this folder. I would double-check permissions too. Mine are listed as rwxr-xr-x in root explorer (owner=root and group=root).

Good luck.
[Captivate Android Development] mattsternc:
Interesting! I actually don't have a CSC directory on my phone at all. I'll pull these files and put them where they should be. From what I gather, if I go to do a reset of CSC, then a wipe is done on the phone. I guess I could make sure my file edits are still in place before I do the switch and see if that fix might work then. I guess we'll see, but I'm not flashing back to stock to do it either hehehehe. No time for that now.

Thanks for the files and I'll post back here with results!

Matt

P.S. - What are these CSC files anyway?
[Captivate Android Development] Red_81:
Short answer.... I don't know.

You might just want to flash back to stock with a factory wipe and make sure the folder gets recreated. Then upgrade back to whatever ROM you like. It might save you from more headaches down the line.
[Captivate Android Development] adrenelized:
Worked great for me - thank you for posting this!!!
[Captivate Android Development] micheleovernet:
Guys i'm trying to use this wiki with some ics version, but everytime i can't overwrite the nv_data file, even with rootexplorer, because "there is no free space."

someone can help me?

Something strange, i used this wiki with darky's rom and works fine, but with ics i haven't an imei, it's clear, isn't strange?
[Captivate Android Development] Red_81:
I tried everything in the post (and a few others) but nothing could bring back my IMEI. I had destroyed too many of the files attempting to fix it. I decided to send it off to Josh at mobiletechvideos to have it repaired. It took about 1 week and now everything is back to normal.

If you want to use his service, just PM him. He is a member here on XDA.

connexion2005
[Captivate Android Development] DMgals:
I got my original IMEI back on Galaxy S (after I tried ICS custom rom) with this procedure:

1. Delete all 2 nv_* files in "etc" folder

2. Reboot into download mode

3. Flash back to gingerbread 2.3 XXJVU stock or possibly back to eclair 2.1

4. To me it worked and I got my original IMEI now restored.

5. I am not kidding that's how I got it really fix from my 47000000...XX funny looking IMEI.

You can try this procedure and hope it works for you like it worked for me.
[Captivate Android Development] nasif619:
Really thanks man. worked for me.
[Captivate Android Development] chochweet:
there is no efs folder, how to get it back