When trying to restore my backup via CWM, it said MD5 mismatch!
Why?!
have u changed the name of the backup? i got an error once when i changed the name to something with spaces in it
Sent from a desire z
Like suggested above a name change or some other alteration to the file took place, possibly corruption.
renamed it to a name with no spaces...
still get the md5 mismatch error...
Make sure to have no spaces in the back up name
Go into the backup folder and remove nandroid.md5
Now, in that same directory, run this command:
Code:
# md5sum *img > nandroid.md5
Boot into recovery and try again.
Did you reflash CWM recovery after your backup?
Sent from a message in a bottle.
today i tried restoring a stock rom through cwm which was installed through odin.. while restoring it i got an error saying there is no MD5 files! So can i put the md5 files from other backups in this??
nope...you can't do that. what CWM was you used before? you should note that skin1980's or madteam's is work just fine. the one from merruk's kernel doesn't work. it still under development stage. please be wary of that
Just create an md5sums.txt using notepad++. And generate the md5sums yourself:
1. Download the md5sums-1.2.zip here. Extract md5sums.exe.
2. To generate md5 checksums for your .tar files, run md5sums.exe -u your_nandroid_backup.tar >> md5sums.txt
3. Edit the md5sums.txt in notepad++. Replace each asterisk (*) beside each filename with a space.
4. Save your file. Ensure it is encoded in utf8.
Your md5sums.txt should contain the following:
Code:
7e613b2d2d799aecad4d76931a80928b cache.rfs.tar
ff68ff227b91bb4ab5006df682d31d5f data.rfs.tar
02da391f4dfb511ffb69b7188174b3ee system.rfs.tar
7c294a7d02fcfb81ef79b258d02da705
.android_secure.vfat.tar
Source:
Bumslayer.
raolemo said:
Just create an md5sums.txt using notepad++. And generate the md5sums yourself:
1. Download the md5sums-1.2.zip here. Extract md5sums.exe.
2. To generate md5 checksums for your .tar files, run md5sums.exe -u your_nandroid_backup.tar >> md5sums.txt
3. Edit the md5sums.txt in notepad++. Replace each asterisk (*) beside each filename with a space.
4. Save your file. Ensure it is encoded in utf8.
Your md5sums.txt should contain the following:
Code:
7e613b2d2d799aecad4d76931a80928b cache.rfs.tar
ff68ff227b91bb4ab5006df682d31d5f data.rfs.tar
02da391f4dfb511ffb69b7188174b3ee system.rfs.tar
7c294a7d02fcfb81ef79b258d02da705
.android_secure.vfat.tar
Source:
Bumslayer.
Click to expand...
Click to collapse
cn u explain step 2?
Today i had the same problem on TermaRom with CWM restore failed MD5 missing.Greeeeetz
Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom ( only works on Jelly Bean ) . On KitKat we have Knox 2.0 which is more harder to conquer
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one for I9192
I9192XXUBMK4_I9192SERBMJ3_SER.zip
U can use this guide on other versions of this phone I9190/I9195
Firmwares that contain MK4/MK5/ML1/ML2/ML4/NA1/NA2 and so on from here have Knox bootloader inside
Only the name will be different but what is inside is the same
Only latest versions of firmware contain Knox Bootloader ( usually the ones released in late november/december 2013 )
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip *.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf *.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn - bootloader ( knox included )
rm -rf sbl1.mbn - part of bootloader
rm -rf sbl2.mbn - part of bootloader
rm -rf sbl3.mbn - part of bootloader
rm -rf *.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Video of "How to" credit to @Mitko
SilviuMik said:
Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one
I9192XXUBMK4_I9192SERBMJ3_SER.zip
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip I9192XXUBMK4_I9192SERBMJ3_SER.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Click to expand...
Click to collapse
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?
hobbya said:
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?
Click to expand...
Click to collapse
I think u can yes But i also think some improvements were made in Modem/Kernel
That rpm.mbn file gets flashed in a special partition and does not get overwritten only if u flash a new one from a firmware that contain it. As i mentioned in other forum only last ones does contain it Russia, Brazil, Trinidad MK4
allows downgrade?
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,
Trepanator56 said:
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,
Click to expand...
Click to collapse
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck
SilviuMik said:
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck
Click to expand...
Click to collapse
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?
Dijinn said:
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?
Click to expand...
Click to collapse
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
SilviuMik said:
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
Click to expand...
Click to collapse
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...
Dijinn said:
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...
Click to expand...
Click to collapse
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back
SilviuMik said:
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back
Click to expand...
Click to collapse
I solved the problem!
If someone else has trouble fixing the Wi-Fi after the flash via Heimdall, here goes!
Flashing TZ partition only won't do anything...you upload the file, but it doesn't seem to get flashed...
The solution is to flash both MODEM and TZ partitions... It seems that when you reflash the modem, the cellphone tends to check for TZ again and TADA! Now it will be there!
Do you think that I could do the same for i9195 ?
Darktitor said:
Do you think that I could do the same for i9195 ?
Click to expand...
Click to collapse
Yes of course Is the same for all 3 models 9190 9192 9195
Great
My friend will be happy
Envoyé de mon GT-I9195 en utilisant Tapatalk
Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?
franzyroy said:
Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?
Click to expand...
Click to collapse
I have no ideea about S4 Maybe knox is in other places too like modem or no ideea. I can`t guarantee. On S4 mini is in aboot.mbn sbl1 sbl2 sbl3 ( bootloader )
Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.
franzyroy said:
Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.
Click to expand...
Click to collapse
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more
SilviuMik said:
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more
Click to expand...
Click to collapse
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
SilviuMik said:
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Click to expand...
Click to collapse
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.
franzyroy said:
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.
Click to expand...
Click to collapse
Yes of course , better to try then flash all the files and see after
Btw, S4 Mini Knox firmware contains:
sbl1.mbn - part of new bootloader , safe to delete
sbl2.mbn - part of new bootloader , safe to delete
sbl3.mbn - part of new bootloader , safe to delete
aboot.mbn - New Knox bootloader , DELETE
rpm.mbn - Resource power Management link
tz.mbn - Trusted zone ( Wifi won`t work if u don`t flash it together with new Modem )
boot.img - Kernel
recovery.img - Recovery/Download mode
system.img.ext4 - your apps/framework/android
NON-HLOS.bin - modem
cache.img.ext4 - CSC / APN settins / What bloat is to be installed depending on zone / carrier
hidden.img.ext4 - Another "system" part of apps that are too big for /system ( for now almost empty ) on S2 was full of apps
Try and see
Thanks ... I know for the S4(I9505), when we have old bootloader, we must put this (GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUBMH1.zip ) modem for that all works.
Perhaps, I can replace modem.bin and NON-HLOS.bin by those in the zip.
I need the official tmob noteII jb 4.3.1 kernel in tar or zip can anyone give me a link please
or latest official kernel
(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado
Got Kernel working
Darkshado said:
(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado
Click to expand...
Click to collapse
Thanks bud used the Kernel and subbed it in zip that did the trick God Bless
Hi all,
Is anybody got stuck their nandroid recovery due to md5 mismatch ???
I have some solutions .Before that let's check why the mismatch came .
You are getting the MD5 mis-match error because the MD5 checksums in the nandroid.md5file do not match the checksums of one or more of the system.img,data.img, orboot.img etc. files in your Nandroid's backup directory.
Solutions :thumbup:
1 . Open Terminal emulator and put the following code
adb shell
_______________________________________________
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53//change this by your backup folder name .
# rm nandroid.md5
# md5sum *img > nandroid.md5
_________________________________________________
2 . Open nandroid.md5 using text editor .Just edit the values in nandroid backup by original value of each .tar or .zip files
Remember Changing values of nandroid.md5 will affect your backup .
It is something like
_________________________________________________
xxxxxxxxxxxxxxxxxx
recovery.img
xxxxxxxxxxxxxxxxxxx
boot.img
xxxxxxxxxxxxxxxxxxx
system.ext4.tar
xxxxxxxxxxxxxxxxxxx
_________________________________________________
Edit xxxxxx with the currect md5 value of each .
3 . Still the problem is there or there is no nandroid.md5 just clear the values of nandroid.md5 using text editor or create a empty nandroid.md5 .
Your problem is now solved . :sly:
Sent from my GT-S7562 using XDA Premium 4 mobile app
Still not working...
I tried the first an the third one and nothing worked... I can't try the second because i deleted my original md5 file and don't have those numbers.
The first solved that problem but created a "error while restoring /data" message every time so i replaced it with a blank file and now it says md5 mismatch
I have no idea, and need this backup
Thanks!
dmanmatt10 said:
I tried the first an the third one and nothing worked... I can't try the second because i deleted my original md5 file and don't have those numbers.
The first solved that problem but created a "error while restoring /data" message every time so i replaced it with a blank file and now it says md5 mismatch
I have no idea, and need this backup
Thanks!
Click to expand...
Click to collapse
Use advanced restore option and restore all files except data .
Hope I helped
Sent from my GT-S7562 using XDA Premium 4 mobile app