Related
After 2 days and a lot of head scratching i've managed to finally get my phone back after a random corruption of my /efs folder... heres what i did:
the important part: you need to be able to access /efs with root explorer etc. and check the 2 files; .nv_data.bak & .nv_data.bak.md5
in order for this to work, these backups must be dated earlier than their .bin counterparts... in my instance, the .bins were modified sep 14th 2011 @ 09:45am (the time i rebooted the phone when i noticed i had no signal and the corruption occured), but my .bak files were both dated dec 31st 2010...
in adb shell, i ran
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
i then downloaded 7-zip, used it to open the .tar file
i deleted the corrupt files;
nv_data.bin
nv_data.bin.md5
i then renamed;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
after closing and saving the changes, i then went back to adb shell and ran
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs-backup.tar.gz -C /
reboot
and voila! i was prompted to select my network provider, check status and all my IMEI, IMEI SV and other info was back to normal!
hope this helps someone out there, as i had a hard 2 days trying all sorts of different methods to get this working and was getting to the point of giving up...
good luck
Dickie.
Original post
right, i've been banging my head against the proverbial brick wall all morning over this... this is the score;
This morning i had no signal - 0 bars with a little x from memory
i switched it into flight mode, thinking when i brought it out it might reconnect
when i entered the power menu again, the flight mode button was greyed out (but it said it was switched on), also 'Call' in settings is greyed out, 'flight mode' is UNticked in 'wireless and networks', and trying to enable bluetooth returns an 'In flight mode' message...
reboots, cache/dalvik/full wipes, reflash of rom, flash of stock from odin inc. modem etc all do nothing...
In settings>about phone>status i am missing a lot of info, including phone number, network type and IMEI/IMEI SV...
i can enable wifi, and i downloaded an airplane mode toggle widget, which re-enables 'call' settings, bluetooth, and replaces the aiplane symbol with a circle with a cross through it...
I'm pretty stuck at this point and all i can think is that perhaps the EFS has become corrupt... anyone got any ideas?? all suggestions appreciated... in the mean time i'm going to look into the EFS stuff which i have no idea about yet lol
cheers,
Dickie.
Click to expand...
Click to collapse
yes you have corrupted /wiped your EFS or IMEI ,
If you backed up your EFS its not a problem just restore .
Plenty of restore EFS posts around broken IMEI etc .
jje
I'm looking in the EFS folder now, all seems to be present, but i am missing my IMEI (*#06#)...
not sure how this has happened, not done anything recently... very strange... but it does seem to be specifically the IMEI as my macs etc all all there and ok...
not backed it up so i'll see if theres a way around it :/
Cheers,
Dickie.
This happened to me 3 days back. Was sure I needed to send it in for service (reflashed and everything without avail) but then someone mentioned the EFS folder corruption issue.
Thankfully, I bumped into Rawat's thread a few weeks prior, and promptly backed up my EFS then.
It only took about 3 minutes in the terminal to fix the problem afterwards, no pc needed.
No EFS backup would usually mean a trip to Samsung service.
I got the same problem sice yesterday... tried all with the help of some guys here but nothing helped!
@eiraku: Do you like to explain me how you fixed the issue in the terminal, because my was /efs folder was also backed up but overwriting doesn't helped
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
dickie2007 said:
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
Click to expand...
Click to collapse
Sounds hopeful.
I'd suggest you take a copy of those backups & put them on an external device before renaming anything.
i took 2 backups of the entire /efs folder, then renamed the bak files to bin, but i'm having trouble copying or pushing them to /efs...
anyone know how to mount it as r/w, i cant through root explorer and not sure via adb
any help appreciated...
Dickie.
---------- Post added at 06:24 PM ---------- Previous post was at 05:40 PM ----------
ok, i have tried the following:
busybox umount /efs
busybox mount -o rw -t ext4 /dev/block/mmcblk0p1 /efs
busybox mv /efs/.nv_data.bak /efs/nv_data.bin
busybox mv /efs/.nv_data.bak.md5 /efs/nv_data.bin.md5
then when i check with root explorer all appears correct with the baks gone and the bins dated 31 dec, but upon rebooting its all gone back to the way it was before...
again, anyone got any ideas??
Dickie
Did you found a solution? I'm thinking about going to a service center
i'm trying to work out how to get the damn /efs folder to remain r/w...
everytime i change the files, moments later its reverted to what it was...
just trying a different insecure kernel to see if that helps... even sometimes whilst i'm deleting/renaming the files it suddenly becomes read only again...
really wish someone who knew how to make either an update.zip or an Odin flashable tar could do so with my renamed .bak backup files to overwrite the original bin files...
Dickie
happened to me but the problem solved in a couple of hour without doing nothing
tried making an update.zip but i get a status 6 error... stuck again...
could anyone take a look at this for me?? ive been on this almost 18hours and im tired and need to sleep...
again, any help appreciated!
Dickie
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
nk_blu said:
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
Click to expand...
Click to collapse
thanks for the input but it made no difference...
i now what i need to do, i need to replace those bin files with the bak backup files... i just cant get it to stick after a reboot... its like i never did it...
cheers anyway bud
Dickie
http://forum.xda-developers.com/showthread.php?t=859914
Don't get rid of this ****ing efs corruption !!!
red103 said:
Don't get rid of this ****ing efs corruption !!!
Click to expand...
Click to collapse
using root explorer, look in /efs.
is there a difference in the dates between nv_data.bin and .nv_data.bak??
Dickie
It works !!!!!!!!!!
Thanks a lots dickie2007 !
Yesterday i updated kernel on Revo 2.7.1 via KitchenPro app (for infos from CFROOT_KI3.zip to CFROOT_KI3_v4_2.zip) everything seem fine but this morning no imei, no baseband...
I search a lot before finding your thread (i think this one should be sticky !)
Your procedure is clear & simple (and hoppefully work in my case).
Thanks again dickie2007
PS : It seem since the serie KI* there's a lot of similar problems (i saw many thread during my research this morning about this kind of trouble)
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
nokia8250 said:
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
Click to expand...
Click to collapse
Does this also work even if baseband is shown as unknown? I flashed a stock ROM with Odin and lost both baseband and IMEI. dickie2007's method didn't work but maybe yours would have...
My efs folder is wiped upon reboot each and every time. I have a T-Mobile Galaxy s II (T989). Luckily the imei is not being saved there, or if it is then Samsung has made it to where it cannot be deleted?
Anyways, I have the files that need to be included in the efs folder to give me my power menu and lock screen and other phone settings saved on my internal sd card. These are hte files that are wiped on each reboot. The efs says it cannot be mounted in CWM.
I have no problems making phone calls and such but I must pull the battery on each reboot, otherwise I also cannot get signal nor does it recognize the sdcard.
I bought this from some douchebag on Craigslist that said he was having a lockscreen issue and nothing else and now he won't respond to any emails. Of course. So I am stuck with it. At least I can make it work, with my bandaid fix of re-migrating those files after each reboot.
I would think that if I cannot get the efs fixed to where it can keep the files there, maybe a script can be initiated upon each reboot to copy the files over th the efs partition so I don't even have to worry about it? I thought this was done already with other options like overclocking and such but I don't know how to include my file migration or even where to begin to make this happen. Is there someone here that can help me?
I was thinking too that there may be a script running thats clearing the efs partition on reboot and maybe there is nothing wrong with the efs partition? I don't really know linux commands all that well and going through the .rc and .sh files on root, I do see some lines in some of the files that call for "mkdir /efs". I'm not sure if that was a one time run file or if that happens upon each reboot or if thse files are ran upon each reboot. I am specifically speaking of fota.rc and lpm.rc. The lpm.rc has " mkdir /efs 0771 system system". I do not know if these files are important or anything though.
I appreciate any replies. If files are neede for comparison, please ask.
Oh yeah, I've tried multiple roms, multiple factory restores and reinstalling CWM but it just keeps clearing out the efs upon reboot.
Anybody? I know it can be done, I just have no clue where to begin.
OK guys, I'm having a annoying problem and need helps.
My tab is P7500 64GB. I had been on AOKP build 38 for quite a long time without any big problem. I tried to flash build 40 recently and my tab was totally messed up. It FC every 30 sec and I decided to return back to HC 3.2 stock.
I went to Team Overcome site and download restock pack, including this "android_fastboot_emmc_full_p4_16G_32G.pit" and flash with stock md5 in Odin. Problem happened here!!! As mentioned on Team Overcome site, just ignore the error appear after Odin finished and continue to the ROM.
1st, after first boot, there is a screen asking for password. I found solution is to go to CWM and wipe data & cache. Everything was ok, except it keep saying "can't mount /efs", and the ROM is crazily sluggish. After that, no matter how I tried different ROMs, from HC to ICS, the ROM is still lag like hell.
Only temporary solution I found is to manually set permission /efs folder to rw-rw-rw after every boot to get the ROM back to it speed.
------------------
OK, in short, I'm deeply f*cked. Just realized that my tab can not realize sim card at all.
Please look at 2nd post and help for backup of /efs.
------------------
Then, f*ck all the sh*t. Just downloaded SGII_Repair from market, fix from it. 2 steps & sh*t gone away. More than happy.
Please close thread
Found this on other device forum
FIXED....
here's how.
as you may see in the post i stopped in the step of trying to format \efs partation.
but instead.
I went to my friend phone and make this command
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/ilostit.dd
this backup the mmcblk0p1 which is \efs to a file.
then move it to my phone \sdcard
and did this commands.
Code:
umount /efs "unmount /efs
dd if=/sdcard/ilostit.dd of=/dev/block/mmcblk0p1 "relfash mmcblk0p1 with the backup.
reboot
this reflash mmcblk0p1 block with the backup,
then copy my \efs backup to \efs.
and no more IO error..
and violaa...
my IMIE is back and the Signal is OK.
Click to expand...
Click to collapse
Which means, some one please back up your P7500 /efs folder and upload here so that I can revive mine. Thanks a lot!
I need this too! My efs is also gone
Sent from my GT-P6800 using xda premium
camapghe said:
Found this on other device forum
Which means, some one please back up your P7500 /efs folder and upload here so that I can revive mine. Thanks a lot!
Click to expand...
Click to collapse
This can't be done...unfortunately efs contains the imei, so if someone gives their /efs backup to you, you will end up with the same imei. Imo it is highly unlikely that someone is willing to give you his/her imei.
Check this out:
forum.xda-developers.com/showthread.php?t=1264021
It may help you!
Sent from my amazing 10.1 galaxy tab
Thansk Panos_dm, but I stuck at this step:
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
No .nv_data file at all! Can you share?
I'm sorry but as I stated earlier I can't risk the contents of my /efs folder. Maybe you could flash a stock rom, go to Samsung and claim that it stopped working...maybe they'll buy it!
Sent from my amazing 10.1 galaxy tab
Ok, may be I'm not that screwed as I thought. I used EFS Pro latest version and some how fixed the efs problem. My tab realized sim card, base band appeared and everything seems fine. However, just TEMPORARY.
Every time I reboot, /efs folder screw again until I fix it by EFS Pro. Any permanent solution guys?
Hello xda!!
I own a GS3 i9300 and im a noob at android's and codings.
When I start the phone, I have no IMEI, cant see any carrier, I don't have lock screen and I don't have that power menu.
The only method I am using to correct this whole issue is :
-Go into Root Explorer
-Go to "/system/efs
-Copy the whole "Efs" directory
-Paste on /Efs
and voilá, it starts to work. I get everything back. The problem is I want this to be permanent, like a normal Phone. I have a rooted stock Rom. This might be simple to solve but I really don't know.
Thanks
raixa said:
Hello xda!!
I own a GS3 i9300 and im a noob at android's and codings.
When I start the phone, I have no IMEI,
Restore your backed up EFS folder .
Fix Permissions see sticky .
IMEI/ EFS see multiple posts on the subject .
jje
Click to expand...
Click to collapse
I've used fix permissions but i cant restore any EFS cause EFS pro says this "efs pro can't locate mount point"
Should I flash a new firmware and restore the EFS?
Just flashed stock firmware and Efs problem still continue.
I have the EFS backup.
The problem is that every single time my device reboots, the EFS folder appears, but has nothing inside. I can´t change permissions on the folder because root explorer wont let me.
Any solution?
raixa said:
Just flashed stock firmware and Efs problem still continue.
I have the EFS backup.
The problem is that every single time my device reboots, the EFS folder appears, but has nothing inside. I can´t change permissions on the folder because root explorer wont let me.
Any solution?
Click to expand...
Click to collapse
No firmware (stock or custom) modifies efs partition when flashed. If it was broken before, it will be when you flash stock firmware also.
You will need root access to fix this problem. If I had this problem I would flash a rom with root, busybox and as no other mods to be on the safe side (or root and install busybox on the stock one). Try to make a new file in /efs (use a file manager with root access) and reboot . The file should be there after restart. If it is the the phone is ok and you will just need to restore the backup. If it isn't you will need help from someone with more experience.
Thanks dav_991.
Just tried your solution but after the restart, there's nothing on /efs again.
One thing I noticed is that when I enter /efs folder its "mounted like R/W", but if I switch to "Mount R/O" and I get out of Root explorer, some files appear on the Efs folder. Thing is every time I restart the phone it appears mounted as R/W.
raixa said:
Thanks dav_991.
Just tried your solution but after the restart, there's nothing on /efs again.
One thing I noticed is that when I enter /efs folder its "mounted like R/W", but if I switch to "Mount R/O" and I get out of Root explorer, some files appear on the Efs folder. Thing is every time I restart the phone it appears mounted as R/W.
Click to expand...
Click to collapse
On my s3 /efs is mounted as rw by default. I do not think that this is related to your problem. To see which partition (and how) is mounted as /efs, in terminal emulator type (and grant permission when asked):
Code:
su
cat /proc/mounts | grep /efs
It should look like:
Code:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
Yot could also post the files that are in the efs partition before and after you mounted as ro with command:
Code:
ls -la /efs >/sdcard/efs_list.txt
In phone memory you will get a file named efs_list.txt with the names of the files (every time you run the command the file is overriten, take this in consideration. Also be careful not to misspell something, you could overrite something you need).
I did some more research and ended up being the /Efs folder that wasn't mounted.
Managed to solve it by the terminal, adding the SU command.
Thanks everyone.
Best Regards,
Luis Matos
Bought and activated used phone 2 weeks ago. Phone worked fine thru Friday night. Woke up Saturday to find I could not connect to cell network. Call to carrier revealed my IMEI number does not match the number they have. Somehow my phone IMEI changed to 350000000000006. Internet search revealed many others with same problem. The main difference between their situations and mine is the fact that in almost all of their cases their phone was rooted and they flashed many different ROMS to their phones and something obviously went wrong. My phone is NOT rooted and I have not tried to modify anything. Simple as that. Went to bed working, woke up broken.
I have now researched this the last few days and have no clear answer. Is it possible to set my IMEI back to my correct, legal,clean and not blacklisted value? Any help is greatly appreciated.
My guess is without a backup of the original, you can't do anything about it. Best bet is probably return it to the store you got it from and get a refund/exchange.
Edit:
Fastest and safest bet would be refund/exchange.
Little research has shown other people had a similar issue. Check Nox to make sure the phone hasn't been rooted before, if it has, you know what happened. If it hasn't, chances are the phone was flagged as lost/stolen after being sold (if 2nd hand).
As for a fix, I found this:
http://forum.gsmhosting.com/vbb/f898/g925f-imei-350000000000006-a-2044425/
Recover corrupt IMEI (without prior EFS backup folder)
Items needed
Root Explorer
Efs folder (no need to have a backup of this prior to the disappearance of IMEI folder, but it has to be this folder on the phone)
Obviously having a rooted phone
Instructions
1- With the Root Explorer to back efs folder to the SD Card
2- For safety make a second copy of the folder to the PC
3- Once both copies made to proceed to erase the original EFS folder on your phone
4 Restart the phone
5- When you start the phone, it will automatically create a new folder EFS, Root Explorer to delete the files and nv_data.bin.md5 nv_data.bin found inside the new EFS folder.
6 Copy the folder from the SAI IMEI folder we saved on the SD card and stick it on the new EFS folder created in the root directory of your phone
7- Since the SAI folder we saved on the SD card .nv_data file copy, paste into the new folder EFS generated in the root directory and rename it nv_data.bin phone, then recopy again .nv_data file rename it nv_data.bin.bak
8- With Root Explorer /efs/nv_data.bin change the owner
9. Restart the phone
If all went well you should have recovered the IMEI can check if recovered by entering * # 06 # on the phone dialer.
Thanks for the response ProdigyThirteen.
The Knox is clean 0x0. Everything I have found says the original IMEI is clean and not flagged.
I will definitely look into the procedure you provided. It looks promising. I'll take any sign of hope I can get.
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Copy the nv_data file from the SD card to the newly generated EFS folder on the phone and name it nv_data.bin. Then make another copy in the same EFS folder and name it nv_data.bin.bak.
Then you need to set the permissions for EFS folder/nv_data.bin file. They need to be set to rw-r-r. However for this procedure you need to be rooted.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Could you tell me did it work?
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Shaggydoo said:
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Click to expand...
Click to collapse
Have you tried flashing the stock firmware again? Either by smart switch or odin?
Will try again tonight when I get home.
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Shaggydoo said:
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Click to expand...
Click to collapse
I remember I did have the exact DRK error on my s6 edge one and dm verity fail. The way I fixed it was by flashing stock firmware through Odin. Quote me when you try again and I'll do my best to help mate.
IMEI
If you want to get back your IMEI try Dashboard .
you will find all your devices there, then try to find a way to write your IMEI in your phone (may need root)
Dashboard (https://myaccount.google.com/dashboard?hl=en)