Hi this is my first post on xda so bear with my n00biness.
I've flashed Entropy's ClockworkMod and a couple of ics roms and it was really nice and getting better every new release. However, my occasional need for my camera and flash player brought me to do a restore back to stock rom (which I backed up on cwm).
Unfortunately, when cwm checks its md5 sum it ends up with an error saying there's a mismatch.
Is there a problem with my version of cwm? Or would I have to wipe my data beforehand?
Sent from my YP-G70 using xda app-developers app
well what i do when i flash back my recovery i factory reset and then clear cache and wipe dalvik cache then i flash my recovery
Did you rename the backup? Sometimes this causes CWM to mess up. If you did rename it then name it something like 'stock' and try restoring again
Sent from my Nexus 7 using XDA Premium HD app
try this,enter terminal emulator and use this commands ..offcourse chage directory with yours
su
cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
rm nandroid.md5
md5sum *img > nandroid.md5
Sent from my S7 using xda app-developers app
thank you so much the bit of time you've given for me, guys.. even after answering questions that you may have said already
Well now this smart guy decided to see if he has the md5 file inside the recovery file, and, pretty surprisingly, there were no nandroid file except for one of my newer backups. (But that apparently doesn't have the md5 file included in that nandroid file either )
Oh well. Renaming the backup won't bring back the file, will it? are all md5's unique per backup? And, just making sure, there needs to be a nandroid file in the recovery folder, right...?
Sent from my YP-G70 using xda app-developers app
umm i think they are different and yes there has to be a nandroid file in the backup folder or else if you screw up the backup wont help either way
create an empty text file and name it nandroid.md5 in the backup folder
then use my script which is located in sig
I have a similar issue with not being able to locate the backups in a folder. Not in cwm folder where they should be. I went through every file I could think of to locate with no prevail, but yet in recovery - there they are! Is this because the cwm recovery is pushed in with the kernel and not through rom manager? Also, has anybody messed around with selecting a different device in rom manager because galaxy player is not listed?
Sent from my SCH-I535 using xda premium
Related
I think i just screwed up and damaged my system/chroot file by copy and paste from the /sdcard/ext2ubuntu/ to my system folder without backing up the original. I am now afraid to re-boot my phone. can someone send me a good copy of the original file. I need someone to copy their chroot file from their /system/xbin/ and send it to me.
Just boot into recovery from HBOOT and restore a backup or flash again after formatting /system
Sent from my ThunderBolt using XDA Premium App
Restored a system backup and fixed. Sorry for the panic attack
ilovesoad said:
Just boot into recovery from HBOOT and restore a backup or flash again after formatting /system
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
Okay, will do. I get it now! I do have a few backups.
You could have just downloaded the rom that you flashed and pulled out whatever you needed yourself from computer or phone
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
If your file name has spaces in it, it may cause the MD5 mismatch error.
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I hate windows....it bites! I mean ":cyclops:bytes"
I did it all on my phone using a file manager. So if I change the name to something without spaces it should be fine?
Sent from my SAMSUNG-SGH-I717 using xda premium
I had the same problem the other day - a known good backup wouldn't install. After much searching and asking I ended up considering the backup scrapped and moved on. Then the next day I tried again and it worked fine.
Do you have another backup?
Did you change the name of the backup?
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I have had this issue since I like to store my older nandroids on my Win 7 PC. Do you know of any way to identify or remove the extra bytes? It would have to be after the file is transferred back to the Note I imagine.
Your should try renaming your file.
tmb993 said:
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Hi
if you did your backup using CWM and you renamed it after doing the backup I suggest you use "." instead of spaces; example if you rename it "CM9 ROM" try "CM9.ROM" or if you backup your stock rom and rename it "stock android rom" tried "stock.android.rom"
Cheers from DFW
Ok well I did that and I thought it would fix the problem but now I keep getting this error message in my recovery. Got it when I tried to reflash the recovery that I properly named and then again when I tried to flash on PA's 4.1 CM10. What in the heck does this mean??
Sent from my SAMSUNG-SGH-I717 using xda premium
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
lactardjosh said:
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
Click to expand...
Click to collapse
Aw man. Well I just had the newest version but reverted back to 5.5.0.4 because it game me a lot of issues. Strange but I also got the same error when I tried to restore from that one backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I could be wrong, I don't know for sure.
But, you could see what recovery other people are using in the ROM thread.
I copy my backups from SD to computer and back and have run into this issue. I followed the instructions in this link, http://forum.xda-developers.com/showthread.php?t=714114 and it fixed the MD5 mismatch issue. I guess these commands "clean" the backup of whatever windows does to it when copied. Worked like a charm! Also, I always change my backup names and am sure not to leave spaces. This works even if the name is not what CWR generated.
Bigjoe, can you please add this to your Super Everything page -- probably in the CWM section? Thank you.
http://forum.xda-developers.com/showthread.php?t=714114
Hi, I did a backup using cwm before flashing jelly bean onto my Galaxy S3. Now I'm tryin to restore my backup but its showing md5 mismatch. These are the files I have: boot.img, data.ext4.tar, recovery.img and system.ext4.tar. I changed the name of the backup file but left no spaces in between.. Can anyone help please.
Thanks
jpx2008 said:
Hi, I did a backup using cwm before flashing jelly bean onto my Galaxy S3. Now I'm tryin to restore my backup but its showing md5 mismatch. These are the files I have: boot.img, data.ext4.tar, recovery.img and system.ext4.tar. I changed the name of the backup file but left no spaces in between.. Can anyone help please.
Thanks
Click to expand...
Click to collapse
Anyone please...Easiest solution
Which file is corrupted? If the data files is intact, you could try manually downloading the rom you had installed before. After flashing it, do a selective restore of the data partition. That should get you back to your old system.
Sent from my GT-I9300
If you rename the back up through a file manager, changes its name to "backup" i had a similar problem when trying to restore, i changed the name to s"tock" and it reverted fine without any errors
Try this thread. Helped me once when I needed it. I used the terminal emulator method to bypass the md5 check.
Sent from my GT-I9300 using xda premium
First flash stock rom with Odin, ther root the phone and restore.
sxi200 said:
Try this thread. Helped me once when I needed it. I used the terminal emulator method to bypass the md5 check.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can you teach us on how to use terminal emulator and bypass md5 check? having the same problem now
Can't believe it worked
vengeance1990 said:
If you rename the back up through a file manager, changes its name to "backup" i had a similar problem when trying to restore, i changed the name to s"tock" and it reverted fine without any errors
Click to expand...
Click to collapse
Thanks man, it actually worked.
Anyone know why I can't do a nandroid backup? Every time I try it gives me an error creating MD5 checksum. Currently I'm on AOKP M1 with the built-in kernel which includes CWM 6.0.1.5, but I don't think I've ever gotten it to work with any JellyBean ROM. I'm still using my stock class 2 card and I still have 9gb free space.
Any help would be appreciated.
Sent from my SCH-I500 using xda app-developers app
Are you trying to restore a older nandroid from before the recent partition change? If so, then it won't work. If not then I believe I remember seeing a thread about correcting an md5 error with a nandroid, but I don't have a link for you, sorry. Try to do a search.
I personally don't use nandroids because it backs up system data which in a way defeats the purpose of doing a complete data wipe (which I do often before installing new roms). I simply use TiBu to restore all my apps and just spend 5-10 minutes or so fixing the system settings, then I'm good to go.
I'm not restoring a previous nandroid backup; I'm actually trying to use it to back up my current setup. I'll try to search the issue, unless someone knows where to find it.
I may have to give TiBu another try. It's just nicer to do the nandroid because I wouldn't have to reactivate the phone or resync my accounts afterwards. Basically if I want to try a different ROM and I don't like it I could easily go back to the previous ROM with all my settings and layout.
Sent from my SCH-I500 using xda app-developers app
scarfman4 said:
I'm not restoring a previous nandroid backup; I'm actually trying to use it to back up my current setup. I'll try to search the issue, unless someone knows where to find it.
I may have to give TiBu another try. It's just nicer to do the nandroid because I wouldn't have to reactivate the phone or resync my accounts afterwards. Basically if I want to try a different ROM and I don't like it I could easily go back to the previous ROM with all my settings and layout.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You have to reactivate the phone when you flash a rom? Yeah I guess I can see how that would be annoying. I've never had to do that before, however I do have to sign into google every time (doesn't really bother me)
I always make it a habit to reactivate after flashing a new ROM if I also do a data wipe. Otherwise I can't receive calls or texts.
I wonder if the failing backup is because of the larger system partition?
Sent from my SCH-I500 using xda app-developers app
Try a older version of cwm...perhaps 6.0.1. Back when ics was first dropped cwm 5 had similar issues. There is a way to fix it, ill see if i can dig it up for ya.
edit* found it!!
Fix CWM 5.x Nandroid Backup
Let's just say you did what I did today, and did a backup, flashed another ROM, then tried to restore back to the nandroid you just made. Didn't work did it. Come to find out, I wasn't watching the backup, and it fails to generate an MD5 sum. I did a little searching to find out what to do, and I found the following steps (not my work...thanks goes to "desmail" for sharing this).
To fix this is assuming you did not change the folder names and let Clockworkmod create them.*
Code:Checking MD5 sums...
MD5 mismatch!
- Plug your phone to the computer
- Open a Terminal and type:
Code:adb devices
adb shell
# cd /sdcard/clockworkmod/backup/2011-06-29.20.22.53
# rm nandroid.md5 (Probably will fail - for me, the file was never there to begin with...this is fine)
# md5sum *img > nandroid.md5
# exit
****Make sure you change "2011-06-29.20.22.53" to the name of your backup folder*****
- Re-run the restore and everything should be fine.
You will most likely need the Nexus S ADB drivers to accomplish this.
I'm using GoogyMax (have also used Siyah) and running Purelook HD Rom along with Slimbean as 2nd ROM. Right now I have my phone exactly how I like it but I also like trying new versions. It gets confusing doing Nandroid in each ROM and running backups from both using TB (Titanium) or MBR (My Backup Root) and recently I managed to stuff things up and had to rebuild from scratch.
Is there a way to do a Nandroid and get the entire package backed up? I am presuming in Slimbean backup I get only that ROM (it's around 1.1GB) and the same for Purelook (it's around 2.17GB) It would be good if I could simply boot to recovery and run one Restore and be back to my full setup.
Or am I mistaken in the idea Purelook, based on 4.1.2 stock, would be 2 times the size of Slimbean?
Shouldn't nandroid in CWM backup both Roms as the second is a kind of subset of the first regarding folder structure?
Sent from my GT-I9300 using xda app-developers app
chrismast said:
Shouldn't nandroid in CWM backup both Roms as the second is a kind of subset of the first regarding folder structure?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No, 2nd ROM is:
/sdcard/.secondrom
This is why it's best to use Siyah recovery to manage nandroid backups for 2nd ROM. However, since /sdcard/.secondrom should contain all the ROM stuff (including data) IIRC, shouldn't you just be able to rename that to /sdcard/.secondrom_OLD and reformat a new /sdcard/.secondrom?
Thanks for the replies.
I am unable to locate the /secondrom using ES File Explorer. Going to / and searching for 'secondrom' gives me no result. secondrom is deinitely there though - I just booted into it. Either it's a setting in ES that I need to change so I can see it (I'm using ES File in the 1st ROM) or I am not understanding how the folder set up works with dual boot. (or possibly, at all )
I guess, unless there is something more specific to find on here, I will have to backup everything then try a restore of each nandroid and see what it gives me.
Its .secondrom, meaning hidden file. Have you enabled hidden files?
On 4.1, /sdcard is /data/media but on 4.2, its /data/media/0 so you'll need to use root explorer permissions to browse and check /data/media if you're on 4.2 as it may appear "missing" as per link in my signature
Sent from my GT-I9300 using Tapatalk 2