# My Car Needed a Jailbreak to Change the Clock

> My car needed a jailbreak to change the clock: a 2014 Renault read Settings off a DRM-locked map card. The house rule is that basic settings stay local.

- Canonical URL: https://webofmike.com/my-car-needed-a-jailbreak-to-change-the-clock/
- Author: Mike Moore (https://webofmike.com/about/)
- Published: 2026-11-19
- Last modified: 2026-11-08
- Tags: Home Automation, House Series, Local First
- Cite as: Mike Moore, "My Car Needed a Jailbreak to Change the Clock", Web of Mike (webofmike.com), 2026-11-19. https://webofmike.com/my-car-needed-a-jailbreak-to-change-the-clock/


<!-- ART: a dark dashboard. The only thing lit is a clock reading 4:04. Never explained. -->

A 2014 Renault needed a jailbreak to change the clock because the TomTom head unit stored the Settings menu on a DRM-locked navigation SD card, so without a legitimate card the clock option never appeared. The actual fix was one integer, 180 minutes to 120. The house rule: if a basic setting is not reachable locally, it does not go in the house.

Daylight saving time ended in Estonia and the guy behind [nns.ee](https://blog.nns.ee/2026/11/02/renault-hack) went to fix the clock in his 2014 Renault Latitude. Normal Sunday chore. Push a few buttons.

The option wasn't there.

There were two Settings buttons. One handled Bluetooth and the phonebook. The other popped up "No maps detected!" every time he pressed it. When he bought the car, the previous owner had asked if he wanted the navigation map SD card, and warned him the car needed it to change the clock. He didn't believe it. The maps were out of date and he navigates on his phone. The card got tossed.

The previous owner was right.

## Why did a Renault need a jailbreak to change the clock?

This is not my car and not my exploit writeup. It is a public reverse-engineering post about a 2014 Renault Latitude, a TomTom Carminat LIVE head unit (codename beaumont), Linux 2.6.28.10, and a clock that would not move when Estonia switched from UTC+3 to UTC+2.

He spent about an hour in the menus anyway. Online videos of similar units showed a Set time option. His unit didn't. The dashboard had already been showing a large "No maps found!" message. He had ignored that. The missing clock option was the part he refused to believe.

A replacement map card, with shipping to Estonia, was roughly 60 EUR. He did not want maps. In his words, "I don't want maps. I have a phone that I use for navigation. I just want to change the damn time."

So the choice on the table was: buy a licensed map product to reach a clock, or get root and change the offset himself. He chose the second. I'm not going to repeat the path. Read his post for the details. The hack isn't the lesson. The coupling is.

## Where did the Settings menu actually live?

He pulled the firmware. Other people had already mapped some of this unit (he points at a French Carminat TomTom LIVE reverse-engineering repo for the update URLs). The update package included a `ttsystem` ext3 image of the root filesystem. The SoC is a Samsung S5P6440 running TomTom's OS on that 2.6.28.10 kernel.

After reading it, he concluded the previous owner was completely correct. There was no way to enter the correct settings menu without a navigation SD card inserted. The menu definition that points to the Settings applet was read from the SD card itself. No card, no Settings. The unit didn't even know how to open the applet.

And not just any card: the system checked the card's CID, a unique ID burned into the card, and signatures tied to it. You couldn't copy the files to a blank one. He guesses the DRM was there to stop people pirating maps. The clock got pulled along for the ride.

Nobody at TomTom or Renault sat down and decided to hold the clock hostage. Somebody put the menu definition next to the map data because it was convenient, somebody else added DRM to the map data to stop piracy, and the two decisions met in a dashboard years later. That's how it usually happens. No villain. Just coupling.

He also found the usual 2011-era hardening that makes a "just copy the files" story fail: partitions mounted read-only, `noexec`, or both. A signed update image. A UI scripting language loaded from the card that could not open the missing Settings applet. He built a QEMU emulator of the unit to test attacks without bricking the car. That is as far as this post goes. The rest is in his writeup.

## What was the actual clock fix?

Once he had root and a backup of the internal storage, he found the time settings. They live in a custom binary file at `/mnt/flash/settings.dat`. The unit has no concept of time zones at all. It gets the time from GPS and stores the local offset as a number of minutes.

His was set to 180. He changed it to 120.

That's it. That's the whole fix. One stored integer, sitting behind a DRM check on a map card he didn't want. Summer time in Estonia was UTC+3 (180 minutes). Winter time was UTC+2 (120 minutes). The car knew GPS time. It did not know the civil calendar.

The size of the fix is the point. The setting was local the whole time. The path to it was not.

A checklist I'd use on any device that claims to have a "setting":

- Can I see the control with the network unplugged?
- Can I change it with the vendor account expired or missing?
- Does the control live on the device, or on a content pack, subscription, or cloud round-trip?
- If the content pack is gone, does a basic function (clock, lock, setpoint, schedule) disappear with it?
- Is the actual stored value a local number I could read from a backup, or a lease from a server?

If the answer to the last two is "it disappears" and "it's a lease," you don't own the setting.

## What house rule does this set?

I've been building out my house for a while now, and this post is going on the wall as the rule I already try to follow: **every basic setting has to be reachable locally.** Not through a content download. Not through a subscription. Not through a cloud call that works until the vendor decides it doesn't.

The clock, the thermostat setpoint, the schedule, the lights, whether the door is locked. If I can't change it with the internet unplugged and the vendor's account expired, it's not a setting I own, it's a setting I rent.

That is the same local-first instinct as [run the model on the quiet chip](/run-the-model-on-the-quiet-chip/): a house box that has to talk to a vendor to do the boring thing is a house box I don't want running all day. Heat, power, and a missing menu are different symptoms of the same coupling.

It is also why the [house agent rereads its rulebook](/house-agent-rereads-its-rulebook/) from local instructions on a schedule. The rules live here. They are not fetched from a portal that can 404 the thermostat. When I evaluate a recorder, a lock, or a light, I want the same property [Pocket notes have when they land in a vault](/pocket-obsidian/): a file I can read with the account offline. Export is a setting you own. A menu that lives on a DRM card is not.

[Hardware is AI's teeth](/hardware-is-ais-teeth/) still applies in the garage. The head unit is hardware with a policy baked into a map SKU. Policy in the wrong layer is how a clock becomes a licensed product.

So when I evaluate anything for the house, the test is the boring one. Pull the network, pull the account, and try to change the most basic setting it has.

If it needs a jailbreak to change the clock, it doesn't go in the house.

