Related
First of all a BIG thanks to ed-gonzo
He made this possible
This is the instruction to activate VoWiFi / WLAN Call on the Poco F1
Its tested and verfied to work with EU ROM (Oreo , Pie and Q based) and german provider o2 (Telefonica)
Before you read on i want to make clear that I am not responsible for bricked devices !
Basic requirements are root rights to do this mod
Maybe latest 2020 Qualcomm Diag QD-Loader Windows 10 Drivers signed are needed for this to work.
!!! Before doing this Mod you should backup EFS-partition !!!
- download QPST tool and install
- enable USB debugging in Developer settings
- now either go to terminal app and type:
Code:
su
setprop sys.usb.config diag,serial_cdev,rmnet,adb
or
adb from PC
Code:
adb shell
su
setprop sys.usb.config diag,serial_cdev,rmnet,adb
- connect Poco F1 with original USB cable to PC
- start PDC (from QPST tool) on PC
- Poco F1 should be recognized by PDC (if not install Qualcomm driver and check Device Manager)
- activate corresponding profile (in case of german o2 its DT_Greece)
- install VoLTE & VoWiFi Enabler Magisk module (optional) or activate setting with dialer code *#*#869434#*#*
- restart Poco F1
- Voila
FAQ:
Q: What are the requirements for VoWiFi
A: A provider resp. plan which includes VoWiFi
Q: How to know if VoWiFi is working ?
A: Put phone in airplane mode and reactivate WiFi only. If you are able to make a call then VoWiFi is working.
Q: Does this only work with MIUI ROM ?
A: No ... its reported to work also on Custom ROMs like LOS, crDroid ...
Thx for this guide! Have been waiting for this.
Does this work with custom ROM (LOS)?
in case of german o2 its DT_Greece? are you sure? german carrier and greece?
saski4711 said:
Does this work with custom ROM (LOS)?
Click to expand...
Click to collapse
in german forum there is a user who has it running.... but it seems that LOS has no icon for VoWiFi
But nlow ...
saski4711 said:
in case of german o2 its DT_Greece? are you sure? german carrier and greece?
Click to expand...
Click to collapse
yes indeed DT-Greece for german o2
I have it up and running ...
der_Kief said:
in german forum there is a user who has it running.... but it seems that LOS has no icon for VoWiFi
But nlow ...
yes indeed DT-Greece for german o2
I have it up and running ...
Click to expand...
Click to collapse
Ok thx will give it a shot as soon as I get access to a windoze PC :highfive:
Ok this definately didn't work on my Poco-f1 with latest LOS16 and 8.11.15 vendor/fw. Funny thing that VoLTE now seems to be gone (Device switches back to H+/E). Got it back by restoring efs. Has anyone else been successful with this running custom ROMs? Even without this "hack" I have been able to activate VoWIFI after 8.11.5 update but it didn't work so I guess this depends on FW version.
Two things - a little offtopic though: Any Idea if this can be tried on the MiA1? I suspect that xiaomi doesn't include support in it's firmware for this device at all and I 'm afraid to cripple both my devices (Poco and MiA1) at the end .
Has anyone had success getting HDVoice with BT headsets on the Poco-f1 with custom ROMs? Sorry for asking this here but in the LOS thread I seem to get ignored with this question / bug report.
@saski4711
to bad that its not working for you.
It defintively works with EU ROMs based on Oreo or Pie.
Double post
*deleted*
der_Kief said:
@saski4711
to bad that its not working for you.
It defintively works with EU ROMs based on Oreo or Pie.
Click to expand...
Click to collapse
Yeah bummer. Will give it another shot the next days maybe I messed up somewhere. Isn't this device supposed to get VoWIFI by default with the Pie update anyway? Maybe this will work OOTB with final pie?
not works with EU pie rom to me too. from Sri Lanka we have VOWIFI network. tried switching many profiles but not works .
saski4711 said:
Isn't this device supposed to get VoWIFI by default with the Pie update anyway?
Click to expand...
Click to collapse
Dont know ... i'm on Stable EU ROM 10.0.6.0 (based on Oreo)
I know for sure it worked out of the box after pie update on stock beta with a service provider in Greece.
Can make settings appear with *#"#vowifi#*#* but being in India don't think providers support vowifi so doesn't work.
sanjay0501 said:
I know for sure it worked out of the box after pie update on stock beta with a service provider in Greece.
Can make settings appear with *#"#vowifi#*#* but being in India don't think providers support vowifi so doesn't work.
Click to expand...
Click to collapse
How can you be sure then?
Enabling the VoWiFi option doesnt mean its working !
der_Kief said:
How can you be sure then?
Enabling the VoWiFi option doesnt mean its working !
Click to expand...
Click to collapse
2 diff statement.
Can enable with code but doesn't work in india.
It worked for a friend in Greece without doing anything immediately after pie update.
What I was suggesting that maybe and just maybe if provider supports it ,vowifi can be enabled simply by code.
It is working perfect. I did some test calls on wifi. Thumb up..... BTW I'm on German Telekom D1
SatBandit said:
It is working perfect. I did some test calls on wifi. Thumb up..... BTW I'm on German Telekom D1
Click to expand...
Click to collapse
could you please tell us which ROM you are using and which profile you activated within PDC ?
I'm using 8.11.27 global beta and I modified the DT_greece section. Set sub0 and sub1 to active.
Opened dialer and dialed *#*#vowifi#*#*
ok this works, just needed a bit more work for WoWiFi in my case
after a reboot it kept returning to my default carrier config (VoLTE working just fine anyway)
so what I did was to remove my carrier config from within PDC Tool, just that by doing that it defaulted to a non-VoLTE config
well, removed that also and this time it kept DT_Greece config on both subs
VoLTE works and VoWiFi also (carrier Orange Romania)
ps. don't restart phone if you want to test new configs
just click on activate and enter airplane mode then exit (keeps testing faster)
I've gotten as far as I can with my Mi Mix 2S, works on both AOSP and MIUI to allow the radios to be enabled, and the settings to appear in MIUI (AOSP usually shows them anyway).
With this said, I tried only enabling the WiFi option on the carrier that already had the sim activated...
I see many people here on different carriers in the EU who enabled the DT_Greece options and voila. Is this an accurate conclusion? I'm wondering if I just need an answer from a carrier other than my own to acknowledge the WiFi option exists to turn it on? Being in the US it seems as if the DT_Greece config could cause some problems, but it's not an option in my list. I don't know at this point.
Edit:
Tried all the US bands and even a few others, specifically ones that said WiFi. None worked so far, I'm going to cry! :crying::crying::crying:
I tried this on a Redmi Note 5 Pro but after selecting the device in PDC it throws an error message and doesn't show the list of carriers.
I've tried QPST 2.7.420 and 2.7.474 and a couple different pie roms, windows 7 and 10 but it always fails.
I can use EFS Explorer and dump the NV data just fine though...
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Can confirm this worked and solved my stupid "no sim" error after upgrading from 11.10.10 global to c44.
Worked perfectly on TMobile converted to global. With the issue of having no signal after 12 update.
Thank you @twinnfamous for making the module and thank you @Libra420T for sharing !! You both saved my A$$!
Is this the only way to get data working? I have a NA global variant that doesn't support dual SIM and seems to have the same issue. Honestly really liking ColorOS besides this... I usually don't root but if I don't have a choice, I guess that's what I'll do.
Thanks much. This worked perfectly after I figured out how to root C.62!
Libra420T said:
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Click to expand...
Click to collapse
thanks so much! I reflashed with msm multiple times and then kept upgrading to 12 since I thought I was doing something wrong, this fixed the SIM issue. now working great!
Hey dear my device OnePlus 9 T-Mobile
After rollback to stock T-Mobile
By unbrick msm tools
Stock T-Mobile not like first time
Sim card always disconnected and reconnected . Any solution?
This is support a Indian firmware?
badlucky said:
Hey dear my device OnePlus 9 T-Mobile
After rollback to stock T-Mobile
By unbrick msm tools
Stock T-Mobile not like first time
Sim card always disconnected and reconnected . Any solution?
Click to expand...
Click to collapse
You need to make sure that the msm tool manager is for your version that shipped with your phone, as well as the right android version number. Only then will you be able to generate a modem from your service provider.
If that doesn't work, I would try to msm to different versions of your T-Mobile vairent (LE2117). You should have rolled back to like 11.2.2 unless you have the Indian version. Idk what the first version was. my guess is that you used an msm tool that didn't include the Indian T-Mobile vairents.
Dear . I'm use msm to flash global firmware then im rollback to T-Mobile
This file sim card fix only on global firmware? Or for both (glo & India ) .
? Any new T-Mobile msm tools ?
Libra420T said:
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Click to expand...
Click to collapse
Hey dear . Update to a12 last version c63 with ota update or local update?
Phoenix47 said:
Will it work on coloros 13 open beta ?
Click to expand...
Click to collapse
Yes it does. Beware that you may lose VoLTE, 5G, and WiFi calling though.
Phoenix47 said:
I don't even use any of them.
Click to expand...
Click to collapse
What carrier do you have? I had to go back to OOS because no US carrier works right without VoLTE now. Couldn’t make or receive calls unless my phone was on 3G (T-Mobile). Went back to OOS and then switched to my 12 Pro Max. Waiting for the Pixel 7 Pro announcement to decide if I’m going to that or getting a 14 Pro Max and saying goodbye to Android (again - my OnePlus 9 is the first Android I had since 2017 when I switched). All I know is I’m over this device.
dual sim will work?
sim issues solved from Android 13?
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
What MSM specifically? If it is the TMo one, then you won't get OTAs from 1+, they come from TMo. 11.2.8.8 is the latest from TMo
Phoenix47 said:
And the tmo to global conversion msmtool is not good. You get sim issue after updating to global oos12.
Click to expand...
Click to collapse
What SIM issues?
Phoenix47 said:
I was on TMO oos 11.2.9.9 before and got oos12 ota update with 5gb size. But now I only get ota till 11.2.8.8 on tmobile rom after using tmobile msm 11.2.2.2 available on xda.
.
.
Regarding sim issue, the global oos12 convert my single sim LE2117 to dual sim LE2115 which cause NO SIM bug.
Click to expand...
Click to collapse
Interesting, I never got 12 when I was TMo, only 11.2.8.8. Maybe different areas get different stages? It is weird the TMo ROM is so far behind though...
Did you follow step 9 of the conversion guide?
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Ah, I am not sure then how you'd fix the issue as I have an unlocked bootloader and root.
And I have not flashed the file yet or the Magisk fix. I have to send the phone off for screen repair, so I haven't popped a SIM in it since converting.
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
I'm also facing this issue
It's been over a week and still no updates after 11.2.8.8
My device was previously on OOS12 C.19 before i bricked it and uses the MSM tool
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
Did you run into SIM card issues after updating to C.48 using this method?
I'm just wondering if i can use the TMO-GLO MSM tool to get 11.2.2 them use the local update to 11.2.10.10 then go to C.48 to hopefully retain Cell service/SIM Card, any help on the matter would be appreciated!
Phoenix47 said:
It is weird that global rom shows dual sim on oos12. I mean there is single sim global model also.
.
And that magisk fix don't work on custom roms.
Click to expand...
Click to collapse
The T-Mobile model is actually dual SIM but with a single SIM tray from my understanding, hence the software bug.
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Flashing modem is only required on the 9 Pro because it has an mmWave modem.
Phoenix47 said:
So you are saying that adding dual sim tray will fix the NO SIM CARDS issue ?
Click to expand...
Click to collapse
No because it doesn't work right either.
EDIT: Looks like I misspoke anyway because it's only the LE2127.
ENABLE DUAL SIM ON TMO 9 PRO ONLY!!!
Frist off I'm not Responsible for anything that happens to your phone!!! THIS HAS BEEN TESTED AND WORKING 100% ON TMO 9PRO LE2127!!ALSO MODEM RETENTION. (THIS IT NOT FOR THE UNLOCKED 9PRO LE2125) DO THIS AT YOU OWN RISK!! THIS METHOD IS...
forum.xda-developers.com
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Does anyone have the TMO 11.2.8.8 or anything around there? I've heard of 11.2.9.9. I was on EU 11.2.10.10. it was mostly ok but I was having a few communication issues*. I want to compare to a stock TMO later-11 version. I'm currently on 11.2.3.3le5acb
I tried searching the forum but it doesn't allow searching for "11.2.8.8" type strings. Or short strings.
*Wifi stopped connecting to some of my APs. Until I toggled Mac randomization, then it was fine. It's no problem in my 7TP5G.
5G would drop off to LTE, no problem... But then, LTE would drop off into no data. SMS would sometimes get stuck until reboot. Visual voicemail worked when it wanted to. None of these were consistently happening but all more than once.
Overall it wasn't too bad really but I want to try a late-11 and see how it goes.
Thanks
EtherealRemnant said:
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Click to expand...
Click to collapse
i can agree with him. i was one of the first people to try this method on the thread he created. works wonderfully. hence why his thread was stickied to the top of xda oneplus 9 page.
I did look through bunch of threads but cant seem to find an answer . . Is there a way to enable dual sim on the LE2115 and if someone has tried successfully (with or without any known issues) ?
If someone can point me to the right steps to follow ?
TIA
centifanto said:
2.10.10. I quickly downloaded that, and lo and behold the upda
Click to expand...
Click to collapse
bguzz said:
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Click to expand...
Click to collapse
how you did the local update? did you have to unlock your bootloader?
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
why when i try to install 11.2.10.10 my phone reset and keep saying is LE2117, it won't let me install LE2115_11.F.16. Pls help
After all procedure I'm on latest global A13 with December security patch but I have very strange issue, after airplane mode or restart my sim stop working and I have to eject and re-insert the sim for network service any solution
[SOLVED] - Solution found here.
This worked for me on OxygenOS 13 and seems to be permanent, persisting after reboot and SIM swap.
Finally!!! GUIDE To enable VoLTE and VoWifi on OOS 12.1 without root
Hello everyone, finally there is a way to enable VoLte without root You need 2 apps for the process .. Before starting if you have 2 sims make sure you disable the second sim and proceed.. After you finish with the first sim then enable the...
forum.xda-developers.com
Hi PPLs,
Has anyone managed to force VoLTE Calling to be enabled on OOS12? I am using the OnePlus 8T and my wife uses the OnePlus 9. I have had to rollback both phone the OOS11 after testing OOS12 and realising the OnePlus Log Kit app no longer works, therefore no way to enable VoLTE calling.
For now we are holding on to OOS11 (with the Log Kit fix) until we find a fix in OOS12, otherwise we both might be forced to look and another brand of phone, which I really don't want to do.
Just as a side note, I was using a Realme XT which I bought in 2020 which had VoLTE enabled by default as soon as it recognised the SIM, so the network is capable, but I get no support from Vodafone AU as the OnePlus phones are imported as they are not generally sold in Australia. It seems the same story with all Australian carriers.
Also, my main reason for not rooting the phones is since we use them as daily drivers and need to use secure banking apps.
I know a few people have asked similar questions before, however I'm hoping there might be some progress on this soon.
Thank you!
Currently running: OnePlus 8T (KB2000) & 9 on OOS11 - Vodafone Australia
joe460 said:
Hi PPLs,
Has anyone managed to force VoLTE Calling to be enabled on OOS12? I am using the OnePlus 8T and my wife uses the OnePlus 9. I have had to rollback both phone the OOS11 after testing OOS12 and realising the OnePlus Log Kit app no longer works, therefore no way to enable VoLTE calling.
For now we are holding on to OOS11 (with the Log Kit fix) until we find a fix in OOS12, otherwise we both might be forced to look and another brand of phone, which I really don't want to do.
Just as a side note, I was using a Realme XT which I bought in 2020 which had VoLTE enabled by default as soon as it recognised the SIM, so the network is capable, but I get no support from Vodafone AU as the OnePlus phones are imported as they are not generally sold in Australia. It seems the same story with all Australian carriers.
Also, my main reason for not rooting the phones is since we use them as daily drivers and need to use secure banking apps.
I know a few people have asked similar questions before, however I'm hoping there might be some progress on this soon.
Thank you!
Currently running: OnePlus 8T (KB2000) & 9 on OOS11 - Vodafone Australia
Click to expand...
Click to collapse
Hi. No way. only Root
joe460 said:
Hi PPLs,
Has anyone managed to force VoLTE Calling to be enabled on OOS12? I am using the OnePlus 8T and my wife uses the OnePlus 9. I have had to rollback both phone the OOS11 after testing OOS12 and realising the OnePlus Log Kit app no longer works, therefore no way to enable VoLTE calling.
For now we are holding on to OOS11 (with the Log Kit fix) until we find a fix in OOS12, otherwise we both might be forced to look and another brand of phone, which I really don't want to do.
Just as a side note, I was using a Realme XT which I bought in 2020 which had VoLTE enabled by default as soon as it recognised the SIM, so the network is capable, but I get no support from Vodafone AU as the OnePlus phones are imported as they are not generally sold in Australia. It seems the same story with all Australian carriers.
Also, my main reason for not rooting the phones is since we use them as daily drivers and need to use secure banking apps.
I know a few people have asked similar questions before, however I'm hoping there might be some progress on this soon.
Thank you!
Currently running: OnePlus 8T (KB2000) & 9 on OOS11 - Vodafone Australia
Click to expand...
Click to collapse
Actually there is a way, but not straightforward and if you mess up, you can brick your phone.
First of all you need to unlock engineering menu in OOS12 and in MBN section try to enable VoLTE. If after this volte still doesn't work, enable diagnostic ports via engineering menu, and only after via QPST and PDC activate carrier profiles for your region (Vodafone Australia).
P.S: Making it via root is easier, as Volte is enabled via Magisk module, and diagnostic ports for PDC & QPST are enabled via basically two commands in adb.
Why not try LineageOS 19.1(Android 12)?
Volte works fine out of box.
You just need gapps, magisk and some module to pass safteynet check, then it's all good.
Rootk1t said:
Actually there is a way, but not straightforward and if you mess up, you can brick your phone.
First of all you need to unlock engineering menu in OOS12 and in MBN section try to enable VoLTE. If after this volte still doesn't work, enable diagnostic ports via engineering menu, and only after via QPST and PDC activate carrier profiles for your region (Vodafone Australia).
P.S: Making it via root is easier, as Volte is enabled via Magisk module, and diagnostic ports for PDC & QPST are enabled via basically two commands in adb.
Click to expand...
Click to collapse
Do you have any guide for this?
Secrecy not worki anymore
Rootk1t said:
Actually there is a way, but not straightforward and if you mess up, you can brick your phone.
First of all you need to unlock engineering menu in OOS12 and in MBN section try to enable VoLTE. If after this volte still doesn't work, enable diagnostic ports via engineering menu, and only after via QPST and PDC activate carrier profiles for your region (Vodafone Australia).
P.S: Making it via root is easier, as Volte is enabled via Magisk module, and diagnostic ports for PDC & QPST are enabled via basically two commands in adb.
Click to expand...
Click to collapse
Thank you for the tip! I'm pretty comfortable with digging around like that.
I'll definitely give that one a go in the near future. It's my daily driver at the moment so I need to pick a time or use an old backup phone for a while.
Much appreciated!
IAAxl said:
Why not try LineageOS 19.1(Android 12)?
Volte works fine out of box.
You just need gapps, magisk and some module to pass safteynet check, then it's all good.
Click to expand...
Click to collapse
Thanks! LineageOS is usually my goto, but in this case it's my daily and I need all the secure banking and similar apps to work.
Finally!!! GUIDE To enable VoLTE and VoWifi on OOS 12.1 without root
Hello everyone, finally there is a way to enable VoLte without root You need 2 apps for the process .. Before starting if you have 2 sims make sure you disable the second sim and proceed.. After you finish with the first sim then enable the...
forum.xda-developers.com
ghost.ign said:
Finally!!! GUIDE To enable VoLTE and VoWifi on OOS 12.1 without root
Hello everyone, finally there is a way to enable VoLte without root You need 2 apps for the process .. Before starting if you have 2 sims make sure you disable the second sim and proceed.. After you finish with the first sim then enable the...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you!
Will give it a go on my wife's OP9 which I've kept on OOS11 because on this.
FYI I recently bought a OP10 Pro EU version and everything works perfectly including VoLTE & VoWIFI.
Looks like maybe the Global versions are having VoLTE issues in Australia on some carriers.
Only just bit the bullet 2 weeks ago with the OP8T and installed LineageOS 20. Works great out of the box.
I might consider re-flashing the stock OOS13 ROM on the 8T just to try this fix too.
ghost.ign said:
Finally!!! GUIDE To enable VoLTE and VoWifi on OOS 12.1 without root
Hello everyone, finally there is a way to enable VoLte without root You need 2 apps for the process .. Before starting if you have 2 sims make sure you disable the second sim and proceed.. After you finish with the first sim then enable the...
forum.xda-developers.com
Click to expand...
Click to collapse
UPDATE: GREAT NEWS! GOT VoLTE WORKING ON 4G & 5G - SOLVED
Thank you so much @ghost.ign !!
I finally got around to unbricking my almost forgotten OP8T KB2005 International Version using MSMDownloaderTool and tried the tweak using the link you provided. It worked!
Best part was, it worked on the current OOS13 and persists after reboot, as well as removing & reinserting the SIM. Very happy!
It's now time to update my wife's OP9 and do the same. Fingers crossed.
Many, many thanks!!!
FYI - For anyone else reading. I found the details to unbrick my OP8T here:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
TIP: When installing the Qualcomm drivers on Windows, boot using the Windows start-up option no.7 to allow unsigned drivers. (Knowing that could've saved me a couple of hours.)
joe460 said:
Thank you for the tip! I'm pretty comfortable with digging around like that.
I'll definitely give that one a go in the near future. It's my daily driver at the moment so I need to pick a time or use an old backup phone for a while.
Much appreciated!
Click to expand...
Click to collapse
Hey any workaround to access pdc to change mbn profile on oos12 non root?
I have tried the shizuku and pixelims, but my ims status not registered.
redzyy said:
Hey any workaround to access pdc to change mbn profile on oos12 non root?
I have tried the shizuku and pixelims, but my ims status not registered.
Click to expand...
Click to collapse
i think i saw some post related to how to access PDC and that kinda stuff on OOS 12 or 13, i will post it here let me check if it is still there.
redzyy said:
Hey any workaround to access pdc to change mbn profile on oos12 non root?
I have tried the shizuku and pixelims, but my ims status not registered.
Click to expand...
Click to collapse
[GUIDE][A11][A12][A13] VoLTE and VoWIFI on custom/stock ROMs with any Carrier
Activate VoLTE & VoWIFI on custom/stock ROMs with any Carrier Yes, yes, I know that this is not the first thread with activation VoLTE and VoWIFI. But my thread will be more convenient and easier to understand. ATTENTION ! ! ! These methods...
forum.xda-developers.com
ghost.ign said:
[GUIDE][A11][A12][A13] VoLTE and VoWIFI on custom/stock ROMs with any Carrier
Activate VoLTE & VoWIFI on custom/stock ROMs with any Carrier Yes, yes, I know that this is not the first thread with activation VoLTE and VoWIFI. But my thread will be more convenient and easier to understand. ATTENTION ! ! ! These methods...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the response, i checked that thread already, for oos12, they need rooted phone.
I can confirm that Oneplus 8T (KB2003) on OOS13, using Shizuku and Pixel IMS can activate VOLTE. I am using KB2003_11_F.63 build.
warlord2045 said:
I can confirm that Oneplus 8T (KB2003) on OOS13, using Shizuku and Pixel IMS can activate VOLTE. I am using KB2003_11_F.63 build.
Click to expand...
Click to collapse
I'm unable to confirm, maybe someone else can. I can however suggest that there's is likely no harm trying. I believe it should work across all carrier unlocked models.
Give it a go and report back if you can share.
FYI - since upgrading from OOS11 to OOS13 my model number has changing from KB2000 to KB2005 using the standard OTA upgrade process.
Rootk1t said:
Actually there is a way, but not straightforward and if you mess up, you can brick your phone.
First of all you need to unlock engineering menu in OOS12 and in MBN section try to enable VoLTE. If after this volte still doesn't work, enable diagnostic ports via engineering menu, and only after via QPST and PDC activate carrier profiles for your region (Vodafone Australia).
P.S: Making it via root is easier, as Volte is enabled via Magisk module, and diagnostic ports for PDC & QPST are enabled via basically two commands in adb.
Click to expand...
Click to collapse
Recent updates have made this method a more dangerous option. I can't go back
If you know how to put it back together, I'd love to know.