Database Develop

ADB access broken....beyond frustrated

This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot

device not found has to do with the phone....make sure your cable is not messed up.

B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.

the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again

B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.

Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.

rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.

At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues

goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)

the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.

Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.

This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol

[Q] Captivate USB problems

Hi everyone,
I have an AT&T Captivate SGH-i897 (2nd hand) and i can't mount the phone to my laptop (winXP 32bit). When i plug in the cable to the phone and then the PC i get the "device not recognized".I've donwloaded the Samsung drivers from the xda wiki page and extracted them and tried to update the driveres via Device Mng ,but didn't work.Also dl'ed the Samsung drivers 5.0.x instaled ,and still nothing.USB Debugging is on...
So to recap,my top can't recognize the phone('s internal sd card) so plz help ???????

Try this, go into usb settings and choose "mass storage"
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

install kies

I would also recommend trying to fully uninstall all the drivers that associated on your pc with your phone (samsung or otherwise), and then reinstall the drivers before you plug in your phone. Then try to reconnect.

Just covering the basics. Assuming your phone is working correctly.
You have tried multiple USB ports on your computer, particularly those on the back if it's a desktop.
You have installed correct drivers (x86 or x64)
" for the correct operating system.
You have uninstalled the drivers before trying to reinstall.
You've tried to get Windows/ Mac to find them online (assuming you're using versions of OS that support doing that)
You've first tried Kies mini before full version, uninstalling in between. (Kies full version isn't supported for US, there are workarounds, but that's a different discussion)
On the phone you tell the phone to connect 'USB storage' (from the pull down menu after connected or in the settings)

I too am having problems with USB connectivity on a notebook with Win7/64. The usual failure mode is Windows not recognizing the USB device. I have followed ZBigT's basics, step by step and still cannot connect.
FWIW, my registry is awash with Samsung entries, some of which cannot be deleted.
I've even tried the AIO Toolbox application (to install the 64 bit drivers) to no avail.
Any other tips?

Is usb debugging turned off?

o hey guys sry for keeping u waiting,
i menaged to install ginger ,
the problem was my lap....rusty old bucket!!!!
had my friend come over with his lap and it worked like a charm ,
the problem is now i need a new one ;(,
damn

mrhaley30705 said:
Is usb debugging turned off?
Click to expand...
Click to collapse
Yes. Still no love. Have tried:
usb_drivers_GalaxyS_x64
SGH-i897_Captivate_USB_Drivers_5_02_0_2
mini-KIES
Kies
AIO
uninstalling reinstalling each time
When I plug in the Captivate, any of 3 USB ports on the laptop, Windows gives the "Unrecognized Device..." message.

Go to settings/about phone. Look at the very bottom to see what rom you are running.

mrhaley30705 said:
Go to settings/about phone. Look at the very bottom to see what rom you are running.
Click to expand...
Click to collapse
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.

mabovalu said:
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
Click to expand...
Click to collapse
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.

mrhaley30705 said:
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
Click to expand...
Click to collapse
Thanks for sticking with this. I was able to connect. I as focused on the Registry remnants, but your advice to clear out the Samsung folder in Programs worked. Thank you.
Additional comments: I am now running the Dlev ROM, it's OK, but when I plugged in the USB cable, just to the phone, it launched the Alarm Clock app! So I deleted that.
Then on the first of my four USB ports I got a USB driver failure to install, then the Windows Unrecognized USB device on ports 2 & 3. On port 4 it worked. (This is a Lennovo/Thinkpad notebook.)
I used the usb_drivers_GalaxyS_x64 package as that also worked on my desktop.
Thank you very much.

USB Mount Issues (CM7)

Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.

1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?

votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!

If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.

Oh, btw, have you had Nookcolotweaks app installed?

I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.

Do make sure you check OFF the USB Host feature (reboot and reconnect)

I gave that a try, too, but still nothing. So confusing!

Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build

When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.

I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk

Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.

A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?

Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck

I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.

Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.

arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.

junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.

arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.

Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.

Cant write to storage via MTP (Or any other mode) from Windows 10 to OP3T

--- SOLVED see first post second page! ---
Hello XDA,
I am only able to read data on the phone when connected via USB on windows. On the phone itself I can change whatever I want ( Via ES-explorer for example) But in windows file explorer I can't. It will not tell me that I do not have proper writing rights, but instead just decides to freeze for 10 minutes everytime I try to make a file change, to eventually give me a beautiful
"windows explorer is not responding" pop-up
What I have tried :
-Rebooting,
-Reinstalling USB drivers,
-Switching USB debugging on and off,
-Reinstalling root,
-Installing the newest Oxygen OS update from February,
-used different cables (also an old micro USB with adapter) And nothing works.
This sucks because I was just trying to change my photography workflow from being Desktop based to being Android based..
Any suggestions ?
Greetings,
Thijs
www.instagram.com/thi_js
Edits: Clarify issue

i have the same problem be great to find a solution

Did you maybe noticed when this problem occurs to you? I know that one months ago it just did work. Should I reinstall Windows completely?

I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back

lorfo123 said:
I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back
Click to expand...
Click to collapse
How should one file a bug-report for windows 10 then, this can't be something that shouldn't keep unnoticed by them.
Did rolling back fix something for you, and how did you do so?

I've checked another Windows 10 computer which hasn't been updated and it recognises my one plus 3T so if you Google / YouTube windows 10 roll back it should work

Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?

1asbak1 said:
Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?
Click to expand...
Click to collapse
The only other thing I could suggest is using a virtual machine to run win 7

Did you try back usb ports?. My pc with windows 10 fails with the front ports.

Solution
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.

New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%

ayush2901 said:
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.
Click to expand...
Click to collapse
Which version of TWRP are you running? The thing is that If I afterward can't restore the data via USB haha, then the whole point of backing it up seems invalid

lorfo123 said:
New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%
Click to expand...
Click to collapse
This actually worked. Wauw.
Had to reboot a view times in order to get it in effect, nonetheless, THANKS let the creativity start again

Really,My A** is burnt while my phone showing messages to update,,, Fiunally donw..Thanks a lot...!!

super it works

This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.

picollo7 said:
This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.
Click to expand...
Click to collapse
When you connect the phone to pc do you get a notification on your phone with the USB options?

DirkGently said:
When you connect the phone to pc do you get a notification on your phone with the USB options?
Click to expand...
Click to collapse
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver

picollo7 said:
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver
Click to expand...
Click to collapse
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.

DirkGently said:
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.
Click to expand...
Click to collapse
Haha, yeah. Does anyone have links to the drivers that work for them?

[Q] cant connect to pc in linux or windows

hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!

Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.

sorry double post

Same issue here. I've had no luck sorting it out.

Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?

Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.

I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.

ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!

Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?

ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?

Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.

ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.