search

Jeija / bluefluff

Reverse Engineering Furby Connect's Bluetooth Protocol and Update Format
MIT License
478 stars 82 forks source link

Don't go above action 128 for Input 33 #29

Open jayasafunctionofe opened 6 years ago

jayasafunctionofe commented 6 years ago

Not really an issue, but a warning for others who are playing around. 33,0,0,129 and up will result in Furby getting stuck in a glitch loop. Sleep mask on/off will break them out of it.

DO NOT send 33,0,0,131, this will crash the Furby hard, you'll have to pull the batteries/power. https://youtu.be/xH1DomoyQV8

XxDJPartyGirl1034xX commented 6 years ago

Does this work for NRF connect too? The app?

jayasafunctionofe commented 6 years ago

The actions can all be triggered from the nRF Connect app, but the numbers need converted from decimal to hex and prefixed with '1300'

so, for example, action 17,0,0,5 (beatboxing) would be 130011000005 (17 becomes 11 when converted to hex)

XxDJPartyGirl1034xX commented 6 years ago

Are u able to give me the specific numbers for NRF connect that glitch Furby out plz and thank u? :D

jayasafunctionofe commented 6 years ago

I cannot speak for @Jeija , but I purposefully did not directly provide the value needed to crash a Furby connect. My experience has taught me that directly showing someone how to do something potentially dangerous without that person understanding what they are doing is problematic.

If you are going to be experimenting with something that could harm your own, or others' equipment, it may be in your best interest to research a little more so you are more prepared to handle potential problems you may run into.

XxDJPartyGirl1034xX commented 6 years ago

Meh, whatever, i just wondered if u could, FYI, i'm not trying to kill my Furby. Since u obviously have a perfect Bluefluff master on your PC, what PC do u have? I have an HP PC, and Windows 10. I've installed it, i get a Microsoft JS "Syntax error" from Windows Script Host... i'll keep trying and update u, and Jeija. I've also owned a Furby connect for 1 year, and got another one this christmas, and i've done tons of reaserch, and debugging a Furby connect, (the 2 are my own, no one elses), and ik how to fix most of the glitches.

XxDJPartyGirl1034xX commented 6 years ago

HOOOLLLYY SHIT! U were right, man! I tried this on FurBLE and it glitched my Furby Noo-Tah pretty hard, I just simply had to reset him, he works perfectly now. So, he’s ok.

XxDJPartyGirl1034xX commented 6 years ago

Also, don’t sent 33,0,0,130, sending this will result in the Furby saying one word over and over again, like, “Wah! Wah! Wah!” Until you press the reset button.

jayasafunctionofe commented 6 years ago

the other indexes all seem to end with with a "end of list" type of action where there are one or two actions that repeat at the end of every list (these actions normally also blink the antenna).

for some reason the name list doesn't do this, and anything above 128 causes a glitch, based on the behaviour it seems like triggering these actions results in some sort of invalid out of bounds memory access (hence the repeating or invalid noises and garbled graphics).

i'm not sure what harm would come from letting the furby sit in this state for any period of time.

XxDJPartyGirl1034xX commented 6 years ago

I’ve seen the glitch triggered by 129 before, and people have been saying that this glitch only occurs when they tap on the furbling when the Furby’s Bluetooth connection is present within the app, so, the app accidentally sends a name action command that’s above 128, causing it to spazz out. So that’s what causes that glitch. If this is the case, why does it only seem to happen to pink and blue Furby connects? I’m pretty sure it’s happened to other colours.

MonsterrTooth commented 1 month ago

I know I am BEYOND late to ask here, but as I have very little experience and wanna be careful

Is it possible to straight up brick a Furby irreparably by sending random commands, or am I good? Since there is no documentation on the specific DLC codes, and I'd love to just try and see what the full spectrum of actions is in general :D

Jeija commented 1 month ago

I don't think anyone can tell you for sure. Worst thing that happened to me was that I needed to re-insert the batteries, but I didn't ever brick my Furby.

jayasafunctionofe commented 1 month ago

I know I am BEYOND late to ask here, but as I have very little experience and wanna be careful

Is it possible to straight up brick a Furby irreparably by sending random commands, or am I good? Since there is no documentation on the specific DLC codes, and I'd love to just try and see what the full spectrum of actions is in general :D

I do not work for hasbro, so i can't make any guarantees, but if all you're doing is sending interaction commands you're probably safe, the worse i've seen is a crash that required a reboot.

i have not seen enough research done on the DLC files and how they're loaded to know for sure how unlikely or impossible it would be that you could, in theory, create a DLC file that result in a furby stuck in an unrecoverable state on boot up.

i would personally hope the "hard reset" would recover from this, but it's hard to say if hasbro planned for people sending unexpected (i.e. corrupt) files to a furby.

as for the "full spectrum of actions", i spend quite a bit of time documenting all the actions i could find here https://github.com/Jeija/bluefluff/blob/master/doc/actionlist.md

i'm doubtful, but would definitely love to know if, you find any new ones!