Your information is incorrect. All Onepluses allow locking bootloader with a custom key, which means that a custom rom could run on locked bootloader. This is possible even with Magisk. My rom (Jaguar) is one example. There are others...Short answer: no - don't ever do that. Your phone will not boot.
Longer answer: Still no. But the reason why is that the bootloader being "locked" means that it will only boot code that is cryptographically signed by the manufacturer's private key. You can't change the key it uses to validate this because it's likely embedded in secure hardware or something crazy like that. Custom ROMs, by definition, are not signed using the manufacturer's private key, and neither is the custom recovery you have to use with them. Even if you root your stock ROM, you still have to unlock the bootloader because rooting modifies the kernel, which causes the digital signature to be invalid.
So, you can only have a locked bootloader on stock, un-rooted, unmodified, software .. which is the whole point of locked bootloaders in the first place. Many manufacturers won't even allow you to unlock their bootloaders anymore. At least OnePlus is still staying away from that horrible bandwagon.
Fascinating - I did not know that. Thanks for the correction. I would like very much to figure out how this works...
Got the apk installed but where do i get the img to install for 12? I can only find OOS 11It works for me, make sure you have OOS12 installed in both slots (installed twice, 2nd time using https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk).
Then follow the instructions and all good.
I used Arjan's Oxygen Updater to get the latest OTA downloaded locally:
Thanks im on Global KB2005_11_C_33. I just msm back to stock and did all the ota updates earlier tonight and unlocked the bootloader. This whole A/B flashing twice thing is really confusing.
Thank you for the reply, I understand the reason now. Would flashing EU mess with US carriers like AT&T and TMobile? I think that's our main concern here. Thanks@skanadian and @JrkSoldierX When the OP8T first came out, the reason behind it was, the Global FW was released on Google Servers and could only be downloaded via OTA Delta (Small Package) or when OnePlus decided (at their whim or some internal policy they never publicly discussed) when it was time to release a Full Update File via their website. During that time it was discovered the EU version didn't have enough noticeable differences between it and Global version to cause issues. As for why now, I can only assume the issue hasn't been overcome (and probably never will).
Have you tried AwakenOS? This one has been much more stable on my 8T. Best thing is it's on OOS11 and comes with OOS Camera.Is the current charging behaviour inherited from OOS12? After upgrading to OOS12 a month ago, the phone lost all USB-PD charging capabilities. I've tested OOS12 with several PD sniffers and chargers, the phone never tried to initiate any PD profiles. It only charges at standard [email protected], or strangely QC2/3.0 [email protected] 18W when battery is <50%. Under OOS11, 8T charges at PD [email protected] 27W when <~50%, and PD [email protected] 15W after. The oneplus community forum does not give a f__K as usual.
I thought it was my phone's usb problem. But no, after reverting back to OOS11 using MSM Tools, the PD charging is instantly back. Now I am on latest Nameless, once again PD is not working. However Nameless is still better than OOS12 since OOS12 somehow deliberately slows down the charging further (down to ~5W) when the screen is on. When my phone sits in my car with Waze + GPS + Bluetooth, the phone does not charge at all under OOS12. With Nameless, it charges ok but is still slow.
Is it possible to change the USB charging behaviour or is it built into the OOS12 drivers?
You need to flash C33 firmware before updating to the latest build.Hey there, today morning I installed 'Nameless-AOSP_kebab-12.1-20220823-2345-Official.zip' as OTA of 'Nameless-AOSP_kebab-12.1-20220723-1310-Official.zip' (working before without problems).
It ended up in a bootloop with an combination of black screen and "take care bootloader unlocked" screen,
did it endlessly.
I attached it to a PC, did a reflash of things in installation guide, incl. recovery, NOT able to boot into recovery anymore even if flashed brand new. Device bricked at the moment.
Any ideas what's broken?
Thanks in advance. Probably, take care!
fastboot flash recovery_a recovery.img fastboot flash recovery_b recovery.img
Disable wide angle correction or whatever it's called from settings