Hello all,
first to all who will say I must read the forum for problem solving - I did but from all the info out there it was simply too much. So I decided to start a thread in the hope that somebody will be able to help me.
So I have a corrupted nv_data.bin in my /efs folder but I still have backup of this file. But only this file.... I know - totaly dumb... I installed new JPX and after trying to change the product code from KOR to MOT (Slovenia) I accidentaly deleted nv_data.bin. I of course tried to replace it thru Astro Mate (I did had rooted phone - Darky's 6.0 was working fine ) but everytime I tried copiing this file tt didn't copy actualy - It said copied but the old file remained there - I know this because the Productcode didn't change. So I deleted the file thinking that this will help and tried to copy again. To my bad luck it didn't. I tried to copy and everytime a new file was created instead. also renaming a bakup file in this folder was not succesfule - it said Fald to rename file nv_data.bak. Since then my SIM card is not recognized and when I check what Baseband version I have it it written Unknown. So I tried even with ADB Shell, use busybox and when I eneter cp /sdcard/nv_data.bin /efs it says Now enough free space??? So I don't know anymore what to do. Does somebody have an idea what I can try to solve this? Please please please? I will donate to the one who helps me saving my SGS.
Thanks,
Borut
Hi !
This is because the file is used by the system.
Safest method:
- Reboot into recovery (make sure you have root in recovery)
- do what do need to do in recovery
- Reboot in normal state
In recovery phone / baseband / RIL are not started.
so you mean when I boot in recovery i can copy the file using adb shell? Or how do you mean I can do what I must do?
I have done it before while the phone is on, but you have to enter flight mode, set the correct owner and rights and reboot afterwards.
Well, regarding ownership and stuff like that - I'm a tootal noob
Help please NV_Data.BIN
I know this isn't the place to post this but I have been trying since yesterday afternoon can't figure out where I should post it to I keep getting an error that due to spam I can't post to certain areas without having 10 posts.
Please help -
I am not sure what to do now. I changed the rom on my phone to put 2.2 on it a while back. I never saved any of the files because I was not aware to. Now I am trying to go back to stock already used the one click Odin program and I have the original stock firmware on it. But when I try to update via kies mini it will not show up. I have searched And found multiple postings related to the fact that the product id and imei could be incorrect and you would need the original nv_data.bin file. I have searched through windows explorer on the phone but can't seem to locate one. Is there any way that I can get a copy of the original folder for /efs/nv_data.bin and any other files that are needed?
I have the Samsung Captivate on AT&T currently running 2.1
BaseBand: I897UCJF6
Kernel Version: 2.6.29 [email protected] #2
Build number: ECLAIR
You need to check your IMEI matches your original .
You have stock rom stock as in not the network supplied firmware that came with the phone ..
Windows explore is no good you need something like root explorer .#
I can get a copy of the original folder for /efs/nv_data.bin and any other files that are needed? Not unless you saved them they are phone specific .
Worth doing a factory reset before you make any step as that may solve your problem .
jje
how do I check the original imei? I didn't backup the files as I was not advised to in the information I found online at the time (couple months back). I have done a factory reset via the phone (privacy settings) a couple times now and still when I plug into kies it tells me Unregistered device.
This is very simple to fix if you have nv_data.bak in the EFS folder.
If that file is present then you can safely delete nv_data.bin and reboot the phone.
A new nv_data.bin will be generated.
how do i know if I have nv_data.bak? where on the phone would I find it and how?
Gotmtdew said:
how do i know if I have nv_data.bak? where on the phone would I find it and how?
Click to expand...
Click to collapse
It should be in the efs folder (unless you've done something to delete it). As said by JJEgan, you will need root explorer. Navigate to it in the efs folder and copy it to the external sd card and then keep it safe somewhere.
how do I check the original imei?
Its on the box and or with the receipt .
jje
SBF FLASH 1.08 (mbm)
VRZ_A955_2.3.20_1FF_01.SBF: No such file or directory
!! failed
this is happening every time i try. I have looked everywhere to find a fix i dont know what im doing wrong. I have been trying this for 2 days now and figured i would ask the experts. Also sorry i would have copied the whole process but i cant drop links for another 8 posts.
Probably entering the file name incorrectly, or your file isn't in the same directory as your sbf_flash, or you are entering the wrong command.
i have double checked all this. ill keep on trying
For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS
Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs
Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2
Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?
Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now
jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..
stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium
vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium
jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.
vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Does K-Tool work with CF-Root kernel?
HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar
Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there
Would someone please PM me a link to a copy of the nv_data.bin file, I need them for some new research.
Thanks in advance.
nv_data.bin file
Odia said:
Would someone please PM me a link to a copy of the nv_data.bin file, I need them for some new research.
Thanks in advance.
Click to expand...
Click to collapse
Hi Odia,
I can provide you with an nv_data.bin file or even the content of the whole EFS folder. I also have a question on this - I heard and see that you are The Expert here on these kind of stuff. The stuff I can send you does not contain my EMEI only a generic but otherwise seems to be OK. Let me know how would you like to receive the files. Also I have to state that - although it would of course be welcome - your help is not "in exchange" for mine.
So here's what happened:
1.) I was using various custom ROMs (rooted of course)
2.) Went back to leaked stock ROM (here comes the problem) 4.0.4 LPQ5. Unfortunately I learnt only after installing the ROM that its PIT file is corrupted. Error messages begun to show about "internal storage not formatted", etc. probably here I made the second mistake agreeing to format the storage. After that I had generic IMEI, had CSC, HW_rev. and Unique number unknown and a black semi transparent window stuck to every screen showing that.
3.) Re-flashed (with Odin) an older Samsung stock 4.0.3 FW (actually the one I bought my phone with), now everything seems to be solved except the IMEI which is still generic 004999010640000. At this stage I took a backup of my whole EFS folder I can provide you with. (Yes I know, I should have taken a backup of EFS before I started to even touch the ROM)
I learnt that the nv_data.bin contains the IMEI in an encrypted form so restoring the original IMEI it's not a simple hex editing. And that's where I'm stuck at now and would welcome any help.
Best regards and please have my appreciation on your work and contribution here!
Zsolt
I am bringing a cmd line sim unlock tool from adam lange to the next version of the Galaxy S3 ToolKit (as well as adding support for all US models obviously) and need the nv_data.bin file from the /efs folder to compare the different variants for unlocking.
If anyone can send me this file, I need the same file from the 4 carriers, I would be most grateful.
Thank you.
Mark.
mskip said:
I am bringing a cmd line sim unlock tool from adam lange to the next version of the Galaxy S3 ToolKit (as well as adding support for all US models obviously) and need the nv_data.bin file from the /efs folder to compare the different variants for unlocking.
If anyone can send me this file, I need the same file from the 4 carriers, I would be most grateful.
Thank you.
Mark.
Click to expand...
Click to collapse
Mark,
I'm on the At&T model and not seeing that particular file in there. Is it called something else? There is only 1 .bin file in the /efs folder called redata.bin and there are six other folders, none with nv_data.bin.
mskip said:
I am bringing a cmd line sim unlock tool from adam lange to the next version of the Galaxy S3 ToolKit (as well as adding support for all US models obviously) and need the nv_data.bin file from the /efs folder to compare the different variants for unlocking.
If anyone can send me this file, I need the same file from the 4 carriers, I would be most grateful.
Thank you.
Mark.
Click to expand...
Click to collapse
any updates?
thanks.
Was this taken care of? Definitely would like to use the toolkit for this phone!
Sent from my SAMSUNG-SGH-I747