Skip to main content

How to recover data of your Android KeyStore?

These methods can save you by recovering Key Alias and Key Password and KeyStore Password.
Image for post
This dialog becomes trouble to you?
You should always keep the keystore file safe as you will not be able to update your previously uploaded APKs on PlayStore. It always need same keystore file for every version releases.
But it’s even worse when you have KeyStore file and you forget any credentials shown in above box.
But Good thing is you can recover them with certain tricks [Yes, there are always ways]. So let’s get straight to those ways.

1. Check your log files

→ For windows users,
Go to windows file explorer C://Users/your PC name/.AndroidStudio1.4 (your android studio version)\system\log\idea.log.1 (or any old log number)
Open your log file in Notepad++ or Any text editor, and search for:
android.injected.signing
and if you are lucky enough then you will start seeing these.
  1. Pandroid.injected.signing.store.file = This is file path where the keystore file was stored
    2. Pandroid.injected.signing.store.password = This is Key store password
    3. Pandroid.injected.signing.key.alias = This is Key alias name
    4. Pandroid.injected.signing.key.password = This is Key password
→ For MAC users,
Launch the Console utility and scrolled down to ~/Library/Logs -> AndroidStudioBeta(Version of your studio) ->idea.log.1 (or any old log number)
Search for android.injected.signing and you can get them.
 Pandroid.injected.signing.store.file=/Users/myuserid/AndroidStudioProjects/keystore/keystore.jks
-Pandroid.injected.signing.store.password=mystorepassword, 
-Pandroid.injected.signing.key.alias=myandroidkey, 
-Pandroid.injected.signing.key.password=mykeypassword,
2. In case you remember KeyStore password but not the Alias name
→ Launch command prompt(i.e CMD)
→ keytool -list -keystore [will show all available options]
Image for post
CMD/TERMINAL after running above command
→ Directly run keytool -list -v -keystore <full path to keystore file>
path example --> "C:\\users\admin\docs\main.keystore"
It will ask for KeyStore password and then shows name of alias,
Image for post
as in my case it shows main key

3. Do hack

→ Use BruteForce method to recover keystore password.
see this Google thread: https://code.google.com/archive/p/android-keystore-password-recover/wikis/HowTo.wiki
and also this github link : http://maxcamillo.github.io/android-keystore-password-recover/

Tips:

→ Any time you upload any app to PlayStore, save your keystore file and credentials at any safe place
→ The remember password checkbox shown in image top of the page, will not gonna save it for life time, if you upgrade your studio, there are chances you will loose them.
→ At least, save your KeyStore Password, as in certain tricks it’s the most vital.

Comments

Post a Comment

Thank You.

Popular Posts

Reloading UITableView while Animating Scroll in iOS 11

Reloading UITableView while Animating Scroll Calling  reloadData  on  UITableView  may not be the most efficient way to update your cells, but sometimes it’s easier to ensure the data you are storing is in sync with what your  UITableView  is showing. In iOS 10  reloadData  could be called at any time and it would not affect the scrolling UI of  UITableView . However, in iOS 11 calling  reloadData  while your  UITableView  is animating scrolling causes the  UITableView  to stop its scroll animation and not complete. We noticed this is only true for scroll animations triggered via one of the  UITableView  methods (such as  scrollToRow(at:at:animated:) ) and not for scroll animations caused by user interaction. This can be an issue when server responses trigger a  reloadData  call since they can happen at any moment, possibly when scroll animation is occurring. Example of s...
Post a Comment
Read more

What are the Alternatives of device UDID in iOS? - iOS7 / iOS 6 / iOS 5 – Get Device Unique Identifier UDID

Get Device Unique Identifier UDID Following code will help you to get the unique-device-identifier known as UDID. No matter what iOS user is using, you can get the UDID of the current iOS device by following code. - ( NSString *)UDID { NSString *uuidString = nil ; // get os version NSUInteger currentOSVersion = [[[[[UIDevice currentDevice ] systemVersion ] componentsSeparatedByString: @" . " ] objectAtIndex: 0 ] integerValue ]; if (currentOSVersion <= 5 ) { if ([[ NSUserDefaults standardUserDefaults ] valueForKey: @" udid " ]) { uuidString = [[ NSUserDefaults standardDefaults ] valueForKey: @" udid " ]; } else { CFUUIDRef uuidRef = CFUUIDCreate ( kCFAllocatorDefault ); uuidString = ( NSString *) CFBridgingRelease ( CFUUIDCreateString ( NULL ,uuidRef)); CFRelease (uuidRef); [[ NSUserDefaults standardUserDefaults ] setObject: uuidString ForKey: @" udid " ]; [[ NSUserDefaults standardUserDefaults ] synchro...
Post a Comment
Read more

Xcode & Instruments: Measuring Launch time, CPU Usage, Memory Leaks, Energy Impact and Frame Rate

When you’re developing applications for modern mobile devices, it’s vital that you consider the performance footprint that it has on older devices and in less than ideal network conditions. Fortunately Apple provides several powerful tools that enable Engineers to measure, investigate and understand the different performance characteristics of an application running on an iOS device. Recently I spent some time with these tools working to better understand the performance characteristics of an eCommerce application and finding ways that we can optimise the experience for our users. We realised that applications that are increasingly performance intensive, consume excessive amounts of memory, drain battery life and feel uncomfortably slow are less likely to retain users. With the release of iOS 12.0 it’s easier than ever for users to find applications that are consuming the most of their device’s finite amount of resources. Users can now make informed decisions abou...
Post a Comment
Read more