本文来源:https://mp.weixin.qq.com/s/BhostUKsN76H8PHGJ1Iqjg
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
朋友有一台 2019 年的 Kindle Oasis 在抽屉里躺了快 3 年。他看我最近拿 Kindle 刷书刷上了瘾,就把它翻出来丢给我,让我帮忙刷个机。
朋友说,当初是冲着 7 寸大屏和实体翻页键买的,结果翻了几十本书,亚马逊中国书店就停止运营了。后面就用电脑拷贝的方式自己找电子书,而且格式还要转换成azw或mobi格式。再后来他就转到了微信读书,导致这个2000元的电纸书一直吃灰。

一台没登录账号的 Kindle,约等于一块电子砖。
所以让我帮他越狱。我折腾了大半个晚上,踩了五个坑,最后真跑通了。现在它是一台能看微信读书的电纸书,进度还能和手机同步。
整个路子我记在下面。先说清楚一件事:这条路不是所有 Kindle 都能走,动手前一定要核对机型和固件。
一、你的 Kindle 能不能折腾,先看固件
越狱卡机型、卡固件,差一个小版本就是完全不同的一条路。

先查固件版本:设置 → 设备选项 → 设备信息,记下那串5.18.x之类的数字。
这台是Kindle Oasis 第十代(KOA3)+ 固件 5.18.2 + 没有亚马逊账号。这个组合有几个思路,但大部分我看完就排除了:
Véra 值得单独说一句。官方写它兼容 5.17 到 5.19.5,这台 5.18.2 明明在范围里,但打开网站,它表明"设备暂不兼容"。
我扒了下网页源码才搞明白:Véra 是靠显示屏分辨率认机型的。KOA3 的分辨率(1264×1680)在它的识别表里,可对应的固件白名单却是空的。通俗讲,它认识这块屏,但没给这台机器准备越狱包。
所以别被"兼容 5.17–5.19.5"这种总述骗了,真实兼容范围是逐机型列的。
排到最后,无账号 + 5.18.2 只剩一条路:SpiderCat。
二、全程大概分五步
用一张表说清整条链路:
下面逐步说,重点是每步的坑。
三、第一步:把存储填满,挡住自动更新
Kindle 有个习惯:趁你联网,偷偷把平台更新包下下来。越狱过程中要是更新一装,前面的工夫全白费。
最省事的办法是把存储填到只剩 100MB 左右,让几百兆的更新包根本下不下来。
这一步必须插 USB 线,是全程少数需要动手连电脑的地方。我把这个写成了一个脚本,跑一下就行:
它会找到 Kindle 盘符,在.kindle-filler目录里塞大文件
每个文件 3GB(FAT32 单文件上限是 4GB,得留点余量)
填到剩余空间 100MB 以下自动停
填完,先开飞行模式,弹出线,再连 WiFi,顺序别搞反。
这里有个小坑:一开始我偷懒用小文件硬填,结果 USB 2.0 下每建一个文件都有开销,几十兆几十兆地爬,慢得想砸电脑。改用 fsutil 直接建大文件,几分钟就搞定。
四、第二步:SpiderCat 越狱
SpiderCat 的触发方式很取巧:它把越狱程序伪装成一本电子书。
你把那本特制的spidercat.azw3拷进documents文件夹,Kindle 就会把它当普通书表明。
然后在 Kindle 上:
关掉飞行模式,连 2.4GHz 的 WiFi(5G 和 WPA3 在 Kindle 上不太稳)
图书馆找到spidercat这本"书",点开它
显示屏先空白几秒,接着文字从顶上一行行往下淌
跳出Restarting Kindle,自动重启

重启完,root 就到手了。标志是documents里多出一个JAILBROKEN.txt,内容就一句"You are jailbroken!"。
顺带一提,越狱成功后平台更新会被自动屏蔽,所以第一步那些填盘文件此时可以删了,空间能还回来。
五、第三步:装 KOReader(这里翻车了)
要让 Kindle 跑微信读书,得先有个能装插件的电纸书,选的是KOReader。
官网的正规姿势是在搜索栏敲两行命令:
;kpm update
;kpm install koreader
我照做了。然后启动,闪回主页,没反应。
这种"看起来装好了但打不开"的情况最烦人。我把启动日志抓出来看,发现了真相:KPM 分发的安装包是坏的。
解压之后,一堆关键文件大小是 0 字节:
luajit 0 bytes (KOReader 的引擎)reader.lua 0 bytes...
一个 0 字节的引擎,跑起来当然直接崩。
我猜是 KPM 把文件解压到 Kindle 的 FAT32 分区时出了岔子。诡异的是,同一个包里fbink、dropbear又是完整的,坏得很随机。
应对办法是从官网下原始压缩包,手动部署,绕开 KPM。解压后把整个koreader目录拷到 Kindle 根目录,再校验一遍关键文件非空。这回一次就起来了。
如果你也遇到";kpm install之后打不开",先去看 KOReader 目录里luajit的体积,是 0 就是包坏了。
装 KOReader 用的是 koreader-kindlehf 这个包(硬浮点机型)。老一点的 Paperwhite、Kindle Touch 要用 koreader-kindlepw2,别下错。
六、第四步:微信读书插件
这一步先说个反常识的事:Kindle 上不存在能用的微信读书 APK。
Kindle 是 Linux 平台,不是安卓,硬件也跑不动安卓运行时。所有号称"给 Kindle 装微信读书 App"的教程,基本都不靠谱。
真实的做法是装一个 KOReader 插件。这个插件用微信读书自己的接口,扫码登录,不需要谷歌服务。
微信扫码之前,手机上要先给账号开个东西:
微信读书 App → 我 → 设置 → 微信读书 Skill → 获取 API Key
然后把这个插件解压到 KOReader 的plugins目录,重启 KOReader,在工具菜单里就能看到"微信读书",扫码登录即可。
登录完,书架就出来了,能下书、能同步进度、能看划线和别人的想法。

七、第五步:在图书馆弄个启动入口
KOReader 装好了,但每次启动都得输命令,太麻烦。
网上教程会让你装KUAL。千万别。KUAL 是旧时代的东西,在新的越狱框架下已经失效了。
现在的正规做法叫Scriptlet:在documents文件夹里放一个.sh脚本,Kindle 就会把它当成一本书表明,点开就执行。
我给 KOReader 做了个启动脚本,还配了张封面。现在图书馆里躺着一本叫KOReader的"书",点一下就能进微信读书。
封面是我自己画的,白底黑字,墨水屏上看着干净。

几个别人不会写的坑
整理一下,都是实际撞过的:
KOReader 开着的时候,电脑连不上 Kindle。因为它会临时关掉 USB 驱动。想传文件,先在 KOReader 里点"退出"。
KPM 装的 KOReader 可能是坏的,动手前把luajit的文件大小看一眼。
Véra 的"兼容范围"要逐机型核对,别信总述。
填盘别用小文件,USB 2.0 下慢到怀疑人生,用大文件。
Windows 上写 PowerShell 脚本记得存成 UTF-8 with BOM,否则中文注释会让 PowerShell 5.1 直接报一堆语法错。
最后
这台 Kindle 早就还给了朋友。听说他现在天天拿它刷微信读书。
越狱这事有风险,会失去保修,操作不当也可能把机器弄成砖。我的建议是动手前先备份,别装来路不明的包。
整条流程的脚本、安装包和更详细的命令,我都整理好了,需要的可以后台回复「oasis3」自取。
如果你也有台吃灰的 Kindle oasis,不妨试试。它可能比你想象的耐用。
再说个事。
我发现不少朋友就算有 AI 帮忙,越狱还是卡在某个环节搞不定。如果你实在不想折腾,或者自己试了几次都没成,可以把机器寄给我帮你处理,往返邮费自理。需要我出手的,打赏一杯奶茶钱就行,我帮你把难题应对掉。
A friend had a 2019 Kindle Oasis lying in a drawer for almost three years. Seeing I recently got hooked on reading with a Kindle, he dug it out and handed it to me to help jailbreak it.
My friend said he bought it for the 7-inch big screen and physical page-turn buttons, but after flipping through a few dozen books, Amazon China's store stopped operating. Later he sourced ebooks himself by copying from a computer, and had to convert formats to azw or mobi. Then he moved to WeChat Reading, leaving this 2,000-yuan e-reader gathering dust.
A Kindle with no account logged in is roughly an e-brick.
So he asked me to jailbreak it. I fiddled for most of an evening, hit five pitfalls, and finally got it working. Now it is an e-reader that can read WeChat Reading, with progress syncing to the phone.
I have written the whole path below. One thing to be clear up front: this path does not work on every Kindle - before you start, you must check the model and firmware.
1. Whether your Kindle can be modded starts with the firmware
Jailbreaks are tied to model and firmware; a slightly different minor version means a completely different path.
First check the firmware version: Settings -> Device Options -> Device Info, and note down the string of numbers like 5.18.x.
This one is Kindle Oasis 10th gen (KOA3) + firmware 5.18.2 + no Amazon account. This combination has a few approaches, but I ruled out most after a look:
Approach
Compatible firmware
Needs Amazon account
Usable on this unit
Vera
5.17-5.19.5
No
No
LanguageBreak
<= 5.16.2.1.1
No
Firmware too high
WinterBreak
<= 5.18.0
Yes
Firmware too high
SpringBreak
Depends on model
Yes
No account
SpiderCat
5.16.3-5.19.5
No
This is the one to use
Vera deserves a special note. The official site says it supports 5.17 to 5.19.5; this 5.18.2 is clearly in range, yet opening the site it says "device not currently compatible".
I dug into the page source to understand: Vera identifies models by screen resolution. KOA3's resolution (1264x1680) is in its recognition table, but the corresponding firmware whitelist is empty. Plainly, it recognises the screen but has no jailbreak package prepared for this machine.
So don't be fooled by a blanket statement like "compatible 5.17-5.19.5"; the real compatibility range is listed per model.
After ruling everything out, with no account + 5.18.2 there is only one path left: SpiderCat.
2. The whole process is roughly five steps
Use a table to lay out the whole chain:
Step
What to do
Where to operate
1
Fill the storage to block platform auto-update
Computer (USB)
2
Get root with SpiderCat
Kindle
3
Install KOReader e-reader
Computer (USB)
4
Install the WeChat Reading plugin
Computer (USB)
5
Set up a launch entry in the library
Computer (USB)
Below, step by step; the focus is the pitfalls of each step.
3. Step one: fill the storage to block auto-update
Kindle has a habit: while you are online, it secretly downloads the platform update package. If an update installs during jailbreaking, all the earlier effort is wasted.
The easiest method is to fill the storage until only about 100MB remains, so the hundreds-of-MB update package simply cannot download.
This step requires plugging in the USB cable - one of the few places in the whole process that needs hands-on connection to a computer. I turned this into a script; just run it:
It finds the Kindle drive letter and stuffs large files into the .kindle-filler directory
3GB per file (FAT32's per-file limit is 4GB, so leave some headroom)
Stops automatically when free space drops below 100MB
After filling, first turn on airplane mode, eject the cable, then connect to WiFi - don't reverse the order.
Here is a small pitfall: at first I was lazy and filled with small files, but under USB 2.0 each file has overhead, crawling tens of MB at a time, slow enough to make you want to smash the computer. Switching to fsutil to create large files directly finished in minutes.
4. Step two: SpiderCat jailbreak
SpiderCat's trigger is clever: it disguises the jailbreak program as an ebook.
You copy that special spidercat.azw3 into the documents folder, and Kindle treats it as a normal book to display.
Then on the Kindle:
Turn off airplane mode, connect to 2.4GHz WiFi (5G and WPA3 are unstable on Kindle)
In the library find the "book" spidercat and open it
The screen goes blank for a few seconds, then text flows down line by line from the top
A "Restarting Kindle" pops up and it reboots automatically
After reboot, root is obtained. The sign is an extra JAILBROKEN.txt in documents, whose content is just one line: "You are jailbroken!".
By the way, after a successful jailbreak the platform update is blocked automatically, so the filler files from step one can now be deleted and the space recovered.
5. Step three: install KOReader (this is where it went wrong)
To make Kindle run WeChat Reading, you first need an e-reader that can install plugins; the choice is KOReader.
The official proper way is to type two commands in the search bar:
;kpm update
;kpm install koreader
I did so. Then launched it - it flashed back to the home screen, no response.
This "looks installed but won't open" situation is the most annoying. I grabbed the startup log and found the truth: the package distributed by KPM is broken.
After extraction, a bunch of key files are 0 bytes:
luajit 0 bytes (KOReader's engine) reader.lua 0 bytes...
A 0-byte engine obviously crashes on launch.
I guess KPM went wrong when extracting files to Kindle's FAT32 partition. Strangely, fbink and dropbear in the same package were intact - the corruption was random.
The fix is to download the original archive from the official site and deploy manually, bypassing KPM. After extraction, copy the whole koreader directory to Kindle's root, then verify the key files are non-empty. This time it came up on the first try.
If you also hit "won't open after ;kpm install", first check the size of luajit in the KOReader directory; if it is 0 the package is broken.
The KOReader package used is koreader-kindlehf (hard-float models). Older Paperwhite and Kindle Touch need koreader-kindlepw2; don't download the wrong one.
6. Step four: WeChat Reading plugin
First, a counterintuitive fact for this step: there is no working WeChat Reading APK on Kindle.
Kindle is a Linux platform, not Android, and the hardware can't run the Android runtime either. All tutorials claiming "install the WeChat Reading App on Kindle" are basically unreliable.
The real method is to install a KOReader plugin. This plugin uses WeChat Reading's own API, logs in by scanning a QR code, and needs no Google services.
Before scanning with WeChat, you must first enable something on the phone account:
WeChat Reading App -> Me -> Settings -> WeChat Reading Skill -> Get API Key
Then extract this plugin into KOReader's plugins directory, restart KOReader, and you will see "WeChat Reading" in the tools menu - just scan the QR code to log in.
After logging in, the bookshelf appears; you can download books, sync progress, and view highlights and others' thoughts.
7. Step five: set up a launch entry in the library
KOReader is installed, but you have to type commands every launch - too troublesome.
Online tutorials tell you to install KUAL. Don't. KUAL is a relic of the old era and no longer works under the new jailbreak framework.
The current proper method is called Scriptlet: put a .sh script in the documents folder, and Kindle treats it as a book to display - open it and it runs.
I made a launch script for KOReader, with a cover too. Now there is a "book" called KOReader in the library; one tap enters WeChat Reading.
The cover I drew myself, white background with black text, clean on the e-ink screen.
A few pitfalls others won't write about
Summarised below, all ones I actually hit:
When KOReader is open, the computer can't connect to Kindle, because it temporarily disables the USB driver. To transfer files, first tap "Exit" in KOReader.
The KOReader installed by KPM may be broken - before you start, check the file size of luajit.
Vera's "compatibility range" must be checked per model - don't trust the blanket statement.
Don't fill the disk with small files - under USB 2.0 it is maddeningly slow; use large files.
When writing PowerShell scripts on Windows, remember to save as UTF-8 with BOM, otherwise Chinese comments will make PowerShell 5.1 throw a bunch of syntax errors.
Finally
This Kindle was long returned to my friend. I heard he now reads WeChat Reading on it every day.
Jailbreaking has risks: you lose warranty, and improper operation can brick the device. My advice is to back up before you start, and don't install packages from unknown sources.
I have organised the scripts, install packages and more detailed commands for the whole process; if you need them, reply "oasis3" in the background to get them.
If you also have a dusty Kindle Oasis, give it a try. It may be more durable than you think.
One more thing.
I found that quite a few friends, even with AI help, still get stuck on some step of jailbreaking. If you really don't want to tinker, or tried a few times without success, you can mail the device to me to handle, at your own round-trip postage. If you need my hand, just tip me the price of a milk tea and I'll sort out the tricky bits for you.