Related
I've been trying to follow the screenshot method with the Android SDK, but it never works. I get as far as opening the ddms tool, but my phone is never listed in there.
I've installed the JavaRE, and the AndroidSDK and the USB thing as instructed.
I tried going to Device Manager (Windows7), and updating the drivers for my phone to use the downloaded USB driver, but it won't have it, saying the best drivers are already installed (I have uninstalled, and reinstalled, and it won't accept it).
Any ideas?
I had this problem. Was something to do with my either my firewall or the tools. I updated the tools and it allowed me allow the connection for my firewall.
I have Avast Antivirus... is this anything to do with it?
No. If your trying to use adb commands for your phone and it isn't working, just update the platform-tools and see if that works. It worked for me when I did that because I couldn't get it to work initially. Am I completely wrong here?
I'm going crazy here. I'm good with all this type of stuff but nothing is working. I want to return my phone to stock so I can exchange it for a new one at verizon. I keep getting the waiting for device error in fastboot. I had this problem a lot with trying to unlock it too. I'm not sure how I ever got it to work. I've downloaded and installed the drivers multiple times and still nothing. Can someone help me figure out what I'm doing wrong please?
I'm using windows 7 64bit. The drivers aren't right in device manager.
The drivers are fishy in windows 7 64bit. Download PDA net to your computer. It will install drivers correctly. Sounds weird but it works.
Sent from my Galaxy Nexus using xda premium
I've certainly noticed that they are pretty messed up on Windows 7. Unfortunately I've already done that and it still doesn't work.
Reboot your computer and plug the phone in and let the drivers try to install automatically, worked for me.
So I installed the driver a different way and it worked fine this time. I'm not really sure why I never tried that way before or why that way worked differently but it did! Thanks for the suggestions.
In what way did you install it? I'm having the same problem and it would be nice for search purposes.
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
That is also what I did that finally worked.
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
thank you!
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...
PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
samwage123 said:
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
Click to expand...
Click to collapse
I don't know about the bluetooth drivers but indeed Android adb driver should work. So here is what I suggest.
Go to the Samsung Android Phone tab, and uninstall these 2 drivers in there, restart laptop, then go and download the ace 2 drivers from here and see if it works, ah btw let the phone connected during the whole process.
Thanks for the advice i followed your advice, uninstalled both the samsung and ADB then restarted my computer. I then reinstalled the drivers you provided with my device plugged in, while they were installing. I got the bluetooth drivers popup again, Also theres a new thing under my portable devices tab i will post more screenshots this is really boggling me :/
Also this popped up when installing the drivers to do with the bluetooth.....
looks like MTP won't work either eh? Well let's see if it's the phone or the pc
Firstly follow those instuctions to do some troubleshooting.
1) Go to http://www.microsoft.com/en-us/downl....aspx?id=19153
3) Download the file
6) Run it
7) Follow the instuctions (NextNextNextNext)
That's it, now the MTP devices should work correctly.*
(ALSO Try de-selecting usb debugging)
If this won't work then I guess it's a problem with the phone.I read somewhere in a thread that some dude with the same problem on a samsung phone did factory wipe, wiped dalvik, and installed another ROM, then the usb drivers problem got fixed.
Good luck.
EDIT: Also check this site here it seems to have solution regarding the bluetooth peripheral thing.
none of those links work It has also stopped coming up as mtp it now just says GT-I8160. Also i noticed when i start up my computer it fails to start until i unplug it and plug it in again (attached pictures)
Also there is no android adb anymore its just the samsung one.... is this right? i appreciate your help
I am also using a 64bit version of windows 7 if that makes any difference.
Have you tried connecting the phone to some other pc just to know which one is the problem?
I've ran outta ideas...well the problem seems to be with the device itself and if not then it's probably the usb port,maybe insert to another port or try your luck on google, search for something like "windows failed to recognize android phone"or smth similar. I'll do some more research and try to help y'out tomorrow
Sent from my GT-I8160 using xda app-developers app
I tried disabling usb debugging also i tried the drivers on my netbook. I am having really strange problems on there with odin i plug it in and odin wont pick it up and as soon as i unplug it it says added then removed very weird :/ thats only when the phone is in download mode....
Im thinking its either the cable or the phone. Im not sure though..
Remove all Samsung related drivers.
Restart pc
Use cccleaner to clean the registry
Reboot pc
Use the drivers that i have provided in the s advance forum in my all in one guide. Install the drivers without connecting the phone.
After the drivers are installed, turn off internet connection and then connect the phone.
Sent from my GT-I9070 using xda premium
Thanks for the new idea shaaan I have succesfully followed steps 1 and 2. But I am struggling to find your all in one guide would one be kind to link me ? I did a forum search with no luck. Also I am using a galaxy GT-I8160 would using the s drivers matter? and thanks for the help mojito0 I would like to think it isn't the cable or phone, as I have literaly owned them for 8 days (just over a week). I can always see if i can borrow another cable of my friend today though
edit: I found your all in one guide I am now going to attempt what you said
After removing all the samsung related drivers and restarting I get all these devices come up? The device is not plugged in either.
I dont know if this helps atall, but I finished doing what you said ignoring the drivers.... Then went to flash using odin, Put the phone into download mode and noticed that after a couple of seconds of being stuck on setup connection. It then says the GT-I8160 cannot start, Also the mtp and adb android driver is still displaying that yellow explanation mark :/ I am a newbie to android here and dont know the difference betwene the samsung adb and the android one as listed do they both need to be working?
Remove all the displayed devices from other devices, also remove that Samsung adb thingy and also there will be one Samsung related device in the usb section! Remove them all and then follow my steps.
As for your driver query, the drivers are universal for a specific range of devices. The driver version 2.0+ should work for all devices which were released in 2012
Sent from my GT-I9070 using xda premium
I have recently root my samsung tab pro 8.4 wifi version. Everything seems to work well, except USB connection to my windows7 desktop. I installed the latest version of Samsung usb driver (download from Samsung's web site for my device). Whenever I connect it, media device mode, the "installing device driver software" icon spins for couple of minutes, then I got the error of "Device driver software was not successfully installed" . In the detail dialog window, it says "MTP USB Device" failed with a red cross. what did I do wrong? thanks.
I have tried several different USB 2 ports on my computers. Also I have Developer mode turned on, with or w/o USB debugging checked. Nothing seems to work. Also the camera mode doesn't work either.
Did you install kies 3 from samsung?, this should install all the drivers you need.
http://www.samsung.com/us/kies/
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
dealcrack said:
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
Click to expand...
Click to collapse
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
redpoint73 said:
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
Click to expand...
Click to collapse
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
dealcrack said:
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
Click to expand...
Click to collapse
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
CuraeL said:
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
Click to expand...
Click to collapse
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
dealcrack said:
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
Click to expand...
Click to collapse
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
dealcrack said:
I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem?
Click to expand...
Click to collapse
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
CuraeL said:
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
Click to expand...
Click to collapse
I download this tool, and remove all Samsung or Android related USB driver. Restart my computer and connect the pad it's not working. Then I uninstall the Samsung driver software, and all USB driver. Then restart and install a samsung driver from the thread about how to root my pad in this forum. Connect my pad, no luck. Still the same problem. I am about to give up.
redpoint73 said:
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
Click to expand...
Click to collapse
I uninstall my LG driver too, along with all Samsung/Android usb driver with the tool from previous reply. No luck, It still shows a MTP device with yellow "!" mark.
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
dealcrack said:
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
Click to expand...
Click to collapse
Glad you sorted it out, to some degree or other.
USB connectivity on Android devices is very tricky, at least on Windows (can't speak on other OSes). My HTC phone connects fine to my work laptop with the HTC drivers. On my home computer (also Win7) it frequently drops adb connection and I have to manually select the "generic" Microsoft drivers to make it work (and the HTC drivers never seemed to work completely right either). My Sammy Pro 8.4 seems to connect just fine to my home PC, however. So it seems its just a crap shoot what kind of connectivity you will get, really.