I recently tried a new ROM and made a Rom Manager recovery restore file prior to changing. Things didn't work out as well as I had hoped and when attempting to restore, it fails at the checking MD5 sum process.
Any way to work around this? I really would like to restore to the previous ROM without starting over.
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
sandiegopaneraiguy said:
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
Click to expand...
Click to collapse
depending on the type of file format used to backup, the restoring could be done manually but a changed md5sum generally means the files are not the same as the original. this could result in corruption and generally it isnt recommended to restore corrupted files as you run the risk of nothing working.
if you're still wanting to proceeding with attempting to restore files which are different than the original and could be corrupted, off the top of my head, you can probably dd the .img files back and untar the .tar files back.
i would suggest starting over and perhaps copying the backup files over to your desktop instead of only leaving on the sdard. this should help ensure at least one of the copies maintains their integrity.
hope that helps!
You can boot into recovery, and run nandroid via adb shell command line, no md5 checksum file needed. Now if the image is bad, you of course get bad results, but if the checksum is just hosed for some reason, it will work fine.
Put the .win files for the partitions you want to restore in /sdacrd
then issue the command "tar xvpf /sdcard/data.win" or "tar xvpf /sdcard/system.win" from the adb shell while in /data or /system respectively. .win files are what TWRP creates for backups.
I had this happen with TWRP 1.01 or 1.02 once on a good backup that passed the checksum tests when I backed it up.
I was testing the reliability of the TWRP package's nandroid and first one failed.
Once I moved to the newer version, I've not had that issue.
Related
I've got 3 CWM backups on the internal memory of my Samsung SG2.
I tried to restore one and it failed on md5 mismatch/error (or something to that effect...) - tried the others - all returned the same error, yet when I'd actually backed them up, they all completed successfully.
The one thing I did to them all, was give them a more recognisable name, rather than just the date & time so I knew which ROM they were...so out of interest, I backed up my existing (new) Cognito ROM while still in CWM, then when it had finished the back up, immediately tried to restore the newly backed up ROM....and it worked! Is it failing on the others because I've renamed the CWM backup folder?? I'm sure I've done this in the past on my old HTC Desire, and had no problems
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Willie_Heckerslyke said:
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Click to expand...
Click to collapse
Google and you will find:
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53 (Which is your clockwork mod backup folder)
# rm nandroid.md5
# md5sum *img > nandroid.md5
Do this from a terminal emulator or from adb...
Thanks karendar...but I'm afraid I'm a bit crap at adb and that kinda stuff
I've downloaded an emulator off the market and when I fire it up, I got a $ prompt; found out how to get # prompt but when I put all that in, it gives the following error:-
"md5sum: can't open '*Img': No such file or directory"
When I looked inside the backup folder, there are a series of img files so is the wildcard * is to be put for each file in the back up folder? (I tried one of them - the boot.img file in there, this time there was no error brought up....but I also never got any 'success' confirmation or anything
Help
(BTW....whenever I type the letter 'i' - it changes into a capital 'I' all the time... What's that all about??)
**Bump** anyone??
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Thanks dude, i had the same problem on my P500, and your tip helped a lot!
Especially since my phone was stuck in a bootloop and my recoverys wouldnt work... You learn something every day!
Gasai Yuno said:
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Click to expand...
Click to collapse
..
just rooted my evo3d, everything went great and i even git CWM to install the first time correctly. heres where i think i went wrong-
i downloaded rom manager and i attempted to use it and it worked great. to me it seemed like it worked because i was able to choose my phone and even flashed the CWM over the original one i had. i made a backup of my stock rom and tried a rom from the dev forum, didnt like it and tried to switch back and got the MD5 mismatch error when i tried to restore my stock rom. now, i thought i would try to flash the original CWM which was blue over the CWM(orange) and then attempted to get the rom to restore. that was also a fail. what can i do? i read that installing busy box could effect this? any help would be appreciated.
sucks but it happens download the RUU from here and reroot if you need too
FIXING MD5 MISMATCH
adb shell
# cd /sdcard/clockworkmod/backup/name_of_backup
# rm nandroid.md5
# md5sum *img > nandroid.md5
gaaah i dont have ADB installed on my mac. is there not a simpler way? anyway to fix this?! i dont think i need to reroot honestly..
Nope sorry.
I may have found a way to fix the MD5 issue.
Well, it worked for mine.
I saved a backup of the stock ROM before I installed the needle kernel.
it was named 2011-08-01-23.53.47
The I saved another backup of the ROM with the needle kernel/
it was named 2011-08-02-19.06.28 w/ needlekernel
What happened was that on the sd card the backup folder was named 2011-08-02-19.06.28 w/ then inside that folder was another folder named needlekernel . And that folder contained the backup files.
It seems that putting the space in the name caused it to create another folder within the backup folder instead of just having the backup files in there. I kept getting the MD5 mismatch when I tried to restore that backup.
So I took the files out of the needlekernel folder and put them in the 2011-08-02-19.06.28 w/ folder. I then deleted the needlekernel folder. The last thing was to take the (space)w/ off of the end of the folder name so it was just as the program named it to begin with.. 2011-08-02-19.06.28
After doing that I was able to restore the backup through ROM Manager. So apparently it's best not to add anything to the backup name when saving it.
One other thing I'll mention. When I restored the backup with the needle kernel in it it put the stock kernel back in the ROM.
Hope this helps anyone with the MD5 issue.
Hey guys, just 2 quick questions about nandroid.
Is it possible to either bypass the MD5 checksum right at the start of every nandroid restore? OR, is it possible to generate your own one somehow?
The reason I ask is, I wanna try and replace the backed up files made by nandroid such as "boot.img", "system.img", "cache.img", "recovery.img" etc with the ones that I have extracted from a stock rom.
The stock rom I have can only be flashed through USB connected to PC, by using "SP Flash Tool". However, I have 2 problems using it. The first is that it doesn't work properly for me. I can only flash the "system.img" file but not the other .img files. It seems I need a USB-to-UART cable to flash ALL the .img files, which I don't have and I don't plan on wasting my money buying it either. Besides, I find flashing on a PC a lot more risky than from memory card.
The 2nd problem I have is that I often have problems getting my phone detected by "SP Flash Tool". I tried using Windows 7 and XP and it's hard to get a connection properly. It's most likely because the phone i'm using a chinese clone, called "STAR A1000". It's cheap and crap, so I'm not surprised that I can't establish a stable connection to my PC. I only got lucky like once or twice but haven't been able to flash from my PC ever since.
So anyway, the stock rom I have contains all the .img files. I wanna try and replace those files with the files generated by nandroid, but of course there's the problem with the MD5 checksum file that will check if the file matches or not. So I need a way to bypass the MD5 checksum completely or force nandroid to perform a restore regardless of the conditions. Either that, or I need a way to generate a MD5 checksum for the .img files from the stock rom, and use that for my nandroid backup.
My last question is, I also have custom roms that are made to be flashed on the memory card. Of course, they contain the "boot.img" file, and so I wanna try and replace that with my own working "boot.img" file. I want to know if this will work when I try to flash it in the recovery, or will it fail and brick my phone?
Hi folks,
The adventures continue. I've been trying to restore my Safestrap backup for ages, and no matter what I try, I continue to get
Code:
Error restoring /data!
at the conclusion of the restoration. I can restore via Fastboot to stock, but no matter what I can't get my full backup restored successfully. Generally unless I restore to stock factory the system ends up in a kind of broken state where there are apps that are installed but have file size 0B, and don't run.
The final error in the recovery log is
Code:
tar: seek failure: Value too large for defined data type
Error while restoring /data!
Of course the first thing I thought was that the backup was corrupt, but it extracts completely fine with plain ole' tar on my Linux laptop.
I have:
Updated Safestrap to 2.11 for Droid Razr
Updated BusyBox via Stericson's BusyBox updater app from Google Play
Attempted restore again after those two steps
Wiped /data and restored to Factory via both Fastboot flash through Matt's Utility and Motorola Recovery menu
Attempted to split the data.ext3.tar file into two, one with my apps directory, one without (since that way, both files are below 2 GB). The first file, the one with the apps directory removed, restored fine. The second one, consisting of just the apps directory, did not (with the same error). It might be a moot point anyway since I think Safestrap formats the partitions before restoring, so it wouldn't "recombine" them anyway.
Bought the XDADevelopers Android Hackers' Toolkit from the bookstore. Haven't finished reading it yet, but hopefully it will give me some ideas.
So I can get access to what my apps directory should look like (I can extract it locally here on my laptop) but I can't get Safestrap to extract it all at once to the correct partition on my phone.
I'm currently almost out of ideas. It seems this is a common problem and that newer versions of CWM Recovery split the tars so to avoid the file size limit imposed by BusyBox, if I'm interpreting what I've read correctly. This might be the case with the newer Safestrap but it doesn't help my old backup, unless I can split it in a way that Safestrap expects and will deal with (is this possible?)
Given that I have the actual files that should be on the phone, and that my phone is rooted, would it make sense to simply attempt to extract the apps-only tar overtop of the apps directory? Would the files be locked when the phone was on normally?
Could this still be a free space issue? Currently I'm showing 1.7 GB free after the latest failed restore. One would think if it was a disk space issue, it would show 0 B free, right? To test this, would it hurt to delete the files in the safestrap directory (i.e. orig and safe, containing a data.ext3.tar in each of about 2.2 GB) since Safestrap is currently in unsafe mode right now anyway?
Also, is there anything I can do to help here? I know C and C++; while I'm not a low-level hardware hacker by any means (I'm a professional web developer) this issue has bugged me enough that I want to try to fix it. I know that Safestrap is on Github but I'm not really sure where to start.
Do you have any other suggestions for ways to get my Safestrap-generated nandroid backup of my data correctly restored to my phone?
Please let me know if I did something wrong in asking this question; I tried to do as much research as I could beforehand. If I haven't done enough, I would appreciate a point in the right direction.
Or maybe the post was too long and drawn out, so I'll try to compact it here.
My phone won't restore a successful Safestrap backup that is 2.2 GB in size. The backup (a tar file) extracts fine on my PC. I'm getting "error restoring /data!". It seems to be the same issue others have had with restoring a CWM backup over 2 GB.
Would it make sense to simply attempt to extract the apps-only tar overtop of the apps directory, or would the files be locked when the phone was on normally?
Could this still be a free space issue?
Do you have any other suggestions for ways to get my Safestrap-generated nandroid backup of my data correctly restored to my phone?
Edit: Could the tar be converted to an image file to be flashed to the data partition with Fastboot?
Final bump. Anyone? Anyone? Bueler?
Is it safe to just grab a root shell through ADB, push the tar containing the apps, and extract over top of my phone's existing apps directory, while the phone is running? Are there risks associated with this?
Edit: Alternatively, is there a native Android GNU tar binary available anywhere, or instructions for cross-compiling one, since this seems to be a problem with BusyBox?
...Answering my own question, apparently yes. I'm going to try replacing the tar symlink to BusyBox with this native version and try again tonight, I'll let you know how it goes.
I had the same problem and the tar from your link worked for me for a 4GB tar extract. Thanks for your tip!
Can I restore data that I have backed up in CWM form my device to another?
As long as the model is same, yes. What device exactly?
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
azzazelium said:
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
Click to expand...
Click to collapse
If you insist on restoring the backup file do this simple trick on md5 mismatch: open the md5 file in your CWM backup folder, erase its contents. Leave the file empty (0 byte) then restore in peace
Keep in mind md5 mismatch means something changed in the backup file, doesn't matter which device it previously on. Do this on your own risk.
Note: CWM will skip verifying the backup if md5 file is empty.