# The PocketType Build Guide

<img src="/files/Th89Oqt5lGZVFmqRPjuv" alt="" width="375">

## Flash your controller

{% file src="/files/GVzmwQtpyokVKe79AOWS" %}

1. Connect the keyboard to your device using a USB cable.
2. Hold the BOOT button when plugging in the controller OR double tap the RESET button QUICKLY. (It might take a couple of attempts)
3. A file explorer window will pop up, copy the file from above into the directory. The windows should automatically close.
4. Once the window automatically closes, you can continue with the build. <br>

## Build Guide

1. Bend, fit and solder all the diodes- stripe should be towards the square pad
2. Bend, fit and solder the two resistors. Orientation doesn’t matter.
3. Fit all 48 switches. They’ll only go in one way. Solder them!
4. Fit the two LEDs. The long leg is the positive and goes into the round hole.
5. Fit and solder the header strips for the controller. Put the short side through the Pockettype PCB, leaving the long side pointing up. Solder just one pin until you are sure they are nice and straight and parallel to each other.
6. &#x20;Fit the controller onto the header strips. See above picture for correct orientation. Solder.
7. Plug in and test. Fit key caps.
8. Case assembly- see graphic below

<figure><img src="/files/I2M88SOzunDLjnO2sdp1" alt=""><figcaption></figcaption></figure>

## Using your PocketType

The firmware supports vial to allow for key rebinding, please see our [Using VIAL guide](/guides/other-guides/using-vial.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides-mechboards.gitbook.io/guides/mbuk-build-guides/list-of-other-build-guides/the-pockettype-build-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.