Repository navigation
device/enchilada: OnePlus 6 descriptor, notes and a WIP matrix row (#432) - #445
Conversation
|
Thank you, @matthewjaybarr-png. This is a careful first PR: the descriptor can't do anything yet (every command refuses Three changes before I merge, all in the text:
A few smaller things, none blocking:
I'll answer the stock-restore plan on #432 separately. Thanks again. This is a solid start for our first SDM845 phone. |
7dab045 to
a3244d9
Compare
|
Thanks, Derek. All three are done, and the smaller items too. Pushed as one amended commit. 1. Boot path per entry, and the commit message. Part of it did run from slot B, and the notes now say which part. Every entry names its boot path and where its root was:
The intro now names both builds: the first-light kernel, and the same tree plus the six matches. The commit message (the squash message) says the same and no longer claims everything ran from 2. Matrix row. The Boot cell names the kernel: Linux 7.1-rc1 from the sdm845-mainline tree, not linux-omarchy-mobile. Display and USB net now link to the first-light entry. 3. Hand writes and slot flags. The slot section now lists every write I made by hand, outside
I have to correct one thing in my #432 reply. I wrote that this all came before your reply, but the timestamps say otherwise. Your reply was posted at 21:13 UTC. The second Smaller items:
|
a3244d9 to
10ce77c
Compare
|
Thank you, @matthewjaybarr-png. This is a model §3.1 record: every entry says how it booted, every write by hand is listed, including the ones after my reply with their exact minutes, and the slot flags are on file from before and now. The two boot paths also explain the one thing I couldn't square last time, so thank you for digging that out rather than smoothing it over. The kernel in the Boot cell, the rescue's own guard described plainly, and the shipped descriptor in One small change before I merge, because of what we settled on #432 since you pushed: the new row under "Wanted" in A question I'd like recorded, not blocking: slot A is unmarked, and its retry count went from 6 to 5. If I read Qualcomm's bootloader right, Optional: the Boot cell could say the firewall and GPU results booted the Arch root on CI is waiting for my approval again after the push; I'll approve it. |
The OnePlus 6 (SDM845) is the first Snapdragon 845 phone here, claimed in derekross#432. This adds what the maintainer asked for as its first pull request: the descriptor, the notes, and a WIP row in docs/DEVICES.md. The descriptor sets BOOT_METHOD=android-v0 (header v0, gzip kernel with the DTB appended). No packer in this tree makes that image yet, so images, flash, push and the installer all refuse it before touching a phone; tests/boot-method checks that for any android-v0 descriptor and for the shipped enchilada one. The header-v0 packer and a LUN-aware UFS_RW come as separate pull requests. The notes record what is on each slot today and how it got there (stock is not on slot A, a CONTRIBUTING.md 3.1 event), including every write made by hand outside the installer, which will not be repeated, and the slot flags. Also the complete backup, the RAM-only first light, and two findings: ufw needs six netfilter matches the first-light kernel left out, and the Adreno 630 needs a zap shader signed for this phone. Tested: tests/all passes. On the phone, with Linux 7.1.0-rc1-sdm845 from the sdm845-mainline tree, not linux-omarchy-mobile: the first light was a fastboot boot that stayed in the initramfs; the firewall failure was seen booting boot_b with the root on userdata; the firewall fix and the Adreno result came from a fastboot boot of the boot_b image with the root on userdata. Each NOTES entry names its boot path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks, Derek. Done, in the same amended commit:
Slot A's retry count: I've added your reading to the slot-flags section as unconfirmed. If #432: understood about the CONTRIBUTING §3.1 entry for marking slot B. It will be its own pull request, with the LUN, the four sectors, the attribute bit, the CRCs, the slot flags before and after, a rollback for a corrupted table, and my written acceptance that slot A holds the rescue rather than stock. The LUN-aware
|
10ce77c to
a642cc4
Compare
|
@matthewjaybarr-png thank you. Everything from both of my reviews is in, and I'm merging this now. Two small things for whenever you next touch these
And please post the |
The OnePlus 6 (enchilada) ABL boots an Android boot image header v0: a gzip kernel with the DTB appended, no dtbo and no vendor_boot. Until now nothing in the tree could make one, so every path refused BOOT_METHOD=android-v0 and the port's first-light image was built by hand. load_device now accepts android-v0 with its own required keys and the six header fields (PAGESIZE, BASE and the offsets), checked as numbers; BOOT_IMAGES must be boot alone and boot_b must be on UFS_RW. images packs boot.img with the pinned mkbootimg.py: gzip -9n of Image with the (overlaid) DTB appended, the shared initramfs as the ramdisk, CMDLINE and the descriptor's offsets. mkdtboimg is only required for android-v4. The port stays RAM-only: fastboot, flash and push refuse android-v0 and point at `fastboot boot`, and the installer still refuses the method, until the slot-B install and its CONTRIBUTING.md 3.1 entry are agreed. Also in device/enchilada/NOTES.md and docs/DEVICES.md, from review on #445 and #432: link the maintainer's decision on restoring stock; say the firewall failure booted from boot_b after --set-active=b; and drop the guess that each rescue boot spends one of slot A's tries (after one more rescue boot A was still at 5 and B at 7). Tested: tests/boot-method (enchilada images reach the kernel check; fastboot, flash, push and both installer modes refuse; bad header fields refused; no phone access) and tests/images-layout, which gains an android-v0 layout test (one boot.img, header v0, page size and load addresses, kernel = gzip Image + DTB, ramdisk = initramfs, deterministic) while the gs201/gs101 baseline still matches 1e7a998 byte for byte. Against the 7.1.0-rc1-sdm845 build used for first light on 2026-11-04, images gives a boot.img byte-identical to the one that was booted then with `fastboot boot` (sha256 78d7bd1a...0d98c). Nothing was sent to the phone for this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erekross#445) The OnePlus 6 (SDM845) is the first Snapdragon 845 phone here, claimed in derekross#432. This adds what the maintainer asked for as its first pull request: the descriptor, the notes, and a WIP row in docs/DEVICES.md. The descriptor sets BOOT_METHOD=android-v0 (header v0, gzip kernel with the DTB appended). No packer in this tree makes that image yet, so images, flash, push and the installer all refuse it before touching a phone; tests/boot-method checks that for any android-v0 descriptor and for the shipped enchilada one. The header-v0 packer and a LUN-aware UFS_RW come as separate pull requests. The notes record what is on each slot today and how it got there (stock is not on slot A, a CONTRIBUTING.md 3.1 event), including every write made by hand outside the installer, which will not be repeated, and the slot flags. Also the complete backup, the RAM-only first light, and two findings: ufw needs six netfilter matches the first-light kernel left out, and the Adreno 630 needs a zap shader signed for this phone. Tested: tests/all passes. On the phone, with Linux 7.1.0-rc1-sdm845 from the sdm845-mainline tree, not linux-omarchy-mobile: the first light was a fastboot boot that stayed in the initramfs; the firewall failure was seen booting boot_b with the root on userdata; the firewall fix and the Adreno result came from a fastboot boot of the boot_b image with the root on userdata. Each NOTES entry names its boot path. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The OnePlus 6 (enchilada) ABL boots an Android boot image header v0: a gzip kernel with the DTB appended, no dtbo and no vendor_boot. Until now nothing in the tree could make one, so every path refused BOOT_METHOD=android-v0 and the port's first-light image was built by hand. load_device now accepts android-v0 with its own required keys and the six header fields (PAGESIZE, BASE and the offsets), checked as numbers; BOOT_IMAGES must be boot alone and boot_b must be on UFS_RW. images packs boot.img with the pinned mkbootimg.py: gzip -9n of Image with the (overlaid) DTB appended, the shared initramfs as the ramdisk, CMDLINE and the descriptor's offsets. mkdtboimg is only required for android-v4. The port stays RAM-only: fastboot, flash and push refuse android-v0 and point at `fastboot boot`, and the installer still refuses the method, until the slot-B install and its CONTRIBUTING.md 3.1 entry are agreed. Also in device/enchilada/NOTES.md and docs/DEVICES.md, from review on derekross#445 and derekross#432: link the maintainer's decision on restoring stock; say the firewall failure booted from boot_b after --set-active=b; and drop the guess that each rescue boot spends one of slot A's tries (after one more rescue boot A was still at 5 and B at 7). Tested: tests/boot-method (enchilada images reach the kernel check; fastboot, flash, push and both installer modes refuse; bad header fields refused; no phone access) and tests/images-layout, which gains an android-v0 layout test (one boot.img, header v0, page size and load addresses, kernel = gzip Image + DTB, ramdisk = initramfs, deterministic) while the gs201/gs101 baseline still matches 45e7109 byte for byte. Against the 7.1.0-rc1-sdm845 build used for first light on 2026-11-04, images gives a boot.img byte-identical to the one that was booted then with `fastboot boot` (sha256 78d7bd1a...0d98c). Nothing was sent to the phone for this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What and why
The first pull request for the OnePlus 6 (enchilada, SDM845), as suggested on #432:
device/enchilada/device.conf,device/enchilada/NOTES.md, and a WIP row indocs/DEVICES.md(matrix + Wanted). I'm opening it before the stock-restore plan because it writes nothing to any phone. If you'd rather it wait for that plan, I'm happy to hold it.BOOT_METHOD=android-v0(header v0, gzip kernel with the DTB appended). No packer in this tree makes that image yet, soimages,flash,pushand both installer modes refuse it before touching a phone.tests/boot-methodnow includesandroid-v0in its refused list and checks the shipped enchilada descriptor too, like flame's. The header-v0 packer (taking the header version as an input, so coral can reuse it) follows in its own PR, and so does the LUN-awareUFS_RW.omamobile.config), and the Adreno 630 needs a zap shader signed for this phone.no.Device and build
uname -r):7.1.0-rc1-sdm845(sdm845-mainline tagsdm845-7.1-rc1-r0+ six netfilter matches; see NOTES)Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packages: no packages touchedversionbumped: n/aCo-Authored-By:trailer, never aSigned-off-by:On the phone
fastboot boot(RAM); the firewall failure was seen bootingboot_b. Since the OnePlus 6 (enchilada, SDM845) port: RAM-only first light, contributors welcome #432 reply the phone has been RAM-only (onefastboot boot, the read-only backup andgetvar)tools/phone-smokewas not run. The phone is RAM-only and this change adds nothing that runs on it. linux-omarchy-mobile has not been tried yet.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)🤖 Generated with Claude Code