remarkable-update VS remarkable2-recovery

Using the image file to upgrade a tablet, use remarkable-update or RCU.

Also, I've used remarkable-update to perform every firmware update on all three of my tablets. You can't use it if you can't SSH into the tablet to modify the update.conf file in the first place, so if a tablet is upgraded to a version where dropbear (the SSH server) isn't running, it's "game over" for that tablet. The same goes for RCU, which just added firmware updating as a feature in the last week or so ... no SSH, no RCU.

You're not being paranoid! What you described in your post was exactly right: do a factory reset, then overwrite both boot partitions via ddvk/remarkable-update (apply an upgrade twice)!

Hi, there. Sorry if this has already been asked, but has anyone been able to successfully downgrade their firmware in order to use some of the cool third-party apps out there? I'm running 3.1x and I'd like to use this script to downgrade to 2.5, but I'm scared I'll brick my device. Any advice?

Is there anyway I can by revert back to version 2.15.1.1189? I tried that guide to change the firmware, but for some reason it says "Error checking the update." when tapping "Check for updates". Even though I've exactly made what was said in the readme and I didn't make mistakes in the IPs. I'd appreciate any help!

[1] https://github.com/ddvk/remarkable-update/blob/main/switch.sh

You can have both using the switch.sh script to flip between partitions configured for 2.15 and 3.x but you can't use the same notebook. See here for latest on ddvk for 3.x.

I should be able to downgrade, right? Via: https://github.com/ddvk/remarkable-update

See remarkable-update, or remarkable-update-helper. Here is another discussion about downgrading, as well.

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