- January 27, 2016 at 1:44 pm #7786
I have tried several times to do a nandroid backup with a few different settings, but it fails at the hash check every single time. The files do end up on my PC. My most recent attempt was just a data partition backup, no compression – full log: http://hastebin.com/imukeposum.texFebruary 8, 2016 at 5:36 am #7861
Having the same issue. Checking the backup files manually and comparing to the md5 generated on backup shows that the files are valid (verified and checked w/Cygwin md5sum) for all the .WIN files that are created.February 8, 2016 at 5:47 am #7865
And just to show the md5sum check is correct:
$ for i in
> cat $i
> md5sum $name
5bb6cdc8993282bb1fecd537f00203cb *system.ext4.winJuly 31, 2016 at 3:02 pm #9446
Same problem (MD5 Verification errors) doing a full Nandroid backup from NRT V2.1.6 of a Nexus 10. However I noticed that when I use “Raymond Lin’s MD5 & SHA-1 Checksum Utility” to check the files using the existing MD5s it changes the alpha characters in the MD5 to upper case and verifies the backup file. Is this a TWRP or Nandroid problem?
I love NRT and wish I had discovered it a long time ago. Thanks for the work!August 21, 2016 at 1:44 am #9634
This is an NRT issue. Your files are being properly backed up to your comp, but the hashcheck for that operation is using an incorrect file path. This hashchecking system was something I created that is very unique, and just wasn’t quite right for that operation in current public release. v2.1.7 is near completion and this is fixed, among many other improvements.September 14, 2016 at 11:04 am #12639
Is there a workaround for this then? I am attempting to restore a nandroid backup. Can I use a different tool? I tried checking to ignore MD5 verification but it seems to still error out.June 10, 2018 at 7:24 am #24581
Seems this bug is back but just for when you do a Restore (of Nanoid). It seems when it does a md5 check on the files it pushed to the phone it is giving the incorrect file path. So i get a lot of file not founds and hence md5 fails.
I get a sense the author has abandoned this project but felt i should post anyway for posterity reasons so random people in the distance future who do come here by accident will see and say “ohh that poor soul never did get a reply”, chuckle, and hit the back button. 🙁 🙁
You must be logged in to reply to this topic.