downloads · firmware and app
Install ExplorInk on your own reader
Two halves: the app on the phone, free on Google Play, and alpha firmware on the e-ink reader, which takes a desktop and a USB cable.
The phone app, right now
ExplorInk GPS is on Google Play. Free, no account, no ads. It sends your position to the reader, brings the missing map squares and records the ride. Android 12 or newer.
Browser flasher What you need Firmware Phone app When it goes wrong
What you need
- An unlocked Xteink reader: the plain X4, an X3, or an X4 Pro. Or a LilyGo T5S3, which LilyGo sells rather than Xteink, see below. Which build you take depends on which one, see the device table below.
- A cable that carries data, not a charge-only one. The plain X4 and the LilyGo T5 S3 Pro both have a USB-C socket and take an ordinary cable. The X3 and the X4 Pro have no socket at all: data comes out on the pogo pins, so you need the USB-C-to-pogo dongle that ships in the box.
- A microSD card, FAT32 formatted. It can be empty: the firmware creates its own directory the first time a map square arrives.
- A computer with Python 3 for the flashing tool. Linux, macOS or Windows.
- An Android phone, version 12 or newer. The Xteink readers have no GPS receiver, so the phone is the receiver. The LilyGo T5 S3 Pro has its own.
Which devices this firmware runs on
| Device | Chip | This build |
|---|---|---|
| Xteink X4 (plain) | ESP32-C3 | Verified on real hardware until 22 Aug 2026, when our X4 was lost. 0.2.3 has not run on one. It is the same binary as the X3’s, which has. |
| Xteink X3 | ESP32-C3 | Compiled in, and the firmware probes for the X3’s own fuel gauge and clock. This download, 0.2.3, flashed and verified on a real X3 on 5 Nov 2026: it boots, mounts the SD card, enters the map and draws it with 1,213 ways and no missing tiles. The same board also pulled this release down over the air from the device itself. The button hint boxes are still cut off by the bottom edge of that panel, so the layout still needs work. |
| Xteink X4 Pro | ESP32-S3 | Its own build, 0.2.3, released 5 Nov 2026. Different chip family, so not the files above: take the X4 Pro download in step 1. Run on a real X4 Pro the same day: boot, the card mounted, the map drawn with 6,980 ways and none dropped. The earlier 0.2.1-alpha build is what was walked through on the device’s own buttons and glass, including the double-tap touch lock and the frontlight sliders. The device page names what is still untested. |
| LilyGo T5 S3 Pro | ESP32-S3 | Its own build, 0.2.3, released 5 Nov 2026. Not an Xteink product: the LilyGo T5S3, which we use to validate the firmware on different hardware. Same chip family as the X4 Pro, but its own images, see step 1. Verified on a real unit the same day, with the published binary, as far as boot, the settings screens and the map activity opening; the card in that board holds no tiles for the ground it was pointed at, so this round did not re-check that the map draws there. 0.2.2 did, on 1 Nov 2026: a town at the closest zoom rung with three street names, 1,745 ways and none dropped. It is also the only board with a receiver, so it is the only one that shows the satellite screen, and the only one with a LoRa radio, so group positions over LoRa exist there and nowhere else. The radio ships switched off. 0.2.2 was the first build for this board taken from the shared line rather than its own branch, and 0.2.3 continues that, so it carries everything the other devices have. |
Two facts that decide whether you can flash at all. The plain X4 is the only device in the line with a USB-C port: the X3 and the X4 Pro carry USB on their pogo pins, so flashing them needs the vendor’s USB-C-to-pogo dongle and there is no substitute for it. And the plain X4 was discontinued by Xteink on 2026-08-12, so the unit on sale today is usually a marketplace one.
Units sold locked, mostly the China-market ones on AliExpress, do not enumerate over USB at all: the computer sees no serial port, so there is nothing to flash. CrossPoint, the project this firmware forks, ships an unlock tool for that case: the CrossPoint unlock tool. We have not run it, so treat it as a pointer, not a recommendation.
The one thing to get right: back up first
Flashing writes over Xteink’s own reader firmware. There is no menu entry, no recovery partition and no vendor download that puts it back. What puts it back is a copy of the flash you made before you wrote anything.
So the first command reads the whole 16 MB flash into a file on your computer. It takes a few minutes, and on an X4 Pro about twenty, with the screen frozen for all of it. Keep that file: it is the reader you paid for, and it is the difference between an experiment and a one-way door. Our firmware also lays out the flash differently from Xteink’s, so the file is not a convenience, it is the only copy of the original layout that will ever exist.
python3 -m pip install esptool
esptool -p /dev/ttyACM0 --no-stub read-flash 0 0x1000000 xteink-stock-backup.bin
The --no-stub is not optional here. Without it the read dies
partway with A fatal error occurred: Packet content transfer stopped. Measured
on an X4 Pro on 10 Sep 2026: it stopped at 15 percent after 21 seconds, and with the flag it
read all 16 MB in 18 minutes. The flag tells esptool to talk to the chip’s built-in ROM
loader instead of uploading its own faster helper, which is what does not survive a transfer
this long. The 3.9 MB firmware write in step 1 does use the stub and succeeds, so the flag is
not needed there. Why the long read fails and that write does not is not settled: those two
differ in size and in direction at once, and only the read has been tested.
Check that the command finished. When the read fails it still leaves a file
called xteink-stock-backup.bin behind, holding however much arrived. It is not a
backup. The finished file is exactly 16,777,216 bytes: ls -l on Linux and macOS,
dir on Windows. A short one means run it again, and do not go on to step 1 until
the size is right, because step 1 is what makes the original unrecoverable.
Port names: /dev/ttyACM0 on Linux, /dev/cu.usbmodem* on macOS,
COM5 or similar on Windows. On Linux, confirm you have the reader and not
another device: udevadm info -q property -n /dev/ttyACM0 | grep ID_VENDOR_ID
answers 303a for this chip. Older esptool releases spell the commands with
underscores (read_flash, write_flash).
Putting it back later is the same tool, the other direction, and the same flag for the same
reason:
esptool -p /dev/ttyACM0 --no-stub write-flash 0x0 xteink-stock-backup.bin. That
one has been run: an X4 Pro was restored from its own backup on 9 Sep 2026 and read back
byte for byte identical afterwards.
Step 1: the firmware
Three downloads. The plain X4 and the X3 share the C3 build. The X4 Pro and the T5 S3 Pro each have their own S3 build. Nothing is interchangeable: a C3 image on an S3 does not boot, and one S3 board’s image does not drive the other’s panel.
The offsets below are not read off a datasheet. Each one was checked against that model’s own 16 MB flash dump, taken off a real device before anything of ours was written to it. Getting this wrong bricks a reader, so it is checked per model rather than copied across.
Already running 0.2.2 or older? This one has to go over the cable, once. Those builds ask GitHub for the latest release, and that endpoint skips pre-releases, which every build of ours is. So the reader looks, finds nothing, and says there is no update. That is the bug 0.2.3 fixes, and a reader cannot fix it before it has the fix. From 0.2.3 onward it finds its own updates and you will not need the cable again.
The browser flasher does everything below for you: it picks the 0.2.3 images for the device it finds, writes them at these offsets, and takes the backup first. Take the files here if you want the command line, or if your browser has no Web Serial.
Xteink X4 and X3, the ESP32-C3 build
Firmware 0.2.3, all four files
- bootloader.bin, 18 kB, goes to
0x0 - partitions.bin, 3 kB, goes to
0x8000 - boot_app0.bin, 8 kB, goes to
0xe000 - firmware.bin, 4.1 MB, goes to
0x10000
esptool -p /dev/ttyACM0 write-flash \
0x0 explorink-0.2.3-esp32c3-bootloader.bin \
0x8000 explorink-0.2.3-esp32c3-partitions.bin \
0xe000 explorink-0.2.3-esp32c3-boot_app0.bin \
0x10000 explorink-0.2.3-esp32c3-firmware.bin
Checksums are published next to the files as SHA256SUMS-firmware.txt.
This exact image was flashed on a real X3 on 1 Nov 2026 and hashed after the
upload: it boots, mounts the card, enters the map and draws Modra at the closest
rung with street names. It has not run on a real X4, because ours was lost on
22 Aug 2026. The binary is the same for both boards. The button hint boxes are
still cut off by the panel edge on the X3. Builds before 0.2.1-alpha left the BLE
position out of the map, so a phone could never send them a fix: replace them.
A card with v3 tiles on it will not work with this firmware, see step 2.
Xteink X4 Pro, the ESP32-S3 build
Four files, the same shape as the C3 set. boot_app0.bin is eight
kilobytes that tell the chip which of its two application slots to boot. Your reader
almost certainly already points at the right one, and writing it costs a second and
removes the case where the flash succeeds and the device still starts
Xteink’s firmware.
Firmware 0.2.3 for X4 Pro, all four files
- bootloader.bin, 18 kB, goes to
0x0 - partitions.bin, 3 kB, goes to
0x8000 - boot_app0.bin, 8 kB, goes to
0xe000 - firmware.bin, 3.9 MB, goes to
0x10000
esptool -p /dev/ttyACM0 --chip esp32s3 write-flash \
0x0 explorink-0.2.3-x4pro-esp32s3-bootloader.bin \
0x8000 explorink-0.2.3-x4pro-esp32s3-partitions.bin \
0xe000 explorink-0.2.3-x4pro-esp32s3-boot_app0.bin \
0x10000 explorink-0.2.3-x4pro-esp32s3-firmware.bin
Plug the pogo dongle in first: without it the X4 Pro shows up as nothing at all.
This exact image ran on a real X4 Pro on 1 Nov 2026, hashed after the upload: it
boots, mounts the card and draws the map with street names. This whole page was walked on
10 Sep 2026 on an X4 Pro put back to Xteink’s own firmware first, using
nothing but what is written here: the four files downloaded from the link above, their
checksums checked, the backup taken, and this exact command run. It booted into
ExplorInk. The one thing that had to change on this page as a result is the
--no-stub in the backup command above. That walk was done with the
previous build; the files have moved on, the steps have not.
0.2.3 is a development build, and it carries the bench commands. Anyone holding the reader with a USB cable can write into its stored settings, including ones that spend mobile data or paint your exact position on the panel, and the change persists to the card. 0.2.1-alpha for the X4 Pro had removed them; 0.2.3 brings them back on every board. We track it as T-241. What is still untested is on the device page: this release says more works than the last one, not that the reader is finished.
LilyGo T5 S3 Pro, the ESP32-S3 build
This is not an Xteink reader: it is the LilyGo T5S3, which we flash to validate the firmware on hardware other than Xteink’s. It has its own USB-C socket, so no pogo dongle is needed here, and the offsets are the same shape as the X4 Pro’s.
Firmware 0.2.3 for the T5 S3 Pro, all four files
- bootloader.bin, 18 kB, goes to
0x0 - partitions.bin, 3 kB, goes to
0x8000 - boot_app0.bin, 8 kB, goes to
0xe000 - firmware.bin, 4.1 MB, goes to
0x10000
esptool -p /dev/ttyACM0 --chip esp32s3 write-flash \
0x0 explorink-0.2.3-t5s3pro-esp32s3-bootloader.bin \
0x8000 explorink-0.2.3-t5s3pro-esp32s3-partitions.bin \
0xe000 explorink-0.2.3-t5s3pro-esp32s3-boot_app0.bin \
0x10000 explorink-0.2.3-t5s3pro-esp32s3-firmware.bin
0.2.3 comes off the shared line, the same commit as the other two builds, see the device page. This exact image was verified on a real unit on 1 Nov 2026, hashed after the upload: it boots, mounts the card and draws three street names at the closest rung.
The reader reboots into ExplorInk on its own. You get a home screen with Explore at the top, and Explore is the map. With no card and no tiles the map has nothing to draw yet, which is what step 2 is for.
Step 2: the card, and where the map comes from
Put a FAT32 microSD card in. It can be blank. Map squares arrive over Bluetooth from the phone: the reader lists the squares it does not have, the app fetches them from our tile server and pushes them across, and the firmware creates the directories as they land.
Coverage is not the whole world yet, and with the v4 tile format it starts from zero: nothing carries over from what was built under v3. What is built today is visible on the live coverage map. Ride onto ground that has no tiles and the reader draws a hatched square instead of a map, and that miss is logged on the server, which builds the area and publishes it, usually within minutes. That works anywhere in the world since 29 August 2026: the builder used to refuse everything outside a box around Europe, and the first owner to write to us was outside it. What still bounds it is throughput, not geography. The builder takes the ten most-asked-for squares at a time and caps the day, so a large area nobody has ever ridden fills in over several passes rather than at once.
Street names need tiles built after 1 Nov 2026. Tiles already on your card draw normally and simply have no names in them: nothing looks broken. The tile server rebuilds published areas on its own schedule, so names appear when the reader next downloads that ground. A card from before 0.2.0-alpha holds v3 tiles, which this firmware cannot read: wipe its map folder and let the reader fetch its tiles again over Bluetooth.
How the tiles are built, and why they are a custom format rather than an existing one.
Step 3: the phone app
ExplorInk GPS, Android 12 or newer, on Google Play. It sends the position, brings the missing map squares, queues a whole area before a trip, records the ride and manages the reader’s pins.
Version 0.3.14, published by Comsultia, s.r.o., free, no ads and no in-app purchases. It installs and updates like any other app, which is the whole point of it being there: no unknown-sources prompt, no Play Protect warning, and updates arrive on their own.
If you already sideloaded an APK, uninstall it first. Android refuses an update across a different signing key, and the Play copy is signed by Google rather than by us, because an app published as a bundle is signed on Google’s side. Uninstalling loses nothing the reader needs: the pairing lives in Android’s companion-device record, and recordings are files you can copy out first.
The APK stays, for anyone who cannot use Play. It lives on the releases page. From now on it carries our own release key instead of the shared Android debug key the earlier builds used, so one APK can at least update the next. What it can never do is cross over: a phone on the Play copy cannot update from an APK, and a phone on an APK cannot update from Play. Pick one route per phone.
On first launch it asks for nearby devices (Bluetooth scan and connect), location, and notifications, which is the foreground service that keeps the link alive. Then you pair with one reader once, through Android’s own companion device dialog. After that the operating system watches for that reader: open Explore on the reader and the app wakes up on its own, with the phone locked and nothing tapped.
When it goes wrong
| What you see | What it is |
|---|---|
Invalid head of packet (0x0D) |
Almost always the wrong serial port, not a bad cable. A phone and the reader both show up as /dev/ttyACM* and they swap places. Check the vendor id is 303a. |
| No serial port appears at all | A charge-only cable, or a locked unit. See the unlock tool above. On an X3 or an X4 Pro it is usually neither: those have no USB socket, so without the pogo dongle there is nothing for the computer to find. |
| Explore opens but the map is blank or hatched | No tiles for that place yet. Check the card is in, then the coverage map. |
| The reader is frozen after flashing | Plug it in and write the firmware again, or write your stock backup back. The chip’s own boot ROM answers the flashing tool even when the firmware on top of it is hung, which is why the backup is always reachable. |
| Play Protect blocks the app | Expected for a self-signed APK. More details, then install anyway. |
| The app installs but never connects | Open Explore on the reader first. The link is started from the map screen, and a force-stopped app cannot be woken by anything. |
What is verified, and what is not
Verified on a real X4 with builds up to August 2026: the map render off the card, place names, track-up, a route overlay, pins, the phone link and tile transfer over Bluetooth. A number on a device page names the device it came from.
Not verified, said plainly:
- A real X3, past first boot and a map with BLE. 0.2.3 was flashed and verified on one on 5 Nov 2026: it boots, enters the map and draws it, and it fetched and installed this release over the air by itself. The BLE link was last driven from a phone on 0.2.2, 1 Nov 2026. The fuel gauge has not been read, the sunlight refresh has not been tested, and the button hints sit in the wrong place on that screen.
- The X4 Pro, past the first day. 0.2.3 ran on a real unit on 5 Nov 2026 and drew the map. The first build, 9 Sep 2026, rendered a map frame in 1,183 ms, and touch, the home key and the frontlight all answered. Still not answered: whether the frontlight flashes at boot, the frontlight PWM frequency on this board, and what the heap does over a long session. The device page has the numbers.
- Whether an X4 Pro can ship with flashing locked. Some marketplace X4 units do. Ours is not locked, and one device is not a survey.
- This exact write onto a stock X3 or X4. The X4 Pro was walked from stock on 10 Sep 2026 with an earlier build, see above. The X3 has only been flashed over our own firmware. The offsets are confirmed against each model’s own flash dump.
- Battery life for a full ride. Ride draws of 17 to 46 mA are measured, the runtime we quote comes from percent per hour on the reader’s own gauge, and nobody has run a cell down on a bench.
Security, before you carry it
The reader answers commands over Bluetooth with no pairing, no bonding and no authentication, and the same commands over the USB serial port. Anyone in radio range can ask it where it is. A lost or stolen reader is not private, and this is a known open item rather than a solved one. Do not put anything on it you would mind a stranger reading.
The one exception is the document wallet: what the phone writes to the card is encrypted, and the reader only ever holds ciphertext plus the key material it needs to show a page.
No account, no telemetry from the device
There is no login and no cloud service. The reader talks to your phone. The phone talks to a static tile server, which sees a request for a map square and nothing else. Your recordings are files on your phone.
Both halves are open source: the firmware and the Android app. There is also a browser flasher: the same four images written over USB from a Chromium desktop browser, with the stock backup taken first and no command line at all.
The questions people ask before trying it · what landed when, with the measurements