I didnt like it, so I flashed CM9, flashed the latest gapps (i redownloaded both today) and then i went to restore and it said MD5 match failed! and from Rom Manager it said MD5 file not found. Is there anything I can do? Or am I starting over again
no, I never renamed it. Hm that's weird I wonder why it's not working. Well thanks for your help!
I booted into recovery to make it. And, I followed these from another part of XDA to restore my md5 files from the terminal steps:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then when I went to restore the md5 check worked fine, but it said error when restoring my /android_secure, and when I rebooted, the phone is stuck on the CM9 boot animation. I think that's called a boot loop but I'm not sure? Either way, I've tried restarting it and it's still gets stuck on the boot animation. I am able to go into recovery. I feel that I am semi-bricked? I'm not sure. Anyway, HELP!
Thanks, I'm starting fresh! Now I just hope any future backups I make are not corrupted like this one, I just don't see why/how it happened.
I didnt like it, so I flashed CM9, flashed the latest gapps (i redownloaded both today) and then i went to restore and it said MD5 match failed! and from Rom Manager it said MD5 file not found. Is there anything I can do? Or am I starting over again
I booted into recovery to make it. And, I followed these from another part of XDA to restore my md5 files from the terminal steps:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then when I went to restore the md5 check worked fine, but it said error when restoring my /android_secure, and when I rebooted, the phone is stuck on the CM9 boot animation. I think that's called a boot loop but I'm not sure? Either way, I've tried restarting it and it's still gets stuck on the boot animation. I am able to go into recovery. I feel that I am semi-bricked? I'm not sure. Anyway, HELP!
Thanks, I'm starting fresh! Now I just hope any future backups I make are not corrupted like this one, I just don't see why/how it happened.