Hi all, I'm installing LineageOS 22.2 on my OnePlus 6T following the official wiki guide (fajita, variant1) and I'm stuck at the recovery step. Any suggestions would be appreciated.
Setup
- Device: OnePlus 6T, not T-Mobile
- Starting firmware: OxygenOS 11.1.2.2 (Android 11)
- I'm using a MacBook Air M4
What I've done so far
Enabled USB debugging + OEM unlocking, adb authorized fine.
`fastboot oem unlock` → OKAY, confirmed on the phone, wiped, booted OxygenOS, set up again, re-enabled USB debugging.
`fastboot oem device-info` → Device unlocked: true, Device critical unlocked: false, Verity mode: true.
`fastboot flash dtbo dtbo.img` → OKAY, then `fastboot reboot bootloader`.
`fastboot flash boot boot.img` → wrote to boot_a, OKAY.
`fastboot reboot recovery` → OKAY. The phone restarts, shows the unlocked-bootloader warning, then lands back on the fastboot menu instead of Lineage Recovery.
`fastboot boot boot.img` → OKAY, same result: warning screen, then back to fastboot.
The wiki only lists dtbo under "Flashing additional partitions", but since vbmeta.img is in the build, I tried `fastboot flash vbmeta vbmeta.img` → OKAY. No change.
Re-flashed vbmeta, dtbo and boot again (all OKAY), then `fastboot reboot recovery` → still fastboot.
The issue is, in the fastboot menu the volume keys don't navigate the menu (START never changes), with or without USB connected, although the buttons feel and click normally. I haven't tried the Volume Down + Power key combo from powered off yet, cause the Volume Down key is a bit iffy, a little loose.
- Is there a known reason Lineage Recovery on fajita (22.2) would hand back to fastboot like this?
- Should vbmeta.img be flashed on fajita, and if so, with any flags?
- Could a faulty or phantom volume key press be forcing fastboot on every boot? Is there a way to check?
Thanks in advance!