I renamed a nandroid backup once so that id remember which one it is but when i tried to restore it, it said MD5 mismatch or something like that. How do i rename it without messing up the MD5?
android1234 said:
I renamed a nandroid backup once so that id remember which one it is but when i tried to restore it, it said MD5 mismatch or something like that. How do i rename it without messing up the MD5?
Click to expand...
Click to collapse
From what I understand you shouldn't rename them. Use rom manager to edit the names of backups.
For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS
Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs
Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2
Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?
Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now
jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..
stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium
vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium
jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.
vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Does K-Tool work with CF-Root kernel?
HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar
Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there
good evening everyone
strate after the rom file I copy the folder to SD / ClockworkMod / backup
I open the recovery but get an error "incompatible MDL5"
What am I doing wrong?
someone I can spend more installation details?
I've been the last Rom Cyanogen ICS
Thanks
Try downloading the files again and try to restore with the freshly downloaded nandroid backup, perhaps some files just got messed up and corrupted along the way. And should it be md5 not mdl5? Maybe you could check the files on your pc and rename it
Sent from my A953 using xda premium
DreadPirateDan said:
Try downloading the files again and try to restore with the freshly downloaded nandroid backup, perhaps some files just got messed up and corrupted along the way. And should it be md5 not mdl5? Maybe you could check the files on your pc and rename it
Sent from my A953 using xda premium
Click to expand...
Click to collapse
no results, I dowload the files and nothing shows up in five CDM fund and complete the final task appears in 5 seconds any ideas?
Is there anyway i can rename the rom backups i create in clockworkmod. Every time i try and rename it fails to restore the renamed back up. thank you.
raziruelas said:
Is there anyway i can rename the rom backups i create in clockworkmod. Every time i try and rename it fails to restore the renamed back up. thank you.
Click to expand...
Click to collapse
Unfortunately cwm does not support this, as when you change the filename or folder name it messes up the md5 sums.
raziruelas said:
Is there anyway i can rename the rom backups i create in clockworkmod. Every time i try and rename it fails to restore the renamed back up. thank you.
Click to expand...
Click to collapse
jwchips said:
Unfortunately cwm does not support this, as when you change the filename or folder name it messes up the md5 sums.
Click to expand...
Click to collapse
It's true, what I do is to create a text file in the same folder, and add every rom backup name with an my own suitable name.
jwchips said:
Unfortunately cwm does not support this, as when you change the filename or folder name it messes up the md5 sums.
Click to expand...
Click to collapse
That's not the truth!
Renaming backup folder doesn't have anything todo with md5 sums. This is only ckecking .img and .tar files inside backup folder (this one with date and time).
Renaming folder with date and time stamp is SAVE. I do this after every backup with total commander on my PC and never had any issues.
Do NOT rename "clockworkmod" and "backup" folder, otherwise CWM will not find your backups.
icke said:
That's not the truth!
Renaming backup folder doesn't have anything todo with md5 sums. This is only ckecking .img and .tar files inside backup folder (this one with date and time).
Renaming folder with date and time stamp is SAVE. I do this after every backup with total commander on my PC and never had any issues.
Do NOT rename "clockworkmod" and "backup" folder, otherwise CWM will not find your backups.
Click to expand...
Click to collapse
I thought it didn't sound right when I was typing it, but it was my understanding of the issue. Do you mean rename folder while retaining the date created/modified timestamps? I'm a little confused as the default folder names for backups are date/timestamps.
U do not have to retaining the date/time stamp.
U can label it what ever U want.
"Typhoon" or "ICTosti_v.0.10" (without quotations) is for example what I label my backups.
But make sure there are no spaces in folder name!
There's a small bug in CWM that causes it to report a MD5 checksum error whenever it cannot find the md5 file. This can happen, for example, if you rename the folder to a new name which contains spaces. I consider it a bug because it should not say "MD5 checksum error", it should say "Unable to find MD5 file".
Anyhow, if you just rename the folder to a name (any) that does *not* contain any spaces, CWM will be able to restore it.
Hello
I rooted my phone using hardcore's speedmod kernel as shown in the CyanogenMod webpage and then inmediately backed up the /efs folder doing a tar using an Android Terminal Emulator
However, the MD5 files information don't match the files themselves
For example
The MD5 string contained in .nv_data.bak.md5 doesn't match .nv_data.bak
The same for the other files as well.
Is my /efs corrupted? My phone has never been touched before, just stock roms applied thru Kies
I have noticed a new folder has popped up in the /efs folder called "lost+found". Why did it go there?
Do yu have another suggestion to backup the /efs as well? seems doing tarballs looses UNIX/Linux permissions
Thank you.
resotre only one file and reboot
albertocastillo2001 said:
Hello
I rooted my phone using hardcore's speedmod kernel as shown in the CyanogenMod webpage and then inmediately backed up the /efs folder doing a tar using an Android Terminal Emulator
However, the MD5 files information don't match the files themselves
For example
The MD5 string contained in .nv_data.bak.md5 doesn't match .nv_data.bak
The same for the other files as well.
Is my /efs corrupted? My phone has never been touched before, just stock roms applied thru Kies
I have noticed a new folder has popped up in the /efs folder called "lost+found". Why did it go there?
Do yu have another suggestion to backup the /efs as well? seems doing tarballs looses UNIX/Linux permissions
Thank you.
Click to expand...
Click to collapse
I had same problem when I install jelly bean first time on my I9000. After reading of some articles about efs folder I decided to restore only one file .nv_data.bak. And it works. I have done in following steps.
1) Backup full efs folder. (For safty purpose only)
2) Deleted both files nv_data.bin.md5 & nv_data.bin
3) Restored nv_data.bin only (No need to put back md5 file)
4) Restart the phone
Let me know if it works.
Hello
My phone works. It's just I have noticed the backup I made at the beginning just after I rooted my phone don't match. But the backup itself.
The backup files don't match their own .MD5 in the backup itself
Thanks!
Any ideas of why these files don't match?
albertocastillo2001 said:
Hello
My phone works. It's just I have noticed the backup I made at the beginning just after I rooted my phone don't match. But the backup itself.
The backup files don't match their own .MD5 in the backup itself
Thanks!
Click to expand...
Click to collapse
Hello
I've also checked that once in a while, some of the files inside /efs such as nv_data.bin and nv_data.bin.md5 change their modified date.
Any idea of why this happens and why the MD5 data doesn't match?
Thank you.