Qualcomm Cdma Usb Modem Driver
I've got ActiveSynk en it work. From thi s post: 1.
Download the attached files -----> OK 2. REMOVE SIM and SD CARDS!! Connect usb cable -----> OK 4. Copy sspl-1.16-nike.exe to your device and run it (usb cable must be connected!) -----> OK 5. After a few seconds 'USB' appears on the display -----> OK 6. Unplug and replug the usb cable -----> OK (OPTIONAL, better to skip it! If you only want to test the sspl try flashing the attached splash screen by running ROMUpdateUtility.exe from flash-splash-niki) Windows looking for USD Device driver and don't find it.
ROM Updare Utility give me ERROR 262 (cominication error) any idea? Quote: Originally Posted by marcotib I've got ActiveSynk en it work. From thi s post: 1. Download the attached files -----> OK 2. REMOVE SIM and SD CARDS!! Connect usb cable -----> OK 4. Copy sspl-1.16-nike.exe to your device and run it (usb cable must be connected!) -----> OK 5.
Qualcomm cdma free download - Multiphone GSM CDMA Sms Software, Send Sms CDMA, SMSCaster E-Marketer CDMA Standard, and many more programs. UBIQUAM CDMA USB Modem. Modem driver.
After a few seconds 'USB' appears on the display -----> OK 6. Unplug and replug the usb cable -----> OK (OPTIONAL, better to skip it! If you only want to test the sspl try flashing the attached splash screen by running ROMUpdateUtility.exe from flash-splash-niki) Windows looking for USD Device driver and don't find it. ROM Updare Utility give me ERROR 262 (cominication error) any idea?
[root@TESTPS]:~ # mknod /dev/ttyUSB0 c 188 0 [root@TESTPS]:~ # usb_modeswitch -v 1c9e -p 6061 Looking for default devices. Found devices in default mode or class (1) Accessing device 002 on bus 001. Using endpoints 0x01 (out) and 0x81 (in) Inquiring device details; driver will be detached. Kodi dlya universaljnih puljtov av10. Looking for active driver.
OK, driver found ('usb-storage') OK, driver 'usb-storage' detached SCSI inquiry data (for identification) ------------------------- Vendor String: HSDPA Model String: MMC Storage Revision String: 2.31 ------------------------- USB description data (for identification) ------------------------- Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: 02 ------------------------- Warning: no switching method given. -> Run lsusb to note any changes. [root@TESTPS]:~ # echo '1c9e 6061' >/sys/bus/usb-serial/drivers/option1/new_id In my dmesg I then see. [root@TESTPS]:~ # usb_modeswitch -W -c /usb-modeswitch-data-20110805/usb_modeswitch.d/1c9e:6061 Reading config file: /usb-modeswitch-data-20110805/usb_modeswitch.d/1c9e:6061 * usb-modeswitch: handle USB devices with multiple modes * Version 1.1.1 (C) Josua Dietze 2010 * Based on libusb0 (0.1.12 and above)!
PLEASE REPORT NEW CONFIGURATIONS! DefaultVendor= 0x1c9e DefaultProduct= 0x6061 TargetVendor= not set TargetProduct= not set TargetClass= 0xff DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 GCTMode=0 MessageEndpoint= not set MessageContent='00' NeedResponse=0 ResponseEndpoint= not set Interface=0x00 InquireDevice enabled (default) Success check enabled, max. Wait time 20 seconds System integration mode disabled usb_set_debug: Setting debugging level to 15 (on) usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device Looking for target devices. Searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1c9e:6061 found matching vendor ID found matching product ID target class ff not matching searching devices, found USB ID 1d6b:0002 No devices in target mode or class found Looking for default devices. Searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1c9e:6061 found matching vendor ID found matching product ID target class ff not matching adding device as default searching devices, found USB ID 1d6b:0002 Found devices in default mode or class (1) Accessing device 002 on bus 001. Using endpoints 0x01 (out) and 0x81 (in) Inquiring device details; driver will be detached. Looking for active driver.