rmhack

I'm the author of RCU. Some details are missing that would help with troubleshooting your problem. Would you post a video showing you extracting the package, then right-clicking on RCU.app > Open > Open, and of the error message thereafter?

Do you have an active support period for the program? (Wondering why you didn't email me directly, which could result with more-helpful information. I just happen to watch RSS feeds for this subreddit.)

Or just Ctrl+A > Export PDF, which will mass export everything and also keep the folder structure.

It takes a special kind of vanity to come into these comments and bad-mouth OP, to tell them they're flat-out wrong and start calling them names. It's incredibly intolerant, disrespectful, and shows a real lack of maturity by those commenters. It makes this whole community appear vicious and shallow.

OP has understandable issues, and they shouldn't be blamed for them. reMarkable, themselves, are indeed unhelpful in many ways that were validly criticized, but also generous in the lengths they'll go to satisfy their customer. As a community, to be unable to take these criticisms constructively, not thinking the problem through, attaching personal feelings, is unacceptable. Did OP go a little too far? Perhaps, if they have to drive somewhere to print documents, c'est la vie, but for those who are intimately familiar with reMarkable's software, the rest of OP's frustrations are understandable.

For one, contrary to what parallel comments have opined, it does NOT break any terms of service to only install a font(s). It isn't hard to install one...it's a supported function of the underlying operating system...BUT, most instructions I've seen elsewhere were written by people who don't have the technical literacy to understand why putting fonts in the system partition (in /usr/local/fonts or such) is a bad idea. It's a bad idea because the reMarkable system partition is ~200 MB large, and most of that space is used up. Depending on the number and size of fonts (and whether a user has also inappropriately put custom templates in /usr), the system partition will fill up. When the system partition fills up, the system software begins to fail. Updates cannot be checked. SSH fails. Bad things happen.

If OP had just put their fonts in /home/root/.local/fonts instead, they probably never would have had an issue.

That reMarkable also doesn't support Asian typography is a clear shortfall. There is no good reason against this -- the fonts are free and libre, and hundreds of people have downloaded my own reMarkable font packages, so there clearly is demand. This is a valid criticism of the default software and company. However, if other people wouldn't post "tutorials" with bad fundamentals, OP probably wouldn't have had any problem (a case of the blind leading the blind).

You have two real options for doing what you want:

1. If you're not afraid to use Python or the command line, you could use codexctl to install specific firmware to your tablet. I haven't ever used it myself, so you'll have to read the docs. I don't think it can just flip the boot partition flag so you might still need to rely on switch.sh.

2. Use a nightly build of RCU, which can flip between boot partitions at-will, and also upload firmware files (with the .signed extension) to the inactive partition. You would right-click on the tablet icon, press Upload Firmware, install the 2.15 one, then do it again for the 3.8 one. To flip between, them, right-click the tablet icon and select Flip Boot Partition.

To download the firmware files, you could either download them using codexctl's CLI, or you could use the URL listed here and combine it with the firmware version numbers and suffixes listed here to get the specific ones you want (pay attention to 'remarkable1' vs 'remarkable2'!).

If you DM me, I'll give you a gratis copy of RCU because I want more people testing this feature.

You could install an application launcher and KOReader (a more-featured Epub reader) through Toltec.

I have kept my RM2 plugged in for the past 2.5 years, with a 6-month stretch where it was locked in a safe when the battery was totally drained. Its total capacity is now 90% of what it was when new (full charge capacity is now 2794 mAh, and its design capacity is 3083 mAh).

Neat -- but also, reMarkable is configured with mDNS, and so you can probably just reach it with remarkable.local instead of an explicit IP.