Hey guys, just got my Tab a few days ago, its unlocked and its working great. I want to root, but my PC wont recognize it (running win7) and it says the USB device has malfunctioned... wth? I searched through some threads about the drivers, and ive tried 4 different ones, restarted my PC, AND my Tab, with no luck. No, USB Debugging is not enabled. (not a noob, just, simply not working)
Any ideas? I would appreciate it
I just got my tab 3hours ago. I got it to work.
Here are what i've done
1.go to control panel and see if samsung usb driver is there. If it is, uninstall it.
2.disable usb debugging on the tab
3.connect the tab to the computer.
Thats wht worked for me. Hope it helps. And yes, samsung has really got to work on the usb thing.
Unzip and run the attached file. Delete any old unused USB device and delete any Android, Samsung or other related device then reinstall Samsung drivers.
NovaFox238 said:
Hey guys, just got my Tab a few days ago, its unlocked and its working great. I want to root, but my PC wont recognize it (running win7) and it says the USB device has malfunctioned... wth? I searched through some threads about the drivers, and ive tried 4 different ones, restarted my PC, AND my Tab, with no luck. No, USB Debugging is not enabled. (not a noob, just, simply not working)
Any ideas? I would appreciate it
Click to expand...
Click to collapse
This helped me: my computer tower has front and back USB ports. Back USB ports are directly embedded in the motherboard, front USB ports are a wire run from the case plugged into the motherboard, but the front USB ports are on a different chip.
When I first tried using the ADB debugger with Android, ADB would not even find my device if I plugged the device into the front USB ports. If I move the cord to the back USB ports, everything works properly. Maybe this is your issue?
Thanks guys, I believe I got it working.
I'm having trouble connecting my N9005 to my pc using Windows8. The problem is it does not recognize the phone's storage and is not able to mount it.
I've tried installing Samsung Universal USB Drivers to no avail.
My laptop only has USB2 ports and if I'm correct N9005 utilizes USB v3. Could it be the cause?
I also have the same problem in Ubuntu.
I also tried Samsung Kies and it doesn't work either.
Upon connecting, my PC recognizes that the phone's been connected but it's not able to mount the storage.
NoobSibot said:
I'm having trouble connecting my N9005 to my pc using Windows8. The problem is it does not recognize the phone's storage and is not able to mount it.
I've tried installing Samsung Universal USB Drivers to no avail.
My laptop only has USB2 ports and if I'm correct N9005 utilizes USB v3. Could it be the cause?
I also have the same problem in Ubuntu.
I also tried Samsung Kies and it doesn't work either.
Upon connecting, my PC recognizes that the phone's been connected but it's not able to mount the storage.
Click to expand...
Click to collapse
The Note 3 mounts as an MTP drive. Make sure you have it selected under the drive connection settings on your phone.
In some cases enabling USB Debugging in Developer Settings would allow for the USB to mount.
nicholaschum said:
The Note 3 mounts as an MTP drive. Make sure you have it selected under the drive connection settings on your phone.
In some cases enabling USB Debugging in Developer Settings would allow for the USB to mount.
Click to expand...
Click to collapse
No difference there my friend.
NoobSibot said:
No difference there my friend.
Click to expand...
Click to collapse
By any chance do you have any unknown devices listed in the Computer Management of your computer?
My Note 3 mounts normally
nicholaschum said:
By any chance do you have any unknown devices listed in the Computer Management of your computer?
My Note 3 mounts normally
Click to expand...
Click to collapse
I don't know what really happened but this last time I connected the device, it mounted normally!
But there's still an unknown Mass Storage Controller in my Device Manager.
unable to connect
Hi,
Perhaps W8 assigned the wrong driver...or a bad / damaged usb cable(?)
Try a system restore to an earlier date
I allways connect my mobile device thru wifi and it's fine
Cheers,
USB3 is backwards compatible with USB2, don't worry about that.
Did you try another cable? You can use any microUSB 2.0 cable, it fits into the right side of the USB port. (the small left bit is the USB3 part.)
Did you unlock the screen when you connect the phone? It can't mount the storage, if you use a lockscreen setting other than none or swipe, until you unlock the screen.
Send From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Hello ShadowLea,
I'm having the same problem on my Samsung Note 3 SM-N9005: "USB device not recognized One of the usb devices connected to this computer has malfunctioned...." when I connect it to my USB3 on my laptop.
I tried the toothpick solution (lifting the tongue of the USB connector on my phone), I tried powering down the Laptop and waiting for 30 seconds to fullly discharge the capacitors, I tried changing 3 different USB cables. I tried different USB ports on Laptop (on USB3 I reiceve the error on the remaining 2 USB2 ports the error does not appear but the phone is not seen by Kies nor Odin.
BTW, FYI, the phone is also having battery charging issues: it only charges if pluggged into the laptop and won't charge if connected to the mains via wall charger (tried 3 different chargers, cables, mains sockets: all work with other devices).
I'm trying to flash a new ROM to try to fix the battery chargin problem but if Odin can't recognize the device...
Also, the dial pad code *#7284# which should give access to the Phone Utility (USB settings) is not working - all other dial pad codes work.
ascanio1 said:
Hello ShadowLea,
I'm having the same problem on my Samsung Note 3 SM-N9005: "USB device not recognized One of the usb devices connected to this computer has malfunctioned...." when I connect it to my USB3 on my laptop.
I tried the toothpick solution (lifting the tongue of the USB connector on my phone), I tried powering down the Laptop and waiting for 30 seconds to fullly discharge the capacitors, I tried changing 3 different USB cables. I tried different USB ports on Laptop (on USB3 I reiceve the error on the remaining 2 USB2 ports the error does not appear but the phone is not seen by Kies nor Odin.
BTW, FYI, the phone is also having battery charging issues: it only charges if pluggged into the laptop and won't charge if connected to the mains via wall charger (tried 3 different chargers, cables, mains sockets: all work with other devices).
I'm trying to flash a new ROM to try to fix the battery charging problem but if Odin can't recognize the device...
Also, the dial pad code *#7284# which should give access to the Phone Utility (USB settings) is not working - all other dial pad codes work.
Click to expand...
Click to collapse
im having the same problem..i try to connect my note 3 via USB cable and is not reading the phone... But for me it start happening after I install the X-NOTE build 18... any Idea how to fix this? Or a link?
xganonx said:
im having the same problem..i try to connect my note 3 via USB cable and is not reading the phone... But for me it start happening after I install the X-NOTE build 18... any Idea how to fix this? Or a link?
Click to expand...
Click to collapse
Hi, I have the same problem with X-Note 18. I tried already all stuff, Odin can see my phone but Kies and any other connection option doesnt help
any update?
any update on this? having the same problem, is it due to xnote?
cussyandrew said:
any update on this? having the same problem, is it due to xnote?
Click to expand...
Click to collapse
Nope, X-Note is fine and I'm using v16 right now without problems.
What I think fixed my problem was using a screwdriver on the usb port on the phone.
I tightened the screws a little bit and it was fine after that.
NoobSibot said:
Nope, X-Note is fine and I'm using v16 right now without problems.
What I think fixed my problem was using a screwdriver on the usb port on the phone.
I tightened the screws a little bit and it was fine after that.
Click to expand...
Click to collapse
well it was working fine on xnote 13, however its been giving me this problem since i updated to xnote 18!!
---------- Post added at 04:21 AM ---------- Previous post was at 04:21 AM ----------
NoobSibot said:
Nope, X-Note is fine and I'm using v16 right now without problems.
What I think fixed my problem was using a screwdriver on the usb port on the phone.
I tightened the screws a little bit and it was fine after that.
Click to expand...
Click to collapse
which screws are you talking about btw?
ive found countless times its a duff or cheap micro USB cable.
if you have been using the genuine Samsung one then it may be faulty. But try another cable.
does any other phone connect ok with the same cable?:good:
I had a similar issue with my note 2 a while back
Sent from my GT-N7100 using XDA Premium 4 mobile app
cussyandrew said:
well it was working fine on xnote 13, however its been giving me this problem since i updated to xnote 18!!
---------- Post added at 04:21 AM ---------- Previous post was at 04:21 AM ----------
which screws are you talking about btw?
Click to expand...
Click to collapse
The ones on the USB port when you remove the back cover.
aladinliverpool said:
ive found countless times its a duff or cheap micro USB cable.
if you have been using the genuine Samsung one then it may be faulty. But try another cable.
does any other phone connect ok with the same cable?:good:
Click to expand...
Click to collapse
No it doesn't connect with any other cable, it charges fine though :/
This problem has already been addressed and solved. Its a problem in the kernel. Download a custom kernel if your using X-note 18.
Wallah, Problem fixed
Dizy801 said:
This problem has already been addressed and solved. Its a problem in the kernel. Download a custom kernel if your using X-note 18.
Wallah, Problem fixed
Click to expand...
Click to collapse
can you please provide links to theses custom kernels?.. im not sure which ones to install
moh277 said:
can you please provide links to theses custom kernels?.. im not sure which ones to install
Click to expand...
Click to collapse
Go download x-note v20. they fixed the problem.
HTML:
http://www.nonsolosmartphone.it/x-note-build-18-0-n9005-nf4-t9278.html
When I plug my note 3 SM-9005 into a USB 3 port I get the 'this device can perform faster yada yada'
There is no USB 3 in the drop down on the phone just MTP and Camera.
Using the cable that came with the phone,running JB 4.3
Ports are USB 3.0 with latest intel drivers.
MystaMagoo said:
When I plug my note 3 SM-9005 into a USB 3 port I get the 'this device can perform faster yada yada'
There is no USB 3 in the drop down on the phone just MTP and Camera.
Using the cable that came with the phone,running JB 4.3
Ports are USB 3.0 with latest intel drivers.
Click to expand...
Click to collapse
reinstalled usb3 drivers no luck
me too
Hello , I have SM-N9005 and I updated it manuly to android 5.0 and since then I have a problem with connecting it to my pc with usb ... I used diffrent usb cables and diffrent pc and laptops and the phone just charge but the pc dont requnaize the phone
Update usb driver. Turn on/off usb debugging.
Sent from my SM-N920C
Rosli59564 said:
Update usb driver. Turn on/off usb debugging.
Sent from my SM-N920C
Click to expand...
Click to collapse
I already did that but it aint working
Answers to this question are usually .
Install Samsung drivers .
Change USB cables .
Change USB port on PC .
See multiple identical posts .
i tried to install drivers on my pc but it still not recognize my phone ..
also installed smart switch still the same problem
(Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.).. windows keep saying this i cant fix it help my guys
If you are using a Usb 3.0 port switch to a 2.0. If you are unsure a 3.0 port is usually blue on the inside.
Dreadsta5889 said:
If you are using a Usb 3.0 port switch to a 2.0. If you are unsure a 3.0 port is usually blue on the inside.
Click to expand...
Click to collapse
still the same problem