Database Users

RESTORE IMEI and Product Code w/o ADB, PC (ALL DONE ON PHONE) nv_data.bin

**VIDEO GUIDE ADDED BELOW**
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
(This should be done from stock 2.1 (JF6) but may not be required (got this to work while in phoenix 1.5 without reverting)- results may very in custom rom environments....
***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.
fyi this fix is intended specifically for persons with borked product codes and imei's due to custom rom flashes and will not address nv_data issues of carrier blocks/etc. for those who had unlocked their devices and may in fact undo your unlock.***
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
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. *Since i have good backups now on PC and external sd...i generally just edit the nv_data.bin file in place and save over the original in the efs folder.
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete all nv_data files from efs folder EXCEPT FOR YOUR NEWLY CREATED NV_DATA.BIN. (Delete the following: .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. This differs from video but i also delete any .nv_state or nv.log file present and they are recreated). FYI IF YOU ARE USING A GINGERBREAD ROM AND YOUR EFS CONTAINS .nv_core.bak and .nv_core.bak.md5 DO NOT DELETE THEM with the other .nv files.
15. (This step may not be necessary unless you lose your voice/data connection upon reboot)
Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
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....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
**NEW: VIDEO GUIDE**
SPECIAL THANKS TO CONNEXION2005 for providing the video guide below:
http://www.youtube.com/watch?v=JqLK_2I-SBM&feature=player_embedded#!
-----------------------------------------------------------------------------
*DISCLAIMER*
have already had one person post a response that this thread was misleading and stating that:
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.
Click to expand...
Click to collapse
I have seen other users make this claim as well, however, they are either mistaken or what i experienced was a complete anomoly.
I had never backed up my efs folder or nv_data files prior to them being messed up (i didn't know they were there and had never used root explorer to view them until i had to research a fix). The first thing i did was use a hex editor to look at my nv_data.bin and its bak(s) and in fact none of them were good. They all contained wrong product code.
So the process i described was conducted without any previously backed up original nv_data.bin or nv_data.bak files.
I started with:
wrong IMEI
wrong product code
totally botched nv_data files with no backup of original unmolested efs folder or nv_data files
I ended up with
Restored original IMEI
Correct Product Code
Healthy/Correct nv_data files that i immediately backed up in multiple locations.
So if you didn't back up your original untainted efs or nv_data files and this fix doesn't work to restore your original imei and product code then allow me to apologize in advance for "misleading" you and trying to assist with your problem by posting what did in fact work for me.
--------------------------------------------------------------------------------------------------------------
DONATIONS NOT REQUIRED OR EXPECTED. IF YOU FEEL THIS THREAD HAVE HELPED YOU WITH A SICKLY DEVICE OR SAVE YOU ANY HEADACHE OR TROUBLE FEEL FREE TO CONTRIBUTE:

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***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. Terminal Emulator
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. 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).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efa/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
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....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.

I think i deleted the file i wasnt supposed to... can someone post that file?

krips2003 said:
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
Click to expand...
Click to collapse
you should revert to stock to run this.
your welcome to try it with any rom you are using but i have only used it in stock jf6 as that was when i discovered the problem. I tried odin one click jf6 when i noticed both my product code and imei were wrong thinking go full stock reinstall would fix. No luck....with alot of reading i discovered one method of fixing the problem then also worked out the 2nd method that doesn't require adb or pc in case it needed to be done on the fly away from computer.

Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?

CapnPez said:
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
Click to expand...
Click to collapse
yes..thanks...duly noted and corrected

So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.

rwj5279955 said:
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
Click to expand...
Click to collapse
what are you looking @ your efs folder with? It shouldn't be empty...even if you had completely deleted your nv_data files when trying the other method there should have been other folders in /efs. You didn't cut and paste or move all the folders/files from efs (rather than copy) somewhere did you?
PS - aside from the files starting nv_ you should have two folders /efs/imei and /efs/.android

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***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. Terminal Emulator
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. 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).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
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....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.

KALI2000 said:
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
Click to expand...
Click to collapse
suspected would only work with stock. the generic id is less of an issue because i think as long as your product code isn't screwed in the nv_data files your original imei will restore upon reflash of stock.
One interesting thing and may be just luck. I had flashed all kinds of roms before and it usually changed the imei to the generic one but it was no big deal because it would restore when going back to stock (and the product code was never altered).
Since having them get messed up and doing this fix i have flashed multiple roms Axura, Assonance, Perception, Epsyl, and currently chronos and it has yet to alter my original imei in the process. Right now i am running chronos and it still has my original imei.

Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post):
http://forum.xda-developers.com/showthread.php?t=786532

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post and it contains links to both versions):
http://forum.xda-developers.com/showthread.php?t=786532

Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.

rwj5279955 said:
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
Click to expand...
Click to collapse
hope it helps. let me know your results when you get a chance.

I did a similar method, but only changed the AATT part in a hex editor and moved the file back with super manager, gave owner full chmod access, rebooted, made sure kies mini detected my device and then reflashed stock/master clear.
Now everything is back to normal.

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

So ... As I can get my imei?

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.
Sent from my MB520 using XDA App
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.

alphadog00 said:
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.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
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.

[Q] /EFS folder empty?

I own a SIM locked Tab from Bell Canada and I'm working on unlock the SIM lock. I just used Z4root get the root privilege and was about to use RootExplorer to backup the /EFS folder to a microSD card. But the RootExplorer didn't show any file under the /EFS folder. I rebooted and checked again, still nothing in the folder.
ROM version: P1000XXJID
So what's going on here? Can anyone offer some suggestions?
Thanks in advance.

Was this an out of the box new tab or used? The empty efs folder is evidence of someone trying to avoid the t-mobile redirect when using the internet.
Go to settings> about device> phone etc and see what your serial number and IMEI number are.

Thanks for you response captain.
The tab is a sealed one (it's from authorized bell retailer), but the store claimed they got a batch of tabs with phone function (could be pre-flashed to some euro rom??). Just checked the SN and IMEI, they all match to the label on the back of tab.
The baseband version is P1000XXJID, don't know if this is the one for bell canada.

Well, don't worry, I deleted everything from that folder and I am in good shape. At least you have your serial number and IMEI.
Other than a blank efs folder, is everything else ok?

Captain, everything else works in the way as they should do. But I cannot unlock the SIM lock until I modify nv_data.bin file under the /EFS folder, can I?
So under this circumstances, how can I perform the SIM unlock?

Put in a sim from another carrier and see what happens - my guess is it's already unlocked. Anytime you use another sim you have to change the apn setting. That's in settings> wireless network> mobile network settings>access point name. If you don't know the particular details (approximately 14 entries), search xda for it, or google it. Usually I get lucky and the settings are already there when I go to change them.

Captain, I entered *#7465625# and it says Network Lock is "ON". I've searched everywhere....ahh, drives me crazy...

hiroshik said:
Captain, I entered *#7465625# and it says Network Lock is "ON".
Click to expand...
Click to collapse
The proof of successful unlocking is putting in another brand sim and having the tab connect and run on the other company network, not what some setting says.

First of all, make sure that your device is rooted, after this install from the market: superuser, busybox & super manager.
Open super manager and give them root access in settings. This worked for me.
Sent from my GT-P1000 using XDA App

If your /efs folder "appear" to be empty it's because you do NOT have root privileges. The files are there you just can't see them.
You need to root your tab b4 anything else.
P_

hiroshik said:
I own a SIM locked Tab from Bell Canada and I'm working on unlock the SIM lock. I just used Z4root get the root privilege and was about to use RootExplorer to backup the /EFS folder to a microSD card. But the RootExplorer didn't show any file under the /EFS folder.
Click to expand...
Click to collapse
He already has root and installed Root Explorer.
I think you should put in another carrier's sim card and verify lock/unlock.
Cromed makes a good point. Is Superuser installed? And have you installed the latest busybox from the market?

I put in Rogers SIM card, the tab asked me for unlock code after bootup. I dismissed it and then the tab only allowed me dial emergency numbers.
I switched back to Bell SIM and using z4root to unroot and then rooted again. The root explorer still couldn't find any file under the efs folder.
P.S. I have installed both superuser and busybox from the market.

Captain, do you think it is possible that the retailer deleted the nv_data.bin file? It was quite suspicious that he mentioned of "official unlock service is available for $60". Assume they delete such file makes us no way to unlock the tab but pay for an "official service"...
And the tab comes with firmware with phone function which is supposed not available on Bell tab? Is P1000XXJID an euro firmware?

I'm sure that's what happened. I saw somewhere Roto sent someone a blank file for them to edit. Maybe search the forum. Have you flashed any rom yet? I deleted my efs folder contents and now files are in there.

Captain, I have NOT personally flashed any rom. Maybe i should re-flash the tab. Anyway, thanks for your help.

I just backed up my efs folder, then flashed Roto JMG, the full install, which wipes your sd card, and the efs folder had all the usual files and folders.
I would flash, because you don't need to be unlocked to do that.
Sent from my GT-P1000 using XDA App

The files only show up when you use a file manager with root access enabled. I had to download Super Manager (free) and give it root access in its settings and then I could see them.

hiroshik said:
I just used Z4root get the root privilege and was about to use RootExplorer to backup the /EFS folder to a microSD card. But the RootExplorer didn't show any file under the /EFS folder. I rebooted and checked again, still nothing...
Click to expand...
Click to collapse
From the op.

unlock i5700?

Can I unlock it for free?

There is a method but it is not realy useable because you loose your imei.
1) Root your phone
2) Use a root explorer of your choice and go into the efs folder
3) Make a backup of your "nv_data" file by copying it to your sd card ("sdcar" folder)
4) Delete the "nv_data" file in you efs folder.
5) Reboot.
6) Now it is unlocked but your imei is 00000000...
PS: Your phone will still work without a problem even with a zero imei. You can always go back by copying the backup file into the efs folder but then the lock will be there again.
Tested with 2.1 os.

Knuffibaer said:
There is a method but it is not realy useable because you loose your imei.
1) Root your phone
2) Use a root explorer of your choice and go into the efs folder
3) Make a backup of your "nv_data" file by copying it to your sd card ("sdcar" folder)
4) Delete the "nv_data" file in you efs folder.
5) Reboot.
6) Now it is unlocked but your imei is 00000000...
PS: Your phone will still work without a problem even with a zero imei. You can always go back by copying the backup file into the efs folder but then the lock will be there again.
Tested with 2.1 os.
Click to expand...
Click to collapse
Just wondering, will loosing your imei do any harm? I mean once we root & flash a custom Rom its not like we have any warrenty but will it ever effect the usage of the phone in anyway?

Please help...
Hey guys i need some help.. I want to unlock my i5700...
i have gone on the website www.UnlockSamsungOnline.nl
i have paid for the unlock code but something is not working
I have inputed both codes
2: Type *#7284# then choose USB > MODEM
3: Type: *#9090# then choose - 1 Uart_null_usb_diag
and nothing seems to appear... when i click dial it states "mobile network not available."
I have CM6.1 rom that i am running on the phone. Please let me know what i could do to unlock the phone.
Would i need to flash it stock in order to unlock the phone????

For everyone with a I5700 / Spica:
For a FREE onlock/root, go to forum.samdroid.net and visit their helpdesk:
http://forum.samdroid.net/f28/helpdesk-faqs-how-guides-2111/
Its the most active Spica community to date.
Just read the entire helpdesk, get educated, get involved and have fun

And to answer your question about how to unlock the spica:
http://forum.samdroid.net/f28/how-spica-i5700-sim-unlock-free-4886/

Spoetnicus said:
And to answer your question about how to unlock the spica:
http://forum.samdroid.net/f28/how-spica-i5700-sim-unlock-free-4886/
Click to expand...
Click to collapse
Yeahhhhh, my method.

thenks
Thanks for ansver
THANKS

Hello guys, i can't find the nv_data.bin file in efs folder. Please help

I prefer wait 6 month for operator code, it's more safe ^^ In france it's 6 or 3 month and operator give num to unlock ^^
But yes, go to samdroid, there are a completly "how to" for do that

check samdroid. someone makes free there.
Sent from my Galaxy Spica using Tapatalk

Use Any Sim for Web on T-Mobile Tab

****DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGE OR BRICKED DEVICES. PROCEED AT YOUR OWN RISK. EVEN IF YOU DO DO EVERYTHING RIGHT, YOU RUN THE RISK OF BRICKING YOUR DEVICE. I AM JUST SPEAKING FROM PERSONAL EXPERIENCE OF 7 TABS THAT IVE DONE!
I've read a few posts and threads and this is probably a subject that's been touched, but I wanted to make stuff a little easier for people like myself. As we all know, T-Mobile has blocked IMEI's from regular SIMs forcing us to sign up with a webconnect plan,or use WIFI. Well, here's a guide for noobs and others alike to use a regular SIM on a Tab.
You can do this with stock firmware, or flash a custom ROM with voice/2g.
3G and voice WILL NOT WORK WHATSOEVER SO PLEASE DONT ASK ME HOW.
*YOU MUST HAVE ROOT ACCESS IN ORDER FOR THIS TO WORK. Z4ROOT WORKS PERFECTLY WITH THE TAB. GOT TO 4SHARED AND DL THE APK.
1. DOWNLOAD Root Explorer or something similar from the market
2. Create a directory on your sd card and name it "efs backups" using any file manager.
3. Open ROOT EXPLORER and navigate to the root of your phone.
4. IMPORTANT:
You can either COPY ALL or MOVE ALL files in the /efs folder (on the root of your phone) to "efs backups" (on your sd card). Do not copy or move the /efs folder itself. You will brick your device.
5. IMPORTANT: IF YOU COPIED THE CONTENTS FROM THE /efs folder, YOU MUST DELETE THE CONTENTS IN THAT FOLDER ON THE ROOT OF YOUR DEVICE. IF YOU DONT, IT WONT WORK. EITHER WAY, MAKE SURE THAT YOU HAVE A BACKUP OF THE /efs folder and that the actual /efs folder is cleared.
6. RESET YOUR PHONE
AFTER THIS YOU SHOULD BE ABLE TO USE ANY SIM AND NOT BE REDIRECTED TO T-MOBILE.COM. IF YOU WISH TO REVERT BACK, YOU'LL JUST NEED TO MOVE THE CONTENTS FROM THE "EFS BACKUP" FOLDER TO THE /EFS FOLDER ON THE ROOT OF YOUR DEVICE AND RESTART.
I've done this several times on several devices and this definitely works. Thanks for all the help from fellow devs that helped me figure this out. Hopefully this guide helps most of you. HAPPY HACKING!

This thread will be deleted soon by the mods as it is a violation of the forum rules. This already happened once before. Just wanted to let you know. But i hope a lot of people can get to this thread before it is gone. I have done this to my tab and it is a godsend.
Sent from HAL 9000

[REQ] i9100T nv_data & .nv_core.bak Need Another Set

I'm currently trying to assist Odia from XDA in SIM unlocking this phone.
He needs another set of nv_core.bin
Use Root Explorer app to get the following files:
/efs/.nv_core.bak
/efs/nv_data.bin
In order to get these off, you will need to copy them to your SDCARD. Make sure to Rename .nv_core.bak to nv_core.bak as windows doesn't support the character . as first character.
Then can you zip/rar/7z it up and upload to mediafire, and pm me the link, so i can pass it to him?
He says he is close, just need another one to find the code.
There is no personal data in these 2 files.

Do u need 2 sets of the files unlocked and locked... Or u after the 2 files locked...

GTIRBOSS said:
Do u need 2 sets of the files unlocked and locked... Or u after the 2 files locked...
Click to expand...
Click to collapse
Just after those 2 files on a locked device would do.
If you can get a unlocked one, that would also be beneficial I think to Odia.

Sent them to odia... Hopefully will have it unlocked this week if no solution becomes avaliable... Then will send unlocked data to odia to help

Meaning of the dot
Hello,
I would like to know is there any special meaning or purpose of the dot as the first character in the filename. Does it mean the file is a backup or is hidden?
Thank you!