Successfully Imported Private Keys from Old Android Wallet into Coinomi !
In the previous comments above you will find instructions concerning openssl and decoding the android wallet.
(This topic was concerning importing private keys to desktop wallet, but this solution utilizes the Coinomi Android Wallet, from there you can send to your desktop wallet if desired)
I created an "openssl" directory on my cdrive, and placed the file in there, and ran the following:
C:\openssl>openssl enc -d -aes-256-cbc -a -in wallet.dat
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
enter aes-256-cbc decryption password: (type_pwd_here)
Example Output:
-----------------------
# KEEP YOUR PRIVATE KEYS SAFE! Anyone who can read this can spend your Bit
PPu1xUcGGuPMhYKPQspkSyqQee1XiFFk9Ba19yUhF1G4MaemEBzS 2014-06-29T16:17:09Z
PUANfzwVt2ftFqH5jizrDDkLdMYBnbHH6rz2g2YmbxAeHufYUxvq 2014-04-24T19:51:37Z
------------------------
I then simply pasted the above private keys (just individual codes, not date)
into http://www.the-qrcode-generator.com to create a QR Code.
Then used the Coinomi "Sweep Wallet" function to scan the QR Code.
Coinomi will verify that a balance exists and then "sweep" the wallet which may take some minutes.
When it finishes you will see a new AUR address and a Send button.
This address is simply another "receive" address for your Coinomi wallet.
Press "Send" and see the pending transaction in your balance tab.
------------
I have verified this process and the transaction has now been confirmed and appears in the blockchain.
Thank you Coinomi !
[aurtip]AeV3xdbvZCqbMa2DovWpBvmc9t5NWhz9VZ[/aurtip]
MegaHertz
Topic: Auroracoin: Importing private keys from Android wallet to desktop wallet (Read 2800 times)
August 23, 2016, 08:50:00 AM
May 07, 2016, 02:32:41 AM
WIF keys are in base58.
However in the meantime I got some kind of answer :
Quote
According to one of our devs it is not possible to import the keys from the Schildbach wallet directly into the auroracoin wallet. He is having a colleague to make a tool to achieve this, he would check tomorrow with him on the status of that.
We also found that the wallet contained a bug to import private keys (from paper wallets) with the latest wallet software. This has been fixed (currently in the development branch of the github repo) and new binaries are prepared.
We also found that the wallet contained a bug to import private keys (from paper wallets) with the latest wallet software. This has been fixed (currently in the development branch of the github repo) and new binaries are prepared.
For anyone exoeriencing this problem I would suggest to check this thread http://auroraspjall.is/viewtopic.php?f=7&t=349
April 18, 2016, 02:06:56 PM
Ok so it seems your backup file is still in the old (pre May 2014) format. Yes I think you should ask the Auroracoin people. In the Bitcoin world, you can import those WIF keys into Bitcoin Core with importprivkeys.
Andreas,do you know any tool to convert from WIF to Base58 ?
WIF keys are in base58.
April 18, 2016, 01:39:42 PM
Ok so it seems your backup file is still in the old (pre May 2014) format. Yes I think you should ask the Auroracoin people. In the Bitcoin world, you can import those WIF keys into Bitcoin Core with importprivkeys.
Andreas,do you know any tool to convert from WIF to Base58 ?
April 15, 2016, 04:22:50 PM
If – after decrypting – you could identify the file as a wallet (see end of "DECRYPTING" section of https://raw.githubusercontent.com/bitcoin-wallet/bitcoin-wallet/master/wallet/README.recover) decryption was obviously successful so this is not an encryption problem.
Hi Andreas, thanks for your replyYes, it's not decryption problem as long private key is 52 chars long. I repeated this steps on linux and win7 booth gives same output: 52 chars long key with date created.
Problem occurs when trying to importprivatekey on Windows based auroracoin wallet.
getting again -5 code
Quote
I assume all forks of Bitcoin Wallet use AES-256-CBC for backup encryption.
Should I contact with creator of AUR android wallet?.. 
Quote
In your description you skipped the part about using wallet-tool. Are you using that to extract the keys from the wallet?
I really don't know what is wallet-tool. Do you mean backup keys usual feature on any android wallet?Edit on 00:00 16/04/2016
Seems Aurora android wallet produces WIF format key which, as I read may be 51/52/53 chars long. Any advice?
Or, does any android wallet contains file named wallet.dat as usual version linux/ windows based?
April 10, 2016, 04:46:01 PM
I just faced problem with importing private keys from my Android wallet to desktop based.
I used openssl to decrypt this key using command enc -d -aes-256-cbc -in keyfile -a -k psswd.
In output I got 52 chars long key. When trying to importprivatekeys in debug console I got message: Invalid private key encoding (code -5)
So far I read compatible length of key is 58 chars.
Now would like to ask this question:
Are all android based wallets always using same kind encryption when creating backup keys : aes-256-cbc ?
Is command I used to decrypt keys correct?
Sorry, I'm just begginer, anyone help appreciated.
I used openssl to decrypt this key using command enc -d -aes-256-cbc -in keyfile -a -k psswd.
In output I got 52 chars long key. When trying to importprivatekeys in debug console I got message: Invalid private key encoding (code -5)
So far I read compatible length of key is 58 chars.
Now would like to ask this question:
Are all android based wallets always using same kind encryption when creating backup keys : aes-256-cbc ?
Is command I used to decrypt keys correct?
Sorry, I'm just begginer, anyone help appreciated.
Jump to: