Hi, please help me with this. I need to activate the Diagnostics COM port in the SGH-i637.
Some info about this phone:
- This phone has a 32 bit Qualcomm MSM7201A CPU and Windows Mobile 6.1 OS.
- When connecting this phone as Modem, only modem driver is installed in Windows.
- During Flashing procedure (Turn off phone, press J, connect USB cable to PC, do not turn on phone) a Qualcomm device is detected and installs a COM port.
- Entering *#197328640#, then Option 9 (Common), then Option 4 (Diag_HFK_Configuration) only UART3 and UART 2DM are available (no USB Diag)
- Entering *#7284# nothing happens. Running Emchanger.exe or dataconnection.exe, you can choose between PDA or USB mode, but nothing happens.
- This phone is very similar to Samsung GT-B7320 and GT-B7330, on those both phones, changing from PDA to USB works (entering *#7284#) and installs the Diag COM Port.
So, any clue if there is a way to activate the Diagnostics port on this i637 smartphone?
Thanks!
Samsung GT-B7330 QXDM
I'm also working with QXDM and Samsung phones. I'm trying to used the USB modem mode(*#7284#) on my GT-B7330 but I can't find the right windows driver for it. Could someone provide me with the Samsung USB modem for the GT-B7330
I've search on the web and although I found many versions I could not get one which worked with the GT-B7330
Thanks
Running Emchanger not happening
as i wrongly updated my gt-b7320 to AT&T sgh i637 windows 6.5 now some of the keys are not working and led is always on
when i connect the phone to pc no COM port is showing it doesnt enter in boot mode as when i do it manually by *#7284# it shows cant find emchanger.exe
so is it possible to get my orginial version back by flashing it with original file.....
can anybody help me.......
Thnks in Advance
I'm a programmer but have no experience in Windows Mobile/CE programming before.
can anyone send me windows folder from healthy b7320 so that i can study and get u guys a solution.
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.
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.
Hi there,
I have been attempting to use QPST's memory debug program to dump the phone's memory. Specifically I'm trying to get the ebi_cs1.bin and ebi_cs1.bin files.
My problem is that QPST will detect the phone fine when USB Settings are at RNDIS + DM +Modem or DM + Modem + ADB modes but once I try to run the memory debug app, it requests to put the phone in download mode and QPST will no longer detect the phone when it is in download mode. When the phone is in download mode, it also does not come up with a Comport in device manager (hence QPST can't detect it), but ODIN will actually detect it. I must note that when the phone is on and not in download mode though, QPST and ODIN detect it on different comports.
I have uninstalled and reinstalled Samsung USB drivers numerous times as well as trying different versions of QPST, two different usb cords, and three different usb ports.
If anyone has any idea on how to dump these files with QPST or via alternative methods, please help me!
B.
Any ideas or alternative methods?
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.