HN Debrief

Reviving a four year old reMarkable 2

  • Hardware
  • Open Source
  • Developer Tools
  • Consumer Tech

The post is a hands-on recovery guide for a reMarkable 2 tablet that had been left in a drawer for years and could no longer update itself. The fix leaned on features most consumer devices hide or block: SSH access over USB, a normal Linux userspace, systemd services, and a built-in web interface for moving files on and off the device. A few commenters noted that parts of the walkthrough were more manual than necessary, because reMarkable now has a support page for the clock-related update failure and some of the needed settings are exposed in the UI.

If you buy specialized hardware, openness can be the difference between a recoverable annoyance and a dead device. For teams shipping connected products, the bar is higher than "hackable if needed". Basic offline recovery and long-idle update paths need to work without shell access.

Discussion mood

Mixed but engaged. People like the hardware, the writing experience, and the fact that the device is unusually open for a consumer tablet. The frustration is aimed at the idea that a four-year-old device can get stuck on updates, plus long-running complaints about the stock software, cloud sync, and file management.

Key insights

  1. 01

    Openness is the product's real safety net

    What makes this story land well is not that the bug exists, but that the owner could fix it without exploiting anything. SSH over USB, root access, systemd, and documented developer hooks turn a stranded appliance into a maintainable Linux box. One commenter corrected that the friendly guide is community-run, not official, but that still reinforces the point. There is enough openness around the device that buyers treat hackability itself as a longevity feature.

    If you ship hardware, documented local access paths buy real goodwill and extend product life. If you buy hardware for a team or niche workflow, treat recoverability as a feature you can evaluate up front.

      Attribution:
    • GCUMstlyHarmls #1
    • zeeZ #1
    • Tarsul #1
    • tremguy #1
  2. 02

    Third-party tools have become the real maintenance layer

    Owners are no longer talking about tweaks for fun. They are naming specific tools like reManager and codexctl as the practical way to update firmware, install KoReader, move large files, and avoid broken assumptions in older modding stacks like Toltec. That shifts the story from "nice hacker community" to "community software is filling gaps in the vendor workflow."

    When power users standardize on unofficial management tools, that is a signal that core product operations are underspecified or unreliable. Watch for this pattern in your own product community before it hardens into the default path.

      Attribution:
    • graceful6800 #1
    • rvz #1
    • haskman #1 #2
    • wingmanjd #1
  3. 03

    The software pain is mostly about document handling

    The sharpest complaints were not about note taking itself. They were about the surrounding workflow. People called out a buggy web uploader, file size limits, awkward local transfer, weak library organization, and unreliable cloud behavior ranging from sync pain to alleged note deletion and restoration errors. The device seems to satisfy the narrow act of writing while disappointing users who expect sane document operations around it.

    For focused devices, the core interaction is not enough. The ingest, sync, backup, and retrieval path will dominate whether people trust the product in real work.

      Attribution:
    • haskman #1
    • davisr #1 #2
    • cyberax #1
  4. 04

    Cheap secondhand e-ink hardware is fertile ground

    Several commenters pointed out that used reMarkable 2 units are easy to find because many buyers expected an Android-style tablet and bounced off the intentionally narrow feature set. That mismatch creates a healthy resale market, which hobbyists are then using as a low-cost Linux e-ink platform for KoReader, custom SDKs on Kobo, RSS reading, audiobooks, and even browser experiments. The bigger idea is that underpowered-looking hardware can still do a lot when the software stays lean.

    There is an opening for products and tools aimed at repurposing discarded single-purpose hardware. If your software can target cheap e-ink Linux devices, you may be building on a growing surplus market rather than a niche curiosity.

      Attribution:
    • gruturo #1
    • tomduncalf #1
    • kadoban #1
    • thepoet #1
    • dismalaf #1

Against the grain

  1. 01

    This was recoverable without much hacking

    A few owners pushed back on the dramatic framing. They said the web interface can be enabled from settings, reMarkable has published support steps for the clock-related update bug, and the device still receives updates. In that reading, the blog post exposed a rough edge, not abandonment, and a reboot or official recovery path may have solved much of it.

    Do not infer product neglect from a recovery blog alone. Before escalating an issue into a platform judgment, check whether the vendor has since documented or fixed the failure mode.

      Attribution:
    • reticulated #1 #2
    • tremguy #1 #2
    • Tarsul #1
  2. 02

    Minimalism is a feature, not negligence

    Some commenters rejected the idea that reMarkable should become a general-purpose tablet or even a strong ereader. They argued the point of the device is focused content creation with low distraction, and that adding broader use cases would trade away the experience buyers actually wanted. From that angle, complaints about missing browser or reader features are often asking the product to be something else.

    Specialized products should be judged first against their primary job. If your strategy depends on extreme focus, be explicit about what you are refusing to optimize so customers self-select correctly.

      Attribution:
    • tomduncalf #1
    • turtlebits #1
    • reticulated #1

In plain english

e-ink ↩
A low-power display technology that mimics paper and is commonly used in e-readers and note tablets.
firmware ↩
The low-level software built into a device that controls its hardware and core functions.
KoReader ↩
An open-source reading application commonly installed on e-ink devices as an alternative to the stock reading software.
Linux ↩
An open-source operating system family widely used in servers, embedded devices, and many consumer products.
RSS ↩
Really Simple Syndication, a feed format used to subscribe to updates from websites and blogs.
SSH ↩
Secure Shell, a standard way to log into and control another computer over a network or direct connection using a command line.
systemd ↩
A widely used Linux system component that starts, stops, and supervises services and background processes.
Toltec ↩
A package repository and tooling ecosystem for installing community software on reMarkable tablets.
USB ↩
Universal Serial Bus, the common cable and connector standard used to connect and power devices.

Reference links

Recovery and device management tools

Alternate software and platform projects

  • Cobalt
    Open-source Kobo app platform described as a way to build and deploy apps on e-ink hardware.
  • NickelMenu
    Kobo customization tool mentioned as a useful complement to Cobalt.

Market and user reports

Official product information