Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
5739866
device/dipper: add a RAM-only first-light build path
quatrixone Nov 7, 2026
e6c1dc2
device/dipper: tighten RAM-only probe runbook
quatrixone Nov 8, 2026
6801b35
device/dipper: expose guarded NFS-root probe input
quatrixone Nov 8, 2026
683d321
device/dipper: require verified recovery before RAM boot
quatrixone Nov 9, 2026
ad55e47
device/dipper: record verified restart and backup gates
quatrixone Nov 9, 2026
16f28af
device/dipper: match read-only gate to main LUN guard
quatrixone Nov 9, 2026
6800595
device/dipper: record RAM boot gate results
quatrixone Nov 9, 2026
b9a3575
device/dipper: enable PMIC key inputs at boot
quatrixone Nov 9, 2026
e98d7bc
device/dipper: finish owner review follow-ups
quatrixone Nov 9, 2026
0b0b4ca
device/dipper: record fastboot helper test
quatrixone Nov 9, 2026
ecc636a
device/dipper: record verified stock backup
quatrixone Nov 9, 2026
25c7e9d
device/dipper: record panel test and guard follow-up
quatrixone Nov 9, 2026
41676a6
device/dipper: clarify reboot and recovery status
quatrixone Nov 9, 2026
17dd15b
device/dipper: record restart under RAM kernel
quatrixone Nov 9, 2026
bce9717
device/dipper: align panel and guard test gates
quatrixone Nov 10, 2026
fc4e114
docs(dipper): record final RAM boot verification
quatrixone Nov 10, 2026
737716d
dipper: pin the rescue SSH host key
quatrixone Nov 10, 2026
829bb43
docs(dipper): record final NFS and RAM probes
quatrixone Nov 10, 2026
454bd93
dipper: apply final owner review notes
quatrixone Nov 11, 2026
c4238ab
device/dipper: link merged bring-up notes
quatrixone Nov 11, 2026
2d67708
device/dipper: fix initramfs container mounts
quatrixone Nov 11, 2026
5d917b4
device/dipper: record current RAM boot
quatrixone Nov 11, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
133 changes: 133 additions & 0 deletions device/dipper/BRINGUP-M1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,133 @@
<!-- SPDX-License-Identifier: MIT -->
# Xiaomi Mi 8 (dipper): RAM-only first light

**Status (2026-11-10):** the combined #503/#505 non-NFS image `540b5d31ea73a31ade9a8d8cb5152cf701dc3c2ad8256734790b0ef2db6dbdd0` booted by RAM on the Xiaomi Mi 8 with kernel/DTS PR #220 at `055a4019998f22cc0e2a8afef7650274a6ce0657`. Its initramfs root had all 85 UFS partition flags at `ro=1`. `/sys/block/sda/ro` was `0`, but `/dev/sda` was absent; `sdb`–`sdf` were `ro=1`. The guard confirmed this state. `qcom_wdt` and its feeder ran, simpledrm registered `fb0`, USB/SSH worked, and `/proc/iomem` reserved `0x85fc0000–0x8a8fffff`, covering the former TZ range. The pinned rescue SSH key matched, and `reboot-to` returned the phone to fastboot. Physical input events were not captured on this exact image.

A separate RAM NFS-root run used image `a2d435a7430e7e4c145c61cdb9866d16929731859d91c7105e6bfcaf9e3e9dd7` with the rebased #503 init. BusyBox `mount` switched to the test NFS root; all six disk flags and all 85 partition flags were `ro=1`. Systemd reached the multi-user target with `RuntimeWatchdogSec=60s`, and SSH remained available. `reboot-to bootloader` returned the phone to fastboot. The exported root was a generic Arch base; this did not test the Omarchy desktop or link-loss recovery. Full results are in [NOTES.md].
The FTS5 driver from [touch #219] is merged into linux-omarchy-mobile. The
Dipper board DTS is under review in [DTS #220], and the EA8074 panel driver is
under review in [panel #218].
The EA8074 panel test is recorded in [NOTES.md]. The FTS5 touchscreen
still needs a hardware test.
On 2026-11-09, a guarded RAM boot was used to capture all 84 GPT partitions
other than `userdata` (the phone has no `super`); source and compressed-image
checksums passed. The separate live userdata archive also passed its checksum
and zstd integrity checks. It is a file-level, non-atomic archive, not a raw
partition image.

This is a RAM-only bring-up. Dipper has one OS `boot` partition and no alternate
OS slot. The descriptor sets `BOOT_METHOD=ram-only`, the builder makes only a
`fastboot boot` image, and the initramfs keeps every UFS partition read-only.
There is no supported flash, push, installer or persistent update path here.

## Recovery and safe boot

Each gate below must pass before proceeding. Set `FASTBOOT_SERIAL` to the
intended handset's serial, `BACKUP_CHECKSUMS` to the locally held stock
partition manifest, and `USERDATA_BACKUP_CHECKSUMS` to the private userdata
archive's checksum file. Do not boot if either backup is missing or fails.

1. **Backup gate** — Expect: the verified backup of the installed system's 84
non-userdata GPT partitions, both checksum manifests, and the userdata archive
are available off-device. Pass: both
`sha256sum -c "$BACKUP_CHECKSUMS"` and
`sha256sum -c "$USERDATA_BACKUP_CHECKSUMS"` report every entry OK (run each
from the directory containing its manifest). The userdata archive is a live
file-level copy, not a raw partition image or an atomic snapshot. Stop: any
missing or mismatched entry. Rollback: do not boot; there is no reviewed
restore procedure yet, and nothing in this runbook writes UFS. Risk: an
unverified backup cannot recover a damaged single-slot phone.
2. **Fastboot gate** — Enter fastboot with **Volume Down + Power**; the §3.1
entry is in [CONTRIBUTING.md §3.1](../../CONTRIBUTING.md#phones-without-ab-slots).
Run `fastboot -s "$FASTBOOT_SERIAL" getvar product` and
`fastboot -s "$FASTBOOT_SERIAL" getvar unlocked`. Expect `dipper` and `yes`.
Pass: exactly one device is listed, both values match, and the serial pins
every fastboot command. Stop: absent/ambiguous device, wrong product or
locked bootloader. Rollback: leave fastboot without writing. Risk: this
device has no alternate OS slot.
3. **Recovery gate** — Fastboot entry uses **Volume Down + Power**; the forced
restart is separate. On 2026-11-09, an attended test found that holding
**Power alone for 10 seconds** restarted into Android from both installed
Android and the Omarchy Mobile RAM kernel. Volume Down + Power then entered
fastboot from Android. Expect: the Power-only hold restarts the phone. Pass:
the observed procedure above is recorded and the phone can enter fastboot.
Stop if Power alone does not restart it. Rollback: do not start a RAM boot
until this gate passes. Risk: a hard kernel hang has not been simulated;
recovery from one still depends on the hardware button reset working.
4. **RAM boot gate** — Run
`fastboot -s "$FASTBOOT_SERIAL" boot boot.img`. Expect: the image starts
without changing UFS, and the screen stays lit because simpledrm holds the
panel's VCI and VDDIO rails. If it goes dark about 30 seconds in, record
`dmesg | grep -i -E 'regulator|simple'` and stop.
Pass only when `uname -r`, the `boot.img` sha256, all partition `ro` values,
whole-disk `ro` values, and `ufs-ro` lines from `dmesg` are recorded.
`/dev/sda` must be absent or present with `/sys/block/sda/ro=1` in NFS mode;
each other whole-disk node must be absent or present with its `ro=1`. Every
partition must have `ro=1`. Stop if any partition or present whole-disk node
has `ro=0`.
Also record the reserved-memory lines from
`grep -i -E 'reserved|System RAM' /proc/iomem`, the bound `qcom_wdt`
driver, its running watchdog feeder, and USB/SSH are recorded and correct.
Stop if any partition or present whole-disk node has `ro=0`, the watchdog
is not fed, USB/SSH fails,
or anything asks to flash. Rollback: use the verified forced-restart
procedure from step 3, then recover from the verified backup if needed.
Risk: a USB host that never configures still reaches the existing watcher
panic after about 65 seconds; on this single-slot phone, recovery depends on
the tested procedure from step 3.

The current recorded first light used the stock `dtbo` untouched. The image is
RAM-only; never use `fastboot flash`, `bin/omamobile flash`, `bin/omamobile
push`, or the installer. Keep the phone and USB cable present during a probe.

## Build and probe

Build a kernel checkout containing the Dipper kernel PRs with
`device/dipper/kernel.config` merged after the shared Omarchy Mobile fragment.
Set `DEVICE=dipper`, `KERNEL_DIR` (source), and `KERNEL_OUT` (build output), then
run `bin/omamobile kernel`. The output must include `Image`, `Image.gz`,
`arch/arm64/boot/dts/qcom/sdm845-xiaomi-dipper.dtb`, and modules from that same
kernel release. Then set `SSH_PUBKEY` to an OpenSSH public key and run
`tools/dipper/build` with the same `KERNEL_DIR` and `KERNEL_OUT`. For a local
NFS-root probe, pass `OMAMOBILE_NFSROOT=<host>:/<export>` to the builder; the
host and export are build inputs, never descriptor values. The builder requires
Docker with arm64 emulation; it writes its output inside `out/dipper` by
default. Do not commit the key or generated images.

The initramfs provides USB networking, SSH and a rescue shell. It does not
mount `persist`, read or embed per-phone identifiers, start Wi-Fi, or install a
root filesystem. The network daemon binds only to the IPv4 address assigned to
`usb0`. No Wi-Fi credentials, MAC addresses or private keys belong in the
repository; the SSH public key and generated host key stay in the local output.

## What remains

- Do not flash until there is a reviewed, device-specific recovery plan and a
verified backup of the installed system. This PR deliberately adds no
persistent writer.
- The initramfs has no Arch root yet. A later hard NFS-root mount can freeze the
root session if the host drops; use it only for a RAM-only probe. NFS-root
needs a root with `RuntimeWatchdogSec=60s`, because `kill -9 -1` stops the
userspace feeder before systemd can take over. It must never fall through to
writable userdata.
- Wi-Fi needs firmware and the phone's own WLAN address. Read identity files
from `persist` with `debugfs` (read-only) before enabling that service; never
mount `persist`.
- The exact systemd journal line from the earlier failed `qcom_wdt` timeout
change was not retained. The 2026-11-10 NFS test root reached systemd with
`RuntimeWatchdogSec=60s`; NFS link-loss recovery and the Omarchy desktop on
that root remain untested.
- Test the FTS5 touchscreen changes and GPU rendering on the phone before
marking them supported.

From this rescue image, an SSH session can return to fastboot with
`reboot-to bootloader`. The installed ROM's `recovery` image was verified from
its 4.9.337 kernel header, but recovery-mode reboot was not tested; this runbook
uses only the verified bootloader path. The helper asks the PMIC reboot-mode
driver to select the bootloader and writes no UFS partition. The PMIC reset path
was verified on the handset on 2026-11-09. The packaged helper returned the
running image to fastboot on 2026-11-09 without writing UFS.

[panel #218]: https://github.com/derekross/linux-omarchy-mobile/pull/218
[touch #219]: https://github.com/derekross/linux-omarchy-mobile/pull/219
[DTS #220]: https://github.com/derekross/linux-omarchy-mobile/pull/220
16 changes: 16 additions & 0 deletions device/dipper/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ the facts needed for review.

| Date | `boot.img` SHA-256 | Source, as recorded | `/dev/sda` and UFS partitions | Checks and gaps |
| --- | --- | --- | --- | --- |
| 2026-11-11 | `665fcbd682cd8e64b3ffec1ff7f4ab9ca33a26b9b47b11073be7a3c267abf2b1` | #505 `2d67708e07728b13b5d2a9eda299ace8a1608163`; kernel/DTS #220 `26aa77c317cd029d16e58890c532562ca275c9f0` | Node absent, disk `ro=0`; all 85 partitions `ro=1`; `sdb`–`sdf` `ro=1` | `uname -r` `7.3.0-rc6-omamobile-push1`; `qcom_wdt` bound and feeder running; simpledrm fb0, USB/SSH and reserved `0x85fc0000–0x8a8fffff` passed. Physical screen, keys, touch, GPU and Wi-Fi not tested. RAM boot only; no UFS write. |
| 2026-11-10 | `540b5d31ea73a31ade9a8d8cb5152cf701dc3c2ad8256734790b0ef2db6dbdd0` | Combined #503/#505; kernel/DTS #220 `055a4019998f22cc0e2a8afef7650274a6ce0657` | Node absent, disk `ro=0`; all 85 partitions `ro=1`; `sdb`–`sdf` `ro=1` | Watchdog/feeder, simpledrm, USB/SSH, reserved TZ range, pinned host key and `reboot-to bootloader` passed; physical keys not captured. |
| 2026-11-10 | `a2d435a7430e7e4c145c61cdb9866d16929731859d91c7105e6bfcaf9e3e9dd7` | Rebased #503 NFS image with #220 `055a4019998f22cc0e2a8afef7650274a6ce0657` | `/dev/sda` present, set `ro=1`; six disks and all 85 partitions read back `ro=1` | `uname`, NFS root, multi-user systemd, watchdog and SSH passed; generic Arch test root only; link-loss recovery and Omarchy desktop untested. |
| 2026-11-10 | `0ee4f11d1973085c434e741a2e9dd73af5a9cd157296c25801ed5a92a6b9e9d9` | #505 `994944d7ecbacd69444221e6951153cb329a374e`; kernel/DTS #220 `055a4019998f22cc0e2a8afef7650274a6ce0657` | Node absent, disk `ro=0`; all 85 partitions `ro=1`; `sdb`–`sdf` `ro=1` | Watchdog/feeder, framebuffer, USB/SSH, reserved TZ range and `reboot-to` passed; physical keys not captured. |
Expand All @@ -26,6 +27,21 @@ name list. The retained backup and kernel records cover 84 non-userdata GPT
partitions plus `userdata`; the other seven names cannot be identified from the
retained artifacts and remain unknown.

## 2026-11-11 — rebuilt #505 RAM image

Built and booted `boot.img` SHA-256
`665fcbd682cd8e64b3ffec1ff7f4ab9ca33a26b9b47b11073be7a3c267abf2b1` with
`fastboot boot` from #505 `2d67708e07728b13b5d2a9eda299ace8a1608163` and
kernel/DTS #220 `26aa77c317cd029d16e58890c532562ca275c9f0`. `uname -r` was
`7.3.0-rc6-omamobile-push1`. The `/dev/sda` whole-disk node was absent; its
sysfs flag remained `ro=0`. Nodes `/dev/sdb`–`/dev/sdf` were present with
`ro=1`; all 85 partition flags were `ro=1`, and `ufs-ro` logged the guard for
each. `qcom_wdt` was bound and the watchdog feeder was running. simpledrm
registered `fb0`; authenticated USB SSH worked. `/proc/iomem` reserved
`0x85fc0000–0x8a8fffff`, including the former TZ range. The physical screen,
keys, touch, GPU rendering and Wi-Fi were not tested in this run. Only
`fastboot boot` was used; no UFS partition was written.

## 2026-11-10 — final PR #505 RAM image

Booted image SHA-256 `0ee4f11d1973085c434e741a2e9dd73af5a9cd157296c25801ed5a92a6b9e9d9` with `fastboot boot`; it was built from PR #505 head `994944d7ecbacd69444221e6951153cb329a374e` and kernel/DTS PR #220 head `055a4019998f22cc0e2a8afef7650274a6ce0657` (touch PR #219 is merged). `uname -r` was `7.3.0-rc6-omamobile-push1`; `/` was the initramfs (`rootfs`). The guard reported the UFS devices read-only. Sysfs showed six disks: `sda` had `ro=0` but its whole-disk `/dev/sda` node was absent; `sdb`–`sdf` each had `ro=1` and present nodes. All 85 partitions had `ro=1`. This matches PR #505's intended missing-node case for `sda`; no UFS write was attempted.
Expand Down
11 changes: 11 additions & 0 deletions device/dipper/device.conf
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# SPDX-License-Identifier: MIT
# RAM-only first-light descriptor for Xiaomi Mi 8 (dipper).
# Persistent install/update is disabled: the phone has one OS boot partition.
CODENAME=dipper
NAME="Xiaomi Mi 8"
SOC=sdm845
COMPATIBLE="xiaomi,dipper"
BOOT_METHOD=ram-only
BOOT_IMAGES=""
UFS_RW=""
PANEL_SIZE=1080x2248
87 changes: 87 additions & 0 deletions device/dipper/kernel.config
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
# SPDX-License-Identifier: MIT
# dipper's kernel fragment, merged after kernel/configs/omamobile.config.
#
# Everything the phone needs to reach a shell is built in, not a module. The
# first boot proved why: arm64 defconfig makes the Qualcomm PHY drivers and the
# UFS glue modules, while dwc3 and ufshcd are built in. So they probed, found no
# PHY, and gave up -- the kernel logged
# platform a600000.usb: deferred probe pending: dwc3: failed to initialize core
# gcc-sdm845 100000.clock-controller: sync_state() pending due to 88e8000.phy
# and the initramfs never got USB or storage. Modules in the initramfs do not
# help when nothing loads them before the devices probe.

# USB and UFS PHYs. Without these, both the USB gadget and storage are dead.
CONFIG_PHY_QCOM_QMP=y
CONFIG_PHY_QCOM_QMP_COMBO=y
CONFIG_PHY_QCOM_QMP_UFS=y
CONFIG_PHY_QCOM_QUSB2=y

# Storage: the core is already built in, the Qualcomm glue was not.
CONFIG_SCSI_UFS_QCOM=y

# The Type-C port manager on the PMIC, for the role switch and VBUS detection.
CONFIG_TYPEC_QCOM_PMIC=y

# Populate the PMIC power/resin key children before the initramfs checks keys.
CONFIG_POWER_RESET_QCOM_PON=y

# The FTS5 driver is upstream after PR #219, but PR #220 has no Dipper touch
# node yet. Keep it built in for a later node/overlay test.
CONFIG_TOUCHSCREEN_STMFTS=y

# Console log into the stock ramoops region: the only way to read an early hang
# on a phone with no serial header.
CONFIG_PSTORE=y
CONFIG_PSTORE_RAM=y
CONFIG_PSTORE_CONSOLE=y

# --- the same lesson, applied to everything first light touches ---------------
# Devices probe once, early. A driver that only turns up later as a module never
# gets a second chance: the device is left unbound and not even on the deferred
# list. The first boot proved it for the PHYs; the second proved it again for
# i2c (geni_i2c loaded by hand bound to nothing, and `bind` by hand failed).
# So everything needed to reach a usable system is built in.

# i2c: built in for the follow-up FTS5 node; PR #220 does not enable it yet.
CONFIG_I2C_QCOM_GENI=y
CONFIG_QCOM_GPI_DMA=y
# Nothing of ours is on SPI, so it stays a module: every built-in byte counts
# against the ABL kernel limit below.
CONFIG_SPI_QCOM_GENI=m

# Display comes from the bootloader's framebuffer through simpledrm, not from
# the MSM display driver, so DRM_MSM stays a module. Built in it pushed the
# kernel past about 16 MiB, which this ABL refuses outright:
# Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
# Nothing loads it; the panel path is open work (see NOTES.md).
CONFIG_DRM_MSM=m
CONFIG_DRM_SIMPLEDRM=y
CONFIG_SYSFB_SIMPLEFB=y

# The remoteprocs Wi-Fi depends on (the modem hosts the WLAN firmware) stay
# modules. Built in they pushed the kernel past what this ABL will load: a
# kernel+dtb of 16,247,767 bytes boots and 16,376,528 does not, with only
# Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
# to go on. In the root filesystem udev loads them; the bring-up initramfs does
# not need the modem.
CONFIG_QCOM_RPROC_COMMON=m
CONFIG_QCOM_Q6V5_PAS=m
CONFIG_QCOM_Q6V5_MSS=m
CONFIG_QCOM_SYSMON=m
CONFIG_RPMSG_QCOM_GLINK_SMEM=m

# Left as modules with DRM_MSM: pinning them only mattered to allow DRM_MSM=y,
# which the ABL size limit ruled out.
CONFIG_QCOM_OCMEM=m
CONFIG_QCOM_LLCC=m

# This phone's ABL refuses a boot image whose kernel is too large, saying only
# Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
# Measured: kernel+dtb of 16,247,767 bytes boots, 16,343,459 does not. The
# boundary sits at 0xF80000 = 16,252,928, which tools/dipper/build-boot.py now
# refuses to cross so the failure is ours and explained, not the bootloader's
# and silent.

# The DSI core can be a module: the panel driver that needs it is one too, and
# the display comes from simpledrm over the bootloader's framebuffer.
CONFIG_DRM_MIPI_DSI=m
1 change: 1 addition & 0 deletions docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@ Devices we'd like to support, with the closest starting point. Open an issue to
| Pixel 11 Pro, 11 Pro XL, 11 Pro Fold | grizzly, kodiak, yogi | malibu (Tensor G6) | stock facts, contributors welcome: 11 Pro ([#26](https://github.com/derekross/omarchy-mobile/issues/26)), 11 Pro XL ([#199](https://github.com/derekross/omarchy-mobile/issues/199), [notes](../device/kodiak/NOTES.md)), 11 Pro Fold ([#40](https://github.com/derekross/omarchy-mobile/issues/40)) |
| Pixel 4 | flame | SM8150 (Snapdragon 855) | **WIP, community port**, in the matrix above: the RAM-only first-light probe is merged ([BRINGUP-M1](../device/flame/BRINGUP-M1.md)); the native install is in review, split out of [#17](https://github.com/derekross/omarchy-mobile/pull/17) into [#55](https://github.com/derekross/omarchy-mobile/pull/55), [#56](https://github.com/derekross/omarchy-mobile/pull/56), [#58](https://github.com/derekross/omarchy-mobile/pull/58) and [#59](https://github.com/derekross/omarchy-mobile/pull/59) |
| 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 |
| Xiaomi Mi 8 | dipper | SDM845 | **WIP, community port:** the RAM-only first-light probe is merged ([BRINGUP-M1](../device/dipper/BRINGUP-M1.md), [NOTES](../device/dipper/NOTES.md)); single-slot, no install path yet. Kernel: touch [#219](https://github.com/derekross/linux-omarchy-mobile/pull/219) merged, board DTS [#220](https://github.com/derekross/linux-omarchy-mobile/pull/220) and panel [#218](https://github.com/derekross/linux-omarchy-mobile/pull/218) in review. |
| 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; `omamobile images` packs its header-v0 boot image, and its `UFS_RW_LUNS=sde` (the guard's second-LUN list, #530) comes with the slot-B install |
Expand Down
Loading