Open kendopt opened 6 years ago
Is your device encrypted?
Hello, same thing here on a OnePlus 3T encrypted with Android 8 beta 20
Okay, it I will add an hint in the next version, if your Android is encrypted, it is not possible to do backups without a password, but this should not be a problem at all.
There is a problem when encrypted, it says it can't find the database --> manually, there was an error with "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7 or 8" see http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html or http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html --> i installed it, restarted mitoolkit --> no error, but no token !? I think it's because no password was provided...
Okay, it I will add an hint in the next version, if your Android is encrypted, it is not possible to do backups without a password, but this should not be a problem at all.
So it is possible to use a password with the backup? It doesn't seem to be an option with the current app
Das selbe hier, in der App habe ich keine Möglichkeit kein Password zu verwenden. Es muss mindestens ein Charakter verwendet werden, aber dann kann der Token nicht ausgelesen werden. Möglichkeit für eine Möglichkeit für ein Password? Ggf auch ein festen.
I also cannot make a backup without a password
I suffer from this password issue too. It would solve this issue if you would update your app in a way that it expects the password to be "pass", then in the popup which says now, that do not set a password, would say set "pass" as password.
Same here. Has this been solved?
Same problem for me with Huawei P9. The message on the phone say that since my device is encrypted, I can't create a backup without a password. Unfortunately, I think there are no way to "decrypt" the phone.
Yea, I could find no way to decrypt my Honor 8. I had to use a cheap tablet with an old version of Mi Home (v5.0.19). Then MiToolkit worked flawlessly... No reset was needed and my devices stayed paired with the original phone after Token recovery. It does look like Xiaomi is attempting to lock down its environment thugh so wait & see!
I've succeeded in decrypting the data base. You can use "android backup extractor" to transform the .ab in .tar and extract the miio2.db by typing inn windows console "java -jar abe.jar unpack NAME_OF_BACKUP.ab NAME_OF_BACKUP.tar
Hello, I managed to extract the Backup.ab database and opened the "devicerecord" table, it shows the information of my Xiaomi devices, but the Token field is empty. Is this normal?
thank you very much
Hi You have to install an older version of Mihome. The 5.09 work for me.
Le 14 févr. 2018 2:52 PM, "foudepc83" notifications@github.com a écrit :
Hello, I managed to extract the Backup.ab database and opened the "devicerecord" table, it shows the information of my Xiaomi devices, but the Token field is empty. Is this normal?
thank you very much
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ultrara1n/MiToolkit/issues/8#issuecomment-365613134, or mute the thread https://github.com/notifications/unsubscribe-auth/AinkLxlv0pnMLTjMl7k5nTQWDOup4DHYks5tUuUhgaJpZM4ROTX9 .
Thank you very much for your answer ! Do you have the link to download the old version of mihome? Thank you very much !
Hello, I managed using an old phone. To download, it's here: https://www.apkmirror.com/
Thank you very much !
Np you're welcome
Le 15 févr. 2018 4:42 PM, "foudepc83" notifications@github.com a écrit :
Hello, I managed using an old phone. To download, it's here: https://www.apkmirror.com/
Thank you very much !
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ultrara1n/MiToolkit/issues/8#issuecomment-365966324, or mute the thread https://github.com/notifications/unsubscribe-auth/AinkLw-fRtc9ysC7pTY4zVc2D6woNYEIks5tVFBngaJpZM4ROTX9 .
I've succeeded in decrypting the data base. You can use "android backup extractor" to transform the .ab in .tar and extract the miio2.db by typing inn windows console "java -jar abe.jar unpack NAME_OF_BACKUP.ab NAME_OF_BACKUP.tar ". The token is in the devicerecord table.
For the record: it can be downloaded form here: https://sourceforge.net/projects/adbextractor/files/latest/download
I've succeeded in decrypting the data base. You can use "android backup extractor" to transform the .ab in .tar and extract the miio2.db by typing inn windows console "java -jar abe.jar unpack NAME_OF_BACKUP.ab NAME_OF_BACKUP.tar ". The token is in the devicerecord table.
sorry I finally managed to extract the database, I do not see a devicerecord table ... is devicerecord a name of a file (its not there) or?
the option to create the backup is not selectable until I write something on the password field