EFS Backup Restore utility (Noob friendly)
What and Why
Before starting with this guide you must know what is EFS and why we need to backup it, still you don't know about it then Read This and come back.
OK so now you know why we need this and again before proceeding make sure you need device Rooted, If you don't have rooted device then first Root it (use this guide option 2 to root ) then join here directly to step 2
STEP1 : prerequisites
1.As said above you should have rooted device
2.Make sure you have CWM/TWRP installed. If you have stock recovery then you can use this guide to make EFS backup. But here described method is much easy and noob friendly.
If you want to install CWM then download this philz recovery and flash using Odin
STEP2 Backup EFS
1.Download EFS_baclup_restore-AromaV2.zip
2.Copy downloaded file to Int/Ext SD card
3.Switch off device and press Vol up + Home + Power to reboot device to Recovery Mod. Once it rebooted to recovery mode, selecy Install zip option from recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.Select option choose zip from sdcard OR Ext Sd card depending on file you have copied
5.Select EFS_backup_Restore_Aroma.zip and select enter.
6.Now next screen you will have is Aroma installer. You can select option depending on your choice, where to store EFS backup. Here in example i have selected to make backup on both place int and Ext SD card
7.Once backup is finished, you will have msg like this. Now you can select next to exit.
8.Now select back and return to main menu of CWM and select to reboot system now.
After successful backup you will have MyEFS folder depending on location you have select to backup. You can see 20MB file efs.img in MyEFS folder. along with that you can see build.prop file too. Actually that file have nothing to do with EFS backup but just for capturing information of your ROM when you made EFS backup.
STEP3 : Copy to safe place
Copy MyEFS Folder along with files in it to safer place on PC / Cloud to make secure extra copy.
RESTORE
Follow first 5 steps as mentioned above in 'Step2 Backup EFS'. Now here you have to select option
'Restore EFS from intSD' OR 'Restore EFS from EXTSD' depending on location you have choose to make backup.
Select one of it and click next.
Now exit from aroma, reboot device.
PS : If you already have efs.img 20MB file which you have created with other tool and want to use this to restore EFS, you need to create MyEFS folder and to put efs.img file to MyEFS folder in sd card manually.
Change log :
[13Sept13] V2 released : All user of first release requested to use V2 to restore EFS, First release have bug in restoring and may fail to restre. If you have made backup with first release no need to make backup again, issue was with restore only. Sorry for inconvenience.
In case need this
Good tool Dr.ketan.
What is the difference between this tool and philz cwm efs backup option?
sent from my GT-N7100. Press thanks if I helped..
Nothing technically
But Philz recovery have option to make EFS quite internal and may be newbie don't knowing it. Also AFAIK it making backup as hidden file so again sometime newbie gets confused.
Here attached tool makes simple efs.img on MyEFS folder and that you can restore with other tool like AS_id's tool OR with Terminal emulator i have mentione in other thread.
Here i have illustrated in detail so it may become easy for any newbie.
So product efs.img file is same as all. And can be restore with other tools also.
One suggestion from my side,
Add date, time and ROM details in .txt file with this efs.img backup if possible.
I know you have backup buid.prob with it, but as noob we can't identify.
And thanks again for this nice tool. Adding this to this thread also.
sent from my GT-N7100. Press thanks if I helped..
Useful
Very very useful for newbies .. :good::good::good::good:
MBariya said:
One suggestion from my side,
Add date, time and ROM details in .txt file with this efs.img backup if possible.
I know you have backup buid.prob with it, but as noob we can't identify.
And thanks again for this nice tool. Adding this to this thread also.
sent from my GT-N7100. Press thanks if I helped..
Click to expand...
Click to collapse
I thought earlier to make date stamp, but i think it's have no use b'coz we can't remember on which date which ROM was there on our device.
Build.prop is giving information of your ROM which really we needs. just open with text editor file from device and you can find information in first few line.
Thx Doc for the great tool. You make people's lives easy :thumbup:
Great tool. It should be included in every aroma based roms.
However is the efs backup valid with any modem? I have the impression that they are related and newer modems effect older modems.
Great, thanks a lot!
albsat said:
Great tool. It should be included in every aroma based roms.
However is the efs backup valid with any modem? I have the impression that they are related and newer modems effect older modems.
Click to expand...
Click to collapse
See you have some misunderstanding.
This is different method of making backup, it doesn't make changes in contents of it.
Modem have no role directly. basically culprit is newer kernel. when you flash new ROM (so kernel) it lakes change in EFS partition which older modem can't read and so No IMEI.
If you flash new modem than again it will work. And tha't why i included to make backup of build.prop to capture ROM information at time of backup. So if you have created backup on older ROM, i recommend to flash older ROM - Restore backup - Upgrade ROM.
DR. Ketan you rocks!!!
Thanks for this valuable info for people like me!!!
You always anticipate mistakes made by newbies like me!!!! and make our life easy by making small installer zips like this.
Thank you once again!!!
Ashwin
And such compliments inspires to make all these possible!
thanks
Thanks for your easy guide
@ All
Who have download first release kindly use V2 to restore. I have foud a bug which may cause fail to restore. No need to make backup again if you have already made with first release, it was only restore issue. Sorry for inconvenience.
Thanks Dr. for providing very easy way to back up and restore of efs.
Sent from my GT-N7100 using xda app-developers app
Dr.ketan, I have saves log file of this tool. Observed it works perfect for backup and restore. But gives some error. Is this ok?
Code:
Mounting...
about to run program [/tmp/mount] with 2 args
mount: mounting /dev/block/mmcblk0p16 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/tmp/mount] with 2 args
about to run program [/tmp/mount] with 2 args
about to run program [/tmp/DrKetanESFBE.sh] with 1 args
mount: mounting /dev/block/mmcblk0p13 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p16 on /data failed: Device or resource busy
/tmp/DrKetanESFBE.sh: line 14: unmount: not found
/tmp/DrKetanESFBE.sh: line 15: unmount: not found
/tmp/DrKetanESFBE.sh: line 16: unmount: not found
run_program: child exited with status 10
Ignore that.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Ignore that.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Hi
will this work on any rom and any device (i.e. - Galxy S3 - I9300)
cheers
Related
***Please backup your /efs folder with Root Explorer or similar before you flash any ROM!***
Here is what happened to me:
a) I flashed some firmware which changed my phone's product code.
b) I tried to restore it by editing the nv_data.bin file contained in the /efs folder.
c) This made my phone show a corrupted IMEI (004999010640000).
c) A corrupted IMEI means lots of trouble, in my case I cannot download apps from market anymore
d) If you don't have a /efs backup your only chance is sending your phone to Samsung for repair (it's illegal to modify IMEI and moderators will ban you for discussing this subject in their forum).
The /efs folder is located in the root of you phone, it is only visible with Root Esplorer or similar, and contains IMEI and product code information which is signed and matching, don't change its contents unless you have a HEX editor (I wrongly used wordpad instead).
If mods think this warning will save some headaches to forum users, they could sticky it.
Probably it will help reduce IMEI modification discussion as well!
imma do this now just incase...
took one for the team huh... good looks...
I understand that modifying your IMEI is illegal here but there should be considerations on how to restore the IMEI back to original state if it was damaged by a firmware flash and no usable nv_data backup, the information on the nv_data is encrypted and from what I understand the IMEI data on nv_data has to match the hardcoded IMEI so Im not sure if its possible to change the IMEI on the SGS by just changing the nv_data contents.
Wow, thats a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this was discussed to death a few month ago and only firmware to do so is JPC, which no one would flash now.
And you shouldn't toch those files, as they are signed (you have to delete so they are recreated from back up). Go and search a bit (look for specific topic and topics with "Release" in them).
I was able to flash JPC ages ago even before the warning on the efs came out, there was a guide on how to restore the IMEI from the back up.. sadly on my end the back up was also corrupted, Not much of a big deal for me as in my place IMEI duplicates dont really matter.
guys i have unlocked my samsung vibrant to other carriers, all is going good. then i accidentally deleted my new efs folder. when i copied my old efs (from the locked phone) my IMEI was screwed up. but still my phone is working fine all that is not good is my IMEI is changed to a different number which has a lot of zeros.
how can i fix this problem?
i got a backup of my efs folder but do anyone knows how to restore it back
dupel said:
this was discussed to death a few month ago and only firmware to do so is JPC, which no one would flash now.
Click to expand...
Click to collapse
But it's always safer to keep a backup of that folder. Any malicious code can delete/modify the ocntents of that folder (with su permissions), and you can't get it back completely by flashing, only by backup.
I backed up my folder and hopefully i'll never need it, but how would I restore it in the case my imei is broken?
how to
Probably a noob Q but how do you backup nv ? Tried kalpik's command line but seems that it doesn't work on jpa
teo74 said:
***Please backup your /efs folder with Root Explorer or similar before you flash any ROM!***
Here is what happened to me:
a) I flashed some firmware which changed my phone's product code.
b) I tried to restore it by editing the nv_data.bin file contained in the /efs folder.
c) This made my phone show a corrupted IMEI (004999010640000).
c) A corrupted IMEI means lots of trouble, in my case I cannot download apps from market anymore
d) If you don't have a /efs backup your only chance is sending your phone to Samsung for repair (it's illegal to modify IMEI and moderators will ban you for discussing this subject in their forum).
The /efs folder is located in the root of you phone, it is only visible with Root Esplorer or similar, and contains IMEI and product code information which is signed and matching, don't change its contents unless you have a HEX editor (I wrongly used wordpad instead).
If mods think this warning will save some headaches to forum users, they could sticky it.
Probably it will help reduce IMEI modification discussion as well!
Click to expand...
Click to collapse
That's why I don't care my productcode. I think it changed to KOR long time ago.
I already have JPO. should I still backup efs for later flashes or did i have to do this on eclair? My IMEI is still OK. Never had JPC though
androidfreak2010 said:
I already have JPO. should I still backup efs for later flashes or did i have to do this on eclair? My IMEI is still OK. Never had JPC though
Click to expand...
Click to collapse
Some people say that JPA is ok, BUT JPO corrupted their IMEI. Its what was said.
I am sorry that my post annoyed some senior members whose opinion I respect and to whom I am thankful for their job here on XDA.
I only own an Android phone since a month and previously I only visited WM 6.5 forums, so I missed all the discussions about this subject.
That's why I thought it would be a good idea to have a warning stickied somewhere for total noobs like me.
For those needing a way to restore their backups it depends on what they did to save their data:
-if they have copied the /efs folder with root explorer or cp command just copy them back to your phone's /efs folder.
-if they have a efs-backup.tar.gz file in their internal memory they have to type in ADB or terminal emulator the command:
su
busybox tar -xvvzf /sdcard/efs-backup.tar.gz
I just checked the esf folder on my pohne with astro file manager and it's empty. What's with that?
Astro is no good for that, you shoul use root explorer or similar.
If your IMEI is ok you definitely have a good /efs folder content.
Search forums for ways to backup its files (either use root explorer or adb or terminal emulator).
Sent from my GT-I9000 running Doc Froyo v7.6.2 JPO
I think I deserved that, that's why I have switched to a new account on xda.
Sent from my GT-I9000 running Doc Froyo v7.6.2 JPO
i move my efs folder to sd card and i moved back do root and now i dont have emei number anymore me cell is infuse 4g whats can i do or its gone...
So, just to make sure.. I opened Root Explorer on my galaxy s2 (with villain rom 3.0) and copied the EFS folder and transfered it to my sdcard, then I also copied it from my sdcard and stored it into a backup folder in my computer.
Does this mean that if my phone somehow becomes corrupt and i lose my IMEI and what not, I can just restore that efs folder with the one I just backed up and my phone will work again?
yes backup - if fail - restore
/EFS partition contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI (nv_data.bin).
It's highly recommended to backup the whole partition, or at least copy the files from the efs directory.
CORRUPTED OR NOT?
You can check if the efs is mounted or completly damaged with this command:
adb shell
mount
You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Red part means /efs is mounted.
IF YOUR PHONE HAVE CORRECT EFS PARTITION:
1, Root your phone - there are several methods to do this.
2, Install root explorer or Estrongs file explorer and copy /efs dir to your sdcard - this will copy the files.
or
2, Make a backup from the whole partition -this is better if you flash a phone with wrong ops, the only way to restore using this backup.
Backup:
adb shell
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Restore:
Add efs.rfs to an unix compatible tar and flash with odin as efs file:
IF YOUR PHONE /EFS IS CORRUPTED:
Flash the included /efs tar with odin:
This will remount your efs partition and (if you have a backup or fixed nv_data.bin) you just need to overwrite files with a file explorer.
confirm WORKING 100% ... all you just need later is the nv_data.bin fixed
Thanks so much for your efforts
I am using I5801 JPB (with restored bootscreen and Rooted via SuperoneClick)
while using "adb shell" command at Better terminal its showing "adb: not found"
I flashed my I5801 from JP9, JPA and JPB till date..
is it possible to restore the backup now..??
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Szaby59 said:
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Click to expand...
Click to collapse
many thnx..
BTW i am not able to get the snaps u attached..
sirtbhopal said:
many thnx..
BTW i am not able to get the snaps u attached..
Click to expand...
Click to collapse
google about install ADB for android phone, so you can follow TUT here... good for you now and future..., long journey to go, m8!
how to make .tar file because backup file is .rfs format help me i want my imei back
ok, using the dd method i made the backup of my /efs to a efs.rfs file that have ~4 MB
But when i go to the efs folder (on / ) or see the copy i've made to my SD card, there is no files at all on this folder. How can we "see" those files (nv_data.bin) ?
Hi
For backup I simply copied my /efs folder to SD card using root explorer.
Then I modified nv_data files to get unlocked.
there was no SSNV in the files.
I have a working unlocked phone now but the problem is that IMEI is all zeros like 000000000!
Can I use that folder to restore my files?
dhruvasoni said:
how to make .tar file because backup file is .rfs format help me i want my imei back
Click to expand...
Click to collapse
Download the Tar Utility from GnuWin32's SourceForge Page.
Code:
hxxp://sourceforge.net/projects/gnuwin32/files/tar/1.13-1/tar-1.13-1-bin.exe/download
(change it to http)
It'll install the tar.exe executable and required dlls in C:\Program Files\GnuWin32\bin
Copy those to where you have your rfs (or you can add the bin folder to your PATH Environment Var, google for help on how to do that)
Now type:
Code:
tar -cf efs.tar efs.rfs
Yes, you can, just copy nv_data to /efs.
Windows users can use IZARC to create tar files.
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
burak721 said:
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
Click to expand...
Click to collapse
If you use a I5801 flash a stock firmware of 2.1...the same applies even if you use I5800...
Sent from my GT-I5800 using XDA App
i have done it but my imei is allways 00000000
pleas help
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
FadeFx said:
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
Click to expand...
Click to collapse
I have used fugomod kernel 2.4
Sent from my GT-I5800 using XDA App
my imei is also showing ooooooo.....plss help mee dudes plss
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
huzo said:
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
Click to expand...
Click to collapse
Pray ...
LOL good answer
[TOOL][LINUX] COPERFIELD ROM MAKER v.0.0.2
DOWNLOAD TOOL
Suport:
Samsung Galaxy S
Samsung Galaxy Tab 7.0
Samsung Galaxy SII I9100
Samsung Galaxy SIII I9300
Samsung Galaxy NoteI N7000
Samsung Galaxy Tab 7.7 P6800
Google Nexus 7
1. Required LINUX and Root access on the device ...
2. Enable debug mode on the device and connect the USB to the PC.
3. Extract the file from the archive with the tool to check just in case the right of scripts and binaries folder /tools - all must be executed ...
4. From the root folder of the tool to run in a terminal script menu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Configure the tool to claim 1 (necessary only once after the start of the tool):
6. Select the appropriate device, the program will create the device image of the system partition, download to PC and convert it to an image suitable for flashing Odin and put it in the out.
7. Select the package in the image archive .tar.md5 for flashing via Odin or fast boot (if necessary, may be placed in a folder out the rest of the ROM - the tool will pack them with the system image), enter the name new firmware and press Enter, the tool will create the firmware and display a report:
8. May be further packed in zip with maximum compression, to achieve the smallest size ...
9. The ability to create cache.img
10. Cache.img empty images in the folder empty (before flashing renamed cache.img)
the s2 and s3 system.img will be ext4 format ?
globula_neagra said:
the s2 and s3 system.img will be ext4 format ?
Click to expand...
Click to collapse
Of cause, kernels don't support different file systems...
Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
---------- Post added at 10:13 AM ---------- Previous post was at 09:15 AM ----------
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing
vijai2011 said:
Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
Click to expand...
Click to collapse
Yes, I do not mind
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing
Click to expand...
Click to collapse
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...
as i9000 said:
Yes, I do not mind
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...
Click to expand...
Click to collapse
I will pm you shortly with what I meant along with commands for you to understand it better
Sent from my GT-N7000 using xda app-developers app
Please can you help a noob - ROM seems extremely small
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .
plug_it_in said:
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .
Click to expand...
Click to collapse
You forgot step 5! configure tool, compile and install zlib and compile ext4_utils, and got empty image system.img...
is there a chance of a port to cygwin?
I like how the title says it supports any device and then the first post says it supports less than 10 devices.
Creating .tar.md5 will create images that increase binary counter ?
Edit:
Only with custom recovery
gianptune said:
I like how the title says it supports any device and then the first post says it supports less than 10 devices.
Click to expand...
Click to collapse
Sorry, it all my bad english, of cose isn't any but some...
I did chang it...
Is there any apps like this for W8??
Sent from my E16i using xda premium
Hi and thx for a great tool
1. Any chance when I run 6. that it stops when it is mounted and I can edit/add content in the output.img before it creates a system.img?
Would be nice to be able to edit before system.img
2. Possible to edit a factory system.img that I have on pc?
Thx for your time
Solution Found!: CWM Restore says "Couldn't open directory. No files found."
I used the Nexus 4 Toolkit to make a Nandroid backup. Now when I try to restore, it copies the files from my computer to the phone and then asks me to do a restore in CWM. However, when I click on Restore, it says: "Couldn't open directory. No files found."
It doesn't even give me the option to select the directory...
Ideas anyone?
RESOLVED!
[B]Solution: Install ROM Manager from Google Play. Open it and "Flash ClockWorkMod Recovery". It will install the latest CWM version. Then go to"Manage and Restore Backups" and you will find your *previously lost) backup there. If you don't see it, then reboot and open ROM Manager again. You can initiate a restore from within the ROM Manager app.
If you boot into Recovery and try to restore the nandroid backup, it will still not find it. But it will work from within the ROM Manager app. This is not an ideal solution but it works. [/B]
Re: Bogus Nexus 4 Toolkit- CWM Restore says "Couldn't open directory. No files found.
montrealguy said:
I used the Nexus 4 Toolkit to make a Nandroid backup. Now when I try to restore, it copies the files to the phone and then asks me to do a restore in CWM. However, when I click on Restore, it says: "Couldn't open directory. No files found."
It doesn't even give me the option to select the directory...
Ideas anyone?
Click to expand...
Click to collapse
The tool kit is to install the proper tools to your computer and phone so you can unlock bootloader, root, and install custom recovery from which you can perform nandroid backups and restore them when desired or necessary among many other options.????
Sent from my Nexus4, how's that feel?
Re: Bogus Nexus 4 Toolkit- CWM Restore says "Couldn't open directory. No files found.
OP, you're already talking about this in another thread. Why open a new one? You could have just edited the title of the other thread.
mustangtim49 said:
The tool kit is to install the proper tools to your computer and phone so you can unlock bootloader, root, and install custom recovery from which you can perform nandroid backups and restore them when desired or necessary among many other options.????
Click to expand...
Click to collapse
You are assuming that I am doing the backup and restore on the same phone. I made a Nandroid backup on my old Nex4 and want to restore on my new Nex4. The toolkit copies the Nandroid backup from my computer to sdcard/clockwordmod/backup, but CWM doesn't recognize it.
Furthermore, I tried to do a backup to find out where it stores them, and I couldn't figure it out!
Re: Bogus Nexus 4 Toolkit- CWM Restore says "Couldn't open directory. No files found.
montrealguy said:
You are assuming that I am doing the backup and restore on the same phone. I made a Nandroid backup on my old Nex4 and want to restore on my new Nex4. The toolkit copies the Nandroid backup from my computer to sdcard/clockwordmod/backup, but CWM doesn't recognize it.
Furthermore, I tried to do a backup to find out where it stores them, and I couldn't figure it out!
Click to expand...
Click to collapse
No I wasn't. I knew exactly what was going on before I made my previous post. The question stands.
estallings15 said:
OP, you're already talking about this in another thread. Why open a new one? You could have just edited the title of the other thread.
Click to expand...
Click to collapse
There are numerous older threads on this particular subject and none of them have a solution. Hopefully someone here will suggest an actual working solution and it will save everyone else a lot of endless searching...
Re: Bogus Nexus 4 Toolkit- CWM Restore says "Couldn't open directory. No files found.
montrealguy said:
There are numerous older threads on this particular subject and none of them have a solution. Hopefully someone here will suggest an actual working solution and it will save everyone else a lot of endless searching...
Click to expand...
Click to collapse
Please learn to use the edit button.
Re: Bogus Nexus 4 Toolkit- CWM Restore says "Couldn't open directory. No files found.
montrealguy said:
You are assuming that I am doing the backup and restore on the same phone........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Furthermore, I tried to do a backup to find out where it stores them, and I couldn't figure it out!
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk 2
Thanks guys! The problem was resolved and I updated the OP with the solution.
Thanks for the solution, it worked for galaxy s3. anyone stuck with not finding the restore file can try this out.
EFS BACKUP AND RESTOREfor
GALAXY GRAND i9082 and i9082L
DISCLAIMER: I am not responsible if you mess up your phone by following steps wrongly. This guide is to help you backup one of the most important partitions on your phone.
This is the FIRST THING that you should do after you root your Galaxy Grand i9082 or i9082L.
This method is ROM INDEPENDENT. It can be performed on any ROM.
Check post #2 below for the EFS BACKUP APP developed by me.
What is so important about EFS and why you SHOULD backup your EFS?
EFS is a system folder in the root directory of your phone that contains very important and basic information about your device's identity like Wi-Fi MAC address, Bluetooth MAC address and the MOST IMPORTANT - IMEI address (nv_data.bin).
Now if this EFS partition accidentally gets corrupted or erased, your phone’s IMEI number will get erased and your device will become completely useless and you won't be able to make voice call further, as the carrier network will not recognize your phone. This can happen for a variety of reasons, sometimes flashing a wrong or corrupted ROM. This kind of damage is not accepted by the service center. Only solution that the service center provides is to replace the motherboard of the device and that costs a lot of $$$!
Only a BACKUP of your EFS can save your phone if something goes wrong with your EFS partition.
(Some of you have already messed up your IMEI. Check Troubleshooting forum for details.)
Below is the correct and the safest method to backup your EFS folder. Copying the "/efs" directory to an external SD card using a root file manager is NOT the correct way as it will mess up the permissions when you restore it back.
NOTE: While some phones have (@k2wl), some of the phones (including mine and @DBZo07) don't have "nv_data.bin" in their "/efs" partition. Even though our IMEI are intact, but this file seems to be missing from "/efs". I am still looking into it as to why it is missing from EFS. I'll update the OP when i am more clear about the reason. Nonetheless, backing up EFS is still an important task and should be performed as soon as you get root permissions on your phone.
BACKUP
1. Open Terminal Emulator.
2. Type the following and press ENTER on your keyboard to grant Terminal Emulator SuperUser permission.
Code:
su
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Type the following and press ENTER on your keyboard (case sensitive - so type it just as it is written here)
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/sdcard0/efs.img bs=4096
If successfully executed, you will see something like this.
You will get "efs.img" file in your internal memory (sdcard0) of size 20 MB. Move this "efs.img" file to someplace safe - Laptop or Online backup so that it is readily available if you need it.
RESTORE
1. Make sure "efs.img" file is available in your internal memory (sdcard0).
2. Follow steps 1 and 2 from above to grant Terminal Emulator SuperUser permissions.
3. Type the following and press ENTER on your keyboard (case sensitive - so type it just as it is written here)
Code:
dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p17 bs=4096
4. Reboot
You'll have one thing less to worry before trying/flashing something new on your Galaxy Grand i9082.
Don't forget to press Thanks! :good:
Credits:
dr.ketan
EFS BACKUP AND RESTORE APPfor i9082 and i9082L
Developed by xenon92
DOWNLOAD
Reserved...
not working on me say cant open
10xian04 said:
not working on me say cant open
Click to expand...
Click to collapse
Can't open What?
Please elaborate when u post.
xenon92 said:
Can't open What?
Please elaborate when u post.
Click to expand...
Click to collapse
that
You spelled the partition WRONG!
Please make sure your spellings are correct and i have mentioned in OP that this is CASE SENSITIVE
It is "mmcblk0p17".
xenon92 said:
You spelled the partition WRONG!
Please make sure your spellings are correct and i have mentioned in OP that this is CASE SENSITIVE
It is "mmcblk0p17".
Click to expand...
Click to collapse
sorry my mistake it work thanks this is very helpfull..
I myself don't have nv_data.bin file in my /efs directory
Sent from my GT-I9082 using xda premium
xenon92 said:
You spelled the partition WRONG!
Please make sure your spellings are correct and i have mentioned in OP that this is CASE SENSITIVE
It is "mmcblk0p17".
Click to expand...
Click to collapse
Copy paste works..
It's very help bro.. thanks
To err is human; to forgive is divine
Glad i could help!
akiratoriyama said:
I myself don't have nv_data.bin file in my /efs directory
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Apparently, only @k2wl has it.
I hope others have it too.
You know this makes things tougher. Not having this file in "/efs" folder. We'll have to figure out other partitions which might contain this IMEI info (mk9efs). This is reference to the new S4 as other devs say that S4 has this info in those partitions.
I own a Note 2 too, and all the files are present under single partition of "/efs". Life is simpler with Note 2!
Can Grand owners confirm the nv_data.bin file in /efs directory ?
Sent from my GT-I9082 using xda premium
akiratoriyama said:
Can Grand owners confirm the nv_data.bin file in /efs directory ?
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Mine does not have that file also. But went ahead and backup efs using this method
Sent from my GT-N7000 using xda app-developers app
I9082l
backup - done
DangeloGH said:
I9082l
backup - done
Click to expand...
Click to collapse
i9082L?
I can't verify as i don't have the device with me. PM me, I'll tell you some steps that would help me verify that what you did was correct and i'll update the OP accordingly.
xenon92 said:
i9082L?
I can't verify as i don't have the device with me. PM me, I'll tell you some steps that would help me verify that what you did was correct and i'll update the OP accordingly.
Click to expand...
Click to collapse
ok...
i did not restore, cause im afraid that somethings maybe going wrong...]
sorrymy english.
@xenon92 since I dont have nv_data.bin so the backup method is useless for me?
Sent from my GT-N7000 using xda app-developers app
Thanks ! So back up should be done only in case of any issues ? Why are people trying to restore the device ?
People are experimenting. I dont want to restore myself since I dont have missing imei
Sent from my GT-N7000 using xda app-developers app
tharmor said:
Thanks ! So back up should be done only in case of any issues ? Why are people trying to restore the device ?
Click to expand...
Click to collapse
Backup is done BEFORE you face any issues so that you can RESOLVE your issues from the backup that you had when you were not facing any issues.
You DO NOT NEED TO RESTORE until you face some problem regarding EFS. You'll know when to use it when u face problems.