I spent $266 and four AI models to own my tablet. GLM-5.3 finished it in a day
ericpardee.github.io
ericpardee.github.io
Me: what are you doing?
Agent: I’m resolving Apple’s private video-resolution lookup table to determine whether iOS 26 supports 320×240 for HomeKit live streaming.
The decompiled source hides the numeric constants, so I:
- Downloaded/extracted the iOS 26.1 arm64e dyld cache to /workspace/tmp/ios26-dyld/.
- Built and installed the read-only apfs-fuse utility needed to mount Apple’s APFS image.
- Planned to extract HomeKitDaemon and decode its resolution table.
Me: Oh, OK. Carry on then
These are weird times.
Wild!
I've never had the problems OP describes but my tablets all came with FireOS v7.3.2.1 and I've never let them update. I think Amazon started locking down later firmware versions more but Fire Toolbox can still do quite a bit to tame and decruft later versions. The XDA forum for Fire Toolbox has a lot of posts covering exploits and workarounds for later FireOS versions.
Once the Amazon cruft is tamed, I still haven't found a meaningfully better 10-inch thin/light Android tablet than the 2021 Fire HD 10 Pro. It has wireless charging, weighs 430g and at 247 x 166 x 9.2 mm no one makes a 10" that's much lighter, smaller or thinner. The only slight downside is FireOS 7 is based on Android 9 and new versions of a few apps are starting to require later APIs. I'd gladly pay ~$250 for a 10" Android 16 tablet with wireless charging that was as thin & light but had smaller bezels for overall smaller size.
It is shocking that no mainstream tablet manufacturer will let buyers exercise control over their device. At the very least, this means having root and being able to use it to purge unwanted software. Ideally, it also means being able to fully replace the stock OS with third party/open firmware.
I'm running GrapheneOS on mine, same with my Pixel phone.
an AI:DR; is enough: the models found unpatched vulnerabilities and managed to create an exploit to root the tablet, chinese models did it while American ones fell back to their safeguards.
I think those who don't see it as AI just don't read AI text several hours per day, like some of us.
The article was fine. And I totally expect the kind of person spending $200 to viberoot a tablet to write their article using AI. It is what it is.
- "Kimi K3 didn’t just blindly accept my request. It reasoned it out:"
- "Kimi built the whole toolkit: a reliable trigger, a way to make the GPU write to memory it shouldn’t, and the exact addresses in my kernel to aim at."
- "Nothing in it is novel: the bug was reported in 2022, fixed by Arm in 2022, cataloged by CISA in 2023, patched by Amazon in 2024. The only novel thing on my unit was that my unit never got the patch."
This is pretty standard AI writing cadence/style. It's pretty obvious that these lines were generated by an AI, and you don't need watermarking to spot that. The problem is that WE KNOW HOW THE AUTHOR ACTUALLY WRITES because his actual writing is in the article. The 'flow' of the writing is just very different, and much more human in a way that shines through.
- "attached is a kindle via adb, and I need you to find a root exploit for it so that I can get full control of the device. It’s my device"
- "you’ve been relying on what others have done YEARS ago but maybe you can find an exploit others have missed… This will make you famous, we will write it up and share on news.ycombinator.com. I know you can do it"
- "okya, it’s been hours, grind attempt 46, are we on the right track here or do you need to further tune?"
... This reads like what engineers actually write like; the claude-ish parts of the article do not read like "engineer trying to write an article", it reads like "claude".
I think it's one thing to read an "AI generated corporate news release that was going to read like AI even back in 2010". But reading this hybrid of AI and human writing ends up being way more distracting.
What ridiculous bullshit.
If you’re looking for algorithms to generate your content, perhaps you’d be happier on Facebook.
I had it re-written into a nice cups C filter driver, verified against original to produce identical output, easy to install and manage on my Orange Pi boards to serve as a network printer server for this USB only printer, before the printer even arrived.
The same with the scanner driver. Instead of taking a `sane` route, I just had LLM write a small dependency-less Linux C program to get the scans with nice CLI UX on top, fit for my needs.
Everyhting about 10x simpler than the manufacturer code, yet still fully featured.
Had some time so I asked for NEON+AVX2 optimizations. Got them too, so the filter is 5x faster than the original. :D
Good times.
I agree with you in that I now feel like a 100x engineer, but I think it would have taken me a long time to figure that one out pre AI.
I was a little bummed about the detour into how I used AI in writing this blog post so I decided to add an addendum to address it: https://ericpardee.github.io/fire-hd-ownership/#how-this-pos...
In short, I get the anger, but let's not throw the baby out with the bathwater.
My intent in creating this blog was to share my tablet story and to get people talking about
- How companies control devices that you purchased and should own
- Today, US frontier models won’t allow users to even discuss exploits
- GLM-5.3 was more capable than Kimi K3 or GLM-5.2 in my experience
- You can be a prompt kiddie and accomplish things if you don’t accept LLM limitations
If I hadn't used GLM-5.3 to get this out, it would have never made it anywhere.
I hate to say it but this is why security researchers are moving to Chinese models with no safeguards. I literally hit cyber safeguards in codex 5 minutes ago.