Yes, you should get tmo 5G
I have the tmo 8t 5g and switched to global rom, can you please send me your file, so I can try it out, thxif anyone is using the global rom on a Tmobile 8t+ i would like you to try my modified files. They are the original Tmobile settings with the blocked lte bands enabled, dss enabled and 5g allowed on all networks.
i am successfully using them on the Tmobile rom and get standalone 5g but haven't received my unlock token yet so i can't test with the global rom.
Thanks for this (and OP). Worked perfectly on my wife's unlocked KB2005 8T. Using a standard Verizon "4G" sim that's years old from her original Pixel XL. Note the status indicator top right in the picture.Fixed my issue. Had a debloater module for Oneplus enabled in magisk, disabled it and worked.
I attached the config for Verizon cause it's way different than the ones that OP uploaded and it was a ***** to track down the info on how to configure it properly for Verizon.
Thanks for the quick response, and this makes sense given my experience so far with the enabled 5G. I think it's a matter of time once the infrastructure gets built out more around my area.5G is a protocol. It does not change the laws of physics. N66 only has the bandwidth that it has been licensed to. Although 5G can combine spectrum, allow more devices on the same spectrum better than 4G and is optimized by 20% theoretical, it won't create bandwidth where there is none. As things get built out, service may improve. You've future proof a bit. Most carriers likely do not yet support SA.
HelloMod edit - translated by https://translate.google.com:
I tried to extract hydrogen files in China based on your method. I hope these XML can help you improve this operation.
The download address is
I tried to extract nitrogen files in China according to your method. Hope these XML can help you improve this operation. The download address is
**************************
我根据你的方法尝试提取了中国地区氢的文件,希望这些XML可以帮助您完善此操作。
下载地址是
我试图根据您的方法在中国提取氮气文件。希望这些XML可以帮助您改进此操作。下载地址是
chinabackup.rar
drive.google.com
It means carrier_policy.xml installed is not compliant with your mobile operator.I followed the guide completely and have started to see the 5G icon, but every time it connects the whole mobile network on my Oneplus disconnects..
I know the network supports it since cellmapper shows me 5g connected (albeit for a second or two) and status as un-restricted
Anyone else having this issue or know how I can debug?
P.s I'm using Etisalat that matches the n78 5g band offering of my device
Install attached files.I works, but partially. After reboot it is back to 4G. I noted the following - in the service menu - after every reboot you have to activate again "NR/LTE/..." mode, then the 5G works. After reboot it reverts to the standard LTE setting. The "preferred network type" in phone settings is shown as "2G/3G4G/5G (Automatic)", but this selection is not available in the selection list itself?!
Phone model KB2003, with OS 11.0.8.13.KB05BA, Operator - Telenor Bulgaria.
Any suggestions for a permanent solution (surviving a reboot) or how to enable as well VoLTE?
Hi,Install attached files.
After that dial *#800# in stock dialer, choose «engineering mode» -> oneplus_logkit -> «Function Switch» tick «VoLTE switch», «VoWifi switch» and «VT switch».
In cellular settings of your sim card(s) enable VoLTE and VoWIFI.
Reboot device.
View attachment 5359707View attachment 5359709View attachment 5359711
It also depends on what carrier profile is activated on your device. Maybe the wrong one.Hi,
Many thanks. In my case 5G is persistent after reboot, but offline until I switch between APN: (default) to (custom) and back to (default). Where custom can be anything. I tried to create new APN like default but this is somehow limited on OOS.
Please, if there is a solution for this too, could you please share it to make some other like me happy?
Thank you in advance,
amplatfus
<plmn_list name="dss_plmns" ns="global">
228-01 505-01 505-11 505-39 505-71 505-72 204-04 262-01 262-06 204-16 204-20 232-03 232-07 204-04 311-480 240-02 238-06 240-01 206-01 204-08 204-12 204-18 204-69 238-01 238-10
</plmn_list>
<lte_feature name="NR_DSS">
<all_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</all_of>
</lte_feature>
<lte_feature name="NR_DSS">
<any_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</any_of>
</lte_feature>
I have managed to do it on Android 12. The steps are similar to those described several pages ago, but there are a few extra steps to be taken. Steps to follow:Has anyone tested if it is possible to do this on any AOSP custom rom based on Android 12?
Quick response, I might write a proper post with more detailled steps but I don't have the time to do so at the moment.Could you please tell us how you managed to use QPST with LineageOS? I tried to install the EngineerMode apk but it doesn't work and I also can't install those special drivers needed for QPST. Windows always gives me an error message that the driver files are not compatible. Is there a way to access those settings without having to revert back to OOS for its Engineer Mode ?
Quick response, I might write a proper post with more detailled steps but I don't have the time to do so at the moment.
I assume you already have Qualcomm drivers at hand, QPST installed in your computer, ADB ready and debugging option enabled in your phone. So I followed these steps (the problem of not being able to use Engineer Mode apk is solved with steps 1 to 3, but don't forget to apply step 6 when you finish):
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,diag_mdm,adb
4. Go to Control Panel – Device Manager .. you will see two unknown device.
Right click on the first one – Update Driver – browse my computer drivers - Let me pick form a list of available drivers- click on Have Disk ..- show all devices browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other unknown Driver. Choose 9018 for both unknown drivers.
5. Change carrier_policy XML files with QPST
6. adb reboot