1. Are you ready for the Galaxy S20? Here is everything we know so far!

ROM Backup Help

Discussion in 'Android Devices' started by zanoodi, Dec 19, 2011.

  1. zanoodi

    zanoodi Well-Known Member
    Thread Starter

    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
     


    scary alien likes this.

    1. Download the Forums for Android™ app!


      Download

       
  2. VoidedSaint

    VoidedSaint Resident Ninja

    if you backed it up in cwr then your ok, scary's app may not like the new version of cwm but im not sure, i will send him a pm and alert him to this thread
     
  3. zanoodi

    zanoodi Well-Known Member
    Thread Starter

    Thanks vs. I wanted to try that ics ROM but I also wanted to make sure I have a current back up just in case.
     
  4. VoidedSaint

    VoidedSaint Resident Ninja

    no problem, and trust me i understand ^_^
     
  5. scary alien

    scary alien not really so scary
    VIP Member

    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!
     
  6. scary alien

    scary alien not really so scary
    VIP Member

    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 (Text):
    1. c:\> [B]adb shell[/B]
    2. $ [B]su[/B]
    3. # [B]cd /sdcard/clockworkmod/backup/[COLOR="blue"]ccyy-mm-dd.hh.mm.ss[/COLOR][/B]
    4. # [B]busybox -c nandroid.md5[/B]
    Should show something like this if successful:

    Code (Text):
    1. C:\android-sdk-windows\platform-tools>[COLOR="Blue"][B]adb shell[/B][/COLOR]
    2. # [COLOR="blue"][B]cd /sdcard/clockworkmod/backup/2011-12-20.01.38.13[/B][/COLOR]
    3. cd /sdcard/clockworkmod/backup/2011-12-20.01.38.13
    4. # [COLOR="blue"][B]busybox md5sum -c nandroid.md5[/B][/COLOR]
    5. busybox md5sum -c nandroid.md5
    6. cache.img: OK
    7. data.img: OK
    8. system.img: OK
    9. # [COLOR="blue"][B]ls -a -l[/B][/COLOR]
    10. ls -a -l
    11. ----rwxr-x system   sdcard_rw        274160832 2011-12-19 20:39 system.img
    12. ----rwxr-x system   sdcard_rw        268842816 2011-12-19 20:42 data.img
    13. ----rwxr-x system   sdcard_rw             2112 2011-12-19 20:42 .android_secure.img
    14. ----rwxr-x system   sdcard_rw            76032 2011-12-19 20:42 cache.img
    15. ----rwxr-x system   sdcard_rw              132 2011-12-19 20:43 nandroid.md5
    16. #
    17.  
    I'm betting, however, that you're having a problem with your SD card.

    Hope this helps.

    Cheers!
     
  7. zanoodi

    zanoodi Well-Known Member
    Thread Starter

  8. zanoodi

    zanoodi Well-Known Member
    Thread Starter

    [​IMG]

    Here is the screenshot of the verification failure.
     
  9. scary alien

    scary alien not really so scary
    VIP Member

    Can you post the contents of the nandroid.md5 file, please?

    I'm sure the data.ext3.tar MD5 won't match what AFV calculated, but it would be interesting to see the entries...

    Thanks!
     
  10. zanoodi

    zanoodi Well-Known Member
    Thread Starter


    I would be glad to. How do I do that?
     
  11. scary alien

    scary alien not really so scary
    VIP Member

    You should be able to navigate to that file from something like Astro File Manage, etc., long-press and select "edit", and it should allow you to launch some little editor or browser so you can copy/paste the contents here (it should only be 4 lines of text).
     
  12. zanoodi

    zanoodi Well-Known Member
    Thread Starter

    47ff1e0d91034eaa6d786baf4b4533d2 cache.ext3.tar
    bcf951d5a5572872e7aa45bb98d7bbef data.ext3.tar
    aee17e0b151d6212facf62892ca49cc2 system.ext3.tar
    33f6bbc357da5c67dbb54d180fede5cc .android_secure.vfat.tar
     
  13. scary alien

    scary alien not really so scary
    VIP Member

    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!
     
    zanoodi likes this.
  14. zanoodi

    zanoodi Well-Known Member
    Thread Starter

    I'll give it a try once I find a card and some time to do it.

    Thank you again for all your help.
     

Motorola Droid X Forum

The Motorola Droid X release date was July 2010. Features and Specs include a 4.3" inch screen, 8MP camera, 512GB RAM, TI OMAP3630 processor, and 1540mAh battery.

July 2010
Release Date
0
Reviews
Loading...
Similar Threads - ROM Backup Help
  1. hacknorris
    Replies:
    0
    Views:
    169
  2. TheManWithTheGoldenGun
    Replies:
    5
    Views:
    773
  3. cidea
    Replies:
    4
    Views:
    1,253
  4. Random22
    Replies:
    5
    Views:
    1,409
  5. Dennis ingate
    Replies:
    4
    Views:
    728
  6. Ravikmr
    Replies:
    2
    Views:
    2,595
  7. SpanDragon18
    Replies:
    2
    Views:
    2,069
  8. krakengz
    Replies:
    4
    Views:
    657
  9. N4ty_Kitty
    Replies:
    2
    Views:
    6,482
  10. LuckyBit33
    Replies:
    4
    Views:
    2,108

Share This Page

Loading...