I ALWAYS get "MD5 mismatch" when I try and do a restore?
This is so messed up! I did the nanroid backup right after I rooted and installed CWM. Also, have done a couple other backups too..
Then after flashing a couple ROMs, I tried a restore. I got the error then! Lucky I have TiBackup and havent really needed to restore a crippled flash(not sure that restore would help in that circumstance tho, but that's not the point!) so doing the restore hasn't been critical to me.
I posted about this in the "General" forum before and the Mods just deleted my post, I guess it was in the wrong place? hopefully this one is in the correct forum, you'd think it would have been moved?
I have followed every instruction to the letter, it's kind of hard to do it wrong with QBking77's wonderful videos, so I'm sure I've done it correctly? Does anyone have a suggestion as to why I'm getting this error?
The reason I was trying to perform the restore this time was trying to do the advanced restore>data function that was described in the "Best ROM Challenge" post http://forum.xda-developers.com/showpost.php?p=22570714&postcount=1 ...Is there something in my settup that I have wrong, why would I ALWAYS be getting this eror, it doesn't make any sence?
Thanks for any help?
yahknow1 said:
I ALWAYS get "MD5 mismatch" when I try and do a restore?
This is so messed up! I did the nanroid backup right after I rooted and installed CWM. Also, have done a couple other backups too..
Then after flashing a couple ROMs, I tried a restore. I got the error then! Lucky I have TiBackup and havent really needed to restore a crippled flash(not sure that restore would help in that circumstance tho, but that's not the point!) so doing the restore hasn't been critical to me.
I posted about this in the "General" forum before and the Mods just deleted my post, I guess it was in the wrong place? hopefully this one is in the correct forum, you'd think it would have been moved?
I have followed every instruction to the letter, it's kind of hard to do it wrong with QBking77's wonderful videos, so I'm sure I've done it correctly? Does anyone have a suggestion as to why I'm getting this error?
The reason I was trying to perform the restore this time was trying to do the advanced restore>data function that was described in the "Best ROM Challenge" post http://forum.xda-developers.com/showpost.php?p=22570714&postcount=1 ...Is there something in my settup that I have wrong, why would I ALWAYS be getting this eror, it doesn't make any sence?
Thanks for any help?
Click to expand...
Click to collapse
Could be a different version of cwm .... You may have noticed when flashing roms that some devs use different cwm versions like acs , rouge etc ....... Did you rename them ?
Sent from my SPH-D710 using xda premium
Epix4G said:
Could be a different version of cwm .... You may have noticed when flashing roms that some devs use different cwm versions like acs , rouge etc ....... Did you rename them ?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No, I didn't rename them.
The Idea of them different CWM had occured to me and yes I think there were diff versions...That matters?
yahknow1 said:
No, I didn't rename them.
The Idea of them different CWM had occured to me and yes I think there were diff versions...That matters?
Click to expand...
Click to collapse
It may some roms won't flash on certain versions....that's what I would try first flash a kernel with that cwm you made backups with
...if you ever rename them no spaces in the name ...
Sent from my SPH-D710 using xda premium
Well, I just shot that theory down. I've re burnt the exact ROM that I mad the Nandroid from and then did a Advanced restore>Restore data.
Resulted in the same MD5 error?
http://www.mydroidworld.com/topic/2798-how-to-fix-md5-mismatch/
I had the same problem for a while....this works everytime
Sent from the near past
Danial723 said:
http://www.mydroidworld.com/topic/2798-how-to-fix-md5-mismatch/
I had the same problem for a while....this works everytime
Sent from the near past
Click to expand...
Click to collapse
So, that looks like it would work, but I'm confused, are you supposed to type the code wwhile in ADB Shell? not while in CWM?
AND
Can you run adb shell from CWM?
yahknow1 said:
So, that looks like it would work, but I'm confused, are you supposed to type the code wwhile in ADB Shell? not while in CWM?
AND
Can you run adb shell from CWM?
Click to expand...
Click to collapse
I just run it from my phone "terminal emulator" from the market
Sent from the near past
Related
I do a nandroid backup... the whole process finishes.. Then I go to restore to it.. And it brings me back to a FRESH install of whatever Rom I backed up. It's done this to me now with Baked Snack and CM6
What recovery are you using? Just curious.
Sent from my PC36100 using XDA App
MJStephens said:
What recovery are you using? Just curious.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Clockwork...
thenags said:
Clockwork...
Click to expand...
Click to collapse
I've never used Clockwork so I'm afraid I can't really give you much insight. I might suggest taking 15 min and installing one of the AmonRA recoverys. I've used them since I had a MT3G and they seem to be pretty flawless. As long as you store your backups on your SD card you shouldnt really be at risk of losing anything. Does Clockwork allow you to make and store multiple backups?
Clockwork works just fine for me. I'm not sure what your problem might be.
i use Amon Ra and i have been having the same issue lately, kinda...when i go to restore a nand backup it gives me an error message saying to push it adb style or sumthing along those lines...very frustrating ...kinda lost too for me...any one have any ideas what the problem is ? using FrEakEfroyo v2 with king#6
dezel29 said:
i use Amon Ra and i have been having the same issue lately, kinda...when i go to restore a nand backup it gives me an error message saying to push it adb style or sumthing along those lines...very frustrating ...kinda lost too for me...any one have any ideas what the problem is ? using FrEakEfroyo v2 with king#6
Click to expand...
Click to collapse
Have you, by any chance, renamed your backups? If you have, you CAN'T have any spaces in the name. If you named it the full version of what you're running it would have to be FrEakEfroyo_v2_with_king#6
dezel29 said:
i use Amon Ra and i have been having the same issue lately, kinda...when i go to restore a nand backup it gives me an error message saying to push it adb style or sumthing along those lines...very frustrating ...kinda lost too for me...any one have any ideas what the problem is ? using FrEakEfroyo v2 with king#6
Click to expand...
Click to collapse
Your problem most likely is that your battery is too low. Happened to me several times usually if the battery is below 30% or there abouts. Plug your phone in, juice it up and try with at least 50 % battery, should work.
Or, I've heard it can happen if you renamed your backups. I never rename my backups because I've heard it can cause issues like this, so I can't tell you for sure if that's the problem.
I'm guessing battery.
This is really getting frustrating. I did a nandroid backup last night of my Baked Snack install. I then wiped and installed CM6. 5 minutes later I had a problem and restored Baked Snack. And it went right back to a fresh install of Baked Snack. I then flashed AmonRA. Installed CM6. Setup CM6 how I wanted it. Did a nandroid backup in AmonRA. Then wiped and restored it. And I was right back to a fresh install again.
MJStephens said:
Have you, by any chance, renamed your backups? If you have, you CAN'T have any spaces in the name. If you named it the full version of what you're running it would have to be FrEakEfroyo_v2_with_king#6
Click to expand...
Click to collapse
i have renamed them...i will check to see if that is the problem or not...thanks for the info...hope this helps me in the future with my nand backups...
I tried not renaming and had the same issue
Sent from my PC36100 using XDA App
Hi,
I was fascinated by MIUI english version and I decided to try it out. Backuped my current setup (Virtuous 2.0.0 with custom kernel) twice then downloaded and installed MIUI us from ROM Manager Premium and it went fine. Decided to stay on my old setup for a while and restored it back.
Then noticed first this error message: "UID's on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and button "I'm feeling lucky". Nothing works properly. Now I'm flashing MIUI again and try to get to use to it...
Tried many times to wipe and restore all over again. My backups should be fine. How to get my earlier system back or do I? What the error message means? Tried to google around and search from the forums but did not find much help...
If you can help, I would appreciate very much. Thanks.
Have you done a complete wipe?
Sent from my HTC Vision using XDA App
Are you referring to a nandroid? Nandroid would be the backup you made with either with rom manager or through recovery
If you made a backup through the above mentioned methods you should download superwipeG2 and flash through recovery. The "I'm feeling lucky" thing is nothing I've ever seen in recovery or rom manage so what are you talking about?
Sent from my HTC Vision using XDA Premium App
coachmoore said:
Have you done a complete wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah.
Spastic909 said:
Are you referring to a nandroid? Nandroid would be the backup you made with either with rom manager or through recovery
Click to expand...
Click to collapse
Yeah, backup from clockworkmod recovery which I suppose is called "nandroid" backup?
Spastic909 said:
If you made a backup through the above mentioned methods you should download superwipeG2 and flash through recovery.
Click to expand...
Click to collapse
So now that I have nandroid backup I could do this "superwipe" (never heard of that before) and then flash the backup (=restore)? Am I misunderstanding something here..?
Spastic909 said:
The "I'm feeling lucky" thing is nothing I've ever seen in recovery or rom manage so what are you talking about?
Click to expand...
Click to collapse
I admit I was a bit unclear. This message and button showed up when I rebooted to system after restoring backup, when some of the stuff seemed to be there, but some not (theme was broken, some apps were not installed etc), not a fully restored backup I guess...?
I don't really want to go gack to Virtuous now that I'm fallen in love with MIUI, but I'm curious to know what caused this?
My backup didn't seem to complete the way it did on my previous devices. I got a weird message and nothing saying the backup was completed successfully. any thoughts?
the last two lines when I try and do a backup are
"unable to find volume."
"Error finding an appropriate backup handler."
I tried to restore a backup I did before I tried to install Google Wallet because every time I reboot I get a box that says "Android Is Updating" and then it proceeds to "optimize" like 100 programs which takes several minutes. When I try to restore it says that the MD5 sum is invalid. Any thoughts?
I even wiped my phone and started over from scratch thinking I messed something up. I keep getting an MD5 sum mismatch when I try to restore from the backup...
vaffanculo403 said:
I tried to restore a backup I did before I tried to install Google Wallet because every time I reboot I get a box that says "Android Is Updating" and then it proceeds to "optimize" like 100 programs which takes several minutes.
Click to expand...
Click to collapse
This is normal behavior, whether you've installed google wallet or not.
Nope it only started after I tried to install it and it stopped after I reflashed the stock system image...
MODS I accidentally posted this in the "general" forum and I meant to put it in the Q&A forum. Please move it if this is a problem Thanks!
vaffanculo403 said:
Nope it only started after I tried to install it and it stopped after I reflashed the stock system image...
Click to expand...
Click to collapse
Its normal on reboot to get the "optimizing" dialogue and cycling through your apps.
Well I"m telling you that It only started after I tried to install Google Wallet and it stopped after I flashed back to the original factory image and hasn't happened since. I've rebooted at least 12 or 15 times trying to get CWM to work since I reflashed...
vaffanculo403 said:
My backup didn't seem to complete the way it did on my previous devices. I got a weird message and nothing saying the backup was completed successfully. any thoughts?
the last two lines when I try and do a backup are
"unable to find volume."
"Error finding an appropriate backup handler."
I tried to restore a backup I did before I tried to install Google Wallet because every time I reboot I get a box that says "Android Is Updating" and then it proceeds to "optimize" like 100 programs which takes several minutes. When I try to restore it says that the MD5 sum is invalid. Any thoughts?
I even wiped my phone and started over from scratch thinking I messed something up. I keep getting an MD5 sum mismatch when I try to restore from the backup...
Click to expand...
Click to collapse
I also getting the same error.
appreciate if u can share the solution if found....
No solution yet and every request for help has fallen on deaf ears...
Sent from my Galaxy Nexus using Tapatalk
I've had the exact same issue every time I've made a backup. Here is the solution to get the backup working:
http://forum.xda-developers.com/showthread.php?t=976453
Sent from my Galaxy Nexus using xda premium
nbeebe24 said:
I've had the exact same issue every time I've made a backup. Here is the solution to get the backup working:
http://forum.xda-developers.com/showthread.php?t=976453
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
hi,
thanks for posted here for the solution worked from your case. appreciate.
I had tried but not working in my issue.
just would like to share the full details about my issue when backup:
ClockworkMod Recovery v5.5.0.2
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android_secure...
Unable to find volume.
Error finding an appropriate backup handler.
basically, normal successfully backup; we should getting 6 files which is:
boot.img
cache.ext4.tar *missing*
data.ext4.tar
nandroid.md5 *missing*
recovery.img
system.ext4.tar
after I got the error above, in the backup folder only got 4 files. I', still failed to resolve the issue by the method from Exca. correct me if I did anything wrong.
Hey vaffan honestly not trying to be rude here but your tone is a little off, you have done these things to your fone not anyone on xda. This forum is a place to discuss and build solutions acting like no one is helping and by some right they should be isn't going to get you anywhere. Its also the holiday season so I am sure many amazing devs are spending time with family.
Now on to your problem. If you have a working solution....flashing back to stock. ... I would try that and work from the beginning reroot your device and reinstall cwm and try just from stock rooted state. You can use logcat and adb to verify things each step of the way.
Half the fun of android for me is breaking it then figuring out where I went wrong
Sent from my Galaxy Nexus using XDA App
vaffanculo403 said:
My backup didn't seem to complete the way it did on my previous devices. I got a weird message and nothing saying the backup was completed successfully. any thoughts?
the last two lines when I try and do a backup are
"unable to find volume."
"Error finding an appropriate backup handler."
I tried to restore a backup I did before I tried to install Google Wallet because every time I reboot I get a box that says "Android Is Updating" and then it proceeds to "optimize" like 100 programs which takes several minutes. When I try to restore it says that the MD5 sum is invalid. Any thoughts?
I even wiped my phone and started over from scratch thinking I messed something up. I keep getting an MD5 sum mismatch when I try to restore from the backup...
Click to expand...
Click to collapse
Do you have GSM or CDMA edition of GN?
If CDMA, what version of CWM do you use?
There has been som issues with CWM 5.5.0.2 and CDMA edition, but there is an CWM 5.5.0.4 version that is working with CDMA edition.
http://androidcommunity.com/clockworkmod-recovery-now-available-for-verizon-galaxy-nexus-20111215/
Don't know if this solves your problem.
t3alc said:
Do you have GSM or CDMA edition of GN?
If CDMA, what version of CWM do you use?
There has been som issues with CWM 5.5.0.2 and CDMA edition, but there is an CWM 5.5.0.4 version that is working with CDMA edition.
http://androidcommunity.com/clockworkmod-recovery-now-available-for-verizon-galaxy-nexus-20111215/
Don't know if this solves your problem.
Click to expand...
Click to collapse
I'm using GSM GN. I had checked the recovery thread for GSM, still is 5.5.0.2
Goat_For_Sale said:
Hey vaffan honestly not trying to be rude here but your tone is a little off, you have done these things to your fone not anyone on xda. This forum is a place to discuss and build solutions acting like no one is helping and by some right they should be isn't going to get you anywhere. Its also the holiday season so I am sure many amazing devs are spending time with family.
Now on to your problem. If you have a working solution....flashing back to stock. ... I would try that and work from the beginning reroot your device and reinstall cwm and try just from stock rooted state. You can use logcat and adb to verify things each step of the way.
Half the fun of android for me is breaking it then figuring out where I went wrong
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I'm going to ignore your first paragraph. I'm a adult and will not tolerate being scolded by you. I'll talk however i want whatever i want. if I make any further comments on this I will end up getting banned. Don't talk to me like that again.
Secondly, I have tried going back to stock (several times in fact). This isn't my first Android device. It is however my first one without an SD card. I believe that it is looking for the SD card and getting confused at certain steps when its finding the internal memory and not the SD card...
Sent from my Galaxy Nexus using Tapatalk
I'm using the CDMA version. I'll try it and report back. Thank you!
Sent from my Galaxy Nexus using Tapatalk
t3alc said:
Do you have GSM or CDMA edition of GN?
If CDMA, what version of CWM do you use?
There has been som issues with CWM 5.5.0.2 and CDMA edition, but there is an CWM 5.5.0.4 version that is working with CDMA edition.
http://androidcommunity.com/clockworkmod-recovery-now-available-for-verizon-galaxy-nexus-20111215/
Don't know if this solves your problem.
Click to expand...
Click to collapse
No dice. It was the same version I had installed but I tried or again anyway and got the same error...
Sent from my Galaxy Nexus using Tapatalk
Originally Posted by nbeebe24
I've had the exact same issue every time I've made a backup. Here is the solution to get the backup working:
http://forum.xda-developers.com/showthread.php?t=976453
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
hi,
thanks for posted here for the solution worked from your case. appreciate.
I had tried but not working in my issue.
just would like to share the full details about my issue when backup:
ClockworkMod Recovery v5.5.0.2
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android_secure...
Unable to find volume.
Error finding an appropriate backup handler.
basically, normal successfully backup; we should getting 6 files which is:
boot.img
cache.ext4.tar *missing*
data.ext4.tar
nandroid.md5 *missing*
recovery.img
system.ext4.tar
after I got the error above, in the backup folder only got 4 files. I', still failed to resolve the issue by the method from Exca. correct me if I did anything wrong.
Click to expand...
Click to collapse
Wait, so you did try the method I linked you to? None of my nandroids have all the files you've listed, and I get the exact same messages when backing up. I get a md5 mismatch and that guide fixes it every time
Sent from my Galaxy Nexus using xda premium
Why don't you try to flash CWM again? First within From and if no dice then with ADB.
vaffanculo403 said:
No solution yet and every request for help has fallen on deaf ears...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App
forelli said:
Why don't you try to flash CWM again? First within From and if no dice then with ADB.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I've done it probably 40 times though ROM Manager and maybe 6 times with ADB...
Sent from my Galaxy Nexus using Tapatalk
Have you tried adb backup instead? You might be right about cwm having trouble
Is anyone else having an issue backing up via cwm? For some reason, it will go as far as backing up data then give me an error message. Sometimes it will even seem to complete a successful backup but when I try to restore, it says md5 mismatch. Is there a way to fix this or can someone point me in the direction of finding another backup app? Thanks
Sent from a Sammy Galaxy far, far away..
I got the same issue before. Some have recommended not using Tom manager and just doing it through recovery with button combo.
Message relayed from the dark side.
Mine gow trough the whole back up and always at the end says that "it could not back up image for /data" :/
Here ya go..... This will resolve your issue. Good luck!
http://forum.xda-developers.com/showthread.php?t=976453
The steps involve downloading android SDK and possibly upgrading your Java but it is a one time fix issue so it's worth it. Which means you don have to do this everytime u want to do sucessful restore/backup.
anomy13 said:
Here ya go..... This will resolve your issue. Good luck!
http://forum.xda-developers.com/showthread.php?t=976453
The steps involve downloading android SDK and possibly upgrading your Java but it is a one time fix issue so it's worth it. Which means you don have to do this everytime u want to do sucessful restore/backup.
Click to expand...
Click to collapse
Thanks for the help but it didn't work. Now it went through the process of the backup and during the restore, it failed at trying to restore system. Not sure what the problem could be. Is there an alternate backup solution?
Sent from a Sammy Galaxy far, far away..
kkholidaze said:
Thanks for the help but it didn't work. Now it went through the process of the backup and during the restore, it failed at trying to restore system. Not sure what the problem could be. Is there an alternate backup solution?
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Did u actually try it or ud rather find a different solution? Cuz i had the exaxt same problem and this resolved my issue once and for all.
Sent from my SGH-T989D using XDA App
kkholidaze said:
Is anyone else having an issue backing up via cwm? For some reason, it will go as far as backing up data then give me an error message. Sometimes it will even seem to complete a successful backup but when I try to restore, it says md5 mismatch. Is there a way to fix this or can someone point me in the direction of finding another backup app? Thanks
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Are you using rom manager? I've never encountered an issue with cwm backups made via recovery mode.
Sent from my Hercules using XDA App
It was happening to me regardless. Rom manager backup doesn't take you to backup anymore. It just takes you straight to recovery. Must be a bug in the new version. Three button combo also results in similar md5 mismatches. What I did was backup my SD card and reformatting it. Also I erased anything in my internal having to do with rom manager and also did a fresh install of my rom. I just tried three button combo and it backedup and restored properly. I can't pinpoint which of what I did helped but something must have been messed up
jordanishere said:
Are you using rom manager? I've never encountered an issue with cwm backups made via recovery mode.
Sent from my Hercules using XDA App
Click to expand...
Click to collapse
Message relayed from the dark side.
I know this is super basic, but have you pulled out your sd card and done a dual check with your computer? Also, ensure you have at least a gigabyte of free space on it.
My CWM backups were failing due to these two reasons.
Hope this helps!
~~ Douglas
Sent from my SGH-T989D using xda premium
chib1panda said:
It was happening to me regardless. Rom manager backup doesn't take you to backup anymore. It just takes you straight to recovery. Must be a bug in the new version. Three button combo also results in similar md5 mismatches. What I did was backup my SD card and reformatting it. Also I erased anything in my internal having to do with rom manager and also did a fresh install of my rom. I just tried three button combo and it backedup and restored properly. I can't pinpoint which of what I did helped but something must have been messed up
Message relayed from the dark side.
Click to expand...
Click to collapse
This is the one. Think it's a issue with ROM manager in general. Deleted the cwm folder, wiped cache/dalvik, backup worked! Somethings up with RM
Sent from a Sammy Galaxy far, far away..
Tried your suggestiongs but at the end still says
"Error while making a backup image of /data!"
linye said:
Tried your suggestiongs but at the end still says
"Error while making a backup image of /data!"
Click to expand...
Click to collapse
Never mind. Tried a second time but as like you, got a error when it got to backing up data. Anyone know what could be causing this?
You guys ahould email koush- the developer of the app. Or follow the link posted in the first few pages as an alternative fix.
Message relayed from the dark side.
Newest update fixed this problem... Works great now
Sent from my SGH-T989 using xda premium
rpolito73 said:
Newest update fixed this problem... Works great now
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ok, I updated the recovery to touch (paid for it instead of fastboot to support by the way) and it was still giving me errors. After some testing, I found out what my issue is. If I try to backup to my external SD, I get the errors. If I just backup to my internal SD, backup goes fine. Did the tests a few times to test theory. I have a 32g Kingston card. Not sure why that would be an issue.
Sent from a Sammy Galaxy far, far away..
The fact that you have a 32 gb kingston card doesnt mean anything. Try it with a different card.
and what kind of errors are you getting when you try to backup with external?
anomy13 said:
The fact that you have a 32 gb kingston card doesnt mean anything. Try it with a different card.
and what kind of errors are you getting when you try to backup with external?
Click to expand...
Click to collapse
Various errors at different times. Sometimes at data, sometimes at md5, sometimes at Android secure
Sent from a Sammy Galaxy far, far away..
kkholidaze said:
Various errors at different times. Sometimes at data, sometimes at md5, sometimes at Android secure
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Do get this as well? Error while making a backup image of /data?
Also, I wanted to ask you, did you really try my suggestion earlier? I understand that solution is a bit of work to do but if you'd like I can help you step by step.
anomy13 said:
Do get this as well? Error while making a backup image of /data?
Also, I wanted to ask you, did you really try my suggestion earlier? I understand that solution is a bit of work to do but if you'd like I can help you step by step.
Click to expand...
Click to collapse
I tried it but I think I did it wrong. I downloaded the necessary files, I think (NotePad ++ etc.) But if you could walk me through it, is appreciate it
Sent from a Sammy Galaxy far, far away..
DouglasK said:
I know this is super basic, but have you pulled out your sd card and done a dual check with your computer? Also, ensure you have at least a gigabyte of free space on it.
My CWM backups were failing due to these two reasons.
Hope this helps!
~~ Douglas
Sent from my SGH-T989D using xda premium
Click to expand...
Click to collapse
This was my issue, not enough space. cleared it and it got fixed.
For the life of me, I cant figure out why I can never restore my back ups after testing out various roms and kernels. I know it has something to do with the kernels and/or recoveries that are used when backing up and restoring but I cant seem to figure it out. Every time I try to restore a backup I usually get an MD5 mismatch and it fails. I THOUGHT that if I did the backup and restore using the SAME kernel/recovery versions that it would work, but that doesnt seem to be working. Is there something I am missing? Ill give you an example in case you have any tips.
I was running Calks v1.5 for awhile, then decided I wanted to try the AOKP rom. As noted in the AOKP thread, to restore, Odin the EL26 CWM kernel/recovery and run a back up. So I Odin the kernel/recovery, ran the backup, then attempted a restore just to see if it worked. Successfully able to restore from within that same CWM session. So I Odin EL26 CWM again, and this time flashed the AOKP and gapps and rebooted into AOKP. No problem there. Messed around with AOKP (which is awesome) but wanted my daily back so I Odin the EL26 CWM again, and tried to restore the Calk 1.5 and got the MD5 mismatch.
What am I doing wrong?
Are you renaming them? They can't have any spaces in the name, must be something like aokp_may10 instead of aokp may 10
Sent from my SPH-D710 using Tapatalk 2
Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?
I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Edit: Well, I saw you beat me to it on the post. LOL
I'll be your Plan B then.
tdunham said:
I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Click to expand...
Click to collapse
Nah I did the backup and attempted restore from EL26 CWM (so I could flash the ICS rom "safely"). I also didnt copy them from the SD card so hopefully thats one less reason for the failure. Thanks
ryan2202 said:
Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?
Click to expand...
Click to collapse
That im not sure of, but try to rename with no spaces and report back
Sent from my SPH-D710 using Tapatalk 2
!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:
Glad that worked! The bright side is your an expert at flashing roms now!
Sent from my SPH-D710 using Tapatalk 2
ryan2202 said:
!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:
Click to expand...
Click to collapse
Lol I remember having this problems back in the days of the galaxy s, I've spent so many hours setting everything up all the time more than testing the roms itself, until I asked this same question.
Sent from my SPH-D710 using Tapatalk 2