So I want to connect but I cant seem to add port in QPST config. I have usb debug turned on and have entered the service menu with 3845#*801#. I am wondering if it is because of the LG ADB Sooner driver that is causing the problem? Or is there another configuration I need to enable. I had no problem doing this with all of my old phones once I found out what the heck needed to be changed. Thanks.
Related
Has anyone succeeded to use QXDM with the Raphael?
Doing this in the CDMA HTC phones is very easy, you just need to run dmrouter.exe
But the CDMA dmrouter app won't work with the Raphael.
If you use the Wireless Modem app found in some ROMs, the Qualcomm Diagnostics port will be added to your computer but it won't respond to anything, of course, because the diag mode is not turned on. But this is telling us the Raphael can be connected to QXDM.
Hi, I have been working on this on and off for some time;
The raphael appears to be missing some components in it's driver set to enable this functionality. If you use smd_com.dll from another msm7201a device with debug code, you can activate the diag ports.. but i've not been able to get any data out of it.
Da_G said:
Hi, I have been working on this on and off for some time;
The raphael appears to be missing some components in it's driver set to enable this functionality. If you use smd_com.dll from another msm7201a device with debug code, you can activate the diag ports.. but i've not been able to get any data out of it.
Click to expand...
Click to collapse
Yeah, I do have smd_com.dll in my ROM, I guess that's why the diag port was created when I used the Wireless Modem app. Did you try any other apps? Have you found something similar to the dmrouter from the CDMA phones?
I also don't get any data from the diag port, maybe it's something related to the rilphone, like there is some procedure that needs to be called to activate the diag mode? Or maybe the rilphone we got just don't put any diag data through.
Whoops, was wrong about smd_com.dll, it's serialusbfnmodem.dll that's needed, along with some others
From the top of my head you need to insert the proper reg entries to load windiag.dll on port WDG1:
Then you need to load the CompositeFn drivers which support multiple com ports over a single usb connection, and set up the registry for those sub com ports, which uses serialusbmodemfn.dll if i recall
Using wmodem.exe by itself only connects to the device's SMD9: port which allows a data connection, but it won't allow diag communications over that port.. serialusbfnmodem.dll, and compositeusbfn.dll with support allows opening of a DAG1: port (diag)
These entries will load windiag.dll:
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WINDIAG]
"Dll"="windiag.dll"
"Prefix"="WDG"
"Order"=dword:500
"Index"=dword:1
"FriendlyName"="Windiag Driver"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WINDIAG\Settings]
"ServerIP"="169.254.2.2"
"ServerPort"=dword:9C4
"MaxRetryCount"=dword:32
"RetrySleepMs"=dword:2710
"Enable"=dword:1
Note server ip, that's the default client IP on a RNDIS connection that the phone would be using, i've tried to connect to it on that port though (2500) and not gotten a reponse..
I've been studying KS20's drivers/registry as they have a working diag connection, which uses the compositefn drivers etc. (ks20 is msm72xx as is raphael)
They have there a program EngineerMenu.exe, which has a menu option "USB Switch Diag" - that menu option runs SwitchUSB.exe, it seems to just switch the default USBFn driver from "RNDIS" (activesync hi speed) to "CompositeFn" - however when I trigger this change on raphael I never get a connection on PC side.. registry entry can be changed back to RNDIS and works fine again.
Recommend studying the KS20 ROM,
I have a Sprint Touch Pro 2 and am trying to use QPST, Bitpim or CDMA Workshop with it. However, whenever I plug it in and it gets detected by windows mobile device center (I'm using windows 7) It places it as a Portable device in Device Manager and won't list it as a Port. Whenever I use QPST, etc. they won't detect the USB, and instead only look for COM1 or COM2. If I manually try to add a "COM3"..etc. It says it either isn't accessible or busy.
Is there ANYTHING i can do to fix this? I just want QPST to recognize my phone so I can change settings. I've been looking for fixes for a good number of hours...can't find any. =(
Before connecting to PC, open phone dialer type ##3424# Then connect to PC after abt 10 sec.
My Verizon Galaxy s6 doesn't get detected at all by my computer AT ALL. I've tried different cables, PC's, USB Debugging etc.. It just charges that's about it. I looked in Device manager etc on all the computers I've plugged it into and it doesn't show anything being connected. Also I even tried a OTG Usb flash drive that doesn't get detected by the phone neither and the LED on the usb doesn't light up. Only thing I haven't tried is to force put it in MTP I don't know how to do that, i'm on 5.1.1 not marshmallow so I don't think I have that option and I can't update the phone to 6.0.1 because I don't use the phone on Verizon's network to OTA and the phone won't connect to my computer so I cant update it that way. The phone charges good when connected to the wall outlet. The only thing I can think of is maybe the charger port is damaged in someway that is not allowing the phone to detect a computer is connected to it which is why I never get a MTP notification. Before I do surgery on this phone and attempt to replace the charger port do y'all know of any reason to why it won't connect to the pc or is there anything I can do to force MTP?
##366633# , disable DM mode , done)
NFVK said:
##366633# , disable DM mode , done)
Click to expand...
Click to collapse
I just tried this still doesn't work
Smart Switch should be able to update it for you if you don't have service. Has to be in MTP mode though. Enable Developer options by going to About Phone -> tap Build Number a bunch of times and then change the USB connection type in Developer options. I think Smart Switch installs drivers. If none of that works maybe its a driver or OS problem.
I am trying to connect my Pixel to QXDM but am unable to establish a COM port. Looking through the USB configurations on the pixel it seems that the device does not support a USB diag mode. Am I missing something or is this really the case?
I attached the config files so someone else could take a look.
also want to know how to enable diag mode
Madscotsman said:
I am trying to connect my Pixel to QXDM but am unable to establish a COM port. Looking through the USB configurations on the pixel it seems that the device does not support a USB diag mode. Am I missing something or is this really the case?
Click to expand...
Click to collapse
Any updates? I'm looking for this too. For the Pixel XL people are saying this works:
"echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on"
However this just gets me "permission denied" on the Pixel, even as superuser, even after changing permissions on the f_diag directory to allow writes.
(nevermind, that turned out to be speculation based on the M8 -- still looking for a Pixel solution!)
https://forum.xda-developers.com/showpost.php?p=75252853&postcount=37
I have run into a weird problem with connectivity on my u12+ recently and was hoping to see if anyone had an idea to resolve it.
The phone will not be recognized by any computer as a device. This is across Win 10, 8 and Mac across various devices. It will only be recognized as a device if booted into recovery/download/bootloader/fastboot.
It WILL charge across all devices and is obviously connected, just not recognized when booted into regular Android.
It IS detected on the same computers and cables when in recovery/download/bootloader/fastboot.
I have tried multiple cables, ports, etc.
The phone is rooted and on the latest firmware (1.21.617) with Magisk/Xposed
Restored with RUU fresh and still had the same issue.
Stock and untouched kernel.
In settings:
USB Connection - Shows None
USB Debugging - Have tried enabling and disabling with no success
Developer Options - Tried enabling and disabling with no success
USB Configuration - Wont show anything other than Charging, wont change if attempted
It did work initially but just can't seem to figure this out! I know the kernel can control some USB stuff (At least on my 10) but since I have not touched the kernel, I was holding off on that to see if I could resolve it first.
Does anyone have any idea?
Could the build.prop somehow have been modified? If so, is the process for viewing and editing it, the same as the 10?
I was thinking of looking at:
service.adb
service.debuggable
sys.usb.config
service.adb.enable
Thanks!
Can anyone please provide their stock build.prop so I can compare mine with theirs?
Thank you