Related
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
I had a md5 mismatch and was freaking out. Turned out that the folder name for my backup couldn't have spaces in it...
This also works for anyone that wants a to make a 100% stock image but keep recovery.
just replace the boot.img and system.img with the ones from the RUU and recalc.
i just got this problem. do i need the "#" for each command?
Any idea what causes this? Is it just the folder name with spaces?
zeke1988 said:
i just got this problem. do i need the "#" for each command?
Click to expand...
Click to collapse
No the # simply means you are logged in as root or Su
If its showing $ then you may need to type /system/bin/Su
I believe or could be /system/lib/su I'm still pretty new to Linux / Android
Sent from my ADR6300 using Tapatalk
s197 said:
Any idea what causes this? Is it just the folder name with spaces?
Click to expand...
Click to collapse
Spaces aren't allowed but it could also be caused by corrupted data or sometimes even simply renaming the folder
Sent from my ADR6300 using Tapatalk
Be warned: If the nandroid was legit broken, then this will restore it *anyways* and your system won't boot / will have weird errors / whatever was wrong with the nandroid will be wrong with your system now.
Obviously you can just restore a previous nandroid if that happens.
i did this and still cant fix the md5. making me to use the older backup
For n00bs could you elaborate on this post, i'm having the same problem.
"To fix this problem use the code below"
I know this is through cmd, but what needs to be where when i'm typing exactly that in (changing the folder name etc) what screen do I need to be on. If it was more detailed, and thank you so far because this is the only post on the net, it could be very useful!
jinkzuk said:
For n00bs could you elaborate on this post, i'm having the same problem.
"To fix this problem use the code below"
I know this is through cmd, but what needs to be where when i'm typing exactly that in (changing the folder name etc) what screen do I need to be on. If it was more detailed, and thank you so far because this is the only post on the net, it could be very useful!
Click to expand...
Click to collapse
If you're messing with nandroid backups by now, we'd hope you would know how to get adb shell started.
So basically you start up adb shell in a command prompt on your computer, this connects to your phone, then you follow those commands following "adb shell"
A brief overview of getting to the adb commands >> http://forum.xda-developers.com/showthread.php?t=709220
permission denied error
I'm using windows 7 CMD to connect to my hero for resolving this md5 mismatch issue.
But when i type in the last command, which is -
md5sum *img > nandroid.md5
it gives me an error -
md5sum: permission denied
I tried running the cmd as administrator also but I dont know in windows how to do a 'SU' like in ubuntu.
can you please give a tip what to do ?
Sean.
Ok wow you guys rock thanks this works great.
THANK YOU!!!!!!!!!!!!!
I had this happen to me today... I woulda had to spend a crapload of time getting things all set up on my phone if I hadn't found this thread. It was my fault, I changed the name of the Nandroid backup folder... I had no idea you couldn't do this.... went to restore and BOOM MD5 mismatch.... noooooooooooo.
Thank you again OP for posting this you really saved my day today.
Jacked up Dell Streak/ US ver. build 6601 MD5 Checksum error
After screwing up my brand new Streak, I turned to XDA and MoDaCo to fix my screw-ups. Read this and did that, and nothing would work. The buttons would flash the Dell logo would come up and freeze. So here is another solution that worked for me Step by step.
Installed the fast boot using Windows 7 64 bit I downloaded Fastboot and followed there instructions. Not sure what it did for me, but I did it.
Now as the phone was, I was unable to do any kind manipulation of the SD card. I tool the micro SD card and put it into an SD adapter and added the files via my lap top. See instructions here
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
thanks fone_fanatic 28th August 2010, 03:14 AM
DO NOT PUT ANY SPACES IN YOUR FILE STRUCTURE. I did and it gave me an "MD5 Check Sum Error" took the space out and bam it worked.
Rebooted the phone and so far every thing works. GPS, WiFi etc and no dam flashing lights or self reboots or O2 stuff Hope this helps ya....Good luck you will need it.
Ihtfp69 to the rescue again!
Man, I can never repay you for how much you've helped me out and saved my bacon! Other dev's, take note, this is an exemplary developer here and his SkyRaider rom is beyond compare!
seansin said:
I'm using windows 7 CMD to connect to my hero for resolving this md5 mismatch issue.
But when i type in the last command, which is -
md5sum *img > nandroid.md5
it gives me an error -
md5sum: permission denied
I tried running the cmd as administrator also but I dont know in windows how to do a 'SU' like in ubuntu.
can you please give a tip what to do ?
Sean.
Click to expand...
Click to collapse
I do not have ABD on my Win 7 machine so I had to use CMD as well. I too received an error, however mine basically said that md5sum was not a recognized command. Not sure where you got md5sum for your win 7 machine, but I got mine at the following website... (fourmilab.ch/md5/) and this one worked just fine. Unzip and copy md5.exe to the system32 folder.
If you are still working through this... good luck. Hopefully it can be helpful to someone else either way. --Josh
OMG ihtfp69!! You're a life-saver!
cscimmia said:
I do not have ABD on my Win 7 machine so I had to use CMD as well. I too received an error, however mine basically said that md5sum was not a recognized command. Not sure where you got md5sum for your win 7 machine, but I got mine at the following website... (fourmilab.ch/md5/) and this one worked just fine. Unzip and copy md5.exe to the system32 folder.
If you are still working through this... good luck. Hopefully it can be helpful to someone else either way. --Josh
Click to expand...
Click to collapse
Hmmm...I just used md5sum from the phone's shell. No need to get anything for Windows.
hey i tried the steps you guys gave buy i get
# cd /sdcard/clockworkmod/backup/2010-10-30.08.23.53
cd: can't cd to /sdcard/clockworkmod/backup/2010-10-30.08.23.53
this is what i did.
I opened terminal in OSX and typed "adb shell" after that i typed "cd /sdcard/clockworkmod/backup/2010-10-30.08.23.53" but it didnt work.
anyone know what i did wrong??
i also did "adb devices" in terminal and it detects my device. i check the su on my sgs and i see my computer, it sees it as unknown.
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Another way: for Example TWRP Cache.ext4.win
most recoverys now have a option to turn off MD5 checking
You can copy your backup folder to your computer, use attached app to check the md5 number , edit md5 file and check and verify and change
this thread is old so md5 file may not be named the same. the picture is TWRP custom recovery
example was with cache.ext4.win that has md5 file named cache.ext4.win.md5
another short cut to try
----------------------------------------------------------------------------
@aeneas1 Thanks!!
i did another google search and found a very simple fix, at least it worked for me, on the first try, and i have tested it successfully with some of my other backups that were also getting the mismatch error.
1. using your phone, navigate to your backup folder using a root browser, i use romm tool box root browser.
2. locate and delete the nandroid.md5 file
3. create a new file and name it nandroid.md5
4. boot into recovery, select restore your backup, and watch the magic begin!
---------------------------------------------------------------------------
Update: thanks @Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
DO NOT renamed your backup with spaces Thanks ltredbeard and those who verified
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse
Wished I'd have seen this before deleting 4 different backups. Can you tell me what exactly this zip does ?
crz6662 said:
Wished I'd have seen this before deleting 4 different backups. Can you tell me what exactly this zip does ?
Click to expand...
Click to collapse
Never mind, opened it up & read the PDF file. Wanted to also thank you for this.
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Using these methods fixed my error! Thanks.
BTW: I name my backup and it contained a space. I ended up having to rename the backup w/o the space. Ex. From - Backup Froyo To - BackupFroyo
Exca said:
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
After follow this easy procedure on my ASUS TransformerTF101, here's the result in my clockworkmod recovery (v3.0.2.8):
1. Checking MD5 sums is OK
2. Restoring system is OK
3. Restoring data is not OK, there is message: ".android_secure.img not found. Skipping restore /sdcard/.android secure.
4. Restoring cache is OK
5. Backup complete
Then after reboot, all my data on that backup file is not restore as expected. I am afraid my data is gone :-(
Can someone help me?
Araf said:
After follow this easy procedure on my ASUS TransformerTF101, here's the result in my clockworkmod recovery (v3.0.2.8):
1. Checking MD5 sums is OK
2. Restoring system is OK
3. Restoring data is not OK, there is message: ".android_secure.img not found. Skipping restore /sdcard/.android secure.
4. Restoring cache is OK
5. Backup complete
Then after reboot, all my data on that backup file is not restore as expected. I am afraid my data is gone :-(
Can someone help me?
Click to expand...
Click to collapse
I'm guessing by following the zip instructions, you deleted the ".android_secure.img" since it says it's safe to delete if there's a nandroid.md5 file already. But that .md5 file does not match the original. So the backup was likely messed up when trying to fix it with the .zip instructions.
I believe the easier method in post #4 should be tried first on a fresh backup dir.
Whyzor said:
I'm guessing by following the zip instructions, you deleted the ".android_secure.img" since it says it's safe to delete if there's a nandroid.md5 file already. But that .md5 file does not match the original. So the backup was likely messed up when trying to fix it with the .zip instructions.
I believe the easier method in post #4 should be tried first on a fresh backup dir.
Click to expand...
Click to collapse
For future reference to all. What I do all the time is when I make a backup, I hook the tablet up to my pc and back the backup to my PC. This saved me from having to do those steps. I just rewrote the backup on my sdcard and it worked.
Thanks that worked for my mytouch 4G.
Works like a charm, Thanks Again!
carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse
CWM 3.0 stable
carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse
he... good work, thanks very much.
it helps me
Thanks for this, really did the trick! I was so scared I lose my DarkSide Sense backup! thanked!
Can anyone tell me quickly why i can't execute "md5sum"?
when i execute the md5sum command, I get:
"/system/bin/sh: md5sum: not found"
fkng awesome <3! this helped me out!!!
Eschmacher said:
Can anyone tell me quickly why i can't execute "md5sum"?
when i execute the md5sum command, I get:
"/system/bin/sh: md5sum: not found"
Click to expand...
Click to collapse
same problem. any1 got a solution? trying to restore MIUI rom backup.. no luck. restores stock rom backup with no probs.
I am on SGSII.
The MD5 checksum fix *worked* for me! TY!
HTC Evo 4G 2.3.3 / 2.16.0000 / CWM 5.0.2.2
carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
THANKS SO MUCH!!! I thought that I was going to lose a bunch of stuff after I formated my SD card (thankfully I had a backup on my computer) while watching Netflix. This really saved my life and I'll be bookmarking this!
Yes I met it before.
But now there is not an issue anymore.
thank you
i used your code now hopefully i will have my 4g back with the back up im restoring right now
UPadte:
I restored a backup from when my 4g was working and nothing changed I still can't get 4g to connect!
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
thank you so very much!!
I installed a custom font on my Tab. I decided to try and replace the Roboto_Bold.ttf, and that's why my Tab started to boot loop. (Long story short: I did the same thing to my Nexus, but I was able to salvage what I could and am now in the process of flashing a new ROM). I wiped the Cache/Dalvik on my Tab and flashed the ROM I had on it, over itself without wiping--thinking it would give me enough control to be able to flash a new ROM. I was wrong. I install the latest CWM (v5.5.0.4) and I go into Recovery mode. CWM won't let me Wipe Data. It just sits there, then ultimately kicks me back to the CWM "Home" screen; the same thing happens when I use an older version of CWM (v4.0.0.4). I've tried restoring backups and nothing works. I even had difficulty mounting the Tab on my laptop long enough to transfer over the newer ROM.
I have no clue what to do, and I feel so powerless. I usually can fix this kind of stuff by myself, but I can't this time.
Any and all help is appreciated.
Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk
kishorsidu said:
Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
I can reach Download mode--but I have no clue how to flash anything from ODIN. -_-
Shameless bump.
Autocorrected from my GNexus
Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of commands, I did a rmdir instead of rm -r).
MapleSyrup said:
Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of comands, I did a rmdir instead of rm -r).
Click to expand...
Click to collapse
I don't mind losing the data; however, would you mind sharing the commands with me?
natezire71 said:
I don't mind losing the data; however, would you mind sharing the commands with me?
Click to expand...
Click to collapse
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/
MapleSyrup said:
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/
Click to expand...
Click to collapse
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Autocorrected from my GNexus
natezire71 said:
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Click to expand...
Click to collapse
That was the problem, I couldn't do it in cwm.
Just wanted to put it out there that I erased the data using Super Manager. Not a clean enough delete for preparing it for sale but good enough for my intentions.
So my microUSB port is broken, and I want to restore the nandroid backup of the stock rom so I can bring it back to t-mobile, but I get the error message md5 mismatch every time. Is there any way I could fix this without using adb (since I cant connect my phone to the computer)? Or any other way I could go back to a stock rom without RSD lite? thank you in advance
You'll need download terminal emulator from market. Type in terminal emulator this commant to recheck md5 sums:
su
mount -o remount rw /sdcard
cd /sdcard/clockworkmod/backup/(YOUR BACKUP FOLDER NAME)
rm nandroid.md5
md5sum *img > nandroid.md5
But doesn't md5 mismatch mean a corrupted backup? So by regenerating the md5, won't it semi brick the phone?
Sent from my MB526 using xda premium
thekguy said:
But doesn't md5 mismatch mean a corrupted backup? So by regenerating the md5, won't it semi brick the phone?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
In some times nandroid.md5 can be corrupted, for etc by errors in sdcard or something similar. You can't semibrick your phone , because i dont think that backup can be corrupted by nothing. What defy did you have? If you have defy mb525 (not +), i can send you my nandroid backup.
In Terminal Emulator to remove root (you know why you need to remove it) :
su
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/xbin/busybox
exit
and reboot phone after rebooting open any root apk to veritfy that it says: cant obtain root access. are you rooted?
turffe said:
In some times nandroid.md5 can be corrupted, for etc by errors in sdcard or something similar. You can't semibrick your phone , because i dont think that backup can be corrupted by nothing. What defy did you have? If you have defy mb525 (not +), i can send you my nandroid backup.
In Terminal Emulator to remove root (you know why you need to remove it) :
su
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/xbin/busybox
exit
and reboot phone after rebooting open any root apk to veritfy that it says: cant obtain root access. are you rooted?
Click to expand...
Click to collapse
Thanks a lot! I'll try it tomorrow! I have a defy+ but hopefully my backup is not damaged just the md5 file
Hi
Everytime I reboot my phone I get a message when it boots up: "Factory mode is on. Wifi and other functions will be disabled."
I tried flashing a stock rom and installing different custom roms without resolving the problem. I am on kitkat 4.4.4. Please help?
Hamodi_ said:
Hi
Everytime I reboot my phone I get a message when it boots up: "Factory mode is on. Wifi and other functions will be disabled."
I tried flashing a stock rom and installing different custom roms without resolving the problem. I am on kitkat 4.4.4. Please help
Click to expand...
Click to collapse
This issue occurs either when the ROM is not completely installed on your device or when the device triggered the factory mode to prevent some app from accessing the /system and /data partitions. In order to correct this issue, you will have to root your device and download Terminal Emulator or Terminal Application from the Google Play Store then type in the following commands. Let me know if this fixes your issue.
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Thank you for your reply. My /efs/ directory is empty. I cant find any files there. I use ES file explorer and I have enable viewing hidden files and root is ON.
Hamodi_ said:
Thank you for your reply. My /efs/ directory is empty. I cant find any files there. I use ES file explorer and I have enable viewing hidden files and root is ON.
Click to expand...
Click to collapse
That is a very odd situation. EFS directory should not be empty because layer 1 and layer 2 android devices kernels/basebands/OS are stored in that partition. I can't think of anything else at the moment other than flashing the stock ROM with ODIN again to see the results, but it looks to me that you've already flashed ROMs a few times according to the OP. Anyone else want to pitch in?
Did you do a full backup using recoveries? You've probably flashed wrong kernel or wiped partitions, restore efs backup or install stock ROM and kernel.
Also see this and this post, its a bit old but may be useful.
homer285 said:
Did you do a full backup using recoveries? You've probably flashed wrong kernel or wiped partitions, restore efs backup or install stock ROM and kernel.
Also see this and this post, its a bit old but may be useful.
Click to expand...
Click to collapse
I Factory restored mine (unrooted and everything stock firmware and the issue will still come back. There's talk that people with this issue have to find a PIT and associated files just like on Note 3 but I can't find them for Note 4.....Same issue here, /EFS is empty even with unhide checked etc.
Fas
FIXED!! READ..VERY easy if you have a nandroid of existing rom or even a slightly older one in the TWRP/backups folder.
I fixed mine. I had an old backup from the current rom I'm running so just booted into TWRP and did a restore and selected the older backup and checked EFS ONLY and then rebooted and now it remembers wifi and no Factory Mode popping up so if you guys/gals have an older or current nandrpoid just restore the efs only from TWRP and you'll be good to go.! WOOT!!
Fas