Okay so here is the issue I'm facing today. I bought a Sprint Galaxy S5, and I managed to unlock it for domestic use (AT&T). I cannot get an LTE connection because my Qualcomm processor does not have the appropriate bands to use ATT LTE's network.
I read on here that you can write your NV memory to write the firmware and enable these other bands using QPST and QXDM. The issue I'm having though is getting my computer to install the diagnostic driver for COM port. It reads the Modem under modem tab in device manager. Since the computer doesn't think there is a diagnostic port, QPST configuration cannot open a diag port which is what I need. I've been able to successfully put my phone in rndis + DM + modem by using this in emulator,
su
setprop sys.usb.confing_rndis,diag,diag_mdm
Do not type the first _ as it's meant as a space bar, but USE diag_mdm
But there is no indication that any driver has installed, and does not appear in device manager (even with hidden devices shown).
I'm running 6.0.1 CM13 w/twrp recovery with SELINUX set to permissive.
On windows 8
I also noticed that the guide to add frequency bands was written in 2014, I also know that in Lollipop, you needed to enable CP Logging to get it show up.
What I'm wondering is if there is a missing step to properly installing the diag driver, or if Qualcomm/Samsung found other means to activate it.
I noticed that when using EFSPro I can set it to Diagnostic + Modem + adb but I can only read not read/write NV memory
Also I observed when I send the SPC to read the phone with EFSPro, it says
"SPC was accepted by the phone!"
Then followed by.. "SPC was not found".
Then after I close that popup it reads my NV memory, but I can't write.
Is there a method to enable CP logging on CM13 MM and install the diag com port for QPST use? I don't have a stock recovery to enable CP logging through usual means in as I'm using TWRP.
Link to GUIDE
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Thanks in advance.
Sent from my SM-G900P using XDA-Developers mobile app
xHolomovementx said:
Okay so here is the issue I'm facing today. I bought a Sprint Galaxy S5, and I managed to unlock it for domestic use (AT&T). I cannot get an LTE connection because my Qualcomm processor does not have the appropriate bands to use ATT LTE's network.
I read on here that you can write your NV memory to write the firmware and enable these other bands using QPST and QXDM. The issue I'm having though is getting my computer to install the diagnostic driver for COM port. It reads the Modem under modem tab in device manager. Since the computer doesn't think there is a diagnostic port, QPST configuration cannot open a diag port which is what I need. I've been able to successfully put my phone in rndis + DM + modem by using this in emulator,
su
setprop sys.usb.confing_rndis,diag,diag_mdm
Do not type the first _ as it's meant as a space bar, but USE diag_mdm
But there is no indication that any driver has installed, and does not appear in device manager (even with hidden devices shown).
I'm running 6.0.1 CM13 w/twrp recovery with SELINUX set to permissive.
On windows 8
I also noticed that the guide to add frequency bands was written in 2014, I also know that in Lollipop, you needed to enable CP Logging to get it show up.
What I'm wondering is if there is a missing step to properly installing the diag driver, or if Qualcomm/Samsung found other means to activate it.
I noticed that when using EFSPro I can set it to Diagnostic + Modem + adb but I can only read not read/write NV memory
Also I observed when I send the SPC to read the phone with EFSPro, it says
"SPC was accepted by the phone!"
Then followed by.. "SPC was not found".
Then after I close that popup it reads my NV memory, but I can't write.
Is there a method to enable CP logging on CM13 MM and install the diag com port for QPST use? I don't have a stock recovery to enable CP logging through usual means in as I'm using TWRP.
Link to GUIDE
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Thanks in advance.
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you ever solve this? I plan on following the same guide and I too am having this same problem.
Related
Hi I've been trying to figure out if AWS can be easily supported in models that don't have the 1700 WCDMA spectrum enabled. Not sure if it's hardware or software.
So far I've found 1700 References look to be missing from the variant I have in the QCN
Actual Supported GSM 1900/850
WCDMA 1900/800/1800/900/2100
Edge 850/900/1800/1900
I've managed to pull the QCN files from 2 Moto X for comparison however I don't have a developer model or T-mobile version to compare.
Could some one be kind enough to send me a copy of theirs. Please PM me since it could contain your IMEI since I see a single reference so far that isn't a null value.
Root or unlocked bootloader is not required
You'll need to install the moto x drivers located here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94931/p/30,6720,8696/reg/348778
QSPT Tools 2.7 Build 378 or newer
Please google where to find it I'm unsure if I'm allowed to post it.
Then you need to boot your phone with BPTools enabled.
1. Power off device
2. Hold Down and Power
3. Follow Instructions to select BPtools (Up is actualy to select not power)
4. Phone will boot normally however new devices will be listed in device manager
5. Go into device manager and you'll see 3 Moto references and 1 rmnet with no drivers in Other devices. You'll need to force a driver motorola drivers don't have references to vendor hw id correctly.
6. Select "Motorola QC Diag Interface" Update Driver --> Let me pick from a list of device drivers from my computer --> Show All Devices --> Motorola --> Motorola QC Diag Port (Force Install) Should now have a port assigned.
7. Start QPST Configuration --> Select Ports Tab --> Select Com# - USB/QC Diagnostic (Should See SURF8960) --> Now on the toolbar tab Select Start Clients --> Software Download --> Select Backup Tab --> Browse where to save QCN File then hit start.
EDIT: Bands are defined in the NVM which is inaccessible in EFS Explorer as well as mot_hob when using QPST? I wonder what mot_hob is. Looks like you need QXDM however I don't have an XP box at the moment.
so you are trying to enable the software disabled bands?
eeshlikhith said:
so you are trying to enable the software disabled bands?
Click to expand...
Click to collapse
Yeah pretty much so far I had one sample for T-mobile from @theOrangeMix and compared the two QCN file and didn't see a 1700 band listed in the qcn. It maybe in a part that is OEM specific, that the tool cannot read. MSM8960 has a software based modem much like the I747 and T999L so assuming Motorola went the same route we can possibly just repurpose the modem for AWS friendly frequencies which should be in the T-mobile or Developer variant.
So far the nvdata partition is write protected atleast with QPST not sure if it has something to do with the locked bootloader, haven't unlocked mine yet or they have some other tool they use to alter the nvdata.
I'm trying to follow this guide to enable extra LTE band on my g2 d800.
Through hidden menu 3845#*800# I have set port settings -> Diag Setting -> USB
Also I've enabled Hardware key mode (all three back button on powering on -> Mode on)
However, QPST is unable to see my phone. I have to disable Show serial and USB /QC diagnostic port only to see the phone modem port. Also even after doing that and adding it, qpst doesn't detect phone
Any ideas of what might be causing it ? I'm using Windows 7 64-Bit as OS and Cloudy 3.3 w/ dorimanx 4.6 kernel and USB mode set to MTP
Mafioso said:
I'm trying to follow this guide to enable extra LTE band on my g2 d800.
Through hidden menu 3845#*800# I have set port settings -> Diag Setting -> USB
Also I've enabled Hardware key mode (all three back button on powering on -> Mode on)
However, QPST is unable to see my phone. I have to disable Show serial and USB /QC diagnostic port only to see the phone modem port. Also even after doing that and adding it, qpst doesn't detect phone
Any ideas of what might be causing it ? I'm using Windows 7 64-Bit as OS and Cloudy 3.3 w/ dorimanx 4.6 kernel and USB mode set to MTP
Click to expand...
Click to collapse
Dont bother. The bands have to be programmed into the radio antenna. Even if you do set the files to allow those bands without it being programmed into the antenna it wont do any good and you run a good chance of messing something up
zelendel said:
Dont bother. The bands have to be programmed into the radio antenna. Even if you do set the files to allow those bands without it being programmed into the antenna it wont do any good and you run a good chance of messing something up
Click to expand...
Click to collapse
Ok thanks As i found out also, it doesn't work on G2 but didn't know the reason...
BTW if anyone is stuck with same problem i.e. QPST not detecting port do below commands via adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Mafioso said:
Ok thanks As i found out also, it doesn't work on G2 but didn't know the reason...
BTW if anyone is stuck with same problem i.e. QPST not detecting port do below commands via adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Click to expand...
Click to collapse
thank you
that makes the software detect my phone, but now i cant connect with it with mtp
i lost my imei after flash and i'm using qpst to recover it, when i click backup it tells me:
Memory Backup Failed
Disk Error while writing to file.
i need help please
i'm following this guide:
https://www.**********.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
Hi all,
I have been having some trouble following a guide on how to add GSM+LTE bands to this device. Specifically, I am struggling to connect to this device in Diagnostic Mode.
I am running Windows 7 x64. I have installed Samsung USB Driver v1.5.45.00. I have tried an updated driver but I seem to have had less issues with this version. I have also tried using Qualcomm USB Drivers For Windows (QD Loader) but when I select this folder to search for an alternative driver instead of the one Windows assignes I have to manually select an *.inf file and the options (HD-USB QDLoader 9XXX) does not make any sense to me which driver is required for my device.
I can run ##DIAG# in the Phone app and bring up PhoneUtil which brings up a menu to select CDMA MODEM / PDA and I have used both with no success. This menu allows me to access RNDIS+DM+MODEM. If I try to use other applications to switch to CP from AP in other USB settings or PDA to MODEM the phone disappears in device manager.
In QPST Configuration I have to untick "Show Serial and USB/QC Diagnostic ports only" to show the port and select the device. If I continue and use Software Download to back up the xQCN (NV memory) file it gets stuck at 12% and gives me an error "Could not Communicate in Diagnostic Mode"
If I use CDMA Workshop to do a backup the files hex just shows 00's and EFS Professionals backup is the same.
I have tried using stock Lollipop 5.0 firmware an enabling CP logging, rooted 5.0, a custom ROM including CM and I am currently running rooted 6.0.1 firmware.
I used Idoneapps paid service to find the SPC for my device but I don't believe there is any equivalent service to enable or disable the bands on my device.
All I can consider is wrong is the possibility of not having the right drivers but I have no idea where to find the right ones. I am at a bit of a dead end, any help would be appreciated.
Thanks.
tai1z said:
Hi all,
I have been having some trouble following a guide on how to add GSM+LTE bands to this device. Specifically, I am struggling to connect to this device in Diagnostic Mode.
I am running Windows 7 x64. I have installed Samsung USB Driver v1.5.45.00. I have tried an updated driver but I seem to have had less issues with this version. I have also tried using Qualcomm USB Drivers For Windows (QD Loader) but when I select this folder to search for an alternative driver instead of the one Windows assignes I have to manually select an *.inf file and the options (HD-USB QDLoader 9XXX) does not make any sense to me which driver is required for my device.
I can run ##DIAG# in the Phone app and bring up PhoneUtil which brings up a menu to select CDMA MODEM / PDA and I have used both with no success. This menu allows me to access RNDIS+DM+MODEM. If I try to use other applications to switch to CP from AP in other USB settings or PDA to MODEM the phone disappears in device manager.
In QPST Configuration I have to untick "Show Serial and USB/QC Diagnostic ports only" to show the port and select the device. If I continue and use Software Download to back up the xQCN (NV memory) file it gets stuck at 12% and gives me an error "Could not Communicate in Diagnostic Mode"
If I use CDMA Workshop to do a backup the files hex just shows 00's and EFS Professionals backup is the same.
I have tried using stock Lollipop 5.0 firmware an enabling CP logging, rooted 5.0, a custom ROM including CM and I am currently running rooted 6.0.1 firmware.
I used Idoneapps paid service to find the SPC for my device but I don't believe there is any equivalent service to enable or disable the bands on my device.
All I can consider is wrong is the possibility of not having the right drivers but I have no idea where to find the right ones. I am at a bit of a dead end, any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
man, if anyone can shed some light on this, itll breathe some new life into my phone. I looked for the very same thing a while back as i switched to H2O wireless using AT&T towers and its working, but just on HSPA+ and thats because all of the LTE bands arent unlocked on my phone. QXDM and QPST are the tools we need, but the driver issues are whats stopping me too. Anyone with insight would be greatly appreciated
bump
I was having trouble with connecting to B5 ( 850) LTE as I was consonantly connected to 1800... So i searched and searched and managed to unlock bands and now getting B5 850 as the first preference ...Below guide can literally break your phone if you do not follow correctly ...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will run.
*/
1. Make sure your phone is rooted and you have SuperSU installed, ADB drivers installed
2. Download "Setup DFS Studio" from http://cdmatool.com or the DFS Studio 16.05.31.0 (an older version) from here https://mega.nz/#!h1ImHJyK!gBcp2j6wI...YSoIjPkY_hJJVY ( use this - demo will work and do not update / will prompt with mandatory update you can drag that aside)
3. Connect the phone to the computer via USB
4. Select MTP and USB debugging
5. Open command prompt from Start => Run and type "cmd.exe". Once opened, type "adb shell". It should show "[email protected]_x2:/ $"
6. Open the SuperSU app on the phone
7. Type in cmd.exe "su" and grant access of ADB shell in SuperSU, you will see "[email protected]_x2:/ #"
8. Type in cmd.exe "setprop sys.usb.config diag,adb" and your phone will enter into Diagnotics Mode - this means that the MTP connection will be lost (you won't find any portable device in My Computer).
9. The drivers should be installed for the Diag Mode and you can see in Device Manager at Ports - Qualcomm HS-USB Android DIAG 901D (COMxx). ( mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS )
10. At this stage, if all should be well, you can start the "Qualcomm Tool" from DFS Studio folder. You can close the login window and it will run in demo mode (enough for what we need)
11. In the "Main" tab, double click on "Qualcomm HS-USB Android DIAG 901D (COMxx)" to select it - in the DFS log you will see "Qualcomm HS-USB Android DIAG 901D (COMxx) device in diagnostic mode"
12. In DFS Tool select tab "Band"
13. In tab "CDMA/GSM/HSPDA" select "RF BC Config" and then "Read"
14. Select the bands you need and then press "Write"
15. In the same tab, select "Bands Preffered" and do the same as above (read-write)
16. Select "LTE" tab which is aside "CDMA/GSM/HSPDA" and do the same as above. I changed values only in "LTE BC Config #6828" as the "LTE BC Config DIV #6829" didn't work for me when I pressed Read (there was nothing selected, all blank).
17. After operation had been completed, close Qualcomm Tool, unplug the phone and restart it.
Notes:
You must back up Rom( stock or modified stock Turbo alike and the EFS partition( in TWRP) as my first reboot said no sim... With EFS back up phone was back from dead
Credits for this goes to chatmonchy and valy_cta
This works to use x720 on US network?
It seems it would work on 720 as well, given that it opened bands that are officially open on 720 but not on 727 (such as band 20).
Abdiel1224 said:
This works to use x720 on US network?
Click to expand...
Click to collapse
Should as I was able to write all available bands, for instance I am using Vodafone which has duplex 1800 but x720 out of box support only one after changes I get both
... Please do not forget to back up ROM (stock or modified stock like Turbo) and EFS partition.
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
vw_diesel said:
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
Click to expand...
Click to collapse
I've mentioned bro,
mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS. i have also installed QPST ( QPST configuration)
you can find here,
https://drive.google.com/file/d/0B4NOhMSMyPxuZURyZldIbGtXYWs/view
*#*#76937#*#* diag port enable
saraprobe said:
I've mentioned bro,
mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS. i have also installed QPST ( QPST configuration)
you can find here,
https://drive.google.com/file/d/0B4NOhMSMyPxuZURyZldIbGtXYWs/view
Click to expand...
Click to collapse
Hmm something seemed to be messed up as I didn't have the refresh port dialog box with the version of DFS i had downloaded. I only had "reset" which didn't seem to do anything. I think i ended up downloading the older version and that one worked.
termomen said:
*#*#76937#*#* diag port enable
Click to expand...
Click to collapse
This didn't do anything for me, however i'm also on Lineage OS so I don't know if those codes are ROM specific.
I can however confirm this message works fine for the x720! I was able to unlock LTE bands 17 and 12 confirmed with network signal guru. Thanks for the write up! :laugh:
vw_diesel said:
Hmm something seemed to be messed up as I didn't have the refresh port dialog box with the version of DFS i had downloaded. I only had "reset" which didn't seem to do anything. I think i ended up downloading the older version and that one worked.
This didn't do anything for me, however i'm also on Lineage OS so I don't know if those codes are ROM specific.
I can however confirm this message works fine for the x720! I was able to unlock LTE bands 17 and 12 confirmed with network signal guru. Thanks for the write up! :laugh:
Click to expand...
Click to collapse
Glad to contribute...mine could have been windows 10 related and only recognised with Stock ROM with super SU
Any follow up on this? Have you went out into the wild and actually confirmed that the unlocked bands are truly being used and not just -reporting- unlocked? I'm still waiting to hear from someone saying the unlocked bands were actually proven to be in live action usage after being "unlocked".
Mine is working... Try it ur self
Driver for Qualcomm HS-USB Android DIAG 901D
vw_diesel said:
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
Click to expand...
Click to collapse
Can you please advise where you download the windows 7 driver for Qualcomm HS-USB Android DIAG 901D? Thank you in advance!
When restarting, the value returns to original.
The wcdma band returns to default.
Omg...
Please change the post title which is confusing, you unlocked nothing .... B5 is already unlocked in the phone, all you did, is choose b5 over the other signals as the preferenced one thts it , dont say you unlock stuff when they already are !.... Right now we know that this phone have this hardware for the le x720(i dont know if its same for le x727 but apparently it is) :
SKY77643-21
Hardware allows u to :
WCDMA Bands I, II, III, IV, V, VIII, IX
TD-SCDMA Bands 34, 39
FDD LTE Bands 1, 2, 3, 4, 5, 7, 8, 9, 12, 13, 17, 20, 28, 30
TDD LTE Bands 38, 39, 40, 41
The x720 band are : B1/2/3/4/5/7/8/20/38/39/40/41
The x727 band are : B1/2/3/4/5/7/8/12/17/29/30/38
So maybe try to unlock b28 (hardware compatible) for example or b12 for the le x720 since only the x727 have it and then u can confirm tht u unlock something cause your post and the title are not saying the same.
As with le max 2, modem firms 15S and beyond have restrictions. Even if you change the band, you return to the original.
Japanese guy are making temporary connection possible situations, but it seems to return to the original after restarting.
http://gadget.hrksv.com/2017/05/23/post-4812
@saraprobe which is the decryption code for mega ?
marios199546 said:
@saraprobe which is the decryption code for mega ?
Click to expand...
Click to collapse
Download from cdmatool.com
Because the update is now mandatory and you need to register in order to work now
zaiem93 said:
Please change the post title which is confusing, you unlocked nothing .... B5 is already unlocked in the phone, all you did, is choose b5 over the other signals as the preferenced one thts it , dont say you unlock stuff when they already are !.... Right now we know that this phone have this hardware for the le x720(i dont know if its same for le x727 but apparently it is) :
SKY77643-21
Hardware allows u to :
WCDMA Bands I, II, III, IV, V, VIII, IX
TD-SCDMA Bands 34, 39
FDD LTE Bands 1, 2, 3, 4, 5, 7, 8, 9, 12, 13, 17, 20, 28, 30
TDD LTE Bands 38, 39, 40, 41
The x720 band are : B1/2/3/4/5/7/8/20/38/39/40/41
The x727 band are : B1/2/3/4/5/7/8/12/17/29/30/38
So maybe try to unlock b28 (hardware compatible) for example or b12 for the le x720 since only the x727 have it and then u can confirm tht u unlock something cause your post and the title are not saying the same.
Click to expand...
Click to collapse
Do it yourself and report instead of making assumptions
saraprobe said:
Do it yourself and report instead of making assumptions
Click to expand...
Click to collapse
Assumption ?? Just saying u didnt " manage to unlock " something like u said in ur first post since b5 is already unlocked by default anyway good luck and naa i already knw its not gonna work since values goes back to default People on other post with other phone's had to change nvram values too in order to make it work anyway gl if i have time to unlock b28 ill see
zaiem93 said:
Assumption ?? Just saying u didnt " manage to unlock " something like u said in ur first post since b5 is already unlocked by default anyway good luck and naa i already knw its not gonna work since values goes back to default People on other post with other phone's had to change nvram values too in order to make it work anyway gl if i have time to unlock b28 ill see
Click to expand...
Click to collapse
I did and travelled OS
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Got stuck at PDC
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
aperture22 said:
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
Click to expand...
Click to collapse
Did you install the Qualcomm usb driver which came included in the QPST zip file.
I'm not sure if it is a problem with the qpst version ,I'm using QPST 2.7.480.
And once I run the command in adb shell I get my device to show up as Qualcomm USB Composite Device in device manager under the universal serial bus controllers category.
And if everything is working well , the pdc will not show anything when it opens up but you'll find your device in the drop down menu.
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
aperture22 said:
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
Click to expand...
Click to collapse
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
activate button is disabled even after running as admin
Gauravlonkar said:
activate button is disabled even after running as admin
Click to expand...
Click to collapse
To activate a profile: Right click on it and under setselectedconfig select sub0/sub1/both (try and check what works for you) and then you'll be able to click the activate button.
To deactivate select the sub under deactivate in the right click menu (or) just activate some other profile .
Do check the other xda forum posts related to this which i've provided links under reference, it might be helpful when you're stuck with something related to this .
the command after su doesn't do anything to my custom rom ....
prokiller1199 said:
the command after su doesn't do anything to my custom rom ....
Click to expand...
Click to collapse
I've tested it to work with luisrom,Havocos and some other rom I don't remember which one.
Running the command doesn't bring any popup or open up anything on the phone but you'll be able to see the change in the device manager of your pc.
The change caused by the command only persists till it is connected (ie. if you unplug nd replug the usb cable it will revert to the default state), until you change the state from the option provided in your notification (ie . something like from charging only to file transfer or tethering ect) and restart of the device.
Do also check if you have the correct drivers installed.
*deleted*
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
aperture22 said:
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
Click to expand...
Click to collapse
hello,
why in PDC shows no devices (even when run as Admin)? I have the same problem.
gammerboy said:
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Click to expand...
Click to collapse
Sir can u make a total video tutorials so that we can easly understand because i just confuse what shuld i insta 8n pc and what shuld instal in mobile
---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------
ronaksworld said:
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
Click to expand...
Click to collapse
Sir in this zip file their two apk file but that not installed in my phone can u tell me which one shuld i instal in pc and phone step by step plz
Tried to enable VoLTE & VoWIFI on my Redme 9 Pro, using the PDC and can actually get the VoWIFI works. However, once the device reboot, it just fall back to the ROW_Commercial profile and have to redo again to get it work.
Can anyone help with this issue?
Thans for your support
I'm also trying to activate VoLTE on my oneplus3t. But stuck in loading a .MBN file in the PDC tool. When I click the load button and select the .MBN file to open nothing happens.