[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] oops_mr_gumby:
I have never flashed a dm-verity zip, I just flash lineage builds with addon-su. In the past I was using Magisk and was also flashing the module I made to make the same changes to /vendor/etc/mixer_paths_tasha.xml that I was making when this problem started happening, but that's it. That device-info output is actually from when OOS was installed (not sure if it was 9.0.4 or OB29 though), before installing Omni. I've just gone through the whole wipe everything/flash OOS/flash TWRP/flash lineage process again though, Lineage is still freezing in the same way, but the "fastboot oem device-info" output is identical to what I posted before. Should I be trying to flash a dm-verity zip? I gather it prevents checks for whether /system and /vendor has been modified, is that right?

Thanks for the reply, I'm glad the missing details on the fastboot screen are normal/expected. I was already on 9.0.4 firmware with the lastest codeworkx TWRP, and I followed the steps in your first link under "[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery", for the most part, slightly out of order and without the magisk uninstaller step. Basically the same thing I already did last night:

-in TWRP, wiped everything - dalvik/art cache, cache, system, vendor, data, internal storage, formatted data

-rebooted back into twrp (else no /sdcard/ to adb-push to), pushed full size official OOS 9.0.4 zip

-flashed OOS 9.0.4 zip

-used advanced wipe to wipe dalvik/art cache and cache

-reboot

-OOS boots without issue

Following the steps in the first post from this thread:

-I was already running Lineage 16 before and 9.0.4 installed successfully so I didn't bother making sure I'd ever run OOS 5.1.4

-I never setup encryption or a pin or password in the first place (not since repeatedly wiping and formatting data yesterday anyway)

-The latest official firmware was installed along with OOS 9.04 (right?)

-bootloader already unlocked

-rebooted to fastboot from stock OOS recovery

-flashed latest codeworkx TWRP - 20190311

-skipped doing a nandroid backup

-did factory reset only (instead of wiping everything and formatting data like I've been doing every other time)

-adb push today's lineage 16 build

-flashed lineage

-did not flash gapps because I don't want them

-rebooted

Just as before, it's not a long first-time boot. The boot sequence freezes almost instaneously once the Lineage logo appears on the screen, and then it reboots, then it freezes again the instant the logo appears and reboots, and over and over until I force a shutdown with the power button or boot into TWRP with the volume down button. Sometimes the first circle never appears, sometimes it freezes when it's just a tiny circle on the right edge of the arc, occassionally the circle makes it to the middle of the arc before it freezes and reboots, sometimes the circle makes it about 1/4 of the way across the arc, but it never gets past the centre of the arc before the animation freezes and rebooting.

Is there no way to get some logs of the boot sequence up until the freeze point? edit: I've tried looking in an adb shell under TWRP for some oops logs in /sys/fs/pstore but that folder is empty. I tried using the "copy logs" function in twrp but I guess that's just the boot logs for TWRP's boot? Any way to disable the animation and get console output instead?

edit: flashed official 5.1.4 full zip, successfully booted, then flashed 9.0.4 firmware zip, latest codeworkx TWRP and tried latest lineage build again, same freezing logo bootloop. This SUCKS I don't want to run Ominrom :(

edit: crDroid has the same immediate boot-logo-freeze-and-reboot-loop issue

edit: and Bliss rom

and Jaguar rom (w/ 9.0.2 firmware)

aicp doesn't even get to the rom logo, reboots immediately after oneplus logo

seems like the thing these roms all have in common is they include a /vendor image in the .zip.

Can anyone please point me to some information that can help me fix this? Why has modifying 2 characters in a text file in /vendor, a change I've made many many times before, suddenly ****ed my phone for installing just about any rom at all?? I'm really sorry for posting these huge text-walls, but I really need some help here. How can I get some logs for an incomplete boot??

edit: seems like I have to try the "unbrick guide for hard bricked..." even though it's not hard bricked - I can only guess there's a partition other than the usual recovery-accessible ones that I've ****ed somehow, and hopefully the guide will restore _everything_ on the phone to stock :( :( :(