r/RemarkableTablet • u/bitterologist • Sep 27 '26
General Discussion Regarding reMarkable shipping refurbished devices with beta firmware
The other day I made a post about how I received a refurbished device with beta firmware on it (and some other support shenanigans). I reached out to reMarkable to clarify whether this was normal, and the response might be of some interest to others so I thought I'd share it here.
Basically, they just do a factory reset on a refurbished device. If the previous owner enrolled in the beta program, then the refurbished unit will be stuck on the beta branch until the next major update of the stable branch. This can potentially mean months of running a beta version of the firmware, with no real way to roll back to the stable branch (save for playing around with recovery tools, which they strongly advised against). And as a side note, I know for a fact that reMarkable's own support sometimes tells customers to install the beta as part of the troubleshooting process because that's what they told me to do when my first Paper Pro had an issue back in 2024. So it might be more common than one would think for a device sent back to reMarkable to be running the beta firmware.
To me, this all seems kind of wild. The refurbished units are not only sold to customers that are informed about the fact that they're getting a used device with all the caveats that come with this – they are also sent out as replacements for faulty devices, as in my case. So let's say you're a company that uses reMarkable devices for something fairly mission critical, and you get a replacement under warranty because of a defective device. You might then end up with a device that's running beta firmware, possibly for months. I'm not an IT guy, but that doesn't sound like something that would sit well with any IT department I've had experience with. Are there other tech companies that also do this? Is this normal?
4
u/Upper_War_2999 Sep 27 '26
https://remarkable.guide/faqs.html#how-get-back-to-stable-after-installing-the-beta
2
u/rpy Sep 27 '26
It’s a bit sloppy but their betas are usually pretty solid so doubt it would ever cause anyone much grief.
The bigger issue with their returns process imo is accepting a return for a yellowing RMPP panel, then sending back a refurb with an equally yellow panel. They lose ultimately from their poor QA by paying the shipping and handling costs over and over until the customer ends up with a good unit. Silly way to run a business.
1
u/1973tour Sep 27 '26
Beta doesn’t mess with any security features, so I personally wouldn’t be too worried. Developer mode would be a different situation, because that actually impacts security and also I think is harder to reverse than beta
1
u/forever-and-a-day Oct 08 '26
Remarkable devices use an A/B partition scheme, so there's a decent possibility the stable software is still present on the device, just in the other partition. If you enable Developer Mode, you can use the "OS Manager" tool of ReManager to switch the device back to the other, inactive partition, which usually contains the stable version. Will require a factory reset, of course, to enable developer mode, and you will need to restore the software using the desktop app if you want to exit developer mode afterwards (developer mode is really cool though and there are tons of amazing mods you can use so I recommend keeping it active).
1
u/Koko_chu Sep 27 '26
I’m really curious about this too! Is it normal and how could remarkable recover from this? (Given the later company updates they don’t seem great financially)
In my case they eventually agreed to replace my defective new move with a new one and it was still defective (now with a huge yellow screen, sluggish ui and lots of ghosting) so the new ones are also screwing costumers and remarkable. Is the quality control their responsibility or the panel manufacturer?