Confirmed working on the SPH-D700 Epic 4g, SPH-D710 Epic 4G Touch, SPH-L700/SCH-I515 Galaxy Nexus and SPH-L710 Galaxy S III
I have a DIAG script for the LG Optimus G LS970 here.
No more flashing back to Touchwiz! The following scripts enable USB Modem/Diag mode in AOSP roms(CM9/CM10/AOKP/etc). For those new to this, USB Modem mode is used to interface with Windows CDMA tools such as QPST, QXDM, DFS and CDMA Workshop. Modem mode has always been possible in stock Touchwiz roms using dialer codes. The issue has been AOSP roms not working with the modem mode dialer codes... requiring flashing back to stock TW to use it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<--------- Doesn't work in AOSP
Few examples of what modem mode could be used for:
[HOW-TO][FIX] Repair your IMEI with QPST - updated w/ info
[How To] Upload a custom PRL to your Epic Touch 4G
[CDMA] 威盛 VIA Repair and Reprogramming
You can use a script manager to run the script. Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed.
You may or may not have to unplug/plugin the usb cable after new mode is set.
Samsung Epic 4G SPH-D700
Use in terminal emulator/adb or add to script.
**As of Oct 1, 2012... all SPH-D700 CM10 builds have working diag mode via *#*#8778#*#* menu thanks to bbelos. Script is not longer needed on those roms.**
**The SPH-D700 script below is confirmed working on the official TeamEpic CM9 builds**
Modem
Code:
echo MODEM USB > /sys/class/sec/switch/usb_sel
PDA
Code:
echo PDA USB > /sys/class/sec/switch/usb_sel
Samsung Epic 4G Touch SPH-D710
E4GT is working but being picky. If not detected in QPST correctly... connect phone to USB cable. While phone is in normal USB PDA mode open up QPST Service Programming > Server > Stop QPST Server. Now run the CP script(or run the commands in terminal emulator as SU) then pull out the USB cable then put it back in. Wait a second.. you should see a serial port being detected in Windows Device Manager. After port has been added and drivers installed.. go back to QPST Service Programming and enable the QPST Server. Your device should now be detected properly. If you disconnect your phone while QPST Server is running you will have to toggle it off/on again for the phone to show back up.
CP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
CP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
ALL (AP+CP)
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo ALL > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy Nexus (Sprint/Verizon)
Script works great for me on my Sprint Gnex. Varied reports about script working on Verizons. If script fails use terminal emulator instead.
MODEM
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo MODEM > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
PDA
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo PDA > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy S III (Sprint/Verizon/US Cellular/AT&T/T-Mobile)
Use the script!
DIAG+ADB
Code:
#/system/bin/sh
# sets DIAG mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo diag,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
MTP+ADB
Code:
#/system/bin/sh
# sets default USB mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo mtp,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
Samsung Galaxy S IV (Should work on ATT, Tmo, Sprint, Verizon, Cricket etc...)
DIAG+ADB
Code:
#/system/bin/sh
#reboot phone to disable
#enables diag mode
echo "0" /sys/class/android_usb/android0/enable
echo "04E8" /sys/class/android_usb/android0/idVendor
echo "685D" /sys/class/android_usb/android0/idProduct
echo "diag,diag_mdm" /sys/class/android_usb/android0/f_diag/clients
echo "hsic" /sys/class/android_usb/android0/f_acm/acm_transports
echo "diag,acm,adb" /sys/class/android_usb/android0/functions
echo "1" /sys/module/ci13xxx_msm/parameters/streaming
echo "1" /sys/class/android_usb/android0/enable
Original post has been removed since this has been solved. For reference it has been moved to post 5.
Subscribed. Would love to have this feature on CM9 for the epic 4g touch.
Hi, I will try to help you as much as time allows.. But I'm easily confused as I'm trying to understand several different platforms, chipsets, models, AOS versions etc etc. So let's try to be very precise, to make sure that other people (not having an SPH-D710 or NS4G) also can benefit from this discussion. Please consider using:
(a) specific model numbers, in addition to generic names such as "SGS2".
(b) XDA-thread names/titles with posted links so that we don't have to waste time clicking on every link just to find out we have already read it. E.g. like this: "Kernel serial console on I9100".
(c) What exact steps you use to obtain a certain type of output.
Sorry for being anal about this, but it quickly gets really confusing and annoying otherwise, once you start following 30+ threads... Having said all this we can move On-Topic.
--------------------------- updated --------------------------------
[Partial re-post of PM]
Your phone is using the Qualcomm QSC6085 baseband processor, which means that your SPH-D710 is basically completely different from the GT-I9100. Thus it is most likely that the chips used (MUX) to interface with mUSB are also different, and if they are not, they must surely be wired differently to accommodate the modem chipset. The resistor values mentioned is valid for most Samsung phones using the FSA9280A mux, for other devices I have no idea, but given the laziness of Samsung they may still be implemented in various other ways..
Many issues with AOS, is with file-permissions. Another is that you may need to reboot, before certain settings take effect. Third is that there are internal mux's used/controlled by baseband with the +CMUX AT-command (and others). But one thing is for sure, Samsung doesn't want their service people to waste time with all this hacking. So yes, USB service mode (to talk to and tune the modem) via USB cable must be available somehow...
autoprime said:
While in AOSP we have no modem access. via computer or through the phone itself.
Click to expand...
Click to collapse
THAT is exactly what I find strange. You see on both my I9000 and I9100 when you connect your phone without using "modem" (as you put it), it still enables the (virtual-serial-usb) modem interface as an additional device. If I use the PhoneUtil menu to change USB to MODEM, I loose normal connection since windows ask to install proper drivers (referring to 7-CDC.) I don't know what that driver is or where to get it. (In fact it may already be present on my computer as part of the multiple driver CDC that was installed with first time use of Kies.) But perhaps need to be pointed to again, for activation...
For example, on a Vista machine the drivers are located under:
../Program Files/Samsung/USB Drivers/25_escape
There's a bunch of files located there, but the most relevant ones (for me) seem to be:
Code:
ssuddmgr.inf --> Install USB Device Management Serial Port Driver SSUD.DeviceDesc = "SAMSUNG Mobile USB At Command Port "
ssudmdm.inf --> Install CDMA USB Modem device driver SSUD.DeviceDesc = "SAMSUNG Mobile USB Modem"
ssudmdm.cat* -->
Do you also have these or are the ones you use different?
looking at my drivers.. they were indeed pulled from a Kies install and it is using those same drivers. Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem. Viewing Logcat while performing the *#*#8778#*#* PhoneUtil toggle shows no action being performed. And manually setting the mode to Modem via "echo MODEM> /sys/class/sec/switch/usb_sel" only kills the USB detection entirely.
... just the appropriate drivers for Diag mode itself. My computer can see all other phones in diag mode...
Click to expand...
Click to collapse
Which are these?
The very same ones you've mentioned establish a successful "Modem" connection to PC when using Stock Touchwiz on the SPH-D710.
Click to expand...
Click to collapse
Please post the output of:
Code:
# cat /sys/kernel/debug/usb/devices
# ls -l /sys/bus/usb/drivers/cdc_svnet
"No such file or directory" for both. The folder structures seem to be different.
Click to expand...
Click to collapse
Also, it is very important to understand that the ServiceMode application is actually running just as a wrapper for the real code, which is usually running in the baseband. This where all the hardware (MUXes, USB, i2c interfaces etc) are specified, that is used to communicate with modem. However, this may be working differently on your BP, and may be instead done in the RIL libraries, etc.
------------ Final PM Response --------------
Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem.
Click to expand...
Click to collapse
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?
2) In fact, unless you know for sure that your phone contain some (or the same) type of USB/UART switch IC (aka MUX) as in the I9100, there is no reason to expect you to have this "switch" functionality.
3) The USB drivers can do much of this virtual switching magic in software (by themselves). But really I have no clue how those things work in detail! Like I mentioned there are 7 "drivers" doing various ****, that is installed with Kies... How, and under what circumstances these are activated and used, is beyond me. (Or better, you can read how USB ports are activated on Wikipedia and about USB composite devices (CDCs) here.)
4) If you're still convinced that you need to do this switch, there is one more trick. You can try to use this tool (thanks to KickerTom in this post) to list the contents of your /mnt/.lfs/param.blk file, in readable format, or in hex-format with:
Code:
# hexdump -C /mnt/.lfs/param.blk
(You'll need busybox to do this.)
You can use that tool to write and change stuff as well, BUT: Make sure you have a full backup!! The .lfs partion is not writable in the same manner as other types of partitions. It can only "grow", and never get smaller... AFAIK.
KickerTom further states:
From my experiments it looks like the SWITCH_SEL parameter is ignored by the HW, at least I haven't observed any real effect. But you can change the UART switch by modifying a file next to the param.blk, /mnt/.lfs/sw_sel. It contains an ASCII number, by default 1. That is modem uart. Change it to 3 to get PDA uart connected, by e.g. "echo -n 3 > /mnt/.lfs/sw_sel". 5) You may need to reinstall the "Qualcomm USB Host Driver"...
Autoprime, you don't get the mass appreciation, but for those of us who know what you are trying to accomplish, we appreciate it.
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Everything between the lines was originally in the OP as part of the unsolved, [Q] Enabling USB Modem(Diag) Mode on Samsung CDMA Devices w/ AOSP thread.
Currently on the Epic 4G Touch SPH-D710 we are not able to put the phone into USB Modem/Diag mode while using an AOSP rom. This is normally toggled through the PhoneUtil apk with *#*#8778#*#*. To this date, the fix has been to restore back to a stock Touchwiz rom or to boot a Touchwiz rom off the SD card. To my knowledge, outside of the Nexus S 4G(SPH-D720), no CDMA Samsung AOSP roms have USB Modem mode working. This thread is being created to help solve this issue.. for ALL SAMSUNG CDMA DEVICES. Modem/Diag Mode works on HTC, Motorola, LG.. it should work for Samsung devices too
USB Modem/Diag Mode establishes a serial-over-usb connection which allows us to use special Qualcomm tools like QPST and QXDM to talk to our phones. We can access the hidden EFS partition including the non-volatile memory to edit all sorts of values.. we also use this for updating PRL's.. etc etc. It has it's value.. although Samsung and the carriers don't want us in there
I see USB Modem mode in AOSP being possible in two ways.
1. Since the Nexus S 4G(SPH-D720) on Sprint is on AOSP and has working USB Modem/Diag mode.. figure out how the NS4G achieves this mode.
2. Use a hardware jig of some sort to boot into USB Modem/Diag mode.
1. For the software side of things here's some highlights I've come across..
a. Logcat of Nexus S 4G(SPH-D720) while toggling USB Modem/USB modes - http://pastebin.com/TfcSHzYB
b. In terminal emulator/ADB we have "radiooptions" command with some interesting output. QXDM Enable/Disable is what interests me in there. QXDM enable would seem to allow the phone to interface with QXDM.. QXDM requires a USB Modem(Diag) Connection to talk to the phone. Attempting the "radiooptions 3" command does nothing(even on the NS4G). Only command that does seem to work is Radiff which requires a reboot to get working again.
Code:
0 - RADIO_RESET
1 - RADIO_OFF
2 - UNSOL_NETWORK_STATE_CHANGE
[B] 3 - QXDM_ENABLE
4 - QXDM_DISABLE[/B]
5 - RADIO_ON
6 - SETUP_PDP apn
7 - DEACTIVE_PDP
8 - DIAL_CALL number
9 - ANSWER_CALL
10 - END_CALL
c. Use manual commands to enable/disable the USB Modem/Diag mode as TheBeano has shown us here in his Fun with resistors (home/car dock mode + more) thread.
You can see what the current state is with this command:
Code:
cat /sys/class/sec/switch/usb_sel
You can change the state with:
Code:
echo PDA> /sys/class/sec/switch/usb_sel
or
echo MODEM> /sys/class/sec/switch/usb_sel
Currently on the E4GT SPH-D710 enabling MODEM and then connecting the device to Windows results in no connection/USB detection at all. Phone is detected in PDA mode only. In addition, using the PhoneUtil menu(*#*#8778#*#*) and setting the USB mode to "Modem" has no effect at all.
2. As for the hardware side of things, I've been reading through XDA and came across some interesting threads in the SGS2 I9100 forums. A post by E:V:A specifically that mentions putting the phone into different modes by using resistors.. which I suppose would be the same thing as the jig's people have been using to reset their ODIN flash counts.. only using different resistors: Kernel serial console on I9100.
301K looks to be what we use for the standard jigs. that is documented here: [GUIDE] How to Make a USB Jig and Get Rid of Yellow Triangle+ODIN Counter reset. I wonder if there is a mode we can force which establishes USB Modem mode ON and then use serial-over-usb.. like how it works when we set Diag mode in touchwiz roms. AdamOutler has thread dealing with the E4GT pinouts etc.. not sure if this would help at all: Processor datasheets required(E4GT SPH-D710)
Code:
xOM_0=pin E3
xOM_1=pin D2
xOM_2=pin C3
xOM_3=pin E4
xOM_4=pin F2
xOM_5=pin A3
xOM_6=pin F3
I have no idea if anything I've said helps... just putting some ideas out there and hopefully get some people who DO actually know this more advanced stuff to join in I have HTC phones, LG phones, multiple Samsung devices.. Epic(SPH-D700), NS4G(SPH-D720), E4GT(SPH-D710). I can provide any logs needed for those devices.
Random references to Diag mode and AOSP on CDMA devices:
Cannot enter Sprint ## CDMA codes on dialer, need DIAG mode! (HTC AOSP DIAG)
Updating PRL on CM7 (Samsung CDMA AOSP)
Epic Dialer Codes working on CM7
DIAG ##3424# using an AOSP ROM CM7 (Various CDMA HTC methods mentioned)
QPST DIAG Mode CM7 Aka ##3424 (HTC Droid Incredible ADR6300)
Fun with resistors [home/car dock mode + more] (Manually enable/disable UART)
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
E:V:A said:
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?....
Click to expand...
Click to collapse
It seems the more we compare notes.. the more we see how different the I9100 and SPH-D710 really are. Without getting into technical specifics I can give you a reason why some things are so different... which is how CDMA and GSM differs really. Looking at "security" alone.. GSM uses a SIM card to authenticate on the network.. outside of the IMEI(which seems to be rather accessible on your devices) the SIM card contains most of info the network is looking for. On our devices CDMA devices, ALL of the authentication info is stored on the device itself. Carriers/Manufacturers do NOT want use touching the hidden EFS partition.. where all of our authentication values reside.. ESN/MEID, EVDO username/passwords, PRL.. etc etc. So now, the main key to accessing this hidden partition... USB Modem(Diag) Mode!
I have taken some screenshots of Windows Device Manager. Far left is my Device Manager with no phone plugged in. Middle is phone plugged in but USB Mode is set to "PDA". Right side is phone plugged in and USB Mode set to "MODEM".
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
I hope this sort of explains why our phone may be "locked down" a bit more due to how CDMA works... and also explains how I am sure that we need this USB Modem mode toggled.. and that I am positive Windows is set up properly etc etc. The issue is that we can not force the phone, while using an AOSP rom, into this diagnostic serial mode.
^^ Very good. I understand. Now, can you reproduce the middle picture for your E4GT?
autoprime said:
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
Click to expand...
Click to collapse
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
E:V:A said:
Now, can you reproduce the middle picture for your E4GT?
Click to expand...
Click to collapse
Yes, the exact middle picture is produced on the E4GT. USB Composite and USB Mass Storage Device both show up. When toggling the PhoneUtil from PDA to Modem.. no changes in Device Manager happen. Tried toggling the UART selection in PhoneUtil as well just to see what would happen... no change as well.
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
That's what I've been trying to tell you guys all along, and I understand my message have not been very clear. This is because I don't quite understand how this works, but that is kind of the whole point with using a USB "Composite Device". The mere fact that you are using adb and can use Kies, is good enough for you to have several virtual (including serial) connections. I already posted a link above, about this. Did you read it?
Also in the middle picture there is an additional icon that is not present in the other two, "Portable Devices". You should run a USB sniffer (eg. USBlyzer ) to find out what happens when you connect, both with the Nexus S and your E4GT.
In addition, what you have marked as "not what we want" in the RHS picture, may in fact be exactly what you want. Because I'm getting more convinced that your Qualcomm tools (from 2006) are seriously outdated. It may just be a matter of updating some drivers, but who knows...
autoprime said:
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
Click to expand...
Click to collapse
Yes, on any stock GB ROM, ##8778#, select All to have both modes enabled (AP and CP will result in just one of the modes being enabled). Haven't tested on ICS.
Any progress??
I'm sure getting the touchwiz ics source code once we get an official ota will greatly help this project.
Sent from my SPH-D710 using XDA
E:V:A said:
Any progress??
Click to expand...
Click to collapse
there are /mnt/.lfs files in touchwiz only.. they are missing in AOSP. AOSP file structure seems to be much different. I believe the issue is a lack of "Diag" code in the AOSP code itself. We need to figure out the code in the Creso4G source(Nexus S 4G SPH-D720) which allows diag mode to be enabled and port it to our own device.
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
^^ That is very good news! But I wish you could have been more specific in what drivers you found and/or installed, and what instructions you followed? (Also, what is the model number of that phone?)
gondo77 said:
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
Click to expand...
Click to collapse
was this a touchwiz based rom.. or a aosp based rom?
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
NiteSnow said:
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
Click to expand...
Click to collapse
Prompts for msl, then gives a modem exception error on CM9 for e4gt.
Sent from my CM9 Epic 4g Touch using Forum Runner
SU PM enable com.samsung
I executed command disable com.samsung ot to get OTA FF18 updates since I am rooted. Then without thinking when to the google store and it told me that the background data was and it gave me an option to ok to turn it on.
Ever since them I can not get to play store it tells me I am not connected but I am . Try to do a able com.samsung command but returns disable.
any suggestions?
thnaks
I am running FF18 rooted stock
COM port not detected
EPIC 4G on stock EC05
All drivers installed
the phone goes into diagnostic mode but does not get detected.
is there any other way to get the phone to connect in CDMA ws ?
Phone was detecting on COM port earlier until i mistakenly uploaded
the Galaxy S3 SPH-L710 NV Item file which i had save from my Galaxy S3.
Instantly i lost my carrier signal and lost connection from CDMA ws.
i rebooted to check. did ##8778# goes to phon utils but even if i select MODEM under USB the modem is not
detected in COM port. just to check if my Drivers were correct or not, i connected my Galaxy S3 in Diagnostic mode..
the phone is detected under COM port but not my EPIC
I Odin back to Stock EC05 and tried without & with root. the phone is not detected on diagnostic/service mode. its detected
on PDA.
Need help to reset the phone so that i can get the phone to work on CDMA ws.
Related
Just to resume a lot of questions regarding this subject. There is a list of steps to get your 3G data connection shared with yout PC via USB for each device.
--== HTC HD7 ==--
1. Download XAP file
2. Download the HTC USB Modem drivers
3. Deploy XAP file to your phone
4. Turn off your Data connection in your phone.
5. Run DFRouter and click on “HTC Modem”
6. If you only downloaded driver package just unzip to any folder, then Open Device Manager (recommended for Win7 64bit).
7. Find USB\VID_0BB4&PID_0EFF&REV_0000&MI_01 and force update driver with HtcUsbMdmV64 (inside unzipped folder)
8. Find USB\VID_0BB4&PID_0EFF&REV_0000&MI_00 and force update driver with HtcVComV64 (inside unzipped folder)
9. You will get two new device HTC USB Modem and HTC Diagnostic Interface (COM8)
10. Connect device to PC, open HTC USB Modem and select Advance Label
11. Add below command +cgdcont=1,”ip”,”APN”
(APN = Your carrier’s APN)
12. Create a new connection with HTC USB Modem, diag number is *99# and disabling IPV6
13.Just connect without user name and password.
============================================================
--== Dell Venue Pro ==--
1. Download the HTC USB Modem drivers
2. Edit both HtcUsbMdmV64.inf and HtcVComV64.inf files from the extracted drivers replacing the HTC device IDs with VID_05c6&PID_3199. Leave the &MI_00.
3. Go to EM(##634#), and go to Service Center, swithcing to Composite Mode. The password is *#301#.
4. After the fone reboots, install the 2 modified device drivers as you would do in HTC tutorial.
4. Continue following the HTC guide from step 9.
============================================================
--== Samsung WP7 Devices ==--
1. Download Samsung USB Drivers and install it
2. Dial ##634# then press the Call button
3. On diagnosis screen, Dial *#7284# and press Call button
4. A “Microsoft USB Test” screen will show up which allows configuration of USB Path Control settings (options available is Zune Sync; Modem, Tethered Call; and Modem, USB Diag). Select Modem, Tethered Call. The phone will restart and activate the setting. Windows will detect and install the driver from the device. A phone modem named Samsung Mobile Modem will be installed.
5. Now you can create a connection dial-up on your windows as step 9 in HTC HD7 tutorial.
============================================================
--== LG WP7 Devices ==--
1. Download LG USB Drivers and install it
2.Launch the LG phone dialer, and dial ##634#, then press the Call button to bring up a list of applications under the screen title of “MFG”.
3.When asked to input password, enter 277634#*# to unlock the password-protected MFG.
4.Turn off the data connection in Settings -> Network Mobile.
5.Start MFG and go to the USB Switching option in Menu Engineer -> Port Setting.
6.Select the QC COMPOSITE and validate.
7.The phone will automatically restart to activate the setting.
8.Connect the phone to PC with a USB cable.
9.Windows should automatically detect the Windows Phone 7 and install driver from the device. A phone modem named LGE CDMA USB Modem will be installed.
10.Edit or configure the LGE CDMA USB Modem settings or properties, and add in additional parameter in the string (change APN for your APN name):
+CGDCONT=1,"IP","orange"
11.Manually create a new dial-up connection that uses the LG USB modem with phone number to dial as * 99 # as HTC HD7 tutorial.
============================================================
While tethering via USB, the synchronization with Zune software may not be working. In this case, just disconnect the USB cable and connect over Wi-Fi connection to sync up with Zune software. And the disclaimer is that the hack violates most mobile carrier’s terms of service, and may cost users a lot of money for overage charge if they’re on limited data plan.
Also, I didn't tested all devices cause I just have a HTC HD7 and all information here was a compilation from some blog bosts I found over the web. I hope moderators can stick it somewhere so people can stop creating new posts regarding this subject 'cause I'll keep this post updated and, when the WIFI/BT/Cableless tethering comes UP, I'll update it here.
I hape it help. Enjoy it.
Best regards...
Gutemberg
thanks this is great but we need internet connection sharing over usb, bt, or wifi
when our carriers can see us dialing up and charge us, well that is just not right
and i will not stand for it, nor will i pay for it lol
megagprime said:
thanks this is great but we need internet connection sharing over usb, bt, or wifi
when our carriers can see us dialing up and charge us, well that is just not right
and i will not stand for it, nor will i pay for it lol
Click to expand...
Click to collapse
Yep, I still working on figure out how to do this. If there is a way to open a socket on the phone and listen on some ports, I can quickly do that.
Also, you will only be billed from your carrier if you dont have a illimited data plan. At least, I'm not charged from nothing and run just fine.
Thanks a lot for compiling all this information and getting it to us. One question though. Do you have to update drivers on each pc you want to tether with? Also, think the link to the HTC USB Drivers is wrong
I've been following this thread for two days now (in the HD2 WP7 forum, http://forum.xda-developers.com/showthread.php?t=922000) but so far I'm not able to get my HD7 going with 3G tethering (always return error code of 692 despite me having to turn off the data connection in phone and having forced update the two drivers from HTC Sync for Android).
See if anyone else can get it going on HD7...
same here cannot download the second file...
kwill said:
Thanks a lot for compiling all this information and getting it to us. One question though. Do you have to update drivers on each pc you want to tether with? Also, think the link to the HTC USB Drivers is wrong
Click to expand...
Click to collapse
Yes, every PC that you are connecting the phone, you will need the USB driver. And sorry about the link. I already fixed it.
eeeeeh said:
I've been following this thread for two days now (in the HD2 WP7 forum, http://forum.xda-developers.com/showthread.php?t=922000) but so far I'm not able to get my HD7 going with 3G tethering (always return error code of 692 despite me having to turn off the data connection in phone and having forced update the two drivers from HTC Sync for Android).
See if anyone else can get it going on HD7...
Click to expand...
Click to collapse
Weird... I'm replying to you right now from my device connection...
galvesribeiro said:
Yes, every PC that you are connecting the phone, you will need the USB driver. And sorry about the link. I already fixed it.
Weird... I'm replying to you right now from my device connection...
Click to expand...
Click to collapse
In my modem log, I'm getting the following:
01-27-2011 13:44:30.317 - Opening Modem
01-27-2011 13:44:30.317 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-27-2011 13:44:30.317 - Initializing modem.
01-27-2011 13:44:30.327 - DSR is low while initializing the modem. Verify modem is turned on.
01-27-2011 13:44:30.327 - CTS is low while initializing modem.
01-27-2011 13:44:30.337 - Send: AT<cr>
01-27-2011 13:44:32.350 - Timed out waiting for response from modem
01-27-2011 13:44:32.350 - The modem failed to respond to the initialization command, Retrying one more time
I've already put the extra initialization command into the modem advanced properties, under "Device Manager", and properties of the "HTC USB Modem"..
Maybe the format of my string is something wrong? I'm using this:
+cgdcont=1,"IP","mobile.three.com.hk"
eeeeeh said:
In my modem log, I'm getting the following:
01-27-2011 13:44:30.317 - Opening Modem
01-27-2011 13:44:30.317 - 115200,8,N,1, ctsfl=0, rtsctl=1
01-27-2011 13:44:30.317 - Initializing modem.
01-27-2011 13:44:30.327 - DSR is low while initializing the modem. Verify modem is turned on.
01-27-2011 13:44:30.327 - CTS is low while initializing modem.
01-27-2011 13:44:30.337 - Send: AT<cr>
01-27-2011 13:44:32.350 - Timed out waiting for response from modem
01-27-2011 13:44:32.350 - The modem failed to respond to the initialization command, Retrying one more time
I've already put the extra initialization command into the modem advanced properties, under "Device Manager", and properties of the "HTC USB Modem"..
Maybe the format of my string is something wrong? I'm using this:
+cgdcont=1,"IP","mobile.three.com.hk"
Click to expand...
Click to collapse
Okay, just to report back, it is now working properly. After some messing around - by not enabling (unchecking) the dial-up properties of IPV6 (so left with IPV4), connectivity went through flawlessly.
thanks everyone!
Awesome.
i have dialed up with my cell before (through windows on my htc diamond) and i was charged. telus sucks yes i know. i have not tried with my lg optimus but i bet they can see...
whats my telus APN name?
+cgdcont=1,"IP","telus" ???
ill test this and report back
The APN field is you APN name configured on your device. Not the APN Address.
In my case here in Brazil it is "TIM CONNECT FAST" so my command should be +cgdcont=1,"IP","TIM CONNECT FAST"
galvesribeiro said:
The APN field is you APN name configured on your device. Not the APN Address.
In my case here in Brazil it is "TIM CONNECT FAST" so my command should be +cgdcont=1,"IP","TIM CONNECT FAST"
Click to expand...
Click to collapse
sp.telus.com
=)... WORKS MINT!!!!
, will report if charged when telus updates my data usage/billing info
eeeeeh said:
Okay, just to report back, it is now working properly. After some messing around - by not enabling (unchecking) the dial-up properties of IPV6 (so left with IPV4), connectivity went through flawlessly.
thanks everyone!
Click to expand...
Click to collapse
Good! Let me update with this results
I'm stumped. Tried the APN address, the APN names, with data on/off, with APN in the cellular settings and without, IPV6 off etc. and nothing. Perhaps it's a T-Mobile US problem? Because I've tried the APN names "T-Mobile" and "T-Mobile US" and still get the 692 error...Any suggestions?
Ok. Now this is weird. I did nothing differently except I accidentally clicked USB Sync before I clicked HTC Modem on DFRouter and the connection went through. Hmm...
Success
Finally i got it working on my HTC-HD7 (Windows 7 x64 Prof).
The one thing a would like to add is I configured the "PPP" settings in the adapter settings (let ony LCP checked) but i don't think this was the breakthrough.
After some play-around in settings (PPP on pc for example, disable Wifi/Wlan on phone) I managed to get the Error "668" instead of "692", also data connection was disabled. Restarting the phone made it work!
Just make sure to have the right driver installed and restart your phone after disabling the data connection that helped for me!
Remember to disable IPv6.
I use the "*99#" number and +cgdcont=1,"ip","internet"
for o2 germany apn
Edit: Let the default COM port.. I didn't change the COM port and it works now.. If you changed then delete the devices from device manager and start from the beginning
good luck
reddragon
how is everyone dialing *99#? are you calling using your computer or your dialpad on WP7's?
t-mobile us settings hd7
alright after a lot of hours trying here and there i finally set up my connection from tmobile hd7 usa.
on the advance tab (to get there after installing the drivers and device on usb modem mode go to to device manager then modems then right click usb modem then properties then advance tab) put there copy and paste +cgdcont=1,"IP","wap.voicestream.com"
then go to settings on your phone, celullar, data connection off, go down add apn
apn
wap.voicestream.com
username
(blank)
password
(blank)
then
Add A New Internet Connection
Close the Phone and Modem Options and the Control Panel.
For XP: Create a new connection with Start -> Connect To -> Show all connections -> Create a new connection.
1. Click Next
2. Select "Connect To The Internet" then Next
3. Select "Set up my connection manually" then Next
4. Select "Connect using a dial-up modem" then Next.
For Vista: Create a new connection with Start -> Connect To ->
1. Set up a connection or network
2. Choose a connection option: Click on "Connect to the Internet (Set up a wireless, broadband, or dial-up connection to the Internet."
3. You are already connected to the Internet - Click on "Set up a new connection anyway"
4. At "How do you want to connect?" Click on "Dial-up"
5. Check only the Standard Modem (if prompted).
6. Give the connection a name such as "BlackBerry Modem", then Next.
7. On the next screen, pick one of the following phone numbers, depending on your carrier:
....If you use GSM/Cingular/AT&T/TMobile/SwissCom: Enter phone number *99#
8. Click Next.
If you use T-Mobile:
.........Username: (blank)
.........Password: (blank)
.........Note: In USA, you can leave both blank
9. click properties
ppp settings
ckeck only lcp extensions.
restart the phone at this point with usb disconnected then when the phone restarts connect usb
open your dial up connection and click connect.
hope this helps
thank u.
lemonspeakers said:
how is everyone dialing *99#? are you calling using your computer or your dialpad on WP7's?
Click to expand...
Click to collapse
You dial with your computer, where you set up the dial up connection.
Aditionaly for everyone with 32Bit Systems (like me...) who have troubles finding the drivers, take these from this post:
http://forum.xda-developers.com/showpost.php?p=10949837&postcount=78
It got it to work with my HTC Mozart 7 and german provider "BASE".
Now I'm curious how this is charged by the provider..... hope this is covered by my dataconnection flat.
C~
T999 - pertinent replies are appreciated.
Dialed *#197328640# > UMTS > COMMON > DIAG CONFIG >
Code:
DIAG CONFIG
[1] USB ( )
[2] UART (*)
[3] DBG MSG ON (*)
[4] DBG MSG OFF ( )
Select the 1st option to switch it to USB and it comes back with:
Code:
USB_Diag Selected
Change Complete.
If You change Uart or USB diag
Please reboot the mobile.
Then, use Settings Key and select "Back" the USB is NOT selected.
Any ideas on how to get it switch to USB?
Tried the diag scripts but they don't enable it either. +those scripts are only for users not on TW (right?).
I've searched quite a bit for a while now with no luck. Need answer(s) specific to this phone as most solutions etc. including some of the USSD codes (eg. *#9090#) that work on other SGSIII don't necessarily work on T999.
The phone is still sim/network locked. Stock ICS 4.0.4 UVLH4 / Insecure Kernel / Rooted and busybox installed.
c'mon, someone's gotta have an answer to this...
I'm on the same boat now. I cant get it to switch to USB.
anyone ever figure this out???
Can you give a little more background ? What is the original problem that led you to try this solution ? Also what happens when you connect to a PC ? Does the MTP come on ?
After that second message about reboot, don't use back button do reboot.
try: menu >> key input >> 1
*#7284# ............ *#0808#
:fingers-crossed:
Here is what I’ve done to manually update the PRL on my new G2. I don’t want to debate the reasons for this. But here’s one way to do it without rooting.
NOTE: This method, to obtain your MSL, only works on the the ZV8 and ZCA software versions. They changed something in ZVC and later versions.
Note: The easiest way to get MSL/SPC code is to just dial ##443336772# on your dial pad and you don't even have to be rooted.
Note: SPC is your MSL. They are the same things.
Note: All this was done on Windows 7-64 bit.
Part 1, Connecting the phone in diagnostics mode:
Install USB drivers. http://www.lg.com/us/support-mobile/lg-LGD801BK. Use the Tmobile D801 USB drivers since it is the same as the AT&T drivers and the LS980 page only had directions to update drivers via the LG Mobile Tools.
On the phone, enable USB debugging in developer options (tap the build # in Settings > About Phone > Software Information, 7 times to enable developer options).
Dial ##Diag# (##3424#) enable diagnostics mode.
Connect phone, select "charge only"
Check windows device manager to see if you have a com port. It should be listed as “LGE AndroidNet USB Serial Port (COMxx) (xx=port #).
Part II, Get your SPC/MSL:
Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
Open Basic Flasher, password is oriax123.
In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)” and ensure the COM port on the drop down menu next to the "Scan" button matches the COM port listed in the display section (see attached screen shot). If it does not, manually select the correct COM port in the drop down menu that matches the LGE device.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG"
F. Click “Read SPC”. The SPC field should populate with your SPC.Note: Stop here and disable the DIAG mode (dial ##3424# and select disabled) if all you want is your SPC/MSL.
Part III, Update your PRL:
Click the “…” next to the PRL field and browse to the file location of the PRL you want to load, select the PRL. In Basic Flasher:
A. Click the “Send SPC” button. The dialog will show “Device Unlocked”.
B. Click the “Provision” button. The dialog will show that the MDN, MIN and SID have been written and the phone will reset.
C. On the phone, go to Settings > About Phone > Status and see if it shows you new PRL number.
D. On thee phone dial ##3424# and disable the DIAG mode.
I was also able to connect the phone to DFS (after getting my MSL with Basic Flasher). But didn’t have success writing the PRL in DFS. I used this 16 digit password EBB4EDB0B8B8C2BD in DFS. It reported “Device Unlocked” but if I tried to write anything in DFS the com port would lock up. Not sure what the issue there is, perhaps it would work if rooted.
Listing of Sprint PRLs along with descriptions http://forum.xda-developers.com/showthread.php?t=1880781.
rich_e said:
Listing of Sprint PRLs along with descriptions http://forum.xda-developers.com/showthread.php?t=1880781.
Click to expand...
Click to collapse
Thanks for sharing the steps. Did you have any problems enabling diagnostics mode prompting for SPC?
Dial ##Diag# enable diagnostics mode. * Newbie Post. If phone is not activated first, SPC will be prompted.*
dryw00d said:
Thanks for sharing the steps. Did you have any problems enabling diagnostics mode prompting for SPC?
Dial ##Diag# enable diagnostics mode.
Click to expand...
Click to collapse
Nope, no problem with accessing the menu.
When i first tried, it was showing the COM in basic flasher, now adb has installed and now i can't get COM showing so i can't access the info for my MSL
I can't get this thing to scan for my device. I have the adb drivers installed already but when I try to Scan in Basic Flasher tool, it keeps telling me "No Device Found". I even opened up a command prompt with adb and did a "adb devices" query and my device shows up.
Anyone else having issues or advice or what to do?
Slightly off-topic, is there a good way with ROOT to get your MSL? For some reason, getprop ril.MSL doesn't work in Terminal...
droidjosh said:
When i first tried, it was showing the COM in basic flasher, now adb has installed and now i can't get COM showing so i can't access the info for my MSL
Click to expand...
Click to collapse
Mine shows the ADB interface and the com port in device manager too but not having any issue finding the com port in Basic Flasher. Maybe uninstalling and re-installing the drivers would help.
WhiteZero said:
Slightly off-topic, is there a good way with ROOT to get your MSL? For some reason, getprop ril.MSL doesn't work in Terminal...
Click to expand...
Click to collapse
I added a step to set method field to "LG" before clicking the Read SPC button. I just noticed that I forgot that step when I repeated the process for the screen shot and got an SPC error with it set to "NV". Try reading it again, can think of any reason why it wouldn't work with root.
ericdabbs said:
I can't get this thing to scan for my device. I have the adb drivers installed already but when I try to Scan in Basic Flasher tool, it keeps telling me "No Device Found". I even opened up a command prompt with adb and did a "adb devices" query and my device shows up.
Anyone else having issues or advice or what to do?
Click to expand...
Click to collapse
If you don't have the com port listed under device manager it won't work. You have to be in diagnostics mode (dial ##3424#) and have the USB connection on the phone set to "Charge only" for the ports to show up.
rich_e said:
Mine shows the ADB interface and the com port in device manager too but not having any issue finding the com port in Basic Flasher. Maybe uninstalling and re-installing the drivers would help.
Click to expand...
Click to collapse
I've uninstalled and reinstalled multiple times. still won't show it. It did the first time, before windows downloaded drivers when i plugged the phone in.
rich_e said:
If you don't have the com port listed under device manager it won't work. You have to be in diagnostics mode (dial ##3424#) and have the USB connection on the phone set to "Charge only" for the ports to show up.
Click to expand...
Click to collapse
I finally got it to work. I didn't have Diag mode enabled. I guess I totally skipped Part 1. However for Part II your procedure needs some additional steps. Suggested revision of your steps. Let me know if you like and if so maybe add that to the OP.
Part 2, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)”.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
ericdabbs said:
I finally got it to work. I didn't have Diag mode enabled. I guess I totally skipped Part 1. However for Part II your procedure needs some additional steps. Suggested revision of your steps. Let me know if you like and if so maybe add that to the OP.
Part 2, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)”.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
Click to expand...
Click to collapse
I made the changes to the OP as recommend. Thanks!
rich_e said:
I made the changes to the OP as recommend. Thanks!
Click to expand...
Click to collapse
A few more slight changes in bold based on feedback from people that had some difficulty when trying out this procedure in Part 2.
In part 1, I updated the link and reference to the USB drivers to use the AT&T/Tmobile LG G2 drivers since they are made for the LG G2 vs. referencing Sprint Optimus G LS970 drivers. I personally use the Tmobile D801 LG G2 USB drivers for the LG G2 and it works fine on the Sprint model.
Part 1, Connecting the phone in diagnostics mode:
1. Install USB drivers. http://www.lg.com/us/support-mobile/lg-LGD801BK. I used the Tmobile D801 USB drivers since it is the same as the AT&T drivers and the LS980 page only had directions to update drivers via the LG Mobile Tools.
2. On the phone, enable USB debugging in developer options (tap the build # in Settings > About Phone > Software Information, 7 times to enable developer options).
3. Dial ##DIAG# (##3424#) enable diagnostics mode.
4. Connect phone, select "charge only"
5. Check windows device manager to see if you have a com port. It should be listed as “LGE AndroidNet USB Serial Port (COMxx) (xx=port #).
Part II, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/show....php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)” and ensure the COM port on the drop down menu next to the "Scan" button matches the COM port listed in the display section. If it does not, manually select the correct COM port in the drop down menu that matches the LGE device.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
ericdabbs said:
A few more slight changes in bold based on feedback from people that had some difficulty when trying out this procedure in Part 2.
Click to expand...
Click to collapse
Thanks again! I've seen people having problems with the drivers and the default behavior of the program to start with the lowest numbered com port. I hope these changes will make it easier for people to get their MSLs.
rich_e said:
Thanks again! I've seen people having problems with the drivers and the default behavior of the program to start with the lowest numbered com port. I hope these changes will make it easier for people to get their MSLs.
Click to expand...
Click to collapse
Thanks for updating the OP. Although I notice it says in the OP ##Diag# (##3434#) instead of (##3424#).
Btw I took your guide and made a sticky on another forum but made the instructions more generalized.
http://s4gru.com/index.php?/topic/5022-easy-method-to-obtain-your-msl/
ericdabbs said:
Thanks for updating the OP. Although I notice it says in the OP ##Diag# (##3434#) instead of (##3424#).
Btw I took your guide and made a sticky on another forum but made the instructions more generalized.
http://s4gru.com/index.php?/topic/5022-easy-method-to-obtain-your-msl/
Click to expand...
Click to collapse
I fixed the typo. Thanks for the cross-post and credit too!
rich_e said:
I fixed the typo. Thanks for the cross-post and credit too!
Click to expand...
Click to collapse
No problem since your guide has helped many folks obtain their MSL and I was able to verify that this method works to get my MSL. I am all for helping my Sprint brothers and sisters access their MSL to triband LTE testing.
If you are curious I did some B41 LTE testing last night and posted some screenshots in this thread below:
http://forum.xda-developers.com/showthread.php?t=2524824
I also did some further B41 LTE testing today on another tower and I almost hit 60 Mbps!!!!! Talk about making use of that Clearwire 2.5 GHz spectrum.
Deleted, found out you have to turn off anti virus to let this through, boy is this easy to use :good:
It is a very newbie question, what is the advantage of updating PRL, will I get more signal and speed on the different Roaming, at work I don't have any signal if update it to verizon Roming PRL, will I get good signal, please help me to find out.
thanks for your help.
I posted this as a reply on another thread, but as hard as it was for me a figure out a workaround for diag mode that doesn't involve the dialer codes, or trying to force the hidden menus with shortcut apps. If you don't have a dialer (Not included in the factory reset, for some odd reason...) there is seemingly NO WAY to get diag/modem mode actually working, and connecting to DFS or CDMA tool.
For some reason, I factory reset my tab, and it allowed me to add root perms during the reset, but now I have no phone or dialer app, and even if I install the official google dialer.apk it won't register the special codes for diag/modem. I tried anycut, and the quickshortcut guy, and when I hit any of the shortcuts it'll tell me "application not found." So I'm unable to activate diag/ modem mode through the gui...
BUT i found a script for an LG phone, that actually works to enable diag/modem mode on the tab 3 (t217s).
Download Smanager (script manager) from the play store.
Make sure you have root access (option when you factory reset, poot, towelroot... etc...)
PHP:
#!/system/bin/sh
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 631B > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo tty > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag,diag_mdm > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
Create a new script with this, and make SURE YOU CLICK "SU" when you save to run the script with root access. It will setup modem/diag mode, but it will require the LG drivers, because it is expecting that venid/devid.
You can get them here if you don't have them.
cdmatool .com, it's the "LG Electronics driver.zip" package.
(It won't let me post an actual link because I'm a new member)
After I ran the script, I didn't need to even unplug/plug the tablet in order for it to connect to diag mode.
NOTE:
You could change these two lines to pertain to drivers that are more compatible with the hardware in the galaxy tab 3, but it seems to work fine regardless.
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 631B > /sys/class/android_usb/android0/idProduct
I guess let us know if you try changing the vendor/devid to a different, more applicable set of drivers. If it seems to have better functionality, I'd like to know. This script with the LG drivers works for everything I've tried in DFS/CDMA ws, so if anyone encounters problems (presumably from the different drivers) please let me know.
Now, get out there and flash some tabs!! And please let me know what other carriers you can flash to. I'm curious if it's possible to switch to another CDMA network and simply disable to RIMM/SIM card.
Hi guys,i have lg g3 ls990 running prime gsm v8 stock rom and i want to enable some 3g and 4g network bands with dfs cdma tool.But i have problem with diag mode,i enter the command for enabling
(echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable)
And when i unplug and replug the phone nothing happens same as i have nothing changed but i think that diag is enabled when i go the directory where the command is navigating and open "diag_enable" file there is "1" which means enable,so what is the problem what am i missing,can some of you guys help me please.
If you guys want we can do it directly on my pc with team viewer or some other app like that ofc i take full responsibility if anything happens.
You must be rooted and type:
Code:
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Don't disconnect your device, otherwise you should repeat the process