[Q] HD7 Tethering "Error 692" - HD7 General

I'm beside myself trying to get my HD7 to tether.
First, I've read every post remotely related to this topic on this forum and others. Thanks to all the people in this community who have shared information on how to crack these phones, provide ROMs, troubleshooting and expertise.
I would have never gotten this far without all of your help.
I hope someone can solve this issue, because it sounds like many others have, or will have the dreaded "Error 692" problem when attempting to tether.
Some background: I'm attempting to tether a Windows 7 32-bit laptop to a T-Mobile HD7 in the US. In order to jailbreak the phone, I got an sim unlock code, then I installed one of the 7004 build ROMs from the HD7 developer's forum on this board, then unlocked with Chevron. I'm still under OS7004, with a boot loader version of 1.54.2250 and firmware 2250.09.15402.531.
I then followed the following procedure, posted on this forum and others:
//
1. Download XAP file
2. Download HTC Sync for Android from HTC for USB Modem driver
3. Deploy XAP file to your phone
4. Turn of your Data conection in your phone.
5. Run DFRouter and click on “HTC Modem”
6. Open your device manager, it will show 2 unknown device, choise device have ID is : USBVID_0BB4&PID_0EFF&REV_0000&MI_01, update your driver with HtcUsbMdm and you got HTC USB Modem.
7. Make a dial up call from your computer and set it work like other WP7 tethering from samsung or LG.
8. Click “Zune Mode” to come back with Zune Sync.
For dial up make a call *99# with mi_01 id modem. Mi_00 is diag port, maybe have some qualcomm unlock here. Don’t forget add +CGDCONT=1,”IP”,”your apn” in your advance property of modem.
//
The only variation is that I could not, no matter how hard I tried, manually install or change the two HTC modem drivers. Despite downloading them from several sources, and even trying both 32bit and 64bit drivers, I could not get windows to accept them. Even if I "uninstalled and deleted the drivers" then attempted to reinstalled the drivers for the two "Unknown Devices" I could not. Windows would not recognize the HTC drivers as being appropriate for the device. The only way I could get the HTC modem to install was using the HTC Sync software that automatically installs those drivers. By doing so, it seemed that in the Device Manager the HTC mode is installed... but there is only one device listed, the "HTC USB Modem."
In troubleshooting this, here are the things I have tried:
- Restarting the phone and machine numerous times.
- Performing all functions with anti-virus and firewall disabled.
- Yes, I have made sure the WiFi and data connection are off before connecting the USB and attempting dial up.
- I have tried the trick of selecting "USB" Sync then "HTC Modem" right before attempting dial up.
- I have tried every T-Mobile APN known to man in the initialization string.
- I have turned off "IPV6" and compression on modem settings.
- I have tried all COM ports 1-8.
- I have entered in the same APNs that are in the modem init string to the HD7's settings under cellular > Network Selection.
There are probably other things I have tried as well... if it was listed in any post on this board, I've probably tried it.
When I attempt to query the HTC Modem, the response I get is always something to the effect of "can't detect modem... make sure it is turned on." Here is a cut and paste of the log... which is always the same no matter what I seem to try.
05-14-2011 08:35:33.152 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
05-14-2011 08:35:33.153 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
05-14-2011 08:35:33.154 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
05-14-2011 08:35:33.154 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
05-14-2011 08:35:33.156 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
05-14-2011 08:35:33.156 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
05-14-2011 08:35:33.157 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
05-14-2011 08:35:33.157 - Modem type: HTC USB Modem
05-14-2011 08:35:33.158 - Modem inf path: oem19.inf
05-14-2011 08:35:33.158 - Modem inf section: Modem0
05-14-2011 08:35:33.159 - Matching hardware ID: usb\vid_0bb4&pid_0eff
05-14-2011 08:35:33.163 - Opening Modem
05-14-2011 08:35:33.163 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:33.168 - Initializing modem.
05-14-2011 08:35:33.173 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:33.173 - CTS is low while initializing modem.
05-14-2011 08:35:33.185 - Send: AT<cr>
05-14-2011 08:35:35.185 - Timed out waiting for response from modem
05-14-2011 08:35:35.185 - The modem failed to respond to the initialization command, Retrying one more time
05-14-2011 08:35:35.185 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:35.186 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:35.186 - CTS is low while initializing modem.
05-14-2011 08:35:35.197 - Send: AT<cr>
05-14-2011 08:35:37.197 - Timed out waiting for response from modem
05-14-2011 08:35:37.197 - The modem failed to respond to the initialization command, Retrying one more time
05-14-2011 08:35:37.199 - 115200,8,N,1, ctsfl=0, rtsctl=1
05-14-2011 08:35:37.201 - DSR is low while initializing the modem. Verify modem is turned on.
05-14-2011 08:35:37.202 - CTS is low while initializing modem.
05-14-2011 08:35:37.212 - Send: AT<cr>
05-14-2011 08:35:39.217 - Timed out waiting for response from modem
05-14-2011 08:35:39.220 - Session Statistics:
05-14-2011 08:35:39.220 - Reads : 0 bytes
05-14-2011 08:35:39.220 - Writes: 9 bytes
I'm sure I must be missing something simple or stupid. I sounds like windows doesn't have the drivers it needs or can't connect to the device.
Any help would be hugely appreciated... I desperately need to get this working so that I can have mobile internet access for my work.
Thanks!

Okay what worked for me was, +CGDCONT=1,”IP”,”your apn” had weird quotation marks, try re-typing the whole lines. If you have the same problem I did you'll notice the quotation marks you type are different than the quotation marks in the box, i.e. " and ”. See how the second is sorta angled?

juanfpina said:
Okay what worked for me was, +CGDCONT=1,”IP”,”your apn” had weird quotation marks, try re-typing the whole lines. If you have the same problem I did you'll notice the quotation marks you type are different than the quotation marks in the box, i.e. " and ”. See how the second is sorta angled?
Click to expand...
Click to collapse
Had same issue and re-typed quote. works a dream. thanks.

Related

mtoken vt100 terminal by cellular line

I got a problem on my new device (TyTN II), normally I working with software(mtoken 4.3.0) perfectly by Atom Life(WM6) and Dopod 900(WM5).
But after I take a new pda phone, I don’t know why it’s not working anymore.
Problem is : it’s take a long time to “Dialing (number)…” and after that “Disconnected: Line Unavailable”.
Then I try to download new v.4.3.1 Trial version and install a new one, The problem still the same.
Could you please to advise me about this, what’s the point I should focusing?
Have you asked the support people for mToken? I figuered as it was paid for software you'd be able to get tech support from them. Or are they suggesting that it's your phone's fault?!
I also gave them this question yesterday.
Now I'm waiting for their response.
Thanks for your reply and if you also get working on it, I just want to ask you something.
-Is it about the CSD Line Type?
-Or any phone setting?
Please buddy,
are you sure that you're connection to 3G /Edge /UMTS /etc is connected? Try opining an internet browser first and then try to connect the vt...
seattleweb said:
are you sure that you're connection to 3G /Edge /UMTS /etc is connected? Try opining an internet browser first and then try to connect the vt...
Click to expand...
Click to collapse
I actually want to connect via analog modem, not internet.
This is what I got from mtoken support.
"Hello,
> Problem is : it's take a long time to "Dialing (number)..." and after that "Disconnected: Line Unavailable". Then I try to download new v.4.3.1 Trial version and install a new one, The problem still the same.
It seems you are trying to connect to an analog data modem via your Pocket PC. Unfortunately, most phone carriers disable such dialup connections when they release new devices, since it can also be used to setup dialup Internet connections. If you can setup dialup Internet, it means you can bypass carrier's "data plan" and the carrier would not really want that. It's also true that most device manufacturers do not support analog data modem nowadays since most Internet users do not use "dialup" Internet settings(especially on mobile phones).
So, please first contact your device manufacturer and phone carrier and make sure your device has in fact an analog modem and it can be used to connect to another analog modem.
Hope this helps.
Best regards,
Support Team ([email protected])
Choung Networks | http://www.choung.net/"
Anybody explaine me how to setup the thing they said step by step?
Thanks again.
I have the same problem with TYTN II
I use mToken to connect via a modem to an auxiliary port on a terminal server for network support purposes.
This worked fine on my XDA Orbit running WM5 with mToken (ver 3.1.2). The SIM card is Vodafone UK.
The same SIM card in the TYTN II works fine for GPRS Internet connections but I can't get the internal analogue cellular modem on the TYTN II to work with this SIM card.
The Windows Mobile connection settings CSD Line Type that works for me on the XDA Orbit was 9600bps(V.32) and Connection element "Non-Transparent". The settings on mToken are "Cellular Line".
Exactly the same settings on the TYTN II do not work with the same SIM card. I've also tried the other available CSD Line Type's (9600bpsV.34 and V.110) and these also do not connect. I've tried mToken version 3.1.2 and the latest version 4.3.1.
I suspect this is a problem with the TYTN II.
-TyTN II-
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600
01-12-2008 10:56:27.403 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600
01-12-2008 10:56:27.403 - Modem type: Standard Modem over Bluetooth link
01-12-2008 10:56:27.403 - Modem inf path: mdmbtmdm.inf
01-12-2008 10:56:27.403 - Modem inf section: GenericCellPhone
01-12-2008 10:56:27.403 - Matching hardware ID: bthenum\{00001103-0000-1000-8000-00805f9b34fb}
01-12-2008 10:56:27.624 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-12-2008 10:56:27.624 - Initializing modem.
01-12-2008 10:56:27.624 - DSR is low while initializing the modem. Verify modem is turned on.
01-12-2008 10:56:27.624 - CTS is low while initializing modem.
01-12-2008 10:56:27.634 - Send: AT<cr>
01-12-2008 10:56:27.684 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 10:56:27.684 - Interpreted response: OK
01-12-2008 10:56:27.694 - Send: ATE0V1&D2<cr>
01-12-2008 10:56:27.704 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 10:56:27.704 - Interpreted response: OK
01-12-2008 10:56:27.714 - Send: AT<cr>
01-12-2008 10:56:27.734 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 10:56:27.734 - Interpreted response: OK
01-12-2008 10:56:27.734 - Dialing.
01-12-2008 10:56:27.744 - Send: ATDT#########<cr>
01-12-2008 10:56:28.114 - Attempting to abort current command
01-12-2008 10:56:28.114 - Send: <cr>
01-12-2008 10:56:37.097 - Recv: <cr><lf>ERROR<cr><lf>
01-12-2008 10:56:37.097 - Interpreted response: Error
01-12-2008 10:56:37.097 - Hanging up the modem.
01-12-2008 10:56:37.097 - Hardware hangup by lowering DTR.
01-12-2008 10:56:37.258 - Detected CD dropped from lowering DTR
01-12-2008 10:56:37.728 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 10:56:37.728 - Interpreted response: OK
01-12-2008 10:56:37.738 - Send: ATH0<cr>
01-12-2008 10:56:37.758 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 10:56:37.758 - Interpreted response: OK
01-12-2008 10:56:37.758 - Session Statistics:
01-12-2008 10:56:37.758 - Reads : 39 bytes
01-12-2008 10:56:37.758 - Writes: 36 bytes
ATQ0V1E0 - OK
AT+GMM - PocketPC
AT+FCLASS=? - (0)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI2 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI3 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI4 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI5 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI6 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
ATI7 - Microsoft Corporation AT Command Interpreter Settings...
E0 L0 M0 Q0 V1 X4 &C1 &D2
S00=000 S01=004 S02=043 S03=013 S04=010
S05=008 S06=002 S07=060 S08=002 S10=014
S12=050
-Another working mobile phone-
01-12-2008 11:10:15.945 - Initializing modem.
01-12-2008 11:10:15.945 - DSR is low while initializing the modem. Verify modem is turned on.
01-12-2008 11:10:15.945 - CTS is low while initializing modem.
01-12-2008 11:10:15.955 - Send: AT<cr>
01-12-2008 11:10:16.025 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 11:10:16.025 - Interpreted response: OK
01-12-2008 11:10:16.035 - Send: ATE0V1&D2<cr>
01-12-2008 11:10:16.065 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 11:10:16.065 - Interpreted response: OK
01-12-2008 11:10:16.075 - Send: AT<cr>
01-12-2008 11:10:16.095 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 11:10:16.095 - Interpreted response: OK
01-12-2008 11:10:16.095 - Waiting for a call.
01-12-2008 11:10:16.105 - Send: ATS0=0<cr>
01-12-2008 11:10:16.165 - Recv: <cr><lf>OK<cr><lf>
01-12-2008 11:10:16.165 - Interpreted response: OK
01-12-2008 11:10:17.377 - Recv: <cr><lf>RING<cr><lf>
01-12-2008 11:10:17.377 - Interpreted response: Ring
01-12-2008 11:10:19.350 - Recv: <cr><lf>RING<cr><lf>
01-12-2008 11:10:19.350 - Interpreted response: Ring
01-12-2008 11:10:20.972 - Passthrough On
01-12-2008 11:11:11.905 - Passthrough Off
01-12-2008 11:11:11.905 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-12-2008 11:11:11.905 - Initializing modem.
01-12-2008 11:11:11.915 - Send: AT<cr>
01-12-2008 11:11:13.908 - Timed out waiting for response from modem
01-12-2008 11:11:13.908 - The modem failed to respond to the initialization command, Retrying one more time
01-12-2008 11:11:13.908 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-12-2008 11:11:13.918 - Send: AT<cr>
01-12-2008 11:11:15.921 - Timed out waiting for response from modem
01-12-2008 11:11:15.921 - The modem failed to respond to the initialization command, Retrying one more time
01-12-2008 11:11:15.921 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-12-2008 11:11:15.931 - Send: AT<cr>
01-12-2008 11:11:17.934 - Timed out waiting for response from modem
01-12-2008 11:11:21.339 - Session Statistics:
01-12-2008 11:11:21.339 - Reads : 0 bytes
01-12-2008 11:11:21.339 - Writes: 9 bytes
ATQ0V1E0 - OK
AT+GMM - +CGMM: MTK2
AT+FCLASS=? - (0, 1, 2, 2.0)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - MTK2
E553_Y14AVT.01.4_26S01
ATI2 - MTK2
E553_Y14AVT.01.4_26S01
ATI3 - MTK2
E553_Y14AVT.01.4_26S01
ATI4 - MTK2
E553_Y14AVT.01.4_26S01
ATI5 - MTK2
E553_Y14AVT.01.4_26S01
ATI6 - MTK2
E553_Y14AVT.01.4_26S01
ATI7 - MTK2
E553_Y14AVT.01.4_26S01
-Modem on my laptop-
01-10-2008 11:07:59.027 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600
01-10-2008 11:07:59.027 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600
01-10-2008 11:07:59.027 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600
01-10-2008 11:07:59.027 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600
01-10-2008 11:07:59.047 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600
01-10-2008 11:07:59.047 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600
01-10-2008 11:07:59.047 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600
01-10-2008 11:07:59.047 - Modem type: ThinkPad Integrated 56K Modem
01-10-2008 11:07:59.047 - Modem inf path: oem40.inf
01-10-2008 11:07:59.047 - Modem inf section: ModemX
01-10-2008 11:07:59.047 - Matching hardware ID: pci\ven_8086&dev_24c6&subsys_055a1014
01-10-2008 11:07:59.247 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-10-2008 11:07:59.247 - Initializing modem.
01-10-2008 11:07:59.247 - DSR is low while initializing the modem. Verify modem is turned on.
01-10-2008 11:07:59.257 - Send: AT<cr>
01-10-2008 11:07:59.257 - Recv: <cr><lf>OK<cr><lf>
01-10-2008 11:07:59.257 - Interpreted response: OK
01-10-2008 11:07:59.267 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-10-2008 11:07:59.277 - Recv: <cr><lf>OK<cr><lf>
01-10-2008 11:07:59.277 - Interpreted response: OK
01-10-2008 11:07:59.287 - Send: ATS7=60L1M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
01-10-2008 11:07:59.297 - Recv: <cr><lf>OK<cr><lf>
01-10-2008 11:07:59.297 - Interpreted response: OK
01-10-2008 11:07:59.297 - Waiting for a call.
01-10-2008 11:07:59.307 - Send: ATS0=0<cr>
01-10-2008 11:07:59.337 - Recv: <cr><lf>OK<cr><lf>
01-10-2008 11:07:59.337 - Interpreted response: OK
01-10-2008 11:08:03.012 - Session Statistics:
01-10-2008 11:08:03.012 - Reads : 24 bytes
01-10-2008 11:08:03.012 - Writes: 88 bytes
ATQ0V1E0 - OK
AT+GMM - +GMM: ThinkPad Integrated 56K Modem
AT+FCLASS=? - 0,1
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - +GCI: B5
AT+GCI=? - +GCI: (00,01,02,03,04,05,06,07,09,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F,30,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,40,41,42,43,44,45,46,47,48,49,4B,4C,4D,4E,4F,50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5E,5F,60,61,62,63,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F,70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F,90,92,93,94,96,97,98,99,9A,9B,9C,9D,9E,9F,A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,AA,AB,AC,AD,AE,AF,B0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C1,C2,C3,C4,C5,C7,C8,C9,CA,CB,CC,CD,CE,CF,D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7,E8,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F7,F8,F9,FA,FB,FC,FE)
ATI1 - 255
ATI2 - OK
ATI3 - SoftK56V_B2.1_V7.22.00.52
ATI4 - ThinkPad Integrated 56K Modem
ATI5 - 181
ATI6 - SoftK56
CModem Version 12
Rksample Version 342
ATI7 - 255
Any idea, mate?
Thanks and Regards,
zoggo said:
I use mToken to connect via a modem to an auxiliary port on a terminal server for network support purposes.
This worked fine on my XDA Orbit running WM5 with mToken (ver 3.1.2). The SIM card is Vodafone UK.
The same SIM card in the TYTN II works fine for GPRS Internet connections but I can't get the internal analogue cellular modem on the TYTN II to work with this SIM card.
The Windows Mobile connection settings CSD Line Type that works for me on the XDA Orbit was 9600bps(V.32) and Connection element "Non-Transparent". The settings on mToken are "Cellular Line".
Exactly the same settings on the TYTN II do not work with the same SIM card. I've also tried the other available CSD Line Type's (9600bpsV.34 and V.110) and these also do not connect. I've tried mToken version 3.1.2 and the latest version 4.3.1.
I suspect this is a problem with the TYTN II.
Click to expand...
Click to collapse
I don't like this sound absolutely.
That's mean I just waste my money with mtokenless pda phone.
Anybody help me check this AT log file, maybe can make an idea for you.
TyTN II CSD Analogue Modem problem
TyTN II AT Log extract:
-----------------------
01-12-2008 10:56:27.734 - Dialing.
01-12-2008 10:56:27.744 - Send: ATDT#########<cr>
01-12-2008 10:56:28.114 - Attempting to abort current command
01-12-2008 10:56:28.114 - Send: <cr>
01-12-2008 10:56:37.097 - Recv: <cr><lf>ERROR<cr><lf>
01-12-2008 10:56:37.097 - Interpreted response: Error
01-12-2008 10:56:37.097 - Hanging up the modem.
01-12-2008 10:56:37.097 - Hardware hangup by lowering DTR.
01-12-2008 10:56:37.258 - Detected CD dropped from lowering DTR
------------------------
Looking at your above log there isn't much to go on regarding the error received. I notice there's no ATDT command in the two other logs you posted - I assume you've removed these from the logs for security purposes and edited the above one with ####### for the same reason.
Having done some extensive google searches I've not found any evidence that anyone has managed to get the analogue CSD modem in the TyTN II working. I've also tried taking the mToken application out of the equation by defining an analogue dial-up Internet modem connection over ppp to my ISP using the Windows Mobile connections settings. This also exhibits the same behaviour - the modem does not establish a connection. This setup works perfectly on my other XDA Orbit PDA (WM5) using the SIM from my TyTN II.
I've reported this problem to the HTC UK support desk. They are going to investigate and hope to have further information in two days.
Will let you know the outcome.
zoggo said:
TyTN II AT Log extract:
-----------------------
01-12-2008 10:56:27.734 - Dialing.
01-12-2008 10:56:27.744 - Send: ATDT#########<cr>
01-12-2008 10:56:28.114 - Attempting to abort current command
01-12-2008 10:56:28.114 - Send: <cr>
01-12-2008 10:56:37.097 - Recv: <cr><lf>ERROR<cr><lf>
01-12-2008 10:56:37.097 - Interpreted response: Error
01-12-2008 10:56:37.097 - Hanging up the modem.
01-12-2008 10:56:37.097 - Hardware hangup by lowering DTR.
01-12-2008 10:56:37.258 - Detected CD dropped from lowering DTR
------------------------
Looking at your above log there isn't much to go on regarding the error received. I notice there's no ATDT command in the two other logs you posted - I assume you've removed these from the logs for security purposes and edited the above one with ####### for the same reason.
Having done some extensive google searches I've not found any evidence that anyone has managed to get the analogue CSD modem in the TyTN II working. I've also tried taking the mToken application out of the equation by defining an analogue dial-up Internet modem connection over ppp to my ISP using the Windows Mobile connections settings. This also exhibits the same behaviour - the modem does not establish a connection. This setup works perfectly on my other XDA Orbit PDA (WM5) using the SIM from my TyTN II.
I've reported this problem to the HTC UK support desk. They are going to investigate and hope to have further information in two days.
Will let you know the outcome.
Click to expand...
Click to collapse
Thank you very much, I'm looking forward to get some from you.
Hopefully,
I have a HTC Diamond and got the same problem. Do you have find a solution to connect use the csd (analog) line?

[Q] Lost IMEI after upgrade

Hi all!
I were in the process to upgrade to 10b on my phone, but during the upgrade the phone stopped responding on upgrading S/W. Please wait. And after some time on that screen, I removed the battery and cable, and tried the different solutions provided by the LG B2C Support Tool.
After that I tried to flash the phone with smartflash and the latest software. And that worked perfectly, but now the phone has no IMEI. Have tried to install the backup I had via CWM but still no IMEI.
I was looking forward to use the 2x this easter, but if noone has a good solution in getting the IMEI back, the phone needs to go on a easter holiday to the service centre.
You did the same thing with me. When using smartflash, DO NOT check option "Erase CAL data" but I did. My SU660 now has serial number = 0000000. P990 will lost IMEI.
Sent from my LG-SU660 using XDA Premium App
I had the same problem, you need to flash the baseband firmware as it is gone.
I think that it was during updating the baseband as part of the V10b mine stopped flashing.
Look here: http://forum.xda-developers.com/showthread.php?t=1008070
It worked with mine o2x.
I managed to solve the situation.
I applied the 10b firmware using nvflash. And then flashed the 10a fw with smartflash, checked that the IMEI were back in business. And then did a new update using smartflash to 10b and now everything is back as normal
restore IMEI (From Modaco)
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Hi mohicanrat,
I tried to set 'Port Setting' -> 'CP USB', but in the device manager (i'm using win7), this device then shows up as 'Other Devices' -> 'Unknown device'.
What should I do now? Where can I get the device driver for this?
hello,
please where i go to "Start hyperterminal, in COM settings"
HyperTerminal was binned after Windows XP, if you have Vista onwards you'll need to download an equivalent.
mohicanrat said:
1. Connect phone by usb
2. Enter 1809#*990# in dialer
3. Select port settings -> select cp usb
4. Start hyperterminal, in com settings select same port like in devide manager -> lge mobile usb serial port, 115200
5. Type at if response is not ok, change port number
6. Type at%imei, it should display your current imei
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... Is your orginal imei number
8. Reset
Click to expand...
Click to collapse
thank you very much. I did as you said and finally got my imei back
thank you a million.
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
It gives error on running at%imei, might it be because phone driver not installed on windows?
at%imei
ERROR
I instaled driver from LG site LGUnitedMobileDriver_S498MA22_WHQL_ML_Ver_2.2.exe
when i type ATI4 for instance it shows same info as from log.
Here's log from modem i removed my IMEI though.
PHP:
11-26-2011 01:29:11.420 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
11-26-2011 01:29:11.420 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
11-26-2011 01:29:11.438 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
11-26-2011 01:29:11.439 - Modem type: LGE Mobile USB Modem
11-26-2011 01:29:11.439 - Modem inf path: oem29.inf
11-26-2011 01:29:11.439 - Modem inf section: LGSI.Install
11-26-2011 01:29:11.439 - Matching hardware ID: usb\vid_1004&pid_6000_modeminterface
11-26-2011 01:29:11.470 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-26-2011 01:29:11.488 - Initializing modem.
11-26-2011 01:29:11.488 - CD is high while initializing modem.
11-26-2011 01:29:11.498 - Send: AT<cr>
11-26-2011 01:29:11.504 - Recv: <cr><lf>OK<cr><lf>
11-26-2011 01:29:11.504 - Interpreted response: OK
11-26-2011 01:29:11.514 - Send: ATE0V1&D2&C1S0=0<cr>
11-26-2011 01:29:11.526 - Recv: <cr><lf>ERROR<cr><lf>
11-26-2011 01:29:11.526 - Interpreted response: Error
11-26-2011 01:29:11.527 - Session Statistics:
11-26-2011 01:29:11.527 - Reads : 15 bytes
11-26-2011 01:29:11.527 - Writes: 20 bytes
ATQ0V1E0 - OK
AT+GMM - 0
AT+FCLASS=? - +FCLASS: (0-1)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI2 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI3 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI4 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI5 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI6 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI7 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
help!!
i can connect but cant type anything in the terminal.. can anyone help .. i ve never done this before.. using win7 x64
Same Problem here....
I've the same problem
IMEI is gone
Baseband is "Unknown"
Battery shows 999%
And like the poster above me, I cant type anything in the Hyperterminal
PLS, who got his IMEI (and with this his loved Optimus) back, help us!!
Thx in advance,
sleep
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Today i was flashing LG Optimus Black P970 with SmartFlash and accidentaly i checked "Erase entire CP". In a result my IMEI has changed...
With this tutorial I managed to recover my IMEI successfully!
It took me 2 minutes and worked at first time.
i'm trying this method but not working
when type At...i get ok
but when i type imei i get error
What error? Paste screenshot or log.
What firmware version do you have in your LG?
You must type exactly this: at%imei - (% symbol is very important) it will display your current IMEI, then
at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x (, (comma) is very important too)
Hi,
I had one time that when i change ril. After backup my old ril all work fine.
I tried this method but i get "IMPL ERROR".
Stock ROM V10c
Tried to downgrade baseband from
1035.21_20110405
to
1035.21_20110315
but still same error...
Any idea?
Can you please tell me exact software version on what this method worked?
any solution for su660 i have the same problem
I expect the same thing would work.
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Anyone know how to perform this with an Optimus L3 device? Apparently i can't have acces to "Port Settings"

[Q] Motorola Milestone Custom Roms? Locked Bootloader? Howto?

Well, hello guys i bought a Motorola Milestone from a friend yesterday.
And I'm that annoying kid that will probably step on your lawn again and again, but i apologize in advance for my stupid questions that will probably come after this.
But i have been at it for about 6-7 hours googling bouncing around to you youtube.
I was up halfway through the night yesterday to find a way to flash my phone with Cyna cyanogenmod.com
And through tutorials wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
When i get to step:
9. Once it is selected, hit Start and wait for it to finish flashing the device.
10/28/11 12:18:51 New Log Started For Software Download.
10/28/11 12:18:55 00000de0 Phone.cpp 450 0 ERROR Generic failure when sending command.
10/28/11 12:18:55 00000de0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
10/28/11 12:19:01 The FlashLog key is turned off.
10/28/11 12:19:02 Multi upgrade started for 1 phones
10/28/11 12:19:02 [Device ID: 0] Flashing phone.
10/28/11 12:19:02 ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file. - on device ID 0.
10/28/11 12:19:02 ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
10/28/11 12:19:02 [Device ID: 0] Phone[0000]: Phone is not compatible with multi-interface super-file.
10/28/11 12:19:03 Multi upgrade finished.
I get this error through searching someone said it was a bug place the *.sbf file in C:\, My documents i tried that same error.
I tried different versions of RSD lite i tried patching the pst_flash.ini file.
After i got shutdown here i tried to push a recovery image through my computer using recovery.img.
adb shell
adb flash_image bla bla bla
i get the error access denied.
Is there any ****ing way to give my telephone a custom rom or change my default Androd bootloader recovery for rom managers?
After a while i found this, i tho to myself was the bootloader locked the whole ****ing time?
ausdroid.net/2011/06/14/an-update-on-motorolas-locked-boot-loader-situation/
ausdroid.net/2011/04/27/confirmation-motorola-to-unlock-bootloaders-for-future-android-devices
If some kind soul out there could spread some light on my issues i will be in your debt forever.
P.S sorry for all the f*cks D.S
The Droid and Milestone are very similar, but have important differences. The Milestone has a locked bootloader, while the Droid doesn't. When it comes to rooting the Milestone and installing a custom ROM, steer clear of instructions for the Droid. It'll get you nowhere.
http://www.droid-developers.org/wiki/CyanogenMod_4_Milestone_FAQ
http://android.doshaska.net/cm7

[Q] Cannot get root on Xperia Z1

I've been trying this for most of the day, having read everything here about doing it, and even watching the video.
Unfortunately, I let the phone update to 14.1.G.2.257, but I found the instructions on how to flash back to the previous 1.534. The flashing worked perfectly.
I am trying to use Root_with_Restore_by_Bin4ry_v32 having read how to and watched the tutorial. USB debugging is enabled, as is Unknown Sources, and the 'adb devices' command in the stuff folder of the aforementioned program lists the phone.
However, it does not seem to work. I get the following output:
Code:
C:\xpe>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.11.2013) v32 =
======================================================================
Device type:
0) Xperia Z1 14.1.G.1.534 Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 0
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
error: protocol fault (no status)
2881 KB/s (2242263 bytes in 0.760s)
error: protocol fault (no status)
error: protocol fault (no status)
133 KB/s (1230 bytes in 0.009s)
error: protocol fault (no status)
Unable to chmod /data/local/tmp/busybox: No such file or directory
Running Exploit
error: protocol fault (no status)
rm failed for /data/local/tmp/getroot, No such file or directory
error: protocol fault (no status)
error: protocol fault (no status)
Rebooting now, after reboot all should be done!
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
The phone reboots, but there is no SuperUser app. I have re-run the program many times, reflashed the stock firmware again to make sure, and banged my head against my desktop several times to no avail.
Please help...
Rick.
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
gregbradley said:
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
Click to expand...
Click to collapse
Yes thanks, USB debugging and unknown sources are enabled. Is this the screenshot you need to see?
**Edit**
I got it to work!
I just pulled out my laptop which had a clean install of Windows 7 as of a few days ago, installed the above stuff (plus ADB drivers from pdanet) on that, and it worked.
Why it didn't work on my main PC I have no idea, but it is probably an issue with some driver somewhere messing things up. I did try reinstalling all of them, but to no avail.
Anyway, got it now. Thanks!

Wi-fi and BT Failing to Start after Rooting Issues - No solutions worked till date!

Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed

Categories

Resources