Repository navigation
Description
Device
| Model | OnePlus 8 Pro, EU variant IN2023 (siblings: IN2020 CN, IN2021 IN, IN2025 NA) |
| Codename | instantnoodlep |
| SoC | Qualcomm SM8250 (Snapdragon 865), Adreno 650 |
| RAM / storage | 8/12 GB LPDDR5, 128/256 GB UFS 3.0 |
| Display | 6.78" 1440x3168, 120 Hz AMOLED (Samsung AMS678UW01 on my EU unit; other panel variants exist) |
| Bootloader | Unlockable out of the box, fastboot oem unlock, no token or waiting period; unlock wipes data |
I own this phone (EU, IN2023) and can have it out of action for a while.
Why a port looks unusually plausible
SM8250 precedent in this project. The POCO F3 (alioth, SM8250 / SD870) was proposed as the first non-Pixel port in #25, paused by its author and closed on 2026-11-11, so the SoC is not new ground for this tree.
Most of the mainline kernel work already exists.
- Upstream Linux carries the SM8250 OnePlus family: the bindings, a common devicetree, panel and Synaptics TCM touchscreen drivers, merged with the initial OnePlus 8T support series (https://lwn.net/Articles/979482/).
- The community SM8250 mainline fork used by postmarketOS/Nura (https://gitlab.postmarketos.org/soc/qualcomm-sm8250/linux) carries
sm8250-oneplus-instantnoodlep.dtsand the fixes the phone needs, for example the Wi-Fi/BT DTS regression introduced around v6.11. - Nura (postmarketOS under its new name since 2026-09-27) maintains a device package for
oneplus-instantnoodlep, and an unofficial Nura image (https://github.com/naorunaoru/oneplus-instantnoodlep-nura-unofficial, releases October and November 2026, kernel 7.2) demonstrates on an IN2023 EU unit: display at 1440x3168 and 120 Hz, GPU, speakers and microphones, Wi-Fi, Bluetooth, modem/SIM/mobile data/SMS, GPS, NFC, sensors, and all five cameras through libcamera. - Firmware has a precedent too: Nura packages
firmware-oneplus-instantnoodlep(ath11k and modem firmware), and per CONTRIBUTING section 7 the per-driver firmware could instead come from the owner's own factory image.
A/B slots look compatible with the safety model. The phone has A/B boot slots (boot_a/b, dtbo_a/b, vbmeta_a/b, ...) with Android's dynamic partitions inside a shared super; userdata is a physical, non-slotted partition. A slot-B install (the phone's boot images on slot B, the Arch root on userdata, super untouched) looks compatible with keeping stock on slot A. To be checked in stage 0: the exact GPT/LUN layout, whether the slot flags live in GPT attributes or devinfo, and what the storage guard's allowlist would need here.
Stage-0 facts (read-only, to follow in this issue)
Following the process from #220, I will collect from my unit and post here:
- Unlock status: "OEM unlocking" in developer options, the
fastboot oem unlockresult, andfastboot getvar allincluding both slots' bootloader version. - The partition list:
ls -l /dev/block/by-name/(both slots, plus the LUN layout). - A stock
dmesgand the device tree, from a temporary-root session (fastboot bootof a patched image, nothing flashed). - How stock is restored: full-OTA payload images via fastbootd as the normal path, and the Qualcomm EDL (MSM Download Tool) service packages that circulate for IN2023 as the last resort, with the usual goal of never needing it.
Caveats I already know
- My EU unit has the Samsung AMS678UW01 panel the Nura port was tested with; OnePlus shipped other panel variants, which may need separate panel/DT work.
- Voice calls (VoLTE) on mainline are not yet verified working on this device; SMS and mobile data are.
- I am new to this project's tooling but comfortable with Linux, fastboot and kernel work, and I will follow the bring-up order in CONTRIBUTING and the [V]/[I] evidence discipline of the plans.
If these facts look right, would you add the phone to the Wanted list in DEVICES.md? Happy to be the hardware-and-testing half if someone more experienced wants to lead the port.
Activity
docs: drafts for the #808 stage-0 comment and the ticket-#8 device.co…
inumineq commentedon Nov 16, 2026
Status from the instantnoodlep port workspace (OnePlus 8 Pro, IN2023 EU, stock
IN2023_13.1.0.591(EX01)), plus the questions we need answered before any slot-B write.Where we are
Stage 0 is done. The bootloader is unlocked. Stock runs from slot A, and slot B holds the same
.591. A read-only SHA-256 comparison (taken with temporary root) shows all 19 slotted bootloader partitions (abl,xbl,xbl_config,tz,hyp,aop,devcfg,keymaster,modem, ...) identical across_a/_b. Radio/calibration partitions are backed up off-repo.M1a, RAM-only first light, passes with two kernels. Both runs used
fastboot bootwith the sharedinitramfs/initand the storage guard and no allowlist:omamobile(317d87dc2db0) plus our four DTS commits (7.3.0-rc6).Results: USB NCM and SSH come up, all 8 CPUs, the watchdog is fed, and every UFS partition is
ro=1with/dev/sdaremoved. Stock comes back on slot A with unchanged slot flags.Two ABL findings other ports may hit:
oplus,dtsi_noand then applies its dtbo entry. It refuses a RAM boot it cannot overlay, and does so silently:Booting OKAY, then it stays in fastboot.oplus,dtsi_no/oplus,pcb_rangecopied from stock, plus a hand-written__symbols__that points every label the stock overlay needs at disabled nodes under a root node with nocompatible.fastboot bootin the same fastboot session, after a refused one, failed AVB. ABL then ranHandleActiveSlotUnbootable: it marked slot A unbootable, set B active and cold-reset (generic Qualcomm ABLVerifiedBoot.cdoes the same). We recovered withset_active a. Our rule now:fastboot reboot bootloaderbetween RAM boots.AVB: stock
vbmetahas Flags 0.boot(location 4) anddtbo(location 3) are chain partitions with their own footers.Numbers for a GPT-attribute entry (from read-only stage-0 dumps)
userdataissda23(LUN 0);boot_b/dtbo_bare onsde, so the descriptor would needUFS_RW_LUNS=sde. Generic ABLSetActiveSlot(..., TRUE)clears the successful bit on the slot it activates, so a mark is still needed afterset_active b.Questions
UFS_RW_LUNS,SLOT_B_MARK) follow in a PR. Does instantnoodlep reusetools/mark-slot-b(tools/mark-slot-b and push over UFS_RW_LUNS, inert until the §3.1 entry (part 1 of #616) #651) unchanged?boot_b+ P_HDR, P_ENT, B_ENT, B_HDR" (theSLOT_B_MARKform above) what the entry should state?--set-active=b. On this ABL it also swaps the_a/_btype GUIDs and moves the UFS boot LUN. Should the plan record a before/after GPT of every LUN andbBootLunEnaround the first--set-active=b, and should the entry name that write too?boot_b. Given the chain descriptors, do you accept upstream's test-keyadd_hash_footeronboot_b(partition size 100663296, rollback 0,os_version12,security_patch2024-06-05)? Fordtbo_b: a footed image of our own, or leave stockdtbo_band rely on the overlay sink above?userdata, booted each time byfastboot boot, withUFS_RW=userdataonly and no slot-B or GPT write. Any objection?docs: drafts for the #808 stage-0 comment and the ticket-#8 device.co…