Related
Hi.
Have Boostmobile Epic that came unrooted.
Downloaded drivers and phone shows in device manager under com ports.
Tried 11 USB cables then saw a video from qbking and bought a blackberry to use its cable making it 12 cables, none work.
Tried 2 computers with Vista and Win 7 x64.
Epic won't communicate with either comp with debugging on or off.
As i said in topic, one click root won't work. Says Phone is not connected.
I also cannot sideload content onto SD card because it does not show in My Computer.
It has been flashed to boost so i assume it has communicated with a PC in the past.
What can i do to fix this?
Reboot pc and phone then try again. If that doesn't work then uninstall drivers from pc then install again. Reboot pc after install after reboot plug in epic then wait for it to finish installing drivers then reboot both again then use odin.
You can also connect the phone with usb debugging on, then go into device manager on the computer and look for "other" or samsung android in USB section. Click on that and select update drivers and let windows update search and install drivers...it takes awhile.
just did the uninstall drivers then reboot both thing.
Driver installation shows device ready to use as...
SAMSUNG USB Composite Device
SAMSUNG Mobile Modem #2
SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM5)
All ready to use.
But Still not showing in my computer for file transfer or working in usb debugging mode for root.
PHug said:
just did the uninstall drivers then reboot both thing.
Driver installation shows device ready to use as...
SAMSUNG USB Composite Device
SAMSUNG Mobile Modem #2
SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM5)
All ready to use.
But Still not showing in my computer for file transfer or working in usb debugging mode for root.
Click to expand...
Click to collapse
Try the update driver choice in device manager. The CDC driver is missing. I think it loads 5 drivers if I remember correctly with USB on...yeah the mass storage driver is missing too. Let Windows update find them all.
kennyglass123 said:
Try the update driver choice in device manager. The CDC driver is missing. I think it loads 5 drivers if I remember correctly with USB on...yeah the mass storage driver is missing too. Let Windows update find them all.
Click to expand...
Click to collapse
Hi, thanks for help.
Just tried uninstalling everything and letting windows find drivers. Windows found a different driver package from S3 studio or something but I still get no mass storage or root.
I've read you can root and install roms without a computer Guess that will have to be my route.
As far as mass storage goes... It's annoying but I pulled the back off and put SD card directly into computer
You are sliding down the pulldown on your epic screen and pushing mount sd card for mass storage right?
jbadboy2007 said:
You are sliding down the pulldown on your epic screen and pushing mount sd card for mass storage right?
Click to expand...
Click to collapse
Yeah, the robot pic turns from green to orange but it never actually connects to either computer.
Going to my brothers house soon to check his 2 computers, he says his Thunderbolt will only work on one.
PHug said:
Yeah, the robot pic turns from green to orange but it never actually connects to either computer.
Going to my brothers house soon to check his 2 computers, he says his Thunderbolt will only work on one.
Click to expand...
Click to collapse
Some computers are finicky and will only work on the USB port used to install the drivers. Odin only works on the left side of my laptop and mass storage works on the right...go figure!
The fact that the phone thinks it connects and the computer probably makes the connection noise shows there is still a driver problem. Did you reboot the computer and phone after the full driver installation?
Yes I restarted both several times while installing/uninstalling
Drivers... I have just accepted that I need to remove the card to sideload content.
On a side note, I am now afraid to root my phone and change the roms because I'm on boostmobile and will be unable to connect phone to a computer to fix if something goes wrong.
Sent from my SPH-D700 using Tapatalk
after you install drivers, reboot, then plug in your phone w debugging on, it should install a bunch of drivers, then take forever on modem, unplug and replug the usb from the phone really fast, this should trip it up into moving to the next device... there should be at least two or three more. If you have GB loaded for some reason the RNDIS drivers are wonky. Make sure you use a USB port on your motherboard, not on a PCI, not on a front port... the drivers are acting weird lately, like they changed em up a bit... idunno... but once you get a setup, dont mess with it! Hope somethin helps... Its almost guaranteed the drivers, unless the Boost is the issue, idunno...
ive had that same problem ever sense ive got the phone, what if you havent given up there is another way for you to connect to your computer. It is very simple and fast it is how i connect now and it works every time.
1. Have computer on and Phone off
2. Boot your phone into ClockworkMod 3.1.0.1 (Power/camera/volume down)(it must be this version of clockwork)
3. Go to mounts and storage
4. On the bottom of the menu you must click mount usb storage.
5. Plug your phone into the computer and your computer should recognize your phone now.
Also if your on Vista / Win7 you should run the command line (cmd) or the bat file to root with admin rights: Right click cmd or the run.bat and select run as administrator and that hould help.
Sent from an Epic with 4G
I don't think the drivers for samsung are 64 bit compatable. If you got the drivers from samsung it should state that.
Sent from my lean mean drunken machine useing XDA Premium and a 12 pack of Sam Lager
tazfanatic said:
I don't think the drivers for samsung are 64 bit compatable. If you got the drivers from samsung it should state that.
Sent from my lean mean drunken machine useing XDA Premium and a 12 pack of Sam Lager
Click to expand...
Click to collapse
The ones installed through Windows Update run fine on my 64 bit Windows 7 Laptop.
kennyglass123 said:
The ones installed through Windows Update run fine on my 64 bit Windows 7 Laptop.
Click to expand...
Click to collapse
good to know.
Hello People
Some people couldn't open their Nexus 7 2013 drive on windows PC. I hope this helps
Open "settings" on nexus, Click on "storage", click on options (3 vertical dots on the top right corner), click on "USB computer connection" , Check allow MTP
Now try connecting to your PC.
iralamanoj said:
Hello People
Some people couldn't open their Nexus 7 2013 drive on windows PC. I hope this helps
Open "settings" on nexus, Click on "storage", click on options (3 vertical dots on the top right corner), click on "USB computer connection" , Check allow MTP
Now try connecting to your PC.
Click to expand...
Click to collapse
I've tried this. I guess I'll need to delete all the drivers and try again. Never had such a difficult time getting my computer to recognize USB Mass Storage.
** Update **
If it doesn't work, open device manager. Delete Google Adb device (including driver) and then plug your Nexus back in with the MTP checked. It will install the driver. Everything works now.
05GT said:
I've tried this. I guess I'll need to delete all the drivers and try again. Never had such a difficult time getting my computer to recognize USB Mass Storage.
** Update **
If it doesn't work, open device manager. Delete Google Adb device (including driver) and then plug your Nexus back in with the MTP checked. It will install the driver. Everything works now.
Click to expand...
Click to collapse
I am sorry to hear that your problem still exists. But it worked for my friends and me after checking the MTP option under Settings/Storage/Options/USB PC Connection. We are all using windows 8 PC. And Google released 4.3 update yesterday. If you didn't update, try updating your Nexus 7 2013.
It works!
iralamanoj said:
I am sorry to hear that your problem still exists. But it worked for my friends and me after checking the MTP option under Settings/Storage/Options/USB PC Connection. We are all using windows 8 PC. And Google released 4.3 update yesterday. If you didn't update, try updating your Nexus 7 2013.
Click to expand...
Click to collapse
Thank you a lot! It worked. I was going to install usb drivers but I dont need to install now. Great!
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Aerowinder said:
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Click to expand...
Click to collapse
That would have been roughly a year ago. I believe I did boot straight into the OS.
mdamaged said:
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Click to expand...
Click to collapse
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Allane176 said:
That would have been roughly a year ago. I believe I did boot straight into the OS.
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Click to expand...
Click to collapse
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
mdamaged said:
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
Click to expand...
Click to collapse
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Allane176 said:
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Click to expand...
Click to collapse
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download these, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
mdamaged said:
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
Click to expand...
Click to collapse
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Allane176 said:
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Click to expand...
Click to collapse
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install Wugs NRT, as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: http://www.nirsoft.net/utils/usb_devices_view.html, but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
mdamaged said:
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install ], as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: , but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
Click to expand...
Click to collapse
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Allane176 said:
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Click to expand...
Click to collapse
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
mdamaged said:
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
Click to expand...
Click to collapse
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Allane176 said:
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Click to expand...
Click to collapse
No problem, maybe you'll work on it again and you'll figure it out. Also, you can use airdroid for transfer of files, I hear it works really well.
I have windows 8.1 and my pc does not recognize my m8. It is connected and charging though, and I am using a USB 2.0 port. USB debugging on. On the device managers, no device shows up. I uninstall all HTC Drivers aswell. Any help? I just need it to have a yellow explanation mark device on device managers, and I know what to do from there.
I tried download HTC drivers but the htcdriver.exe won't bring up an installation window. I'm running out of time as I need to return to stock quickly before Wednesday.
ThePwnie said:
I tried download HTC drivers but the htcdriver.exe won't bring up an installation window. I'm running out of time as I need to return to stock quickly before Wednesday.
Click to expand...
Click to collapse
Try this solution.
[Q] Device not recognized by Windows 8.1
Have you tried different cables and usb ports? A different pc as a last resort?
Make sure you have no other phone drivers installed (Samsung, etc.) and make sure all HTC drivers are uninstalled. Make sure you don't accept the option to automatically install HTC Sync when you connect the phone. After that, you should get the yellow exclamation point in Device Manager. Select the option to manually select the drivers, and pick the generic Android MTP device (or some similar description).
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.