sharpe351, on 27 September 2011 - 04:31 PM, said:
I knew you would be the one to ask. I did one already in cwm. I wasthinking that this may actually be a bit quicker. I read the thread on XDA. I figured you may shed some more light on it than I could get from what I read. Thanks. I've also been having trouble using some commands in nvflash to flash clockwork and a new boot logo. It keeps telling me permission denied. I know I'm typing something incorrectly, but I'm not sure what.
sent from my AOSP CM7 Gtablet with Clemsyn Kernal using Tapatalk
Don't mean to rain on the parade but IMO, nand backup/restore in CWM is much more comprehensive than nvflash backup. Nand bckup takes a snapshot in time, saving not only the nand partitions, but also the /data partition & the .android_secure mount point that reside on the internal sd. Restoring from a nand backup will restore the entire os, system & user settings & all installed apps.
Nvflash only backups the nand partitions. If you do use nvflash to do a backup & later do a restore of it, you must be sure to to a factory/data reset, wipe cache & wipe dalvik after the restore (so that you don't use possibly corrupt data/apps/settings left over from the previous installation).
For those situations that you can not enter CWM, I believe it is faster (and more reliable) to nvflash to the factory image, install CWM & then restore the nand backup (that includes all your apps & settings).
If you read post#42 on the thread Mike identified, you will note that rajeevvp does not recommend using nvflash to backup & restore for the reasons I noted. If you take another look through the thread you will see user "aabbondanza", that's is me.
Nvbackup does have it's uses though. I think it's a great tool to make a copy of your original image so that you always have a copy & especially for your original boot config table (bct - partition 2) & partition table (PT - partition 3).
This post has been edited by AlAbbo: 27 September 2011 - 07:23 PM