Is there a way to Verify a Nandroid? - Nexus One Q&A, Help & Troubleshooting

The topic says it all, is there a way to verify the integrity of the nandroid backups we make? Sometimes after doing nandroid backup and I have to come back to restore it, i find out that the backup is corrupt or faulty and the nandroid backup wont work. Either it will hang in the restoring process where the little dots "..." keep going or it says cant restore or something

I think with Clockworkmod recovery will give you an MD5 sum for every back up, not a 100% sure tho.

joshlusignan said:
I think with Clockworkmod recovery will give you an MD5 sum for every back up, not a 100% sure tho.
Click to expand...
Click to collapse
Can anyone confirm? Is there a way to verify if we're using amon's 1701?

A MD5 sum is only going to help provide integrity that the FILE contents haven't changed since you did the MD5 hash of the backup...this doesn't actually verify that the backup will restore properly.
I too wondered this same thing as i've had backups that wouldn't restore.
Mike

You can always try to restore the nandroid before doing anything else. I guess the catch may be that if it does fail, who knows what state your phone might be in. What about backing up twice and comparing the md5sum?

You probably have a bad sd card.

Related

Nandroid won't complete a backup

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.

Nandroid md5 mismatch

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.

[help]back up and restore in CWM!!!

today i wanna try my cwm backup work or not, so i make a back up and try to restore it, then i get this.... i can't get in android anymore... why is that??
Checking MD5 sums...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext/..
some people said cwm backup reliable... i never get a successful restore, before was system.img not found, now like this.... it's cause too much trouble, i know i can use odin reflash everything back, but i just want to know what exactly went wrong to cause such a problem? pls help me

Nandroid recovery problem - MD5 mismatch/Error restoring boot image

I accidentally did a factory reset while in Safe mode. My first time ever getting into Safe mode and I have no idea how I got in there, only realized after the wipe. Thus, I lost all my pictures, videos etc... I made a Nandroid backup before the wipe so that got deleted as well. I have another Nandroid backup on my SD card that I have been trying to copy to the phone's internal memory but I keep getting errors.
First error on CWM was the annoying MD5 mismatch - I think I was able to fix that with the terminal emulator and the Notepad++ and MD5 calculator. Then the next error was, 'error restoring boot image.' I made this Nandroid backup with Semaphore 2.7.4 and still is my kernel now.
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it? I've tried PhotoRec and Recuva already and they didn't work for me. PhotoRec gave me weird filenames and Recuva didn't find the stuff I was looking for. I still have this untouched backup on my SD and everything else on the SD works by the way.
Zytorious said:
I believe this Nandroid recovery is corrupted. Is there any chance of recovering it?
Click to expand...
Click to collapse
Have you tried to flash your semaphore kernel + recovery via Odin/Heimdall, so you have a clean recovery?
Cheers
EDIT: If this isn't working for you, you are always able to flash a stock samsung rom and then get back to your current rom + recovery.
If this does not work, i would guess your backup is corrupted. Had this by myself in the past... corrupted backups

[Q] Bootloop "Unfortunately the process com.android.phone has stopped"

Hi everybody !
I have a very annoying issue with my Nexus 6
I did a full nandroid backup with TWRP before sending it for RMA
I received yesterday my phone repaired, and I have tried to restore my nandroid backup
unfortunately, I've got a bootloop with the message "Unfortunately the process com.android.phone has stopped"
Can somebody help me please ? thank you very much
I will be very grateful...
MrMoi said:
Hi everybody !
I have a very annoying issue with my Nexus 6
I did a full nandroid backup with TWRP before sending it for RMA
I received yesterday my phone repaired, and I have tried to restore my nandroid backup
unfortunately, I've got a bootloop with the message "Unfortunately the process com.android.phone has stopped"
Can somebody help me please ? thank you very much
I will be very grateful...
Click to expand...
Click to collapse
You can't restore a back from one device to another. Boot to recovery and do a full factory reset. You'll have to set it up as a new device.
This is triggered by the phone application or sim card application. Can you get into bootloader or twrp?
thank you !
but it's the same phone, just the screen is new
And I have access to twrp and the bootloader of course
Nobody ? I can pay for a solution...
MrMoi said:
Nobody ? I can pay for a solution...
Click to expand...
Click to collapse
Have you tried a factory reset in recovery, as I suggested previously?
You can try to flash system.img using fastboot (download factory image from developers.google.com/android/nexus/images, and extract system.img, and fastboot flash it - no guarantees it will work, but worth a try )
I have already try to flash only the system.img
And a factory reset works.. But I wont lost everything ..
MrMoi said:
I have already try to flash only the system.img
And a factory reset works.. But I wont lost everything ..
Click to expand...
Click to collapse
Pick your poison...
if someone know which apps cause the issue, I can try to delete it with adb shell
You have a nandroid backup, so do a full reset to get the phone up and running again...
After that, let the Google backup feature install all your apps from the playstore and then use Titanium Backup to restore data only from the nandroid.
I've flashed a clean system, and after I tried to restore my app with Titanium Backup with my nandroid backup but it doesn't work..
Details please... "It doesn't work" doesn't say anything.
Stop using the nandroid to restore things.. They almost always cause issues. Also never restore a nandroid after a repair. The parts are different. So things could easily get messed
I use Google backup and MyBackup Pro.
When I try to restore with titanium backup, I can browse my nandroid backup, see all my apps.. Restore them (it tooks long time ) titanium tell me "success" but nothing append
zelendel said:
Stop using the nandroid to restore things.. They almost always cause issues. Also never restore a nandroid after a repair. The parts are different. So things could easily get messed
Click to expand...
Click to collapse
There's a reason he has zero thanks. He won't listen to advice....
cam30era said:
There's a reason he has zero thanks. He won't listen to advice....
Click to expand...
Click to collapse
I would like.. but a nandroid backup is the only backup that I have ... for the next time, I will do a different backup..
Do you have a better alternative for the next time ?
for the moment.. I have only a nandroid backup.. I need to try with it
MrMoi said:
I would like.. but a nandroid backup is the only backup that I have ... for the next time, I will do a different backup..
Do you have a better alternative for the next time ?
for the moment.. I have only a nandroid backup.. I need to try with it
Click to expand...
Click to collapse
Just flash stock, it's that easy!
As long as you sign in with the same Google account that was previously on the device, there will be something in the setup asking if you would like to restore from a previously used device, and you just select Nexus 6 from the drop down menu (make sure you select the right date), it will restore all of your apps, contacts, and it'll be back to normal within a few minutes. You'll lose your app data, but this doesn't matter much unless you play games. You'll have to flash twrp and root again, but at least you'll have a working device.
Although this is coming from someone who doesn't have any important data on their phone, it doesn't matter. You still have between having a device that doesn't boot or starting fresh. It's kind of fun sometimes .

Categories

Resources