IMEI corruprt(fake). nv_data files deleted. HELP! - Vibrant Q&A, Help & Troubleshooting

Hey,
So i got this vibrant off craigslist. I rooted it, installed root explorer and checked the efs folder and it had the nv_data files but the IMEI was 004999010640000. Now i know my nv_data file isnt the original one cuz i tried the repair_nv_data fix with absolutely no luck. No matter what i still get this fake IMEI. Completely different from the one on the back of my phone.
Is there any way to restore my original nv_data files or manually edit the IMEI number? I flash back to stock firmware using ODIN a=but it resulted in the exact same thing. My IMEI was this 004999010640000 number.
Really need help

---

I have something you might be able to try (but want to you to look at something first).
I encountered a problem after an i9000 rom flash where something changed my product code in the nv_data file (captivate model). The generic imei was nothing new as i had often seen this using custom roms but a flash to stock always restored my original imei until the time my nv_data files were corrupted and showing the wrong product code.
Download SGS-Toolbox and check your product code....report results back here.

---

bames said:
I have something you might be able to try (but want to you to look at something first).
I encountered a problem after an i9000 rom flash where something changed my product code in the nv_data file (captivate model). The generic imei was nothing new as i had often seen this using custom roms but a flash to stock always restored my original imei until the time my nv_data files were corrupted and showing the wrong product code.
Download SGS-Toolbox and check your product code....report results back here.
Click to expand...
Click to collapse
Hey thanks a lot for the reply. Uh yea just did that and i got this:
product code in nv_data.bin: i9000hkdkor. Lol thats totally wrong isnt it?

---

darktranquility18 said:
Hey thanks a lot for the reply. Uh yea just did that and i got this:
product code in nv_data.bin: i9000hkdkor. Lol thats totally wrong isnt it?
Click to expand...
Click to collapse
totally wrong.
give me some time as my fix was for the captivate and its codes......need to update/convert the changes to be applicable to your vibrant. Watch here and i will post a fix to try shortly.
In the meantime. Please do me a favor download Hex Editor Free from the market. Go ahead and make backups to external SD Card or if you don't have one create a temp efs backup folder on /sdcard (internal sd) (Backups of all nv_data files in your efs folder) even if they are wrong.
1. Use hex editor to open the backup of the nv_data.bin
2. Use the capacitive menu button on your phone and it will bring up your options....choose JUMP TO
3. enter 0188008 which takes you to line 188008 and tell me what the text to the far right reads (should read something like .4....K )
3. Scroll down to 00188010 and report text @ right
4. Scroll down to 00188018 and report text @ right
4. finally scroll down to line 188020 and also tell me what text is to the far right (i want to make sure product codes on the vibrant are located on same lines as the captivate)

---

bames said:
totally wrong.
give me some time as my fix was for the captivate and its codes......need to update/convert the changes to be applicable to your vibrant. Watch here and i will post a fix to try shortly.
In the meantime. Please do me a favor download Hex Editor Free from the market. Go ahead and make backups to external SD Card or if you don't have one create a temp efs backup folder on /sdcard (internal sd) (Backups of all nv_data files in your efs folder) even if they are wrong.
1. Use hex editor to open the backup of the nv_data.bin
2. Use the capacitive menu button on your phone and it will bring up your options....choose JUMP TO
3. enter 0188008 which takes you to line 188008 and tell me what the text to the far right reads (should read something like .4....K )
3. Scroll down to 00188010 and report text @ right
4. Scroll down to 00188018 and report text @ right
4. finally scroll down to line 188020 and also tell me what text is to the far right (i want to make sure product codes on the vibrant are located on same lines as the captivate)
Click to expand...
Click to collapse
Yo really appreciate the help man. Aite
00188008: .800...K
00188010: OR....GT
00188018: -I9000HK
00188020: DKOR....

---

darktranquility18 said:
Yo really appreciate the help man. Aite
00188008: .800...K
00188010: OR....GT
00188018: -I9000HK
00188020: DKOR....
Click to expand...
Click to collapse
thanks just a little bit more info before i convert my fix.
Go back to those same lines in hex editor
There will 8 block of data between the line # and the text at the right that you reposted. Please post the #'s/letters for each corresponding block so i can ensure that i convert properly.
00188008 | | | | | | | | | .800...K
00188010 | | | | | | | | | OR....GT
00188018 | | | | | | | | | -I9000HK
00188020 | | | | | | | | | DKOR....
I will need the 2 digit/numeral codes in each of the boxes for the line above.
thanks

---

bames said:
thanks just a little bit more info before i convert my fix.
Go back to those same lines in hex editor
There will 8 block of data between the line # and the text at the right that you reposted. Please post the #'s/letters for each corresponding block so i can ensure that i convert properly.
00188008 | | | | | | | | | .800...K
00188010 | | | | | | | | | OR....GT
00188018 | | | | | | | | | -I9000HK
00188020 | | | | | | | | | DKOR....
I will need the 2 digit/numeral codes in each of the boxes for the line above.
thanks
Click to expand...
Click to collapse
sorry...i know thats a pain in the butt but once i have that data i think i can convert the fix to work for you

---

bames said:
sorry...i know thats a pain in the butt but once i have that data i think i can convert the fix to work for you
Click to expand...
Click to collapse
disregard last post...i got the code from a health nv_data file so you just need to compare the data from those lines to your own and make corrections in Android Hex Editor.
I sent you detailed instructions in a PM. Please test it....if it works i will repost my ported fix to the general section.
let me know if something is unclear.
PS - Even in a custom rom this should correct your product code (tested in 2.2 code).
I was in stock 2.1 when i crafted and executed this fix the first time so i don't know if it will restore your imei in custom rom environment as when i had an invalid product code in 2.2 i still had right imei.

---

any resolution to this??? i unlocked my vibrant in the USA and used it with both at&t and tmobile, came to india and i can't use indian sim cards...i took it to a local unlocking wiz, and he told me that my phone's imei has been wiped and according to indian law, no network will register to a phone that has a wiped imei...SO NOW I EITHER HAVE TO figure this out, or buy a new phone for 2 weeks
ANY HELP?

---

ppriyank said:
any resolution to this??? i unlocked my vibrant in the USA and used it with both at&t and tmobile, came to india and i can't use indian sim cards...i took it to a local unlocking wiz, and he told me that my phone's imei has been wiped and according to indian law, no network will register to a phone that has a wiped imei...SO NOW I EITHER HAVE TO figure this out, or buy a new phone for 2 weeks
ANY HELP?
Click to expand...
Click to collapse
Oh for real? So it is the imei? I have 2 vibrants. Used both in the US with AT&T. I came back to india in november and my vibrant worked perfectly. It has the right imei. When i came back in decemeber with the other phone, unlocked working perfectly in the US, it just said no service here. If what you said was true then the only solution would be to repair the imei somehow. Ive tried everything and no luck :S

---

bames said:
I sent you detailed instructions in a PM. Please test it....if it works i will repost my ported fix to the general section.
let me know if something is unclear.
Click to expand...
Click to collapse
Hi, Bames!
I have the same issue with IMEI of my phone. Now it shows 004999010640000.
Can you help to restore it to the original which must be equal to the number in the back of my phone?
Thanks.

---

Id like to know if this was ever resolved and if the correct IMEI had been restored or not? Thank you

---

bumping because I want to know the reultion to this as well

---

Hey I got the same problem~!!
Wanna know the resolution, Please~!!

---

Hasnt been fixed on my phone yet. But try doing what bames did. Maybe itll work for you

---

i thought the imei number for your phone is located under the battery?

---

Original post by bames. Just posting it again to make everything clear.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Android Terminal Emulator (make sure to download the one with higher star rating)
D. Hex Editor
E. SGS Toolbox
__________________________________________________ _______________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. To the left you will see line #’s followed by 8 blocks of hex code data that will be 2#’s, 2 letters, or a combination of #’s letters (examples | ff | 54| 00| 4b|). Well will need to edit code in 3-4 lines of the code. Once you have used the jump to option you will see all the lines that need edited on the screen starting with 00188008 (the others will be 00188010, 00188018, 00188020)
9. Compare that data in each of your corresponding lines you see below. Where your numbers are different correct them with the corresponding #’s below. (click corresponding box and it brings up the contained # simply replace it with correct # from chart below). I put the parts you will be comparing and correcting in bold to make viewing easier.
00188008 | 2e | 33 | 00 | 00 | 00 | 00 | ff | 54 |
00188010 |4d | 42 | 00 | 00 | 00 | 00 | 53 |47 |
00188018 |48 | 2d | 54 | 39 | 35 | 39 | 5a | 4b |
00188020 |42 | 54 | 4d | 42 | 00 | 00 | 00 | 00 |
10. Save the file and move it back to efs using root explorer copying over the original.
11. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
12. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
(If you have an issue in Android Terminal Emulator where the keyboard doesn’t come back up after entering su command simply hit the capacitive menu button and you will have the open to re-open the keyboar)
13. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
Using hex editor, check these again:
00188000 - ff ff ff ff 52 45 56 30 - . . . . R E V 0
00188008 - 2e 33 00 00 00 00 ff 54 - . 3 . . . . . T
00188010 - 4d 42 00 00 00 00 53 47 - M B . . . . S G
00188018 - 48 2d 54 39 35 39 5a 4b H - T 9 5 9 Z K
00188020 - 42 54 4d 42 00 00 00 00 - B T M B . . . .
00188028 - 00 00 01 50 02 4e 03 4e - . . . P . N . N
Also, the imei cant be fixed without the original nv_data files(ur efs folder). So its very unlikely that itll be fixed. Also with certain carriers in certain countries, Airtel in india for example, have banned phones from connecting to their network cuz of the wrong imei numbers. On the other hand, a phone with a wrong imei still works on a carrier like at&t.

---

DontJoinTheDarkSide said:
i thought the imei number for your phone is located under the battery?
Click to expand...
Click to collapse
The imei number of the hardware must match the imei in the nv_data.bin file located in the efs folder of the phone. If they do not match, when u go to 'about phone', you get a wrong imei like 004999010640000 which is banned by certain networks and the android market acts weird at times(doesnt download).

---

How would the imei number get changed in the 1st place?

---

edit lines 00188000-00188020
to match the screenshot