[OnePlus 10 Pro] beatbreakee:
imho i doubt it. in every other fw prior to android 12, and on every oneplus phone, having an unlocked bootloader always triggered the same warning screen. its just like the Yellow "!" with the bootloader unlocked warning on samsung, the "press power to continue" warning on google pixel, , or similar warning screens on most every other model device. I just believe Google made an oversight with Android 12 and either forgot to put in the trigger that activated these screens, or in the case of OnePlus, maybe with all the different versions they have of EVERY phone, they didnt wanna bother mapping 40+ different devices each their own separate trigger.

I mean think about it... theres 4 different 10T, 4 different 10 pro, 4 different 10 R, and thats not including the special china version of each respectively with the Ace, Ace Pro, 10 Pro Extreme.... If you follow our threads at all you will find out that there are certain STILL UNIDENTIFIED differences in the model specific fw on each of the 4 variants of all the prior mentioned devices, that are JUST DIFFERENT ENOUGH that using one or more of the other variants EXACT SAME fw version, is causing devices to bootloop , or in many cases completely render the phones into a state that does not power on at all ! I can honestly say that NEVER before in my experience with Android, (going on 12 years) have i EVER seen 2 different models of the SAME PHONE, have such a catastrophic failure as to render the device "full brick" simply by flashing the other models fw. I cant speak for every android phone, but lets look at Samsung... One of THE MOST heavily restricted devices of modern phone era, (Since Galaxy S7). This particular brand usually REQUIRED a "frankenstein" build rom, with bootloaders, system images, modems, and userdata partitions of up to 5 DIFFERENT pieces of fw from other countries, devices, and sometimes homemade modifications, ALL be stitched together like a jigsaw puzzle that had the wrong pieces but you still taped them together... then zipped up and signed with some unofficial package manager into a flash file labeled, "Samsung Galaxy S_ COMBO fw"... THAT is what we had to either build ourselves or wait months for someone brave enough to do it for us, if we wanted Root access , and even then it was usually GLITCHED root, with many self inflicted issues after flashing... but we were able to flash these crazy malformed packages to any variant of each respective model, without fear of an unrecoverable brick. That is just insane when you think about it, on the most restrictive mfg besides apple, that we could flash these ill advised, sometimes dangerous combo fw and the phone still booted.... But flashing a ne2213 fw to a ne2215 phone WITH THE EXACT SAME VERSION FW, and each phone having the exact same hardware... not one resistor different! Might make your phone go into infinite Bootloop, or worse the No power, no buttons work, no charge Uber Brick state!?!

Tell me that aint the most ridiculous thing ever. Now pair that with the fact that EVERY oppo/oneplus phone each has 4 different variants, and several models are competing with each other being released within the same generation... ALL having to individually have that "Orange state" trigger added to all of their android 12 fw packages.... Oppo, Realme, Vivo, OnePlus and iQOO all owned by BBK Corp... That means OPPO Reno 8, OPPO Reno 8 Pro, OnePlus Nord 2T, POCO F4 GT, Realme GT Neo 3T, Oneplus 10 Pro, Oneplus 10T, Oneplus 10R, Xiaomi, Oneplus Ace, and Oneplus Ace Pro (plus a few i missed) ALL were released THIS YEAR from an Oppo partnered company! Im surprised that the "Orange State" screen is the only official thing that was missing in all the Android 12 builds... with the train wreck of all those devices PLUS all the previous models still supported each needing their own flavor of A12. YIKES!