hey everyone,
first of all this is my first post and im new to this so please bear with me
I just bought a T-Mobile SGH-T889 Samsung Galaxy Note II running on Android 4.1.1 with build # JRO03C.T889UVALJ1
I am having some troubles connecting my phone to my computer via the the included usb cable
whenever I connect try to connect my phone to the computer, it would search for updates to install drivers but it would always say that the driver software was not installed due to no drivers found. from what I understand, they should be Samsung drivers but for some reason, mine says:
Qualcomm CDMA Technologies MSM X No driver found
Qualcomm CDMA Technologies MSM X No driver found
I did several searches on the forums but have yet to find a solution or driver for my phone. please help!
I have looked into this thread but the driver provided for the root kit is for Samsung V 1.5.9.0
Thanks!
Welcome to the forum!
I'd say to try uninstalling any Samsung drivers from your pc, then restart it. Go to the Samsung site and download the latest USB drivers. The ones provided in the kit usually work, and I'm not sure the ones on the site are any newer.
Once that is done, if you are still having problems, try a different USB cable.
Sent from my SGH-T889 using xda app-developers app
I had similar issues all I did was Change to another USB port.
Also I did a complete shutdown of the PC & phone not just a reboot.
thanks for the quick replies
I have tried several times or rebooting both the phone and the computer after installing the drivers but to no avail...
I have also tried changing to all the different usb ports on my computer but still no luck
I will try to find another cable in the house to see if that will work.
Will the samsung usb drivers work though? because i have tried those several times, the ones from the root kit as well as the ones from the samsung website but it still doesnt detect it. Are there qualcomm drivers available?
some other information that I forgot to mention earlier, I am running Windows 7 64-bit
sometimes when I connect the phone to the pc, it would load up this driver --> Qualcomm HS-USB Modem 9004 Driver
but then when i disconnect it, it wont detect it again...
a solution im thinking is maybe i should reset the phone to factory default settings? would that help?
For whatever reason, your pc is not recognizing the phone correctly. Can I ask, have you installed drivers for another phone on that pc in the past? What flavor of Windows are you running? Are you up-to-date? Have you tried disabling your firewall temporarily? Finally, try booting up in safe-mode and connecting the phone. That should let you see what it thinks your phone is when no drivers are installed.
Sent from my SGH-T889 using xda app-developers app
I had a Blackberry before but I had already removed all the software and drivers for it before getting the note 2 and I am currently running Windows 7 Home Premium 64-bit and they are up to date. I will try disabling my firewall and safe mode once i get home.
I re-read the tool-kit instructions and noticed i missed something. Am I supposed to put the phone into download or recovery mode before connecting the USB to the computer (after installing the USB drivers)?
I will have to try that once i get home as well... but I still dont understand why it shows up as qualcomm drivers instead of Samsung drivers
anyways thanks for the suggestions I will let you know how it turns out.
This problem is likely due to Samsung's USB cable, as noted in other threads.
Change the usb cable before trying anything else....
ok so i got the drivers to install finally...what i did was boot the phone in to download mode then connect the phone to my computer via usb cable and it worked...but for some reason it doesnt detect it when i launch the rootkit it does not detect my serial number
If i restart my phone normally, and then try to detect the phone again on the computer it will not detect it and goes back to saying the qualcomm CDMA technologies MSM is missing drivers again...
So the only way for it to detect the drivers is in download mode but i cant seem to get the rootkit to detect my phones serial number
1ns0mn1a said:
ok so i got the drivers to install finally...what i did was boot the phone in to download mode then connect the phone to my computer via usb cable and it worked...but for some reason it doesnt detect it when i launch the rootkit it does not detect my serial number
If i restart my phone normally, and then try to detect the phone again on the computer it will not detect it and goes back to saying the qualcomm CDMA technologies MSM is missing drivers again...
So the only way for it to detect the drivers is in download mode but i cant seem to get the rootkit to detect my phones serial number
Click to expand...
Click to collapse
EDIT: another question...so once i have the drivers installed, am i supposed to reboot the phone back normally (not download mode) for it to detect the serial number?
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
I was trying to transfer some files to my phone through a USB cable today, but the phone was not recognized by the PC at all (Even though it was working a week or so ago). I had some issues before with the cable needing to be still in a certain position or it would disconnect from the PC, so I tried using another USB cable which didn't work either (I tested both USB cables with another device, and both cables were working and the other device was recognized by the PC).
I also updated the USB drivers on my PC with the official drivers on the ASUS support page, and tried putting my phone in fastboot and recovery mode, but both were still not being recognized by my computer. My phone still charges properly, but I am wondering if the USB port got damaged somehow so that it can't connect to a PC anymore?
pyroshroom said:
I was trying to transfer some files to my phone through a USB cable today, but the phone was not recognized by the PC at all (Even though it was working a week or so ago). I had some issues before with the cable needing to be still in a certain position or it would disconnect from the PC, so I tried using another USB cable which didn't work either (I tested both USB cables with another device, and both cables were working and the other device was recognized by the PC).
I also updated the USB drivers on my PC with the official drivers on the ASUS support page, and tried putting my phone in fastboot and recovery mode, but both were still not being recognized by my computer. My phone still charges properly, but I am wondering if the USB port got damaged somehow so that it can't connect to a PC anymore?
Click to expand...
Click to collapse
uninstall and reinstall the drivers. Ensure that phone is not connected during the process.
also have you upgraded your pc os ? if yes then its a little cumbersome to get the same working...
i changed from stock to cm, it is showing well now ... using RR now
Is your phone encrypted? If so you need to unlock in order for your pc to recognize it.
Thank you both of you for the help, unfortunately, my phone was not encrypted so there was no need to unlock in order for it to be detected. Uninstalling and reinstalling the drivers didn't work, and my PC was already on windows 10 since a few months ago. I would also prefer sticking to the stock ROM for this phone for now since they keep coming out with updates.
In addition, I tried using a USB OTG cable to see if the phone could detect the USB drive and my phone couldn't (it has worked before, and my old Galaxy Nexus could still detect it). I also tried plugging my dualshock 3 into the phone, and it also couldn't be detected (also had worked before).
It looks like it's actually a hardware issue and my only option is to RMA it now. I'll have to do it at a time when I don't need my phone as much or when I am not as busy.
PS: In case anyone else has this issue in the future, quick charging also no longer works
zenfone2 I also experienced that, and I have tried several ways, but remains unchanged. I was dizzy today :crying:
I have no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.