Today I discovered that my Nexus S (9023) had no valid IMEI number. I suspect this happened while I was playing around with TWRP (I'm already back to CWM for the record).
Anyway, I saw no reason to panic, since I had backed up /efs back in june and I still had that backup.
At first, I tried to extract the tarball and copy it's contents to the /efs folder. This lead to my phone not even recognizing my sim card anymore. I tried several other methods of restoring my efs folder including this and this (edit: and this). I didn't succeed with any of these methods to get my sim recognized or have a valid IMEI number. In fact, I even ended up getting an efs folder inside the efs folder and another one inside that one (so ultimately leading to a /efs/efs/efs folder).
Then I wondered what would happen if I were to just delete the whole /efs folder. To be sure, I only renamed the thing to /efs_back. The result was amazing. Immediately, I had a valid IMEI number (the one that actually belongs to my phone). The efs_back folder was now gone however and /efs was back (with just the right content).
So what I can't help wondering is how my /efs folder was miraculously restored. Does the 9023 have some sort of self restoring feature, or did I do something right after all?
Today my IMEI was gone again, but I did not flash anything. I tried again renaming /efs to /efs_back and again, it was immediately replace by a /efs folder, but this time, I needed to reboot to get my IMEI back.
Can somebody please explain what's going on? I'm running CyberGR-MOD ver.8. Should I report my issues in the CyberGR-MOD thread?
Krekker said:
Today my IMEI was gone again, but I did not flash anything. I tried again renaming /efs to /efs_back and again, it was immediately replace by a /efs folder, but this time, I needed to reboot to get my IMEI back.
Can somebody please explain what's going on? I'm running CyberGR-MOD ver.8. Should I report my issues in the CyberGR-MOD thread?
Click to expand...
Click to collapse
Once you get it back, delete the bin files in the folder, then rename the bak files to bin files (ie: the bak files will become bin files after renaming!), reboot & see how you go from there! If all is well then it should stick on each reboot & you should then copy your efs folder to somewhere safe! Your bak files record the changes, so when you've deleted the bin files needed for connection & rename/change the bak files to bin files, the correct information that recorded the change should stick on each reboot!
CrackDaddy said:
Your bak files record the changes, so when you've deleted the bin files needed for connection & rename/change the bak files to bin files, the correct information that recorded the change should stick on each reboot!
Click to expand...
Click to collapse
I don't quite understand. Aren't the .bak files exact copies of the .bin files? And what do you mean by change? What change are you referring to?
Sent from my Nexus S using XDA App
..
Krekker said:
I don't quite understand. Aren't the .bak files exact copies of the .bin files? And what do you mean by change? What change are you referring to?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
The bak file records any "changes" to the bin file (before you had a problem, ie: before your imei got corrupted!), meaning that if anything goes wrong with the bin file, the bak file will have the "correct" information stored on it before that "change" happened! Why not just try what I've said? because at this stage you have nothing to lose that you haven't already lost!
PS: if this fix doesn't correct your problem, try following this guide here: http://forum.xda-developers.com/showthread.php?t=881162 This works with the Nexus S also, good luck!
The problem is not how to fix my IMEI. I'm just very confused about why a simple renaming of the whole /efs folder fixes the problem and what caused my IMEI to get corrupted in the first place.
Sent from my Nexus S using XDA App
As the great member Election day taught me a great way of backing up the efs folder as .img by using the cat command in cwm recovery..as soon as you get a valid imei use that method.
Krekker said:
The problem is not how to fix my IMEI. I'm just very confused about why a simple renaming of the whole /efs folder fixes the problem and what caused my IMEI to get corrupted in the first place.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Aside from user intervention, who knows why /efs managed to get corrupted - anything i say is just speculation.
As for the renaming, most likely some kind of factory-backup that was restored when you (effectively) deleted it. This is just fuel for figuring out whether these /efs backups mean anything when the phone can fix itself, but most of us are perfectly happy without the worry of sorting out our IMEI's
Related
Hi,
I have .nv_data.bak.md5 and .nv_data.bak files in the /efs folder...
They are dated as far as a year ago. they should be ok.
When I try to erase the nv_data.bin, something it re-creating it...
I can see that in the nv.log:
nv_data.bin does not exist.
default MV restored
how can I copy the backup ??
bump... please... help
SOLUTION!
I've wiped everything and installed a stock rom from my phone (Nexus S)
This was the first time that I saw a valid IMEI, but... it was a general IMEI 000444 something.
I had to root the phone again, installed root explorer and paste the good efs folder from back, reboot and it worked...
This time I was able to paste the file without getting restored from somewhere (No idea where it came from)
Gil.
Terrifying when your IMEI goes wrong, but good to see how you solved it, thanks
Sent from my SNES
So,
I tried the Galaxy S unlock software from the market, and now I am getting null/null as IMEI and I am not able to use it on any network..
Now, I saw in my sd card, there is a file nv_data.bak , that is around 20mb file...now I am trying to overwrite the one that exits in the efs folder, but its not letting me do it, saying I don't have enough space...
I am not even sure if the nv_data.bak is the actual file, I mean its like 20mb..is it supposed to be this big?
Would really appreciate if someone can tell me how to proceed from here...
I am currently on 2.2.1 Froyo.VUVKD1 kernel and 2.6.32.9 firmware.
Thanks
jackdowsan said:
So,
I tried the Galaxy S unlock software from the market, and now I am getting null/null as IMEI and I am not able to use it on any network..
Now, I saw in my sd card, there is a file nv_data.bak , that is around 20mb file...now I am trying to overwrite the one that exits in the efs folder, but its not letting me do it, saying I don't have enough space...
I am not even sure if the nv_data.bak is the actual file, I mean its like 20mb..is it supposed to be this big?
Would really appreciate if someone can tell me how to proceed from here...
I am currently on 2.2.1 Froyo.VUVKD1 kernel and 2.6.32.9 firmware.
Thanks
Click to expand...
Click to collapse
I've actually had that happen while flashing ROMs before... I crapped myself.
I fixed it by flashing to another ROM then to stock. Not promising a fix, but it worked for me, hell, its worth a shot eh?
Thanks...so should I try and flash back to Stock?
jackdowsan said:
Thanks...so should I try and flash back to Stock?
Click to expand...
Click to collapse
I would, yeah. When It happened to me I was flashing to a GB ROM, so I ended up flashing to another GB ROM and it was the same so I flashed back to 100% stock and it was back to normal. No clue on how or why it happened XD
flashed stock again...still NULL IMEI...I think I should flash one other rom before stock? Can you tell me which one you did?
jackdowsan said:
flashed stock again...still NULL IMEI...I think I should flash one other rom before stock? Can you tell me which one you did?
Click to expand...
Click to collapse
To be honest with you man I haven't the slightest clue. Mine may have fixed itself by random chance, or the reasons behind the problem are different. I just flashed a few times out of frustration and blind hope XD
Also, can you tell me what is the size of your original nv_data.bin?
I have a backup on sd card, that is like 20mb...and the one in efs folder is like 2 mb.... strange
jackdowsan said:
Also, can you tell me what is the size of your original nv_data.bin?
I have a backup on sd card, that is like 20mb...and the one in efs folder is like 2 mb.... strange
Click to expand...
Click to collapse
Im not finding a .bin titled nv_data. I've got an nv.log in my efs folder, thats the closest I see, its 400-some bytes.
It should be in efs\root\afs\settings
Would be great if you can look once and tell me...
jackdowsan said:
It should be in efs\root\afs\settings
Would be great if you can look once and tell me...
Click to expand...
Click to collapse
Herp derp im a tard! XD
Its 256kb
No problems..thanks mate, atleast now I know that 20mb is of no use...
jackdowsan said:
No problems..thanks mate, atleast now I know that 20mb is of no use...
Click to expand...
Click to collapse
Im thinking maybe that app you DLd was for the wrong phone or was just a crap app to begin with... there's gotta be a way to get it fixed but I can't speculate on it, I'll leave it to the smarter people here =X
do you have an nv_data.bin file in your /efs/ folder? Can you copy and email me the one in your /efs/root/afs/settings/ folder? I think IMEI NULL/NULL is different than the all 0's problem.
dagentooboy said:
do you have an nv_data.bin file in your /efs/ folder? Can you copy and email me the one in your /efs/root/afs/settings/ folder? I think IMEI NULL/NULL is different than the all 0's problem.
Click to expand...
Click to collapse
Thanks a lot for taking your time out to look into this, I have mailed you my nv_data.bin
Let me know how it goes, I am hopeful
Thanks
Jack
Anyone? I am still stuck here
Bump....anyone?
Rename nv_data.bak to nv_data.bin
I think you used a bad unlocking program.
Anyway, it created the backup, so rename and push.
But, delete a duplicate from efs if there is one.
also, try adb push, or repartition your phone if nothing works.
airfluip1 said:
Rename nv_data.bak to nv_data.bin
I think you used a bad unlocking program.
Anyway, it created the backup, so rename and push.
But, delete a duplicate from efs if there is one.
also, try adb push, or repartition your phone if nothing works.
Click to expand...
Click to collapse
re-partition would restore everything back? cause I think the backup is not working..
Try this
I had the same thing happen to me and this is how I solved it.
First check if you have any baseband version in phone settings -> about phone
If not your modem is not starting and this causes the null/null problem because of corrupt nv_data.bin.
1. rename your nv_data.bak to .bin
2. get root explorer and go to the efs/root/afs/settings folder
3. mount r/w if folder is r/o mounted
4. delete nv_data.bin and nv_data.bin.md5
5. copy your nv_data.bin from sdcard to this folder and reboot.
this fixed my screwed IMEI.
To get your unlock code just open the nv_data.bin file in a hex editor and look at adsress 1460 for something like 00 01 00 00 00 the text after this is your network lock code in PLAIN TEXT (if you use HxD free hex editor your code is in the ansi column in the right field) so just enter this to the phone and your phone is now unlocked.
brokencobba said:
I had the same thing happen to me and this is how I solved it.
First check if you have any baseband version in phone settings -> about phone
If not your modem is not starting and this causes the null/null problem because of corrupt nv_data.bin.
1. rename your nv_data.bak to .bin
2. get root explorer and go to the efs/root/afs/settings folder
3. mount r/w if folder is r/o mounted
4. delete nv_data.bin and nv_data.bin.md5
5. copy your nv_data.bin from sdcard to this folder and reboot.
this fixed my screwed IMEI.
To get your unlock code just open the nv_data.bin file in a hex editor and look at adsress 1460 for something like 00 01 00 00 00 the text after this is your network lock code in PLAIN TEXT (if you use HxD free hex editor your code is in the ansi column in the right field) so just enter this to the phone and your phone is now unlocked.
Click to expand...
Click to collapse
Does this still work ? ?
Hi,
for some reason i lost my Imei number. Im not sure when or how, but i would guess it was due to flashing.
Now i do have a backup of my efs folder, but somehow putting that one back doesnt work.
I get the following error in my nv.log:
Backup NV restored.
"MD5 fail. Original MD5 '17f88xxxx etc'
Computed MD5 'fbe9xxxxx etc'
Anybody with a solution to this?
I was thinking it might be because with ICS my radio was changed to the new one, so it makes a different MD5 checksum. Does this make any sence at all?
[edit]
ok this is really weird. Apperently ICS causes this. When i restore a nandroid back to GB and restore my backed up imei files, they stick and i have my imei back. As soon as i go back to ICS the problem is back.
Lowroad said:
Hi,
for some reason i lost my Imei number. Im not sure when or how, but i would guess it was due to flashing.
Now i do have a backup of my efs folder, but somehow putting that one back doesnt work.
I get the following error in my nv.log:
Backup NV restored.
"MD5 fail. Original MD5 '17f88xxxx etc'
Computed MD5 'fbe9xxxxx etc'
Anybody with a solution to this?
I was thinking it might be because with ICS my radio was changed to the new one, so it makes a different MD5 checksum. Does this make any sence at all?
[edit]
ok this is really weird. Apperently ICS causes this. When i restore a nandroid back to GB and restore my backed up imei files, they stick and i have my imei back. As soon as i go back to ICS the problem is back.
Click to expand...
Click to collapse
If you're rooted, use Root Explorer & navigate to efs folder, then delete your nv_data.bin file, then rename your nv_data.bak file to nv_data.bin, therfore changing it from a bak file to a bin file, then reboot & see if this helps! If this fails try this technique here: http://www.youtube.com/watch?v=JqLK_2I-SBM Works with nexus s!
CrackDaddy said:
If you're rooted, use Root Explorer & navigate to efs folder, then delete your nv_data.bin file, then rename your nv_data.bak file to nv_data.bin, therfore changing it from a bak file to a bin file, then reboot & see if this helps! If this fails try this technique here: http://www.youtube.com/watch?v=JqLK_2I-SBM Works with nexus s!
Click to expand...
Click to collapse
thanks for the ideas!
However, i dont have any bak files. I dont think i need them, since i do have the original .bin file.
The original does work, but in ICS it doesnt stick. As soon as i reboot its back to 00049 again.
In GB it does stick, but obviously i prefer to stay on ICS
Very weird problem.. cant be the only one having this issue?
Lowroad said:
thanks for the ideas!
However, i dont have any bak files. I dont think i need them, since i do have the original .bin file.
The original does work, but in ICS it doesnt stick. As soon as i reboot its back to 00049 again.
In GB it does stick, but obviously i prefer to stay on ICS
Very weird problem.. cant be the only one having this issue?
Click to expand...
Click to collapse
You should have bak files!? bak files are for recorded changes! You say you have a backup of your cfs folder? if you do, open that & do as I mentioned, then try repacing that folder with the one on your device, reboot & see if that helps!
CrackDaddy said:
You should have bak files!? bak files are for recorded changes! You say you have a backup of your cfs folder? if you do, open that & do as I mentioned, then try repacing that folder with the one on your device, reboot & see if that helps!
Click to expand...
Click to collapse
Well as I said, i have done that and it does work in ics... Until i reboot. Then its back to 0049...
In gb it does stick after rebooting, which seems strange to me.
not an ideal solution but why not just script the file copy. so when you reboot you dont need to do it manualy...
For those of you whom have flashed a rom for this phone, only to find you want to go back to stock, you may eventually run into a problem.
You lose data connectivity, EDGE2, 3G, 4G.
If you take a look into About Phone area in the Settings, you click status, and you will find your IMEI is corrupted.
Worst case you have to use a HEX Editor to change the values back to default, but I found a simple workaround that any new user can follow
Must be rooted.
Download Root Explorer or ES File Explorer
Change your settings to allow root options
Go to the root of your SD
Navigate to the efs folder
You will see a folder called imei, but you don't want that, you want the root folder
Now go into the afs folder
Now Settings
you should now be in /efs/root/afs/settings
nv_data.bin is the file you are looking for, copy it to the root of your internal or external sd card.
Now delete the nv_data.bin from /efs/root/afs/settings and reboot
Check your IMEI number as you did prior to the walkthrough, chances are, if you are lucky, the OS grabbed the imei during the boot.
Good luck, hope this helps someone like it did me.
imei
andrew2163 said:
For those of you whom have flashed a rom for this phone, only to find you want to go back to stock, you may eventually run into a problem.
You lose data connectivity, EDGE2, 3G, 4G.
If you take a look into About Phone area in the Settings, you click status, and you will find your IMEI is corrupted.
Worst case you have to use a HEX Editor to change the values back to default, but I found a simple workaround that any new user can follow
Must be rooted.
Download Root Explorer or ES File Explorer
Change your settings to allow root options
Go to the root of your SD
Navigate to the efs folder
You will see a folder called imei, but you don't want that, you want the root folder
Now go into the afs folder
Now Settings
you should now be in /efs/root/afs/settings
nv_data.bin is the file you are looking for, copy it to the root of your internal or external sd card.
Now delete the nv_data.bin from /efs/root/afs/settings and reboot
Check your IMEI number as you did prior to the walkthrough, chances are, if you are lucky, the OS grabbed the imei during the boot.
Good luck, hope this helps someone like it did me.
Click to expand...
Click to collapse
Can you possibly tell my step by step how to fix it in a hex editor and what hex editor to download? I actually have a couple of apps that wont work without the imei
I hate this phone. 2 days now and still no help on how to rewrite my imei back to my phone. debating on trashing it and buying another phone now.
Omg thanks!!!!
DUDE, THANK YOU SO MUCH!!!!
I literally spend 7 days trying to get this phone fixed. A T-Mobile representitive finally identified my IMEI as the problem and told me I would have to buy a new phone myself, since rooting it kills the warranty.
BUT
After searching around a bit, I found your post.
YOU FIXED A PROBLEM NO T-MOBILE REPRESENTATIVE EVEN KNEW ABOUT!!!
Saved me a bunch of money!!
Seriously man, great post. Big help!
Can someone tell me in here what should I do if my "efs" folder is EMPTY and I've no backup?
Sorry if I'm resurrecting this thread from the grave.
efs folder not found
What to do if there is no efs folder or a file called nv_data.bin?
I did a low level format to my phone in order to unbrick it, could this fix my imei?
Could this brick my phone again?
Hi just having a look around on my N8000 I noticed the EFS folder is empty, just wondering if anyone else has an empty EFS folder. Need root, file manager to / and look in the efs folder.
Problem sorted forgot to enable root explorer in Estrong file manager so that's why nothing was showing up.
Mate, back up your EFS folder, If it goes bye bye so does your phone and mobile internet.
No-one in their right mind will give the details of their EFS file to another person as it includes their UNIQUE IMEI number....
Do you need root to backup it? (on my other phones I've used ktool but it requires root)
Brgds... /Tubgirl
Sent from my GT-N8000 using xda premium
I believe it does as you are accessing the root drive for the information.
Not really sure as I root all my phones/tabs within an hour of getting them
where is it located btw?
i saved mine but completely forgot where to put it back in.
thanks