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?
Related
Is there a way that I can retrieve/extract my contact list from a nandroid backup without restoring the phone to said backup? If so, please explain... thanks guys
Sent from my ADR6300 using XDA App
Do you store your contacts with your gmail account?
They're not in any of the attached accounts.
Dunno what i was thinking but when i created new contacts i added them to "phone" instead of "gmail"
I flashed a new rom and kept all my apps and junk but only maintained my gmail and facebook contacts, as woulda been expected if i was thinking.
Is there a virtual drive or something similar that i can use to mount the .img files from the nandroid backup?
Thanks.
MagicISO won't mount it
EDIT: I decided to just go ahead and restore to the old backup and then export the contacts, but, the old nandroid backup is saying "MD5 mismatch" so, any good ideas?
This may help:
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Good luck, hope it helps.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
With the new OTA being released many are asking how to restore stock recovery. I think that the original /system/etc/install-recovery.sh file is required, unfortunately I did not make a backup. Does anyone have a copy of the original version of this file? Please post it here if you have it and anyone who knows how to restore stock recovery please post any helpful instructions here. If I get the file and proper instructions I will update the OP accordingly. Thanks.
I made a backup but have no idea how to extract that file.
You have to write which TPT you have.
US or....?
16, 32 or 64GB?
toenail_flicker said:
I made a backup but have no idea how to extract that file.
Click to expand...
Click to collapse
What did you backup with? If you backed it up after installing CWM then it was probably already gone (which is why I don't have it).
In the ROW instructions they cleverly added this line to the install instructions:
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
which creates a backup of the file in /system/etc/
If you did this then you should be able to copy the file install-recovery.sh.backup from /system/etc/ using root explorer or adb.
I have the US 32GB version, I'm not sure if the files are the same but I would guess that they are. Anyway if you can get the file that would be great.
I have 183827U 64GB. Yes, I made a Nandroid backup after installing CMW. I also have Titanium and MyBackup saves, but have no idea if they save the file. I'll go looking for it with RE and let you know what I find.
---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------
Seems I have install-recovery.sh but the date is recent, so I guess it's from when I rooted. No backup of the same name.
Mine is:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:0a48c18ee1ca32bba5a785d8ea8b6976fc0a190e; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3170304:fa229b8ff37128302094316ea4ced3d68ad5edcf EMMC:/dev/block/mmcblk0p1 53a249cd150c483f9255eba03adccdf6e7c014a6 3524608 fa229b8ff37128302094316ea4ced3d68ad5edcf:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
WE-TPT-64GB
I edited a file manually in the system partition and my phone didn't boot and I didn't have a CWM backup.
By creating a new backup in CWM and mounting the SD card, I could open system.ext4.tar with "7-zip File Manager" and change back what I messed up and restore the system partition successfully!
----
What I discovered was that the MD5 mismatch would still appear even if I changed to the new MD5 string by using a MD5 generator.
This is a problem in CWM and appears in Abyss Kernel and Francos Kernel (The ones I tried and newest version as of this date), BUT luckily, SpeedMod kernel saved me!
By emptying the whole nandroid.md5 file, SpeedMod kernel's CWM did not check the MD5 sum and the system partition got restored with the corrected files and the phone booted successfully.
Hope this helps others as well and hit the Thanks button if it did, Thanks!
Could you not just boot into recovery, mount the system partition and then connect via an adb shell and/or use adb pull/push on the problem file?
Your method seems good though.
knightnz said:
Could you not just boot into recovery, mount the system partition and then connect via an adb shell and/or use adb pull/push on the problem file?
Your method seems good though.
Click to expand...
Click to collapse
That would work too of course!
Though many basic user are not familiar with adb or think it's complex.
If not, your method works as well.
Off Topic:
You should add "then" and "than" to your list. Also a common mistake.
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.
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..