Getting Started

Welcome to the S1 Pro Docs documentation. This guide walks you through discovering your scooter on your local network, communicating with its onboard diagnostic interface, and enabling a fully functional wireless ADB connection with root access.

No Hardware Modifications Required

Everything documented here works over Wi-Fi. You do not need to disassemble the scooter, splice CAN bus wiring, or open the dashboard.

Choose Your Setup Method

You can unlock and pair with your scooter using either method:

PC Setup Guide (Terminal)

Manual developer workflow. Use your computer with s1util.py and standard Android SDK platform tools for full command-line control.

Start PC Guide →

Android App (No PC Required)

All-in-one mobile workflow. Run discovery, ADB key pairing, and mode switching directly from your Android phone on the same Wi-Fi network.

Use Android App →

---

PC Setup Roadmap

If you are using a computer, follow these sections to set up your environment and connect to your head unit:

1. Network Discovery Connect your scooter to Wi-Fi, locate its link-local IPv6 address, and determine your network interface scope ID.

2. Verifying Connection Send a probe to the onboard diagnostics service on TCP port 50005 to confirm gRPC communication.

3. Enabling ADB Authorize your ADB public key and switch the scooter to manufacturing mode to enable wireless ADB access.

4. ADB Access & Control Connect via wireless ADB, launch an interactive root shell, mirror your dashboard display with scrcpy, and sideload applications.

Quick Navigation

Network Discovery

Find your scooter’s IPv6 link-local address on your local network.

Find Address →

Verify Connection

Test the gRPC diagnostics interface on port 50005.

Test Interface →

Enabling ADB

Pair your public key and unlock wireless ADB access.

Enable ADB →

ADB Access & Control

Connect via ADB, spawn a root shell, and mirror your screen.

Open ADB →

---

Safety & Boundaries

Before beginning, it is important to understand what this unlock touches and what it leaves strictly alone:

What This Controls (Android Head Unit)

• Android display, launcher, and touch interface
• Wireless ADB access and command-line shell
• Native Android Settings app and sideloaded APKs
• Reading live vehicle telemetry from the virtual CAN socket (vcan0)

What This Leaves Untouched (Vehicle ECUs)

• Motor controller (VCU): Throttle curves, speed limits, and power delivery
• Battery Management System (BMS): Safety cutoffs, thermal thresholds, and cell balancing
• ECU Firmware: We strictly avoid flashing or modifying vehicle microcontroller binaries

Vehicle ECUs & Firmware Update Boundaries

While root access on the Android head unit technically exposes low-level access to update routines capable of flashing individual ECU microcontrollers over the CAN bus, this project strictly does not cover, provide instructions for, or support modifying ECU firmwares.

Attempting to alter or flash vehicle controller firmware carries severe risks, including permanently bricking vehicle electronics, disabling vital safety cutoffs, and voiding warranties. We will not guide users through ECU flashing, nor can we assist in diagnosing or recovering damaged controllers if attempted. All tooling and procedures in this project operate exclusively within the Android head unit userland and passive telemetry monitoring.