And under Connected Devices : a second entry, labeled simply: Gear.01.

Now it was midnight. Rain tapped the window. Leo had spent three hours reading forum posts— “Bricked my Ninebot after update” — “Try the ST-Link method” — “Just buy a new controller board.” But Daisy wasn’t just a scooter. She was the last thing his dad had helped him buy before the move. They’d test-ridden her down the boardwalk, his dad laughing at the “futuristic spaceship noise” the motor made.

Leo smiled, folded Daisy, and tucked her into the corner. Tomorrow, he’d ride to the boardwalk. He’d sit on the bench where his dad used to laugh, and he’d listen to that ghost in the gears.

He picked up his phone one more time. A fresh thread had appeared, posted eleven minutes ago: “Ninebot firmware recovery – unofficial rollback tool.” The author was a user named GhostInTheGears. The instructions were terrifying—disassemble the deck, short two pins on the BMS, connect via a modified USB cable—but the final line read: “Brings any bricked Ninebot back to life. Tested on Max G30, G2, and F-series.”

The first thing Leo noticed was the silence.

He’d retried. Twice. The second time, the screen went black and never came back.

And for the first time in a long time, the silence didn’t feel wrong. It felt like waiting—for the next ride.

Not the quiet of an empty street at 2 AM, but the wrong kind of silence—the kind that comes from a machine holding its breath. His Ninebot electric scooter, Daisy, sat on the living room rug like a sleeping metal dog. The dashboard was dark.

Leo typed a message to GhostInTheGears: “It worked. Who are you?”