This is a set of firmware patches for the reMarkable 1 tablet. They are all in bspatch format. They are organized by firmware version (currently versions 2.1.1.3, 2.2.0.48, and 2.5.0.27 are supported).
Current patches:
- Bind the web interface to
lo(localhost) instead ofusb0 - Make the web UI "invincible" (i.e. if you enable the UI, it will persist through reboots)
Disable file uploading and keep downloading (if you don't want your notes to leave your reMarkable)Bind the web interface towlan0(Wi-Fi IP) instead ofusb0
(I'm not updating the strikethrough patches -- I'm only really interested in binding to localhost and keeping the Web UI persistent.)
You may also want to take a look at @FiloSottile's reput project. reput allows you to synchronize content to your reMarkable tablet without using the reMarkable cloud service, and will automatically apply the localhost and web UI invincibility patches.
When the reMarkable software is queueing files to be uploaded, it checks if the device is online. This patch causes that check to fail always, so that files are never uploaded from the device to the reMarkable cloud. Using the cloud to sync documents from your computer to the reMarkable will still work.
Warning: This patch will be undone by a firmware upgrade, and documents will start syncing with the reMarkable cloud again.
You can find this patch in xochitl-w.x.y.z-no-upload.bspatch.
Note Since version 2.2.0.48, you don't need a separate invincibility patch.
This patch keeps the reMarkable web UI enabled across reboots. When this patch is first applied, you will have to toggle the web interface on. If you want to disable it again, you must toggle the Web UI switch off and then reboot the device.
I can confirm that this works consistently if you bind the web interface to lo. If you bind it to wlan0 or keep the default behavior of binding to usb0, the web interface may not come up automatically, as wlan0 and usb0 both lack assigned IP addresses on boot.
You can find this patch in xochitl-w.x.y.z-lo.bspatch.
Since the update to reMarkable v2.0, the web interface will no longer activate if usb0 is not assigned an address. This means that you can't activate the web interface if the reMarkable isn't plugged in to a computer (or the interface is manually assigned an IP).
This patch causes the web interface to bind to wlan0 instead, meaning you should be able to access it over a wireless network. Note that the UI will still say to navigate to the USB IP, but this is erroneous.
You can find this patch in xochitl-w.x.y.z-wlan0.bspatch.
This patch causes the web interface to bind to localhost instead, so you can access it via an SSH tunnel (e.g. ssh -L 8080:localhost:80 root@remarkable).
Note: As of 2.5.0.27 (and probably other 2.5 firmwares), you need to plug in the USB cable once to toggle the web interface on after applying the patch. After this is done, the web interface should persist through reboots.
You can find this patch in xochitl-w.x.y.z-lo.bspatch.
You'll need bsdiff and bspatch installed. On a macOS system, you can brew install bsdiff.
xochitl is the binary that runs the reMarkable interface. You can get it from your reMarkable via scp:
scp remarkable:/usr/bin/xochitl /path/to/local/dir/xochitl
To apply the "bind web interface to wlan0" patch, for example:
bspatch xochitl xochitl-wlan0 xochitl-w.x.y.z-wlan0.bspatch
Upload the patched binary to /usr/bin/xochitl. You'll need to stop the service before you do this.
I recommend that you make a backup of your system xochitl binary before modifying it. On your reMarkable, issue a cp /usr/bin/xochitl /home/root/xochitl-backup.
To upload a patched binary:
- On your reMarkable:
systemctl stop xochitl - On your computer:
scp xochitl-wlan0 remarkable:/usr/bin/xochitl - On your reMarkable:
systemctl restart xochitl
Note that the xochitl binary must have execute permissions! The default permissions for the file are 755, and I've put my reMarkable into a boot loop before by accidentally messing those permissions up.
- Q: Can I apply more than one patch?
- A: Yes, you just have to do them in tandem. I can't guarantee every patch will play nice, but you should be able to do something like the following:
$ bspatch xochitl xochitl-no-upload xochitl-w.x.y.z-no-upload.bspatch
$ bspatch xochitl-no-upload xochitl-no-upload-wlan0 xochitl-w.x.y.z-wlan0.bspatch
Note that the wlan0 and lo patches probably won't play nicely with each other, as they patch the same locations in the binary. The rest should not interfere with each other.
Feel free to file a GitHub issue for any other questions!