Codex Helped Me Rescue Texts From an Old Android Phone
Bruce Hart
The most useful AI projects are not always glamorous. Sometimes they are just the ones that finally get an old, annoying, emotionally important task across the finish line.
I have an Android phone that is more than 10 years old. It still boots, technically. But it is stuck in the past in all the ways old phones get stuck.
It runs Android 6. Google Play does not really work. Gmail does not really work. Account login is broken enough that most of the normal routes are closed. The phone is alive, but it is not meaningfully connected to the modern internet anymore.
I wanted one thing from it: my text messages.
Not because I needed them for some practical purpose. Because there are memories in there. The earliest messages between me and my wife are on that phone, from when we first started dating. I already had SMS archives from other phones, but this one gap had been bothering me for years.
The funny thing is that the job was probably always possible.
It just sat in the category of things that were possible, annoying, and easy to postpone forever.
The hard part was not one big technical wall
I did not have SMS Backup and Restore installed on the phone. Normally that would be the obvious tool: install the app, make an XML backup, upload it somewhere, move on.
But the Play Store was not usable. I could have tried to update Android, update Google services, update the apps, nurse the whole thing back to life, and hope the old hardware cooperated. Maybe that would have worked. Maybe it would have taken an afternoon and ended with the same login error.
That is the kind of ambiguity that kills little preservation projects.
You do not know if you are 20 minutes away or four hours away. You do not know if the next step is safe. You do not know if the old device is going to get more fragile as you poke at it.
So I opened Codex and asked it to help me think through the path.
The good suggestion was not magic. It was practical: stop trying to fix the phone as a phone. Treat it as an Android device you can reach with developer tools.
Install ADB. Connect over USB. Manually install the APK. Use the phone just enough to create the export.
That was the shift.
Not "restore the ecosystem," but "extract the artifact."
ADB turned the phone back into a computer
Codex walked me through installing ADB and using it to talk to the device from my computer. Then it helped me manually install SMS Backup and Restore without using the Play Store.
Once the app was on the phone, I could run the backup and create the SMS XML file locally.
That felt like the finish line for about 30 seconds.
Then I hit the next boring wall: I still could not get the backup off the device in any normal way.
No Google Drive upload, because I could not log in. No easy cloud share. No account-based escape hatch. And when I saved the file locally, the app did not want to put it in some obvious folder I could casually browse from my computer.
This is where Codex was genuinely helpful again. It suggested places to save the file that would be visible enough to ADB, then helped me pull the exact file directly from the phone to my computer.
That is the sort of step I used to lose steam on.
Not because it is impossible. Because it is a stack of friction: where did Android 6 put that folder, what permissions apply, what is the exact adb pull path, why is this file browser hiding the thing I need, what do I try next?
Codex did not need to be brilliant. It needed to keep the thread moving.
Agents are good at reducing activation energy
This is one of the places where I think coding agents are quietly underrated.
The headline examples are big: generate an app, refactor a codebase, automate a workflow, wire up infrastructure.
But the everyday value is often smaller and stranger. There is a class of personal tech chores that are too custom to be productized and too fiddly to be worth doing by hand.
Recover this old archive. Convert this weird file. Extract these attachments. Rename this pile of photos. Make this one-off HTML view. Merge these backups into a local SQLite database.
None of those are moonshots. They are just annoying enough to sit undone.
Codex changes the activation energy. It lets me start with, "Here is the messy situation," and then work step by step without having to hold the whole map in my head.
In this case, the whole project took less than an hour.
I got the XML file off the device, uploaded a copy to Google Drive for safekeeping, and then had Codex run scripts I already had for importing SMS backups into my archive. The messages now live in SQLite, searchable and accessible, alongside the archives from my other phones.
I also had Codex extract the messages between me and my wife from those early dating days and generate a simple HTML file I can keep in Drive. Nothing fancy. Just a readable version of the conversation that started one of the most important parts of my life.
The archive matters because the life changed
Reading those messages was more emotional than I expected.
There we were, over 10 years ago, figuring each other out one text at a time. Now we have been married for almost a decade and have two growing kids who are busy building lives of their own.
It is strange to see the thin little thread at the beginning of something that became your whole life.
My parents kept letters they sent to each other when they were dating. I always liked that. It felt tangible and deliberate. My generation has a messier version of the same thing: SMS databases, XML exports, old phones in drawers, cloud backups that may or may not exist, and memories trapped inside apps that were never designed to last forever.
So yes, this was a technical project.
But mostly it was a preservation project.
And the lesson for me was not "AI can recover old text messages." The lesson was smaller and more useful: an agent can sit beside me while I do the awkward, specific, non-repeatable work that otherwise never quite gets done.
Because sometimes the thing you are recovering is not data in the abstract. It is a little piece of the path that got you here.