remarkable2-framebuffer VS remarkable2-recovery

Looks like rm2fb is now installed by default: https://github.com/ddvk/remarkable2-framebuffer/issues/90

We can currently hook into it, but only to obtain the framebuffer or send updates ourselves. 3rd party mods use remarkable-framebuffer which does the injection and easily enables 3rd party community apps/mods to use the screen.

Is is safe? there are issues like this or this

Instructions here, at the end of the "Configuration" section. Please not, however, that these settings were only added to the rm2fb repo 11 hours ago (commit). So again, best to check that up-to-date settings exist before upgrading your firmware.

It's an eInk screen, so yes-ish.

We get around this by just piggybacking on the build in application's screen display routines[0]

https://github.com/ddvk/remarkable2-framebuffer

Have you installed rm2fb? https://github.com/ddvk/remarkable2-framebuffer

This seems to have updated all the installed components. In particular, rm2fb is now on the latest release which, if I'm understanding correctly, supports 2.9. ("Support for release 2.9.0.210")

⚠️ Warning: Toltec does not support OS builds newer than 2.15.1.1189. You will soft-brick your device if you install before support is released. See remarkable2-recovery for information on how to recover your device if you have done this.

The option of last resort might be to use the pogo pins to get into recovery mode. There are instructions in the ddvk github repo. https://github.com/ddvk/remarkable2-recovery

I don't think it's particularly risky to install third-party stuff on your rM2. I would urge you to be very careful to understand the uninstall process, and to understand what it takes to recover it if you do manage to brick your device. TL;DR: you'll need a Linux machine, a USB-C breakout board, and some patience. If you're comfortable with going through that process - even though you shouldn't have to - I'd say you have nothing to worry about.

There's a recovery process that requires some simple and improvisable hardware.

Storage is not encrypted. On an rm2, rather trivial hardware allows the device to be used as USB mass storage. An rm1 can be read without extra hardware. Both of these are explained as recovery methods, but unlike, for example, Android recovery with encrypted storage, where recovery methods usually allow you to overwrite partitions, these allow you to mount existing, unencrypted partitions.

I am new to Toltec and all hackings. After yesterday's official update, I was rushing to re-enable my Toltec without reading the warning. Now my rM2 gets stuck on starting screen. Is recovery tools for reMarkable 2 the only way to unbrick my device? It is beyond my knowledge. I saw there was mentioning a 10k resistor, but it doesn't show on the requirement list.

You have to ssh into it and maybe check if xochitl or rm2fb is disabled. If can't ssh into it, then refer to https://github.com/ddvk/remarkable2-recovery.

Unless I'm mistaken, the pogo port can be enabled externally by pulling down B8 / SBU2 on the USB-C port. This is why you either need a special plug or a breakout board; ddvk also speculates that you could use a USB audio adapter and headphones.

Hi - I'm considering to jump on ddvk hack but worry if the basic functionality will not be there - like Send to my Remarkable , cloud functionality etc.