I was able to get the charging animation from ColorOS 12, by running the msm tool to OxygenOS and updating it with the OOS 12 right afterwards(do not flash the oem_cust1, it was probably kept on a secondary partition). But the UI issue remains the same, the real issue is that the new ColorOS 12 notification/quick action bar is totally different from the OOS version, I dunno how to port that over, as this is out of my knowledge level.
It didn't change the partition, oem_cust is still present in the ColorOS zip, and the partition is there, whoever said that has no idea of what they're talking about.
This is the themeinfo.xml file, that informs which apps will have the cyberpunk flag on them, some of them could be shared between OxygenOS and ColorOS, but to be more specific the one that is broken is the com.android.systemui from OOS, that APK is totally different from the one on ColorOS which features the new theme version. A simple Magisk module porting some of those apps should give us the full customization behavior back to OOS.
Well, after the update to Android 12 it seems that we'll need to do some research again.
I've repeated the same steps but extracting the oem_cust1.img from the latest Color OS build (C.17).
The result looks like this, but the text is a white mess and it's buggy amongst many apps.
View attachment 5571071
The app drawer, notification & ringtone sounds, boot animation, camera effects all are looking good and working fine.
It seems that the ColorOS notification drawer is totally different than the OxygenOS, and that is probably the main reason for this weird behavior, does anyone know if there's an easy way to port the notification drawer from ColorOS to OxygenOS?
Update worked, however I need to highlight that 184.108.40.206 seems buggy to me (Stutter and other stuff)
Ok. So I got Global 220.127.116.11 update (OTA, incremental, around 500 MB size).
I updated and it worked (with all cyberpunk elements working and nothing changed).
1) Cyberpunk8T Phone at Global OOS 18.104.22.168, and showing receiving new update under system-update:
2) Downloading Global OOS 22.214.171.124 update. Not full update, OTA, incremental, around 500 MB size:
3) Booting to Global OOS 126.96.36.199 after update and restart (it took a bit more time while booting, but worked at the end):
4) Showing updated phone to Global OOS 188.8.131.52 with cyberpunk elements intact:
So, I think flashing cyberpunk cust on both slots before, and then relocking and updating did work.
Below I will put the steps I took (please note that I tried this on Global version, no idea if EU or IN is the same).
-1) If you received phone on HOS, do full local update into next HOS in order to ensure cust is flashed to the other slot. (preferably do 2 HOS full local updates just to ensure, recommended versions are OnePlus8T_Hydrogen_184.108.40.206_15.H.19_KB05, and OnePlus8T_Hydrogen_220.127.116.11_15.H.20_KB05. (another option would be to flash cust at this stage, but I am just stating what I did personally).
0) Use MSM tool to convert to Global OOS (check thread and forums for this step)
1) Now your cyberpunk 8T phone should be on OOS, and you have all cyberpunk elements working (this is important as it points that param flag for cyberpunk is active)
adb push H19_OTA-oem_cust1-raw.img /sdcard/oc1.img
(I actually unziped and copied the file to phone root through windows and renamed it to oc1.img, then did adb shell in cmd, and ran the below commands)
dd if=/sdcard/oc1.img of=/dev/block/bootdevice/by-name/oem_cust1_a
dd if=/sdcard/oc1.img of=/dev/block/bootdevice/by-name/oem_cust1_b
2c) remove root and relock the bootloader (optional)
3) After rebooting the phone, you should have all elements, and OTA incremental updates should not affect your cyberpunk elements or cause bootloop
This what have worked for me. Please familiarize yourself on how to unbrick just in case things did not go well.
Edit: fixed OOS 18.104.22.168 video link, and info about the adb commands
Edit2: flashing cust files using "dd" commands require the phone to be rooted. Alternatively, I added another flash commands using fastboot that not require root.
I was able to get back to HOS (22.214.171.124). So this even downgraded my version, and I had all cyberpunk elements.
Then it hit me. I was trying to figure out how did the sellers flash the global OOS.... and most of xda members here state that their device came on "126.96.36.199.KB05AA ", and it had " SOME Cyberpunk things ".
So I went and did an MSM restore on my Cyberpunk8T HOS (188.8.131.52) to EU OOS 184.108.40.206 (from unbrick-tool thread above). Guess what it worked. I was able to boot to EU OOS 220.127.116.11.
I received a Oneplus 8t (Cyberpunk Edition). The phone was supposed to have HydrogenOS as it is a Chinese phone. However, the vendor installed Global OxygenOS (KB05AA). After OTA updates, the phone wouldn't reboot and would get stuck on the Cyberpunk boot animation.
I tried updating/restoring OxygenOS using the the MSM download tools here:
Pros:Working OTA updates, the original Cyberpunk theme, and Google Apps! Cons: A little bit of time and maintenance.
Overall I would highly recommend trying the HydrogenOS solution I've linked above. It works excellent for me, so I won't be pursuing a solution for OxygenOS unless things change. The guide I wrote and linked above should get anyone with a Cyberpunk phone on to HydrogenOS (with OTA updates, original theme, and Google Apps).
OK, so i finally got Oxygen OS 18.104.22.168.KB05AA (Global/USA) Running on my Oneplus 8T Cyberpunk edition (KB2000) with all the Cyberpunk goodies.. .
After all the previously mentioned attempts this is what got me through:
1.- MSM to Hydrogen OS using the link provided at OP.
2.-- Update Hydrogen OS to 22.214.171.124 using OTA update (incremental update directly on the phone).
3.- Once Hydrogen complete update to 126.96.36.199. Turn phone OFF.
4.- MSM to Oxygen OS to 188.8.131.52.
5.- Once Oxygen OS boot up, loaded 184.108.40.206.KB05AA FULL zip update (Provided on OnePlus website) to the phone's root directory.
6.- Perform a Local update through the "gear" icon under the system update section.
If you guys have any questions in regards of what i did, feel free to ask me.
Best of luck~