I saw many people getting md5 mismatch while doing backup. So, I wrote this thread to help them.
Today I am going to share with you a method of restoring backups easily without an md5 error.
1ST METHOD:
Here are the steps:
1)Go to the folder where you saved your backup.
2)Open nandroid.md5 file with any text editor on your phone.
3)Delete all the lines from starting to end.
4)Save the file and close it.
5)Now restore your backup through CWM or Philz Touch or TWRP.
2ND METHOD:
If you changed the name of the backup folder, then, that is causing the problem. Try to change the name without adding spaces and/or special characters.
3RD METHOD:
Also you can use nandroid manager to recreate md5 sums.
Link in the next post by akiratoriyama
Thanks to @akiratoriyama
Or if you don't want to use nandroid manager, then you can use terminal emulator to recreate those sums:
Open terminal emulator then,
Use the following commands. (DON'T FORGET TO REPLACE "2012-04-17.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME)
su
# mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
Don't forget to put the spaces!!
Voila, now your backup will restore properly without any md5 error:beer:
Sent from my GT-I9082 using Tapatalk Pro
Ateekujjawal said:
I saw many people getting md5 mismatch while doing backup. So, I wrote this thread to help them.
Today I am going to share with you a method of restoring backups easily without an md5 error.
1ST METHOD:
Here are the steps:
1)Go to the folder where you saved your backup.
2)Open nandroid.md5 file with any text editor on your phone.
3)Delete all the lines from starting to end.
4)Save the file and close it.
5)Now restore your backup through CWM or Philz Touch or TWRP.
2ND METHOD:
If you changed the name of the backup folder, then, that is causing the problem. Try to change the name without adding spaces and/or special characters.
Voila, now your backup will restore properly without any md5 error:beer:
Sent from my GT-I9082 using Tapatalk Pro
Click to expand...
Click to collapse
Alternate method
Use Nandroid Manager to recreate md5 sums
Sent from my GT-I9082 using Tapatalk
i tried the first method and it works for me
i cant backup my rom
i tried flashing the zip version of the s4 launcher and widget on my sgg-gt i-9082,,as instructed i backed up my stock rom but it didnt complete the backup..when i tried restoring the rom i get the error "md5 mismatch"..i wanted to try the methods youve posted but i cannot locate the nandroid.md5 file...i tried to install the touchwiz.apk (both in the system and user option) but the app just closes"unfortunately touchwiz has stopped working"..
so i have these questions:
1.is there a way i can still resore my stock rom?
2.i was running on jb 4.1.2..if i download the 4.2.2 update from the samsung website and flash my phone..wil i hav my touchwiz back?coz i dont like the holo launcher thaaaat much..
i'd be grateful for your help..
g_javella said:
i tried flashing the zip version of the s4 launcher and widget on my sgg-gt i-9082,,as instructed i backed up my stock rom but it didnt complete the backup..when i tried restoring the rom i get the error "md5 mismatch"..i wanted to try the methods youve posted but i cannot locate the nandroid.md5 file...i tried to install the touchwiz.apk (both in the system and user option) but the app just closes"unfortunately touchwiz has stopped working"..
so i have these questions:
1.is there a way i can still resore my stock rom?
2.i was running on jb 4.1.2..if i download the 4.2.2 update from the samsung website and flash my phone..wil i hav my touchwiz back?coz i dont like the holo launcher thaaaat much..
i'd be grateful for your help..
Click to expand...
Click to collapse
No way to restore stock rom. You didn't complete the backup.
Yes you can flash 4.2 to get TouchWiz back.
Sent from my GT-I9082 using Tapatalk Pro.
Ateekujjawal said:
No way to restore stock rom. You didn't complete the backup.
Yes you can flash 4.2 to get TouchWiz back.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
thank you so much....
i tried the nandroid manager method and it worked..turns out my data was the one that didnt fully backup...i lost some-most-of my data but its better than losing my rom--...
thanks again..you are a life saver..
Related
Hi guys,
Once again, thanks to MartinEve and the whole unrevoked team for the work they've made on Wildfire rooting.
I've just used unrevoked to root my wildfire. Seems alright cause :
> id cmd tells I'm root
> titanium backup tells root permission is given
Cool
But... I try to do a nandroid backup from the clockworkmod recovery and it says : "Error while dumping boot image!"
Do you have any idea ?
Thx a lot
Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.
mmr41 said:
Solved...
It was due to a problem on my sdcard (was not able to write in the /sdcard folder even from windows). I had to delete some files and then nandroid backup was available.
Click to expand...
Click to collapse
Why dont you post your problem and its solution here for others to benefit from it
http://forum.xda-developers.com/showthread.php?t=742518
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Tasssadar said:
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Click to expand...
Click to collapse
Thank you for your help but I'm using clockworkmod recovery. What do i need to change in that command to suit CWM?
Matty Matt said:
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
Click to expand...
Click to collapse
Haha, I thought I was the only one! I thought I had partitioned my card somehow. I basically did the same thing as you. I also am running CWM. Its making Rom flashing almost impossible for me, I can only select & flash files from the SD "O". All my nandroids are on the regular SD selection. Did you ever find you answer Matt.?
Sent from my Nexus 7 using Tapatalk 2
Folks,
I had some free time on the weekend and tried some ROMs on my new Nexus. I use one of the newer versions of CWM as Recovery and of course did always a backup before flashing something new, ended up with five of them.
The problem is now that I am not able to restore any of them due to the known md5 mismatch error.
All the tutorials and videos in the inet for solving this issue are based on the ‘older’ cwm structure where you find the backup under /sdcard/clockworkmod/backup where we used to have the five files
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
system.ext4.tar
The ‘newer’ CWM is different, the backups are obviously splitted and following /data/media/clockwordmod we have the folders ‘backup’ and ‘blobs’. In the backup folder I now have:
boot.img
recovery.img
system.ext.dup
My initial idea was to use the Terminal Emulator app and to create a new nandroid.md5 with following commands:
su
cd /data/media/clockworkmod/backup/*nameofhtebackup*
rm nandroid.md5
md5sum *img > nandroid.md5
Before I continue with above procedure I thought it would be a good idea to ask you guys and experts if I am on the right track? Needs the nandroid.md5 to be in that ‘new’ backup folder at all?
And another question: as my Nexus is so new and there is only quite few stuff on it yet – maybe it would be better to start from scratch and get rid of CWM and and use TWRP instead?
Any assistance is highly appreciated!! ThX
Yes! I was about to suggest that you scrap CWM, Team Win is much more stable. And just so you know, you can actually use CWM backups with TWRP so there's no need to start over
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 07:42 AM ---------- Previous post was at 07:38 AM ----------
There's also an option in the TWRP restore menu that allows you to 'skip MD5 check' so you won't be experiencing that again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
the easiest way is to open the .md5 file in a text editor, remove all the data from it and save it. This way CWM bypasses md5 check
same
renjithrs007 said:
the easiest way is to open the .md5 file in a text editor, remove all the data from it and save it. This way CWM bypasses md5 check
Click to expand...
Click to collapse
I also have the same problem. I used cwm touch to backup. unlike old cwm backup, the backup showed backup folder and blobs folder. when i tired to restore, it showed md5 mismatch. I have no clue how to proceed. how u guys from above solved the problem?
Hi
I did a backup with nexus 4 toolkit before rooting but now when I try to restore my backup it starts backing up but just 1 app and then reeboots without adding any of the other apps. Anyone know an alternate method or whats wrong?
c2h5oh2 said:
Hi
I did a backup with nexus 4 toolkit before rooting but now when I try to restore my backup it starts backing up but just 1 app and then reeboots without adding any of the other apps. Anyone know an alternate method or whats wrong?
Click to expand...
Click to collapse
thats reason # 84261 why you should never use a toolkit.
Well, whats done is done. It seems like it tries to recover some system file that causes a reebot. I will try to restore from recovery mode if the bootloader can restore .ab-files.
Failed to restore .ab file in bootloader. Does anyone have any idea how I can restore the .ab file?
Why would you want to go back to stock? You want to get back the apps you had?
I guess you will have to re-download them... This is what I did : I made a Titanium backup save for my apps, before rooting, and restored it, after rooting.
To restore .ab files install adb and open a command window (or a terminal on linux). Then navigate to the folder where the .ab file is or open the command window there. Connect your phone now powered on to your PC and be sure unknown sources and usb debugging are enabled
Now type
Code:
adb restore nameofyourbackup.ab
Unlock your device, confirm the restore and wait until it has finished
Sent from my Nexus 4 running Android 4.2.2
I shouldn't have used a toolkit :S
I'm having the same issue, I used the toolkit, created a backup from all apps (including system and data) in a .BAK, unlocked, rooted, and now I try to restore with the toolkit, the process triggers my phone's backup but then it restarts and nothing has been restored! I tried HOLO Backup as well, and I'm trying with the SDK method right now.
Is .BAK compatible with full backup? Is there any other way (other than ADB) to restore my info?
Thanks
Edit: Trying with SDK as command prompt didn't recognize adb as a valid command.
Edit: SDK did not work, I guess I just did the same in 3 different ways... any ideas?
Got it!
Titanium tools pro version has an ADB backup extraction. Move the .BAK file to your SD card folder, and then restore the extracted info