Session 35 — 2026-03-30a
| Field | Value |
|---|---|
| Date | 2026-03-30 |
| Phase | 04 — Firmware Acquisition |
| Duration | ~1 h |
Critical: NA2 Uses SDM662, Not SDM636
XBL build path confirms: /work/disk5/sdm662/sdm662_android_rom/. Vendor: ro.board.platform=bengal. This is Snapdragon 662 (Bengal), a completely different SoC from NA1’s SDM636 (SDM660 family). The original project assumption was wrong.
| Note Air 1 | Note Air 2 | |
|---|---|---|
| SoC | SDM636 (sdm660) | SDM662 (bengal) |
| Kernel | 4.4.x | 4.19.157 |
| Android | 10 (SDK 29) | 11 (SDK 30) |
| Partitions | static, single-slot | dynamic A/B + super |
| Encryption | FDE | FBE |
Consequence: direct firmware port at partition level is not viable. Kernel, vendor HALs, and bootloaders are incompatible.
NA2 Firmware Chain
| Version | Type | Size | URL MD5 |
|---|---|---|---|
| v4.0 | Full | 1.84 GB | 9bcffd50… |
| v4.0.2 | Incremental | 50 MB | 91a889a3… |
| v4.1.1 | Incremental | 338 MB | 04e3c7d5… |
Served from http://firmware-us.boox.com/<md5>/update.upx. Decrypted with DeBooxUpx.py, extracted with payload-dumper-go v1.3.0 (A/B OTA format).
Onyx APKs — All Compatible with NA1
22 APKs extracted from system.img. All target SDK 29, minSDK 24 — compatible with NA1’s Android 10. Key apps: kreader2 v37913, knote2 v41957, kcb launcher v54255, ai-assistant v30165. Will run on NA1 without modification via sideload.
Project Pivot
- APK extraction first — sideload NA2’s newer Onyx apps onto NA1’s Android 10
- GSI approach deferred — theoretically possible via Treble but VNDK mismatch risk (29 vs 30)
- Full partition port — definitively not viable