Related
I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.
enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.
I need to root this device to upgrade the software, but I can't find the ADB driver, so I can't do anything about it.
I've tried all the usual suspects, SuperOneClicks driver doesn't work, neither does the robodobo thingy. Nurvo doesn't have any drivers on their site.
The device self-identifies as rk30sdk, which is pretty normal for the 3066 chipset, I guess.
Anyway, does anyone know of a driver that THEY KNOW will work? If you've done it yourself, that would be great, but please don't just link me to a forum post or name a driver that they think might work. I've already installed five different drivers, I'm getting tired of it..
have you checked if your device have usb debugging checked on and if you can access linux do lsusb and find the device id then go back to windoze and edit an adb usb driver inf file copy one line from the other line then change the device id in it to match your device it did worked for me on old tablets
Tom Fagerland said:
I need to root this device to upgrade the software, but I can't find the ADB driver, so I can't do anything about it.
I've tried all the usual suspects, SuperOneClicks driver doesn't work, neither does the robodobo thingy. Nurvo doesn't have any drivers on their site.
The device self-identifies as rk30sdk, which is pretty normal for the 3066 chipset, I guess.
Anyway, does anyone know of a driver that THEY KNOW will work? If you've done it yourself, that would be great, but please don't just link me to a forum post or name a driver that they think might work. I've already installed five different drivers, I'm getting tired of it..
Click to expand...
Click to collapse
I don't have Linux, and I understood almost nothing of that...
Under windows you can install almost any android driver regardless of your device, at least i use the same pack for motorola/lg/samsung phones and also some tablets work fine, just needed a different driver for a a13 tablet, but also used a generic driver it was not device specific.
Hi, I'm trying to go back to stock rom following this guide but I can't get adb to recognize my phone (even if I've already used adb in this pc to unlock the bootloader and flash the custom recovery). I'm on Liquid Smooth ROM and my pc has Windows 8.1.
I tried uninstalling motorola drivers and reinstalling again and uninstalling and letting windows install the drivers automatically but no luck either way (and USB debugging is activated in the phone).
When I access to the device manager in the pc it shows a warning sign on Motorola ADB Interface saying the controllers for that device are not installed, that the manufacturer is unknown and that there aren't compatible controllers for the device (I'm translating what the pic says for those who don't understand spanish xD). I tried to uninstall that Motorola ADB interface thing but it remains there.
What can I do?
SOLUTION: See last post.
You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.
Are you on CM11?
I had the same problem, tried Motorola USB Driver, Universal ADB driver, Google USB driver and also editing the USB.inf to match the hardwareID.. none of that worked until I set the USB computer connection to Camera (PTP)
Good luck!
neozen21 said:
Are you on CM11?
I had the same problem, tried Motorola USB Driver, Universal ADB driver, Google USB driver and also editing the USB.inf to match the hardwareID.. none of that worked until I set the USB computer connection to Camera (PTP)
Good luck!
Click to expand...
Click to collapse
That same thing happens to me, if I put it in camera mode it does work, the problem is that I need it to work in fastbood mode and it doesn't recognize my device there
gpz1100 said:
You'll need to manually install the driver for the unknown devices. Point to your motorola driver folder.
Click to expand...
Click to collapse
EDIT: I've found the solution, I noticed I had two Motorola ADB Interface controllers, one in "Android Devices" and the other in unknown controllers. I went to the unknown one and imported the same certificate the upper one had and now it works (though I have two Motorola ADB Interface in android devices).
binlalo said:
That same thing happens to me, if I put it in camera mode it does work, the problem is that I need it to work in fastbood mode and it doesn't recognize my device there
Click to expand...
Click to collapse
In fastboot mode, I made the USB work by using Koush's Universal ADB driver.
But if you are using Windows 8 or 8.1, you'll need to turn off the forced signature verification before you can install the drivers, since they are not signed.
Well... glad you got it..
binlalo said:
EDIT: I've found the solution, I noticed I had two Motorola ADB Interface controllers, one in "Android Devices" and the other in unknown controllers. I went to the unknown one and imported the same certificate the upper one had and now it works (though I have two Motorola ADB Interface in android devices).
Click to expand...
Click to collapse
Well... glad you got it..[/QUOTE]
can you explain how did you do this? i have the same problem on c-rom....
FaiTCRaH said:
Well... glad you got it..
Click to expand...
Click to collapse
can you explain how did you do this? i have the same problem on c-rom....[/QUOTE]
Go to device manager, you should see a device called "Android Device" (IIRC). Right click to update device drivers, select device driver, manually search for one but then pick choose from a list. You should be able to see the right driver that is normally used.
A couple days ago my mobile data just stopped working. I had a couple updates I had been ignoring because it would remove the root. I finally gave in and ran the updates. Data returned. Root gone. I connected to my home computer to begin the root process, but my phone would not be recognized by the PC and would not show anything related except that it was charging. It's a new cable, barely used. I tried on my work computer with a different cable and still nothing except "charging". To the best of my knowledge, it connected to my computer just fine prior to the updates.
I've checked Developer Options for anything that says "USB". Toggled USB debugging, revoked authorizations, etc. "Select USB Configuration" is a weird one, all I have are: "Charging", "MTP", "PTP", RNDIS (USB Eathernet)", and "MIDI". But in "Default USB Configuration" I have: "No data transfer", "File transfer / Android Auto", "MIDI", "PTP", "USB tethering". I've selected every option, but (again) no reaction from my phone or PC.
My final options are wipe and reset, or take it to a store; I'm wanting to avoid both of these if possible. Does anyone have an idea of what else I can try?
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
IamTheBRAVE said:
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
Click to expand...
Click to collapse
I'll take a look at that tonight.
To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
IamTheBRAVE said:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
Click to expand...
Click to collapse
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.
Both are Win10
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
IamTheBRAVE said:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
Click to expand...
Click to collapse
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.
Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.
Short version: Nothing worked.
I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.
I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?
I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".
I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.
Have you tried clearing out the dust bunny's in the usb port on phone?
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
MrSteelX said:
Have you tried clearing out the dust bunny's in the usb port on phone?
Click to expand...
Click to collapse
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.
IamTheBRAVE said:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
Click to expand...
Click to collapse
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
tconn said:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
Click to expand...
Click to collapse
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.
10.26 MB file on MEGA
mega.nz
You can use this thread as tutorial for root (you don't need all parts of it)
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.
So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.
So try different ports, different computers, something different.
The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).
Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/
Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.
Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.
So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.
Code:
[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"
Good luck.
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
tconn said:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
Click to expand...
Click to collapse
Try using a toothpick. Just try not to bend port too much.