Problem with restoring imei - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi guys. I have problem. So i have my efs folder backuped. It contains following files
Code:
imei
-> bt.txt(23 bytes)
-> mps_code.dat(3 bytes)
nv.log(87,2kb)
nv_data.bin(1 697kb)
nv_data.bin.md5(32 bytes)
nv_datadel.bin(2 048 kb)
So i copied this to efs folder on my phone with root explorer. Rebooted phone and nv_data.bin changed to 2mb and i still have wrong IMEI
So guys. What is the solution?
Could someone help? Or know way how to prepere efs folder that would have my imei? I can provide pictures of my imei printed on my galaxy s box to proof that i'm not lying.
@EDIT
I forgot to mention that i have some clockwork backups. Do they contain imei backup?

if it was a nandroid backup then yes it will contain the imei
when you are using root explorer have you mounted system RW ??
if so and you still cant get it back, flash back to a froyo rom and it will be restored

Flashing Froyo helped. Thank you.
Close this topic

Related

[Q] JM6 IMEI Change

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.

can't restore efs backup :/

well after flashing jetpack 5.2 my imei deletedi have efs backup
but but
i cant restore it
when i type
cp /sdcard/nv_data.bin /efs/nv_data.bin
i get error that says :
cp:write error: No space left on device
yes i tried flash 3 file stock jvs , jvq and jvu roms but nothing
i restored nand backup = nothing
i would like some help since im getting screwed cuz phone is not mine :|
thanks
some1 said u need tp flash imcorrupted efs.rfs filewhat is that? where can i get it?
A little search found me this.... Good luck
azzledazzle said:
if you have a .tar version of your EFS. Unzip it. Copy all the contents of it, And paste them to the /EFS on the phone. Making sure they overwrite the current contents.
Once that has done, Restart the phone without backing out of root explorer (or what ever app you are using to copy/paste these files).
If that fails, Repeat the above step but ONLY copy / paste the NV_data.bin & NV_data.bin.md5
And finally if that fails. Backup all your stuff using Titanium Backup (or similar) And re flash a stock Froyo ROM. Maybe older, its upto you.
That will Definitely restore the IMEI, Then re-root and go back to whatever ROM you wish.
Good luck.
Click to expand...
Click to collapse
well i cant paste with ex explorer or root explorer says its fulland when i delete the files in efs the system immdietly make new nv_data,bin so again its full
//
i flashed stock froyo JPU and didnt work :|
i read some topics and i think phone bml3 (stl3) messed up
have you tried nitrality.... download it and make a back up of efs, and then replace the nitrality back up with your back up (sdcard/insanity/backup/efs). Then restore with nitrality.
it restores but not workin weird

Lost IMEI Noob here :(

Hello xda;
I installed ICS milestone 4 and my efs file corrupted.I can see lost+found folder under efs folder and some such files.Hopefully i have a backup when i first root
So i read some threads but couldn't understand.I tried overwriting my efs folder but the efs folder that is originial goes down to /efs/efs.Under the main efs folder it goes there Ç(
How can i restore my Phone funtion
Please guys help me (
i read on darkyrom http://www.darkyrom.com/community/index.php if you flash a stock rom through odin it may fix it ,ask on there also one of the devs will help you or someone else its pretty friendly
dreamer94 said:
Hello xda;
I installed ICS milestone 4 and my efs file corrupted.I can see lost+found folder under efs folder and some such files.Hopefully i have a backup when i first root
So i read some threads but couldn't understand.I tried overwriting my efs folder but the efs folder that is originial goes down to /efs/efs.Under the main efs folder it goes there Ç(
How can i restore my Phone funtion
Please guys help me (
Click to expand...
Click to collapse
Flash a stock rom via odin.
http://hdtechvideo.com/community
Sent from my GT-I9000 using Tapatalk
Delete the Efs Folder than replace it
...via Tapatalk 2.0...
Just flash a stock rom and the IMEI should be restored to normal
tHANKS.Everybody! I just flashed stock JVU from odin .No problems IMEI is back.
But i wonder.When i was on ics milestone 4 ,I change files from restored one (step by step imei file,nv_state file.... when i want to directly overwrite ,my restored efs folder go to /efs/efs.You got that? it goes under to main efs directory.)
Also in the corrupted efs file there was a "lost+found" blank folder.I deleted it but each time i deleted it,it went back Also other files...
Like i said i tried to overwrite all files step by step in restored efs to corrupted efs.It worken i mean my all restored efs went to normal.But my imei was changed 0049... to unknown.So i revert back to stock .And now
I'm using AOKP build 27-3 +devil 1.1.6b cfs kernel No problems at all
Anyone using galaxystmd milestone 4? I tried over 2 times from stock.And my imei was changed.How is that for you?
regards

I have no efs folder yet I am able to get an efs_backup?

Using the thread below, I am able to get an efs_backup, but there is no original efs folder on my phone. it has all the nv_data.bin and files like that, but no "efs" folder on my phone. What is the proper file structure? Thanks
http://forum.xda-developers.com/showthread.php?t=881162
You have no /EFS partition? and still get a backup with the files in it? Use a root enable file explorer and check the very root of the phone for /efs not /system/efs but /efs...
I am running the stock Xperia Play ROM and I don't have an /efs partition either. I haven't tried making backups yet, but I do have an IMEI and I can make and receive calls.
I understand this is the forum for a Samsung phone and perhaps only Samsung phones store their IMEI like this. Is it even possible to lose your IMEI on an Xperia Play?

:( EFS folder empty = 12mb of 12 used! How to restore unzipped backup?

Hi all..
So Im pretty new at flashing androids, been using ubuntu for years and am quite familiar with the terminal as well as computers in general. I made the silly mistake of not doing a complete backup of my phone with CWM before flashing with CyanogenMod 9 and now my EFS folder is "empty" but still with Zero free space... giving the "usual" errors":
1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
2) No Network and Signal ( calls, sms and mobile Internet not working)
3) No base Band or Unknown Baseband
4) Sim card lock missing
as described in the [A.I.O. Helpline] My Android Solutions.
CWM seems to have created a copy/paste backup of my EFS folder (not .zip and not .img, just a folder) on sdcard/efs/backup but the EFS folder is read only and root manager cant paste into it. I've read that deleting the EFS folder should recreate it, I tried in terminal with
Code:
rm -r /efs/*
and got the reply:
Code:
rm failed for /efs/lost+found, Directory not empty
How do I go about restoring the EFS folder?
Finally figured out how to copy/paste into the read only EFS folder! I have searched probably about a million threads, all say to "just copy paste" into the efs folder... but never how to do it when its locked because of read only permissions.
I think im one step closer.. but still not quite there yet.
The way to get write permissions is simply to open terminal and get root access and unmount the efs directory using:
Code:
umount /efs
After that, I could open the efs directory in Root explorer and mount it as R/W. Automatically, I get some default files there created by the system which I can delete and then I could copy/paste my backup into the efs directory. Bang, mobile network running, but baseband version is still unknown. Also, my IMEI number is the generic one, not my unique one
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Snarlster said:
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Click to expand...
Click to collapse
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
xsenman said:
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
Click to expand...
Click to collapse
Thank you, I had read each thread linking from those threads but it was good for me to do it again!
Flashing the EFS folder with Heimdall gave me the same results as copy/paste, setting the ownership/permissions made no difference in both cases, always empty on reboot.
FINALLY, these are the steps I took to get my phone "working".
1: Odin re-installed the stock I9000JVJV9_OJVJV9_JXJV6.tar file found on sammobile.com as well as the Pit file found on 4shared
2: This gave me an error on bootup... something about "failed to mount dbdata", this was solved with Odin as well by selecting only PDA and using the dbdata.rfs.tar found on hotfile.com.
After this, my phone booted up with the generic imei, a very welcomed change to the previous no imei thats been bothering me! Also, my baseband is showing, the EFS directory is full of files and google play is working... and fortunately, my carrier doesnt seem to care about the generic imei
I'm still going to get my imei back, but first things first! Its time to do some backing up!
Current plan is:
1: Install ClockworkMod
2: BACKUP
3: replace nv_data.bin with the backed up one.
4: reboot / see if my IMEI number is back.
5: BACKUP
6: install CyanogenMod
I hope this helpes someone down the road.. dont be shy on letting me know if my hours of pain helped you!
And... one more thing, my phone is Samsung Galaxy S GT-I9000
Thanks again for pointing me to the right direction
did you only used the PDA included on the I9000JVJV9_OJVJV9_JXJV6.tar file? and how did you use teh dbdata.rfs.tar? thanks.
efs Folder Contents
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
dixielee said:
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
Click to expand...
Click to collapse
I would be careful with that, if you have your efs folder on your sd card, I think it would be better to copy/paste them with root explorer back before reboot... though this is just a guess. In any case, since you have the folder on your PC, then at least you have the backup you need if you get into serious trouble.
If it did reset, please tell us about it in case someone else needs this info later
efs file restore
Thank you so much. After days of not having calling and texting functions available from a corrupted efs folder, who would have thought that a simple copy and paste of the backed up efs to the system would help greatly?
Hey, this worked for me, but I still can't connect to some carriers.

Categories

Resources