Hello everyone,
N7000, rooted, on stock 4.1.2
In my EFS folder (which is already backed up), I find nv_data.bin, nv_data.bak and nv_core.bak, alongwith their corresponding md5 files.
The only problem with my phone is a dead gps. After much googling and trying out different hardware/software solutions, I am convinced the nv_data file might be the cause.
I compared the nv_data.bin and nv_data.bak files (both 2mb each) on a windows machine and find a lot of differences. Also, the .bak is dated 01/01/2012, while the .bin carries the current date.
So, would it be safe to try out the .bak file by renaming it to nv_data.bin? I can always go back to the original, right?
Also, the 3rd file I mentioned, nv_core.bay (also dated 01/01/2012) is just 1 mb in size. What exactly is its purpose?
Thanks for any advice, I'm very eager to get the gps working and I love my phone!
Related
Hi, i've just dialled *#06# to get my IMEI and my imei number has changed from 352*********** to 00004**********.
Does anyone currently know of a way to change the imei number back? Thanks in advance.
Your Friend
Phil
I noticed on JM6 and JMA that it made my IMEI number incorrect as well, so when I entered it, it didn't recognise it to change the CSC.
Not sure if there is a way, hopefully so!
I'm sticking with JJ7 now on my replacement tab until we get a proper recovery mode in place.
I had this on my galaxy S. Solved it by backing up the efs directory to be safe. you need root. then delete everything in the efs dir except nv_data.bak then rename it to nv_data.bin and reboot. It should rebuild the efs dir correctly and put the imei back.
But this only works if the nv_data.bak file has not been modified in anyway otherwise it will rebuild with the 0044 imei.
Lordao
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
diigibio said:
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
Click to expand...
Click to collapse
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
zerocool76 said:
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
Click to expand...
Click to collapse
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
rgbc said:
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
Click to expand...
Click to collapse
I destroyed my original nv_data.bin editing with a txt editor instead hex editor, plus I deleted baks files for mistake with root manager (no booze when playing with this **** anymore ), I didn't know that the IMEI is encrypted in that file. When I found a copy in my sdk (that I didn't make!?) I restore everything, and after that time I flashed a lots of Firmwares and Modems, but my imei is still ok.I know that a Galaxy S firmware made this issue because it was changing the nv_data and it didn't match anymore with the phone, so corrupted IMEI.I'm wondering if there is a firmware that is doing the same with the Tab
Mine has done the same but with JK5. First noticed when I did the Samsung UK offer thing. Completely different IMEI to whats on the back of my Tab.
Sent from my GT-P1000 using XDA App
Sorry to dig up and old thread, but is this still an issue, can say flashing back and forward from Overcome for example corrupt IMEI etc?
Interesting - are other Samsung devices able to have their IMEI changed?
What this means is that to a technically capable enough thief (or one who knows someone technical enough that will work on credit), Samsung devices are much more valuable: Normally if your mobile got stolen and you had the IMEI, you would report it to your network and they would have it blocked on all networks. Furthermore the police would use the IMEI to prove that the device is yours if it were recovered. If the IMEI can be changed, the device can't be identified and can't be blocked from networks. It only needs slight tweaking to make it appear valid. Don't know about the implications for post-registration call routing, but the thief wouldn't care about that.
In the US, gsm carriers won't block the number - they seem to view stolen phones as a potential new subscriber.
hello,
i have the same trouble ( imei change)on galaxy tab , but the phone work normally (for now ...).
Can i let it so , or could have trouble in future?
because i don't save nv data folder, and i'm not very good to restore rom.The mod was made from my friend.
excuse for my english ,bye
zerocool76 said:
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Click to expand...
Click to collapse
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
paul.robo said:
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
Click to expand...
Click to collapse
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
ktmman said:
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
Click to expand...
Click to collapse
So i got my IMEI no.back but i still don't have a data connection. The strange thing is if i swap sim cards
with my phone it works so im not sure whats wrong with it.
I googled and searched but I couldn't quite find an answer. It would seem that my phone (SGS 4G, running Froyo) does NOT have an /efs/nv_data.bin file. I saw a few other users in the same predicament but I found no answers... can anyone shed some light?
Thanks!
Have you flashed a custom rom .
EFS can be restored from your efs backup ..
How do you know you have no efs folder
.
jje
the /efs folder is there. However, it contains nv.log and a few folders, but no nv_data.bin . The phone is as I got it from TMobile, minus the Superoneclick 1.6.5 root exploit. ROM should be the one that the factory put in there.
Well, apparently per the now-updated unlocking thread, the file is in a different location in the 4G. Found, fixed.
Hi guys,
Looking for helps here.
First I want to thank the guy created the "Overcome for Gingerbread", it comes w/ a great details instruction and I successfully upgraded.
My tab was original from Bell Canada, the phone feature was locked. I was able to unlock it by modifying the nv_data.bin file...
But now after I upgraded to Gingerbread, my phone feature is disabled again so I suppose I should do the whole unlock process again. However when I looked for the nv_data.bin file, the directory /efs is empty?!?!?!. Can someone help me here?
Thanks,
Edit: I found a nv_data.bin file on my laptop (not sure if it's the orginial one), trying to copy it to the /efs folder on the tablet, but I got error "not enough space"...
What program u using to copy with. Put that file on the SD card first from your PC.
Then get EF File Explorer rooted, and copy that from the SD card to the /efs directory
The nv_data.bin edit unlocks the tablet to allow use on other carriers like rogers, fido etc.
It does not provide phone usage, you need to flash a european rom to enable the phone,
then you need to flash a suitable modem to allow 3G data and phone, then edit your apn info.
Are you sure efs is empty, maybe your no longer rooted and can't see it?
You get the not enough space error because you have most probably renamed the original file and are trying to copy the new one in the directory. Delete the file and also the.md5 correspondent (it will be recreated on reboot.
P
Thanks for all the replies guys, but my problem is still there.
@Sonictab: I'm rooted and I'm sure that my /efs folder is empty.
@StarLog: I'm using Super Manager to copy the file
Now I can't even download files from the browser nor using the market place to download any apps. Something went wrong and I'm not sure what. Should I downgrade?
help pls,
i have been wrongly delete the .nv_data.bak.md5 & .nv_data.bak file in efs folder without any backup done.
but i still have the file nv_data.bin.md5 & nv_data.bin in efs folder,
and i been Flash from DXJPA , to JPY , to JPU, to JVB , to JVE , to JV5.
what can i do to get back the .nv_data.bak.md5 & .nv_data.bak file in efs folder??
or can i just get the file from another phone and do some editing ??
y not 1 answer to me ?
can i just get the file from another phone??
just copy and paste it on my phone ??
what will happen if i do by this way ?
Ofc you can try.Here are the files. http://hotfile.com/dl/120562433/d70ac90/files.zip.html
thanks ,
This file is either removed due to copyright claim or is deleted by the uploader.
i have few friend use SGS phone, i can simple get the file from them ,
the problem is i don't know when will happen if i just copy the file from other SGS phone and paste it on my phone .
the imel number will changes to my friend imel number ?
I dont think your imei changes, but your product code might change. Imei is in "imei" folder.
Ps: Hotfile sucks I uploaded files by myself....
They're the backup files and it won't cause a problem that they're deleted. They should be recreated by rebooting your phone if not, just copy the original files and rename them.
You should definitely disregard previous advice in this thread.
This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Nice one
mosen5 said:
This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Click to expand...
Click to collapse
This didn't work. I also tried installing EZbase Froyo and the IMEI was still 004999010640000...
Is there a working solution for this yet???
Mosen5, you say to copy to original eds folder. But where is that? Also do I not copy IMEI folder as well (that is within the backup folder)
Its frustrating this as I reflashed this about 5 times now and still stuck with no service.
Updated: Never mind. I found that efs folder (didn't show up with ezexplorer I had used). Pasted those two files and.... it didn't work for me :-(
I even took set it as flight mode, sim out, etc.
I suspect its resetting those files back to what it was because if you try delete them, its back in again straight away. So, pasting those files, would mean it might get reset back to what it had in the first place.
Found a solution. Going along the lines of what mosen5 suggested, but have to use adb command.
Full details here: http://forum.xda-developers.com/showthread.php?t=859914
Important notes the author forget to say:
YOU HAVE TO SET THE PERMISSION ACCODINGLY TO THE OTHER FILES ALREADY PRESENT IN THE EFS FOLDER,otherwise it won't work
Thx