AI拯救了我的积灰Kindle阅读器AI Brought My Dusty Kindle Back to Life


AI free token/AI免费积分

本文来源:https://mp.weixin.qq.com/s/yPtJXdxX9eF3HYv9_cDmwg
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。

积 灰 设 备 改 造 · 老 K P W 改 造 记

AI 把我的老 Kindle 救回来了

一次有报错、有吐槽,最后真的能读书的积灰设备改造

图片

文中漫画由 AI 生成,仅作流程示意

Kindle 有个流传很广的外号,泡面盖。说的是它买回家读不了几本书,最后被拿来压泡面。

我家也有一台。2015 年款的 Paperwhite 3,六英寸墨水屏,充一次电能撑小半个月,当年出门基本都会带上。后来它被放到一边,偶尔翻出来,翻两页又放下。书架角落那层灰,就这么积起来了。

这事不能全怪机器。

2023 年 6 月 30 日,亚马逊中国关停了 Kindle 电子书店,新书买不到,硬件也不再销售。2024 年 6 月 30 日,云端下载服务关闭,之前没下载到本地的书再也没法拉下来,Kindle 中国的客服支持也在同一天结束。

推送没得更早。以前把一本 epub 用 Send to Kindle 发过去,几分钟就能在屏幕上读。这条路现在走不通。

剩下的是本地那点功能。存着的书还能读,阅读进度和笔记不再同步,账号一旦退出登录,已经下载的内容还会被清空。它像一台只能读存量、进不了新书的单机机器。原生系统对如今最常见的 epub 支持也不好。

一台还正常工作、却没有内容来源的设备。扔掉可惜,用着不顺手,就这么搁着,继续积灰。

转念想了一下,不如试着用AI改造一下?说干就干!

01 先弄清它到底是什么型号

图片

这次我把任务定得比以往都具体。先认清型号和固件,把资料备份好,再查官方向导。只有匹配到适配方案才能往下走,安装包只用官方发布的版本。需要我在 Kindle 屏幕上操作的地方,及时叫我。

老 Kindle 外形都差不多,安装包的名字也容易看花眼。型号认错一步,后面全是白折腾。

AI 报回来的结果是 Paperwhite 3,第 7 代,Wi-Fi 版,固件 5.16.2.1.1。再跟着 KindleModding 的官方向导查,匹配出来的方案是 WinterBreak2。

我特意让它把结论和判断依据一起给我,别只丢一个包名过来。网上流传的教程大多不带设备条件,照着做,很容易在某个不起眼的步骤上停住。

02 备份 1.45 GB,只为不出事

图片

准备工作里最没存在感的一步是备份,也最不能省。

USB 能读到的资料全部复制到 Mac,895 个文件,约 1.45 GB。复制完不算完,还要逐个核对 SHA-256,确认复制前后没有差异。这样一来,旧书和批注先有了落点,后面真出状况,可以对着记录找原因,不用靠文件名猜哪个包是不是可靠。

另一件事是防自动更新。越狱过程中如果机器自己悄悄下载了系统更新,前面的活可能白干。办法是往里塞占位文件,把剩余空间压到约 80 MB,让更新没有落地的余地。等永久更新屏蔽验证通过,再把占位文件删掉。

听起来都挺琐碎。真出事的时候,能救你的往往是这些琐碎。

03 报错、卡住,我催了它一句

图片

第一个跟头来得很快。我在电脑浏览器里打开越狱入口,页面直接报错。

AI 检查了响应,解释说那个入口给 Kindle 的实验性浏览器准备了特殊响应头,电脑浏览器不认,会直接拒绝。换到 Kindle 本机打开,才是官方向导要求的做法。这一步在教程里常被一笔带过,不少人也就停在这儿。

更磨人的在后面。验证入口总算出现在书库里,点下去,屏幕一直停在“正在打开”,没有任何变化。

屏幕就一直停在那行字上。我问它,这对吗。

“你成功率能不能高一点啊。”

重新接上 USB,从机器里读出了验证报告。脚本确实以 root 权限运行过,Hotfix 文件和更新的公钥都对得上,OTA 程序已经屏蔽,没有更新进程在运行。检查是完成了,界面没有正常返回,屏幕上那行“正在打开”,只是没刷新过来。

我那句催它的话,也留在了这次对话里。

04 屏幕上终于出现 KOReader

图片

有了这份验证报告,才轮到装阅读器。

对应这台机器的安装包是 KOReader 的 kindlepw2 版本。觅阅选的是正式版 6.0.0,为的是保留正式更新通道。文件复制进去,又回读核对了一遍,1,276 个文件。

然后就是看得见的结果了。我拔下数据线,在 Kindle 书库里点开 KOReader,进去了。

图片

装它图什么,也值得说清楚。Kindle 原生系统只认自家那几种格式,PDF 在六英寸屏上基本没法读,现在最常见的 epub 得先转。KOReader 是开源阅读器,epub、PDF、TXT、漫画包都直接打开,扫描版 PDF 还能重排,字体、行距、页边距、词典都能自己调。旧机器上它的翻页速度通常比原生系统还快。

觅阅也已经装进 KOReader,入口在顶部工具菜单,名字是“觅阅 · 微信读书助手”。它接的是微信读书,等于把现在的书库重新接回这台老机器。连上 Wi-Fi,用微信扫码确认,登录这一步也走通了。

到这儿,这台 2015 年的机器才算真的回到了日常。屏幕没坏,电池也没坏,卡住它的是内容进不来。

一台被官方放下的机器,重新有了内容来源。

05 一台积灰的设备,和立马行动起来

这次改造我也算多做了两件事。一件是把型号、固件、备份清单、验证报告都存了档,万一以后要回滚,不用重新猜。另一件是记下了每一步的官方依据,出问题先查依据,再决定要不要继续。

有风险的地方也要讲清楚。越狱属于有风险的折腾,方案随型号、固件和时间变化,我这台的安装包只对这次匹配出来的设备条件负责。真要动手,跟着当前官方向导走,备份和校验一步都别省。

装好之后还有几件长期要做的事。固件别手动升级,根目录里出现的更新文件定期清掉,平时用不上 Wi-Fi 就关掉。这几条在公开教程里被反复提醒,因为它们决定越狱能不能长期有效。

AI 在这次改造里处理掉的,是原本最耗时间的部分。翻资料、对版本、核文件、解释报错,报错了它也不烦,接着往下查。我负责接线、点屏幕,看到什么现象就告诉它。

把我卡在那台机器前面的,和技术没什么关系。它有几年时间就静静躺在抽屉里,我却一直没动手。最后把它拿出来的那个下午,事情就走完了。

折腾完这一台机器,我改了原来的想法。让人停在原地的,常常是另一种情况。手里有一台还能用的设备,心里有一件想做没做的事,一直往后推,等一个不忙的时候。

那个不忙的时候,通常不会自己来。

图片

AI 时代最怕的,可能就是你还没行动起来。

我的老 KPW,先继续读下去。

梦迪早七点

Source: https://mp.weixin.qq.com/s/yPtJXdxX9eF3HYv9_cDmwg If you have any copyright concerns, please contact us at 13951431913#139.com or submit a comment on the right.

Dusty Equipment Retrofit · A Story of Old KPW Revival

How AI Brought My Old Kindle Back to Life

A dusty equipment makeover with bugs, gripes — and, in the end, a device that actually reads books again

图片

The illustrations in this article are AI-generated and serve as process diagrams only.

Kindle has a widely known nickname: the instant noodle lid. It refers to the fact that you buy it, read a few books, and then it ends up being used to weigh down your instant noodles.

I have one too — a 2015 Paperwhite 3, six-inch e-ink screen, a single charge lasting nearly half a month. I used to bring it everywhere. Later it got set aside, occasionally dug out, read for a couple of pages, then put back down. The dust in that shelf corner just kept accumulating.

But this isn't entirely the device's fault.

On June 30, 2023, Amazon China shut down the Kindle eBookstore — no more new books could be purchased, and hardware sales ceased. On June 30, 2024, cloud download services were disabled, meaning books not yet downloaded to the local device could never be retrieved again, and Kindle China customer support ended on the same day.

I should have pushed content earlier. In the past, I'd send an epub via Send to Kindle and have it reading on the screen within minutes. That path is now closed.

What remains is purely local functionality. Stored books can still be read, but reading progress and notes no longer sync. If you log out of your account, already downloaded content will be cleared. It's like a standalone machine that can only read existing content — new books can't get in. The native system also handles the most common epub format poorly.

A device that still works, but has no content source. Pity to throw it away, awkward to use as-is, so it just sits there, gathering more dust.

Then I thought — why not try retrofitting it with AI? Let's do it!

Step 01: Figure Out Exactly What Model It Is

图片

This time I set the task more specifically than ever before. First identify the model and firmware, back up all data, then look up the official guide. Only by matching the right solution can we move forward, and only official releases should be used as installation packages. I asked AI to call me out anytime it needed me to operate on the Kindle screen.

Old Kindles all look similar, and package names are easy to confuse. One wrong model guess and everything downstream is wasted effort.

AI reported the result: Paperwhite 3, 7th generation, Wi-Fi version, firmware 5.16.2.1.1. Cross-referencing with the KindleModding official guide, the matching solution came back as WinterBreak2.

I specifically asked it to provide both the conclusion and the reasoning behind it, not just throw a package name at me. Most tutorials circulating online don't specify device conditions, so following them blindly easily hits a dead end at some obscure step.

Step 02: Back Up 1.45 GB — Just to Be Safe

图片

The most invisible step in preparation is also the one you absolutely cannot skip: backup.

All data readable via USB was copied to my Mac — 895 files, approximately 1.45 GB. Copying wasn't the end; I verified each file's SHA-256 hash to confirm no differences between source and destination. This way, old books and annotations have a safe landing point, and if anything goes wrong later, I can trace the cause from the records instead of guessing which package is trustworthy by filename alone.

The other concern was preventing automatic updates. During the jailbreak process, if the device silently downloaded a system update, all prior work could be undone. The fix was to塞 placeholder files into it, reducing remaining free space to about 80 MB, leaving no room for an update to land. Once permanent update blocking was verified, I removed the placeholders.

It all sounds tedious. But when something actually goes wrong, it's often these tedious steps that come to your rescue.

Step 03: Error, Stuck — I Prompted It

图片

The first stumble came quickly. I opened the jailbreak entry page in my computer browser, and it threw an error immediately.

AI checked the response and explained that the entry page sends special response headers intended for Kindle's experimental browser — a computer browser doesn't recognize them and rejects the page outright. The correct approach, as the official guide requires, is to open it directly on the Kindle device itself. This step is often glossed over in tutorials, and many people end up stuck right here.

The harder part was yet to come. The verification entry finally appeared in the library. I tapped it, and the screen kept stuck on "Opening," with no change.

The screen just stayed on that line. I asked it, Is this supposed to happen?

"Can your success rate be a bit higher?"

I reconnected the USB and pulled the verification report off the device. The script had indeed run as root, the Hotfix file and updated public key both checked out, and the OTA program was blocked with no update process running. The check was complete — the UI just hadn't refreshed. That "Opening" line on screen was all that was left unresolved.

My prompt to hurry up also stayed in that conversation log.

KOReader finally appeared on screen.

图片

With that verification report in hand, it was time to install the reader.

The matching installer for this device was the kindlepw2 version of KOReader. MiYue selected the stable release 6.0.0, to keep the official update channel open. I copied the files in, read them back to verify, and confirmed all 1,276 files.

Then came the visible result. I unplugged the data cable, opened KOReader from the Kindle library, and it launched.

图片

Why go through all this trouble just to install a reader — that deserves an explanation. The native Kindle system only recognizes its own formats. PDF is basically unreadable on a six-inch screen, and the most common format, epub, needs to be converted first. KOReader is an open-source reader that opens epub, PDF, TXT, and comic archives directly. It can reflow scanned PDFs, and lets you customize fonts, line spacing, margins, and dictionaries. On older devices, its page-turn speed is often faster than the native system.

MiYue was also installed into KOReader. The entry appears in the top toolbar, labeled "MiYue · WeChat Read Assistant." It connects to WeChat Reading, effectively re-linking the current library to this old device. Connected to Wi-Fi, scanned the QR code with WeChat, and the login step went through.

At this point, this 2015 device truly returned to daily use. The screen wasn't broken, the battery was fine — what held it back was simply the inability to get content onto it.

A device abandoned by the manufacturer now had a content source again.

05 A dusty piece of hardware, and the act of just getting started

This改造 also included two extra things I did. First, I archived the model number, firmware version, backup manifest, and verification report — so if rollback becomes necessary someday, there's no guessing. Second, I recorded the official source for every step, so if anything goes wrong, I can check the documentation before deciding whether to proceed.

The risky parts need to be stated clearly. Jailbreaking is inherently risky. The approach varies by model, firmware, and time. The installer I used is only valid for the exact device conditions I matched this time. If you're going to do this yourself, follow the current official guide step by step, and never skip backup or verification.

After installation, there are a few long-term habits to maintain. Don't manually upgrade the firmware. Clear any update files that appear in the root directory on a regular basis. Turn off Wi-Fi when you don't need it. These points are repeated in public tutorials again and again, because they determine whether a jailbreak remains effective over time.

What AI handled during this改造 was the part that used to take the most time: searching documentation, cross-checking versions, verifying files, and decoding error messages. Even when errors came up, it didn't get frustrated — it just kept investigating. I handled plugging in cables, tapping the screen, and reporting whatever phenomenon I saw.

What kept me stuck in front of that machine had nothing to do with technology. It sat quietly in a drawer for years, and I never found the moment to act. In the end, the thing that unblocked everything was simply picking it up one afternoon.

After completing this改造, I changed my original way of thinking. What holds people still is often something else entirely: you have a working device in hand, something you want to do on it, and you keep putting it off, waiting for a less busy time.

That less busy time usually never comes on its own.

图片

The thing most to fear in the AI era might be this: you haven't even started moving yet.

My old KPW — let's keep reading.

Meng Di, 7 AM

暂无评论,快来发表第一条评论吧!No comments yet. Be the first!

📮 需求咨询📮 Inquiry