Hello,
I've been lurking around here for a while now... reading and learning.
I started playing with ROMs for my SGSII a few weeks ago. I've successfully created and restored nandroid backups of my daily driver(rooted stock ROM) many times. I also backed up unnamed ROM once and it restores fine too.
MY PROBLEM:
I have 2 different Nandroids of two different nightlies of CM7 and neither of them will restore. Both give an MD5 sum error. How can i Nandroid backup CM7 and and restore it correctly?
Thanks!
frankos72
frankos72 said:
Hello,
I've been lurking around here for a while now... reading and learning.
I started playing with ROMs for my SGSII a few weeks ago. I've successfully created and restored nandroid backups of my daily driver(rooted stock ROM) many times. I also backed up unnamed ROM once and it restores fine too.
MY PROBLEM:
I have 2 different Nandroids of two different nightlies of CM7 and neither of them will restore. Both give an MD5 sum error. How can i Nandroid backup CM7 and and restore it correctly?
Thanks!
frankos72
Click to expand...
Click to collapse
I have had this happen a lot to older backups that I have made. This thread here has worked for me.
http://forum.xda-developers.com/showthread.php?t=976453
Solution:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
Enjoy
Thanks, I'll give it a go.
Oh boy that was quite a ride. For some reason when I restored the bu after using adb to fix the md5 sums I went into a reboot loop that would cross the sgs2 splash.
I had to reflash the stock plus root with odin and then a UN New kernel with cwm so I could get back to my DD. That was a bit scary just hours ahead of the SOPA blackout.
So, is there some reason that only cm7 roms are having a bad md5 sum? I really wanted to work on making cm7 My dd, but that won't be possible if I can't count on it too backup and restore reliably.
Got any tips?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
You can either flash the same nightly you were on, let it reboot, then exit back out to recovery and restore your nandroid backup.
Here is another option to try. Flash the kernel zip I am attaching here: http://db.tt/wlfhSfag in cwm, then go and restore your nandroid backup. The file I am linking is JUST the kernel for CM7.
The reason you are having the issue is due to the OTHER roms using a different version/ version number of CWM. So once you flash the kernel and MAYBE try to boot it up( it will be stuck on the cyanogenmod boot screen), then 3 button back into recovery, now you will have a different version of CWM, which should allow you to restore your nandroid now.
Sent From My KickAss ATT SGS2 SPORTING CM7
^^^RockRatt definitley knows what he is talking about when it comes to cm7. I have never had an issue going from asop to Samsung based roms restoring from a backup. I read somewhere on here that if you rename your backups and you put a space in the name that this will cause issues with the md5 sum match. Did you happen to do this?
RockRatt said:
The reason you are having the issue is due to the OTHER roms using a different version/ version number of CWM. So once you flash the kernel and MAYBE try to boot it up( it will be stuck on the cyanogenmod boot screen), then 3 button back into recovery, now you will have a different version of CWM, which should allow you to restore your nandroid now.
Click to expand...
Click to collapse
Thank You! I haven't tried it but my gut says that you are spot on. I figured it was something like that because I had read about how entropy's DD kernel is for stock based roms and doesn't work with CM7. I just didn't really know what to do about it. I'm going to try the flash a CM7 kernel then restore and I'll report back my results.
moustro said:
I read somewhere on here that if you rename your backups and you put a space in the name that this will cause issues with the md5 sum match. Did you happen to do this?
Click to expand...
Click to collapse
Nope I read that and haven't renamed any of my backup..... yet. It's good to know just in case I ever do rename them. Thanks!
Related
Re: Nandroid backup
i would like to flash the froyo. I installed the clockwork and using nandroid to back-up the current rom but stuck in the "back up data...." . Can somebody help?
If you have 2.1 currently, there's no worries for backup because flashing back to 2.1 is as simple as flashing Update.pkg. so hurry and hop on to froyo already
Sent from my Dell Streak using XDA App
dickzoe said:
i would like to flash the froyo. I installed the clockwork and using nandroid to back-up the current rom but stuck in the "back up data...." . Can somebody help?
Click to expand...
Click to collapse
It's a known issue with no fix anticipated for the forseeable future, use MyBackup Pro or Titainium Backup for restoring your data and apps
thanks for your reply
Actually, I think there *IS* a way! I was able to connect to the Recovery via ADB and then run
Code:
nandroid backup
from there! It didn't get stuck like it used to before. I don't remember if I restored it successfully after. You might have to create the MD5 sums yourself with
Code:
md5sum boot.img recovery.img data.img system.img > nandroid.md5
..I'm typing that off the top of my head right now, so it may not be 100% accurate. I'd be interested if others have success with it. Maybe nandroid is usable like this after all, which I would really like.
Let me know if it works for you!
W0nk0
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Hahaha I had that problem a few days ago, just flash back to stock with odin. Best to try a different rom....
Sent from my SGH-T959 using XDA App
Starting to think the phone might be bricked. Can't get into recovery mode or download mode. Always immediately comes back to the Vibrant screen. Pulled the battery. Didn't help.
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
DPCerberusBlaze said:
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
Click to expand...
Click to collapse
Thank you! That did the trick. I put the stock Froyo back on via Odin now and am back up again. Whew, Christmas is saved! Thanks.
Try Eugene Ginger Clone is pretty face...I'm currently running Team Whiskey Nero Beta 3...noticed a couple bugs nothing major
Sent from my SGH-T959 using XDA App
Ravynmagi said:
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Click to expand...
Click to collapse
You were trying to load a 2.1 nandroid restore onto a 2.2 kernal. Nandroid does not restore the kernal so you would have to install one separate from the nandoid if you want to try it again.
in order to restore your nandroid backup you would have to first flash a 2.1 ROM, preferably the one you are restoring from, whenever I am changing versions, 2.2 to 2.1, I always Odin back to JFD and build up from there.
Kernel flashing questions
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
tenbeau said:
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
Click to expand...
Click to collapse
Thanks button right next to the quote >.<
I'm used to the quote being on the left.
Anyway, you can flash just the kernel. Check the Development section. There are some out there (Eugene has a bunch as do others). Depending on how they packaged the kernel, you would either flash with CWM or through Odin. The different ROMs typically come with the kernel, so you could just flash a 2.1 ROM and then nandroid back to what you had, or flash just the kernel, then nandroid.
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Click to expand...
Click to collapse
Any help would be appreciated.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
Are you sure you wiped data and cache. Also dalvic. I always flash miui twice also. That happened to me once before and I re flagged and all is well. The reason it is overheating is cause it stays at Max frequency ( CPU). Anyways check out the Miui thread in development if you want to try it again.
As far as your restore error, I don't know.
One time at football camp, I put my shoulder pads in my arse.
I may try miui again in the future, just want to get back where i was before. Thanks.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
creepyncrawly said:
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
Click to expand...
Click to collapse
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
gadget069 said:
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
Click to expand...
Click to collapse
sdcard/.android_secure is the hidden folder where apps2sd puts apps. It might be specific to cyanogen mod and miui, but not sure.
It happened when you first made your nandroid backup via cwm. The other day when I did a backup I watched it and saw the error skipping sdcard cause of no . android_secure . It has to do with cwm not being able to do a restore backup to our external sd. If you go in your external sdcard dir you will see the android secure file. So if next time you want your apps just move the file over for the backup and restore
Sent from my SAMSUNG-SGH-I777
OK, I'm having an odd issue with my phone. After flashing ICZenwich rc1.4 I decided to restore a backup I made of rc1.3. However it won't properly restore... I keep getting this in CWR...
Checking MD5 sums . . .
Erasing boot before restore . . .
Restoring boot image . . .
Restoring system . . .
Restoring data . . .
Can't mount /data!
Click to expand...
Click to collapse
Then the restore process stops. I've tried starting from scratch via Odin and then again attempted to restore. Nothing works. Help would be greatly, greatly, appreciated!
I had this issue several times with previous versions of ICZen...I saw an app in Xda called Nandroid Browser but i never used it...
Sent from my SGH-T959 using XDA
Thanks for the suggestion, but that didn't really solve the issue. Luckily I frequently backup with Titanium Backup so I was able to upgrade to rc1.4 and restore. Everything seems to be working. Maybe later I'll try what dougfresh suggested and try flashing the Glitch B6 kernel and try to see if the restore works. However at the current I think I'll hold off on any nandroid backups for a while .
i tried also to restore the nandroid after flashing another kernel and still had the same issue...maybe the problem is not with the restore but the backup with the previous versions of MP kernels...
Got an idea Noob. Try to do an advanced restore and restore everything one by one except the boot.img. if it is a kernel issue then this might be a way to bypass it for now until MP or Br1ck'd gets a look at it.
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Br1cK'd said:
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Click to expand...
Click to collapse
The kernel that was backed up was MP's "cwm-subZero-Vibrant-1.0.1VC_build26-BFS_BLN" kernel. However it wouldn't restore even when attempting to restore after flashing the build 26 kernel. It was a very odd issue, during which I couldn't even mount nor unmount /data in CWR. However it apparently works now. Perhaps I'll start testing backups again at a later date, I've already got everything setup again anyhow. I'm again settled down with your amazing work!
PS- Working on a "Royale with Cheese" boot animation. May take some time, but it's in the works
I got the same Can't mount /data! error when trying to restore a backup after trying a build of CM10.
I just did a wipe data/factory reset, then the restore worked.
Hello all. Happy Saturday!
I came on the site after a few months searching for a solution to my problem... I seen that others also had the same problem even on Google
First off I I stalled ICS from cyanogen a few days ago but I feel the phone a bit laggy especially when I type or scroll thru pages.
It doesn't feel fluid, I did do a factory full wipe and it formatted fine and deleted cache ..
So after I felt the problem I decided to format and delete cache again and reinstall ICS from cyanogen to see if it would fix the problem...
But when I now go into clock work recovery and choose the wipe option it starts to format but then when it gets down to SD card data it says something like it couldn't format or mount sdcard/ data! And then stops..
So I decided to Install aokp jb ROM. Thinking maybe that would solve the problem
It installed fine but the problem carried over and its driving me nutsoooo.. it also seems like I can no longer make backups either..
Alittle help would be extremely helpful. Thanks all
It's not a problem.
It's a null error. Means nothing. Stop worrying about it
Raise yer mizzenmast and swab 'er poop deck!
As far as i know it does that so as to not erase your external sd card. At least that's what I heard. From a birdie.
Sent from team Pirate headquarters using Beanacle ROM. As soon as he builds it.
Hey guys, thanks for the quick response.
But as I was saying i don't remember it doing that with previous ROMs.
And it doesn't seem to be making backups either. Or it won't even go back to my previous backups that I made in the past
I never had that problem before all my backups used to work.
Which recovery can we use besides cwm. On the i777?
xxkhbxx said:
Hey guys, thanks for the quick response.
But as I was saying i don't remember it doing that with previous ROMs.
And it doesn't seem to be making backups either. Or it won't even go back to my previous backups that I made in the past
I never had that problem before all my backups used to work.
Which recovery can we use besides cwm. On the i777?
Click to expand...
Click to collapse
Flash back to stock then root again to see if problem persists?
122ninjas said:
Flash back to stock then root again to see if problem persists?
Click to expand...
Click to collapse
That's actually one of the backups I'm trying to flash back to. Or do you mean using Odin?
True or not true when I was researching I read something about ICS or jb changing the file system format and that may cause problems?
xxkhbxx said:
That's actually one of the backups I'm trying to flash back to. Or do you mean using Odin?
True or not true when I was researching I read something about ICS or jb changing the file system format and that may cause problems?
Click to expand...
Click to collapse
using odin
The 6.x versions of CWM recovery uses blobs. It's a different backup scheme all together. Your old backups made with a 5.x or earlier version of CWM recovery will not restore in 6.x version. You would have to first flash a kernel with a 5.x version of CWM recovery, then restore the old backups. You should be able to find a CWM flashable version of the kernel you need, or CWM flash a complete firmware with the correct kernel.
creepyncrawly said:
The 6.x versions of CWM recovery uses blobs. It's a different backup scheme all together. Your old backups made with a 5.x or earlier version of CWM recovery will not restore in 6.x version. You would have to first flash a kernel with a 5.x version of CWM recovery, then restore the old backups. You should be able to find a CWM flashable version of the kernel you need, or CWM flash a complete firmware with the correct kernel.
Click to expand...
Click to collapse
Didn't know that. But why do I get the feeling the cwm is not making a full backup tho. It gives me an error but I'll try to write down what it says. Thank you all