*solved* Md5 mismatch - Motorola Droid Bionic

so I made a backup through CWM of my current rom, and installed another rom, and changed my mind and wanted to go back. When I try to do so I get an MD5SUM Mismatch error. I have not changed the names of the folders in anyway shape or form.
I found a thread on XDA with a fix, which I tried, to no luck. http://forum.xda-developers.com/showthread.php?t=714114
anyone have any ideas? I can live without what was in the backup if I need to...but I would rather not.
I did notice that the file size of the other MD5 sums I have for my other backups is closer to 130+ KB files, and the new one is 22 KB.... my biggest backup yet, with the smallest MD5 sum?
any ideas?
EDIT: further looking into this I noticed that the backup files are .ext3.tar so I tried from the other post, instead of doing "md5sum *img > nandroid.md5" i tried "md5sum *ext3.tar > nandroid.md5" and "md5sum *tar > nandroid.md5" and both of these fail aswell. Still looking for any ideas on how to fix this.
EDIT #2: I figured it out...after being beyond frustrated...lol. So when I used Notepad++ to open the nandroid.md5 file, and use MD5 calculator to verify the actual MD5sums, i noticed something interesting between multiple backups. Every other nandroid.md5 file I had, had two spaces between the MD5sum and the file name, except the one I had that was failing. So I fixed this, and my rom is restoring as we speak. So incase anyone else has this issue, and wants to fix their MD5sum error, here is what it should look like
a5cf3fc0bc5144856c9bba7f410ece5f data.ext3.tar. So with two spaces, not one.

Related

Problems in restoring from CWM

Hey guys,
I need help. I just realized that I couldn't restore from CWM backup. I have several backups and I even tried diff version of CWM but all keep saying MD5 checksum match error.
What should I do?
Thanks
Sent from my LG-P990 using XDA App
have you changed the name of them??
They need to be left exactly as the phone makes them
They don't, but you can't have spaces in the name of the folder.
If all else fails, recreate the checksum:
Code:
md5sum *.img > nandriod.md5
Rusty! said:
They don't, but you can't have spaces in the name of the folder.
If all else fails, recreate the checksum:
Code:
md5sum *.img > nandriod.md5
Click to expand...
Click to collapse
not sure i understand this. the code that you mentioned, where should i run it? thanks
Run it via adb shell/terminal in the folder the backup is in
thanks rusty

MD5 Mismatch! How come?

Hi guys. I flashed a new baseband for my Optimus 2x. After that, I wanted to restore my backup and I get a MD5 Mismatch. How come? I didn't rename my backup or changed the recovery. Nothing!
hey, i had this not so long ago, its nothing more than a bad nandroid backup, nothing will fix it, you gotta reflash another backup or start over (i started over cuz other backups were too old)
You may be able to solve it with these steps:
1. Go to the directory of the backup.
2. Delete nandroid.md5
3. Recreate nandroid.md5 of all images with 'md5sum'.
Sent from my Optimus 2X using xda premium
Egan said:
You may be able to solve it with these steps:
1. Go to the directory of the backup.
2. Delete nandroid.md5
3. Recreate nandroid.md5 of all images with 'md5sum'.
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
This will allow you to flash a corrupt image, and is therefore not recommended
I got one just today, really annoying..
@kiljaken any idea why it happens, or how it can be avoided?
Imperticus said:
I got one just today, really annoying..
@kiljaken any idea why it happens, or how it can be avoided?
Click to expand...
Click to collapse
Not really no. All it takes is one changed bit in either file
My guess is you renamed the folder with a space, if so, try without it, if not then recreate the md5 as mentioned the MD5 with md5sum * > nandroid.md5
I always have this issue when I make the back up through Rom Manager. So I always make it now in clockwork recovery mode.
Rusty! said:
My guess is you renamed the folder with a space, if so, try without it, if not then recreate the md5 as mentioned the MD5 with md5sum * nandroid.md5
Click to expand...
Click to collapse
Works!!! Thank you..
1) rename folder (no spaces)
2) inside the folder, type "rm nandroid.md5"
3) then type "md5sum * > nandroid.md5
Sent from my LG-P990 using XDA App
Good spot, I missed out the >

[XT860] Help is needed (urgent)

i tried xUltimate to deodexing my XT860 and...... since then ו'm stuck in boot loop
Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium
Endoroid said:
Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!
boazal said:
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!
Click to expand...
Click to collapse
****ty. I don't know if there is a way to fix that. Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Sent from my XT860 using xda premium
If yes to my last question, just flash the stock bell 2.3.6 rom located in the dev forum. If no then you have 2 options. First it follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=1404608
Or
Use motofastboot to flash a system.img, this will restore the /system, reroot, install bootstrap and then flash the already deodexed stock bell rom I previously mentioned to restore your /system, remove bootstrap, install safestrap and flash either that rom, or the rom of your choice into safe system and use safe system from now on.
Sent from my XT860 using xda premium
You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before
DeadChex said:
You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before
Click to expand...
Click to collapse
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium
Endoroid said:
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The back up should just be a folder, open the folder, and run the MD5 Command in the Terminal on each of the backup archives (eg cache.ext3.tar, system.ext3.tar) and put them into nandroid.md5
The nandroid.md5 file should hopefully be laid out easily and just replace the hashes (random letters and numbers) with the ones you generated with the correct file's hash
And Restore away!
Endoroid said:
Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Click to expand...
Click to collapse
don't know, how to find out?
boazal said:
don't know, how to find out?
Click to expand...
Click to collapse
V1.08d
Sent from my XT860 using xda premium
Endoroid said:
V1.08d
Click to expand...
Click to collapse
it's v1.08,
what can be done?
Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Sent from my XT860 using xda premium
Endoroid said:
Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Click to expand...
Click to collapse
sorry for bothering, i'm not familiar with the process, can you guide newbi? (preferred flash the rom methods)
people's, please i need assistance.....
boazal said:
people's, please i need assistance.....
Click to expand...
Click to collapse
Im at work but later tonight I will give more detailed instructions
Sent from my XT860 using xda premium
Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Method- Manually Altering MD5 Sums (Linux-Ubuntu)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
4. Run md5sum on system.ext3.tar
Write down that MD5
5. Run md5sum on data.ext3.tar
Write down that MD5
6. Run md5sum on cache.ext3.tar
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
You're gonna have to do the leg work to get the files and programs I mention because finding and linking while on my fine is a pita.
There is another option, the easiest of all, however it will remove you from the bell update path as we have no way currently of returning to the stock bell firmware. You can grab rsdlite and a fastboot package from the dev forum and flash that, it will fix it up but you are no longer on bell firmware. Up to you if you can live with that.
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Find zergrush easy root utility and follow the directions for it to root your phone, then install a bootstrap(or the tweaked safestrap that allows nonsafe flashing and then go grab the stock bell rom from dev forum and flash that. It is already deodexed.
this will keep you stock bell
Sent from my XT860 using xda premium
DeadChex said:
Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Click to expand...
Click to collapse
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!
Endoroid said:
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Click to expand...
Click to collapse
C:\moto-fastboot-win32>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.386s]
writing 'system'... OKAY [ 15.596s]
sending 'system' (175872 KB)... OKAY [ 17.214s]
writing 'system'... OKAY [ 9.043s]
but refuse to boot
boazal said:
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!
Click to expand...
Click to collapse
Linux or Windows? Esure you are safely ejecting (windows) or unmounting/ejecting (Linux) before removing the SDCard, I've noticed file changes sometimes don't stick if you don't safely eject.
I'm not sure if the method I'm giving is a soloution anymore with the reflash (That's not a bad thing!)

can an OTA update be modified?

How can one go about modifying an OTA update? I see there is an updater-script file in-particular that checks the ckecksums of system files before loading the OTA... can this file be modified and what would be the procedure? Thanks in advance.
I'd like to modify the checksum values listed in this file to have it accept certain modified system files... What is used to calculate the checksum values?
Should be in Q&A. Reported.
Moved to Q and A
I found that sha-1 is used to create the checksums values in the updater-script file. In the assert check_patch lines the first value is the new file and the last value is original file. In the assert apply_patch lines same is true except middle value is size of new file in bytes.
Beyond this it looks as if the CERT.RSA, CERT.SF, and MANIFEST.MF files in the META-INF folder of your update.zip may be the next obstacle... I know this thanks to jhankinson thread on the topic.
I don't know if jhankinsons solution to simply deleting these and resigning would work on the Bionic? (I'm total noob in this regard.)
Perhaps we can edit the checksum values in these files. I found that in the MANIFEST.MF file checksums are simply SHA-1-BASE64.
Anyone know what is used for the values in the CERT.SF file? (it says it's sha1-digest but i'm using fsum-frontend with no luck getting a match)
And would I need to do anything with the CERT.RSA file? (Again total noob to how these are signed)

problem with replacing gps.conf

Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much

Categories

Resources