[OnePlus Nord 2 5G] Zombnombs:
Exact same boat too! Not sure if you guys have managed a fix yet, but let me know what you guys have tried. It seems like TheWing has found a fix. Which I'm currently trying right now. I have the 12gbram 256gb storage DN2103 EU variant phone on A12.

@TheWing Thanks for sharing your fix! Could you perhaps share the vbmeta, boot and recovery images you used to flash the fix? When you say "from the A12 OTA", what do you mean? Do you mean the incremental A11 to A12 update.zip? Could you provide a link to this or point me where i can find it?

If I understand correctly, you solved your bootloop using the mtkclient's ability to flash partitions despite having a locked bootloader; So you basically did a "normal" bootloop fix and managed to correct your phone.

I'm trying it right now but it hasn't seemed to work. Tried using the Recovery/Boot/vbmeta files from my nandroid, but also files from the google drive in the OP's google drive link. Can't seem to get the phone out of it's partitions destroyed message. A link to that OTA12 update file that you mentioned would be extremely helpful.

Question, were you able to boot into recovery prior to these fixes? The recovery.img in the OP's download link seem to work for me! But using it's format data and wipe data function doesn't seem to do anything, and I've tried it a dozen or more times.

Could you also check if these files sizes look right to you? So i know if I'm in the right ballpark.

boot.img: 33,554,432 bytes (32.0 MiB)

All the stock boot images seem to be this exact size, whether it be from my nandroid backups, or the ones provided here on XDA for stock .A12 update. I've tried a bunch but none of them are working so far. I assume they're all identical.

recovery.img: 134,217,728 bytes (128.0MiB)

This is where things get a little confusing for me. The TWRP recovery image from Denniz's TWRP thread is also this exact same size. The supposedly "stock" recovery in the google link in the OP of this thread is also this exact same size.

vbmeta_vendor.img(from download link in this thread) and vbmeta.emmc.win (from nandroid): 8,388,608 bytes (8.00MiB)

Alright this is where I'm getting really confused. There's 2 different file sizes here. I assume you're flashing the ones that are 8 megabytes large? That's the vbmeta partitions in my nandroids, and also the vbmeta included in the OP's download link.

However, there's also teh vb.img file that people use for the "./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" command, which is only 4,096 bytes (4KB) large, which I assume is far too small to be what you're flashing.

Could you check these commands for me and see if they look right to you? And if I'm placing them in the correct location in the mtkclient?

"python mtk w boot boot.img"

"python mtk w recovery recovery.img"

"python mtk w vbmeta vbmeta.img"

I renamed files from my nandroid backups from things like "vbmeta.emmc.win" to just "vbmeta.img". I then placed the renamed files into the /opt/mtkclient directory and flashed them using the above commands. The flashes seemed to work fine. Do you think renaming the files, or that .emmc.win files from TWRP backups are incompatible somehow? (like TWRP compresses them funny or something)

Any ideas, file uploads, or file download links that any of you guys have will be appreciated.