BOOX Picco Ships a Hidden Custom CrossPoint Fork in 2026

On September 16, 2026, Onyx International put the BOOX Picco on sale for $99 — a 3.97-inch, 58-gram pocket reader positioned as a "companion device" rather than a primary e-reader. It is a genuinely interesting piece of hardware at a genuinely interesting price. It is also the clearest example yet of a problem that has been quietly building in the budget e-reader market all year: you no longer know what operating system you are buying.

Here is the specific wrinkle. When reviewers asked what software the Picco runs, Onyx would not say. Good e-Reader reported on September 16, 2026 that a site which received the firmware identified it as a custom fork of CrossPoint — not an official CrossPoint release. Onyx separately confirmed only that the Picco runs on the ESP32 platform. Then, in the same breath, the company gave customers this advice:

"We are aware that products with similar hardware configurations on the market support installing third-party firmware. However, we do not recommend attempting this. Modifying the firmware or flashing third-party firmware may not only damage your device, but also void its warranty."

Read those two statements together and the tension is hard to miss. Onyx is shipping a community firmware project's code inside a commercial product, keeping the details undisclosed, and simultaneously warning buyers not to touch the very ecosystem the code came from. If that sounds like a technicality, it is not — it changes what you can expect from the device you just paid for, and it tells you something useful about how the budget e-reader market works right now.

What CrossPoint actually is

CrossPoint is not an obscure hobby project. As of September 18, 2026, the crosspoint-reader/crosspoint-reader repository on GitHub reports 7,911 stars, 1,775 forks and 549 open issues, with the most recent commit pushed on September 17, 2026 — the day before this article. It is written in C, licensed under MIT, and was created in December 2025. In under ten months it has become the de facto community firmware for small ESP32-based e-readers.

Its release cadence tells the same story. The project shipped version 1.6.0 on September 5, 2026, with a 1.6.5 release candidate appearing on September 14, 2026. The 1.6.x line added support for the Xteink X4 Pro and M5Stack PaperMono, transparent sleep overlays, a Reading Night Mode toggle, and a light-sleep idle plus refresh downclock the project measured at roughly 3.2x active reading time on the Xteink X3. The 1.6.5 release candidate went further, adding a searchable Recent Books library view, official support for the ESP32-S3-based Xteink X4 Classic, more precise KOSync EPUB reading positions, and reduced font and EPUB memory pressure.

That is what active open-source maintainership looks like: frequent releases, public issue trackers, real hardware support landing within weeks of a device shipping. We covered the 1.6.0 release in detail in our CrossPoint 1.6 breakdown, and the broader picture of ESP32 readers in our FreeInk ecosystem guide.

The fork question: why "based on CrossPoint" is not the same as CrossPoint

An MIT license is permissive. It explicitly allows a company to take CrossPoint's code, modify it, ship it in a closed product, and never publish the changes. That is legal, and it is common. But it produces three concrete consequences for a buyer that are worth understanding before you spend $99.

1. You get the version the vendor froze, not the version the community maintains

CrossPoint shipped 1.6.0 on September 5 and a 1.6.5 release candidate on September 14. If the Picco's firmware was forked at some earlier point, the device you receive may be missing the fixes that landed in between — including the EPUB memory-pressure reduction and the KOSync position precision work in 1.6.5. Those are not cosmetic. Memory pressure is what determines whether a large EPUB opens cleanly or crashes on a device with limited RAM.

2. Security and bug fixes do not reach your device automatically

An official CrossPoint release can be flashed by the user the day it ships. A vendor fork can only be updated when the vendor chooses to ship an update. If a book-rendering bug or a file-transfer safety issue is fixed upstream, nothing obliges the fork's maintainer to port it. The 1.6.x release notes specifically mention improving "web file-transfer safety" — exactly the kind of fix you want to actually receive.

3. The warranty warning cuts both ways

Onyx's statement that flashing third-party firmware "may void its warranty" is a normal vendor position. But it sits awkwardly next to a device that already contains forked community code. A buyer asking whether they can install the official CrossPoint release is not asking for something exotic — they are asking whether they can move from an undocumented fork to the documented upstream project. The answer, per Onyx's own statement, is: we would rather you did not.

Picco at a glance: what $99 buys you

For completeness, here is the hardware itself. These are the specifications Onyx has published, cross-checked against Good e-Reader's September 16 coverage and the device's own listing.

Specification	BOOX Picco
Price	$99.00 USD
Display	3.97-inch monochrome E Ink, 480 × 800, 235 PPI
Front light	Warm and cool, switchable via button
Platform	ESP32 (confirmed by Onyx); exact SoC undisclosed
Firmware	Custom fork of CrossPoint, per third-party firmware analysis — not an official release
Storage	16 GB card included, expandable to 2 TB (all data and ebooks live on the card)
Battery	920 mAh
Dimensions	105.5 × 62 × 5.5 mm, 58 g
Connectivity	Wi-Fi, Bluetooth, USB-C charging
File transfer	BOOX Tiles app or web transfer
Ebook formats	EPUB, MOBI, AZW3, AZW, AZW5, FB2, FB2.ZIP, FB3, FBZ, TXT, PDB, PRC, RTF, HTML, XHTML, HTM, CHM
Bundled apps	Pomodoro, Todo, Countdown

Two things stand out. First, the format list is unusually broad for a device this cheap — EPUB, FB2, RTF, CHM and the older MOBI/AZW family are all handled natively. Second, the storage model is card-first: the internal 16 GB is a bundled card, and everything you own lives on it. That is a real advantage for portability (pull the card, move the library) and a real risk if the card fails without a backup.

The $79-to-$99 pocket-reader price war

The Picco did not arrive in a vacuum. It landed directly on top of Xteink, whose hardware is the reference platform CrossPoint was originally written for. The Xteink X4 Classic, also known as the X4 V2, arrived in September 2026 at $79 — roughly 68 grams, 4.9 mm thin, and built around an ESP32-S3 with a paper-feel E-Ink display. The Xteink X4 Pro brought a 4.3-inch 220 PPI touchscreen, a proper front light, and a 5.98 mm body, and became available on Amazon in early September 2026 — a meaningful change for anyone who cares about returns, since Xteink's own store has a reputation for not accepting them.

So the sub-$100 tier now has at least three credible entrants, and the differentiator is no longer screen size or battery life. It is what software you can run. A $79 Xteink that runs the official CrossPoint build — flashable, documented, actively maintained, and updated by the community the same day a release ships — and a $99 Picco that runs an undisclosed fork are not the same product, even though the spec sheets look comparable.

The deeper pattern: firmware transparency in 2026

This is not an isolated incident. The e-reader market has spent 2026 bifurcating into two camps, and the split is now visible at every price point.

On one side are the open platforms. CrossPoint and its ecosystem — see our FreeInk guide — publish their source, license permissively, maintain a public issue tracker, and let users flash whatever they want. KOReader, which we covered in our KOReader ZEN UI article, is the other major open reading system, and its device support list is public and verifiable. The open EPUB 3.4 specification work sits on the same standards-based side of the line.

On the other side are the vertically integrated vendors. Onyx's own Palma 3, launched September 15, 2026 at $339.99 with an anodized aluminum frame and active stylus support, is a fully closed Android-based product. That is a legitimate choice — Android buys you the Google Play Store and real apps. But it is a different contract with the buyer than an ESP32 reader running MIT-licensed firmware.

The complication arises when a closed vendor borrows open code and does not say so. That is what makes the Picco story worth more than a product announcement. The buyer's mental model — "this is a cheap closed reader from a big brand" — does not match the technical reality — "this is community firmware, forked and frozen, with the warranty warning attached."

A practical pre-purchase checklist for open-firmware readers

If you are shopping in the $79–$120 range and the ability to run the firmware you want matters to you, ask these questions before you buy. They are quick, and the answers are almost always discoverable.

1. Does the vendor name the OS and the SoC? A vendor that will not tell you the processor is usually also not telling you other things. "Android" or "ESP32" plus a specific chip is a good answer. "Undisclosed" is a warning sign.
2. Is the firmware an official build or a fork? Check the vendor's support site and the upstream project's hardware support list. If the vendor's device is not on the upstream list, assume a fork.
3. Does the vendor publish firmware updates? Look for a dated changelog. If the last entry is the launch date, the fork is frozen.
4. What does the warranty say about third-party firmware? A flat "void" is common. Understand what you give up.
5. Where does your library physically live? Card-first storage is flexible but needs its own backup discipline. Copy the card to your computer before you rely on it.
6. Does it read your actual files? Verify the format list covers what you own. The Picco's list is broad; not every cheap reader's is.

What this means for your EPUB library

Here is the part that matters regardless of which device you choose. A reader is a viewing window; your EPUB files are the asset. Every one of the devices in this story — Picco, Xteink X4 Classic, Xteink X4 Pro, Palma 3 — is replaceable. Your library is not.

That argues for keeping your books as plain, standards-compliant EPUB files with clean metadata, rather than in any vendor's cloud or proprietary container. It also argues for card and folder hygiene: if a device stores everything on a bundled microSD card, that card is a single point of failure you should mirror. If you want to clean up metadata or normalise a messy library, tools like Calibre can do it locally — we cover the metadata workflow in our Calibre metadata guide.

The Picco's own format list is a reminder that buying for format breadth is cheap insurance. A reader that opens EPUB, FB2, RTF and CHM will still open your files in five years, whatever happens to the vendor's firmware roadmap.

The bottom line

The BOOX Picco is a capable $99 pocket reader with a broad format list and a genuinely portable form factor. It is also shipping an undisclosed fork of an MIT-licensed community project while telling buyers not to flash third-party firmware — and those two facts belong in the same sentence whenever the device is discussed.

None of this makes the Picco a bad purchase. It makes it a purchase you should make with clear eyes. If you want a cheap, locked-down companion reader and you accept the firmware you get on day one, $99 is fair. If what you actually want is a device that stays current with an active project, the $79 Xteink X4 Classic running official CrossPoint is the more honest deal — and the upstream community, with 7,911 stars and a release less than two weeks old, is the thing keeping it that way.