> is available for all but the most up-to-date Kindles<p>Bought one from eBay to try it out. Silly me connected it to wifi and suddenly it’s up to date and no longer breakable
If you want a cheap rooted eReader I think you're better off getting a Kobo instead, they don't <i>officially support</i> rooting but AFAICT they make basically no effort to prevent it.
The latest Kobos use MediaTek SoCs with locked bootloaders. The Kobo Clara BW's MT8113, for example. As far as I know, one of the early bootloaders it, BL1, refuses to execute the next bootloader (BL2) unless its signature is valid. We can get the device into a mode where BL1 waits for upload of a BL2 via USB using an exploit called Kamakiri, but in public there is neither an exploit to get BL1 to boot an arbitrary BL2, nor an authorized BL2 image to upload. See here: <a href="https://github.com/bkerler/mtkclient/issues/1332" rel="nofollow">https://github.com/bkerler/mtkclient/issues/1332</a><p>Kobo devices have root exposed but don't let users boot their own kernels (and the kernel they ship was not compiled with kexec either).<p>I really don't know the reason so many devices these days don't have an unlock method. It seems predatory. Who knows where in the chain this happens... maybe it's Kobo, or maybe MediaTek won't sell you their SoCs for mass-market devices unless you lock them.
According to the github issue it seems to be a simple checksum step, not a true signature verification? If so there is no locked bootloader in any real sense.<p>If the real impediment is lack of demand or low-level development effort for any given device, that's in principle a solvable issue once projects like pmOS and Mobian choose to focus on some reasonably-available hackable hardware and bring it up to true daily driver state.
mtkclient does not seem to correctly interpret the usb output of the device past some part of the early boot process. Really, any of those messages formatted by mtkclient are unfaithful to the intended meaning. So yes maybe it is "just a checksum step" or maybe something else entirely. Last year I collected some UART logs on the device during bootup in a zip here:<p><a href="https://github.com/bkerler/mtkclient/issues/1289" rel="nofollow">https://github.com/bkerler/mtkclient/issues/1289</a>
Can you just access /dev/mem or load a kernel module? Is there a SELinux policy stopping that?<p>If you can do either of those, it should be trivial to get kexec working by just loading it as a module.
As far as I know, yes, it's possible. No SELinux. Kernel is a branch from 4.9.something pretty far off mainline with a few proprietary binary blob modules. As far as I know the real impediment here is lack of demand.
Older Kobos sound ok though?
+1 to a Kobo, they cheaper and better than Kindles, with full Calibre support (<a href="https://github.com/kovidgoyal/calibre" rel="nofollow">https://github.com/kovidgoyal/calibre</a> - OSS which has been in development for ~20 years!).<p>The way you install additional software is literally just moving files into folders whilst its plugged into your computer. I'm sure it could handle Tailscale.
I agree with your sentiment that the Kobo is better than the Kindle from an... ethical standpoint, if you have the money for one. However, it is worth noting that Kindles will always be cheaper than Kobo devices [0] due to economies of scale and lockscreen advertisements (removable with jailbreaking). From a pure cost perspective, and assuming the user is technically-minded enough to accomplish the jailbreak, the Kindle is likely always [1] a better deal.<p>[0] as of today, 12/8/25, the "base model" Kindle 11th Generation is priced at $109.99 USD, and the respective Kobo Clara BW is $139.99 USD.<p>[1] I say "likely always" to cover my bases. To my knowledge Calibre supports Kindle, just not as well as Kobo. That said I have found that the KOreader app is more than powerful enough for my use case (reading my own epubs, using dictionaries, etc.)
That doesn't always hold, if you want <i>color</i> e-ink then Kobo is currently the cheaper option.<p>Kindle Colorsoft (7" 16GB) - $250<p>Kindle Colorsoft (7" 32GB) - $280<p>Kobo Clara Color (6" 16GB) - $160<p>Kobo Libra Color (7" 32GB) - $230<p>The Libra also supports a stylus (sold separately) while the Colorsoft doesn't, that's reserved for the much bigger and pricier Kindle Scribe.
Where do I get DRM-free ebooks to put on a Kobo? I don't support breaking DRM. So I'm using a Kindle because it has the best access to and integration with almost any book I want.
Also consider koreader instead of the stock reader app.
Most (?) Kobos can run libby so you can get ebooks from your library.
I use the Calibre support, but did not know you could install additional software that easily!
Same with the Barnes and Noble Nooks. I've never rooted one, but via ADB one can install a launcher and most Android applications run. I've used four generations of Nooks to run AnkiDroid.<p>Just beware to check what version of Android the Nook is using before you buy, and what your app needs.
I used to like my Kobo a lot but recently it's got some pretty severe unreliability issues, usually around reading non-Kobo epubs and PDFs. Like, if I open of those files, the device usually crashes and when it recovers after a reboot, the file disappears.
Kobo is great. I use Plato and KOReader on mine. They worked better than the original reader software for reading manga.
The only (tiny) issue I've had with Tailscale on Kobo has been that the tailscale daemon prevents me from using the Kobo in Mass Storage Mode while it's active, so I have to disable/quit KOReader to be able to plug it in again, which is admittedly not frequently warranted anyways.
I was more after a eink display in a shape that is cheaper than new boards for a DIY project
Resell it, or wait six months. FWIW the 10th generation Kindle Paperwhite (the "PW4" in kindlemodding/mobileread lingo) doesn't have as large a screen as the newest models, but its maximum supported OS is currently 5.18.1 (and you can download that update directly from Amazon and transfer over USB), which is vulnerable to AdBreak. I just jailbroke and Tailscaled my PW4 this weekend after numerous failed attempts over a period of about a year to use the previous WinterBreak exploit.<p>I read mostly on my iPad; the Kindle is really just for reading outside, like at the beach/pool. But it was such a neat idea that I couldn't just pass it up.
Been there before with the OG pixel.
There is a new jailbreak, that is currently unpatched. You might need to make sure your Kindle doesn't get updated first by filling in all the disk space.
If you're looking for a good resource on jailbreaking and installing KOReader on your Kindle, I highly recommend the guides at <a href="https://kindlemodding.org/" rel="nofollow">https://kindlemodding.org/</a>
I have tailscale running on my robot vacuum. It's my own little autonomous mesh vpn node that lets me connect back to my home network when I'm on the go.
I used Tailscale on my remarkable tablet for a while; synchronizing documents over ssh is a lot easier with a static IP. It's fairly hard to get stuff to start on boot on the RM, or at least it was at the time, so I eventually moved off that plan. But it was pretty awesome to be able to ssh in from anywhere in the world.
That’s cool, and unexpected from a corporate blog.<p>Ma favourite e-reader setup still is the Kobo + Booklore combination. Editing a configuration file on the device I can have it connect to my Booklore library that adds my own ebooks seamlessly on top of the one I can get from the Kobo store.<p>I haven’t setup Tailscale on it yet but it’s possible.
This is pretty interesting write-up*, though I'm not sure my employer would be happy with me putting out EULA-violation instructions to our company homepage.<p>* - at least for me, as the bugs in the stock reader drive me nuts, and have been waiting for this opportunity for a while
You can also run Syncthing on a jailbroken Kindle. That opens up a world of possibilities!
Whoa, now that sounds like the use case I've been looking for since I jailbroke mine.<p>I have calibre set up to just email books to my Kindle, but that's an extra layer of indirection that I really don't need. I'll have to check that out.
I too have heard about syncthing for the first time today but from a different submission[0] you might care to be aware of.<p>Although, I realize Android != Kindle's OS, so I'm not sure how much concern there should be.<p>[0]: <a href="https://news.ycombinator.com/item?id=46184730">https://news.ycombinator.com/item?id=46184730</a> "Syncthing-Android have had a change of owner/maintainer"
If you have calibre, just turn on the wireless connection and have your Koreader connect to it.<p><a href="https://github.com/koreader/koreader/wiki/calibre" rel="nofollow">https://github.com/koreader/koreader/wiki/calibre</a>
I thought this was a random blog post, but it's coming directly from Tailscale, <a href="https://tailscale.com/blog/tailscale-jailbroken-kindle" rel="nofollow">https://tailscale.com/blog/tailscale-jailbroken-kindle</a>
Oh, this will be very useful. My current solution is incredibly hacky, I run an unauthenticated SSH server on the Kindle (key-based wasn't working), port scan to find it, and SFTP new files. At home, at least, I have a static IP. The whole system falls apart enough that I usually just connect to calibre's remote server and send books that way, though. I wonder what the battery impact of running tailscale on a Kindle is.
Kudos to all involved in freeing up Kindles around the world.
Excellent. This plus OPDS will make for easier transfer of files locally.
yes, let's definitely do that
Now do Tesla! I had to resort to running an oauth-proxy to access my Plex on Tesla.
Love the splash Jameson quote in the first pic.<p>> If everything means something else, than so does technology
What kernel version is it running?<p>I wanted to add an old paperwhite to a kubernetes cluster and the ancient kernel held me back.