• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ROM Backup Help

zanoodi

Well-Known Member
Jan 10, 2011
184
35
I need some help with backing up my current ROM. I am currently running Revnumbers GBCM7, build 10/19 I believe. I tried backing up my ROM through ROM Manager and through CWR but when I verify the backups with Scary Alien's Android File Verifier, awesome app btw, it says that the verification failed each and everytime regardless of the method used. I am running CMR version 5.0.2.0, could that be the culprit? Should I switch to an older version? 2.5.0.7 is the only other option through ROM manager. Any help or advice is appreciated. TIA
 
  • Like
Reactions: scary alien
I need some help with backing up my current ROM. I am currently running Revnumbers GBCM7, build 10/19 I believe. I tried backing up my ROM through ROM Manager and through CWR but when I verify the backups with Scary Alien's Android File Verifier, awesome app btw, it says that the verification failed each and everytime regardless of the method used. I am running CMR version 5.0.2.0, could that be the culprit? Should I switch to an older version? 2.5.0.7 is the only other option through ROM manager. Any help or advice is appreciated. TIA

zanoodi,

Sorry for the delay in getting back to you...was a pretty busy day at work and I'm just now catching-up on things.

Thanks for the kind words about my app :)...I very much appreciate it :).

I've been doing a "Verify Nandroid Backup" on my ClockworkMod Nandroid's since Friday (done at least three of them without issue).

You are navigating to inside the ccyy-mm-dd.hh.mm.ss folder inside /sdcard/clockworkmod/backup and long-pressing the nandroid.md5 file, correct? (I have a new version that will allow you to simply select the folder to do this, but its not yet finished).

Can you check the MD5 checksums of each file in the backup folder individually and compare those values to what's in the nandroid.md5 file? (that's what AFV does and what an md5sum -c command will do).

edit: disregard the stuff I wrote below...I was thinking this was the Gnex...I have another idea...give me a minute to reply...

I think the most recent version of ClockworkMod is 5.5.0.4, so that might be the issue...

I have seen some wonky behavior myself with how the internal SD card behaves and seen a few report issues even being able to make a Nandroid backup without it failing (i.e., reporting that the SD card is not mounted).

I would try to flash a newer version of CWM and see if that helps.

Let us know.

Cheers!
 
Upvote 0
zanoodi,

Apologies! I had my wires crossed re. which device I was responding about :eek:.

My version of ClockworkMod on my DX is 2.5.0.8 though...

I have heard of folks having issues making and verifying Nandroid backups that turned-out to be SD card related...

Can you try switching to a different card?

Also, if you are adb conversant and have a busybox installed, you should be able to do this, too:

Code:
c:\> [B]adb shell[/B]
$ [B]su[/B]
# [B]cd /sdcard/clockworkmod/backup/[COLOR="blue"]ccyy-mm-dd.hh.mm.ss[/COLOR][/B]
# [B]busybox -c nandroid.md5[/B]

Should show something like this if successful:

Code:
C:\android-sdk-windows\platform-tools>[COLOR="Blue"][B]adb shell[/B][/COLOR]
# [COLOR="blue"][B]cd /sdcard/clockworkmod/backup/2011-12-20.01.38.13[/B][/COLOR]
cd /sdcard/clockworkmod/backup/2011-12-20.01.38.13
# [COLOR="blue"][B]busybox md5sum -c nandroid.md5[/B][/COLOR]
busybox md5sum -c nandroid.md5
cache.img: OK
data.img: OK
system.img: OK
# [COLOR="blue"][B]ls -a -l[/B][/COLOR]
ls -a -l
----rwxr-x system   sdcard_rw        274160832 2011-12-19 20:39 system.img
----rwxr-x system   sdcard_rw        268842816 2011-12-19 20:42 data.img
----rwxr-x system   sdcard_rw             2112 2011-12-19 20:42 .android_secure.img
----rwxr-x system   sdcard_rw            76032 2011-12-19 20:42 cache.img
----rwxr-x system   sdcard_rw              132 2011-12-19 20:43 nandroid.md5
#

I'm betting, however, that you're having a problem with your SD card.

Hope this helps.

Cheers!
 
Upvote 0
Screenshot_2011-12-20-09-55-18.png

Screenshot_2011-12-20-09-57-13.png

Screenshot_2011-12-20-09-58-41.png

Screenshot_2011-12-20-09-58-59.png

Screenshot_2011-12-20-09-59-40.png
 
Upvote 0
47ff1e0d91034eaa6d786baf4b4533d2 cache.ext3.tar
bcf951d5a5572872e7aa45bb98d7bbef data.ext3.tar
aee17e0b151d6212facf62892ca49cc2 system.ext3.tar
33f6bbc357da5c67dbb54d180fede5cc .android_secure.vfat.tar

Ah, yep, if you compare the MD5 sums that AFV reported for data.ext3.tar vs. the entry in the nandroid.md5 file that ClockworkMod created (via its md5sum commands), they are clearly different.

I can't explain other than it certainly identifies a discrepancy that shouldn't be ignored (I certainly would not restore a backup that had an MD5 sum mis-match--you could certainly replace the MD5 entry in the nandroid.md5 file with what AFV reported and CWM will allow you to restore it--but you'd be ignoring this intended safety feature).

My bet is still on a bad SD card at this point...let us know if you try a different card and what the results are.

Thanks!
 
  • Like
Reactions: zanoodi
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones