conv.

All stories
TechRunning 1m

Developer revives four-year-old reMarkable 2 tablet via SSH troubleshooting

A user documents technical steps to restore a 2021 reMarkable 2 paper tablet after years of disuse, resolving sync and update failures.

2 items150 engagement100 comments Hacker NewsPress

Conversation activity · last 28 hours peak 2/hr

Peak 2 items in one hour at Aug 9, 7 AM; 2 items over 28 hours Aug 9, 7 AM — 2 itemsAug 9, 8 AM — no itemsAug 9, 9 AM — no itemsAug 9, 10 AM — no itemsAug 9, 11 AM — no itemsAug 9, 12 PM — no itemsAug 9, 1 PM — no itemsAug 9, 2 PM — no itemsAug 9, 3 PM — no itemsAug 9, 4 PM — no itemsAug 9, 5 PM — no itemsAug 9, 6 PM — no itemsAug 9, 7 PM — no itemsAug 9, 8 PM — no itemsAug 9, 9 PM — no itemsAug 9, 10 PM — no itemsAug 9, 11 PM — no itemsAug 10, 12 AM — no itemsAug 10, 1 AM — no itemsAug 10, 2 AM — no itemsAug 10, 3 AM — no itemsAug 10, 4 AM — no itemsAug 10, 5 AM — no itemsAug 10, 6 AM — no itemsAug 10, 7 AM — no itemsAug 10, 8 AM — no itemsAug 10, 9 AM — no itemsAug 10, 10 AM — no items 2 items · 7 AM
Aug 10

Summary, timeline and people extracted by Claude from 2 items across 2 sources · 22h ago. Quotes are verbatim.

A developer published a detailed guide on restoring a reMarkable 2 tablet that had been unused for approximately four years and was experiencing cloud sync failures and software update errors. The post documents troubleshooting steps including clock synchronization via SSH, sequential software updates, and enabling alternative file transfer methods through the device's web interface.

  • An out-of-sync system clock was the root cause preventing software updates and cloud synchronization on the dormant tablet.
  • Sequential software updates were required; the first update (to 3.11.2.5) was insufficient and required a restart of update services to access version 3.27.3.0.
  • Software version 3.22+ silently disables SSH over WiFi; SSH must be accessed via USB or re-enabled via the rm-ssh-over-wlan command.
  • When cloud sync remained broken, the developer used the device's web interface as an alternative method for file transfer instead of further debugging.

How it unfolded

  1. Reaction Post gains traction on Hacker News

    The article reached Hacker News frontpage with 73 points and 56 comments, indicating community interest in device recovery techniques.

  2. Report Troubleshooting guide published

    A developer (tremguy) published a comprehensive technical post detailing how to restore the tablet by setting the system clock via SSH, applying sequential software updates, and enabling the web interface for file transfer.

  3. Event Device unused for ~4 years

    The tablet sat unused for approximately four years, entering a non-functional state with cloud sync failures and error 0.

  4. Event reMarkable 2 purchased

    The tablet was originally purchased in 2021.

What people are saying verbatim

“I found my old reMarkable 2 paper tablet, bought in 2021, it had sat unused for ~4 years or so. The device was in a sorry state: Cloud sync failing.”

tremguy, Developer/author · Hacker News / blog post

“Unable to sync. Please update this application to continue using the reMarkable cloud.”

reMarkable cloud service, Cloud sync error message · Blog post (from device journal)

“This failure mode is also documented in an official support article: an out-of-sync device clock can prevent software updates.”

tremguy, Developer/author · Blog post