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://xdaforums.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://xdaforums.com/showthread.php?t=1483053
http://xdaforums.com/showthread.php?t=1471241