Hello people.
So i unlocked my phone and rooted it and before installing a custom rom i nandroid backed up the stock rom via cwm.
Then i flashed a custom one and also backed it up.
Problem is that if i try to restore either of the two backups i get a md5 mismatch and they won't restore...
Is cwm backup broken? Or am i SO unlicky that both of my backups got corrupted??
Many thanks in advance
Sent from my CoreDroid powered HTC One X via Tapatalk 2
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
jazznaura said:
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
Click to expand...
Click to collapse
I solved it a long time ago
The problem was due to renaming the backup
Thanks for the input though!
Related
Hello,
I just got back my desire from repair and have rooted it again using unrevoked, my main rom i flashed was cyanogen 7, i made a backup and then i thought i would s-off and update to clockwork recovery 3....everything was successful.
But when i try out other roms then decide to restore my nandroid back up of cyanogen 7 messeges pop up quickly saying all the apps and stuff have stopped unexpectedly and then the phone reboots again and again.
Can some one help please.
Cheers.
Just do a full wipe and fresh install then backup again.
Sent from CM7
Meaple said:
Just do a full wipe and fresh install then backup again.
Sent from CM7
Click to expand...
Click to collapse
Hi,
I have done this 3 times and the nandroid backup still reboots, only way to fix it is to install cyanogen on top of it and it fixes it.
I think i will need to try with a sense rom and see if it happens too.
Thanks.
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
And if you did some fancy formatting to your SD card. Well, Might think about that also....
Meaple said:
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
Click to expand...
Click to collapse
I have deleted the old backup and made new one's each time after a full wipe, the card is formatted correctly and working fine, i have only had this problem after i updated clockwork mod and s-off.
Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Think some people encountered an issue with that version under certain circumstances, can't remember if it was related to wipe/format of boot or Sys partition or something else. If you can revert back to RC 2, or flash one of the newer test versions and try that.
Sent from my HTC Desire using Tapatalk 2
Kosh_ac said:
Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Click to expand...
Click to collapse
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
paolo-red1 said:
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
Click to expand...
Click to collapse
Just tried a complete recovery, problem unfortunately persists
Regards,
Guido
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Kosh_ac said:
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Click to expand...
Click to collapse
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
andy.smith said:
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
Click to expand...
Click to collapse
No! I did not flash another HBOOT after S-OFF with revolutionary!
Regards,
Guido
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
SANCAH said:
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Kosh_ac said:
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Click to expand...
Click to collapse
I am using the latest version of the touch test recovery, haven't had any issues so far.
Sent from my HTC Desire using Tapatalk 2
Hello everyone!
Just wanted to give feedback about my problem!
Updated to 4Ext Recovery 1.0.0.5 RC3 prior to installing Supernova Extreme and made a Nandroid Backup without the problem I encountered before!
Did two additional Nandroid Backups after flashing the new ROM also without any problems!
So this thread can be closed
Thanks again to everyone for your helpful ideas!
Regards,
Guido
hi
so i have installed cm9 alpha 7 and made a nandroid backup before through with the help of cwm recovery. when i tried to revert back through the same menu it gave md5 mismatch error, i have seen on other sections of this forums and they do have fixes for htc one and hd2... any fixes for wildfire s ??
let me know if it wasnt clear enough !!
thanks
just writing it here so that someone may get help from this post
well i have gone through some forums and the adb shell method written their didint worked out
i figured out i have renamed the folders from the cwm restore format to my own, so i reverted them back and the phone is restoring now
hit thanks if it helped you
Did you make a backup with a different CWM and try to restore it with a another version? Let's say you did a backup with version 3.X.X and then you tried to restore it with version 5.X.X, did you do that? If so revert back to your original CWM that you made a back up with. Also did you rename the backup file? That could cause a MD5 mismatch. Hope this helps
well as mentioned in second post, i have resolved the problem ... cwm recovery versions are same but i did "renamed" the folder. i reverted to original name and it restored well.
The problem is that cwm does not allow spaces in the name of the backup file....thus the following error arises.
Sent from my GT-S5570 using xda app-developers app
Hi guys
I'm having g some weird issues I have a gs3 from bell. I rooted it and been flashing all kinds of Roms and never having any issues going back to restoring stable Roms until I decided to try twrp recovery but I noticed that I couldn't restore anything backed up by cwm so I flashed cwm though Rom manager and since then whenever I try to backup a Rom it finishes then when I try to restore them they say md5 mismatch. So after a lot of research I managed to notice that cwm isn't making any nandroid md5 files.
So my question is have I flashed a bad version of cwm through Rom manager or may I have just screwed my phones files somehow I was thinking of uprooting my phone and rerooting it but I don't know if that will fix this. Please help
*deleted*
Good luck
Just so u know i've read through that 3 times already I don't have that issue ... I dOnt have a nandroid md5 like showing up in any of my backups so thanks for nothing if you would have read my post you would have understood That already
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
DLM2583 said:
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
Click to expand...
Click to collapse
Hi, I am still having the same problem as you, and I bought Cwm touch from rom manager and i created a backup and when i restore it it says md5 mistmatch.. So did you get a different older version of cwm? How did you end up using the backup that you couldn't open? Thanks for your help
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.