diff --git a/device/enchilada/NOTES.md b/device/enchilada/NOTES.md new file mode 100644 index 000000000..5e9723616 --- /dev/null +++ b/device/enchilada/NOTES.md @@ -0,0 +1,192 @@ + +# OnePlus 6 (enchilada) bring-up notes + +Findings from one retail OnePlus 6 (`ONEPLUS A6000`, `oneplus,enchilada`, +Qualcomm SDM845 / Snapdragon 845), newest first. Claim and discussion: +[#432](https://github.com/derekross/omarchy-mobile/issues/432). Captures +(`fastboot getvar all`, the partition map, command lines) stay off the +repository; facts from them are quoted here. Dates and times are US Eastern +(UTC−5). + +Every entry says how the phone was booted (`fastboot boot` into RAM, or +the image on `boot_b`) and where its root was (the shared initramfs, or +the Arch root on `userdata`). Two builds of one kernel were used, both +Linux `7.1.0-rc1-sdm845` from the +[sdm845-mainline tree at tag `sdm845-7.1-rc1-r0`][sdm845-tag] +(`85f1df2a4ec7`) with the qcom-sdm845 kernel configuration that tree is +distributed with, and the upstream `qcom/sdm845-oneplus-enchilada.dtb`: + +- **the first-light kernel**: exactly that; +- **the netfilter kernel**: the same, plus the six netfilter matches in + the 2026-11-05 firewall entry. + +linux-omarchy-mobile, which carries the same upstream DTS, has not been +tried yet; it is next. + +[sdm845-tag]: https://gitlab.com/sdm845-mainline/linux/-/tree/sdm845-7.1-rc1-r0 + +## Slots and what is on them (CONTRIBUTING.md §3.1) + +**Slot A does not hold stock Android.** This is a §3.1 event, recorded +here as the maintainer asked on #432. Putting stock back on slot A is +outside the project: this tree only writes slot B and `userdata`, and +never `vbmeta`. If it is done, it is the owner's own step, with +OnePlus's own images, and it is recorded on #432 (slot flags before +and after, what was flashed and from which image, then a fresh +read-only radio backup). The owner has decided not to restore it, so +slot A keeps the rescue. This port stays RAM-only (`fastboot boot`) +until the slot-B install and its CONTRIBUTING.md §3.1 entry are agreed. + +| Where | What is there now | How it got there | Storage guard? | +| --- | --- | --- | --- | +| `boot_a`, `system_a` | a small Arch Linux ARM rescue root and its kernel | `fastboot flash boot_a` and `fastboot flash system_a`, 2026-11-04, after a third-party Android build had replaced stock OxygenOS | its own, not the shared init: see below | +| `boot_b` | a header-v0 boot image of this port, netfilter kernel; its command line has no `omamobile.initramfs`, so the shared init hands off to the Arch root on `userdata` | `fastboot flash boot_b`, 2026-11-04 (first-light kernel); again 2026-11-05 16:15 (netfilter kernel) | yes: the shared `initramfs/init`, which leaves `boot_b` read-only (LUN `sde`, see first light) | +| `dtbo_b` | erased | `fastboot erase dtbo_b`, 2026-11-04: the third-party build's downstream overlays would not apply to a mainline DTB | - | +| `vendor_a`, `vendor_b`, `odm_a`, `odm_b`, `system_b` | leftovers of the third-party Android build | that build's installer | - | +| `userdata` | an Arch root built by `bin/omamobile`, with packages added from the rescue (below) | `fastboot flash userdata`, 2026-11-04 | - | +| bootloader firmware (`xbl`, `abl`, `tz`, `modem`, ...) | OxygenOS firmware, identical on `_a` and `_b` | never written by this port | - | + +**Writes made by hand.** Every write below was typed by hand, outside +`tools/install-phone` and `bin/omamobile` (whose installer path refuses +`android-v0`), and none will be repeated: + +- `fastboot`: `flash boot_a` and `flash system_a` (the rescue), + `erase dtbo_b`, `flash userdata`, `flash boot_b` twice, and + `--set-active`, which writes the GPT slot flags, to move between A and B. +- From the rescue, into `userdata`: on the night of 2026-11-04 the + image's first 24 KiB were rewritten and the partition's last 1 MiB + zeroed, because a nested GPT left from the third-party build kept + overwriting the flashed image's head; on 2026-11-05 linux-firmware + (`whence`, `atheros`, `qcom`), the device package and a kernel module + tree were installed into the Arch root, and ufw enabled there. On + `system_a`, the rescue's own root, `systemd-pstore` was enabled. + +All of it happened before the maintainer's reply on #432 except the last +three steps of 2026-11-05: that reply was posted at 16:13 (21:13 UTC), +and `flash boot_b` (netfilter kernel), `--set-active=a` and the package +install into `userdata` ran from 16:15 to about 16:20, before I had read +it. Since then the only commands sent to the phone have been the read-only +backup, one `fastboot boot` (2026-11-05 16:35) and `getvar` (below). No +slot flag is written again until this phone has a per-device entry in +CONTRIBUTING.md. + +**Slot flags** (`fastboot getvar all`, read-only): + +| Read | `current-slot` | A: successful / unbootable / retry-count | B: successful / unbootable / retry-count | +| --- | --- | --- | --- | +| 2026-11-04, before any write of this port | a | no / no / 6 | yes / no / 7 | +| 2026-11-07, now | a | no / no / 5 | no / no / 7 | + +Between the two reads, B lost its successful mark (left by the third-party +build; `--set-active=b` clears it and nothing of this port marks a slot) +and A's retry count went from 6 to 5. Neither slot is marked unbootable. + +Slot A is not marked successful, so each boot of the rescue may spend one +of its tries. If ABL works as on other Qualcomm phones, `--set-active=a` +on 2026-11-05 reset A's count to 7, and the rescue boots since (including +the reboot after a `fastboot boot` panics with no USB host) took it to 5. +At 0 ABL would switch to slot B and run B's tries down too, and since +nothing here may mark a slot, the phone would then stop in fastboot and +need a `--set-active` to come back. This is not confirmed yet: one more +`getvar` after the next rescue boot will tell. Until then, rescue boots +are kept few. + +**The slot-A rescue.** It is not the shared init and has no initramfs (an +empty ramdisk): the kernel mounts `system_a` from the `root=` that ABL +appends, and `system_a` is mounted read-write. Its own udev rule +(`60-rescue-ufs-guard`) sets `ro=1` on every UFS partition except four +allowed writable ones, `system_a`, `userdata`, `boot_b` and `dtbo_b`, and +makes read-only every disk holding none of them; it keeps the whole-disk +nodes. That protects against accidents only. It replaces nothing in this +tree and goes away if stock is restored. + +**With no USB host**, a `fastboot boot` of the shared init gives up after +20 s and panics, and `panic=10` reboots the phone. ABL then starts the +active slot, A, which is the rescue. + +## 2026-11-05: complete backup + +Taken from the slot-A rescue (`boot_a`, `system_a`), read-only. Every +partition by GPT label except `userdata` (this phone has no `super`), +both slots: 100 images, with `persist`, `modemst1`, `modemst2` and `fsg` +never mounted. The sha256 of each raw partition was taken on the phone +before the copy and checked again after transfer and after decompression; +99/100 match all three ways. The exception is `system_a`, which was the +running rescue root, so that copy is live; the image it was flashed from +is kept beside it. The backup is kept off the repository. + +Every firmware partition is byte-identical between `_a` and `_b` (`xbl`, +`xbl_config`, `abl`, `aop`, `tz`, `hyp`, `devcfg`, `keymaster`, +`cmnlib`, `cmnlib64`, `qupfw`, `storsec`, `modem`, `dsp`, `bluetooth`, +`LOGO`), so the two slots' bootloader versions match. + +## 2026-11-05: the firewall needs six netfilter matches + +**Failure, booted from `boot_b`** (`--set-active=b`, first-light kernel, +root on `userdata`; 2026-11-04 and again 2026-11-05 15:41): the +first-light kernel configuration leaves out the xtables matches that +ufw's rules load through `nft_compat`. Without them `ufw-init` stops at +`before6.rules` (`-m rt`, `-m hl`) and `before.rules` (`-m limit`), +firstboot's "services and firewall" step never completes, and the +half-loaded ruleset blocks new SSH connections on `usb0`. + +**Fix, booted with `fastboot boot`** (2026-11-05 16:35, the netfilter +kernel's `boot_b` image sent to RAM, slot A still active, root on +`userdata`; no `--set-active`): with the matches built as modules +(`NETFILTER_XT_MATCH_LIMIT`, `_HL`, `_STATE`, `_OWNER`, `_RECENT` and +`IP6_NF_MATCH_RT`), firstboot completed, `ufw status` was active with +`22/tcp on usb0 ALLOW IN` (IPv4 and IPv6), and fresh SSH sessions +worked. `kernel/configs/omamobile.config` already enables the same +matches, so linux-omarchy-mobile should not need this. + +On the very first boot only, SSH on `usb0` was blocked for about 100 s: +`ufw.service` starts default-deny about 5 s into boot, and the `usb0` +rule arrives only when firstboot reaches its firewall step. Later boots +load the saved rule at once. + +## 2026-11-05: Adreno 630 needs this phone's zap shader + +Same boot as the firewall fix (`fastboot boot`, netfilter kernel, root on +`userdata`). With `linux-firmware-qcom`, `qcom/a630_sqe.fw` and +`qcom/a630_gmu.bin` load. The zap shader the DTB names, +`qcom/sdm845/OnePlus/enchilada/a630_zap.mbn`, is signed for this phone +and is not in linux-firmware, so `adreno_load_gpu` fails with `-2` and +the compositor cannot start. Like the modem's firmware, it has to come +from the phone's own partitions at install time and is never committed; +the modem/rmtfs plan will say how, before any radio step. + +## 2026-11-04: RAM-only first light + +A header-v0 boot image (first-light kernel, gzip `Image` with the DTB +appended, the shared `initramfs/init` with `omamobile.initramfs`), booted +with `fastboot boot`. It stayed in the initramfs, mounted nothing, and +wrote nothing. + +- The USB gadget came up about 4 s after `fastboot boot`, and + `ssh root@172.16.42.1` worked. +- The storage guard held: allowlist `boot_b userdata`, every `sd*` + partition `ro=1` except `userdata` (`sda17`), `/dev/sda` removed, + nothing mounted. +- **`boot_b` is on LUN `sde`, not `sda`.** The shared guard's `UFS_RW` + only looks at `sda`, so `boot_b` and `dtbo_b` stay read-only (seen + live). This is the same split as dodge; a LUN-aware `UFS_RW` will be its + own shared pull request. +- msm DRM came up (`fb0` is `msmdrmfb`). +- ABL appends `root=PARTUUID= skip_initramfs ro init=/init` to + the command line even on `fastboot boot`. The shared init runs as PID 1 + regardless, so it needs no change. + +## Stock facts (2026-11-04, before the port) + +- Model `ONEPLUS A6000`; fastboot `product` `sdm845`, `variant` `SDM UFS`; + `slot-count` 2; `max-download-size` 805306368 (768 MiB). + `FASTBOOT_PRODUCT=sdm845` is the SoC name, not the phone's: any SDM845 + phone may report it, so it never identifies this phone by itself. +- Bootloader unlocked, EDK2-based ABL; `qcom,msm-id` 0x141 + (`androidboot.platform_id=321`). +- Boot images: Android boot image header v0, page size 4096, gzip kernel + with the DTB appended; no `vendor_boot`, no `init_boot`. The header + offsets are in `device.conf`. +- UFS: `userdata` is `sda17` (fastboot reports it as f2fs); `boot_*`, `dtbo_*` + and `vbmeta_*` are on LUN `sde`. +- Panel: Samsung `sofef00` command-mode DSI, 1080x2280. diff --git a/device/enchilada/device.conf b/device/enchilada/device.conf new file mode 100644 index 000000000..40d415f20 --- /dev/null +++ b/device/enchilada/device.conf @@ -0,0 +1,46 @@ +# SPDX-License-Identifier: MIT +# Guarded SDM845 descriptor for the OnePlus 6 (enchilada). Format rules: +# device/cheetah/device.conf. Notes and the state of each slot: NOTES.md. +# +# RAM-only bring-up: this ABL boots an Android boot image header v0 holding +# a gzip kernel with the DTB appended (no dtbo, no vendor_boot), booted with +# `fastboot boot`, so nothing is written. No packer in this tree makes that +# image yet, so images, flash, push and the installer all refuse +# BOOT_METHOD=android-v0 before touching a phone (tests/boot-method). The +# header-v0 packer is a separate change; flash, push and the installer keep +# refusing it until the slot-B install and its CONTRIBUTING.md §3.1 entry +# are agreed. +# +# Storage: userdata is on sda, but boot_* sit on LUN sde, so the shared +# init's sda-only guard keeps boot_b read-only (the same split as dodge). +# Never flash xbl/abl/vbmeta/modem/persist from an image. +# +# FASTBOOT_PRODUCT=sdm845 is ABL's `getvar product`: the SoC's name, which +# other SDM845 phones report too, so it never identifies this phone alone. + +CODENAME=enchilada +FASTBOOT_PRODUCT=sdm845 +NAME="OnePlus 6" +SOC=sdm845 +COMPATIBLE="oneplus,enchilada" +BOOT_METHOD=android-v0 + +DTB=qcom/sdm845-oneplus-enchilada.dtb +INITRAMFS_INIT=/initramfs/init +PANEL_SIZE=1080x2280 + +# Header v0 layout this ABL accepts, from a boot image known to boot it +PAGESIZE=4096 +BASE=0x00000000 +KERNEL_OFFSET=0x00008000 +RAMDISK_OFFSET=0x01000000 +SECOND_OFFSET=0x00f00000 +TAGS_OFFSET=0x00000100 + +BOOT_IMAGES=boot +UFS_RW="boot_b userdata" +OMAMOBILE_SLOT=b +# The first-light kernel builds the USB gadget as modules (USB_CONFIGFS=m) +INITRAMFS_MODULES="libcomposite u_ether usb_f_ncm u_serial usb_f_acm" +# omamobile.initramfs: stay in the initramfs; RAM-only, nothing is mounted rw +CMDLINE="console=tty0 panic=10 omamobile.initramfs omamobile.ufs-probe" diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 364f51375..6bc7f29b6 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -30,6 +30,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B into the initramfs with USB and SSH, no Arch root yet; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md), [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | WIP (UFS at HS-G4 behind the read-only guard, from the initramfs only, nothing run on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206); the device package and storage plan are in review, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | no | no | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | | OnePlus 13 ([notes](../device/dodge/NOTES.md)) | dodge | sm8750 (Snapdragon 8 Elite) | testing (kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [BRINGUP](../device/dodge/BRINGUP-M1.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (msm/dpu; warm-boot drop fixed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (Adreno 830 / gpu2; Vulkan untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (CDC NCM + SSH; gadget stuck after replug until reboot; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (WCN7860 / ath12k; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (pairing; A2DP untested; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (gauge; charging path not claimed; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | no | no | - | testing (speakers, earpiece, mics; headset plug untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (accel, prox, compass; autorotate; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (LTE data; calls/SMS untested; opt-in flag; [modem](../device/dodge/modem/README.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | WIP (s2idle not default; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | +| OnePlus 6 ([notes](../device/enchilada/NOTES.md)) | enchilada | SDM845 (Snapdragon 845) | WIP (RAM-only `fastboot boot` of a header-v0 image; kernel: Linux 7.1-rc1 from the sdm845-mainline tree, not linux-omarchy-mobile; the firewall and GPU results booted the Arch root on `userdata`; stock is not on slot A, a §3.1 event: [notes](../device/enchilada/NOTES.md#slots-and-what-is-on-them-contributingmd-31); [#432](https://github.com/derekross/omarchy-mobile/issues/432)) | WIP (UFS behind the read-only guard; `boot_b` is on LUN `sde` and stays read-only; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | WIP (msm DRM framebuffer console; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (needs the phone's own zap shader; [notes](../device/enchilada/NOTES.md#2026-11-05-adreno-630-needs-this-phones-zap-shader)) | no | no | testing (NCM + ACM + SSH; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (modem/rmtfs plan first) | no | no | no | no | no | no | - | no | no | no | no | no | no | no | | *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | | ## cheetah (Pixel 7 Pro) in detail @@ -79,4 +80,5 @@ Devices we'd like to support, with the closest starting point. Open an issue to | Pixel 4 XL | coral | SM8150 (Snapdragon 855) | **WIP, community port**, in the matrix above: bring-up notes merged ([#52](https://github.com/derekross/omarchy-mobile/pull/52): [BRINGUP-M1](../device/coral/BRINGUP-M1.md), [NOTES](../device/coral/NOTES.md)), with companion kernel/userspace sources ([omarchy-mobile-coral v0.2.3](https://github.com/HemangKumawat/omarchy-mobile-coral/tree/v0.2.3)); slot-B installer and `CONTRIBUTING.md` §3.1 entry still to land | | POCO F3 | alioth | SM8250 (Snapdragon 870) | the first non-Pixel port: a guarded installer and root image in review ([#25](https://github.com/derekross/omarchy-mobile/pull/25)) | | OnePlus 13 | dodge | SM8750 (Snapdragon 8 Elite) | **WIP, community port**, in the matrix above: device files, notes and the qcom-abl boot images merged ([#111](https://github.com/derekross/omarchy-mobile/pull/111)); its kernel stays in the contributor's fork ([mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed: the SoC series is out of this tree's scope); the guarded installer follows in a later pull request | +| OnePlus 6 | enchilada | SDM845 (Snapdragon 845) | **WIP, community port: [#432](https://github.com/derekross/omarchy-mobile/issues/432)**, in the matrix above: descriptor and notes; RAM-only (`fastboot boot`) until the slot-B install and its CONTRIBUTING.md §3.1 entry are agreed; the header-v0 packer and a LUN-aware `UFS_RW` follow in their own pull requests | | PinePhone Pro | pinephone-pro | Rockchip RK3399S | No port in this tree yet; mainline's `rk3399-pinephone-pro.dts` is already in our kernel. Prior art: [Omarchy on the PinePhone Pro](https://github.com/FlorencioJP/omarchy-mobile-pinephone-pro) | diff --git a/tests/boot-method b/tests/boot-method index e1c3184dc..f83b84aa6 100755 --- a/tests/boot-method +++ b/tests/boot-method @@ -19,7 +19,7 @@ done export PATH="$t/bin:$PATH" CALLS="$t/calls" unset KERNEL_OUT KERNEL_DIR KERNEL_BASE WORK || true fail() { echo "not ok - $*" >&2; cat "$t/log" >&2; exit 1; } -for method in ram-only uboot-ext4 unknown ''; do +for method in ram-only uboot-ext4 android-v0 unknown ''; do printf 'CODENAME=probe\nBOOT_METHOD="%s"\nBOOT_IMAGES=""\nUFS_RW=""\n' "$method" > "$t/repo/device/probe/device.conf" cp "$t/repo/device/probe/device.conf" "$t/bundle/device.conf" for cmd in images flash push; do @@ -42,6 +42,21 @@ if "$t/repo/tools/install-phone" --device flame > "$t/log" 2>&1; then fail "flam grep -q 'unsupported BOOT_METHOD=ram-only;' "$t/log" || fail "flame fails for the wrong reason" echo 'ok - the shipped flame descriptor has no persistent installer path' +# The shipped enchilada descriptor: android-v0 has no packer here, so every +# path that would make or write an image refuses it before phone access. +mkdir -p "$t/repo/device/enchilada" +cp device/enchilada/device.conf "$t/repo/device/enchilada/" +for cmd in images flash push; do + if DEVICE=enchilada "$t/repo/bin/omamobile" "$cmd" > "$t/log" 2>&1; then fail "enchilada $cmd succeeds"; fi + grep -q 'unsupported BOOT_METHOD=android-v0;' "$t/log" || fail "enchilada $cmd fails for the wrong reason" +done +for dry in '' --dry-run; do + if "$t/repo/tools/install-phone" --device enchilada $dry --work "$t/work" > "$t/log" 2>&1; then fail "enchilada installs"; fi + grep -q 'unsupported BOOT_METHOD=android-v0;' "$t/log" || fail "enchilada installer fails for the wrong reason" +done +[[ ! -e $t/calls && ! -e $t/work ]] || fail "the enchilada descriptor accessed a phone or prepared an image" +echo 'ok - the shipped enchilada descriptor is refused by images/flash/push and both installer modes' + # qcom-abl is accepted by images only when device/$DEVICE/chainload/ exists # (installer still refuses until a later PR). flash and push both refuse # qcom-abl before phone access. A complete dodge-shaped descriptor with