Develop Bugs

[SOLVED] To port IMS Manager to KLTE

I want to port/build IMS Manager for getting VoLTE feature on klte (LineageOS 14.1) but there is no guide on XDA, YouTube or even on google search... There are even VoLTE patches for Mi, Moto and Yu devices. Please help me to build it as I don't even know where to start after getting sources... Thanks in advance! ?
Update:
Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699

So you are aware IMS manager is that, a Manager, it doesn't effect your IMS functionality. Furthermore, LineageOS doesn't currently have native VoLTE functionality afaik. IMS manager is a samsung app for the samsung system, you'd better bug the Lineage Dev's for a tool for manipulating the IMS settings in LineageOS and more so bug them to implement VoLTE, however this comes at a risk as it can interfere with 911 Functionality and as such could pose libaility they wish to not deal with

Pls help him, I need VoLTE, too

If you need another similar to stock android 32 bit chip set ROM with ims manager, I could suggest you download wind7 ls 5016 firmware(snapdragon 210 with marshmallow). It might help you. Please try.

kvsjxd said:
I want to port/build IMS Manager for getting VoLTE feature on klte (LineageOS 14.1) but there is no guide on XDA, YouTube or even on google search... There are even VoLTE patches for Mi, Moto and Yu devices. Please help me to build it as I don't even know where to start after getting sources... Thanks in advance!
Click to expand...
Click to collapse
Bro you saw my above comment?

Have you made any progress on this? I've had a look at this in latest lineageos and on Galaxy s6. Though I think the basic idea is the same. The ImsManager is part of lineageos Rom. Though it needs a ims service. If that is not available even if you enable volte or WiFi calling over build.properties it will not work.
So to my (limited) knowledge, the first thing one would have to do is provide an implementation of that service. I think in Stock Galaxy s6 that is provided in imsservice.apk that comes in /system/priv-apps. I've attached the version of stock s6. Though I'm unable to use that since it's signature is not accepted and I'm neither able to decompile nor to resign /zipalign the package.
Any ideas? Or is this an all wrong way I'm following?
Br
Johannes

orgler said:
Have you made any progress on this? I've had a look at this in latest lineageos and on Galaxy s6. Though I think the basic idea is the same. The ImsManager is part of lineageos Rom. Though it needs a ims service. If that is not available even if you enable volte or WiFi calling over build.properties it will not work.
So to my (limited) knowledge, the first thing one would have to do is provide an implementation of that service. I think in Stock Galaxy s6 that is provided in imsservice.apk that comes in /system/priv-apps. I've attached the version of stock s6. Though I'm unable to use that since it's signature is not accepted and I'm neither able to decompile nor to resign /zipalign the package.
Any ideas? Or is this an all wrong way I'm following?
Br
Johannes
Click to expand...
Click to collapse
Some more ideas I've tested are described over there :
https://forum.xda-developers.com/galaxy-s6/orig-development/rom-lineageos-14-1-t3598775/post72465060

Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699

kvsjxd said:
Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699
Click to expand...
Click to collapse
Explain please.

西村大一 said:
Explain please.
Click to expand...
Click to collapse
I didn't had to port IMS Manager to lineageos or any rom. And instead I tested the above specified rom, it's for SM-G900F but I flashed it on SM-G900W8 and SM-G900T. After flashing and booting up for the first time, I got VoLTE running on both devices without even changing a setting. Keep in mind that the rom have 3 bugs, SystemUI crashes when you get a notification from WhatsApp, You cannot disable the lockscreen, If you change lockscreen from swipe to something else and lock the screen, you won't be able to unlock the device. Then you'll need to factory reset/flash the rom again or have to manually remove lock using TWRP. I am switching to a different operator next week, I am tired of the battle for VoLTE. Hope it helps.

@TheMadScientist Please close this thread.

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

[ROOT] [MAGISK] [Module] Hardware Origin Bypass for Xiaomi devices

Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316

PWn3R said:
Hi All -
Just wanted to make a thread here to link to the Magisk Module I created that bypasses the bootloop we get when we have CN hardware with the Global Rom. I think this will work for India and Russia hardware too. Enjoy.
https://forum.xda-developers.com/apps/magisk/module-xiaomi-global-rom-cn-hardware-t3899316
Click to expand...
Click to collapse
Thanks for this! Have you tested this to make sure stock camera still works without any issue?

xterminater07 said:
Thanks for this! Have you tested this to make sure stock camera still works without any issue?
Click to expand...
Click to collapse
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.

Great, all works, no problem with camera or slider settings.

PWn3R said:
Mine never stopped working before, however, this works completely differently. This inserts a script into the boot process that happens before the device starts launching system services that changes the ro.boot.hwc and ro.boot.hwcountry to be "global". The other way I was doing it was to make the product props to a value that would make it skip the checks entirely. Unfortunately, changing that value removed the slider settings, broke the slider camera, and for some, stopped the stock camera from working. I have checked an all expected settings are in the menu, safetynet passes, the slider works, the stock camera works.
Click to expand...
Click to collapse
Eggcellent!!! lol... so just flash with twrp and that's it?

Yes, flash Magisk, 18.0 and 18.1 don't work for me. Use 17.3 and then flash this and you should be golden.

i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版

bluviper said:
i dont know who created this, but this was shared on a Mi Mix3 FB group from PH.
Magisk-v18.1_mix3专版
Click to expand...
Click to collapse
does this work on chinese device with chinese rom or xiaomi eu rom?

I have got it working on chinese device with xiaomi.eu rom.

xterminater07 said:
does this work on chinese device with chinese rom or xiaomi eu rom?
Click to expand...
Click to collapse
I can confirm that works, I already flashed
Inviato dal mio MIX 3 utilizzando Tapatalk

yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.

bluviper said:
yes, its working on EU ROM coz im on Mi-Globe which is based on EU ROM.
Click to expand...
Click to collapse
Why would you use it on the EU/Mi-Globe?

Mackay53 said:
Why would you use it on the EU/Mi-Globe?
Click to expand...
Click to collapse
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.

bluviper said:
before, V18.0 wont work with mix3.
no matter how you install it. only 17.3 works
as of the moment, since the week before the Chinese New Year, there are no updates from mi-globe. until this weekend. so this is a good alternative to make v18 work with mix3.
Click to expand...
Click to collapse
What benefits do v18 make over v17.3?

Mackay53 said:
What benefits do v18 make over v17.3?
Click to expand...
Click to collapse
Other than a new magisk manager interface I don't notice any difference.

954wrecker said:
Other than a new magisk manager interface I don't notice any difference.
Click to expand...
Click to collapse
That's what I was thinking but people seem to really want to install it, I'm still on 17.1 as that's what comes with twrp.

I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.

PWn3R said:
I haven't tested 18.1 as posted above, but 17.3 is the latest working released version for global.
Click to expand...
Click to collapse
Most people on telegram are now using 18.1 , apparently support for modules will end soon for 17.

The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk

PWn3R said:
The released 18.0 and 18.1 do not work on the mix 3. I have no idea if the one linked above does, but I also don't know what they modified which is why I was advising 17.3
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
its working. some of the others guys here installed it.
they said its working. i for one, installed, and its working.
based on the screen capture i posted. you can see a logo of xda, maybe they are a part of it somehow.
moreover, there are tons of bulleted changelogs for the 18.0 & 18.1
some of them may not be noticeable for a very large audience, but this "i guess" will make it future proof for the reason of rom updates and compatibility. since Android Q is in the works.
also, noticed these changes
Code:
v18.1
- [General] Support EMUI 9.0
- [General] Support Kirin 960 devices
- [General] Support down to Android 4.2
- [General] Major code base modernization under-the-hood
other changes are for MagiskHide, maybe to better hide other apps. because there are some few apps that still can detect rooted devices even if they are HIDDEN.

[GUIDE][ROOT][MAGISK] Photochrom Filter Enabler

Disclaimer: you accept responsibility by flashing this magisk module to your device at your own risk. If you experience any issues with Magisk, please refer to https://github.com/topjohnwu/Magisk/issues
This magisk module was created by isolating the diff between the full payload.bin of OOS 10.5.8 and the delta payload.bin of OOS 10.5.9 which had entirely disabled the Photochrom camera.
- Tested on OOS 10.5.10 IN2025.
- Currently not working on OOS 10.5.11 IN2025 due to additional changes that were made, I am working on fixing this. Please do not ask me for an ETA or complain about my internet uploads speeds.
Please advise: this has not tested on Indian or European models, and I cannot guarantee compatibility.
Download link (compatible with OOS 10.5.10) for IN2025: https://www.androidfilehost.com/?fid=8889791610682885705
I identified the following changes:
/system/priv-app/OnePlusCamera.apk: removal of the photochrom filter selection, confirmed via changes in smali bytcode
/vendor/lib/camera/: various camera firmware binaries were recompiled, including changes to what I presume to be the 5MP camera with the built-in infrared lens filter (gc5035)
/vendor/lib/camera/components/: various camera component feature stubs/wrappers for the camera apk
/vendor/lib/hw/: changes to camera.qcom.so, which is compiled against the previously mentioned binaries, statically linked
/vendor/lib64/camera/: same as above
/vendor/lib64/camera/components/: same as above
/vendor/lib64/hw/: same as above
This magisk module will restore these changed files, including the stock camera application, camera firmware binaries/drivers and dependencies systemlessly. If you would like to revert the changes, simply disable or remove the magisk module via magisk manager.
Enjoy!

Anymore info?

Yeah how do we get this done?

Taking a bit longer than expected to upload, but it is coming.

xian1243 said:
Taking a bit longer than expected to upload, but it is coming.
Click to expand...
Click to collapse
wow over 4hrs upload for a simple Magisk module?

Mar-cel said:
wow over 4hrs upload for a simple Magisk module?
Click to expand...
Click to collapse
I guess we will never see it

xian1243 said:
...
Download link: (pending)
...
Click to expand...
Click to collapse
xian1243 said:
Taking a bit longer than expected to upload, but it is coming.
Click to expand...
Click to collapse
@xian1243 THREAD CLOSED! Placeholder are not accepted.
Please advise the moderators' team (best via the report function) when ready to provide a download link.

Oswald Boelcke said:
@xian1243 THREAD CLOSED! Placeholder are not accepted.
Please advise the moderators' team (best via the report function) when ready to provide a download link.
Click to expand...
Click to collapse
Thread re-opened as OP provides the download link.

Is it working ? anybody tried it yet ?

please for non root device please. (can flash over twrp without root ?)
because root is fail cts profile is false?
for oneplus 8 pro 10.5.10

The module doesn't work! IN2020

Working on IN2021 running OOS 10.5.10.IN11DA

bigstix said:
The module doesn't work! IN2020
Click to expand...
Click to collapse
Unfortunately I only have IN2025 to test with. So far it has been confirmed working for the Indian model IN2021 and the Global/US model IN2025. Are you running OxygenOS on your Chinese IN2020 model?

brmbjn said:
please for non root device please. (can flash over twrp without root ?)
because root is fail cts profile is false?
for oneplus 8 pro 10.5.10
Click to expand...
Click to collapse
Root with Magisk shouldn't break CTS profile. That being said, you could theoretically put these files directly onto the /system and /vendor partitons, however making changes to those partitions will most definitely cause you to fail CTS profile checks.
edit: I've been advised by Some_Random_Username that with HW attestation keys being enforced by Google now that will cause Magisk to fail SafetyNet/CTS.

https://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=1341422
just install this apk.

Breaks camera app on my EU model IN2023 with 10.5.10, can anyone verify this?

rhodry999 said:
Breaks camera app on my EU model IN2023 with 10.5.10, can anyone verify this?
Click to expand...
Click to collapse
Broken also on 10.5.11 on IN2025.

brmbjn said:
https://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=1341422
just install this apk.
Click to expand...
Click to collapse
This won't work, you also need the camera libraries that contain the calibration for the photochrom camera.

Dashwood Foxe said:
Broken also on 10.5.11 on IN2025.
Click to expand...
Click to collapse
This was tested on IN2025 10.5.10. It seems like Global version 10.5.11 and EU version 10.5.10 breaks the module, I'll have to look and see what changes were made. The changelog for this new update includes "adjustments" to the photochrom filter which was reenabled... but now doesn't "see through" plastics and such. That being said we may be able to reverse those changes with a similar module.

xian1243 said:
This was tested on IN2025 10.5.10. It seems like Global version 10.5.11 and EU version 10.5.10 breaks the module, I'll have to look and see what changes were made. The changelog for this new update includes "adjustments" to the photochrom filter which was reenabled... but now doesn't "see through" plastics and such. That being said we may be able to reverse those changes with a similar module.
Click to expand...
Click to collapse
Update disables the unfiltered camera and uses the ultrawide instead.

Finally , One Module-unlock 5G-Volte-VoWIFI

Hello,,
After a long term of tries and workarounds. Finally found some module by ender-zhao
Thanks for him so much.
Simply one module to enable 5G and Volte ,vowifi...
install it from magisk , restart and everything should be fine. 5G,VOLTE
Here is the module
Download Here
Good luck and thanks for ender-zhao
This module works on Pixel 5 , Pixel 4a (5G)
Thanks Again and Good luck

The problem is we are getting unknown calls
Has anyone fixed it in the module?
I managed to fix it by replacing ims files

Eiad Ajam said:
The problem is we are getting unknown calls
Has anyone fixed it in the module?
I managed to fix it by replacing ims files
Click to expand...
Click to collapse
possible its fixed , I tried it and didn't face any issue.

Eiad Ajam said:
The problem is we are getting unknown calls
Has anyone fixed it in the module?
I managed to fix it by replacing ims files
Click to expand...
Click to collapse
What exactly did you do ?

Wow this ****ed my phone I have no service now

nfqa said:
Hello,,
After a long term of tries and workarounds. Finally found some module by ender-zhao
Thanks for him so much.
Simply one module to enable 5G and Volte ,vowifi...
install it from magisk , restart and everything should be fine. 5G,VOLTE
Here is the module
Download Here
Good luck and thanks for ender-zhao
This module works on Pixel 5 , Pixel 4a (5G)
Thanks Again and Good luck
Click to expand...
Click to collapse
Seriously need help

rbouza1 said:
Wow this ****ed my phone I have no service now
Click to expand...
Click to collapse
So if anyone has problems , clear cache on carrier services all the carrier apps and reboot. I didn't have any mobile data or service. Scary stuff

Works for me. Tnx.

Eiad Ajam said:
The problem is we are getting unknown calls
Has anyone fixed it in the module?
I managed to fix it by replacing ims files
Click to expand...
Click to collapse
May i know how do replace the IMS file? Thanks.

Ok here's my guide. I think it's best we don't start another 5G/Volte thread so maybe laughterwym can reference this post in the first post of this thread.
Download EfsTools modded and extract.
Put the correct mcfg_sw.mbn in the EfsTools folder. Download the mcfg_autoselect_by_uim file and also put it in the EfsTools folder.
Flash the Volte module in Magisk (doesn't really matter wheter your mbn is in it, as long as it has the right system props and more important disables the qril stuff that) (Both this module and this module are working for me. You can also find the modded module I used here. I'n my modded module I set the 5G connection to NSA so use that one if your carrier doesn't support SA yet.
Connect your phone to your computer with usb debuggin on in your developer settings. Make sure you have both qualcomm drivers and google usb drivers and of course the latest platform tools (and add the dir to your system path).
Use the workaround we normaly use to connect our phone to qpst:
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
Open a command prompt in the extracted efstools folder
Run the following command
Code:
EfsTools.exe efsInfo
You will get errors because of the hacky workaround we have to do with Pixel phones to use them with efs software. In my case everything worked like a charm. You can check efs explorer after writing your mbn to see if it looks allright.
Run the following commands one by one:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
The -s 1 options are there so we write configurations for the second sim slot.
Important note: If you have a carrier that uses NR-NSA you'll have to edit lte_feature_restrictions.xml in EFS explorer to get everything right. I've uploaded the file here. If your mcc isn't in the following list you'll have to add it;
Code:
<plmn_list name="dss_plmns" ns="global">
228-01 505-01 505-11 505-39 505-71 505-72 204-04 204-08 204-69 204-12 262-02 204-16 204-20 232-03 232-04 232-07
</plmn_list>
Your VoLTE, VoWiFi, ims settings and 5g should be working now! Some carriers have very short carrierpolicy.xml, mine only says dds is enabled. Keep that in mind when you use apps to monitor your connection. 5G is working on my phone but I see empty rat stuff. Currently I'm writing code for changing lte_faeture_ca.xml to add all the information other Carriers have on the phone. Once you start tweaking it's hard to stop right?
Please share your findings! I'll update this post when I remember something usefull so your feedback is very helpfull!

expos said:
May i know how do replace the IMS file? Thanks.
Click to expand...
Click to collapse
Check this thread
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Update (9 Oct 2022): Upload module here. Update (7 Apr 2021): If you are looking for the manual way to add 5G support besides the magisk module way or the module does not work for you. Please refer to #54 for the detailed steps. Thanks again to...
forum.xda-developers.com

Hi! Can confirm that @Kars88 's steps are working... Luckily, I am on cerrier which was officially added in March update, but only VoLTE, no VoWiFi... With this steps I am able to use VoWiFi too
If will somebody needs, here are mbns from Nokia 8.3, they are working with our pixel too

somin.n said:
Hi! Can confirm that @Kars88 's steps are working... Luckily, I am on cerrier which was officially added in March update, but only VoLTE, no VoWiFi... With this steps I am able to use VoWiFi too
If will somebody needs, here are mbns from Nokia 8.3, they are working with our pixel too
Click to expand...
Click to collapse
Ah thanks for sharing the mbn files and nice to hear it's working for you! Seems like the Nokia mbn is different from the one I used so new stuff to explore!
I've added your mbn collection to the google drive I'm revering to to stack everything in the same place.

Still not getting any 5G connections. On Google Fi using US Cellular towers and the map shows coverage in my area. On Proton rom with the Proton kernel. I'm in Illinois USA. Am I missing something?
EDIT: Nvm just did some research and I guess 5g is only supported by T-Mobile which sucks in my area. Bummer.

The download link showed "Not found".
Could you drop a google drive download link here ?

Hi there, my pixel 5 is now on Android 12. Will the module work with Android 12 or strictly for Android 11? thx!

acheng said:
Hi there, my pixel 5 is now on Android 12. Will the module work with Android 12 or strictly for Android 11? thx!
Click to expand...
Click to collapse
Hi, based on my experience on 4a5g Android 12 (Stock and ProtonAOSP), the module will work to at least enable the VOLTE/VOWIFI switches. To really fully enable them, follow instruction
https://forum.xda-developers.com/t/finally-one-module-unlock-5g-volte-vowifi.4240547/post-84648477

creezalird said:
Hi, based on my experience on 4a5g Android 12 (Stock and ProtonAOSP), the module will work to at least enable the VOLTE/VOWIFI switches. To really fully enable them, follow instruction
https://forum.xda-developers.com/t/finally-one-module-unlock-5g-volte-vowifi.4240547/post-84648477
Click to expand...
Click to collapse
Many thx! will try out.

Just curious.. will this enable 5g C-band? N77/78 for instance?
The Pixel 4a 5g and the Pixel 5 have the hardware/modem to use N77/n78. However, only the Pixel 5 has received the necessary software update to enable it.
I'm dying to access this band, and the 500mb-1.0gig speeds it offers.
And I'm at a loss for how to enable the bands on the 4a5g.
I'm just curious, would flashing the updated radio.img do the trick? Or would your module help me?
Any help would be greatly appreciated.
As of now, I can get 5g, but it's the lower bands.. a fast extension of the existing LTE network. I can download at around 100-150mbps on average, with random runs at over 200mbps.
However, with C-band going nationwide last week, I've got friends who are pulling 1gig speeds on their iphone 13's using C-band.
Considering that I use my phone as a hotspot for my laptop, fire stick, and smart TV... The difference between 100mbps and 1000mbps is quite noticable.
Thanks for your guidance.

General [CLOSED BETA 4] ColorOS 13 | OnePlus 9 Pro

ColorOS 13 based on Android 13 has finally arrived for the OnePlus 9 Pro.
It's a Closed Beta version for the moment and therefore unstable (you could potentially encounter some bugs).
If you want a review :
Download Links (please flash at your own risk) :
ColorOS F.03 :
https://gauss-componentotacostmanua...22/08/05/eb43c65721f14cfead64de23686dd181.zip
ColorOS F.04 : https://yun.daxiaamu.com/OnePlus_Roms_2/一加9 Pro/ColorOS 13.0.0 F.04/
ColorOS F.05 :
一加9 Pro/ColorOS 13.0.0 F.05 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
ColorOS F.06 :
一加9 Pro/ColorOS 13.0.0 F.06 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
F.06 was the latest Closed BETA version.
OPEN BETA -> https://forum.xda-developers.com/t/open-beta-1-coloros-13-oneplus-9-pro.4493509/

Changelog (F.04) :
[Optimization] System stability in some scenarios.
[Fix] Icons in the notification bar are overlapped.
[Fix] Slow response to automatic adjustment of screen brightness.
[Fix] Some application icons on the desktop display blurry.
[Fix] Probabilistic screen-off or phone flashing when unlocked.
[Fix] The drop-down status bar probabilistic control center display is transparent.
[Fix] Double-click on the screen and the screen off function in guest mode are invalid.
[Fix] The "other" type of storage space in the settings is displayed abnormally.
Changelog (F.05) :
[Optimization] System stability and fluency in some scenes
[Fix] The charging prompt keeps popping up when charging probabilistically
[Fix] The app icon is not fully displayed when using the home screen style
[Fix] The multitasking icon does not match the app

Whyyyyyy C.47?! If I could keep C.62 on one slot and flash COS to the other, I would do it, but I'm not in the mood to go through the hassle of downgrading.

EtherealRemnant said:
Whyyyyyy C.47?! If I could keep C.62 on one slot and flash COS to the other, I would do it, but I'm not in the mood to go through the hassle of downgrading.
Click to expand...
Click to collapse
You can try to use something like clone phone

progerturn said:
You can try to use something like clone phone
Click to expand...
Click to collapse
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.

It is closebeta not openbeta

EtherealRemnant said:
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.
Click to expand...
Click to collapse
What Magisk module is this? I've had trouble getting my SIM to work on COS so I'm interested.

If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.

Mohsin6643 said:
What Magisk module is this? I've had trouble getting my SIM to work on COS so I'm interested.
Click to expand...
Click to collapse
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
Says TMO but it works for any single SIM variant.

djsubterrain said:
If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.
Click to expand...
Click to collapse
I highly doubt anything will happen. There's no way to prove who leaked it because it's not like OnePlus is going around tagging individual OTA files and closed beta tests are dumb anyway. I get it for devices like the 10 Pro that don't have MSM Tools but all of us with the 9 series can recover pretty easily. This is not the first closed beta test that leaked and it undoubtedly won't be the last.

djsubterrain said:
If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.
Click to expand...
Click to collapse
No one is getting sued over this. Especially not from Chinese. lmao.

brmbjn said:
It is closebeta not openbeta
Click to expand...
Click to collapse
thx, edited

EtherealRemnant said:
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.
Click to expand...
Click to collapse
Alright good luck sir

progerturn said:
Alright good luck sir
Click to expand...
Click to collapse
Ended up figuring it out.
I unlocked the bootloader and used Fastboot Enhance to flash directly from C.62 to F.03. I deleted the cow partitions to make enough room and just directly flashed the payload.bin. Worked perfectly.
Unfortunately, I was correct about the SIM issue. I did indeed have to root and flash the data fix patch to get data. Fortunately, the patch still works fine on COS13. You can even force enable 5G on T-Mobile using the Force 4G LTE app.
I have way too much stuff that I need from my Google backup that I can't restore to COS due to the lack of Google services at boot so I won't be able to daily drive it but it's looking pretty promising. Definitely noticed my phone was running on the warmer side as well though but that is to be expected.
I went ahead and flashed C.48, since that's the most recent full OTA available for NA 9s, over it using Fastboot Enhance (FBE has no qualms about upgrading and downgrading) and that also worked without an issue after I factory reset in fastbootd so if people are wanting to mess with it, they don't have to deal with the whole process of downgrading, flashing COS, then downgrading or MSM to get back.

progerturn said:
ColorOS 13 based on Android 13 has finally arrived for the OnePlus 9 Pro.
It's a Closed Beta version for the moment and therefore unstable (you could potentially encounter some bugs).
If you want a review :
Download Links (please flash at your own risk):
Closed Beta 1 : https://gauss-componentotacostmanua...22/08/05/eb43c65721f14cfead64de23686dd181.zip
I'll update this topic as soon as there is a new release.
Click to expand...
Click to collapse
Do you have link for this closed beta but to OnePlus 9 global?

Gabiru05 said:
Do you have link for this closed beta but to OnePlus 9 global?
Click to expand...
Click to collapse
一加9/ColorOS 13.0.0 F.03 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
Beware that you'll need the Magisk data retention fix on T-Mobile devices and that ColorOS has a lot of bloat. There are also issues with third party app notifications if you want them to wake the display. It ran pretty warm, battery was IDLING at 40C and the CPU was idling about 48~58C (because it doesn't really idle, it's always doing something). For comparison, my 9 running the India C.62 firmware right now is at 28C battery and idling about 30~31C on the CPU.
Also, to install it, you either need to be on C.47 or you need to use Fastboot Enhance (make sure to search the partitions for cow and delete every one of them or you'll brick and have to MSM) to flash over whatever else you're running.

ДDo you have link for OnePlus 8?

kovaljet said:
ДDo you have link for OnePlus 8?
Click to expand...
Click to collapse
This is a OP9 forum.

kovaljet said:
ДDo you have link for OnePlus 8?
Click to expand...
Click to collapse
Hi, check on the OnePlus 8 forums here:
OnePlus 8
The OnePlus 8 is a 6.55" phone with a 1080x2400p resolution display. The Qualcomm SM8250 Snapdragon 865 chipset is paired with 8/12GB of RAM and 128/256GB of storage. The main camera is 48+8+2MP and the selfie camera is 16MP. The battery has a 4300mAh capacity.
forum.xda-developers.com

Is there a way to googlefy Cos13?