These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
What is it for?
ybregeon said:
What is it for?
Click to expand...
Click to collapse
How to install Qualcomm Drivers for people who are having trouble installing the drivers.
Just explain that you mean the PC drivers. Some might get confused and think you mean Qualcomm bootloaders in the phone.
Sent from my Lumia 800 using XDA Windows Phone 7 App
for xp??
ok i am with nokia lumia 710 and i am trying to write new os,but it wants this drivers "qualcomm cdma technologies msm" pls help,i am on xp,my phone have unlocked qualcomm bootloader
info
hi.
I succeeded in no way, unfortunately the third already does not settle. but Windows 7 64 bits of my system yes. May this be the trouble?
PnPUtil -i -a msmdm.inf (installed o.k.)
PnPUtil -i -a qcmdm.inf (installed o.k.)
PnPUtil -i -a qcser.inf (not installed, platform compatibility problem. )
i very sad! i flashed (my lumia 710 prototype rainbow rom with lumia 710 douwnloader. the rom is okay, but i have no call sound!!!! i want the original firmware . but nss not see the lumia help
Adrammelech said:
PnPUtil -i -a qcser.inf (not installed, platform compatibility problem. )
Click to expand...
Click to collapse
looks like you need x64 drivers...
Worked on x64 Windows 7. Thanks very much for this
hasn't worked for me, still shows up as drivers not installed in Device Manager. When I point towards the files it doesn't accept them or if I do a computer/internet search. Just says driver cannot be found.
Any ideas?
---------- Post added at 10:07 PM ---------- Previous post was at 10:03 PM ----------
RHodgett said:
hasn't worked for me, still shows up as drivers not installed in Device Manager. When I point towards the files it doesn't accept them or if I do a computer/internet search. Just says driver cannot be found.
Any ideas?
Click to expand...
Click to collapse
I should say I am running Windows 7 64bit.
Confirmed that work on Windows 8 dev preview and customers preview with Vista drivers (x86)
Hey, I've done the commands you gave.. All drivers installed correctly like you said.. But When I plug in my lumia 800 windows says it can't find the drivers
What can I do?
Yours sincereley,
Shabo09 said:
Hey, I've done the commands you gave.. All drivers installed correctly like you said.. But When I plug in my lumia 800 windows says it can't find the drivers
What can I do?
Yours sincereley,
Click to expand...
Click to collapse
does your phone come up as a flash disc in restore mode if it doesnt then you dont have a unlocked bootloader regardless if its a qualcomm, there were 2 versions from what i can gather one allows nand access and one doesnt sounds like you have the one that does not
rob:good:
I have problem only with the installation of this....
PnPUtil -i -a qcser.inf
When i try to install this, receive this message:
Can not install the drivers for any of the devices in the system: exhausted the available data (translated from italian)
I need only of this driver for flash, I have an unlocked NAND
OS Windows 7 x64
bombolo85 said:
I have problem only with the installation of this....
PnPUtil -i -a qcser.inf
When i try to install this, receive this message:
Can not install the drivers for any of the devices in the system: exhausted the available data (translated from italian)
I need only of this driver for flash, I have an unlocked NAND
OS Windows 7 x64
Click to expand...
Click to collapse
you dont need the drivers to flash put the phone into nand mode vol+ and power short vibration then plug usb, either flash in linux or in nss
rob:good:
moaster7 said:
These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
Click to expand...
Click to collapse
---
Hello
Does anyone know why I get the following error?
Processing inf : qcmdm.inf
Adding the driver package failed : Access is denied.
Adding at least one driver package failed!
kian1234 said:
---
Hello
Does anyone know why I get the following error?
Processing inf : qcmdm.inf
Adding the driver package failed : Access is denied.
Adding at least one driver package failed!
Click to expand...
Click to collapse
Are you the admin or have the administrators rights to install drivers.
check that 1st.
I got the same 800 with Qualcom CDMA technologies MSM ... so can I flash and full unlock my 800????
I still get Certificate issues after installing your certificate.
Start command prompt as admin and type "shutdown -o -r -t 0"
disable driver signatures
Now installed drivers fine, going to restart now hope it works
Using windows 8 x64
After installed this drivers NSS pro didnt recognize my lumia 710
before driver
when i click on "READ INFO" it answer me correct
now
Checking selection...Supported(USB) interface selected.
Init connection...Done.
----------------------------------------------------------------------
Phone details:
-----------------
NCSD Version: N/A
SW Version: N/A
HW Version: N/A
IMEI: N/A
Product Code: N/A
Basic Product Code: N/A
Module Code: N/A
Production SN: N/A
Battery life: N/A
Number of Nams: N/A
Number of Mins: N/A
ESN: N/A
ESN Decoded: N/A
PRL Version: N/A
Battery Charge Capacity: N/A
Battery Full Capacity: N/A
Battery Cycle Count: N/A
Battery Temperature: N/A
Battery Voltage: N/A
Battery State of Charge: N/A
Battery Average Current: N/A
Battery Flags: N/A
Battery Standby Current: N/A
Battery MaxLoad Current: N/A
Battery Health State: N/A
Battery Nominal Capacity: N/A
Battery Remaining Capacity: N/A
any suggestions?
regards
moaster7 said:
These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
Click to expand...
Click to collapse
seem to be having a problem while installing those inf files through cmd
getting the following message -
Adding the driver package failed : Invalid INF passed as parameter.
Total attempted: 0
Number successfully imported: 0
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Hello, I m after some help.
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
hey i try to get the ADB things to work. i was albe to make myself a developer and all i want to do its to change the resolution of my display from 2k to 1080.
if its to hard and i need to root i will wait for i want to damage my worrenty or anything leik that due to it costed to much.
i use a Huawei Mediapad M5 LTE 64Gb tablet.
i use windows 10 pro x64
the error i get when i type ADB this is
Code:
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
it seems its not installed but i dont know i tryed some problems from the site and even puged my tablet and put on usb debugging but it dont get up on any list or anything.
thanks for the help.
So I have a few of these Kramer Panels which aren't supported anymore (The official webpage doesn't have them anymore but the same product here) and I want to wipe out the Kronomeet Software they got going on and install some other flavor of Android (I'm thinking Lineage OS).
To start I got adb and fastboot up and running with Aptitude.
Code:
$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
$ fastboot --version
fastboot version 28.0.2-debian
Connecting fine with adb, and using lsusb we see
Bus 001 Device 037: ID 2207:0011 Fuzhou Rockchip Electronics Company SmartTab
Googling around that name led me to the Rockchip Wiki, which had an article on Fastboot and a bunch of open source repos
https://opensource.rock-chips.com/wiki_Fastboot
Which states: "Rockchip uses 0x2207 as its USB vendor ID. This VID is not in Google's original fastboot code. So every fastboot command has to use "-i" parameter to specify vid to fastboot."
However, running -i on fastboot gives me an invalid option error:
Code:
$ sudo fastboot -i 0x2207 devices
fastboot: invalid option -- 'i'
I also tried downloading the most recent version of the android platform tools with fastboot version 33.0.3-8952118, which gave the same results.
Doing any other fastboot command without the -i just has < waiting for any device >
So essentially, I'm trying to figure out how to load a custom rom onto it, and what my next steps try are.
Other Misc Info I've tried:
In the Developer Settings on the tablet, there's no option to enable "OEM Unlocking"
Tablet doesn't have a power button, just a switch, so no pressing power and volume at the same time.
Rockchip seems to have a TWRP image available to build, which I would like to be able to fastboot flash (https://github.com/rockchip-software/TWRP/tree/android-9.0)
There's also a development tool (https://opensource.rock-chips.com/wiki_Rkdeveloptool) that also lets you load firmware.
Using adb reboot bootloader reboots the tablet to a black empty screen, which I can then communicate with the rkdeveloptool.
In this mode, lsusb returns a new name:
Code:
$ lsusb
Bus 001 Device 038: ID 2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode
$ ./rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x320a,LocationID=106 Loader
$ ./rkdeveloptool ppt
**********Partition Info(parameter)**********
NO LBA Name
00 00002000 uboot
01 00004000 misc
02 00006000 resource
03 0000E000 kernel
04 00016000 boot
05 00026000 recovery
06 00036000 backup
07 00050000 cache
08 00090000 kpanic
09 00092000 system
10 00392000 metadata
11 0039A000 radical_update
12 003BA000 userdata
Found some more useful thread, and am trying to use rkflashkit. But still struggling to find out what .img to use.
Firmware Upgrade Guide For RK3188 RK3288 RK3368 Devices
UPD: Rreflashing guide for linux Host PC added. BEFORE START What you need: 1. Image file 2. Host PC (Windows) 3. USB OTG Cable Supported host OS: 1. Windows XP （32/64bit) 2. Windows 7 (32/64bit) 3. Windows 8 (32/64bit) All manipulations I...
forum.xda-developers.com
[Q] has anyone had success flashing a RK3126 based tablet?
Hello, I've got an irulu X30 (expro 30 plus) running stock firmware, nougat 7.1.2 I've been trying to use rkflashtool in linux and androidtool in windows. Both programs can report some device info and read partitions, the img files created...
forum.xda-developers.com