As stated here cyberpunk customization data is on another partition on ColorOS 12.No solution so far, to get the oem_cust you need to get the ColorOS payload, the OOS one won't have it.
@g4seb
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.As stated here cyberpunk customization data is on another partition on ColorOS 12.
Is that shipped pack or add on like one, if so could you backup it and sendWell, 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?
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)
su
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
fastboot flash oem_cust1_a H19_OTA-oem_cust1-sparse.img
fastboot flash oem_cust1_b H19_OTA-oem_cust1-sparse.img
Still stuck at bootloop...
I have done the following
MSM to HOS then MSM to OOS (GLOBAL) - local update to newest update full zip (GLOBAL)= bootloop
MSM to HOS then MSM to OOS (EU) - local update to newest update full zip (EU) = bootloop
Cyberpunk goodies only work on HOS so far...
I'm kind of out of ideas, any suggestion?
Thanks!
Was just going to post this - the other command is if you are rooted.So to flash using dd commands, you need to be rooted (sorry I did not notice that at first). See https://forum.xda-developers.com/t/...eplus-8t-devices.4198459/page-5#post-84055453
However, I think flashing the parse images through fastboot might work without being rooted. if someone want to test that here are the steps:
i) download this file: https://1drv.ms/u/s!AsJy8Rcn_wjLhLwtuwnEWCG4E1bNMQ?e=iRf5jm
ii) flash through fastboot using these commands
Bash:fastboot flash oem_cust1_a H19_OTA-oem_cust1-sparse.img fastboot flash oem_cust1_b H19_OTA-oem_cust1-sparse.img
I will update my original post to state that flashing through dd command need root, and add this above info as unconfirmed (until someone can test?)