update 5/2/2011: wow...forgot about this old thread...FYI, please check out this thread:
http://androidforums.com/application-announcements/209740-app-afv-android-file-verifier.html#post2637616
for a more up-to-date, current version of this app.
Cheers and enjoy!
--------------------------------------------------------------------
~-~-~ On-phone ROM Checksum Verifier ~-~-~
Download: View attachment MD5-Checksum-v2.2.apk (new version!)
Changes in the 2.2 version include:
1. larger rows and font for easier/better file-selection
2. sorted list of files displayed in file-selector
3. retain directory between each file-selection
4. verify read-access of selected file to prevent force-close
5. test file's suffix to warn if non jar-type file is selected for jar-verification
6. add menu support (help, change log, acknowledgements)
Download: View attachment MD5-Checksum-v2.1.apk
This version is detailed in a post over at XDA (xda-developers - View Single Post - [Begging] Devs - please publish your MD5's) but its highlights are as follows:
- still includes all of the functionality of the previous versions
- now includes two jar file verification functions (they both basically do the same thing; radio button JV1 selects an explicit jar verification (read jar, calculate SHA1 digest, compare to manifest); radio button JV2 just uses the implicit JarFile Java method of jar verification and is much faster since its not doing a second, separate validation (23 seconds for method JV2 on a 100MB ROM vs. 2.5 minutes for method JV1 (all on my Droid X)).
- now has a file-selector instead of requiring manual filename text input (you can still do this too)
======================================================
Download: View attachment MD5 Checksum v1.1.apk (free!)
Download: View attachment checksumdb.txt (save to either /sdcard/download or /sdcard)
Note: if you have problems downloading via the stock browser, try using a different browser (Opera Mini works just fine).
Our esteemed erisuser1 has long been exhorting folks to verify the size and checksums of the files that they download (see thread over on XDA [Begging] Devs - please publish your MD5's - xda-developers and this post http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-7.html#post1296149).
I originally created the MD5 Checksum (v1.0) app (ref. http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html) to assist in this effort.
To try to take it one step further and in lieu of a real (very difficult at this time to do on the phone) 'jarsigner -verify', I have updated my MD5 Checksum app to now include a basic ROM checksum verification feature. Note: this does not have to be used exclusively for ROMs--this verification can be done on any type of file.
It does this by comparing a selected file's checksum (either MD5 or SHA1) and file size against a database of known values.
 
Here's the details about what has (and has not) changed:
1. The original, basic function of the app remains intact and unchanged.
2. At startup, the app loads a file named "checksumdb.txt". This file contains file name, file size, and checksum (both MD5 and SHA1) information about many (approx. 70) of the well-known Eris custom ROMs.
3. Next, when you input the name of a file (yes, a file-selector feature is still very desireable and is forthcoming), the app will, as before, calculate either an MD5 or an SHA1 checksum depending on which you selected via the radio button.
4. Then, the app will scan through the information from the checksumdb.txt file previously loaded at startup and will look for entries whose filesize and checksum match the entered file.
4a. If the filename, filesize, and selected checksum all match the information loaded from the checksumdb.txt, you will see a pop-up indicating "- VERIFIED -" (with an "Awesome!" button ).
4b. If only filesize and checksum match the database, then you will see "- verified -" (with an "awesome!" button) displayed. Additionally, the presumed name of the file from the database will be included in the pop-up.
4c. If the file is not found in the database at all, you will see the same information that you normally would (i.e., no pop-up).
That's about it. I'll go back and update the other thread (http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html) when time permits.
Screenshots:
 
Notes:
1. The checksumdb.txt file can be located in either /sdcard (checked first) or /sdcard/download (checked second).
2. A file-selector feature is being worked on so that you don't have to type-in the filename...stay tuned...
3. SHA1 checksums can take a very long time to calculate, especially for very large files (so, be patient or choose MD5). The "Calculate" button will remain red while the checksum is being calculated.
4. There are obviously new custom ROMs being created all the time, so the checksumdb.txt file will need to be updated, but the app will not.
5. If you find a new ROM that is not in the checksumdb.txt and happen to download it, feel free to post in this thread the ROM name, file size (in bytes), and its MD5 and/or SHA1 checksum, and I will update the checksumdb.txt file in this thread for the benefit of all.
6. The old, v1.0 version of this app obviously does not know about the checksumdb.txt file and cannot verify against it.
7. The files that are in the checksumdb.txt file do not have to be ROMs--they can actually be any file type whatsoever.
8. Just like the original v1.0 app, this one was developed to be able to run on Android version 1.5 and higher.
9. The checksumdb.txt file was created for this app by downloading approximately 70 Eris ROMs (more than six gigabytes worth) and calculating both their MD5 and SHA1 checksums. Yeah, it took me a while .
Click below to view a sample (top portion) of the checksumdb.txt file:
I hope this is helpful. Let me know what you think. Cheers!
http://androidforums.com/application-announcements/209740-app-afv-android-file-verifier.html#post2637616
for a more up-to-date, current version of this app.
Cheers and enjoy!
--------------------------------------------------------------------
~-~-~ On-phone ROM Checksum Verifier ~-~-~
Download: View attachment MD5-Checksum-v2.2.apk (new version!)
Changes in the 2.2 version include:
1. larger rows and font for easier/better file-selection
2. sorted list of files displayed in file-selector
3. retain directory between each file-selection
4. verify read-access of selected file to prevent force-close
5. test file's suffix to warn if non jar-type file is selected for jar-verification
6. add menu support (help, change log, acknowledgements)
Download: View attachment MD5-Checksum-v2.1.apk
This version is detailed in a post over at XDA (xda-developers - View Single Post - [Begging] Devs - please publish your MD5's) but its highlights are as follows:
- still includes all of the functionality of the previous versions
- now includes two jar file verification functions (they both basically do the same thing; radio button JV1 selects an explicit jar verification (read jar, calculate SHA1 digest, compare to manifest); radio button JV2 just uses the implicit JarFile Java method of jar verification and is much faster since its not doing a second, separate validation (23 seconds for method JV2 on a 100MB ROM vs. 2.5 minutes for method JV1 (all on my Droid X)).
- now has a file-selector instead of requiring manual filename text input (you can still do this too)
======================================================
Download: View attachment MD5 Checksum v1.1.apk (free!)
Download: View attachment checksumdb.txt (save to either /sdcard/download or /sdcard)
Code:
[FONT=Courier New]Checksums for 'MD5-Checksum-v2.2.apk':[/FONT]
[FONT=Courier New]Size: 36,523 (bytes)[/FONT]
[FONT=Courier New]MD5: 3aec3fd4cae8f200db8457894ae4193f[/FONT]
[FONT=Courier New]SHA1: b164382f92259aa0726c7fe61178904c58bc5fbc[/FONT]
[FONT=Courier New]Checksums for 'MD5-Checksum-v2.1.apk':[/FONT]
[FONT=Courier New]Size: 33,268 (bytes)[/FONT]
[FONT=Courier New]MD5: 667440bb47bd574c4972d1fa6f4cfda1[/FONT]
[FONT=Courier New]SHA1: 394f16a5520dab3ff1f56bd769695040d2447df2[/FONT]
[FONT=Courier New]Checksums for 'MD5-Checksum-v2.0.apk':[/FONT]
[FONT=Courier New]Size: 28,951 (bytes)[/FONT]
[FONT=Courier New]MD5: 2fd0d7bf6cd2b43a667592eb4ed83c15[/FONT]
[FONT=Courier New]SHA1: 287419e3e006d514b2f8287b1a0a524e0dd39818[/FONT]
[FONT=Courier New]Checksums for 'checksumdb.txt':[/FONT]
[FONT=Courier New]Size: 20,480 (bytes)[/FONT]
[FONT=Courier New]MD5: a68db3d2e822938fe9f626b82d054a5f[/FONT]
[FONT=Courier New]SHA1: dc4899c45be32472c925123395c502f3852b9d24[/FONT]
[FONT=Courier New]Checksums for 'MD5 Checksum v1.1.apk': [/FONT]
[FONT=Courier New]MD5: 0f70015e405e08470ea705161a1a5253 [/FONT]
[FONT=Courier New]SHA1: f15cf0fb4dca386a154b1eecccc8d7b13267421a[/FONT]
Our esteemed erisuser1 has long been exhorting folks to verify the size and checksums of the files that they download (see thread over on XDA [Begging] Devs - please publish your MD5's - xda-developers and this post http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-7.html#post1296149).
I originally created the MD5 Checksum (v1.0) app (ref. http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html) to assist in this effort.
To try to take it one step further and in lieu of a real (very difficult at this time to do on the phone) 'jarsigner -verify', I have updated my MD5 Checksum app to now include a basic ROM checksum verification feature. Note: this does not have to be used exclusively for ROMs--this verification can be done on any type of file.
It does this by comparing a selected file's checksum (either MD5 or SHA1) and file size against a database of known values.
 
Here's the details about what has (and has not) changed:
1. The original, basic function of the app remains intact and unchanged.
2. At startup, the app loads a file named "checksumdb.txt". This file contains file name, file size, and checksum (both MD5 and SHA1) information about many (approx. 70) of the well-known Eris custom ROMs.
3. Next, when you input the name of a file (yes, a file-selector feature is still very desireable and is forthcoming), the app will, as before, calculate either an MD5 or an SHA1 checksum depending on which you selected via the radio button.
4. Then, the app will scan through the information from the checksumdb.txt file previously loaded at startup and will look for entries whose filesize and checksum match the entered file.
4a. If the filename, filesize, and selected checksum all match the information loaded from the checksumdb.txt, you will see a pop-up indicating "- VERIFIED -" (with an "Awesome!" button ).
4b. If only filesize and checksum match the database, then you will see "- verified -" (with an "awesome!" button) displayed. Additionally, the presumed name of the file from the database will be included in the pop-up.
4c. If the file is not found in the database at all, you will see the same information that you normally would (i.e., no pop-up).
That's about it. I'll go back and update the other thread (http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html) when time permits.
Screenshots:
 
Notes:
1. The checksumdb.txt file can be located in either /sdcard (checked first) or /sdcard/download (checked second).
2. A file-selector feature is being worked on so that you don't have to type-in the filename...stay tuned...
3. SHA1 checksums can take a very long time to calculate, especially for very large files (so, be patient or choose MD5). The "Calculate" button will remain red while the checksum is being calculated.
4. There are obviously new custom ROMs being created all the time, so the checksumdb.txt file will need to be updated, but the app will not.
5. If you find a new ROM that is not in the checksumdb.txt and happen to download it, feel free to post in this thread the ROM name, file size (in bytes), and its MD5 and/or SHA1 checksum, and I will update the checksumdb.txt file in this thread for the benefit of all.
6. The old, v1.0 version of this app obviously does not know about the checksumdb.txt file and cannot verify against it.
7. The files that are in the checksumdb.txt file do not have to be ROMs--they can actually be any file type whatsoever.
8. Just like the original v1.0 app, this one was developed to be able to run on Android version 1.5 and higher.
9. The checksumdb.txt file was created for this app by downloading approximately 70 Eris ROMs (more than six gigabytes worth) and calculating both their MD5 and SHA1 checksums. Yeah, it took me a while .
Click below to view a sample (top portion) of the checksumdb.txt file:
Code:
// ------------------------------------------------------------------------------------------------------------
// checksumdb.txt - for ScaryAlienWare's MD5 Checksum v1.1 app
// last updated 05-Sep-2010 14:24
//
// format of non-comment entries:
//
// <phonetype> <filetype> <checksumtype> <filename> <filesize> <checksum>
//
// where <phonetype> = "desirec" (for the Eris); field is reserved for future use
//
// <filetype> = "ROM" for custom ROMs; field is reserved for future use
// "upd" for update.zip-type files
// "file" for everything else
//
// <checksumtype> = "MD5" for MD5 checksums
// "SHA1" for SHA1 checksums
//
// <filename> = name of the file being registered in this database; do not include spaces/blanks
// in the filename or else this line will not be correctly parsed
//
// <filesize> = size of the file in bytes
//
// <checksum> = value of either the MD5 or SHA1 checksum of the file
//
// ------------------------------------------------------------------------------------------------------------
// testing files
//
any file MD5 gscript.zip 3915189 92796a8c6e61e8f1ee36e315c0acae7d
any file SHA1 gscript.zip 3915189 8e624c04db2a7fcbfd48ce5ae015d9ea890fda26
// ------------------------------------------------------------------------------------------------------------
// CPCookieMan's ROMs
//
desirec ROM MD5 TheCookieRomV0.34.zip 111685324 1e77c7591987a722464202dfba93b395
desirec ROM MD5 TheCookieRom_0.4.zip 112053696 f176d1774ca1c877c26989f6335cb107
//
desirec ROM SHA1 TheCookieRomV0.34.zip 111685324 407adeb11f7822c284d2912d4f48a245a4f71afc
desirec ROM SHA1 TheCookieRom_0.4.zip 112053696 fa7f211d75d56bec9c013311c921c6e190d9399b
//
// ------------------------------------------------------------------------------------------------------------
// Conaps's ROMs:
//
desirec ROM MD5 CELBFroyo2.1.zip 53788185 450ab221a13d0890438dee0494c14f6b
desirec ROM MD5 CELBFroyo2.2.zip 56835915 a83a52344b123ae7c8c32ddb5d93d163
desirec ROM MD5 CELBFroyo2.3.zip 57785330 f91fed960a3f3f5270271cecd901d802
desirec ROM MD5 CyanogenELB2.8.zip 54300252 9921f2c41b7ca86180277e39d9d0e915
desirec ROM MD5 DroidDoesPink2.0.zip 104301735 6f1bbcd11060acf9b4c62b41129c973e
desirec ROM MD5 ErisLightning3.02.zip 101481107 3f272f3d859aeeb777163c4fe681efa4
desirec ROM MD5 ErisLightningBolt1.4.zip 97205705 d438f214890b598cc9e9d630b39b61fb
//
desirec ROM SHA1 CELBFroyo2.1.zip 53788185 48a4fd29a25a95faa3a685895b14d0b7df6ebc3a
desirec ROM SHA1 CELBFroyo2.2.zip 56835915 5e2fbf7bb6c5d6a96d45702d2fe699aea14c9221
desirec ROM SHA1 CELBFroyo2.3.zip 57785330 5109fe7441ce347229392926dcca1dc373381d7c
desirec ROM SHA1 CyanogenELB2.8.zip 54300252 08bb790eb24665a1f0337f0040c928efcb308f7e
desirec ROM SHA1 DroidDoesPink2.0.zip 104301735 d4f81da8699eb414501700858869f13292620113
desirec ROM SHA1 ErisLightning3.02.zip 101481107 a2f59baa8b865d2171f40fdcd05572a63c51ab53
desirec ROM SHA1 ErisLightningBolt1.4.zip 97205705 3910e88601b3c400623fb25623df4a06550f63dd