Just recently I have had a problem with a key store. I know there are plenty of questions about this problem already. I have read them all and Googled furiously.
My key alias stoped working sudenly. (Ok, after few updates of Android Studio and Java).
I tried all solutions from this thread as well as from others. In my case the solution was surprising. I have the keystore with few aliases. None was working except one, which had password the same as keystore. But unfortunately it wasn't the one I needed. This made me thinking with no logic involved. I copied single alias to new keystore with
keytool -importkeystore -srckeystore old.keystore -destkeystore new.keystore -srcalias importantalias
And then I changed alias password to the same as keystore's password with:
keytool -keypasswd -keystore new.keystore -alias importantalias
Finally I was able to sign my apk. It looks like silly bug which can waste a day of development.
I had the same problem and I tried everything that is suggested in this thread but nothing was able to save my alias password. The point is that I was absolutely sure about the password, since I had updated the app four times already. I was getting the "Keystore was tampered with, or password was incorrect" message.
It appears that at the creation of the keystore using eclipse, a space character was added in front of the password!
This nasty bug was apparently fixed at a later version rendering me unable to sign my app with the password I thought was the correct one.
Based on this SO link: Ant fails to build signed apk after updating to android v20 I would suggest that you try adding a space character before of after your password.