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...
I been playing with my phone for a few days now trying to get it to work and I haven't had much success although I have been learning a hole bunch and now able to load any rom onto my phone easily and flash kernels and such with ease...
The situation is that I received a phone from a friend SGSII I have never had a rooted phone and it came pre rooted, never knew much about it as it is my first Android phone and now love it
never knowing I had to do these things like "backup EFS directory" and such as I know now... anyhow, a few days ago what has happened is I have a stock rom + CF-Root and my phone all a sudden started telling me there is no IMEI and no SIM card present.. after much research, flashing of roms, kernels, bricking the phone, re flashing and so on and so foth....... xda-developers is a FANTASTICK site full of useful information btw now I'm still at the same point but a lot more knowledgeable, I have learned that the problem lies with my efs folder and have found a .nv_data.bak file that is dated dec 31 of last year, at this point it is my only so called backup and hope that it will restore proper functions of the phone, as per some of the guides and other posts and questions I have learned to do this.. so what I have done was copy using ADB my files to my sdcard folder renamed my nv_data.bin to nv_data.bak and my .nv_data.bak to nv_data.bin
also I have used root explorer to copy the hole efs folder to a location on my external sd card and used HC-kTool to make a backup of my efs folder
now I have been trying to use the command to copy my nv_data.bin file in the sdcard folder to my efs folder and it is not working as it gives me msges of write protected file or file exist canot copy... the commands I have been trying to use are
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/
I have tried also
rm command to remove the file but nothing has been working...
one thing I should mention is that I have been connecting withough usb cable as I can't seem to connect with that I keep getting device not found so I been using the wireless adb function
abd connect "ip addressort"
I have tried installing the kies driver for usb and the google sdk drivers and none seem to work, in fact kies doesn't reconize my phone aswell... but Odin seems to function through my USB just fine.... not sure if that matters or not but trying to give as much info as possible
Thank you in advance for the help.... this is a great site with very knowledgeable ppl
permissions have to be reset as the back up does not copy the permissions. Use cwm recovery to reset the permissions.
Thank you very much for you quick response, however I have just tried that, booted into cwm recovery, went to advanced and reset permissions, rebooted my hone and still cannot copy the file
Try using a Root Explorer from the market.Connect via wifi obviously if your phone cant detect sim.Phone needs to be rooted.Give Root Explorer root permission and set to R/W from R/O and copy paste the nv.data files and IMEI to the efs folder in the root of your phone,reboot,boot to recovery and "fix permissions" and boot again.
sorry I guess I should of mentioned that aswell but thank you very much for the suggestion... I have tried to edit the file weather just delet it or overwrite or change permissions with Root Explorer and to no success.. also when I push the mount r/w button in the efs folder... nothing happens and the button stays as mount r/w
I found this.Maybe it will help.
http://forum.xda-developers.com/showthread.php?t=1258734
http://forum.xda-developers.com/showthread.php?t=1261948
http://forum.xda-developers.com/showthread.php?t=1085374
and if you manage to get it back then use this:
http://forum.xda-developers.com/showthread.php?t=1308546
Thank, I havent had time to read through them all but I will try tonight and see if I can come up with a solution... I will post here my findings weather they are good or bad..... but thank you very much for the info
I have read and tried and seen all those post, thankyou for the info the problem is still that I cannot modify my nv_data.bin file in any way... I cannot overwrite to it or anything using rootexplorer or adb or any other program... does anyone know of any other programs or command lines to strip the read only permissions on this file as it seems stuck on this and it's driving me insane lol
Gave up
I gave up and had it done professionally, they couldn't figure it out either and had to replace the phone.... Thank you all for the great help, even tho we didn't get it figured out it was great that help was provided
Thank you XDA-Developers your awesome!!
ive the same issue,got a rooted s2 with cwm all the forums cay copy the efe data but i cant find a way,anyone know how to do it?,i need to eddit it to unlock my phone:ie the simlock.
thanks
thank you for sharing your ideas
THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
IF YOU DON'T WANT THAT TO HAPPEN, MOVE ALONG, THIS AIN'T FOR YOU!!!
AS WITH ANY FLASHING PROCESS, SOMETHING COULD GO WRONG!!!
NEITHER I NOR XDA SHALL BE HELD RESPONSIBLE FOR ANY DAMAGE
THAT YOU CAUSE BY FLASHING THIS ZIP!!!
Now that's out of the way, let me explain the reasons for this zip's existence.
I personally do not like having things left hanging around on my phone's SDcard
after I flash a new ROM onto it, I usually back up my data and format the card too.
It struck me that due to the nature of having an internal SDcard in the Prime
There most surely be stuff hanging around in there from all the flashing I've done.
I also find that hunting down application folders for apps that I have since deleted
can be rather tiresome as they are not always labelled as expected.
Maybe I'm just lazy, but there you go.
Now you can simply install this Zip and all of your partitions will be fresh and clean.
So that's why this zip was born unto the world.
ONCE AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
BEFORE STARTING, MAKE SURE YOU CAN ACCESS YOUR PRIME THROUGH ADB IN RECOVERY!!!!
INSTRUCTIONS: (THIS GUIDE ASSUMES YOU KNOW HOW TO SETUP AND USE ADB)
1. Download prime-full-wipe.zip to your Prime.
2. Backup everything from your internal SDcard to a location that exists outside of your Prime. USB Hard drive, flash drive or another SDcard.
3. After making certain that your data is safe, reboot your Prime to recovery. (zip will work in both CWM and TWRP)
4. flash the zip.
5. Once complete, you will need to reboot to recovery manually otherwise ADB push will not behave correctly.
6. After a successful reboot to recovery, open up Terminal or Command Prompt.
7. Push a new ROM.zip to your Prime via the command
Code:
adb push /path/to/rom.zip /sdcard/
If "/sdcard/" doesn't work, which sometimes happens use
Code:
adb push path/to/rom.zip /data/media/
for some reason it seems that "/sdcard/" is not seen all the time. So far seems to be a windows issue only.
8. Install your new ROM and enjoy that factory fresh taste.
I hope that these instructions are clear enough. If anyone needs help I or someone else will be happy to assist.
I STRESS AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
Credits to mero01 for the original idea and Team Virtuous for some sexy code used in the zip file.
KOUSH for CWM and Team Win for TWRP
Big thanks to swiss-prime and anthonyexmouth for being patient men/windows guinea pigs!
Thanks to Nandrew for pointing out that users may need to reflash CWM if experiencing ROM Manager errors after flashing this ZIP!.
UPDATE: 31/05/12
OK, so to anyone that has had problems pushing a new rom to the SD card after using this zip file. I have found some rather odd behaviour that sometimes occurs when formatting the Prime.
After many hours of testing yesterday, I found that when using CWM I simply couldn't push a file to the sdcard no matter whether I was pushing to "/sdcard/" or "/data/media/"
The only way I was able to get a rom onto the sd card was to eventually flash TWRP using fastboot and push the file after booting into TWRP. However after doing so and then getting a rom installed on the Prime, when looking through the file structure with Root explorer I found that the sdcard symlink had not actually been re-created properly, the file was there, but it was not showing as a folder, and as such, I believe that this is where the problem some people are having stems from.
The only solution that I found was to re-flash the full-wipe.zip again in TWRP and then push a rom onto the sdcard again. After successfully getting back into a working rom, I checked out the file structure and the alias had been properly re-created this time.
The behaviour is very weird and there seems to be no rhyme or reason to it. However, if you have had issues pushing to the sd card after using my zip, I can only apologise for your worry.
I hope that the above makes sense and helps people out who feel that they are now up sh*t creak without a paddle.
To be clear I do not believe this to be an issue caused by CWM, I believe it to be a Prime issue.
Update 01/06/12
Nandrew pointed out to me that you will receive non-critical error messages from CWM about a missing log file after using this ZIP. Once you have made a backup, a log file will be created and these error messages will cease.
You may also need to reflash CWM if you experience rom manager errors.
I think I should give it a shot!
john9 said:
I think I should give it a shot!
Click to expand...
Click to collapse
I'm heading out for about 20 minutes, but I'll be around after that. If you run into any issues.
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
paddycr said:
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
Click to expand...
Click to collapse
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
<Edit> Nevermind... I read the whole post!
Doktaphex said:
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
Click to expand...
Click to collapse
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
paddycr said:
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
Click to expand...
Click to collapse
Just finished restoring my TiBU and all my apps and relevant data are intact after only copying across the TiBU folder.
Im glad someone finally made this for everyone else. I had once had a problem with my prime that no matter how many times i wiped and reflashed my status bar was not working and when i tried to return to my back up of stock it was giving me read errors restoring the data section and would stop. I had to modify a zip to format what this does and then reflash and then everything worked again. Wiped my tf201 clean but hay it worked again and thats what mattered.
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
acdcking12345 said:
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
Click to expand...
Click to collapse
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Doktaphex said:
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Click to expand...
Click to collapse
It is windows. :-(
acdcking12345 said:
It is windows. :-(
Click to expand...
Click to collapse
I would have a look at the naked ADB driver thread here very useful for windows users and should help put some of those fears to rest.
Yes and if you follow this guide to install ADB it will be easy:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Yeah, I dont think I am that gutsy to take this risk. But Ill keep researching it. I would like to start fresh as possible..
anthonyexmouth said:
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Click to expand...
Click to collapse
No I mean exactly as I said. After flashing in recovery, you have to reboot back into recovery. It is a funny quirk that I may need to look into further.
No then, to your problem. Do you have an irc client on your computer? If so, come over to #asus-transformer on freenode irc and we can talk in real time.
If not, then I will endeavour to assist you here.
Gonna take the zip down for a moment until we can sort this out.
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
anthonyexmouth said:
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
Click to expand...
Click to collapse
I assume that you are abbreviating when you say adb push "rom" /sdcard
It should take no more than 3 minutes to push the rom
yeah full path is adb push c:\android\virtuousprime.zip \sdcard
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?
To make a long story short, I have a Samsung S3 I9300 (International Version). I installed an AOKP-based ROM through CWM 6, it flashed successfully the second time around (was very laggy first time). Anyhow, I didnt get any mobile signal and found out my baseband, imei and meid were all unknown, After tinkering for hours, reverting to stock ROMS, etc. I accidently managed to format my EFS folder, thinking it would repair the problem since i have a backup. Thus.. now i cant boot up the phone. Stuck at samsung logo. I can get into revovery and download mode. And I HAVE a backup .tar and .img file on my INTERNAL memory (ya i know that sucks ) SO could my phone be repaired anyhow. Could its efs be brought back and restored?
Thanks in advance
Some more details
Stumbling through the forums, i found this thread http://forum.xda-developers.com/showthread.php?t=2087567&highlight=efs+file&page=2
The last post does mention a solution, however, my efs backup is located on the INTERNAL memory. Any idea how i could possibly access and recover and copy that to my pc?
boot into recovery and pull the files with adb
Thanks for the reply Glebun
But could you be more specific with your proposed solution? Im a noob i admit, and i'd really like to get my self out of this situation!
I boot into recovery.. i have cwm recovery 6.0.2.7
Now what is adb? Could you link me to the program and how exactly do i run it? and connect it? note that my phone cant even go past the boot screen
You need to learn to google.
Searching for "pull files with android adb" should get you started
Alright managed to do some googling as you mentioned and got as far as the point of connecting adb successfully to my device.. Just help me in one last step and ill be greatful. I've tried for hours but i cant seem to pull files from my device? I've tried 'adb pull /' 'adb pull /sdcard' 'adb pull /sdcard0' amd many more, but they return with '0 files found 0 skipped'
What to do?
i have atleast 8gb of data in my internal memory
The path is incorrect.
Type "adb shell", then "ls" for the list of all files and folders in the current directory. "cd %foldername%" to move to a folder
Thank you so much
I managed to recover the efs files successfully
I just need to restore them back to my phone without any hassle, and everything will be perfect!
I have 2 files now.
One is "efs.backup.tar.gz"
Second is "efsdev-mmcblk0p3.img.gz"
Suggest me a way to get these back onto my phone
https://www.google.com/search?q=efs.backup.tar.gz
first link. You haven't learned to search
Glebun I would really need some detailed help with this.
The internet and forums seem to be full of ways to backup the efs folder.
However no specific way to restore it back
I followed the first link and the fourth post gave me instructions to type this:
"gzip -d efsdev-mmcblk0p1.img.gz
cat efsdev-mmcblk0p1.img > /dev/block/mmcblk0p1"
I also typed
"gzip -d efsdev-mmcblk0p3.img.gz
cat efsdev-mmcblk0p1.img > /dev/block/mmcblk0p3"
but to no avail.
Then I proceeded to install efs proffesional in order to restore my efs backup but it crashes everytime the device is connected.
Could you please guide me through adb or through an application to help restore my efs back in place?
Sorry for any trouble
put the backup file on the internal storage and make sure you type in the correct path. read the whole instructions