Database Develop

[Q] I9000 UART DIAG Connection ?

when i try to enter UART mode on i9000 it's asking about an "7 CDCs" driver
i tried all the drivers i could find, but none of them is compatible
enter UART mode with *#9090# > Log via UART
then
enter *#7284# > UART MODEM - USB PDA

what are you trying to do?
theathering ?
if so, you don't need any of that

well...
was more thinking of making an normal sim-unlock solution for this model
i already found an uart connection on the phone PCB but for this you have to open the complete phone and work with the testpoints.. not suitable for normal users
on older android models you can enter the uart mode via diag driver over the usb port (for example on i5700, T939, i7500 etc with swallowtail driver) but this one uses a different driver

ahh, that makes sense now.
if you are using the KIES driver, uninstall it.
use the Android SDK drivers, then you will have full access to the phone via USB as a Com port

thats what i already tried, but it keeps popping up with the "7 CDCs" device and asking for drivers with i switch the USB to MODEM with *#7284#
I need to have the Android Diagnostic port available to make some checks
as USB ID i get:
USB\VID_1519&PID_0020

If you know the manufacturer (or chipset) of the modem or if modem is integrated to the motherboard, then you can probably get the drivers from the manufacturer vendor site.

there is another topic in the Dev section that is trying to do something similar
http://forum.xda-developers.com/showthread.php?t=756988

i'm afraid that also not gonna help..
we need to get the uart1 or uart2 enabled somehow..
maybe there is some hardware switching in the phone

This is exactly what I want to do. I'd like to enable Diag mode on the Samsung I9000 in order to use it with QPST.
I tried out the following procedures:
-sending at$susbc=1 on the modem port
-*#782872# does not work
-*#9090# => neither "log via usb", "log via uart" nor "log via ipc" works
Nothing helped.
Any hints are more than welcome.

Jan_1 said:
This is exactly what I want to do. I'd like to enable Diag mode on the Samsung I9000 on order to use it with QPST.
Any hints are more than welcome.
Click to expand...
Click to collapse
Why are you attempting to use it with QPST, the i9000 does not have a Qualcomm CPU.
Odia.

But isn't Snapdragon a Qualcomm chipset?
I'd like to get radio trace out of it.
I tested the Dalvik Debug Monitor (dump radio state) and logcat but these tools deliver very little radio information.

Hello Jan_1,
I expect the same answer, i want to do some radio trace with this type of mobile phone (i9000 and i7500),
If I find something, I will notify you here.
Thanks

Just thought I would finish this off, since no one has posted the way to the diag port.
For starters, you need to enable the weird comneon suspend device and the 7 acm cdc usb com ports.
This can be done thru the commands previously mentioned, *#7284# and *#9090#
Leave the top part alone, where it says MODEM. Change USB to MODEM.
In the 9090 menu set the speed to 115200
After doing that, you should get the devices I mentioned in the device manager.
Download the appropriate bit via drivers from this thread: http://forum.xda-developers.com/showthread.php?t=1696621
You can also enable the weird comneon suspend device and the 7 acm cdc usb com ports by using that little script in thread above in case you don't have access to the 7284 or 9090 menus like me.
You want to use the one that says USB MODEM.
Then you need to extract the drivers to a folder. Then after that you need to extract the files from the msi.
I used the latest unofficial version of uniextract for that.
Now go into the VIA_USB_MDM directory and edit the VIA_USB_MDM.inf file
Basically you want to create 7 different lines in there for each one of your ports.
What I did was edit the BC.MDM line and replace it.
There's 3 sections in my inf file. You want to replace the all the BC.MDM lines with several.
Like so:
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_0a
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_08
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_06
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_04
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_02
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_00
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_0c
After modifying the driver, I right clicked on each unknown device, clicked on update driver software, then clicked on locate driver software manually.
Enter the full path to the VIA_USB_MDM folder, then click ok.
It should create a BR-something modem complete with a com port.
I used realterm to open each port at various baud rates and typed AT
into each port and checked for any response.
There was one port that gave strange responses back, so I thought that might be the right port, but it was actually the next port I tried that gave correct responses back.
And there you have it, AT command access to the modem.
But keep in mind, this is not direct access to the modem. It is still going through one or more hals (Hardware abstraction layers) somewhere.
The best way to talk to the modem is with ril commands or ipc commands.
You can use ipctool and logcat -b radio to talk to the modem with ipc commands.
Ril command injection is possible, but damned annoying. I recommend ipc unless there's a really good reason.
These 2 threads are really good sources of info I used to help me get this far:
http://forum.xda-developers.com/showthread.php?t=1483053
http://forum.xda-developers.com/showthread.php?t=1471241

[Q] Xperia Z into Diag Mode

I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area

qew204 said:
I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area
Click to expand...
Click to collapse
Hmm, I don't know.
But tell me more about it or link me to a thread. :laugh:

Nexus 4 Diag Mode
I tried the su -c 'setprop usb.sys.config diag,adb' command in the android terminal and nothing happen when I plugged it into the computer.
I'm wondering if the command would be different for the Xperia Z.

qew204 said:
Nexus 4 Diag Mode
I tried the su -c 'setprop usb.sys.config diag,adb' command in the android terminal and nothing happen when I plugged it into the computer.
I'm wondering if the command would be different for the Xperia Z.
Click to expand...
Click to collapse
Hey.Have you found out how to put it to diag mode?

fil925 said:
Hey.Have you found out how to put it to diag mode?
Click to expand...
Click to collapse
No, never really worked. I think that Diag mode may only be for the Nexus 4

qew204 said:
No, never really worked. I think that Diag mode may only be for the Nexus 4
Click to expand...
Click to collapse
have you tried connecting through bootloader because it should be connecting as modem.I wound but i can't unlock bootloader

Diag Mode for XPERIA ZL
I have tried as well with Sony ZL,
setprop persist.sys.usb.config diag,adb
Nothing happened while connecting the device, no new hardware detected for COM port
Appres=ciate please your help as I need to connect to QXDM, QPST
thanks
BR
Samir

qew204 said:
I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area
Click to expand...
Click to collapse
Open ADB console and type :
adb shell
su
setprop persist.usb.eng 1
source : http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
i follow thread above but cant get the diag driver for C6603 so QXDM wont work..

Question Regarding the removal of /dev/diag Interface of SM-G998U(Qualcomm Chip)

Hello, everyone
I am trying to collect DM information through Qualcomm diagnostic kit(/dev/diag) on SM-G998U device.
However, in the currently uploaded open source(G998USQU4AUF5), the contents of /dev/diag are deleted.
Is the Diag Interface changed to something else? Or does the latest device not support Diag Interface?
I hope someone can help me out.
Thank you

[HELP] Lg v40 Verizon Diag Port Mode issue.

Hi I am using LG v40 Version on Hovac 3.8 Custom Rom (Android 10) , rooted with Magisk. I Am trying to Put phone to Diag mode to get it recognized by Qfil to repair its imei. I have tried Services code method , Adb command method as well as terminal command method but my cell is not being recognized as Diag 901d port. Any leads?

Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?

FLAmbuRNE1 said:
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
Click to expand...
Click to collapse
only verizon roms doesnt have imei write protection (idk about A10 but for Pie its working)
if you imei on v40 already null you can try this guide
but use v40 verizon rom
on verizon rom for diag mode enable try this hidden menu code ##7764726405 and hit the call button type service code 000000

All guides seem to point towards the device being called HB-USB Diag 901D in the device manager.
I feel like this is a critical step towards being able to write protected NV items.
Trying to connect to the phone using QXDM tools does not work since the phone isn't recognized as being in Diag mode.
I've tried soooo many ways at this point but don't want to give up just yet.
Let me know if anyone has any luck in getting V40 to correctly connect in Diag mode - or prove to me that diag mode is achieved with the hidden menu (I don't see it working for me - guide me in case I'm misunderstanding something).
FLAmbuRNE1 - I stand corrected - via experimentation.
I was not seeing any ports change in Device Manager or any other application after issuing the
Code:
setprop sys.usb.config diag,adb
command as a super user or after enabling the diag port from the hidden menu.
QFIL's QCN Backup+Restore functionality kinda indicated that these commands do indeed make a difference. When QFIL Restoring QCN on my phone I noticed that QFIL was unable to reset the phone after sending data to the phone - unless I had done both of the above steps. As soon as I did, it would be able to restart my phone and verify that restore was completed.
I have some additional experiments on the way to try and figure out the exact memory locations in
Code:
modemst1, modemst2 & fsg
to modify and flash in order to restore my original IMEI. Fingers crossed...
I'll circle back here with what I find, or don't find. If I don't follow up, anyone interested, message me.

setprop sys.usb.config diag,adb
not work
C:\adb>adb shell
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
flashlmdd:/ $ su
flashlmdd:/ # setprop sys.usb.config diag,adb
flashlmdd:/ #

[GUIDE] VoLTE & VoWIFI for Xiaomi 10T/10T Pro 5G custom roms

Hi all,
I would like to write a short instruction about getting VoLTE and VoWIFI to work on a Xiaomi device. I'm using a Xiaomi 10T 5G with Evolution X, but it has mainly to do with the modem in your device, so it might work for other devices and ROMs as well. If you use a different ROM, the way DIAG mode is enabled might be different for you.
Code:
/*
* I am not responsible for bricked devices or any damage you made
* to your device. You have been warned
* Your are making changes to your modem's firmware. Make sure you
* have a backup!
*/
You have to enable VoLTE and VoWIFI in your device settings.
To check if it works:
- dial *#*#4636#*#*
- chose phone information
- chose in the menu IMS-servicestatus
You will have VoLTE and VoWIFI if it says registered and availabe.
If not, you can continue with the instructions below:
You will need a few things for this, like:
- Qualcomm USB Drivers
- QPST
- Root or another way to enable diag mode
- ADB
- Xiaomi firmware zip file
You can find many tutorials on XDA about these things, so I'm not going into detail about how to set this all up.
If you have the above installed and working:
Open a command prompt
Code:
adb shell
Code:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
After you install QPST search in winodws for PDC (a yelllow and white icon) and open it.
Select 'Qualcomm HS-USB WWAN adapter'. (if this doesn't work, check if you've installed the Qualcomm USB Drivers correctly)
You'll now see a list of all modem configuration files. Check if your carrier is in the list. If so, right click on it, select SUB0 and SUB1, and click 'activate'. Check if VoLTE and VoWIFI works, if yes, reboot and check again.
If you do not see your carrier in the list, download the firmware for your device.
Extract the zip file
Navigate to \firmware-update\NON-HLOS.bin and extract this file
Navigate to \firmware-update\NON-HLOS\image\modem_pr\mcfg\configs\mcfg_sw\generic\ and search for the .mbn file for your carrier. Mine was in fw_apollo_miui_APOLLOGlobal_V14.0.1.0.SJDMIXM_2e94304468_12.0\firmware-update\NON-HLOS\image\modem_pr\mcfg\configs\mcfg_sw\generic\AF\Vodafone\Commercial\EG
Go back to PDC and chose 'load'
Select the .mbn file you've found above
PDC will reload the list and you'll now see the profile for your carrier.
Right click on it, select SUB0 and SUB1, and click 'activate'. Check if VoLTE and VoWIFI works, if yes, reboot and check again.
Now go back to adb and write
Code:
setprop sys.usb.config mtp,adb
to go back to default usb settings.
This should do the trick. You'll now have VoLTE and VoWIFI working.
It took me days to come down to this, with a lot of Google-Fu and very helpfull XDA topics. So I hope it might help you as well.
This has been tested for Vodafone Egypt, mbn for Vodafone EG has been attached (extracted from latest global firmware V14.0.1.0.SJDMIXM), just load and activate.
reference: https://forum.xda-developers.com/t/guide-volte-vowifi-xiaomi-phone.4573331/