OpenXPlay Flasher v0.2.0-beta.2

Windows native USB flashing

• ADB and fastboot use native WinUSB, without requiring an external adb server. An already-running adb server remains supported.
• USB ports remain distinct across host controllers, and Windows PnP serial capitalization no longer breaks stock-device identity checks. Ambiguous device inventories and incorrect erase confirmations are still rejected.
• Missing interface drivers are reported explicitly. Install a matching WinUSB driver for each ADB or bootloader interface while preserving the RNDIS network adapter.

Hardware validation on Windows x64:

• The official Windows amd64 build completed all 49 steps of a full install from original Android 4.4 on a real UFI003, with exit code 0. It backed up and restored all four modem calibration partitions, wrote the base-system partitions including rootfs and boot, rebooted, and verified the installed device support and relay.
• The resulting system runs OpenStick with kernel 5.15.0-handsomekernel+, device support 0.2.1, and relay 0.1.5~beta.2.
• A second UFI003 already running OpenStick was upgraded from relay 0.1.5~beta.1 to 0.1.5~beta.2, with service verification. Native ADB reads, fastboot identity reads, RAM transfers of 4,096 and 2,097,153 bytes, and normal reboot also passed. Matching WinUSB drivers were installed without replacing the RNDIS network interface.

The signed beta package catalog is now at sequence 4 and recommends the corrected UFI003 device-support bundle 0.2.1, alongside OpenStick v1 and relay 0.1.5~beta.2. Refresh the package list before installing.

Builds remain preview software. Windows binaries are provided for amd64 and arm64; SHA256SUMS covers all release artifacts.

Windows 原生 USB 刷机

• ADB 和 fastboot 使用原生 WinUSB，无需外部 adb server；仍兼容已经运行的 adb server。
• 修复不同 USB 控制器端口混淆，以及 Windows PnP 序列号大小写导致的原厂设备身份校验失败。设备身份不明确或清空确认不正确时仍会拒绝操作。
• 缺少接口驱动时会明确提示；为 ADB 和 bootloader 接口分别安装匹配的 WinUSB 驱动，保留 RNDIS 网卡驱动。
• 官方 Windows amd64 安装包已在真实 UFI003 上，从原厂 Android 4.4 完成全部 49 步安装，退出码为 0：备份并恢复四个基带校准分区，实际写入基础系统分区（包括 rootfs 和 boot），重启后完成设备支持和中继验证。最终运行 OpenStick、内核 5.15.0-handsomekernel+、设备支持 0.2.1 和中继 0.1.5~beta.2。
• 另一台已运行 OpenStick 的 UFI003 也完成了中继 0.1.5~beta.1 至 0.1.5~beta.2 的升级和服务验证；原生 ADB 读取、fastboot 身份读取、两种大小的内存传输及正常重启均通过。
• 已签名的软件包列表升级至 sequence 4，推荐修正后的设备支持 0.2.1、OpenStick v1 和中继 0.1.5~beta.2。安装前请刷新软件包列表。

仍为预览版本，提供 Windows amd64 和 arm64 安装包，全部发布产物均附 SHA256SUMS。

OpenXPlay Flasher v0.2.0-beta.1

OpenXPlay Flasher 0.2.0-beta.1: install OpenXPlay on a UFI003, from its original firmware or one layer at a time

Install OpenXPlay on a UFI003 USB dongle from its original firmware, or update a single layer, in the app or from the command line; the command line also lets an AI assistant do the install. · 在 UFI003 随身 Wi-Fi 上从原厂固件开始安装 OpenXPlay，或单独更新某一层；可以用应用，也可以用命令行，命令行还可以交给 AI 助手完成安装。

New

• Installs and updates the three layers of a UFI003: the base system (OpenStick Debian 11), device support and the OpenXPlay relay. A brand-new dongle with its original Android firmware is installed in one go, in about 6 to 7 minutes; later, usually only the relay needs updating.
• Before the base system is written, Flasher backs up the dongle's modem partitions (calibration data and IMEI) to OpenXPlay Backups in your Documents folder, and only ever writes this dongle's own backup back. Actions that erase the dongle ask you to type its serial number.
• A signed package list on openxplay.org gives each layer's version, download links and SHA-256. Flasher never downloads packages: you download them from the links and Flasher recognises them by SHA-256. The signature check can be turned off in Settings for your own lists.
• Guided steps: Connect, Choose, Prepare, Back up, Flash, Done, with a summary before you start, the dongle's name and serial in the confirmation, and Repair for an interrupted install.
• Next steps whenever a dongle with the relay is connected: add your CarPlay identity (key and certificate, or a ZIP) and open the relay's admin page over USB.
• Command line for scripts and AI assistants: status, files, plan, install, identity and admin, with JSON output. Install instructions written for AI assistants: https://openxplay.org/agents/ufi003-install.md
• Phicomm N1 over SSH on the network (preview): connect with the address, user name and password or key. Its packages are not in the package list yet, so this release cannot install anything on it.

Fixed on real dongles

• Brand-new dongles: the original Android 4.4 firmware is recognised (its shell has no printf).
• Installing from the original firmware no longer stops halfway through the boot chain: after the new partition table is written, sizes are checked against that table, and every image is checked before the first critical write. If an install is interrupted there, Repair continues from the unfinished step without restarting the dongle.
• Installs wait for the dongle's daily apt job, which can start as soon as its clock is set, instead of failing with "exit 1", and failed steps show the dongle's own message.

Notes

• macOS 12 or later (Apple silicon and Intel) and Windows 10/11 (x64 and Arm64). On Windows, Flasher can install and update device support and the relay only, and adb must be running; the first install needs a Mac.
• The builds are not signed with an Apple or Microsoft certificate; https://openxplay.org/en/ufi003-relay#flasher-download shows how to open them.
• Known limits: the corrected install from the original firmware has been tested with simulated devices; on a real dongle every step except the boot-chain fix has been tested. You supply your own Apple accessory (MFi) identity; no package contains one.

新增

• 安装和更新 UFI003 的三层：基础系统（OpenStick Debian 11）、设备支持和 OpenXPlay 中继。运行原厂 Android 固件的全新随身 Wi-Fi 一次即可装好，约 6 到 7 分钟；之后通常只需要更新中继。
• 写入基础系统前，Flasher 会把这台设备的基带分区（校准数据和 IMEI）备份到“文稿”文件夹中的 OpenXPlay Backups，并且只会写回这台设备自己的备份。会清空设备的操作都要输入设备序列号确认。
• openxplay.org 上的签名软件包列表给出每一层的版本、下载链接和 SHA-256。Flasher 从不下载安装包：你按链接下载，Flasher 按 SHA-256 识别。使用自己的软件包列表时，可以在“设置”中关闭签名校验。
• 引导步骤：连接、选择、准备、备份、刷写、完成。开始前先显示安装摘要，确认时显示设备名称和序列号，安装中断后可以“修复”。
• 只要连接着已安装中继的随身 Wi-Fi，就可以在“接下来”中添加 CarPlay 身份（私钥和证书，或 ZIP），并通过 USB 打开中继管理页面。
• 供脚本和 AI 助手使用的命令行：status、files、plan、install、identity、admin，可输出 JSON。写给 AI 助手的安装说明：https://openxplay.org/agents/ufi003-install.md
• 斐讯 N1 通过网络 SSH 连接（预览）：输入地址、用户名和密码或私钥即可连接。它的安装包还不在软件包列表中，这个版本还不能为它安装任何内容。

在真机上修复的问题

• 全新随身 Wi-Fi：能识别原厂 Android 4.4 固件（它的命令行没有 printf）。
• 从原厂固件安装时不再在写入引导链途中停下：写入新的分区表后，按新分区表核对大小，并且在第一次关键写入前核对所有镜像。如果在这一步中断，“修复”会从未完成的步骤继续，不重启设备。
• 设置设备时间后，系统每日的 apt 任务可能立即开始；安装会等它结束，不再以“exit 1”失败，失败的步骤也会显示设备给出的原因。

说明

• 支持 macOS 12 或更高版本（Apple 芯片和 Intel）以及 Windows 10/11（x64 和 Arm64）。Windows 上只能安装和更新设备支持与中继，且需要先运行 adb；第一次安装需要 Mac。
• 安装包没有使用 Apple 或 Microsoft 证书签名，打开方法见 https://openxplay.org/ufi003-relay#flasher-download 。
• 已知限制：修正后的原厂固件安装流程已用模拟设备测试；在真机上，除引导链的这项修复外，其余每一步都已测试。Apple 配件（MFi）身份需要你自己提供，任何安装包都不包含。

OpenXPlay Flasher v0.1.0-beta.1

OpenXPlay Flasher 0.1.0-beta.1: first preview that detects devices and shows their layers

New

• Desktop app for macOS 12 or later (Apple silicon and Intel) and Windows 10/11 (x64 and Arm64), in English and Simplified Chinese.
• Finds a UFI003 USB dongle in adb, fastboot or EDL mode from its device profile and shows the layers it can install: base system, device support, OpenXPlay relay.
• Other Android devices are listed apart and ignored.
• Command line: devices, watch, profiles, version.

Notes

• Preview only: this version does not write to any device.
• The builds are not signed. See the README for how to open them on macOS and Windows.

新增

• 适用于 macOS 12 或更高版本（Apple 芯片和 Intel）以及 Windows 10/11（x64 和 Arm64）的桌面应用，支持英文和简体中文。
• 根据设备配置识别处于 adb、fastboot 或 EDL 模式的 UFI003 随身 Wi-Fi，并显示可安装的各层：基础系统、设备支持、OpenXPlay 中继。
• 其他 Android 设备会单独列出并忽略。
• 命令行：devices、watch、profiles、version。

说明

• 仅为预览版：本版本不会向任何设备写入内容。
• 安装包未签名，在 macOS 和 Windows 上的打开方法见 README。