I go back and forth between cm6 and 2.1, and I have messed something up. I was going from cm6 to 2.1, wiped my data and cache, and went to restore, but accidentally hit backup instead. My phone acted like it was backing something up, and when it was finished I wiped again and tried to restore my 2.1 nandroid. It said there is an md5 mismatch. Restored my cm6, which worked fine, then wiped again and tried to restore my 2.1 nandroid and got the same mismatch message. Could it be because I did a backup after I wiped, or could there be another reason? That nandroid worked great until now. Many thanks in advance.
Sent from my HERO200 using XDA App
Did you change the name of the folder in which the Nandroid backup was stored? If so, revert it and try.
If not, you could generate the md5 and try restoring, but I would not recommend doing that.
Related
i did a nandroid backup and tried restoring it, and it gets stuck at the bootscreen.
any ideas?
Did you wipe before restoring?
yup, complete wipe
come on guys. when i do the restore on kingklicks 2.1 it loops the nexus one bootscreen
smjfosho said:
come on guys. when i do the restore on kingklicks 2.1 it loops the nexus one bootscreen
Click to expand...
Click to collapse
I want to preface this by saying it is a guess.
Theory 1
Since the rom had written data to the EXT partition, when you wiped before restoring, it is looking for something on that partition???? You may need to start over with Kingklick. If you use Bart or Switchrom to do your backups, you should always be able to restore without need ing to wipe.
Theory 2
After you wipe (everything) make sure you "repair ext" from the recovery menu.
i did a BART backup and restore and that worked perfect
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me? Thank you
Nothing to see here, move along.
Thanks bud you are sooo helpful.
Sent from my SAMSUNG-SGH-I897
koreancanuck said:
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me?
I am not sure but do you only have one backup you are trying to use? Could be an issue with backup. Is three any lag fix in the equation? It sucks but if three worst of it is you can flash the rom but not restore your apps then I guess consider your self lucky
Captivate
Cog 2.4
Click to expand...
Click to collapse
Yep. I disable my lagfixes before doing restores. To be honest it's not that big of a hassle since I can just use tibu pro and do one click restore for apps and restore my settings as well. And nandroid takes so much longer on captivate than magic D: Still it would be nice to always go back..
Sent from my SAMSUNG-SGH-I897
Ok so i had an issue with flashing a theme so i had to restore my nandroid backup. The backup took quite a long time (i backed this up about a week ago). Now when im tried to restore, everything was going fine but now its stuck at this:
ClockworkMod Recovery v2.5.1.3 - Voodoo lagfix
Checking MD5 sums...
Restoring system...
Restoring data...
databases
It's been stuck there for a loooooong time.. Anyone know whats up?
Hey guys,
I used odin to get boot it back up and then I used ClockworkMod to restore backed up data....
After phone said 'restore complete,' I let the phone reboot, but the phone will not reboot
at&t screen pops up and then black out then pops up again then into android recovery mode.
Any ideas?
Could you please provide a little more information about how you got to where you are? (e.g. what rom/kernel/modem/theme you were flashing, what ODIN you used, what version of CWM, etc.) Anything you provide will be helpful in troubleshooting.
Well I had cognitive 4.5.3 installed and I tried restoring using clockmod recovery
the restore wasn't successful and the phone would stay black screened after Galaxy S logo screen
So I turned on odin3 and put my phone on download mode then hit start on odin3
that successfully restored the phone to froyo 2.2 without any of my data
so I tried using clockmod recovery once again to restore the backup
and then... that's where I am
The phone won't boot. It will just go into recovery mode
Here's the message I got after trying to restore once again
--------------------------------
ClockworkMod Recovery v2.5.1.2
Checking MD5 sums...
Restoring system...
Restoring data...
Restoring datadata...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext/.
Restore complete!
--------------------------------
When did you make that nandroid backup? If you made it while on stock, you'll have to go back to stock first, then run the restore command. If on cognition, you'll need to be on the version you were on when you made the backup and restore there.
Here's the link I found on how to return to stock rom
http://forum.xda-developers.com/showthread.php?t=731989
I've done the first part - before the master reset and then tried restoring the backup and that is how I got to where I am right now.
Do I need to factory reset as well?
If I do factory reset, won't that erase the backup file?
Thanks. I really appreciate your help
jc830 said:
Here's the link I found on how to return to stock rom
http://forum.xda-developers.com/showthread.php?t=731989
I've done the first part - before the master reset and then tried restoring the backup and that is how I got to where I am right now.
Do I need to factory reset as well?
If I do factory reset, won't that erase the backup file?
Thanks. I really appreciate your help
Click to expand...
Click to collapse
To answer your question, doing the master clear will erase EVERYTHING stored in the phone's internal memory. Don't do that step now, as you should be able to get out of where you are without doing that.
I think where your problem occurred is that at some point you made a nandroid backup in CWM, and by trying to restore that on stock, it's freaking out. If you can remember what ROM setup you had on your phone when you made the backup, you could try to get back to that setup to use the restore option in CWM.
Before doing any of the things you're doing now, had you made a backup in Titanium Backup?
I do have backup made with Titanium Backup.
apps data and everything that I could backup with Titanium Backup
Will restoring what I had backed up with Titanium Backup and then restoring the system using CWM work?
I am currently at 2.2 Froyo, which was the rom I was using when backing up using CWM
You've flashed 2.2 stock? If so just flash the rom you previously had with cwm then let it boot. After it boots reboot into cwm then perform a restore in cwm. If that doesnt work nand backup might not be good and you will just have to flash stock again and just rub tibu and leave it at that.
**Thing about NAND backups is that you have to use the same system when you restore (i.e. you nand backup usng cognition then you flash another rom when you nand restore its not going to boot).
Thanks guys for the suggestions!
My phone has been saved!