Related
Hi, i just purchased a galaxy tab 10.1 and it charges fine with usb but when i plug into my PC it says MTP-Connected on the tab but first fails to install on windows than it's not detected at all, i've also tried on my mac with the android file transfer and its not detected either
Galaxy Tab 10.1 - Device not recognised
Hi,
I have the same issue, I am running Windows 7 Ultimate 64bit. This all worked last week and now it is simply not recognised. I have uninstalled all of the drivers and re-installed them again but with no luck. I am wondering if MS has pushed another dodgy update again! The Tab is at 3.1 and is rooted... does anyone have an idea why this is happening?
*checks forum section*
Umm, Im pretty sure this is the Galaxy Tab 7" section. You just might get help if you post in the correct location.
;-)
Sent from my GT-P1000 using XDA App
It's not their fault that this forum is unclearly titled, and you could be a little more helpful too.
Here's the correct forum for your posts...
http://forum.xda-developers.com/forumdisplay.php?f=1050
Edit: I've asked a mod to consider renaming the Galaxy Tab forums to something else like Galaxy Tab 7.0", like the 10" one does, to avoid further confusion.
Make sure the USB Debugging option in Applications is DISABLED. I get consistent detection as usb storage already since I turned that off.
64 bit win 7, home premium.. I downloaded the win 7 usb driver from the sticked post on the Q/A forum.. I am at the end of my rope with trying to save the files for my friends wife.. she has pictures of her kids she wants off the phone and other stuff.. I realize I could use a wifi file transfer program but I want to root this phone and put jellybean on it.. and I cannot do that without the USB working..
any help would be appreciated.. really would.. I can also give you the stats on my cpu/phone if you need.. thank you so much for any help
there are two things in my device manager called base system device.. I do not know if this is the phone or not.. any help guys.. <3
wolfxwinds said:
64 bit win 7, home premium.. I downloaded the win 7 usb driver from the sticked post on the Q/A forum.. I am at the end of my rope with trying to save the files for my friends wife.. she has pictures of her kids she wants off the phone and other stuff.. I realize I could use a wifi file transfer program but I want to root this phone and put jellybean on it.. and I cannot do that without the USB working..
any help would be appreciated.. really would.. I can also give you the stats on my cpu/phone if you need.. thank you so much for any help
there are two things in my device manager called base system device.. I do not know if this is the phone or not.. any help guys.. <3
Click to expand...
Click to collapse
I use Windows 7 64Bit and have no trouble at all. Make sure you are plugging the phone directly into a motherboard usb slot, otherwise - yes, you'll want to kill someone.
.. what do you mean motherboard usb slot.. my computer has 4 usb slots.. all of them do the same exact thing.. just charge the phone.. I have installed files for this thing left and right and no MMS, it doesn't show it on my computer.. and in device manager it says something about base system device.. their are two listings for it.. I am not sure why.. I uninstall them and they pop back up after scanning for hardware changes.. I am doing everything I can not to throw this phone in the garbage
windows update isnt finding any drives for them.. it just says failed.. not sure why..
sigh.. this is a head ache from hell.. just need someone whos had this problems advice
Dl drivers directly Samsung. I think the proper Samsung drivers end in .4.5. You could also try the drivers from the note or s3, ends in .4.6 (but that's a longshot). Make sure you have a good cable. Clean the usb port on your phone with compressed air. Check usb pins on phone for malformation.
mrhaley30705 said:
Dl drivers directly Samsung. I think the proper Samsung drivers end in .4.5. You could also try the drivers from the note or s3, ends in .4.6 (but that's a longshot). Make sure you have a good cable. Clean the usb port on your phone with compressed air. Check usb pins on phone for malformation.
Click to expand...
Click to collapse
can you directly link me to the driver? The phone charges on the usb port so I doubt its a damaged port or cable connection problem.
nevermind, it was the cable.. lol...
Use drivers from Samsung or ones posted here. Don't ever use MS's drivers! I use win7 x64 boot camp on my MacBook even and haven't had an issue. (I know it was cable, just sayin)
Sent from my SGH-I897 using xda app-developers app
So I've run into a weird issue that was happening with my Atrix HD the last few days of its life too and now over to the note on my laptop.
I know this is probably a more computer specific problem, as it's recognized on my desktop but I'm running outta ideas here so maybe someone can help?
I've been flashing and rooting and all that jazz since android was released so I know how to work it and my thinkpad was accepting mtp/android connections as recently as september. I unlocked my Atrix HD bootloader and all that but couldn't get the phone to accept the twrp so eventually I just gave up because it was just a stop gap phone.
But now with my new Note 3, I can plug the phone to the laptop and it'll charge but it doesn't bring up the MTP notification (all my androids do this now)
I've checked device manager, it's not even an unknown device in the list..so weird.
Anyone run into this issue before? I know it's not really phone specific but yeah.
thanks in advance
Are you using it on a USB 3.0 port? My home pc only recognizes mine if it's plugged into USB 2.0. Fought this same fight last night myself. Good luck.
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Do you guys have BC 1.1 enabled on your machines? If so that's why the 3.0 port doesn't work.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
to both of you, my thinkpad (for some awful reason) doesn't have usb 3.0, so no there isn't any USB 3.0 issues.
Literally plug it into my laptop, and nothing. no response from the computer at all not even in device manager, just starts charging as if the phone was plugged into a low voltage socket or something.
baffling.
works absolutely fine on my desktop, but I don't have all my adb and sdk tools set up the way I like them on there.
I have no idea.
ERR edit that it just started working :/ weirdd
Verizon note 3 here - same issue.
Do you guys have any programs that's suppose to charge devices faster with usb? It has to be software related on your laptop
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
To everyone with this problem, you have to specifically download the Note 3 drivers from Samsung
samsung.com/us/support/owners/product/SM-N900VZWEVZW
I was having the same problem, but now both Kies and manual usb file transfer work perfectly on Windows 8
I have same problem here as well ?? its not reconizing my phone in usb 3.0 and i have the newest drives as well for note 3 gn 9005
got it working
Had the same problem after trading in handset,maybe there is some kind of hardware identifier messing things up for usb?
I removed (uninstalled and deleted) drivers for usb, including for hub then reinstall hub drivers followed by reinstall driver option in Kies3 to install samsung drivers. This got everything working.
Panikos said:
Had the same problem after trading in handset,maybe there is some kind of hardware identifier messing things up for usb?
I removed (uninstalled and deleted) drivers for usb, including for hub then reinstall hub drivers followed by reinstall driver option in Kies3 to install samsung drivers. This got everything working.
Click to expand...
Click to collapse
I disable fast usb 3.0 charging in the BIOS..Now it works.
---------- Post added at 05:52 AM ---------- Previous post was at 05:51 AM ----------
pachi72 said:
I disable fast usb 3.0 charging in the BIOS..Now it works.
Click to expand...
Click to collapse
PEOPLE DISABLE FAST 3.0 USB CHARGING IN YOUR MOBO BIOS..IT WORKS FOR ME NOW>:highfive:
NOOOO its easy! thats too much work. All you have to do is dial *#0808# and click mtb+adb and that should solve the problem for everyone. If that doesn't click on something else lol but thats what I did.
Hope this helps someone :good:
Android3220 said:
NOOOO its easy! thats too much work. All you have to do is dial *#0808# and click mtb+adb and that should solve the problem for everyone. If that doesn't click on something else lol but thats what I did.
Hope this helps someone :good:
Click to expand...
Click to collapse
Your going to mess your phone up some kind of bad playing with those settings if you don't know what your doing. Also please don't recommend doing any of that without a trustworthy source because you can cause another person to mess up their phone as well.
The Note 3 does NOT support BC 1.1. That's what "Fast Charge" or whatever they call it is. Your phone will not use that connection so there is no workaround, just disable the BC 1.1 function.
Agent said:
Your going to mess your phone up some kind of bad playing with those settings if you don't know what your doing. Also please don't recommend doing any of that without a trustworthy source because you can cause another person to mess up their phone as well.
The Note 3 does NOT support BC 1.1. That's what "Fast Charge" or whatever they call it is. Your phone will not use that connection so there is no workaround, just disable the BC 1.1 function.
Click to expand...
Click to collapse
Yes I stand corrected however I always mess with these settings in order to unlock 90% of the gsm galaxy lineup. This is just a different way of mounting your phone to the computer at least that is what I was told and have been doing for a while. I have tried all the methods on the note 3 and so far no problem. I have been using my phone like this for a while without any hiccups and I had this usb problem since day one on my SAMSUNG laptop so I tried this method which worked. You can easily switch back to the same setting but once again you might be right about the messing up your phone part. FYI MTP just stands for media trasnfer protocal I think so I went with it after a little research.
Just letting everyone know what worked for me no harm done
Android3220 said:
Yes I stand corrected however I always mess with these settings in order to unlock 90% of the gsm galaxy lineup. This is just a different way of mounting your phone to the computer at least that is what I was told and have been doing for a while. I have tried all the methods on the note 3 and so far no problem. I have been using my phone like this for a while without any hiccups and I had this usb problem since day one on my SAMSUNG laptop so I tried this method which worked. You can easily switch back to the same setting but once again you might be right about the messing up your phone part. FYI MTP just stands for media trasnfer protocal I think so I went with it after a little research.
Just letting everyone know what worked for me no harm done
Click to expand...
Click to collapse
I tried installing the drivers from samsung with no luck and then tried this and no luck either. GOD DAMNIT! Why is google making it harder and harder to do this ****? Why can't it be as simple as moving files to another other usb drive like it used to be.
IT works!!it actually works..
what i did was,,download kies 3,supported kies for note 3, and go to Tools tab, and see the option "reinstall device driver" dont unplug your note 3,,and voila!!just wait a while, and see how the kies recognize ur note 3..:laugh:
Android3220 method works for me using Note 3, Windows and Kies. Thank ypu.
Panikos said:
Had the same problem after trading in handset,maybe there is some kind of hardware identifier messing things up for usb?
I removed (uninstalled and deleted) drivers for usb, including for hub then reinstall hub drivers followed by reinstall driver option in Kies3 to install samsung drivers. This got everything working.
Click to expand...
Click to collapse
Do you plug it in USB port 3.0 or in 2.0? Mine, either port are not working
Try using a USB hub,,, 2.0 or 3.0.... this will work......
Go to device manager then to USB find the Samsung driver uninstall. Plug your note 3 in then your system will see your note 3 and reinstall your drivers. Then your good to go.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Pullback said:
Do you plug it in USB port 3.0 or in 2.0? Mine, either port are not working
Click to expand...
Click to collapse
From what I remember I had tried both and neither worked before re-installing as described
My lap top does not recognize my galaxy note 3
already installed the new driver for usb drivers and for the phone
still the same issue
anybody can help
AJ.J said:
My lap top does not recognize my galaxy note 3
already installed the new driver for usb drivers and for the phone
still the same issue
anybody can help
Click to expand...
Click to collapse
couple things..
try another usb slot
if none of the usb slots work, then good chance it might be a driver issue.. id try and find another one... jsut google it or i thin some of the stickies here have links to a driver as well.. im sure its one of these 2
From my Fired-up Note Pro 12.2!
I have installed all drivers i could fine. Whenever i plug the watch into my pc it doesn't even make the chime sound, nor does the device show up in device manager.
Can someone please help me, i just got my watch two days ago and would like to enable more cores because mines quite laggy on android wear 2.0.
If you have enabeld USB Debugging ?
This you can do in the Developers Options.
If you dont see Developers Options under SETTINGs then you must first enable the Developer Options...
To do this ...
Go to SETTINGS there in Devices Info and then TAP 7 times at Buildnumber... after this go back to Settings and you see the Developers Options and there you can enable USB Debugging
Sorry for my bad english...
i have already done that also. ive tried about everything i can fine. the dock charges the watch just fine, i have also tried different usb cords. is there any way to adb over wifi?
TTGZDOG said:
i have already done that also. ive tried about everything i can fine. the dock charges the watch just fine, i have also tried different usb cords. is there any way to adb over wifi?
Click to expand...
Click to collapse
Hey did you found any solution?
I am on the same boat, the watch can charge and works (laggy) fine, but I am unable to let it be recognize in any way.
I tried same USB cord with several phones and it's ok, but the watch cannot be in any way recognized...
Someone please help us out lmao, the watch is so damn laggy and battery is awful.
I managed to do adb over wifi on the watch, but obivously this do not help with unlocking bootloader or anything in fastboot mode..
codymamak said:
I managed to do adb over wifi on the watch, but obivously this do not help with unlocking bootloader or anything in fastboot mode..
Click to expand...
Click to collapse
Did you all download and try the latest adb? I was having this same issue and turned out that once I updated the adb from the Android sdk, everything worked perfectly.
Uhm, I'll try thank you!
I downloaded all the driver I could get, even from official android.com site, but still the issue is same:
When I plug USB cable in the PC, I get no chime sound or request of anything: tried putting the watch on cradle in standard running mode, in fastboot mode, or in recovery or even powered off.
Same result: no reaction from PC at all.
Tried connecting various phones with same cable as the watch cradle usb cable, everytime the driver kick-in and phone is detected and system either use Google USB driver or ask for drivers.
I read somewhere on the internet that if phone is not connected with Wear app the smartwatch is not connected? But how to do that if the watch is in fastboot mode for unlocking?
Btw I also found that the system update was to version NXG47C and now the fastboot menù is indicating that bootloader is version LENOK22b (secure boot is enabled in green and lock state is locked).
I am lost, even the SDK Android drivers did not change a thing, but more than anything else I do not get why PC do nothing (not even chime sound) when plugging in, my cradle is original and all things come from its box from 2014..I never tried before connection so I do not know if that was working before, but I am starting to think I need a new cradle maybe...
codymamak said:
Btw I also found that the system update was to version NXG47C and now the fastboot menù is indicating that bootloader is version LENOK22b (secure boot is enabled in green and lock state is locked).
I am lost, even the SDK Android drivers did not change a thing, but more than anything else I do not get why PC do nothing (not even chime sound) when plugging in, my cradle is original and all things come from its box from 2014..I never tried before connection so I do not know if that was working before, but I am starting to think I need a new cradle maybe...
Click to expand...
Click to collapse
I have 2 cradles (that -same thing as you- work with anything else instantly) and since the NXG47C/LENOK22b combo simply do not work, so it seems it isn't a cradle problem. :crying:
Did you find anything else, codymamak?
m3ta said:
I have 2 cradles (that -same thing as you- work with anything else instantly) and since the NXG47C/LENOK22b combo simply do not work, so it seems it isn't a cradle problem. :crying:
Did you find anything else, codymamak?
Click to expand...
Click to collapse
Sadly, no.
I was just looking to cradle options but what you are reporting here now makes me believing that really, it's something else...but probably only LG knows why they did that...Only reason I can think of, is to make us users purchase newer models locking out features that make it still good with AW 2.0
It's really a pity.
My only other idea is to try with a different OS, as atm I got only Win 10 64bit Creator Update , but I could use a old HDD and try with a Win 7 32bit...but it's a LOOOOOOOOONG shot as from my experience at least the chime sound should be there...:crying:
Oh! Different OS - I forgot to mention it before, sorry: I tried on Windows 10 and MacOS.
Again, both work fine with other Android USB-debugging-active devices.
Sorry for adding more bad news to an already bad story.. :/
I would have guessed this, sadly.
Well, this means something needs to be found to reactivate the fastboot connection from the devs...meanwhile, I found that the old dev options to lower the scale of the animations improves a bit the slugginess of the watch...
Let's hope someone notices this thread and find a way to help us out, as I'm 100% no-dev...
codymamak said:
Sadly, no.
I was just looking to cradle options but what you are reporting here now makes me believing that really, it's something else...but probably only LG knows why they did that...Only reason I can think of, is to make us users purchase newer models locking out features that make it still good with AW 2.0
It's really a pity.
My only other idea is to try with a different OS, as atm I got only Win 10 64bit Creator Update , but I could use a old HDD and try with a Win 7 32bit...but it's a LOOOOOOOOONG shot as from my experience at least the chime sound should be there...:crying:
Click to expand...
Click to collapse
Exactly same thing about me. USB plugged in and nothing happen, I tried win 10 OS and win7 - same problem - I also thought it is cradle problem, I almost bought a new one but after you wrote I dont't think I could help look we are stucked with AW2.0 and only thing is hope someone will find solution for this...
I am still stuck on this situation, no way to make watch try the USB connection.
Could it be possible that the latest update disabled the USB ADB?
Can someone confirm if the USB ADB files are still in the package?
And if not, is it possible to add them back using for example ADB over wifi, through maybe the original recovery if not possible with system running?
codymamak said:
I am still stuck on this situation, no way to make watch try the USB connection.
Could it be possible that the latest update disabled the USB ADB?
Can someone confirm if the USB ADB files are still in the package?
And if not, is it possible to add them back using for example ADB over wifi, through maybe the original recovery if not possible with system running?
Click to expand...
Click to collapse
It is really anointing when some other users write about downgrade without problems. I'm thinking how is it possible, so everyone got the same version of AW2.0, it is really weird
I have 2.0 on gwr and my win 8 recognised them. I just installed adb usb drivers in same way as I did for Huatch: as Motorola android sooner composite adb interface.
Where do I find these famous motorola android sooner drivers for w7 x64?
Adambeat22 said:
Where do I find these famous motorola android sooner drivers for w7 x64?
Click to expand...
Click to collapse
Probably installed with drivers for motorola phone. The thing is I did not install this exact adb driver on purpose. I found it as I was trying out anything to make the watch connect to PC. It was a pure luck.
same thing happen to me!
I thought it was the cradle, I have 3 cradles, though all is not original, all fail. so I though the cradle only can charge. But I vaguely remember I once using it to flash, but my memory is not so reliable, so it can be the original or the 'not original'.
I can connect ADB using the bluetooth debug mode and go to fastboot, but even in fastboot mode, my pc still cannot detect the watch.