Plaud

Current focus: writing our own firmware for the device.

What this is

We own a Plaud Note Pro — a voice recorder that leans hard on its companion app and cloud pipeline. We want to personalize it (starting with the on-screen art), but the stock firmware and app won't allow it. So the path we've committed to is writing our own firmware for the hardware itself, done carefully and reversibly: nothing gets written to the device until a known-good stock dump exists.

How we got here

  1. Recon without touching the device (Sep 16) — FCC filing photos and manuals gave us the internals: board layout, an exposed debug pad row, and the assembly story before we ever opened anything.
  2. Mined the official Android app (Sep 16–19) — mapped how it talks to the device (Bluetooth protocol, cloud API, update flow) and disassembled the firmware-update path down to how update keys are delivered. Learned that USB file transfer was permanently gated off by the vendor's firmware.
  3. Bench tests (Sep 17–19) — tried the least-invasive physical footholds first: the pogo-pin factory cable doesn't enumerate a data or serial interface (a clean dead end), and live Bluetooth probing proved the Pro silently rejects every plaintext command — its command layer is encrypted with per-pairing keys.
  4. Traffic capture (Sep 20) — captured and mapped the app's cloud traffic structure, confirming there's no hidden command door we missed.
  5. Verdict — there is no remote hook to piggyback on. Customization has to come from firmware we control.

Where we are now

Research phase is done; the device is still stock and untouched. Next stage is the firmware work itself: identify the SoC and flash layout from a dump, then build and flash our own image — staged, least-invasive-first, with a full rollback at every step.

Notes: this is a personal, non-commercial modification project on hardware we own. Vendor names are used descriptively; no affiliation.

← Back home