Hardware · v0.7.2-beta

Three devices, three honest states

Nuxel v0.7.2-beta runs on the Galaxy S10+. The Moto G7 Power is an expendable bring-up target. The Pixel 10 Pro XL is the goal, and Nuxel has not booted on it yet.

Download release Help with bring-up (opens in a new tab)

Honest status

A supported codename is not a promise that every subsystem works. Each device below lists what is verified, what is in progress and what is still blocked.

Stylized front view of a Google Pixel 10 Pro XL showing the Nuxel interface
🎯 Final target

mustang

Google Pixel 10 Pro XL

SoC Google Tensor G5 (gs501) + Exynos 5500 modem

The phone Nuxel ultimately wants to run. The repository has the inventory, recovery path, flash tooling and firmware gates ready; none of the on-device steps has been executed for Nuxel yet.

Current state Hardware-gated — no Nuxel boot yet
Reviewed serial
58211FDCQ001LA
Hardware revision
MP1.0 · SKU G45RY
Boot chain
Google ABL + AVB 2.0 + Titan M3
Kernel target
Mainline 6.12 LTS (not yet booted on Nuxel)
Flash path
fastboot / fastbootd, gated by five inventory checks
OS state
Stock Android; no Nuxel image has been flashed

Verified / implemented

  • Device inventory commands and Phase 0 collection guide
  • Recovery and de-bricking path documented
  • Firmware verification manifest and signing tooling
  • AVB key generation and image-signing scripts

Open / blocked

  • Five hard gates: slot integrity, build/bootloader match, OEM unlock, real blob filenames, vendor kernel access
  • Factory image and vendor blobs must be supplied by the operator
  • Kernel, GPU, modem, camera and DRM bring-up are all future work

Evidence: docs/pixel10proxl-device-inventory.md, docs/mustang-recovery-bringup.md

Get Nuxel v0.7.2-beta
Stylized front view of a Samsung Galaxy S10+ showing the Nuxel interface
📊 Active development

beyond2lte

Samsung Galaxy S10+

SoC Samsung Exynos 9820

The device Nuxel actually runs on today. It boots a real Fedora 43 userspace, presents the launcher and has working Wi-Fi, Bluetooth and audio playback. Several subsystems remain open.

Current state Boots Nuxel · owner acceptance in progress
Model
SM-G975F
Kernel
Samsung-derived Linux 4.14.253 (vendor tree)
Userspace
Fedora 43 aarch64 · systemd PID 1
Display
DECON fb 1440×3040 · no /dev/dri (no DRM/KMS)
Memory
7,420 MiB usable · no swap
Storage
ext4 on USERDATA · single rootfs, no on-device A/B yet

Verified / implemented

  • Boot chain and userspace: kernel → initramfs → Fedora systemd → launcher
  • Display presentation through Phoc headless + DECON screencopy bridge
  • Wi-Fi radio, scan and NetworkManager control
  • Bluetooth hci0 registration, power-on and peer scan
  • Audio playback through the ABOX RDMA1 route with an advancing hw_ptr
  • Serial Live Console over USB CDC-ACM
  • Preload cinema, keyboard, global navigation and app resurrection (v0.7.2)

Open / blocked

  • GNSS: hardware responds, but Broadcom BBD/LHD userspace is missing (BLOCKED_FIRMWARE)
  • HDMI/DRM: CONFIG_DRM and a Type-C DP Alt Mode stack are absent
  • Camera capture: UI and navigation exist; the backend is deferred
  • Owner acceptance for touch flows, keyboard feel, microphone/WAV capture and the full boot sequence
  • Laptop-side file transfer access remains a host verification step

Evidence: docs/s10plus-live-fixes-20261028.md, docs/releases/v0.7.2-beta.md

Get Nuxel v0.7.2-beta
Stylized front view of a Motorola Moto G7 Power showing the Nuxel interface
🔧 Hardware bring-up

ocean

Motorola Moto G7 Power

SoC Qualcomm Snapdragon 632 (SDM632 / msm8953 family)

A deliberate hardware bring-up target built on the postmarketOS motorola-ocean port, msm8953-mainline and the lk2nd chainloader. It is not flashable or verified yet.

Current state Scaffold — not flashable/verified
Model
XT1955
Boot chain
PBL → ABOOT → lk2nd → Linux
Port basis
postmarketOS motorola-ocean + msm8953-mainline
Chainloader
lk2nd (dtbo flashed before lk2nd, always)
Protected partitions
modemst1/2, fsg, fsc, ddr, persist, misc — never touched
OS state
No verified Nuxel boot

Verified / implemented

  • Two-phase fastboot flow with the stock ABOOT and lk2nd
  • Protected-partition guard enforced in code
  • EDL unbrick path documented
  • Phase 0 inventory template and build gate

Open / blocked

  • Every checksum, load address and firmware filename is a placeholder until the unit is inventoried
  • A real kernel and lk2nd build still have to be produced and tested
  • Touch, Wi-Fi and panel bring-up are unverified

Evidence: docs/g7power-bringup.md, docs/g7power-device-inventory.md

Get Nuxel v0.7.2-beta

Reality check

Support is earned, not assumed

Nuxel tracks capability per subsystem, per device. The S10+ boots and runs a real userspace; the Moto is still a scaffold; the Pixel has not been touched. A device is added to this page only with the evidence behind it.

Explore the feature catalogue Read the safety model