This question already has answers here:
How to handle a lost KeyStore password in Android?
(42 answers)
Closed 4 years ago.
I want to update my Application to playstore and I lost my keystore password.Now I am trying to create a new one . Will there be any problem if I build APK with another keystore password ?
As #CRUSADER said, Android Keystore Password Recovery might work for you. I could retrieve my password with it. Here is how to do that. I was on Windows 7.
Run the following command,
java -jar AndroidKeystoreBrute_v1.05.jar
Then you will get the following guide,
AndroidKeystorePasswordRecoveryTool by M#xiking
Version 1.03
There are 3 Methods to recover the key for your Keystore:
1: simply bruteforce - good luck
2: dictionary attack - your password has to be in the dictionary
3: smart dictionary attack - you specify a dictionary with regular pieces you use in your passwords. Numbers are automat
icly added and first letter will tested uppercase and lowercase
args:
-m <1..3> Method
-k <path> path to your keystore
-d <path> dictionary (for method 2 and 3)
-w saves the certificate in a new Keystore with same passwort than key
-start <String> sets start String of the word (for method 1)
-p use common replacements like '#' for 'a'(for method 3) WARNING - very slow!!
-h prints this helpscreen
Max memory: 247M
I've used method 2 because I had some guess of my password. I typed the following command,
java -jar AndroidKeystoreBrute_v1.05.jar -m 2 -k android.keystore -d dict.txt
In case you might wonder, my dict.txt was something like this,
gussedpassword1
gussedpassword2
gussedpassword3
I could successfully retrieve my password and alias.
Well, you are not the first to lose keystore password..
I use this one for bruteforce when I got stuck: Android Keystore recover
You can go with few guesses.
And as #StinePike mentioned.. you cannot continue updating your existing applications
There will be no problem for uploading new application. But you can not continue updating your existing application with new keystore. You need to create new applications by resubmitting them if you want to update your previous applications.
Always preserve the keystore with a best possible way :(
If you have lost the password to the keystore, then the only option is to create a new signing key. There will be no problem doing so.
However, you will not be able to update the existing application. And neither can you upload another application with the same package name.
For example, if you current package is:
com.example.mycurrentapp
You will need to use a different package name to go along with your new signing key. For example, you can change the package name to:
com.example.mynewapp
The above, are of course, illustrations. ;-)
The Google Play ecosystem identifies different applications using their package names and therefore, they have to be unique. Unfortunately, if you have a good user base, unless they install your new app, they will not be able to get updates to the older app.
It's unfortunate, but when you lose your keystore, or the password to your keystore, your application is orphaned. The only thing you can do is resubmit your app to the market under a new key. You will not be able to update your app without the key.
You will have to publish your app again with a new keystore and under a different package name, or remember your password.
Related
I just created my first game using Buildbox and I am trying to upload it to the Google Play Store. Apparently, I have to use Android Studio to turn the game file into an APK. So far, I know how to open it and select "Generate signed APK" or something along those lines, but then I am given a screen like this.
I have virtually no prior knowledge of any of this, so am I supposed to create a new key store path? Do I already have one? How do I do it?
Any tips are appreciated :)
Key Store Path is the location where your keystore should be created.
If you are creating an apk for first time to release in play store, you have to select 'Create New...' ketstore path, where in which you will be promoted to a new window where you can fill in the details:
KeyStore path : select a path in your system (Create a path in any drive eg: *F:\AndroidKeys*)give a name to your key(eg:game).save in here with the specific name for your project (F:\AndroidKeys\game.jks).
Password**: Give some new password and confirm it(Don't forget).
Alias : Enter an identifying name for your key.
Password : Create and confirm a secure password for your key. This should be different from the password you chose for your keystore.
Validity: select time period for validity of key.
Certificate: Enter some information about yourself or organization (like name,..).
Done with new key generation.
Now on the screen you mentioned select the path, key store password,key alias,key password(will be auto filled at first key generation).
click next -- select build variants(debug or release) release in your case, select the signature versions-- finish .
You can find your release apk in app\release folder of your project.
Note: Please do remember the key and the password it should be same for the future update release of your application.
Refer official android developer site for any referece: https://developer.android.com/studio/publish/app-signing
If it is your first time, create new path for example in your desktop. Then choose an arbitrary password and alias for yourself. Write somewhere your settings not to forget them.
can anyone clarify me that is it possible to recover keystore alias key?
i am in big trouble my app is already on playstore and update is ready,and stuck at this point
Here is link bruteforce
using from last two days,nothing works for me..
You can try and find the password in one of the gradle files if you still have the source code and were using Android Studio to develop the app. Try looking for:
..Project\.gradle\2.4\taskArtifacts\taskArtifacts.bin
Alternatively, you can create new keystore and set new password for it with the keytool command below. You don't need original keystore password for it:
keytool -importkeystore -srckeystore path/to/keystore/with/forgotten/pw \
-destkeystore path/to/my/new.keystore
When prompted, create password for your new.keystore and for source keystore password (which you lost) just hit Enter.
You will get warning about integrity not checked, and you will get your new.keystore identical to original with newly set password.
The reason this works is keystore password is only used to provide integrity of the keystore, it does not encrypt data with it, in contrast to private key password, which actually keeps your private key encrypted.
I know the step of siging the application.
problem is i lost my builded key for siging and i only know the password that key built with it.
is it possible to make another key with same password and use it for sign porgram to update old one ?
or should i rename my application and make new one ?
There is no way that you can update the app in playStore.You must be create an new app with a new package name and remove the old app, then republish new app
i have a problem when i want to run my android application, this is the error message :
Error generating final archive: java.security.UnrecoverableKeyException: Cannot recover key
how to solve this problem?
thankyou
Keystore password and key password both need to be the same. You must be getting this error if they are not same.
Either you have enter your keystore password or Alias password is wrong, that is why you got Cannot recover key Exception.enter correct password for both keystore and alias.
Sometimes if the key is invalid due to expiration,etc then this also happened
I had the same problem, and the solution was as follows:
1- When I changed the key store password,the returns was "error in the password who has tempered the key", in that case the keystore pass is incorrect.
2-If you have the following error, "cannot recover key", in that case the storepass is correct but the password for that alias is incorrect, i remembered my pass and changing, the problem is gone.
you have problem with your key.
This will give you how to info on keys
http://developer.android.com/tools/publishing/app-signing.html#debugmode
To change key in debug mode
(To do so in Eclipse/ADT, go to Windows > Preferences > Android > Build.)
This is one nightmare faced and documentation seem rather not clear on figuring your way out... I had the same issue but I understood after brainstorming.
Now in simplest term...
When you opt in for app signing, Google makes you create a key you use to sign in your app. This is like your legacy key (App signing certificate) and is the bedrock.
Now in uploading, another key is mapped to you which is a second layer ID to you, this lets you update your app.
Now whenever you loose the alias/password you contact google via your mail and they will tell you to create a new keystore that they will reset the old one(upload key) with because they have they legacy key already. Thus at any point in app lifecycle, you don't need to have your legacy key because they have housed it for you already.
I can't provide any input from my keyboard or from the on-screen keyboard when using keytool to generate key pair (public and private keys) and a signing certificate.
This problem occurs only when executing this command not in any other commands.
I tried using running command from .bat file but still can't provide any input.
The only input i can provide is enter(button).
So should i go forward by again providing enter(button)?
Note: I am referring Oreilly Android Application Development 2009.pdf
Web version: http://androidapps.org.ua/i_sect17_d1e6459.html
Are you sure you can't provide password? It doesn't show you any character when you type password and it is correct. Did you try print e.g. '123' as password and '456' as re-enter password? Does it say they don't match?