remarkable2-recovery VS webinterface-onboot

⚠️ 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.

The only other active binary hacks I'm aware of are rM-signature-patch and webinterface-onboot. Those are to solve specific issues though, they do not modify anything you may see. They can both be applied after ddvk.

While no longer enabling the web interface setting is great, the real magic is in what is now possible. The web interface keeps running when the usb cable is disconnected, which means that it still has the ability to upload and download files, there is just no way to connect to it. But now that we can ensure the web interface is always running and accessible via webinterface-onboot and webinterface-persist-ip, we can write programs that connect to the device over wifi but can still use the web interface under the hood. This is useful as uploading a file to the device most any other way will require restarting the device to see the file, and work is still being done on programs that can generate pdfs from the new file format (the web interface can). As a first step in that direction, I created..

- This program will not start/enable the web interface nor ensure that the usb interface maintains the ip 10.11.99.1 [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) does this for version 2.10 but I do not have the newest software to test against. Using something like [webui_invincibility.sh](https://github.com/reHackable/scripts/wiki/webui_invincibility.sh) with [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) would ensure that [WebInterface-Wifi](https://github.com/rM-self-serve/webinterface-wifi) works on boot.