This page needs JavaScript

Reading your flysight.txt and picking the right firmware is done by script, in your browser — there is no server doing it for you. With JavaScript switched off, this page can only show you the instructions.

Turn JavaScript on and reload, or ask whoever pointed you here for the file that matches the Pubkey_X line in your flysight.txt.

// FIRMWARE FLASHER · FLYSIGHT 2 · ENGO HUD

GROUNDRUSH FLASHER

Install the ENGO HUD firmware on your FlySight 2. This page works out which firmware your device needs, checks it, and — in some browsers — writes it for you. Everything happens on your own machine: no file you touch is uploaded anywhere, and there is no account to make.

How this actually works

The FlySight 2 has no over-the-air update for this. What it does have is a bootloader: hold the button until the light turns orange and the device re-appears on your computer as a plain USB drive. Put a firmware file at FW/APP.SFB on that drive, eject it, and the bootloader installs the firmware on the next power-up.

Firmware is encrypted for one manufacturing batch, so there are five different files and only one of them will install on your device. Your FlySight says which batch it is in a file called flysight.txt in the top level of its drive. That is the only thing this page needs to read.

Jump to: identify & download which file do I need? what this page will and won't do

DEVICE CONSOLE IDLE

Every line above is a real event on this page. Nothing here is a simulation, and there is no progress bar for work that is not happening.

// PATH A

ONE-CLICK INSTALL

1
Identify your FlySight

Plug the FlySight into this computer with a USB cable, normally — no button holding yet. Wait until it appears as a drive, then click the button and choose that drive.

The browser will ask you to confirm. This step only reads flysight.txt; nothing is written and nothing leaves your computer.
2
Put the FlySight into bootloader mode
This is the step everyone gets wrong. If you copy the firmware onto the FlySight while it is in its normal USB mode, absolutely nothing happens — the file just sits there for ever, the firmware version never changes, and it looks as if the update failed silently. It did not fail. It was never offered to the bootloader.

With the FlySight still plugged in:
1. Press and hold the FlySight's button.
2. Keep holding for about ten seconds — through the other colours — until the light turns orange.
3. Let go. The drive will disappear and come back. That new drive is the bootloader, and it is the only thing that will accept the firmware.
Orange light = bootloader = ready. No orange light, no install. If you never reach orange, unplug, plug back in, and hold for longer.
3
Write the firmware

Click below and choose the drive that appeared when the light turned orange. This time the browser will ask for permission to change files — that is what writing the firmware needs.

This page then downloads the firmware for your batch, checks its SHA-256 against the published checksum, writes it to FW/APP.SFB, and reads it back to prove it landed. If any check fails it stops and removes the file rather than leaving half an image on your device.
4
Finish the install on the device
The file is on the device, but the device has not installed it yet.
1. Eject the drive properly (macOS: drag to the Bin or press ⌘E; Windows: "Safely remove hardware"). Do not just yank the cable.
2. Unplug the USB cable.
3. Wait about ten seconds. The light will blink while the bootloader installs the firmware, then the device reboots on its own.
How to check it worked: plug the FlySight back in normally and look in the FW folder. If APP.SFB is gone, the bootloader consumed it and the install is done. If the file is still sitting there, the device was not in bootloader mode — go back to step 2 and watch for the orange light.

The version line in flysight.txt is written by the firmware itself and is not always a reliable way to tell which build is running. The disappearance of FW/APP.SFB is the dependable signal.

// PATH B

IDENTIFY & DOWNLOAD

This path works in every browser, on any computer. You show the page your flysight.txt, it works out which firmware you need, and hands it to you already named APP.SFB. You copy it across yourself. It is exactly as safe as the one-click path — it just makes you do the last step by hand.

Drop flysight.txt here or click to choose it

Plug the FlySight in normally, open its drive, and take the file called flysight.txt from the top level. The file is read in your browser and is not sent anywhere.

// PATH C

WHICH FILE DO I NEED?

Open flysight.txt from the FlySight's drive in any text editor and find the line that starts with Pubkey_X:. Match it below. The first eight characters are enough to tell them apart.

Batch	`Pubkey_X` starts with	File	SHA-256
Loading the firmware list…

Firmware version —. Every file is the same firmware; they differ only in which batch of devices they will decrypt on. If your Pubkey_X is not in this table, stop — none of these files can install on your device, and trying the wrong one is a waste of time rather than a way to find out.

// THE SMALL PRINT THAT ISN'T SMALL

WHAT THIS PAGE WILL AND WON'T DO

WON'T TOUCH ANYTHING ELSE

The only file it creates on your device is FW/APP.SFB. It also deletes macOS ._ leftovers and abandoned .crswap scratch files inside that same FW folder, because they are junk the bootloader has to scan past. Your logs, your config and everything else are never opened.

WON'T GUESS YOUR BATCH

If your device reports a Pubkey_X this page does not recognise, it says so and stops. The firmware is encrypted per batch, so a near miss is not a near miss — it simply will not install, and pretending otherwise would just waste your evening.

CHECKS BEFORE AND AFTER

The download must start with the four bytes SFU1, be exactly the published size, and match the published SHA-256. After writing, the file is read back off the device and hashed again. A mismatch at any point aborts and removes the file rather than leaving something half-written.

WON'T UPLOAD ANYTHING

flysight.txt is read in the browser and never sent anywhere. There is no analytics on this page, no account, and no server that learns your device ID. The firmware itself is served from this site, not fetched from somewhere else.

CAN'T DO IT WIRELESSLY

Not over Bluetooth and not over USB-as-a-device: the FlySight bootloader presents itself as an ordinary disk, and browsers deliberately refuse to talk to storage devices directly. A file on a drive really is the mechanism, not a workaround.

IF SOMETHING GOES WRONG

A failed copy is not a bricked device. The bootloader stays put and keeps accepting files, so you can always try again — or go back to the official firmware the same way. The console above records what happened, so you have something concrete to report.