HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ddvk
remarkable2-recovery
OPEN SOURCE2020–2026
ddvk / remarkable2-recovery

remarkable2-recovery

recovery tools for reMarkable 2

4Distinct people
4Mentions
0Explicit recommenders
294GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

recovery tools for reMarkable 2

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2020-11-18 18:25:45 UTC to 2026-02-05 05:30:34 UTC.

0122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

4 sources
SSH in and you have access to basically everything. The stock setup has two partitions for the OS (it toggles between them when you update, or toggles back if it fails to boot a few times) so you can: Dual boot (disable updates and install any two you like): https://remarkable.guide/tech/dualboot.html Some lower level details here: https://github.com/ddvk/remarkable-hacks/issues/304 And installing a specific release is largely automated: https://github.com/ddvk/remarkable-update Last time I did it, I just did it manually - back up the OS version you want over ssh, then restore it whenever you want (on the non-active partition). And screwed it up the first time, and had to do a recovery: https://github.com/ddvk/remarkable2-recovery (requires using the contact pads on the spine for USB access - not too hard to solder up a pogo pin thing, bu
Read the rest
t might take some time to get the parts). So I'd recommend the automated way, though I haven't tried it yet :) There's a (single) relatively active discord server if you want specific Q&As with other people too, or to double check whatever the current recommendations are (probably do that, as I'm somewhat out of date): https://discord.com/invite/nQ6nHwfDfc And do definitely back up your data partition before making any major version movements tho, in case something doesn't work right and you need to roll back. I forget if/when that's necessary, but it's a good safety net just in case. And <8GB isn't much to store just in case.
In Remarkable Pro Colors
Attack surface reduction? On a device with unencrypted storage, the root password displayed in the about screens, no verified boot, no password by default (with password protection that amounts to a lock screen), and unprotected USB access to all user files by default? Where there are four exposed pins on the exterior that allow mounting of the root filesystem as USB mass storage regardless of password protection (https://github.com/ddvk/remarkable2-recovery), and the root password is stored in plain text?
In PineNote E Ink tablet and PinePhone Pro developer versions now shipping
Oh boy do I have opinions with this one. This seems like a lot of work to avoid using a perfectly good package manager on the device. They could have used rsync without installing rsync on the device. The target device doesn't need to have rsync for rsync to be used. They could have installed the package manager and left it. It doesn't run anything in the background on my device. It's easy enough to verify you don't have a systemd service or timer running it. (cron isn't installed, iirc) They could have compiled rsync with all of the libraries bundled with it. (Maybe this is beyond their expertise?) Their solution is using Docker to use the package manager and then overwriting system files on the device in the worse possible way, without understanding what they are doing. At that point, they verified in Docker. Should be safe to run it on
Read the rest
the tablet then, yes? What attack vector are they worried about? :/ Toltec is actively worked on, odds are someone would notice someone else fucking with repository. The cherry on top was completely not understanding how the remarkable works. There are two partitions for a reason. The inactive one is used for software updates. When the reMarkable downloads an update, it downloads it to the inactive partition. When you "install" the update, it flips which of the two partitions is active. If the update fails to boot, it flips back to the known good state. All they had to do was switch the active partition, the next update would overwrite the broken partition. https://github.com/ddvk/remarkable2-recovery/issues/6 This looks like a bad case of tunnel vision, combined with a lack of understanding. I'm glad they managed to figure out how to fix it.
In I bricked then recovered my reMarkable 2

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.