The above link will definitely help.
Locate the debug.keystore by searching for it in the windows start button. start->type debug.keystore-> right click on search result-> open location->copy the location from address bar and use it for the
keytool.exe -list -alias androiddebugkey -keystore "C:\android\debug.keystore" -storepass android -keypass android
If somehow it fails the generate your own keystore file which is normally used for releasing your application for android devices...
You have a default debug keystore automatically. For release, you need to generate your own private keystore first with something like:
keytool -genkey -v -keystore my-release-key.keystore -alias release_alias -keyalg RSA -keysize 2048 -validity 10000
Once you've chosen and entered all the passwords (make a note of them!) you've generated a new MD5 (different from the debug one)
To view it:
keytool -list -alias release_alias -keystore c:\YOUR PATH TO IT\my-release-key.keystore
release_alias, 08-Sep-2010, PrivateKeyEntry, Certificate fingerprint (MD5): CE:xx:xx:xx etc....
If you use Google maps then you need a new API key for this. Repeat the process you did to generate the one for the debug MD5 but enter the new MD5
Hope this helps"
-from http://stackoverflow.com/questions/3781 ... w-keystore