[T-Mobile REVVL V+ 5G] mitchness:
For those of you that got stuck in a perpetual boot loop, I may just have a solution.

I noticed I was getting a second error. It wasn't saying "orange state," but "dm-verity error," followed by a different explanation basically saying you've toasted it

The first part that almost caused several new holes in my wall was trying to get it into any fastboot mode, so I let it boot loop the battery dead (this takes almost 2.5 days if it's fully charged, btw).

So noticing the new "oh crap" error, I used the extracted IMG files from the zip and went on a flashing spree. (I held power and volume down before plugging it in and it went into the fastboot mode with just the text at the bottom of the screen, which worked).

I went ahead and did:

Fastboot flash boot /your_path/to_your/boot.img --disable-verity --disable-verification

This got rid of the dm-verity error and went back to boot loop but reverted back to the "orange state" message and lasted longer until it rebooted and entering fastboot worked fine.

Now there's steam coming out of my ears...so I ran almost every command for flashing with filenames matching the command but added the two disable commands for each one.

Fastboot flash vbmeta_a /pathto/vbmeta_a.img --disable-verity --disable-verification

I have no idea which of all the 17+ files I flashed individually with the added disable verity options actually worked, but I had a factory non-rooted and working revvl v+ 5g like nothing ever happened. (The orange state message was the only persistent thing)

So I did

Fastboot flash boot /samemagisk/patched.img --disable-verity --disable-verification

Now the phone is rooted and working, however without ANY network abilities..

No Bluetooth. No wifi. No mobile networks. No NFC. Nothing. All entirely u phased by any changes in engineer menu or adb pulling and editing then pushing files back, even though the edited files persist after reboots.

This is because the patched magisk file does something with the firmware version or something along those lines that mismatches the magisk patched file with the rest of the system, completely severing all ties to all radio (modem) functionality. It knows the hardware exists, but forgot how to talk to it.

If you flash back to the supplied (not patched) boot.img, everything works as intended and it doesn't matter if you add the two disable commands when doing so.(but you lose root regardless).

I wanted to see if flashing the modem image with the verity disabled would fix it since it was pretty much the only file I didn't patch considering it doesn't have the typical obvious name like "system_a.img" that has a matching flash command associated:

System_a with system_a.img

Vbmeta_a with vbmeta_a.img

But ..

Wtf are all these other IMG files that seem to not have any matching flash commands? I can take a shot in the dark at a few and confident I'd still be in the ballpark but WHICH IMG IS THE MODEM IMG????

I want to flash it with --disable-verity --disable-verification and see if that tells whatever part of the system it's supposed to just to ignore whatever got mismatched along the way and maybe that would let it work again, like how the magisk patched image just magically started working doing the same thing.