I was doing a nandroid backup to test some features. but to my surprise when I tried to restore sd-ext is unable to be restored.
I am using clockwork 3.0.0.5. I even tried the advanced restores, but it seems to just get "stuck".
I looked on the backup folder, and I do see the sd-ext with a 600mb size.
How do I manually get that uncompressed and into my sd-ext partition?
I'm having this same issue. I thought it was just taking awhile... its still recovering an hour into it. Seem to be wrong on that assumption. I'm worried that this might be a severe bug in 3.0.0.5.. I guess I can always downgrade and try again.
My sdext somehow became corrupted. I had to run the command in terminal:
mke2fs /dev/block/mmcblk0p2
However replace mmcblk0p2 with the one applicable to your phone.. it could be different although I think unlikely but you could end up formatting the fat 32 partition. I ended up formatting my sdcard to FAT32 first then made the partition and did it via the alternative recovery, not clockwork. I think it depends on what partition was created first.
The command mk2fs formatted and fixed the sdext partition. Afterwards did a restore (using the old recovery 2.5.1.4 and a backup made with that recovery) and it worked.
Unfortunately I still have a md5 checksum error on my very latest backup with the latest clockwork recovery and the old 2.5.1.4 recovery. I'm back on cyanogen 6 as the one made right after flashing 7 is gave me the md5 checksum error.
I believe there might be issues with the new clockwork 3.0.0.5 on restoring backups made by the previous version (which caused the corruption in either the sdext and/or the backup file itself) and/or issues with the cyanogen 7 nightlies making proper backups on the previous version of clockwork. I don't have any other cyanogen 7 backups to test this theory nor do I have the time with a test tomorrow. Could just be back luck. I'm just glad I finally figured it out and have my phone back to the way it was.
Will backup more often for sure...
I am not sure how or why but I have had two instances now where the Nandroid backup has failed. Once with a backup of CoreDroid 4.9 MD5 mismatch wont restore and once now with CoreDroid 5.0 same error when i try to restore. I have tested and verified that it is not the rom.
I did a full wipe again
reinstalled full version ROM
set it up with a few apps
did a nandroid backup
rebooted
restored backup from SD card
Restored and booted no issue
All Normal! I do not know what happened on the other two backups?
Normally I boot to CWM by means of Rom Manager which gives you the option to name your backup. It is possible that I did those by means of CWM (Going directly to CWM with ADB) which does not allow you enter a name. It just starts and assigns it a name (number) and then I changed the name later on? Not sure. I am also not sure if this would cause a MD5 mismatch?
Always a concern if a backup does not work 100% of the time until I find a cause.
Has anyone seen this before?
Thanks all.....
Has there been any other reports of this? This is the first time I have had an error with CWM and I have had it twice.....
Hey everyone, i have an HTC Desire C, with CWM 5.5.0.4 installed.
My problem is that i cannot do a nandroid backup.
Whenever I try to backup with CWM, it completes backing up my system, but at about halfway of backing up my data it reboots automatically.
When I check the backup folder afterwards, it contains 4 files:
recovery.img, boot.img, system.ext4.tar and a data.ext4.tar that is 0 bytes. There are no .md5 files.
I have tried to backup my device over 10 times and it has only worked once.
What can be wrong?
I've made a backup using stock recovery. But I am unable to restore it due to checksum error. Now that I've installed CWM, it doesn't shows that backup file. Is there any way I can have a restore of the my original .backup file?
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Have a look at and/or post your log from twrp. You can find this under advanced options then copy log or use the command adb pull /tmp/recovery.log.
Also, I know in the past titanium backup hasn't been great at extracting nandroids. Try https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore and see if it makes a difference.
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Have you actually tried using the backup to restore? You sure the app you are using to check isn't the issue?
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Switch to Philz it will handle twrp bu's too. You can watch the md5 check going on before you command the restore to take place. At least on 624.
Thanks for the help and suggestions. Here's what I found:
Tried TWRP 2.6.3.1, 2.6.3.0 and 2.7, all with the same result. Corrupt files. I verified this using Android File Verifier (great utility, used for years). When running Calc MD5 checksums on the individual backup files, some would verify and others would not.
Running multiple backups with each version resulted in failed backups. On a weird note, I could not remove the TWRP directory using either Root Explorer or ES file explorer. Both would cause the phone to reboot. The only way I could remove the directory was using file manager in TWRP.
Switched to Philz recovery and ALL backups verified just fine! Although it doesn't have the fancy interface or some of the features of TWRP, it gets the job done!
My conclusion is that there's some sort of issue with TWRP writing to the internal SD as proven with the incomplete backups and the directory problem it caused on the SD. I would recommend others use the Android File Verifier to make sure they are getting complete backups!
Mike
I just installed twrp and completed my first nand, the adv program said everything was fine. So I should be safe finally