Develop Bugs

[Q] Extracting and Repairing CWM/Nandroid Backup

I recently recently backed up my phone (on midNIGHT ROM 5.3 EXT4 - Froyo EC05) using CWM 3.0.2.5. Then, I reformatted my phone to RFS to try out an Gingerbread EE05 ROM. Then, I Odin'd back to stock EC05 (RFS), reinstalling CWM with the One-Click method, and restoring my backup image. CWM keeps telling me that my boot images (even an image made previously) were having problems restoring after checking the MD5 Checksums.
I dig some digging and found an How-To for extracting the backup image:
[How-To] Extracting/Accessing Recovery/Nandroid backup (.img) files
Now for the questions:
1. I know that the backup images are somewhere on the SD card. Does anyone know the specific location?
2. Does anyone know of a way to repack the information (data.img / cache.img / system.img) into a proper backup image for restoration?
3. Does anyone know how to modify the backup image so that the MD5 checksums are proper once again?

The backups are under clockworkmod and then click backups. That is where your backups are stored
"The greatest respect you can earn is self respect" Louie Simmons

After checking in the backup sub-folders of clockworkmod, I see that the cache.img, data.img, and system.img are already separated. However, I also see a .android_secure.img file. What is that supposed to be used for?
Also, is there any way to change the accompanying nandroid.md5 file to properly restore with CWM? Is there any way to verify that it works aside from pure iteration in CWM?

if its failing the md5 check you dont need to mess with any of that its a simple fix
in a shell goto the disrectory of the backup
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
then after you run that you will be able to restore it in cwm
ohh and .android_secure is the apps stored on your sdcard

chris41g said:
if its failing the md5 check you dont need to mess with any of that its a simple fix
in a shell goto the disrectory of the backup
Code:
md5sum *img > nandroid.md5
then after you run that you will be able to restore it in cwm
ohh and .android_secure is the apps stored on your sdcard
Click to expand...
Click to collapse
Windows Command Prompt doesn't recognize md5sum as a command. Do I need a program in that same directory for working on the md5 file?

Dante of the Inferno said:
Windows Command Prompt doesn't recognize md5sum as a command. Do I need a program in that same directory for working on the md5 file?
Click to expand...
Click to collapse
in a shell on your phone...
from a windows shell c:\whatever\>
Code:
adb shell
then from the shell on your phone $
Code:
cd /sdcard/clockworkmod/backup/whateverbackup/
md5sum *img > nandroid.md5

I downloaded a shell terminal onto the phone, navigated to the backup, and input the code. It paused for a minute, but seemed to do its thing. I shut down the phone, went into CWM, cleared the data, cache, and Dalvik, and hit the restore option for the proper backup. This is what follows.
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Any other ideas? If worst comes to worst, the only thing worth saving would be the apps themselves. So should I focus on extracting the apps out of the .android_secure image?

Do advanced restore, that's not a 3.0.25 backup so advanced restore each part individually
Sent from my SPH-D700 using XDA App

Dante of the Inferno said:
I downloaded a shell terminal onto the phone, navigated to the backup, and input the code. It paused for a minute, but seemed to do its thing. I shut down the phone, went into CWM, cleared the data, cache, and Dalvik, and hit the restore option for the proper backup. This is what follows.
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Any other ideas? If worst comes to worst, the only thing worth saving would be the apps themselves. So should I focus on extracting the apps out of the .android_secure image?
Click to expand...
Click to collapse
Are you using 3-finger method to boot into CWM?

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.

Thanks... a very useful guide. Bookmarked

WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!

I keep getting "md5sum: not found"

Put this in the general android section as it works across most devices. ..
Sent from my One V

Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.

I fixed it in adb
Sent from my SPH-L710 using xda premium

Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!

thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.

i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone

haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7

unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup

CWM showing different versions
-Delete-

maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out

Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app

Thank you so much. You saved my phone.

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)

plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

Looking for Android v4.0 ROM

Hello,
I am looking for original ROM Android version 4.0 or something.
I was searching it but I didn't found.
Actually I have 4.1.1 and I need older version because have to check how will be work my dock station (HTC CR S650) with older versions.

http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using xda premium

drali500 said:
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks mate.
I don't understand step #5. What does it mean "copy the boot.img in the folder that you prefer"?
1- Go into Recover (CWM) and Mount USB
2- Now From your PC create a folder in the root of the storage and call it "clockworkmod"
3- In the "clockworkmod" folder create another folder named "backup"
4- Extract the .zip file in that folder (do not change the name of the folder extracted cause it could give md5sum problems)(also the folder name must not have any space between words)
5- Before continuing on the phone, open that folder from the pc and copy the boot.img in the folder that you prefer
6- Reboot phone into Fastboot mode and flash the boot.img by typing
Code:
fastboot flash boot path/to/boot.img
7- Reboot the phone into Recovery again
8- Go to Backup & Restore> restore> and here choose the folder previously extracted, and that's it

ZaKooN said:
Thanks mate.
I don't understand step #5. What does it mean "copy the boot.img in the folder that you prefer"?
1- Go into Recover (CWM) and Mount USB
2- Now From your PC create a folder in the root of the storage and call it "clockworkmod"
3- In the "clockworkmod" folder create another folder named "backup"
4- Extract the .zip file in that folder (do not change the name of the folder extracted cause it could give md5sum problems)(also the folder name must not have any space between words)
5- Before continuing on the phone, open that folder from the pc and copy the boot.img in the folder that you prefer
6- Reboot phone into Fastboot mode and flash the boot.img by typing
Code:
fastboot flash boot path/to/boot.img
7- Reboot the phone into Recovery again
8- Go to Backup & Restore> restore> and here choose the folder previously extracted, and that's it
Click to expand...
Click to collapse
That means to copy it in a folder from which you will perform step 6. To make your life easier, I usually copy it in the same folder where I keep fastboot and adb files.
In that case you should only type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Good luck! :good:

[email protected]|-|oR said:
That means to copy it in a folder from which you will perform step 6. To make your life easier, I usually copy it in the same folder where I keep fastboot and adb files.
In that case you should only type:
Good luck! :good:
Click to expand...
Click to collapse
And when I want to back to my original Android (had made nand backup) I just doing the same but with mine files?

ZaKooN said:
And when I want to back to my original Android (had made nand backup) I just doing the same but with mine files?
Click to expand...
Click to collapse
Which nandroid you have?
4.1.1?
If so, then yes, repeat the procedure once again with your bakup to return to Jelly Bean.
One more thing, make sure that the nandroid you download is named with date and time (something like "2013-01-28.08.49.48"), otherwise you will face md5 issue. There is a solution for that, too, but I don't know if you would do it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:10 PM ----------
Here you are, the full explanation is HERE.
In particular check this explanation:
What if i get MD5 Mismatch?
type in teminal:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/Name_of_the_nandbackup_folder
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse

[email protected]|-|oR said:
Which nandroid you have?
4.1.1?
If so, then yes, repeat the procedure once again with your bakup to return to Jelly Bean.
One more thing, make sure that the nandroid you download is named with date and time (something like "2013-01-28.08.49.48"), otherwise you will face md5 issue. There is a solution for that, too, but I don't know if you would do it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:10 PM ----------
Here you are, the full explanation is HERE.
In particular check this explanation:
Click to expand...
Click to collapse
Damn I downloaded it but there is MAC OSX folder...
Look on the image, it is correct or I have to find another ROM?

ZaKooN said:
Damn I downloaded it but there is MAC OSX folder...
Look on the image, it is correct or I have to find another ROM?
Click to expand...
Click to collapse
It looks alright. You have your cache, data, and system partitions in it.
And, I was right - you will get MD5 mismatch, for sure! So, you will have to follow the instruction that I indicated before.
If it doesn't work, or you are having problems, keep your current boot.img handy, and give it a try. You can always revert to your previous state.
What is in this Mac OS folder?

[email protected]|-|oR said:
It looks alright. You have your cache, data, and system partitions in it.
And, I was right - you will get MD5 mismatch, for sure! So, you will have to follow the instruction that I indicated before.
If it doesn't work, or you are having problems, keep your current boot.img handy, and give it a try. You can always revert to your previous state.
What is in this Mac OS folder?
Click to expand...
Click to collapse
There is file: nandroid.md5
So I should keep the boot.img file in that folder?

ZaKooN said:
There is file: nandroid.md5
So I should keep the boot.img file in that folder?
Click to expand...
Click to collapse
If you copy boot.img files into your "fastboot" folder, then it's easier to type the command. Instead of:
fastboot flash boot c:/user/somebody/something/.../folder/boot.img
Click to expand...
Click to collapse
all you do is type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Less possibility for error.
You can place both boot.img files to this folder, only name them in a way you can recognize them in future (boot_my.img and boot_old.img, for example).
I would also check if nandroid.md5 is the same as the one in parent folder. But, anyhow, you will have to adjust your md5, I'm sure of it.

[email protected]|-|oR said:
If you copy boot.img files into your "fastboot" folder, then it's easier to type the command. Instead of:
all you do is type:
Less possibility for error.
You can place both boot.img files to this folder, only name them in a way you can recognize them in future (boot_my.img and boot_old.img, for example).
I would also check if nandroid.md5 is the same as the one in parent folder. But, anyhow, you will have to adjust your md5, I'm sure of it.
Click to expand...
Click to collapse
I am flashed new ROM but in options still have 4.1.1 version, just see the telephone was return to fabric options

ZaKooN said:
I am flashed new ROM but in options still have 4.1.1 version, just see the telephone was return to fabric options
Click to expand...
Click to collapse
Search for "2.17.xxx.xx" nandroid. That is ICS ROM (4.0.3 or 4.0.4).

[email protected]|-|oR said:
Search for "2.17.xxx.xx" nandroid. That is ICS ROM (4.0.3 or 4.0.4).
Click to expand...
Click to collapse
Damn Why you didn't wrote it earlier?
Downloading now and we will see

ZaKooN said:
Damn Why you didn't wrote it earlier?
Downloading now and we will see
Click to expand...
Click to collapse
I thought you knew what you're doing
No worries, just be patient, and keep your battery charged! :good:

AW: Looking for Android v4.0 ROM
Why did you open 2 threads for this?
Sent from my HTC One X using xda app-developers app

psyko93 said:
Why did you open 2 threads for this?
Click to expand...
Click to collapse
I think he ffirst opened one in Original Development forum, where he was advised to ask for help elsewhere. Then he opened this thread, and then mods moved his first thread here.
You are right, one of them should be closed/deleted.

[email protected]|-|oR said:
I think he ffirst opened one in Original Development forum, where he was advised to ask for help elsewhere. Then he opened this thread, and then mods moved his first thread here.
You are right, one of them should be closed/deleted.
Click to expand...
Click to collapse
Okay new ROM is flashed but I can't insert PIN code because of screen didn't react on touch, just power button is working

ZaKooN said:
Okay new ROM is flashed but I can't insert PIN code because of screen didn't react on touch, just power button is working
Click to expand...
Click to collapse
Try going back to fastboot and typing:
fastboot erase cache
Click to expand...
Click to collapse
After that go to recovery, and do wipe dalvik cache. Reboot. See if it works.

[email protected]|-|oR said:
Try going back to fastboot and typing:
After that go to recovery, and do wipe dalvik cache. Reboot. See if it works.
Click to expand...
Click to collapse
Nope, still the same situation

ZaKooN said:
Nope, still the same situation
Click to expand...
Click to collapse
Hmmmm, mate, I don't know about this.
Could you try flashing back your own nandroid and see if that's the ROM, or something else?

[Tools][How-To][Guides] Backup & Restore EFS + Get out from Permanent Safe mode

Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
{
"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"
}
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9500 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
CWM / PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing XWUBMG5, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on older version, recommended is XXUBMG9(right to 05/08/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
You will find at least one method that works on your device, so don't give up after one method.
Note II & S4 has the same EFS partition (mmcblk0p3), All methods were checked by me on my Note II and fully work. So it should work on S4 too. At least 90% of them
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
Original thread:
http://forum.xda-developers.com/showthread.php?t=2430177&nocache=1&styleid=19
The software:
A.S._id said:
SAMSUNG_I9500_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access, debugging USB and busybox
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
p.s. * Deposit assured recovery - to have the device firmware version corresponding to the backup copy
Click to expand...
Click to collapse
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Then click enter.
When it finishes, check if you have efs.img on your phone memory. If so, copy it to comupter, if not, you did something wrong try again.
Click to expand...
Click to collapse
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Download this and copy it to your device:
http://d-h.st/f4I
Reboot into recovery
Flash the zip
Reboot your device.
Connect your device to your pc, and copy the backup in "efs_backup" folder.
Click to expand...
Click to collapse
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
With root explorer, go to your efs folder and delete all files inside
Long press on power button will turn off your device.
Then turn on the device, you will be in "Permanent Safe Mode".
Continue to one of the following methods.
Click to expand...
Click to collapse
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
Original thread:
http://forum.xda-developers.com/showthread.php?t=2430177&nocache=1&styleid=19
The software:
A.S._id said:
SAMSUNG_I9500_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access, debugging USB and busybox
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
p.s. * Deposit assured recovery - to have the device firmware version corresponding to the backup copy
Click to expand...
Click to collapse
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
Then click enter.
Now, reboot your device. If you still don't have IMEI/You are still in Safe Mod, reboot again.
In the second reboot, the bootanimation might stuck and the device will reboot automatically again. Don't worry, it is ok because it installs your efs.img.
Click to expand...
Click to collapse
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Download this script & copy it to your device:
http://d-h.st/XcL
Reboot into recovery
Go to mount section and click on(Very important!):
Mount /efs
Click to expand...
Click to collapse
Now install the script you have downloaded.
After it finishes, reboot.
Now everything should be fixed, of course if your backup is 100% ok.
If it doesn't work, try method 4.
Click to expand...
Click to collapse
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Reboot device.
Click to expand...
Click to collapse
Method 2
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Click to expand...
Click to collapse
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode I9500, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05

Awesome my friend 5 stars hit, I will link you in my post.
I hope people read in detail and take precautions
Hugs
Sent from my GT-I9500

Crash 1976 said:
Awesome my friend 5 stars hit, I will link you in my post.
I hope people read in detail and take precautions
Hugs
Sent from my GT-I9500
Click to expand...
Click to collapse
Thank you my friend,
In my note II I did like 20 backups before I deleted my EFS folder around 20 times ahah.
People should be aware that samsung is trying to mess up our devices.

Thank you Tarmida, This is the best userful topic ever for my S4 :good:. This will saving many lives of XDA member :good:

Excellent my friend tamirda! :good:
regards!
5 stars! and sticky please!

great topic and guide tamir.5 stars from me :thumbup: will help me a lot if i get stuck with any prob like before arghhhh
Sent from my GT-N7000 using Tapatalk 2

galza said:
great topic and guide tamir.5 stars from me :thumbup: will help me a lot if i get stuck with any prob like before arghhhh
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I am happy to help you any time
» Arrow « said:
Excellent my friend tamirda! :good:
regards!
5 stars! and sticky please!
Click to expand...
Click to collapse
Thank you friend!
bafknight said:
Thank you Tarmida, This is the best userful topic ever for my S4 :good:. This will saving many lives of XDA member :good:
Click to expand...
Click to collapse
Thank you friend, and yes this can be very useful for alot of users.
Sent from my GT-N7100 using xda app-developers app

@tamirda
Hi I'm using crash rom 5.5
I made full wipe and flash MG5
By odin and now I have fake imei
I restore crash rom 5.5 backup from cwm and the problem still exsist
I don't make EFS backup before
How to fix it ?
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams

AL_IRAQI said:
@tamirda
Hi I'm using crash rom 5.5
I made full wipe and flash MG5
By odin and now I have fake imei
I restore crash rom 5.5 backup from cwm and the problem still exsist
I don't make EFS backup before
How to fix it ?
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
Click to expand...
Click to collapse
Hello,
It seems that crash backuped your Fake IMEI.
Something that I thing it might help, helped for some other, download latest modem from here:
http://forum.xda-developers.com/showthread.php?t=2192025
install it as a Phone in Odin.
it is importand to mark phone, and flash via odin.
Then try..
If you don't have any other backup, I think you might have to use your warranty.

When I backup the rom I forget my phone in flight mode maybe this the reason why I lost my imei ?
And my baseband now is
I9500DDUBMF8
+Edit
I found these in my internal storage
The First One From Crash Rom 5.0
And The Second From Stock MG5 Where I have fake imei
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams

AL_IRAQI said:
When I backup the rom I forget my phone in flight mode maybe this the reason why I lost my imei ?
And my baseband now is
I9500DDUBMF8
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
Click to expand...
Click to collapse
I don't think there is connection between these two.
Downlaod this:
http://d-h.st/esG
Open odin, Select Phone, select the modem's tar, connect phoen and flash.
After that check if you have IMEI.
If not, Try to install stock XXUBMG9 or XXUBMG5 - If you had MG5 before, it seems that you can not downgrade your phone, so try to install MG5.
If after MG5 there is still no IMEI,
Flash again as Phone via odin this modem:
http://d-h.st/Xxk
If still there is no IMEI, try to restore your current EFS backup.(Make sure you have Root and busybox and all I asked in the main thread)
If after that no IMEI,
Restore to stock and use warranty( make a story that you woke up one morning and you couldn't conect to your network, and you tried to mnake factory reset and still it didn't help)
Good luck

tamirda said:
I don't think there is connection between these two.
Downlaod this:
http://d-h.st/esG
Open odin, Select Phone, select the modem's tar, connect phoen and flash.
After that check if you have IMEI.
If not, Try to install stock XXUBMG9 or XXUBMG5 - If you had MG5 before, it seems that you can not downgrade your phone, so try to install MG5.
If after MG5 there is still no IMEI,
Flash again as Phone via odin this modem:
http://d-h.st/Xxk
If still there is no IMEI, try to restore your current EFS backup.(Make sure you have Root and busybox and all I asked in the main thread)
If after that no IMEI,
Restore to stock and use warranty( make a story that you woke up one morning and you couldn't conect to your network, and you tried to mnake factory reset and still it didn't help)
Good luck
Click to expand...
Click to collapse
Thanks I'll Try These Method
If not working I'll use my warranty
EDIT
I directly flash I9500_UBUBMG9_MODEM
And know it's work fine with me
I Should Try it before ask sorry for that
this is the first time I have this problem
Thank you very much
Sent From my i9500 With Crash Rom

AL_IRAQI said:
Thanks I'll Try These Method
If not working I'll use my warranty
EDIT
I directly flash I9500_UBUBMG9_MODEM
And know it's work fine with me
I Should Try it before ask sorry for that
this is the first time I have this problem
Thank you very much
Sent From my i9500 With Crash Rom
Click to expand...
Click to collapse
Hi mate,
First of all,
I am more than happy that I helped you.
Second, this is ok to ask questions, that is why I am here.
Now backup at leat 5 times your EFS .img & tar.gz.
Enjoy!

tamirda said:
Hi mate,
First of all,
I am more than happy that I helped you.
Second, this is ok to ask questions, that is why I am here.
Now backup at leat 5 times your EFS .img & tar.gz.
Enjoy!
Click to expand...
Click to collapse
I backup 3 times with every method
Thanks
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams

Awesome guide.
Burned up whole weekend over the issue and now fixed my issue following the guide.
Cannot thank you enough man!
Regards,
Pdash

pdash79 said:
Awesome guide.
Burned up whole weekend over the issue and now fixed my issue following the guide.
Cannot thank you enough man!
Regards,
Pdash
Click to expand...
Click to collapse
I am happy to help & hear that you succeed in restoring IMEI.
Sent from my GT-N7100 using xda app-developers app

I read your post, all most the method use terminal emulator, so what is that ?, and can you give me link of that ?
thanks you very much

daogiahieu said:
I read your post, all most the method use terminal emulator, so what is that ?, and can you give me link of that ?
thanks you very much
Click to expand...
Click to collapse
Linux command line shell on Android. Here's it, mate https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=vi

Thanxs @tamirda
I could see everyday a new post related to messed up EFS folder.
It would surely help people out
Anyhow i had already backed up mine using the EFS professional Software. Is it enough or should i backup using your methods also?

manu44 said:
Thanxs @tamirda
I could see everyday a new post related to messed up EFS folder.
It would surely help people out
Anyhow i had already backed up mine using the EFS professional Software. Is it enough or should i backup using your methods also?
Click to expand...
Click to collapse
I think it is enough, depands on your feeling

[Q] SIM not recognized - Help needed

Hi
My wife bought a Note 2 (N7100) in China, second hand. I thought it was stock, so I tried to update it manually (official update) with Odin. But of course it was rooted and with some chinese ROM (my guess since I saw chinese charachters).
That didn't work so I proceeded to install a custom rom. After trying over and over, my phone would not recognise the SIM no longer (it worked before I started out with this mess). I have basically tried installing multiple roms (4.1, 4.3, 4.4), Odin fails when trying offical roms, multiple modem zips etc. Dont know what to do.
Problem is that I can not get the PCode because there is no connection with the SIM. IMEI is on the back of the phone, but trying *272*#IMEI-code# doesn't give me nothing because i just get fail. Trying to download a official rom from china over baidu.com, but until now no luck. What would you do? Right now its a phablet with wifi, nothing else. Anyone have an idea how to fix this little mess I put myself into?

Flash custom recovery and TRY THIS method in ADB.
Confirm if they have the same efs address though, but I think it's the same.

cz4r3n said:
Flash custom recovery and TRY THIS method in ADB.
Confirm if they have the same efs address though, but I think it's the same.
Click to expand...
Click to collapse
Looks like my /efs/ partition is zero, nill nothing. What to do? Use it as a wifi phablet? I dont have linux, only mac, so I cant do these two steps, but I guess it does not matter since I can not open the efs.img file
linux# losetup /dev/loop0 efs.img
linux# fsck /dev/loop0
So the phone is impossible to fix now - right? /efs/ folder on phone is emtpy.

Found my IMEI number for this phone on Google Dashboard. Is it possible to restore the EFS image only using that?

mikasjoman said:
Found my IMEI number for this phone on Google Dashboard. Is it possible to restore the EFS image only using that?
Click to expand...
Click to collapse
Did you ever have a backup on your efs?If yes, then restore it.there are so many threads on how to restore your efs.
---------- Post added at 07:55 PM ---------- Previous post was at 07:44 PM ----------
mount efs in adb.
adb shell
su
mount
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.bin
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
dd if=/sdcard/mmcblk0p3.bin of=/dev/block/mmcblk0p3
mmcblk0p3.bin

That is a no Or maybe. I made a copy to my harddrive with those instructions you linked to. Could I email the efs.img file to you and you check if its usable? Maybe it is just corrupt. I really don't know how to figure it out on this mac. If it was empty it should not be the 21 MB it is.
I did a "cat" on the efs.img file and it seems full of info.
Being the poor student I am, I wont be able to buy a new phone in some time