reMarkable Update FUSE
Mount remarkable update files using FUSE
Usage
pip install remarkable_update_fuse
mkdir /mnt/signed /mnt/image
rmufuse path/to/update_file.signed /mnt/signed
Known Issues
- Will report checksum errors for Directory inode, even though they are fine
- Will report checksum errors for extent headers, even though they are fine
Building
Dependencies:
- curl
- python
- python-build
- python-pip
- python-pipx
- python-venv
- python-wheel
make # Build wheel and sdist packages in dist/
make wheel # Build wheel package in dist/
make sdist # Build sdist package in dist/
make dev # Test mounting 2.15.1.1189 to .venv/mnt
make test # Run automated tests
make install # Build wheel and install it with pipx or pip install --user
make executable # Build a standalone executable
make portable # Build a standalone executable with some extra dependencies embedded
Building for the reMarkable (Or really any linux/arm/v7 device)
The same as above, but use ./make_for_remarkable.sh instead of make. This requires docker to be installed.
Metadata
Release files for remarkable-update-fuse 1.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| remarkable_update_fuse-1.4.3.tar.gz | 6.0 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| remarkable_update_fuse-1.4.3-py3-none-any.whl | Python 3 | none | any | Details |
| remarkable_update_fuse-1.4.3-cp313-cp313-manylinux_2_34_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.34+ x86-64 | Details |
| remarkable_update_fuse-1.4.3-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details |
| remarkable_update_fuse-1.4.3-cp311-cp311-manylinux_2_34_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.34+ x86-64 | Details |
Total release size: 1.1 MB
Release files / remarkable_update_fuse-1.4.3.tar.gz
| Download URL | remarkable_update_fuse-1.4.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0cedfb5b63de615ae40e5bc94ed004d28beca6edf72408dea8d14769e2f09227
|
|
BLAKE2b-256 checksum How to use checksums |
6c3767a7881a5740a4253a1b621810852037c57dc7dc26b05cbbe92cb954aaac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logRelease files / remarkable_update_fuse-1.4.3-py3-none-any.whl
| Download URL | remarkable_update_fuse-1.4.3-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d92e023183bcabda0da3598816cd60a33e28707fbc76a357a21a02c5adab3a6a
|
|
BLAKE2b-256 checksum How to use checksums |
41f97ee0c7364cce8f114394da2e320a48ed169158d0a1a323f4f757878c5d9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logRelease files / remarkable_update_fuse-1.4.3-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | remarkable_update_fuse-1.4.3-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 360.4 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
3c45192f178a53e6ae2e65d8af923465993ae7b5c147ab1129eaab5678203737
|
|
BLAKE2b-256 checksum How to use checksums |
1df6976ec57733a19f724267993da3683a2b15d89cd4620d54ba2d7610769125
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logRelease files / remarkable_update_fuse-1.4.3-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | remarkable_update_fuse-1.4.3-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 357.7 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
2899cb34e62826ae9ecda926616a252f86da6adcb1ecb2c3f89841d316d50e89
|
|
BLAKE2b-256 checksum How to use checksums |
2d5d46f1371c56798409baa33d93c3f4db9345261a820ca945e3da3bf1156ab6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logRelease files / remarkable_update_fuse-1.4.3-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | remarkable_update_fuse-1.4.3-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 322.5 kB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
4c60cb02fb273332ac57b36830128eb82c480992463ffc260d1946df279aef3a
|
|
BLAKE2b-256 checksum How to use checksums |
eb3f933a4fbccd660506bed30e615488de028949feeaf69141459fcc86075458
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logSecurity for remarkable-update-fuse 1.4.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for remarkable_update_fuse-1.4.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.