This is an old revision of the document!
If your r0ket isn't working try the following steps in this order:
Please note: our market research has told us people buy stuff with closed crypto keys and vendor approved applications like crazy, theref0re the r0ket is compatible with this audience. The original firmware contains some crypto keys to make this possible, so if you flash your own firmware you will lose those forever. We don't want to stop you from doing so (everything you lose wouldn't be there without that stuff anyway), just wanted to tell you before you start flashing. Possibly you want to live on the Bluemchenwiese for a day or so before jailbreaking your badge…
Please also note: Camp hasn't even started yet and we are putting more stuff together on flashing etc. Some of us aren't even at Camp yet. Probably just start with the simulat0r if you want to write your own Tetris NOW.
Pushing joystick up while powering on erases the firstboot config. There is no risk in doing that except having to type in your nick again…
It SEEMS some badges have a wrongly formated DF. The DF is the 512K Chip storing the filesystem containing fonts, l0dables, config etc.
A corrupted FS can result in the badge displaying some error on firstboot about unavailable functions. You can attach the badge to a PC (linux preferred) and start the USB Storage in the menu, a 512K FAT filesystem with >30 files should appear. If that somehow looks crazy it MIGHT be you have a corrupted fs.
We will put up a dd image of a working filesystem soon - you can then dd that to your badge and should be fine. Note: there is a key pair in the flash for secure data transfer - if you copy someone elses badge you will share those keys with him. No real problem (at least if it's a friend you trust…), but you probably will want to recreate your own keys later. We will tell you how to do so here - I just currently don't know it…
Careful, display connectors are fragile.
Find someone who has a working display, try that. But: so far we haven't encountered a broken display. Your problem might be something else.