How To Guide (Updated 5/21/23) How to enable N77 C-Band with 5G UW icon on OnePlus 9/9 Pro 5G (LE2115/LE2125) | Oxygen OS 11-13.1 with Custom ROM support | Verizon

Search This thread

rmendez011

Senior Member
@caseyr7 is right! I got a new SIM card from Verizon and I do see a 5G UW icon when in N77 areas, it seems that OnePlus is going to enable N77 officially in one of the next few updates! Excuse the hard to read dark red text, I am running a Substratum theme.
Screenshot_2023-02-21-14-30-25-12_79d0ff8f9752a3fc32487e6d62330a6a.jpg
Screenshot_2023-02-21-14-31-14-11_a2a5fdc6850144137057ba851b3c6cca.jpg
 
  • Like
Reactions: EtherealRemnant

lbyinchina

Member
Oct 29, 2011
23
2

rmendez011

Senior Member
What SIM Card were you using? 4G LTE SIM Card? Are you saying we should be able to pickup N77 simply by upgrading to the 5G SIM card?
I was using a 5G SIM card that I got before N77 launched, so I could connect to N77 by doing my hack, but I could only get the 5G UW icon on mmWave, with the new 5G SIM card, I now get a 5G UW icon when connected to N77, getting a new SIM card will not allow you to connect to N77, you have to do the hack.
 

lbyinchina

Member
Oct 29, 2011
23
2
Sounds good! You do not need a new Verizon SIM card to connect to N77, you need a new SIM card to get a 5G UW icon, I haven't gotten F.21 yet, Oxygen Updater notified me about the update.
How come your Network Signal Guru shows dual connectivity with NR on the right? I am testing mine on a OnePlus 10 Pro but it only shows LTE B66, althought the 5GUW icon is active and speedtest gives 300mbps down. I don't see n77 whatsoever.
 

lbyinchina

Member
Oct 29, 2011
23
2
Did you apply the hack or does it work by default on F.21?
Please see my other thread in OP10Pro discussion:

@rmendez011 Do you know the answer to this? Is that real N77 or B66?
 

rmendez011

Senior Member
How come your Network Signal Guru shows dual connectivity with NR on the right? I am testing mine on a OnePlus 10 Pro but it only shows LTE B66, althought the 5GUW icon is active and speedtest gives 300mbps down. I don't see n77 whatsoever.
Network Signal Guru pulls data from the Modem, and by doing so requires root, prior to the release of Oxygen OS 13 on the 9 Series, only Network Signal Guru could see you being connected to N77, post Oxygen OS 13 launch for the 9 Series, NSG, CellMapper, and other similar apps can see which 5G band you're connected to, this is because before OnePlus hadn't enabled broadcasting for 5G, now they do, OnePlus probably hasn't enabled broadcasting for 5G on the 10 Pro, or LTE Discovery can't see 5G data on OnePlus phones, if you root and use NSG it will show which 5G band you're connected to, alternatively, try CellMapper first.
Please see my other thread in OP10Pro discussion:

@rmendez011 Do you know the answer to this? Is that real N77 or B66?
Don't worry, that is real N77, the 5G UW icon is only whitelisted at the system_ui.apk for N77, N78 (I assume, hasn't launched yet), N260, and N261 only (only 9 Pro, and Verizon 8 5G UW), on my OnePlus 9 Pro, LTE discovery doesn't show N77 either, CellMapper on the other hand does, try it on your 10 Pro, it does not require root.

Screenshot_2023-04-01-19-46-59-05_adef6f788faab99f13b41f3f09b0569c.jpg
Screenshot_2023-04-01-19-47-03-91_ffbad1d3365dc318e70a4282340f21a4.jpg
 

lbyinchina

Member
Oct 29, 2011
23
2
Network Signal Guru pulls data from the Modem, and by doing so requires root, prior to the release of Oxygen OS 13 on the 9 Series, only Network Signal Guru could see you being connected to N77, post Oxygen OS 13 launch for the 9 Series, NSG, CellMapper, and other similar apps can see which 5G band you're connected to, this is because before OnePlus hadn't enabled broadcasting for 5G, now they do, OnePlus probably hasn't enabled broadcasting for 5G on the 10 Pro, or LTE Discovery can't see 5G data on OnePlus phones, if you root and use NSG it will show which 5G band you're connected to, alternatively, try CellMapper first.

Don't worry, that is real N77, the 5G UW icon is only whitelisted at the system_ui.apk for N77, N78 (I assume, hasn't launched yet), N260, and N261 only (only 9 Pro, and Verizon 8 5G UW), on my OnePlus 9 Pro, LTE discovery doesn't show N77 either, CellMapper on the other hand does, try it on your 10 Pro, it does not require root.

View attachment 5878401View attachment 5878403
Thank you, indeed, the CellMapper comfirms N77! Without Root.
 
You want to be the first to find out?? 😆
I'd love to, but I don't use OOS, and QPST doesn't work on custom ROMs (atleast crDroid). I MSM'd then updated to OOS 13, but could not get the device to show in QPST. It showed in device manager, and I updated the drivers for them. Do you have another guide I could try? I'm using a Windows KVM with my entire USB controller passed through, which worked perfectly for MSM.
 

TheGhost1951

Senior Member
Feb 11, 2009
2,041
533
Garfield
OnePlus 9 Pro
I'd love to, but I don't use OOS, and QPST doesn't work on custom ROMs (atleast crDroid). I MSM'd then updated to OOS 13, but could not get the device to show in QPST. It showed in device manager, and I updated the drivers for them. Do you have another guide I could try? I'm using a Windows KVM with my entire USB controller passed through, which worked perfectly for MSM.
MSM is the best and safest to use.
 

rmendez011

Senior Member
I'd love to, but I don't use OOS, and QPST doesn't work on custom ROMs (atleast crDroid). I MSM'd then updated to OOS 13, but could not get the device to show in QPST. It showed in device manager, and I updated the drivers for them. Do you have another guide I could try? I'm using a Windows KVM with my entire USB controller passed through, which worked perfectly for MSM.
Yea no, I never could get QPST to work on Custom ROMs, I'm going to update to F.21 in a bit, I had to MSM Tool my phone because for some weird reason my Microsoft Authenticator was not working, no website was accepting the 2-factor code, funnily enough, trying to add 2-factor to an account would also not work, it would say "wrong code" even though I scanned the QR Code.

This is the reason I was locked out of my Twitter account for 5 weeks thinking it was a Twitter is, once I realized my Amazon, Discord, Mega.nz, etc accounts would not let me login with said codes, I realized it could be game over haha.

I'm tempted to try a custom ROM again but idk, I don't think it's worth it, screen off gestures only work with the screen off, in the ambient screen it just swipes.
 
  • Like
Reactions: TheGhost1951
Yea no, I never could get QPST to work on Custom ROMs, I'm going to update to F.21 in a bit, I had to MSM Tool my phone because for some weird reason my Microsoft Authenticator was not working, no website was accepting the 2-factor code, funnily enough, trying to add 2-factor to an account would also not work, it would say "wrong code" even though I scanned the QR Code.

This is the reason I was locked out of my Twitter account for 5 weeks thinking it was a Twitter is, once I realized my Amazon, Discord, Mega.nz, etc accounts would not let me login with said codes, I realized it could be game over haha.

I'm tempted to try a custom ROM again but idk, I don't think it's worth it, screen off gestures only work with the screen off, in the ambient screen it just swipes.
I really don't like OOS but I also cannot find a custom ROM I like. I love this phone though. I came from an older iPhone and I've developed jailbreaks and stuff so I like Android due to being able to mod it and stuff. 5G UWB would be great since it's all over near me on the map.

Honestly thinking of switching to T-Mobile. I wouldn't have issues with disabled bands, right? T-Mobile has better coverage in New York.

And yes, I'm on F.21 with Lineage, but I don't seem to be able to connect to UWB, although my mom's iPhone can connect fine. We have the same Verizon plan. What's weird to me is that we're supposed to have mmWave where I am, but I can't connect to that either? Is n260 and n261 disabled aswell?

I might MSM then go back to OOS F.21 to test if UWB works there. I doubt it though since I should be using F.21 now.
 

rmendez011

Senior Member
I really don't like OOS but I also cannot find a custom ROM I like. I love this phone though. I came from an older iPhone and I've developed jailbreaks and stuff so I like Android due to being able to mod it and stuff. 5G UWB would be great since it's all over near me on the map.
Have you tried Nameless ROM? Though I don't think it has N77 or N260/N261 enabled, I only tested it for a limited time. Apparently StagOS has N77 enabled, but again, I could not test it as I had major issues with that ROM.
Honestly thinking of switching to T-Mobile. I wouldn't have issues with disabled bands, right? T-Mobile has better coverage in New York.
Yes, the 9 Pro has all T-Mobile bands, however, I don't think you will see a 5G UC icon, who knows, maybe you will, maybe you won't, https://www.mintmobile.com/free-trial/ try this 7-day free trial.
And yes, I'm on F.21 with Lineage, but I don't seem to be able to connect to UWB, although my mom's iPhone can connect fine. We have the same Verizon plan. What's weird to me is that we're supposed to have mmWave where I am, but I can't connect to that either? Is n260 and n261 disabled aswell?

I might MSM then go back to OOS F.21 to test if UWB works there. I doubt it though since I should be using F.21 now.
That I don't know, when I tested Nameless I was not in a 5G UW area, so I could not test it, F.21 will have N260 and N261 enabled, F.20 had it enabled as seen here:
N77 I don't know, F.20 had it disabled, but once enabled it showed a 5G UW icon in the status bar, I will let you know if F.21 has it officially enabled.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    How to enable N77/N78 5G on the LE2115/LE2125 OnePlus 9/9 Pro running Oxygen OS 11-13.1​

    Before we start, keep in mind the following:
    Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this modification before applying it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

    Keep in mind:
    This can dramatically affect your battery life whenever on 5G data, as this an unofficial mod, the phone will be constantly connected to 5G UW (without the 5G UW logo of course) in N77 areas, I have no idea how to solve this (other than turning off 5G until you want SPEEEEEED). Smart 5G does not seem to have an effect on this.

    Update 5/8/23:
    Thanks to @itsnebulalol, they have been able to enable N77 on custom ROMs on OnePlus 9 and 9 Pro, for anyone with a OnePlus 9/9 Pro running a custom ROM, you can follow their guide here, on Github.

    Update 2/21/23:
    On Oxygen OS 13 F.20/F.21 (maybe older) if you get a new SIM card from Verizon (cannot confirm about other carriers) post N77 launch, you will get a 5G UW icon in your status bar, thanks to @caseyr7 for pointing this out. (Sorry about the slow SpeedTest).
    screenshot_2023-02-21-14-30-25-12_79d0ff8f9752a3fc32487e6d62330a6a-jpg.5843571

    You will need these two items:

    QPST, download it from here.
    ADB (Obviously).


    Since OnePlus officially enabled N78 in Oxygen OS 12, this is how we will be able to enable and connect to N77 on Oxygen OS 13. I myself cannot personally test if this works on Oxygen OS 12, I can only assume it does.

    Great news! I have successfully enabled N77 on OnePlus 9 & 9 Pro running Oxygen OS 13 on the Verizon network! This would not have been possible without the help of @Rootk1t for showing me how to get Rndis,diag switch working, @sakun-ice, @jimmy123322, and @21prods for providing the necessary drivers needed.

    Disclaimer:
    Unfortunately, root is needed, so if you do not have root, do not continue reading.


    If you do have root, without further ado, let's begin.

    • Download the files provided below:
    • Once downloaded, open the ZIP file, head to Qualcomm Drivers, copy the "Mi5_Qualcomm_Drivers" to your desktop.

    • Once on your desktop, plug in your phone to your PC, make sure USB debugging is enabled.

    • Open a Terminal window and type the following code one line at a time:
    adb shell
    su
    setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb

    Note:
    If you have never done "adb shell" "su" before, you will get a Superuser request on your phone, press "Grant".
    Screenshot_2022-07-19-01-14-48-73_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg
    Once you have pressed Grant then do:​
    setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb

    Note2:
    If you get "error: device '(null)' not found" or you do not see your device when doing "adb devices" under "List of devices attached" in Terminal
    NVIDIA_Share_b58JrnICYe.jpg
    NVIDIA_Share_7sD2cTxK6c.jpg
    You have to switch from "File Transfer / Android Auto" to "Photo Transfer" under the popup when you plug in your phone to your PC .
    Switch Use USB For to Photo Transfer.jpg
    This is what I have to do on my personal PC, but not on other PCs for some reason, it might be the same for you.
    • After doing the previous command you will hear a USB disconnect and reconnect sound, do not panic, this is intended.

    • Open device manager.
    1658219286386.png
    Under "Other devices" you will see quite a few devices with no driver, we're only going to focus on 3 of them.​
    • Double click on the first "SM8350-MTP _SN:E1B16ED0" device you see, once the properties window appears, press "Update driver...".
    1658219359722.png
    • When the "How do you want to search for drivers?" window appears, press "Browse my computer for drivers".
    1658219489438.png
    • When the "Browse for drivers on your computer" tab appears, press "Let me pick from a list of available drivers on your computer".
    1658219558722.png
    • When the "Select your device's type from the list below:" tab appears, press the top most "Show all devices" option and press next.
    1658219674517.png
    • When the "Select the device driver you want to install for this hardware" press "Have Disk...".
    1658219765684.png
    • When the "install from disk" window appears, press browse.
    1658219834943.png
    • When the locate file window appears, navigate to the "Mi5_Qualcomm_Drivers" folder you extracted to your desktop earlier and open the "qcmdm.inf" file.
    1658219924679.png
    • When you return to the previous "Install from disk" window press Ok. Once that window closes, you should be at the previous "Select the device driver you want to install for this hardware" window, on the left side, make sure to select "Qualcomm Incorporated", on the right, scroll down until you find "Qualcomm HS-USB Android DIAG 9018" click it, and press next.
    1658220200551.png
    • You might get a "Update driver warning" stating that updating this driver is not recommended because Windows cannot verify compatibility, press yes.

    • Once Windows successfully updates your driver, press close, keep in mind windows might restart after you do so. You will have to do the command again.
    "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb".​
    • Now do the same to the other 2 "SM8350-MTP _SN:E1B16ED0", for me, QPST only worked with the second one, it could different for you.

    • Once you have done the steps above, open QPST config.
    NVIDIA_Share_3wYhw27bjU.jpg
    • Once QPST is open, at the top press "Start Clients" > and press "EFS Explorer", once you press EFS Explorer, a "Phone selection" window will appear, be sure to select the one that is called "LAHAINA" and has your ESN on it, AKA do not select one that says "Unknown" and "No ESN", press OK.
    NVIDIA_Share_OECOkT21k2.jpg
    • Once you press ok, it will take 20-30 seconds for the EFS Explorer window to appear, once it appears, on the left side press "policyman", and on the right drag and drop "policies.xml" to the desktop.
    1675835868694.png
    • Open "policies.xml", and remove the following 3 lines.
    1675835976652.jpeg
    1675836018595.jpeg
    • Once you have removed the 3 lines, and ONLY those 3 lines, once you have saved and closed the file, just drag it back into EFS Explorer, once that is completed, do a reboot.

    • Wala! Your OnePlus 9 or 9 Pro should be able to connect to N77 as seen below.
    OOS 13 N77 5G Speedtest.jpg
    Network Signal Guru OOS 13 N77.png
    By doing this mod, it completely ignores the "generic_band_restrictions.xml" file, @ale_jenior this might even allow it to connect to LTE band 28. I however cannot test this.

    Hopefully this tutorial helps all of those on Verizon and have a 5G UW plan.

    Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this modification before applying it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

    Make sure you're on Oxygen OS 11 (11.2.10.10 preferably, as this is what I tested this on):

    • Download this APK and install it.
      • Alternatively, go to this website, follow the guide, and carry on.

    • Once both the apk (unless you went the alternative route) and QPST are installed, open your phone dialer and dial *#801#.

    • Press Engineering Mode, if it asks you, press "just once".
      • Ignore if you went the alternative route, it should open engineering mode once you dial *#801# right away.

    • Once engineering mode is open, turn on the last switch called "Rndis,diag switch" keep it on that screen and plug your phone into your PC, then open the QPSTConfig program on your computer.
    • Only 1 device should show up, make sure it's selected.
      QPSTConfig_kIvg9mNXd6.jpg


    • Press "Start Clients" in the menu bar and "EFS Explorer" in the sub menu.
    QPSTConfig_TFwK2DUhdp.jpg

    • Again, only 1 device should show up, make sure it's selected, and press ok.
      EFSExplorer_PtLfwFTrOD.jpg
    • On the left side click "policyman", on the right side find "generic_band_restrictions.xml" drag and drop it onto your desktop.
    EFSExplorer_3AiZOXsDuF.jpg
    • Open it (duh lol)
    • Look for the 2 lines shown in red boxes below.
    EFSExplorer_f3EYw7Y5dr.jpg

    • Change it exactly to how it is shown below (extra space after each 47)
    EFSExplorer_UlfrUNNZZw.jpg
    • Once you've edited and saved the file, drag and drop it back into your "policyman" folder (make sure to not change the file name or extension, always make a backup of your original file!), congrats! It should be enabled, make sure to reboot to make sure the effects apply.

    Here is a speed test I ran on my 9 Pro, and next to it, is Network Signal Guru showing it connected to N77.​
    yahSU6e.jpg
    PP2CS3r.jpg

    Something important to keep in note is that I have not tested this on Oxygen OS 12, if someone has enough courage to try on OOS 12 and finds a way to enable engineering mode, feel free to let others know in a reply.

    I have only tested this on the North American LE2125 OnePlus 9 Pro 5G on Verizon, it should work on the North American LE2115 OnePlus 9 5G on Verizon, and maybe work on the T-Mobile LE2117/LE2127 OnePlus 9/9 Pro. Unsure if international variants have N77 and N78 disabled (I doubt they would work on Verizon anyways), only try if you're willing to risk it! Let me know in a reply if it works.

    Now I don't know if you need Qualcomm Drivers, but if your phone doesn't appear in QPST, download them from here.

    If you have any more questions, feel free to ask me!

    I cannot confirm whether or not this works on any other OnePlus 9/ 9 Pro model, do this mod at your own risk.​

    5
    Notice:
    I did this on a U.S. OnePlus 9 Pro LE2125 running Oxygen OS 12.1 (LE2125_11_C.61)

    I have not tested to see if N77 actually works after performing this mod, also, please keep in mind:

    Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this modification before applying it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

    I will test to see if I get an N77 signal sometime today.

    KEEP IN MIND THIS DOES NOT SURVIVE A REBOOT, OnePlus changed something going from OOS 11 to OOS 12, you will have to use QPST EFS Explorer every time you reboot to enable N77, I have no idea why.

    It seems OnePlus has officially enabled N78 on the 9/9Pro, no idea why they didn't go ahead and enable N77 but oh well 🤷🏻‍♂️ (maybe Verizon is unlocking N78 soon, no idea).


    Good news! I have figured out a way to get QPST working on Oxygen OS 12! This means I could also enable N77 on the 9 and 9 Pro running on the Verizon network! This would not have been possible without the help of @Rootk1t for showing me how to get Rndis,diag switch working, @sakun-ice, @jimmy123322, and @21prods for providing the necessary drivers needed.

    Disclaimer:
    Unfortunately, root is needed, so if you do not have root, do not continue reading.


    If you do have root, without further ado, let's begin.

    • Download the files provided below:
    • Once downloaded, open the ZIP file, head to Qualcomm Drivers, copy the "Mi5_Qualcomm_Drivers" to your desktop.

    • Once on your desktop, plug in your phone to your PC, make sure USB debugging is enabled.

    • Open a Terminal window and type the following code one line at a time:
    adb shell
    su
    setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb

    Note:
    If you have never done "adb shell" "su" before, you will get a Superuser request on your phone, press "Grant".
    Screenshot_2022-07-19-01-14-48-73_785cfb1f0fb0c9a2030c9b38a1c3479a.jpg


    • Once you have pressed Grant then do:
    setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb

    • After doing the previous command you will hear a USB disconnect and reconnect sound, do not panic, this is intended.

    • Open device manager.
    1658219286386.png
    Under "Other devices" you will see quite a few devices with no driver, we're only going to focus on 1 of them.​
    • Double click on the first "SM8350-MTP _SN:E1B16ED0" device you see, once the properties window appears, press "Update driver...".
    1658219359722.png
    • When the "How do you want to search for drivers?" window appears, press "Browse my computer for drivers".
    1658219489438.png
    • When the "Browse for drivers on your computer" tab appears, press "Let me pick from a list of available drivers on your computer".
    1658219558722.png
    • When the "Select your device's type from the list below:" tab appears, press the top most "Show all devices" option and press next.
    1658219674517.png
    • When the "Select the device driver you want to install for this hardware" press "Have Disk...".
    1658219765684.png
    • When the "install from disk" window appears, press browse.
    1658219834943.png
    • When the locate file window appears, navigate to the "Mi5_Qualcomm_Drivers" folder you extracted to your desktop earlier and open the "qcmdm.inf" file.
    1658219924679.png
    • When you return to the previous "Install from disk" window press Ok. Once that window closes, you should be at the previous "Select the device driver you want to install for this hardware" window, on the left side, make sure to select "Qualcomm Incorporated", on the right, scroll down until you find "Qualcomm HS-USB Android DIAG 9018" click it, and press next.
    1658220200551.png
    • You might get a "Update driver warning" stating that updating this driver is not recommended because Windows cannot verify compatibilty, press yes.
    1658220294212.png
    • Once Windows successfully updated your driver, press close, keep in mind windows might restart after you do so. You will have to the
    "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" command again.​

    • Once you have done the steps above, enabling N77 is somewhat similar to before, but I will repeat the steps again, start with opening QPST.
    1658220671508.png
    • Once QPST is open, at the top press "Start Clients" > and press "EFS Explorer"
    1658220750658.png
    • Once you press EFS Explorer, a Phone selection window will appear, select your phone and press OK.
    EFSExplorer_frvNzoDGcn.jpg
    • Once you press ok, it will take 20-30 seconds for the EFS Explorer window to appear, once it appears, on the left side press "policyman", and on the right drag and drop "generic_band_restrictions.xml" to the desktop.
    1658221153518.png
    1658221184711.png
    • Open "generic_band_restrictions.xml" and edit the follow line to remove "77".
    wordpad_GDKeTUfx67.jpg
    wordpad_2_GDKeTUfx67.jpg
    • Once you removed "77" as shown above, save the xml, then just drag and drop the "generic_band_restrictions.xml" file into EFS Explorer and N77 should be enabled!
    2
    2
    Very interesting to say the least I would assume you are just connected to 77 I don't know why it would say 78? I do not think n78 is enabled anywhere for Verizon yet.


    But are you on Android 13 and you're rooted I take it?, Is it the same instructions to enable n77 as it was before with Android 11?

    Did you install anything or you just tried the code and you were able to get into those menus after being rooted?
    I actually "included" N78 in the "carrier_policy.xml" file as it was missing before, and it survives restarts, what doesn't survive restarts is the "generic_band_restrictions.xml" file, I remove the N77 exclusion from that but every restart/every ~12ish hours N77 reappears in the exclude section.

    I am on OOS 13 (you can tell by the status bar icons), yes, I am rooted, this is not possible without root, and no this will take a new guide on how to enable it, it still requires QPST and most of the instructions, but it includes modifying new xml files in QPST.

    I installed the Magisk Module you provided, and then the dialer code worked. Weird stuff haha.

    However, how do you enable VoWIFI with the dialer command? I cannot find it.
    1
    Wonder if it would work for AT&T. I'm guessing the bands are already available though, just not provisioned on AT&T's end.