Repository navigation
device-dodge 0.1.0: the OnePlus 13's device files, and qcom-abl boot images - #111
Conversation
|
I read the shared parts against the Pixel 9a (tegu), which uses the same installer.
|
|
Thanks for checking it against tegu, good to hear the Pixel path is unchanged. Agreed on the firmware copy: it's a second Qualcomm exception of the same kind as the slot-flag write. It's now named in CONTRIBUTING §3.1, with the partitions, the check before the copy, the verification after it and the way back. AGENTS.md points to it, and I reworded the installer comments so they no longer say those partitions are never flashed. Commit: f38c7ab |
Move the OnePlus 13 row into the main matrix (it had landed under the cheetah detail table with a missing column) and replace blanket WIP cells with legend words backed by NOTES evidence. Correct Adreno 830 (was A740), WCN7860 naming, USB replug and Bluetooth A2DP gaps, and point Wanted plus README at derekross#111 / kernel derekross#115. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
|
Thank you, @mrlund, and welcome. A OnePlus 13 running Omarchy with display, GPU, Wi-Fi, audio, sensors and LTE data is a big piece of work, and a lot of this PR shows real care: the modem only ever runs on copies ( The phones in this project have calibration data that can't be replaced, so the rules in CONTRIBUTING §3 are mine to change, and I have to read this PR mostly as a safety review. As it stands I can't merge it. Here is why, and a route that gets most of it in quickly. 1. The firmware copy is a policy decision, and the PR grants it to itself. The helper writes
2. 3. Omarchy on slot A, and the allowlist. Two of the shared changes affect every phone:
4. The storage guard is a fork. 5. The record has to match the trees.
6. Backups before radio work. CONTRIBUTING §3.3 asks for a read-only copy of the modem's partitions (here A route that lands most of this soon: split the PR in two.
Two smaller things for later: most of the runtime pieces are I know this is a lot of feedback for a first PR. Most of it comes from the phones we can't afford to lose, not from the quality of your work, and I'd like this port in the tree. |
3752429 to
697554c
Compare
|
Thanks Derek — appreciated the careful read, and the welcome. Happy to take the split you suggested. Pushed a rewritten This PR (device only). Cut down to The other fixes, also in this PR:
Installer generalisation comes as a second PR after you've decided on §3.1. Two things I'd like to put on the record, then leave to you: 1. Firmware copy (why it exists; moves to PR 2). 2. Boot-success (not modem-related; asking which shape you want). On Tensor/Pixel the same job lives in I'm fine either way:
Which do you prefer? |
|
Thank you, @mrlund, for taking the split so quickly, and for a reply that goes through my points one by one. The PR is now much easier to review. The installer, CONTRIBUTING and AGENTS changes are gone, the boot-success timer is gone, the allowlist is Some things still need fixing before it can merge. The first one stops the build.
Smaller things, none of them blocking:
CI for this push is waiting for my approval because you're a first-time contributor. I'll approve it. I ran Thanks again. The device side of this is careful work, and once the init path is right and there's a boot from this tree, it's close. |
|
Thanks @derekross. Going through your latest points in your numbering. The branch is now at 1. INITRAMFS_INIT. Fixed to 2. Shared init / LUNs. Read-only on the phone: userdata is sda15, boot_b is sde48 (both LUNs 4096-byte sectors). The shared init’s sda-only allowlist therefore keeps boot_b read-only — which is what the guard should do — and the old “day-2 updates rewrite boot_b” claim is wrong here until a LUN-aware follow-up (separate branch, not in this PR). BRINGUP and NOTES mark the shared init as untested on dodge until a full phone-smoke of both PR heads from images built by 3. flash. Refuses 4. GPT record. BRINGUP §7 now has the LUN (sde), 4096-byte sectors, the primary and backup GPT (8 sectors / 4 files), bit 54 on boot_b (and boot_a), header and array CRCs, and getvars (both slots successful=yes, unbootable=no, retry 6/6, current b). This round was a read-only dump — no GPT write — so it is the current state, not a before/after. By hand, once per install of slot B’s boot image; never from a service or at boot. Rollback is restore those four dump files onto the matching LBAs; if both GPT copies on sde are bad the phone is likely EDL-only, and I have not checked whether this ABL takes 5. Matrix. USB / Bluetooth / Battery cells are 6. Version / title. Package version is Smaller. Chainload stays in the PR (PLAN.md / dodge_vbif / timing-probe removed). This ABL refuses header-v2 under SmokeMorning baseline, RAM-only
Tip |
1ff57b9 to
fabb349
Compare
|
Thank you, @mrlund, for going through my last comment point by point, and for answering with the facts I asked for rather than guesses. The I checked the new head against the one I reviewed last time. The new part of this push is the boot image itself:
Smaller things, none of them blocking:
When this merges I'll write the squash message myself, because some of the commit messages still describe the earlier header-v2 version. Thanks again. This is close, and the record you've built of how this ABL behaves will help the next Qualcomm phone too. |
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Hey there, happy to help. I have a OnePlus 13. Happy to test or contribute in any way. |
|
Thanks @derekross, and thanks for approving CI. The branch is now at Blockers
Also in this tip
Factory reset / way back. Stock's own factory-reset path over a foreign userdata has not been confirmed on this phone, so BRINGUP §7 still uses Evidence RAM-only Sound playback on a fresh tip RAM boot the same afternoon (Europe/Copenhagen): 4 clk WARNs during msm probe (traced; count = 4)Clocks: phone-smoke (RAM tip after one-hand tip-modules-overlay; tools at `ce58ee7` (branch tip later `eb0b9a2`), 2026-10-31 afternoon)Early pre-overlay unit failures (kmod-overlay / adsp-battery / …) are expected without a packaged Display is
|
Device-only first cut for OnePlus 13 (dodge). Omarchy on slot B with UFS_RW="boot_b userdata", shared initramfs/init, BOOT_METHOD=qcom-abl. BRINGUP records how this phone was installed (firmware A→B for ARB, GPT bit 54 by hand); the inactive-slot installer and firmware-match helper are deferred. Includes the reboot wrapper the package test compares. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
USB gadget networking, SSH, mirrorlist and reboot-to, with the package test that cmp's reboot and reboot-to.c against device/dodge/. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Phone-verified userspace for the subsystems that work on dodge. Modem units stay inert without /etc/omamobile/modem-probe.enable; README covers CONTRIBUTING §3.3 off-phone backups with SHA256SUMS. No firmware, EFS or calibration blobs. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Status cells are testing (kernel in review, derekross#115). No Wanted-line or README edit. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Qualcomm ABL phones build a single header-v2 boot.img (kernel + ramdisk + DTB). load_device still refuses *_a in UFS_RW and keeps the shared allowlist; images packs boot.img and returns. install-phone continues to refuse qcom-abl until a later installer PR. tests/boot-method covers the acceptance path. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
INITRAMFS_INIT lacked the leading slash, so bin/omamobile initramfs looked under device/dodge/ for the shared init that this PR removed. Match every other descriptor: /initramfs/init. qcom-abl images: drop the tools/dodge-try comment, and prefer mkbootimg.py (tree-local or SRC_DIR) over a host mkbootimg. The build container has no android-tools. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
boot_b is on LUN sde (sde48); userdata is sda15. The shared init's sda-only guard therefore keeps boot_b read-only, so day-2 push cannot rewrite it on dodge until a later LUN-aware change. Drop the claim that day-2 updates rewrite boot_b. Also record that this ABL boots a header-v4 kernel-only chain-loader (built-in /omamobile init → kexec stage 2), not a plain qcom-abl header v2 pack from omamobile images. Pixel behaviour of the shared init is unchanged. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Keep the chainload path: OnePlus ABL refuses header-v2 under `fastboot boot`, and a header-v4 boot.img with a ramdisk still pairs with the flashed vendor_boot DTB (uploaded boot ramdisk ignored). The only RAM-only way to our DTB without flashing vendor_boot is a v4 boot.img whose kernel has a built-in initramfs that kexecs stage 2. - tools/dodge-chain: pack-only helper (LIVE_DTB required; host mkbootimg) - bin/omamobile images (qcom-abl): call dodge-chain; Pixel path unchanged - bin/omamobile flash: refuse qcom-abl (set_active vs GPT bit 54) - chainload/init: PID 1, mounts proc/(optional)sysfs only, never exits; no PLAN.md / dodge_vbif / timing-probe remnants - drop chainload/probe-init; rewrite chainload/README - tests/boot-method: images accepts qcom-abl; flash refuses it Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
- packages/omamobile-device-dodge version 0.1.0 - DEVICES.md / NOTES.md: USB, Bluetooth, Battery partial → testing - setup-stock: require USER (no default ml) - modem/README: dodge has no Pixel phone-provision path; modules under .held/ - bluetooth/README: same modules-path note for the peach/WCN stack - BRINGUP-M1: why the chain stays; stage 1 is PID 1 and touches no disk; flash refuse; real LUN map (userdata sda15, boot_b sde48); GPT §7 with tonight's getvars (both slots successful=yes, unbootable=no, retry 6/6, current b); morning-only read-only GPT steps listed Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Documented in BRINGUP that stage 1 is PID 1 and touches no disk. Add a soft check before kexec: if /proc/mounts somehow lists a /dev/sd* mount, hold and reset instead of loading stage 2. Stage 1 still never opens or writes storage itself. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
BRINGUP §6 now notes the derekross#115 tip re-smoke after the dual-memory fix (booted; SSH ~26 s; storage/root/USB/Hyprland ok; module-backed drivers skipped for the tip uname). NOTES states the shared init is still untested on dodge. BRINGUP also says this PR has no in-tree day-2 path. Assisted-by: Grok Bot Signed-off-by: Martin Lund <mrlund@hotmail.com>
Blockers: - Stage 1 disables SCSI_UFS_QCOM/UFSHCD; drop the 'may still probe UFS' caveat from BRINGUP and chainload README. - Require device/$DEVICE/chainload/ (CHAINLOAD_DIR) so splash/panel/RSC/ SMMU stay out of the generic path; stage2.dtb naming; boot-method coverage for missing/present chainload. - push refuses qcom-abl early like flash; flash message says there is no in-tree day-2 path. Non-blocking: - Tree-local mkbootimg only on the qcom-abl path; Pixel stays on $SRC_DIR/system/tools/mkbootimg only. - Pass KERNEL_DIR / CHAINLOAD_DIR / LIVE_DTB / STAGE2_CMDLINE into the container; build stage 1 via in_container when IMAGE+CLANG_DIR+WORK are set, otherwise host make LLVM=1 as before. - Stage 1 cmp of this boot's memory reg in /proc/device-tree against the copy saved at pack time from LIVE_DTB, holding on mismatch. - BRINGUP: omamobile-fastboot/sysrq warning + button combos; §7 -s <serial> placeholder; justify fastboot -w; GPT getvar table; bit-54 hand-write was boot_b only. - Wire descriptor CMDLINE into STAGE2_CMDLINE; stage 1 appends androidboot.slot_suffix from /proc/bootconfig or chosen/bootargs (CMDLINE_FORCE hides ABL keys from /proc/cmdline). Assisted-by: Grok Bot Signed-off-by: Martin Lund <mrlund@hotmail.com>
A pack that reused STAGE2_OUT left arch/arm64/boot/Image with INITRAMFS_SOURCE and CMDLINE_FORCE set; the next pack nested that stage-1 Image as stage 2 (~87MiB) and hung on RAM boot. The morning-good ~66MiB pack used a clean ~44MiB stage-2 Image. assert_clean_stage2_image refuses: - CONFIG_CMDLINE_FORCE=y or non-empty INITRAMFS_SOURCE (ikconfig), else the stage-1 cmdline marker rdinit=/omamobile/init (strings fallback) - STAGE2_IMAGE under CHAIN_OUT - CHAIN_OUT equal to STAGE2_OUT check-stage2-image exercises the same rules; tests/boot-method covers marker, CHAIN_OUT nest, equal outs, and a clean Image. Assisted-by: Grok Bot Signed-off-by: Martin Lund <mrlund@hotmail.com>
ABL does not put androidboot.slot_suffix in bootconfig or chosen/bootargs under `fastboot boot`, so the live readers alone still leave stage 2 without a slot. Pack /omamobile/slot_suffix from device.conf's OMAMOBILE_SLOT and have stage-1 init fall back to it after the two live sources. Live bootconfig or bootargs still win when present. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Fill BRINGUP §6 for the 2026-10-30 evening RAM-only chain smoke (boot ok with packed slot_suffix=_b, 0 WARN, adsp running). Reword the memory.reg docs/hold message so "live" means this boot's tree, not the pack-time LIVE_DTB capture. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
BRINGUP gave Power / VolDown+Power as plain instructions; those combos have not been verified on this phone. Tag them unverified, and record that phone-smoke's boot check on fastboot-boot RAM images is descriptor-derived via the packed OMAMOBILE_SLOT fallback. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Root cause of the evening tip regression (simpledrm, no GPU/touch/Wi-Fi): omamobile-display-msm stamped /run/omamobile-display-msm.tried when dispcc-sm8750.ko was missing (no $uname.held), so a later tmpfs modules overlay could not retry. Bare modprobe msm without dispcc then hit msm-mdss -110 after the deferred-probe timeout. Do not stamp when dispcc is absent; treat "already done" as a bound DSI connector, not mere /sys/module/msm (udev can load msm before clocks). Stage 1 now dumps /proc/bootconfig and chosen/bootargs to kmsg, logs which slot source won, and carries omamobile.slot_src= on the stage-2 cmdline (stage-1 kmsg is lost at kexec). This ABL still omits androidboot.slot_suffix under fastboot boot — keep the packed OMAMOBILE_SLOT fallback. boot-method tests cover both guards. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
After a tmpfs modules overlay, udev can load msm before dispcc; mdss then probes with -110 and stays failed even once dispcc is present. Once the unit has loaded dispcc, unbind/bind ae00000.display-subsystem so probe retries. OMAMOBILE_MODULES_H lets tests drive an empty modules tree; boot-method now asserts exit 0 and no stamp functionally. Soften the stage-1 ABL-empty comments until a slot_src= boot confirms stage 1's view. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Tip Images with a tmpfs modules overlay were insmod'ing the userdata 6.16 panel/msm under the display dir (Invalid module format) and giving up. Prefer that out-of-tree .ko only when vermagic matches uname -r (whole release, space-terminated). Also record whether msm was already loaded before the dispcc-first loop: rebinding right after a fresh insmod can race the probe and hang the oneshot past TimeoutStartSec (seen on a tip RAM boot; not yet re-verified as fixed). Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Rootfs a345 rebound as soon as status!=connected and destroyed a half-ready probe (no /dev/dri on 2026-10-31 gated boots; healthy boot -38 won the race). Keep msm_preloaded, wait briefly while any DRM card exists, and rebind only when there is still no card*-DSI-1 node. boot-method covers the half-ready skip and the classic no-DSI rebind. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Tip RAM boots with a tmpfs modules overlay never enumerated 17cb:110e: omamobile-wifi-pcie only insmod'd the packaged gpu2 kos (wrong vermagic) and never loaded tip pwrseq/phy before the PCIe rescan. Prefer modprobe so the overlay's matching modules win; keep the held /usr/local/lib/omamobile kos as the gpu2 fallback. Same for ath12k once the endpoint appears. phone-smoke counted WARNING: CPU only. Tip 7.3 prints WARNING: drivers/... at ..., so the 4 clk_core_disable/unprepare WARNs during msm(+) were reported as 0. Count both forms. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
7.3 prints WARNING: <path>:<line> at … for any source file, not only drivers/. Count CPU: and that form so WARNs from kernel/, mm/, fs/, net/, and friends are not reported as zero. Also drop private rootfs / boot labels from display-msm and boot-method comments, and note that the DSI wait is a fixed grace (simpledrm already owns card0). Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Bring the phone's omamobile-touch-load into device/dodge/touch and prefer modprobe so a tip Image with a tmpfs modules overlay gets matching kos. Fall back to the held files under /usr/local/lib/omamobile for the packaged gpu2 rootfs boot. Order stays gpi -> spi_geni_qcom -> synaptics_tcm2. boot-method covers modprobe preference and held fallback. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Make tip RAM boots work with a tmpfs modules overlay as the only hand step. adsp-battery, bluetooth and audio-bringup prefer modprobe (tip overlay tree) then fall back to the pinned held kos. Restore omamobile-kmod-overlay in-tree and add omamobile-tip-modules-overlay: extract the matching modules tar onto a tmpfs under /lib/modules/$uname, clear early-boot stamps, restart display/wifi/touch/adsp/bt/audio/sensors, and bounce sddm once DSI is bound (B avoids the simpledrm→msm sddm-helper 255 by ordering display-msm before sddm; tip starts sddm early so the bounce is the small device-scope fix). Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Install tip-aware ADSP/audio scripts through a private bind of / when omamobile-kmod-overlay has bound omamobile.$R over /usr/local/lib/omamobile, so tip RAM boots (no bind) see them on the real rootfs. Prefer LOCAL ($D) before pinned HELD for adsp-battery fallback (held also ships q6v5_pas / pd_mapper). Stamp the tip sddm bounce so a helper re-run does not kill a live session. Cite sddm.service.d/50-dodge.conf for B's After=ordering. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
Holding Power alone under Omarchy Mobile opens the power menu and does not force a restart (tested 2026-10-31 on slot B). Forced restart that works: hold Power + Volume Up + Volume Down until it resets (confirmed; no hold time claimed). Fastboot entry: from power-off, hold Volume Down while powering on (confirmed). Drop the prior Power ~30 s and VolDown+Power ~20 s claims. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
eb0b9a2 to
b2d530b
Compare
|
Thank you, @mrlund. All three things I asked for are in, and I checked each in the code: stage 1 builds without UFS and the pack refuses if it comes back, Small things for a follow-up, not blocking: |
The Pixel 9a's SoC and board device tree, 120 Hz, the touchscreen and its sleep fix, NFC's ST54L mode and poll stop, and the panel's local high brightness mode are merged (kernel #80/#81, #88, #82, #131, #71, #126; #155). The Pixel 8 Pro's buttons are in the published kernel (kernel #148). The OnePlus 13's device package is merged (#111), mustang has stage 0 notes (#198), and kodiak joins the Pixel 11 row (#201). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…l bind on failure, park the deliberate panic (#218) Follow-ups from #111: bin/omamobile fastboot refuses a qcom-abl device after reading its descriptor and before any phone I/O (Pixels only gain the descriptor read; tests/boot-method covers both boot methods), the install scripts undo their bind of / in an EXIT trap when a step fails, and BRINGUP parks the deliberate sysrq panic until it has a gated runbook.
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…-loader boot images (derekross#111) The OnePlus 13 (dodge, SM8750) gets its device descriptor, notes and device package, and bin/omamobile images learns the qcom-abl boot method: a stage-1 chain loader built without UFS (the pack refuses if UFS comes back) that hands over to the device's own chainload/ directory. images refuses without that directory, and push and flash refuse qcom-abl before touching the phone, so nothing in the tree writes this phone yet; the guarded installer follows in a later pull request. The storage guard allows only boot_b and userdata. The Pixel images build byte for byte the same (tests/images-layout). tools/phone-smoke now counts warnings in the 7.x kernels' format, which changes the WARN count on every phone's report (it was always 0 before). The CI Tests failure on this head is the owl-idle timing flake fixed by derekross#207 (the run tested against a base from before it).
The Pixel 9a's SoC and board device tree, 120 Hz, the touchscreen and its sleep fix, NFC's ST54L mode and poll stop, and the panel's local high brightness mode are merged (kernel derekross#80/derekross#81, derekross#88, derekross#82, derekross#131, derekross#71, derekross#126; derekross#155). The Pixel 8 Pro's buttons are in the published kernel (kernel derekross#148). The OnePlus 13's device package is merged (derekross#111), mustang has stage 0 notes (derekross#198), and kodiak joins the Pixel 11 row (derekross#201). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…l bind on failure, park the deliberate panic (derekross#218) Follow-ups from derekross#111: bin/omamobile fastboot refuses a qcom-abl device after reading its descriptor and before any phone I/O (Pixels only gain the descriptor read; tests/boot-method covers both boot methods), the install scripts undo their bind of / in an EXIT trap when a step fails, and BRINGUP parks the deliberate sysrq panic until it has a gated runbook.
Martin's rule for this phone: a boot image goes only onto the inactive slot, and only after that slot's firmware matches the running one (OxygenOS anti-rollback). The helper that checked this went out of the merged derekross#111 with the deferred installer, and it ran from the dodge initramfs that main no longer has. device/dodge/firmware-match/check is its read-only half, as a script for the booted Omarchy root (or piped over tools/phone-ssh): sha256 of the 33 A/B firmware pairs, the same list as the 2026-10-28 copy, without vbmeta, qweslicstore, oplusstanvbk or the boot images. It prints MATCH, DIFF or MISSING per pair and one RESULT line, exits 0 only when every pair matched, and never writes: no setrw, no dd, no copy mode. A copy stays a by-hand step the owner approves. Signed-off-by: Martin Lund <mrlund@hotmail.com> Assisted-by: Grok Bot
dodge: OnePlus 13 device files (device-only)
Base:
mainBranch:
dodge/pr-device-v1on https://github.com/mrlund/omarchy-mobileCompanion kernel PR: derekross/linux-omarchy-mobile#115
Summary
Device-only first cut for the OnePlus 13 (dodge, SM8750). The guarded
inactive-slot installer and firmware-match helper are deferred to a later
PR (after the §3.1 call). How this phone was installed is a record in
BRINGUP, not a procedure for others.
device/dodge/— descriptor, NOTES, BRINGUP, audio, Wi-Fi, Bluetooth,sensors, modem (opt-in units, no blobs), desktop, display, idle, timesync,
chainload helpers, reboot wrapper
packages/omamobile-device-dodgedocs/DEVICES.mdmatrix row — statusestesting (kernel in review, #115)(no Wanted line, no README edit)
bin/omamobile— acceptsBOOT_METHOD=qcom-abl(two-stage chain viatools/dodge-chain;flashrefuses qcom-abl).UFS_RWstill refuses*_a.install-phonestill refusesqcom-abluntil the installer PRinitramfs/init(no dodge fork);UFS_RW="boot_b userdata",OMAMOBILE_SLOT=bCompanion kernel: derekross/linux-omarchy-mobile#115.
Feature matrix
Aligned with docs/DEVICES.md and
device/dodge/NOTES.md.
boot_b; kernel #115; installer deferredboot_b+ userdata allowlist; shared initInstall record (not a procedure)
See device/dodge/BRINGUP-M1.md: firmware A→B
copy for OxygenOS ARB (27 pairs, sha256 read-back; vbmeta/EFS/NV untouched),
Omarchy on
boot_b, GPT bit 54 marked by hand. Tip re-smoke of companionkernel
#115head recorded in BRINGUP §6 (SSH ~26 s; module-path gaps for tip uname).Checklist
tools/pr-check origin/main HEADcleantests/boot-method,tests/storage-guard,tests/install-phone, device package test green