Hey guys,I've been testing roms today om my device,so I made a nandroid of my LeeDroid 2.2.3 setup.I checked my first backup with AFV(Android File Verifier,very nice app,I found it in the market) and cache.img and data.img were corrupted.I deleted it and made another backup.I checked with AFV and all was ok.I installed MDJ's rom,RCMixHD 6 and some other stuff,but later,when I wanted to come back to my LeeDroid rom,I tried to restore but CWM(3.0.2.8) gave me an MD5 Mismatch message.Now I have to start from scratch once again.Luckily enough,I backed up everything with Titanium,just in case.
Thing is,it's not the first time this is happening.At first I thought it was my CWM version,but none has worked well,and I've had 2.5.1.3,3.0.0.6,3.0.2.4,3.0.2.6 and 3.0.2.8.Anybody knows why this is happening?Cause I'm getting sick of it!Plus there is no AmonRA for the DHD.
Anyway,is there any way of manually restoring my supposedely corrupted data.img via adb or something?Even if it is corrupted,something won't work well but at least I will have tried!
Many thanks in advance,
Apostolis
Idea:
Could I "trick" CWM into restoring the "broken" nandroid backups by generating a new MD5 with MD5 Generator?If yes,there won't be any real danger other than having bootloops etc,right?
Two thoughts
Your SD card is corrupt
You actually have some corrupt data on data which is erroneously leading a AFV to report a corrupted backup
Personally I backup and restore all the time with nandroid with no hassle, I suppose the other thing is a rom specific issue as I'm using cm.
You've not been renaming your backup files or anything have you?* You shouldn't be getting MD5 mismatch errors unless the file has been changed somehow since it was created.
*because that's exactly what I did; renamed them when I moved them to my pc for easier filing. Then of course none of them worked until I eventually realised and changed them back
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Thanks for your replies guys.
Firstly,there is a chance the SD is ****ed up,because I had some photos' thumbnails missing the other day.Now,if something in /data was corrupted...Well,maybe!I'll format my SD sooner or later and see...It's 16 freakin' gigabytes!
Secondly,no,I never renamed my backups to anything else.
Can anyone answer my question though?Could I trick CWM into restoring those backups?Would it hurt to try?
tolis626 said:
Could I trick CWM into restoring those backups?Would it hurt to try?
Click to expand...
Click to collapse
I don't think you can, It's a safety feature to prevent you from flashing a corrupt image.
How have you flashed your recoveries? Via ROM Manager or fastboot?
MD5 checksums are generated from the contents of a file, filenames are not included in this generation, unless of course there are filenames within the file that have been modified.
andyharney said:
I don't think you can, It's a safety feature to prevent you from flashing a corrupt image.
How have you flashed your recoveries? Via ROM Manager or fastboot?
MD5 checksums are generated from the contents of a file, filenames are not included in this generation, unless of course there are filenames within the file that have been modified.
Click to expand...
Click to collapse
Ahaa...
I flash my recoveries through fastboot.Since I learned how to use it(I was afraid I'd somehow **** up at first)I flash them through fastboot.How is that relevant?
Anyway,I haven't modified anything.If I had,it'd make sense,but it doesn't.I didn't mess with the backup's files in any way,yet it got corrupted.Am starting to get desperate here...
I only asked because I know *sometimes* you have to flash recoveries twice within ROM Manager.
If the MD5 of the Recovery.img you flash is correct, then the problem has to be somewhere else. Other than checking your SDcard for errors & formatting, I'm not sure much else can be done.
andyharney said:
I only asked because I know *sometimes* you have to flash recoveries twice within ROM Manager.
If the MD5 of the Recovery.img you flash is correct, then the problem has to be somewhere else. Other than checking your SDcard for errors & formatting, I'm not sure much else can be done.
Click to expand...
Click to collapse
Pff...I start to miss my Desire's flexibility!
Anyway,many thanks for your time man!Will see what I'll do...
I just checked my card for errors and there was indeed something wrong!Possibly my card is damaged somehow.It gives me problems too often.Or it's the phone,cause I used the same card on my Desire with no problems at all.Time will tell...
You can expect more people reporting similar issues here soon.I posted in LeeDroid's thread about it as a reply to andreasy and he has a similar problem.
Related
Is it possible to rename a folder created by a nandroid backup and still have it to work?
I have 3 or 4 roms backed up and it's geting difficult to remember which is which
poddo said:
Is it possible to rename a folder created by a nandroid backup and still have it to work?
I have 3 or 4 roms backed up and it's geting difficult to remember which is which
Click to expand...
Click to collapse
Yes it is possible.
I do this and it works:
\SDCard\nandroid\HT9APNT01015\ *custom named folders with img files inside*
Did you get that?
that's what I tried to do, but it seems nandroid didn't like its backups anymore after renaming the folders
when i 'Nandroid' restore the phone, do i have to reroot my phone? Or is root access still available? (Again, i'm new to the custom ROM world and getting familiair with the basics)
doing a nandroid backup is like creating an image of the phone software.
once you restore, your phone revert back being exactly the same as when you did the backup (rom wise, which includes root)
poddo said:
doing a nandroid backup is like creating an image of the phone software.
once you restore, your phone revert back being exactly the same as when you did the backup (rom wise, which includes root)
Click to expand...
Click to collapse
Thanks, i back-upped the phone after root was enabled, so it won't harm my root access.
poddo said:
that's what I tried to do, but it seems nandroid didn't like its backups anymore after renaming the folders
Click to expand...
Click to collapse
Hmmm, that is weird. I wonder if it has to do with the type or version of recovery image you have. At the moment I have RA-hero-v1.6.2.
Just to be clear, if you don't rename the folders, it restores properly?
it does, just one time it happened the backup got corrupted and wouldn't let the phone boot after restore (I am using same recovery img as yours)
I'm going to try renaming the folders again later
I wish you luck! Could you please post back with the result? I am very curious.
In my ongoing travels on the internets I will keep an eye out for a possible solution.
looks like this time it worked.
for some reason nandroid it seems nandroid has an erratic behaviour from time to time.
first time I made a copy of my first (working) backup and I renamed it, nandroid won't let me load it (thus why I created this thread); yesterday, after working fine it created a corrupted backup and I had to reinstall cronos from scratch.
only difference between my first try renaming backup directories is that the first time I made the copy via windows, while the second time I did it through Astro.
I'm going to watch into this.
EDIT: k, sorted the renaming issue. nandroid simply won't handle folders with spaces in their name
still, a couple times nandroid produced corrupted backups and this is forcing me to backup 3 times in a row just to be sure. :/
poddo said:
looks like this time it worked.
for some reason nandroid it seems nandroid has an erratic behaviour from time to time.
first time I made a copy of my first (working) backup and I renamed it, nandroid won't let me load it (thus why I created this thread); yesterday, after working fine it created a corrupted backup and I had to reinstall cronos from scratch.
only difference between my first try renaming backup directories is that the first time I made the copy via windows, while the second time I did it through Astro.
I'm going to watch into this.
EDIT: k, sorted the renaming issue. nandroid simply won't handle folders with spaces in their name
still, a couple times nandroid produced corrupted backups and this is forcing me to backup 3 times in a row just to be sure. :/
Click to expand...
Click to collapse
Glad you've found the issue! That is really weird about Nandroid creating corrupted backups...
It is so strange that using Windows (or not) creates or solves problems. I've read of instances where creating a goldcard with Win7 failed but WinXP worked.
Guys,... You using AmonRa yeah?.... It might be worth mentioning all your finds to the man Amon Ra himself,... Post something in the AmonRa thread, maybe there is something he can sort for future updates.
Hello!
Suddenly I'm getting on one of my backups "MD5 mismatch..." error. Didn't do anything. Haven't change a name of the folder, nothing.
Is there is some way to restore data from that backup?
Help me, please?
Thank you!
Did u try an advanced restore of data
Sent from my SPH-D700 using Tapatalk
Yes. Actually, I've tried it first.
I am getting the same problem, and Yes I also did advanced restore but I got the same error there also.
I had the same problem once. I ended up having to restore an older backup.
Leave SPACES out of your filenames and folders
antila said:
Hello!
Suddenly I'm getting on one of my backups "MD5 mismatch..." error. Didn't do anything. Haven't change a name of the folder, nothing.
Is there is some way to restore data from that backup?
Help me, please?
Thank you!
Click to expand...
Click to collapse
I was reading on this as was having same issue...a guy posed that you can't have SPACES in your filenames or folder names.
I did this and worked a treat!!!
Good luck...just take out the spaces...
There was no spaces because I did not change anything. It was Nandroid backup and suddenly it was not working. Couldn't do anything, so, restored older backup.
Are u perhaps using ext4 with no_journaling? All it takes is one zero misplaced and your data goes poof. Suggest in future you place copies of backups on your hard drive.
Brought 2 u via Bonzai! 5.0.2
I assume you're talking about flashing back to DI18 using Odin. Rename the file from .md5 to .tar and it will work fine. I don't think the .tar has a valid MD5 hash that ODIN recognizes.
Or not, just reread post.
I built a couple of CWM Recovery Nandroid backups for all the folks looking for a stock restore image that is pre-rooted and devoid of bloatware.
Built on: 1838CTO 32GB US Thinkpad Tablet with Gobi 3000 WWAN. No internet connection made during boot. No account information entered. Superuser pre-activated.
You should update to the latest CWM Recovery port, i.e. VENTANA RECOVERY from http://everyrandom.com/files/files.php
BACK-UP YOUR OWN THINKPAD FIRST USING CWR
- and report your experiences afterwards!
UNZIP the folder to /clockworkmod/backup/ on EXTERNAL SD-CARD
Use CWR after a full power down, choose backup/restore, choose restore, choose the backup folder
There are TWO options currently:
NO BLOATWARE 0089 / OTA2.5 -- 350MB zip
No-Bloat 0089/OTA2.5 US Rooted Nandroid - NEW LINK
NO BLOATWARE 0075 / OTA1 -- 330MB zip
NO Bloat 0075 US Rooted Nandroid ZIPPED
pwstein said:
I built a couple of CWR Nandroid backups for all the folks looking for a stock restore image that is pre-rooted.
Useful for users wanting to roll back to an earlier firmware (0075) on US supported Thinkpads with CWR installed.
Built on: 1838CTO 32GB US Thinkpad Tablet with Gobi 3000 WWAN. No internet connection made during boot. No account information entered. Superuser pre-activated.
PLEASE -
UPDATE TO THE LATEST CWR port
BACK-UP YOUR OWN THINKPAD FIRST USING CWR
- and report your experiences afterwards!
IT IS ZIPPED - UNZIP and move to EXTERNAL SD-CARD
The SD_CARD should have:
/clockworkmod/backup/no_bloat_0075_US_root_NANDROID/**files**
Use CWR after a full power down, choose backup/restore, choose restore, choose the unzipped backup
YES BLOATWARE -- I allowed the Lenovo Add-on apps to install - 550MB, i.e. stock, factory fresh US build
YES Bloat 0075 US Rooted Nandroid ZIPPED
Click to expand...
Click to collapse
Thanks for doing this!
I kept having trouble with downloading the files.
After entering the security code & clicking on Dowload File, it will automatically refresh the page & bring me back to the beginning again.
I tried both on Firefox & IE.
Which CWR are you referring to?
I can't locate the new port in the original CWM thread...I'm using the one posted in the first post of that thread.
Konker
konker said:
Thanks for doing this!
I kept having trouble with downloading the files.
After entering the security code & clicking on Dowload File, it will automatically refresh the page & bring me back to the beginning again.
I tried both on Firefox & IE.
Which CWR are you referring to?
I can't locate the new port in the original CWM thread...I'm using the one posted in the first post of that thread.
Konker
Click to expand...
Click to collapse
I don't know why the site isn't working for downloading, seems like lots of folks have been successful. I ran in to the same issue trying to test the download. Any ideas from the forum?
CWR/CWM Recovery -- It is called ventana_recovery and can be found in US or ROW types in 16, 32 and 64 iterations at everyrandom.
http://everyrandom.com/files/files.php
New link for the No Bloatware Nandroid added to original post. When I can get the other Nandroid uploaded to the new server, I'll add that link.
Don't know why the other links wouldn't serve up... sorry all.
pwstein said:
I don't know why the site isn't working for downloading, seems like lots of folks have been successful. I ran in to the same issue trying to test the download. Any ideas from the forum?
CWR/CWM Recovery -- It is called ventana_recovery and can be found in US or ROW types in 16, 32 and 64 iterations at everyrandom.
http://everyrandom.com/files/files.php
Click to expand...
Click to collapse
Is this the one I should be using for my 32Gb TPT?
It's labelled ventana32_recovery.img.
I don't know what happened but yesterday, I couldn't even browse the Files folder to view other files.
Thanks for reposting the Nandroid backups!
Yes, you've located the right one if you've got a US tablet.
The gps.conf is modified from the original file that shipped on tablet. This causes updates to fail.
CWM will cause OTA2 to fail during update. My apologies about GPS.conf, I missed that. It is a simple thing to fix.
Also, there are OTA builds that don't require the original files and recovery here in XDA.
I downloaded the 0075_US file. I am looking to replace a couple of system/app files (mainly PinyinIME.apk) as I deleted them before without a backup.
I want to take my TPT back to stock or run some sort of update without too much trouble as I plan on selling my TPT (need the money).
Is there a way that I can extract the files that I need from the 0075_US files that was posted here?
Thanks
There is a system dump provided by GodfatherIP at another forum, here is a link http://dl.dropbox.com/u/6846397/System.zip
Maybe that'll help...
hey guys!
i was looking for such a non bloated rom - yet, im not sure on how to exactly install cwm ... call me stupid, but i can't really find a step by step guide and rom manager wasnt working for me. could someone link me (obviously too stupid for the search function) a thread or give a guideline?
thanks in advance, also for the rom!
hansonenator said:
I downloaded the 0075_US file. I am looking to replace a couple of system/app files (mainly PinyinIME.apk) as I deleted them before without a backup.
I want to take my TPT back to stock or run some sort of update without too much trouble as I plan on selling my TPT (need the money).
Is there a way that I can extract the files that I need from the 0075_US files that was posted here?
Thanks
Click to expand...
Click to collapse
Download the archive and open it with winrar. You will find system.ext4.tar. Open it inside winrar and it will extract it. In the app directory you will find all system apps.
Copy PinyinIME.apk and the odex to your device /system/app and do :
chmod 644 /system/app/PinyinIME.*
pau-pau123 said:
hey guys!
i was looking for such a non bloated rom - yet, im not sure on how to exactly install cwm ... call me stupid, but i can't really find a step by step guide and rom manager wasnt working for me. could someone link me (obviously too stupid for the search function) a thread or give a guideline?
thanks in advance, also for the rom!
Click to expand...
Click to collapse
noone can help me here?
my post to Temetka might help you
pwstein said:
my post to Temetka might help you
Click to expand...
Click to collapse
thanks, worked fine after some more research
http://dl.dropbox.com/u/10649086/0089_US_no-bloat_rooted.zip
is the link down just for me?
//jk, worked
MD5 checksum mismatch?
pwstein said:
I built a couple of CWM Recovery Nandroid backups for all the folks looking for a stock restore image that is pre-rooted and devoid of bloatware.
Built on: 1838CTO 32GB US Thinkpad Tablet with Gobi 3000 WWAN. No internet connection made during boot. No account information entered. Superuser pre-activated.
You should update to the latest CWM Recovery port, i.e. VENTANA RECOVERY from http://everyrandom.com/files/files.php
BACK-UP YOUR OWN THINKPAD FIRST USING CWR
- and report your experiences afterwards!
UNZIP the folder to /clockworkmod/backup/ on EXTERNAL SD-CARD
Use CWR after a full power down, choose backup/restore, choose restore, choose the backup folder
There are TWO options currently:
NO BLOATWARE 0089 / OTA2.5 -- 350MB zip
No-Bloat 0089/OTA2.5 US Rooted Nandroid - NEW LINK
NO BLOATWARE 0075 / OTA1 -- 330MB zip
NO Bloat 0075 US Rooted Nandroid ZIPPED
Click to expand...
Click to collapse
pwstein,
Finally got down to restoring your Nandroid backup to my TPT.
However, I kept getting the MD5 checksum mismatch error.
Am downloading again to try and see if it makes any difference.
Do I need to preserve the folder name 0089_US_no-bloat_rooted?
Konker
konker said:
pwstein,
Finally got down to restoring your Nandroid backup to my TPT.
However, I kept getting the MD5 checksum mismatch error.
Am downloading again to try and see if it makes any difference.
Do I need to preserve the folder name 0089_US_no-bloat_rooted?
Konker
Click to expand...
Click to collapse
Reloaded the 0089 package but ended up with the same MD5 mismatch error.
Tried this method to recreate the nandroid.md5 but my TPT does not have md5sum even though busybox is already installed.
Anyone has a clue what I can do to overcome this?
Konker
Off the top of my head, and I apologize if you have made this apparent elsewhere, are you using a US (or UK) firmware Tablet?
pwstein said:
Off the top of my head, and I apologize if you have made this apparent elsewhere, are you using a US (or UK) firmware Tablet?
Click to expand...
Click to collapse
I'm using a US TPT.
Do you think the CWR versions we're using matters?
I've since upgraded the CWR to the version you recommended & so I'm wondering if this is a factor.
Konker
I don't know about the different CWM Recovery. I wish I did.
After you have extracted the zip, the folder can be renamed but it should be placed within the backup folder, like:
EXTERNAL SD-CARD ROOT/clockworkmod/backup/0089_US_no-bloat_rooted/**files**
I'm running version 5 (beta) of the Tweaked Stock ICS ROM on my GT-P6800, but I'm having a problem with nandroid from CWM.
I've created some valid nandroid backups in the past, but I found (to my cost!) a few weeks ago that the more recent backups I'd made weren't valid.
Reading the CWM thread over at http://forum.xda-developers.com/showthread.php?t=1542897 it sounded like there was a known problem, but should have been fixed. I flashed version 6.0.1.1 this morning, but I'm still having the same problem.
Instead of getting three .img files and three .tar files, I'm getting the three .img files but then get three small (<1MB) .dup files instead of the .tar files (data.ext4.dup, cache.ext4.dup and system.ext4.dup).
Anyone else seen this? Any ideas why?
Sorry for posting this here instead of in the developers forum - I don't seem to have posted enough on XDA to allow me to post the question in the right place!
Thanks,
Adam.
Cwm now does incremental backups as only the changes from the original backup are done. This results in faster and smaller backup sizes after the original backup. If your original backup is corrupt delete the clockworkmod folder and redo your backup. After that incremental backups will be fast and small.
Sent from my GT-P6800 using xda premium
kishd said:
Cwm now does incremental backups as only the changes from the original backup are done. This results in faster and smaller backup sizes after the original backup. If your original backup is corrupt delete the clockworkmod folder and redo your backup. After that incremental backups will be fast and small.
Click to expand...
Click to collapse
Aaaaah! Right. Hmmmm. I kinda liked the standalone nature of the full backups.
Having been bitten by a broken backup before, I'm rather nervous of testing this out! So if I want to restore an incremental backup, do I select just the latest dated file, or do I need to restore the last full back-up (and it'll restore the original and all the changes), or do I need to restore each increment myself?
Are the backup folders completely portable, such that I can move them in and out of the 'clockworkmod' directory as requried, to force full backups each time?
Many thanks,
Adam.
Just select the last dated backup. I have restored a number of times using Iocerra's cwm 6
Sent from my GT-P6800 using xda premium
Fantastic. Thanks, kishd.
Sent from my GT-P6800 using XDA Premium HD app
Is there any way to make a standalone backup?
And how do we know what backup folder is the main backup? Aka how do we know what one is safe to delete?
I've made several backups on different roms/kernels, and I often delete old backups to free room on sdcard..
edit: I just did a backup after changing backup format to "tar" and it was over 1GB. The previous backups were between 1 and 3 hundred MB, so I assume setting the backup mode as tar does a standalone backup. can anyone confirm?
changing backup format to "tar"
mvmacd said:
edit: I just did a backup after changing backup format to "tar" and it was over 1GB. The previous backups were between 1 and 3 hundred MB, so I assume setting the backup mode as tar does a standalone backup. can anyone confirm?
Click to expand...
Click to collapse
How did you do this? I know I saw the option last night, selected it, and backed up, but then I flashed a couple upgrades and now I don't see this option anymore. I tried deleting the clockworkmod folder and backing up from fresh, but it made a dup backup. I've been burned by a string of broken dup's so I really want the tar format (plus, I can extract apps and data from a tar, but not from the blob/dup mixture). I even see a file in my new clockworkmod directory called ".default_backup_format" that contains only one word: tar. This file had to be created with the backup I just did, and yet it was still a dup style backup.
So, where did you see the option to change format to "tar"? I would really like to know.
Thanks.
kevlar11 said:
So, where did you see the option to change format to "tar"? I would really like to know.
Thanks.
Click to expand...
Click to collapse
advanced backup options in CWM recovery (or same) ))
I've noticed this since I installed garwynn's version of CWM. Just installed the official CWM touch recovery and experiencing the same thing.
When making a backup, the date and time are very wrong. For instance, today is June 11th and the recovery is saying that it's February 15th, 1970. 1970-02-15.08.16.07 should be 2013-06-11.09.57.xx.
Any idea on how to solve this problem?
I don't know for a fact, but unless garwynn speaks up, I would try to run another cwm backup to see if the date corrects itself. I would highly suspect the invalid date backup is bad. I don't have proof to back up my opinion BTW.
Philz recovery had the same issue on mine but a traul through the settings in recovery and I was abke to alter time.date ect
Now alls good
Sent from my GT-I9300 using xda premium
adie1234 said:
Philz recovery had the same issue on mine but a traul through the settings in recovery and I was abke to alter time.date ect
Now alls good
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Where did you alter the date/time at?
In philz its in the advanced settings menu
Sent from my GT-I9300 using xda premium
Rom manager
If you do a backup using ROM manager, the dates come out right no matter which recovery you are on.
It has been a problem on all official CWM based recoveries for quite a long time now. It got messed up in one of the updates upstream a long time ago and it's been lost in the code. (Something like that)
But basically it's not really a problem or effecting any actual utility. And btw don't try manually changing the back up names as it will mess up the MD5 and you won't be able to restore them.
Sent from my kTWEAKed, Turbo Charged, CrossBreeding, NOS injected, OCed, UVed, BEAST of an S4
I've changed the name of the folder within the backup folder so it would be easier to know what that backup was. You don't use spaces in the folder name. Md5 still works. I md5 a file, then change the name of the file and md5 it again. Same sum. Granted, you shouldn't be drastically messing around with backups, but I don't see any harm in renaming a folder to like stock.rooted or stockrooted instead of a date and time. The files in the folder haven't been altered. When you're poking around with recovery, it makes backups easier to choose if they are different ROM backups.
oscarthegrouch said:
I've changed the name of the folder within the backup folder so it would be easier to know what that backup was. You don't use spaces in the folder name. Md5 still works. I md5 a file, then change the name of the file and md5 it again. Same sum. Granted, you shouldn't be drastically messing around with backups, but I don't see any harm in renaming a folder to like stock.rooted or stockrooted instead of a date and time. The files in the folder haven't been altered. When you're poking around with recovery, it makes backups easier to choose if they are different ROM backups.
Click to expand...
Click to collapse
Do not change the names of the internal folders, that would mess the restore part.
Sent from my SPH-L720 using Tapatalk 4 Beta
inlineboy said:
It has been a problem on all official CWM based recoveries for quite a long time now. It got messed up in one of the updates upstream a long time ago and it's been lost in the code. (Something like that)
But basically it's not really a problem or effecting any actual utility. And btw don't try manually changing the back up names as it will mess up the MD5 and you won't be able to restore them.
Sent from my kTWEAKed, Turbo Charged, CrossBreeding, NOS injected, OCed, UVed, BEAST of an S4
Click to expand...
Click to collapse
So, if you have changed the name what does one do? I am currently experiencing this at the moment? Am I screwed at this point?