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.....
Related
I rooted my Desire S and now I want to install a ROM on it, this is my first time so I'm being a little cautious.
How do I make a full backup of my phone? In the case I don't like the ROM and want to return to how my phone is now, is this possible?
If so, how to make this backup? And how would I restore my phone back to it?
Thanks!
Assuming you've rooted your phone and put a custom recovery on it (4EXT or CWM), run a backup - also called a NANDROID backup - and that will give you an image saved on your SD Card that you can restore if you ever need to.
Alright, I've got CWM and just did a NANDROID backup, it created 6 files on my sd card, which are:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
How do I used these files to restore back to if I ever need to?
Just go into CWM again and select 'Restore'. I don't know if it is 100% necessary, but I always do a full wipe of all partitions (except for sdcard) before restoring as well just to be certain.
Alright, thanks for that!
Since that back up is done, going to back up all my app's now then flash my first ROM
Assuming (again) that you are using Titanium Backup to backup your apps - although this is probably true for other backup methods - be careful when restoring. There can be problems if you are restoring Sense app backups to an AOSP ROM or vice-versa. If you start getting problems post-restore then try restoring a few apps at a time to see if you can pin-down the problem app. From my experience, it's often better to install the app fresh from the marketplace and then restore just the settings (if you need them).
Make sure to use md5 sum check and verify them after every backup. It's good practice to avoid corruptions.
I use 4Ext control for that
Sent from my HTC Desire S using xda premium
This is weird...I'm running cm10.1.2 using latest version of TWRP
So, today I made a nandroid backup. I choose to backup everything- cache, system, recovery, boot, data and I always choose to enable compression and I do not skip generate md5.
Well everything appears to be successful and it shows backup successful once it's done but the process is taking 200 seconds, seems faster than normal.
I go to look in esfile explorer to make sure it worked and it's not there. Ok, so I make another one...same thing. I looked everywhere and I can clearly see that I have the same amount of space in storage as I did before making those two full nandroids.
I don't know what's going on. Twrp says successful but there's no b/u
Any ideas?
Okay wow, I'm very confused and have been Googling/reading the forums for hours now. I'm a complete noob and here's exactly what I did.
Currently have CWM touch v6 and Cyanogenmod 11
1. I have been running everything for a month with no problems at all.
2. I made a backup of my stock rom before I switched to Cyanogenmod 11, and I've also tested going into it and back to 11 in the past.. I know it works!
3. Today I decided I wanted to go into the the stock rom again and view some old text from my gf.
4. Before going back to my old stock backup, I decided to make a current backup of my Cyanogenmod 11
5. I also decided to make sure that one worked, so I made another backup of my current 11
6. Upon trying to access the backup I ran into a md5 hash error and noticed it wasn't creating a nandroid file for the cyanogenmod backups like it did for the old stock rom backup.
7. I went in and created a new file blank file "nandroid.md5" for both the Cyanogen backups I created.
8. Upon trying to restore again, I now received, "error while restoring /data!"
9. I was able to access the rom, however it only seemed to have loaded a partial amount of my /data ...I even I had to go back through the cyanogenmod prompts as if I freshly installed the rom, but my text messages/apps were all there.
10. I then attempted to wipe everything (using the wipe settings cache/dal/etc in CWM) and install the stock rom (since I know it works). Again I received the, "error while restoring /data!". But, again the same story, it loaded the stock rom, but with partial data and as if I freshly installed it.
11. I found online the problem could be due to the partition size not being able to handle the backup size (and my backups are over 600mb)..I deleted the stock rom (taking up 1gb) and again tried to install my Cyanogenmod 11 backup, to again be greeted with, "error while restoring /data!"
QUESTION 1:. I've read that using the Titanium app or nandroid manager can help alleviate the issue by restoring items, but how can I solve this annoying "error while restoring /data!" error?
QUESTION 2: I have the entire backup folder pulled from adb on my desktop, would it be advisable to use the format /Data and /Data/Media option on CWM and then push the Cyanogenmod 11 backup back into my phone and then try restoring? I've also read someone was able to factory restore their phone from settings, then try restoring the rom.. is this advisable?
Thanks in advance for the help, I have a headache
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
Hi i need help ASAP,
I backed up my phone with CWM it made a folder as a backup.
When I tried to restore the backup I navigated to the folder and it showed me inside that folder (like there are no files) instaed of starting the backup procces.
one more problem is that now i flashed another ROM with TWR and I didn't know it will be with TWR so I am not sure I can backup CWM with it.
please refer to my 2 questions as it combined.
Can you clarify if CWM is able to restore the Backup ? If its not, then the backup was not made successfully.
To your Question, are you saying you flashed TWRP Recovery and then flashed the new Rom ? If that's the case then the CWM backup can't be restored by TWRP.
EDIT - I should caution you that it is not a good idea to restore the backup made by one Recovery with another.