You bought a reMarkable 2 because you wanted to escape notifications, to write without distraction, to feel like you were using paper but with the power of digital. And for a while, it worked. Then one day, the sync stops. The updates stop. The device becomes a beautiful, expensive paperweight.
That’s not a bug. That’s a business model.
The moment a company stops supporting your device, they reclaim ownership — even if you paid for it.
A developer named Oskar recently wrote about reviving his four-year-old reMarkable 2. The hardware was pristine. The e-ink display still crisp. But the software had aged out. The solution? A community project called codexctl that lets you bypass the official update server and install the latest firmware manually. It’s a jailbreak for a note-taking tablet.
This is absurd. A device designed for focused, long-term use is thrown away not because it can’t function, but because the manufacturer decided it’s time for you to buy a new one. The reMarkable 2 is a perfect example of planned obsolescence — except the hardware is still perfectly capable. The obsolescence is entirely artificial.
Paper and pencil never need a firmware update. They never run out of support. They never brick. That’s the real benchmark.
And here’s the irony: the community fix is actually better than the official one. codexctl gives you control. The company’s update process is a black box. The community’s is open. So who really owns your device?
If you have an old reMarkable, don’t throw it away. Hack it. Demand right to repair. And remember: the enemy of longevity isn’t time — it’s the business model.
FAQ
Q: Isn't this just a niche problem for reMarkable users?
A: No. It's a universal issue. Every device with a closed firmware — from smartphones to smart home gadgets — faces the same risk. The reMarkable is just a vivid example because it's a simple device that should last.
Q: Why not just use paper and pencil?
A: That's the point. Paper is eternal. But digital convenience has a hidden cost: dependence on the manufacturer. If you want the best of both worlds, demand open-source firmware and right-to-repair.
Q: Is codexctl safe to use?
A: It's as safe as any community tool. The code is open-source, auditable, and actively maintained. It's far safer than trusting a company that can arbitrarily cut off support. The real risk is not using it.