-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest i3s model (firmware 65) not working #37
Comments
In the meantime I got confirmed that i3S cubes with newer firmware don't work with the v1.2 version of the Supercube app. They must have changed something this year... We should investigate this, otherwise people who get the new cube models won't be able to use custom apps/websites made for Giiker cubes. :-/ |
Somebody with a background in cryptography should be able this, since you can generate a near infinite set of data and encrypted data.
… On 30 Aug 2019, at 08:21, Bence Kovacs ***@***.***> wrote:
In the meantime I got confirmed that i3S cubes with newer firmware don't work with the v1.2 version of the Supercube app. They must have changed something this year... We should investigate this, otherwise people who get the new cube models won't be able to use custom apps/websites made for Giiker cubes. :-/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#37?email_source=notifications&email_token=AIMFUESUSJGJQZBEPZBFUTTQHC4ANA5CNFSM4ISJL7V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5QVYBQ#issuecomment-526474246>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIMFUEVSSWNUOH25LTXBXF3QHC4ANANCNFSM4ISJL7VQ>.
|
I will post more status data soon, with the turn count as well... maybe it will help someone to crack it :-) |
All these data represent the FULLY SOLVED cube, with WHITE FORWARD as the last 4 turns: turn count: 2412 turn count: 2416 turn count: 2420 turn count: 2424 turn count: 2428 turn count: 2432 turn count: 2436 Regular data (from older firmwares) is like this:
I hope someone can do something about this! :-) |
You may wanna look into the cstimer repo, because they managed to decrypt the giiker I3se. As far as I can tell they also use a slightly diffrent approach when it comes to connecting. The link to their giiker.js file is here: Giiker.js file. I hope this helps. |
Wooow, thank you very much!!!!! :-) :-) :-) :-) |
i got today my i3s and want to connect with the hakatashi or pdoronila site but it doesnt work. on bluetooth.cubing.net it works but when i turn the side on the cube the site shows undefinied or ?. |
I believe the new version of the Giiker cube is called i3SE. |
any news why the "new 2019 version" can't connect? |
The giiker.js file mentioned above is already removed, but here is the decryption part.
|
the giiker.js above is renamed to bluetooth.js -> https://github.com/cs0x7f/cstimer/blob/master/src/js/bluetooth.js |
I've implemented the decryption part mentioned above in my fork of the bluetooth API that is used for the timer. Feel free to test the compatibility of different versions of the Giiker cube on https://kabelbinder.github.io/smart-cube-timer/ |
Last year we managed to work with firmware 65, but it seems that now Giiker might have come out with another firmware in April 2020. One of the cubes works with the Supercube app but not with our app... :-( |
One of my friends just purchased a Giiker i3s from Amazon, and his cube is not working with custom apps... Firmware version is 65 (my i3s has v39).
The cube seems sending encrypted data after each turn. The following is the normal data we should get for a fully solved cube, after WHITE side was rotated forward 4 times:
1234567833333333123456789abc000041414141
But this new model transmits different data even for the same state... the following 3 should be the same as the above (same state, same last 4 moves):
a1421c1a4759e9af00213cec7026f95e0eb1a70a
a716a8babc44f77eedd70c492ce2218d4744a7f9
4aa65c6109743e77a716a8ba23cdc44b1ce4a771
Maybe they encode the data with the step count as a secret cypher? 🤔
The text was updated successfully, but these errors were encountered: