[Verizon] MD5 Mismatch Error

scary alien · Jan 12, 2012

Well, I transferred my data.ext4.tar file to my Linux laptop and extracted the files so I could more easily review them. Here's the biggest files on my device:

Code:

# [COLOR="red"][B]find . -size +3500000c -ls | sed 's/^[ ]*//g' | cut -d ' ' -f 3-[/B][/COLOR]
-rw-------   1 scaryalien scaryalien  4202496 Dec 31 06:05 ./data/stericson.busybox/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien  7855844 Oct 30  2009 ./data/com.adobe.flashplayer/lib/libflashplayer.so
-rw-------   1 scaryalien scaryalien  4202496 Jan  1 20:02 ./data/com.weather.Weather/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien 15817584 Jan 15  2012 ./data/com.adobe.air/lib/libCore.so
-rwxr-xr-x   1 scaryalien scaryalien  4210721 Feb  6  2012 ./data/com.amazon.kindle/lib/libKRF.so
-rw-------   1 scaryalien scaryalien  4202496 Dec 20 13:44 ./data/com.amazon.kindle/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien 16570800 Jan 19  2012 ./data/com.google.earth/lib/libearthmobile.so
-rw-r-----   1 scaryalien scaryalien  3862528 Jan 11 11:56 ./data/com.google.android.gm/databases/mailstore.scary.alien@gmail.com.db
-rw-------   1 scaryalien scaryalien  4202496 Jan 11 11:56 ./data/com.google.android.gm/cache/webviewCacheChromium/data_3
-rw-------   1 scaryalien scaryalien  4202496 Jan  7 15:29 ./data/com.google.android.browser/cache/webviewCacheChromium/data_3
-rw-r--r--   1 scaryalien scaryalien  7392949 Jan 11 05:04 ./data/com.android.providers.downloads/cache/downloadfile-1.apk
-rw-------   1 scaryalien scaryalien  4202496 Jan  7 04:30 ./data/com.metago.astro/cache/webviewCacheChromium/data_3
-rw-r--r--   1 scaryalien scaryalien  4732928 Dec  7 15:30 ./dalvik-cache/system@app@Maps.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien 11324176 Dec  7 15:30 ./dalvik-cache/system@app@Thinkfree.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien  5019496 Jan 11 05:04 ./dalvik-cache/data@app@com.google.android.apps.maps-2.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien  4707663 Dec 19 05:15 ./app/com.adobe.flashplayer-1.apk
-rw-r--r--   1 scaryalien scaryalien  5240716 Dec 19 05:09 ./app/com.google.android.music-1.apk
-rw-r--r--   1 scaryalien scaryalien  8634759 Jan  4 16:15 ./app/com.google.earth-1.apk
-rw-r--r--   1 scaryalien scaryalien  7392949 Jan 11 05:04 ./app/com.google.android.apps.maps-2.apk
-rw-r--r--   1 scaryalien scaryalien  5735832 Jan  6 16:46 ./app/stericson.busybox-1.apk
-rw-r--r--   1 scaryalien scaryalien  3708455 Dec 22 06:32 ./app/com.android.vending-1.apk
-rw-r--r--   1 scaryalien scaryalien  3511811 Jan  9 03:33 ./app/com.keramidas.TitaniumBackup-1.apk
-rw-r--r--   1 scaryalien scaryalien  8781135 Dec 21 07:10 ./app/com.adobe.air-2.apk
-rw-r--r--   1 scaryalien scaryalien  9587332 Jan 11 05:02 ./app/com.amazon.kindle-2.apk

What's interesting that I found and that quickmustang might look for is the internet cache and the email cache and downloads take up quick a bit of space. Obviously your apps and dalvik-cache can also consume quite a bit of space.

There's got to be something very large that the OP has downloaded or received, etc. that accounts for the /data partition being so large.

quickmustang · Jan 13, 2012

scary alien said:

Well, I transferred my data.ext4.tar file to my Linux laptop and extracted the files so I could more easily review them. Here's the biggest files on my device:

Code:

# [COLOR="red"][B]find . -size +3500000c -ls | sed 's/^[ ]*//g' | cut -d ' ' -f 3-[/B][/COLOR]
-rw-------   1 scaryalien scaryalien  4202496 Dec 31 06:05 ./data/stericson.busybox/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien  7855844 Oct 30  2009 ./data/com.adobe.flashplayer/lib/libflashplayer.so
-rw-------   1 scaryalien scaryalien  4202496 Jan  1 20:02 ./data/com.weather.Weather/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien 15817584 Jan 15  2012 ./data/com.adobe.air/lib/libCore.so
-rwxr-xr-x   1 scaryalien scaryalien  4210721 Feb  6  2012 ./data/com.amazon.kindle/lib/libKRF.so
-rw-------   1 scaryalien scaryalien  4202496 Dec 20 13:44 ./data/com.amazon.kindle/cache/webviewCacheChromium/data_3
-rwxr-xr-x   1 scaryalien scaryalien 16570800 Jan 19  2012 ./data/com.google.earth/lib/libearthmobile.so
-rw-r-----   1 scaryalien scaryalien  3862528 Jan 11 11:56 ./data/com.google.android.gm/databases/mailstore.scary.alien@gmail.com.db
-rw-------   1 scaryalien scaryalien  4202496 Jan 11 11:56 ./data/com.google.android.gm/cache/webviewCacheChromium/data_3
-rw-------   1 scaryalien scaryalien  4202496 Jan  7 15:29 ./data/com.google.android.browser/cache/webviewCacheChromium/data_3
-rw-r--r--   1 scaryalien scaryalien  7392949 Jan 11 05:04 ./data/com.android.providers.downloads/cache/downloadfile-1.apk
-rw-------   1 scaryalien scaryalien  4202496 Jan  7 04:30 ./data/com.metago.astro/cache/webviewCacheChromium/data_3
-rw-r--r--   1 scaryalien scaryalien  4732928 Dec  7 15:30 ./dalvik-cache/system@app@Maps.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien 11324176 Dec  7 15:30 ./dalvik-cache/system@app@Thinkfree.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien  5019496 Jan 11 05:04 ./dalvik-cache/data@app@com.google.android.apps.maps-2.apk@classes.dex
-rw-r--r--   1 scaryalien scaryalien  4707663 Dec 19 05:15 ./app/com.adobe.flashplayer-1.apk
-rw-r--r--   1 scaryalien scaryalien  5240716 Dec 19 05:09 ./app/com.google.android.music-1.apk
-rw-r--r--   1 scaryalien scaryalien  8634759 Jan  4 16:15 ./app/com.google.earth-1.apk
-rw-r--r--   1 scaryalien scaryalien  7392949 Jan 11 05:04 ./app/com.google.android.apps.maps-2.apk
-rw-r--r--   1 scaryalien scaryalien  5735832 Jan  6 16:46 ./app/stericson.busybox-1.apk
-rw-r--r--   1 scaryalien scaryalien  3708455 Dec 22 06:32 ./app/com.android.vending-1.apk
-rw-r--r--   1 scaryalien scaryalien  3511811 Jan  9 03:33 ./app/com.keramidas.TitaniumBackup-1.apk
-rw-r--r--   1 scaryalien scaryalien  8781135 Dec 21 07:10 ./app/com.adobe.air-2.apk
-rw-r--r--   1 scaryalien scaryalien  9587332 Jan 11 05:02 ./app/com.amazon.kindle-2.apk

What's interesting that I found and that quickmustang might look for is the internet cache and the email cache and downloads take up quick a bit of space. Obviously your apps and dalvik-cache can also consume quite a bit of space.

There's got to be something very large that the OP has downloaded or received, etc. that accounts for the /data partition being so large.

Well I set my phone back to stock, then unlocked and rooted again. The backups were working great. I restored all my apps and made another backup. Everything was still good. Then I restored Nova launcher and flashed a new radio because my 3G signal wasn

scary alien · Jan 13, 2012

quickmustang said:
Well I set my phone back to stock, then unlocked and rooted again. The backups were working great. I restored all my apps and made another backup. Everything was still good. Then I restored Nova launcher and flashed a new radio because my 3G signal wasn’t working. Tried to create a back up then and I got the same problem again. I only had about 3.5 gigs on my internal memory at that time. Even if I restored to my first backup that worked and tried to back that up again, I would get the same error.

Wow...I'm not familiar with Nova launcher, but I can't imagine that the radio would take any extra or too much space.

What you have to remember is that you are basically backing-up everything from /data (excepting /data/media [i.e., you "SD card"]) and the other things that are backed-up for a Nandroid backup by CWM (/boot, /cache, /recovery, and /system) to /data/media [i.e., your "SD card"].

So, your /data partition needs to have at least as much space available (plus a little padding, of course) to accommodate all of that.

Its sounding like something is really making your /data partition grow too large. The fact that you were able to make Nandroid backups right after returning to stock says that the parts are working okay, but it must be one of the new things you are adding that overloading it.

If you (as nkk suggested) copy your data.ext4.tar to your PC and explore it with 7zip or winrar or Winzip, can you see what your largest directories and files are? (how they work and allow you to do that depends on which app you are using, of course).

That might reveal the culprit.

quickmustang · Jan 13, 2012

My entire data partition was only 3 Gb and the backup wasn't working.

scary alien · Jan 13, 2012

quickmustang said:
My entire data partition was only 3 Gb and the backup wasn't working.

That's from a current df?

Before, you reported this (I know it was before you returned to stock):

Code:

Filesystem Size  Used Free Blksize
/dev        347M  32K 347M  4096
/mnt/asec   347M   0K 347M  4096
/mnt/obb    347M   0K 347M  4096
/system     643M 318M 324M  4096
[COLOR="Red"][B]/data        28G  22G   5G  4096[/B][/COLOR]
/cache      425M   7M 418M  4096
/factory     19M   4M  15M  4096
/mnt/sdcard  28G  22G   5G  4096

which could easily explain what you were seeing before...

By the way, you can also do this on-phone (i.e., without having to use adb and your PC) by using something like the Android Terminal Emulator (free in the Market--great app). Doesn't require root to just type the df command.

If you've really only got 3GB used for /data, then I'm still stumped...

nkk · Jan 14, 2012

So... I am curious. Did a complete revert and reroot fix it?

Nkk

scary alien · Jan 14, 2012

nkk said:
So... I am curious. Did a complete revert and reroot fix it?

Nkk

Apparently and initially:

quickmustang said:
Well I set my phone back to stock, then unlocked and rooted again. The backups were working great. I restored all my apps and made another backup. Everything was still good. Then I restored Nova launcher and flashed a new radio because my 3G signal wasn’t working. Tried to create a back up then and I got the same problem again. I only had about 3.5 gigs on my internal memory at that time. Even if I restored to my first backup that worked and tried to back that up again, I would get the same error.

I didn't really get the nuance of quickmustang saying that even after he restored one of the first (stock-ish) Nandroids, that he couldn't re-run the Nandroid backup from there...

Puzzling and curious indeed...I'm stumped at this point...

nkk · Jan 14, 2012

scary alien said:
Apparently and initially:

I didn't really get the nuance of quickmustang saying that even after he restored one of the first (stock-ish) Nandroids, that he couldn't re-run the Nandroid backup from there...

Puzzling and curious indeed...I'm stumped at this point...

Hmm..interesting. That seems to point to the problem being with something that CWM restores. Odd. Oh well...if the OP figures out how to get it working, that is good.

Nkk

scary alien · Jan 14, 2012

nkk said:
Hmm..interesting. That seems to point to the problem being with something that CWM restores. Odd. Oh well...if the OP figures out how to get it working, that is good.

Nkk

You know...I now wonder if flashing the radio had something to do with it...like corrupting the /data partition or something? (wild guess).

quickmustang, what is the download link you used for the radio?

quickmustang · Jan 16, 2012

I got my radio file from here:

[RADIOS][Galaxy Nexus] All available radios/basebands - RootzWiki

I tried the 4.02 and the 4.03 radio. I am back to stock now because I had to take the phone in to Verizon to get my 3G to work again. Apparently my Sim card went bad. I don't know if that could have been causing my problem or not.

I never actually restored my nandroid backup. I just was able to get them to work. The backups stopped working once I installed the radio update.

I'm not the only person with this problem:

CWR Issues (Nandroid Backup/Restore) Failure

CWM mounting issue - RootzWiki

I can't decide if I want to root again or not now. I don't have tons of time to keep messing with things.

scary alien · Jan 16, 2012

Thanks quickmustang!

I'll take a look at those links this evening to see what the other guys say, too.

There's got to be some explanation, but its obviously not a consistent or simple cause / reason.

Thanks for your patience with all of this and all of our questions

.

Cheers!

scary alien · Jan 16, 2012

quickmustang,

Reading the first (non-radio) link reminded me of issues we saw and heard about in the Eris forums for folks using CWM and ROM Manager. I've also seen other references here and there, all related to ROM Manager causing unexplained issues for rooted folks. The issues we saw on the Eris involved various internal partitions on the phone getting memory blocks marked as bad. We never saw this with the Eris's normal Amon_RA custom recovery. But to be fair, we did have many reports of users that did use CWM and ROM Manager for the Eris without issue, but these were the more careful, experienced rooters.

I'm not trying to knock ROM Manager at all, but I'm wondering if you could try doing your stuff outside of ROM Manager and see if you have a different experience.

You can flash CWM with fastboot and invoke CWM for backups, etc. using something like Quickboot (which is what I always use).

Don't know if that will help, but it might be worth a shot, especially since you seem to be able to reproduce the problem.

Cheers!

quickmustang · Jan 16, 2012

scary alien said:
quickmustang,

I'm not trying to knock ROM Manager at all, but I'm wondering if you could try doing your stuff outside of ROM Manager and see if you have a different experience.

You can flash CWM with fastboot and invoke CWM for backups, etc. using something like Quickboot (which is what I always use).

Don't know if that will help, but it might be worth a shot, especially since you seem to be able to reproduce the problem.

Cheers!

Thanks for all your help. I don't know exactly what Quickboot is yet though. It might be a few days before I get to try anything again. I've got family from out of town in. Since I'm not the only one with the problem, I really want to figure it out so we can help the community.

scary alien · Jan 16, 2012

quickmustang said:
Thanks for all your help. I don't know exactly what Quickboot is yet though. It might be a few days before I get to try anything again. I've got family from out of town in. Since I'm not the only one with the problem, I really want to figure it out so we can help the community.

Oh, its just a simple (free) and really useful root app in the Market for rebooting either normally, into recovery, or bootloader mode, or to power off the device. I use that instead of ROM Manager to invoke CWM, etc. to initiate a custom recovery session. You could also power-down and reboot into bootloader mode and invoke recovery that way, too.

I was just thinking that if you were able to successfully able to do things without ROM Manager and things were okay, then maybe you could resume using ROM Manager and see if the problems reappear. That would be pretty conclusive to me.

Also, there was a flashable .zip file that erisuser1 wrote called MTD Inspect that displayed the bad block status for the various partitions on your phone. It might be useful in further debugging and/or ruling-out any bad memory block stuff that might be going on that we had previously attributed to the use of CWM/ROM Manager.

I guess it also could be that you simply had a device with a plethora of bad blocks already, and the issues you had performing Nandroid backups were a symptom of that.

So, did they replace your phone or just give you a new SIM card?

If you've got the same device, we could try running the MTD Inspect utility on your device to see what it reports (I'll have to try running it on mine first, of course).

Cheers!

quickmustang · Jan 16, 2012

They just replaced the sim card. I wouldn't mind trying to run something to look for bad blocks.

scary alien · Jan 16, 2012

quickmustang said:
They just replaced the sim card. I wouldn't mind trying to run something to look for bad blocks.

Okay, let me make sure its safe on my device first... I'll report back...

scary alien · Jan 17, 2012

scary alien said:
Okay, let me make sure its safe on my device first... I'll report back...

Blech!

Don't think this script / .zip is going to work...its got hard-coded /sdcard references in it for where to write its report. It also tries to inspect the mtd? partition mounts in /proc/mtd, for which there only appears to be one (mtd0) for the GNex.

I think I'm comparing apples to oranges here, unfortunately...sorry, but I'll have to do (a lot) more research.

Perhaps you could still revert back to stock again and then try to do your root activities sans ROM Manager...

Just an idea.

Cheers!

quickmustang · Jan 19, 2012

Well I think I'm going to replace my phone with another Nexus and try again. I am still having problems with my radio even after they replaced the sim card. I spend a lot of time with signal, but no data. If there is something physically wrong with the radio in the phone, maybe that explains why flashing a new radio messes everything up. Now I'm having camera problems too, so I think it's time for an exchange. All these problems are with the phone in a factory state.

quickmustang · Jan 20, 2012

So how do I do everything without rom manager? The instructions I have been seeing say reflash recovery through rom manager at the end.

scary alien · Jan 20, 2012

quickmustang said:
So how do I do everything without rom manager? The instructions I have been seeing say reflash recovery through rom manager at the end.

Well, you certainly should be able flash CWM via ROM Manager, I don't think there's any issue with that (at this point, and lots of other folks certainly do use ROM Manager to flash CWM).

If you've got fastboot and are able to use it, you can still be ROM Manager-free by flashing it that way:

How to install ClockworkMod custom recovery

(the fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img command is pretty straightforward though if you are comfortable with that utility)

I was just trying to get you to be ROM Manager-free for the sake of ruling it out as a possible reason for your issues.

Let me know if you have questions.

Cheers!

nkk · Jan 20, 2012

quickmustang said:
So how do I do everything without rom manager? The instructions I have been seeing say reflash recovery through rom manager at the end.

So...what is the problem?

Get the recovery image for CWM and "fastboot flash recover <path-to-recovery-image>" (no quotes). Obviously you issue this command in fastboot mode.

Now, if you already did that and the problem is that the recovery keeps reverting to stock after each reboot:

First go to /system/reboot_from_recovery.p (I do not know if that is the exct filename, but there is only one file with a similar name to the one I gave...that is it) and rename it to reboot_from_recovery.p.old.

That is the file that overwrites the recovery. Now it cannot be found, so it will not run and cause you hedaches.

Issue the fastboot command as above.

Now you are set. Enjoy.

-Nkk

EDIT: Nija'd.

scary alien · Jan 20, 2012

nkk said:
EDIT: Nija'd.

LOL...us aliens are sneaky like that, too!

BringTheRain403 · Jan 25, 2012

For those of you having trouble getting the backup to complete properly and you are getting the error mentioned in the 3rd post delete .android_secure from your SD Card and try the backup again. It fixed all my problems...

quickmustang · Jan 25, 2012

BringTheRain403 said:
For those of you having trouble getting the backup to complete properly and you are getting the error mentioned in the 3rd post delete .android_secure from your SD Card and try the backup again. It fixed all my problems...

I'm guessing that was my problem too. Although I have changed a few other things since then (the phone, no rom manager, etc.) but I don't seem to be having problems anymore.

Thanks so much to everyone that helped! I'm finally happy with my Nexus! Now to decide which ROM to run.

[Verizon] MD5 Mismatch Error

not really so scary

Newbie

not really so scary

Newbie

not really so scary

Android Expert

not really so scary

Android Expert

not really so scary

Newbie

not really so scary

not really so scary

Newbie

not really so scary

Newbie

not really so scary

not really so scary

Newbie

Newbie

not really so scary

Android Expert

not really so scary

Android Enthusiast

Newbie