And what variant will be shown in the "about phone"? Like KB2007, KB2005, Etc, Etc....?
And what variant will be shown in the "about phone"? Like KB2007, KB2005, Etc, Etc....?
Does wifi calling still work on T-Mobile if converted to the EU firmware?
I installed KB2005 C.11 ROM after bootloader unlockedDoes wifi calling still work on T-Mobile if converted to the EU firmware?
Yes.Does wifi calling still work on T-Mobile if converted to the EU firmware?
I tried a magisk module that was posted that detects sim and I have data services now but can't place or receive phone calls.Android 12 disables SIM 2. You can reactivate it with a root module. SIM 1 should still work fine.
Can't detect sim after updating to Android 12. I couldn't find a fix anywhere. I am using Verizon with the unlocked T-Mobile. Not sure if that has anything to do with it. I had to MSM back to 11 for now.
Updating to Android 12 works fine for SIM 1 but it does disable SIM 2 on the T-Mobile model. I haven't personally tried rooting to restore the second SIM functionality.I would recommend not trying this. This is a warning to anyone who is thinking about it. If you do try it, stay on Android 11. If you update to Android 12, it will not detect your sim and you will not be able to send and receive phone calls, nor have data services. The only thing you will have is text messaging. I have been trying for a week and a half trying to get back to T-Mobile and there are only two modified MSM's that return to stock and neither work for me. Also the magisk data fix doesn't work, so don't even bother trying. You will still only have texts working. It does indeed convert your phone to EU but it will cause problems later. Just a word of warning. As a last resort, I even backed up my persist, param and modems, and used the SMT download option in MSM which wiped my IMEI thinking that maybe I had corruption in the partitions. No big deal because I restored my backup to get everything back but the problem still exists.
There is no sim 2 on the TMobile model, that's the problemUpdating to Android 12 works fine for SIM 1 but it does disable SIM 2 on the T-Mobile model. I haven't personally tried rooting to restore the second SIM functionality.
You didn't specify what SIM slot you were having issues with. If you need dual-SIM, sticking with Android 11 will keep both SIM slots enabled.
I only have one sim slot and it's not detected on Android 12 but it's showing two on the phone. It says no sim even though I have one in. Works perfect on Android 11 so I'll just stick with 11.You didn't specify what SIM slot you were having issues with. If you need dual-SIM, sticking with Android 11 will keep both SIM slots enabled.
That is the piece of information that will save other people (like me) weeks of time would have been wasted on this.I would recommend not trying this. This is a warning to anyone who is thinking about it. If you do try it, stay on Android 11. If you update to Android 12, it will not detect your sim and you will not be able to send and receive phone calls, nor have data services. The only thing you will have is text messaging. I have been trying for a week and a half trying to get back to T-Mobile and there are only two modified MSM's that return to stock and neither work for me. Also the magisk data fix doesn't work, so don't even bother trying. You will still only have texts working. It does indeed convert your phone to EU but it will cause problems later. Just a word of warning. As a last resort, I even backed up my persist, param and modems, and used the SMT download option in MSM which wiped my IMEI thinking that maybe I had corruption in the partitions. No big deal because I restored my backup to get everything back but the problem still exists.
Ok, I figured it out finally after so much frustration. I used the EU MSM and reflashed then downloaded the Oxygen Updater app and performed all Global local upgrades through the app and everything is working perfectly now. I'm on current Android 12, Global with fully working phone, calls, texts, data. I don't know why doing this instead of just updating through the built in system updater would make any difference at all but it seems to have!!That is the piece of information that will save other people (like me) weeks of time would have been wasted on this.
Such a shame that OnePlus now tortures the users to this extent just for bowing to carriers. I am returning the phone and won't consider this company till they stop such sh**y behavior.
Partial updates versus full package updates more than likely.Ok, I figured it out finally after so much frustration. I used the EU MSM and reflashed then downloaded the Oxygen Updater app and performed all Global local upgrades through the app and everything is working perfectly now. I'm on current Android 12, Global with fully working phone, calls, texts, data. I don't know why doing this instead of just updating through the built in system updater would make any difference at all but it seems to have!!
Congrats! Do you think it is worth it to stay on OOS11 to maintain VoLTE and Wifi Calling on US carriers? Nevermind if it is not related to you.Ok, I figured it out finally after so much frustration. I used the EU MSM and reflashed then downloaded the Oxygen Updater app and performed all Global local upgrades through the app and everything is working perfectly now. I'm on current Android 12, Global with fully working phone, calls, texts, data. I don't know why doing this instead of just updating through the built in system updater would make any difference at all but it seems to have!!
I have VoLTE now on 12 just no Wifi calling but I don't need Wifi calling. If that's what you want then stay on 11 but it doesn't matter to me. The other thing I forgot to mention is that to ensure you keep all services, you need to root and install the Magisk data fix module with what I did to fix my issues.Congrats! Do you think it is worth it to stay on OOS11 to maintain VoLTE and Wifi Calling on US carriers? Nevermind if it is not related to you.
Okay thanks for the information. I also tried EU MSM + full local update via oxygen updater to OOS12, and lost connection to the second sim. As you said, root and Magisk data fix module is probably needed. I will keep it simple for now and just stick to OOS11 for a while. But it is very important that you verified that dual VoLTE works in your case.I have VoLTE now on 12 just no Wifi calling but I don't need Wifi calling. If that's what you want then stay on 11 but it doesn't matter to me. The other thing I forgot to mention is that to ensure you keep all services, you need to root and install the Magisk data fix module with what I did to fix my issues.
adb reboot edl
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
fastboot oem unlock
adb reboot fastboot
fastboot reboot fastboot
fastboot flash boot boot_magisk_patched.img
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img