Database Users

[HELP] My Nexus 4 is no longer recognized

Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance

I don't think you need to exchange it and Google should exchange it even if the bootloader is unlocked, provided you factory reset it I guess. And to re-lock the bootloader you just have to boot it into fastboot mode and type in the command line: fastboot oem lock
(Just follow this guide to return the phone to stock if you need: http://forum.xda-developers.com/showthread.php?t=2010312)
As for recognizing the device, maybe the MTP driver become unrecognized or conflicted, check in the Device Manager of your computer it should be called "Nexus 4" under Portable Devices. If it's not, right click on it and uninstall it. Then reconnect the phone and let it reinstall the driver, also try switching on and off USB Debugging option in the Developer mode.
If that still don't work, try this method: http://forum.xda-developers.com/showpost.php?p=35667806&postcount=23
Because this is likely a driver issue even if you get a new Nexus 4 your computer still might not recognize it. The issue is likely on your computer side, unless your phone's microUSB port is damaged somehow.

Thank you for answering.
I tried the command to lock the bootloader but it does not work because my device is not recognized
That catches image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You need to install the adb/fastboot driver, again, follow the link I posted for instruction. But you can download the Universal Naked Driver here: http://forum.xda-developers.com/showthread.php?t=1996051
sent from xda premium app

I tried to update the drivers but Windows told me that the driver is already up to date

Uninstall it and also check the option to delete the driver, then rescan the devices and reinstall it.
sent from xda premium app

Without success

In that case I suggest do a clean Windows 7 installation and reinstall the drivers on a clean system . Or wipe out Windows completely and install the latest Ubuntu which will detect your device automatically.

OK I installed ubuntu, I 'll let you know

I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange

androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Did you try to update sdk manager, provided it is installed on your C: drive?
This 1st step has proven to be helpful for re-installing drivers which let you access adb and fastboot.
Bonne chance, mon ami

Yes, the SDK is installed and the drivers google
Merci

androboy06 said:
Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance
Click to expand...
Click to collapse
I had simular issue.However if i am connected to USB and activate USB debugging, then windows sees the Nexus4 again as an MTP device, and stops as soon as i disable it. I know you said you tried that but still, thought i'd let you know.

I've ssay but thank you anyway

androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Don't exchange it. After uninstalling the drivers, go to pdanet and get the drivers there. I was having the same issue and that fixed it

I've tried, maybe my problem is hardware and not software

androboy06 said:
I've tried, maybe my problem is hardware and not software
Click to expand...
Click to collapse
can you be precise bro
is it windows 8 or windows 7??

I have two PCs, one with Windows 7 and one with Windows 8

USBDView(download it), remove anything android and nexus involved, reboot and replug
Sent from my Nexus 4 using xda app-developers app

Hello, I have the same problem.
My phone is in the official service center,and the last information I have is that it needs logic board replacement which costs aproximately 230 euros.
They would repair it under warranty if it wasn't rooted and flashed with TWRP. Of course, I dont want to pay that amount of money, so I'll try to find to buy a N4 with cracked screen and/or back and take the board from it.
So, if anyone has the same problem, the only solution is replacing the logic board or using ADB over wifi if the kernel supports that feature. Nothing else will work

[Q] Nexus 4 MTP Storage Problems

Recently, I have not been able to get my Nexus 4 to show up in my computer. I am able to use ADB and the drivers work fine, but when I connect my Nexus 4 it will not install the drivers for MTP. Rather, it will say it has the correct drivers installed, but it cannot start (Code: 10) and the icon for the device has a yellow exlamation mark next to it. I tried switching it between MTP and PTP as well as enabling and disabling USB Debugging, but it wont show up. Next, I decided to try to switch ROMS, as well as uninstall and re install all the drivers for the phone. No matter what I do I am able to connect to the phone through ADB, but MTP will give me the same error over again. Even on PTP my PC wont install the drivers for the phone.
I have looked through numerous threads and tried all kinds of solutions people have suggested, but none of them have worked for me. I've even tried switching between USB ports, cords, and computers (32 bit, 64 bit) and have tried plugging it into a new computer which i have never plugged the phone into, and nothing at all will work.
I am really at a loss here as I have spent many hours going through the solutions posted on these forums and others. I use USB for backing up my device as well as adding files etc. , and I dont want to do anything with my phone without being able to connect to it by USB at the very least. Airdroid will work as a temp. solution but it is way too slow when i transfer bigger files. My Nexus has worked fine with MTP since I bought 3 months ago, and even after rooting and updating the MTP has still worked regardless. I am running Windows 7 ultimate 64 bit, and my phone is on 4.3.
To anyone who will tell me to look on other threads I realize there are a ton of them out there, but I have tried using so many of the methods described, and none of them have worked.

Is there anyone that can help me with this problem? My phone is having issues and I need to backup up my stuff so I can flash to stock, factory wipe, etc.
Sent from my Nexus 4 using xda app-developers app

What rom and kernel are you running? Have you tried on stock firmware and stock kernel, with USB Debugging turned off? It sounds like an issue with the software in your phone.
Also when you connected your device, look in Device Manager and tell me the exact name listed for your Nexus 4, it should be saying "Nexus 4" or "Google Nexus 4 ADB Interface".
You can back up your files through adb: adb pull /sdcard/ C:\backup\
Instead of AirDroid you can try WorkGroup/Samba sharing. Enable a Workgroup shared folder on your PC then use ES File Explorer to access it and transfer file that way.

Here is my system info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried enabling and disabling debugging but it doesn't make much of a difference. It'll show up as MTP USB Device under portable devices with a yellow exclamation mark next to it, as well as Google ADB Interface Device under Android Device. Sometimes it will show up in Other Devices as Nexus 4, but then it install the drivers for ADB and it goes away.
I have also tried getting it to connect with AOKP milestone 2 (4.2.2) and the latest version of Carbon ROM which was also 4.2.2. I had Franco.kernel installed on both of these. The only thing I haven't done is a factory reset of all my data or flash back to stock rom.
Thanks for the backup tips I'll try those to see if I can get everything off it.
Sent from my Nexus 4 using xda app-developers app

Try uninstalling the driver, select the checkbox option to delete the files as well. Then reconnect it while in ADB mode and use the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=2263822
Also this will sound strange, but on your Pc, go into "Disk Manager" and make sure there are no blank partition or disk that might vaguely resemble your device. If there is one and without a driver letter, assign to it any drive letter.
Make sure there aren't conflicting ADB or USB drivers from other Android device, if there are, remove them.
Try live booting into Ubuntu 13.10, if it still can't copy your files, the phone is the problem.

Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.

Well let me know when it stopped working.
sent from xda premium app

Oh, one more thing. Is there a way for me to know what I can put onto the folder that shows up in the windows file explorer. Sometimes, I will put a folder in /sdcard, and it won't show up on the computer. It is really confusing sometimes when I need to move certain files to my computer.

Microsoft's MTP is a ****ty protocol, that's just my opinion.
The new files won't show up if it's not been read by the Media Server (I think), you have to do a media scan and replug the phone. If you still don't see it, just reboot the phone and let it scan the files for a few seconds before plugin it in. You should be able to move any files to the phone, just ignore the warning if it say the file might be incompatible.
sent from xda premium app

I often have to disable/uninstall the ADB device in Windows device manager to get MTP working...but that was on a Windows XP machine.

afff53 said:
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Click to expand...
Click to collapse
Something similar happened to me once. I reinstalled the drivers several times unsuccessfully and then it just started working. It seemed like a Windows 8 issue to me but I never determined for sure what caused it. Good luck.

I solved my problem at this way. Maybe it will help.

[GUIDE] adb and fastboot drivers for Windows

If someone has problems installing the official Motorola adb and fastboot drivers for Windows, try the following, this works for me:
1. download the UniversalADB driver from @Koush here: https://github.com/koush/UniversalAdbDriver
2. install it
3. locate the file android_winusb.inf in the folder (may vary) x:\Program Files\ClockworkMod\Universal Adb Driver\usb_driver
4. open it with any texteditor
5. add the following two lines (somewhere in the devices section) and save the file:
Code:
MotorolaADBInterface = USB_Install, USB\VID_22B8&PID_2E76&REV_0228&MI_01
MotorolaBootLoaderInterface = USB_Install, USB\VID_22B8&PID_2E80&REV_0100
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
7. enjoy!

Work fine thanks

Is the phone recognized by RSD Lite in fastboot mode with these drivers?
I have the Motorola drivers, using Windows 7 SP1 32-bit.
With USB debugging enabled I get a "Mot Composite ADB Interface" device in device manager (Driver Version 2.0.1.0).
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

t-bon3 said:
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
Click to expand...
Click to collapse
Got the same with the universal ADB/fastboot drivers damn.
[edit]
The MotoG PID is missing in PST.ini and/or sdk_common.ini, maybe we have to add it manually or wait for a new RSDlite

hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )

Worked great. Thank you

maty3ux said:
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Click to expand...
Click to collapse
Not yet, last version is 6.1.6

I do not understand this instruction:
shaftenberg said:
let Windows install this driver from koush's directory
Click to expand...
Click to collapse
Windows doesn't attempt to do anything when I connect the phone in ADB mode. Device Manager lists XT1034 under Other devices and says "The drivers for this device are not installed. (Code 28)". If I do "Update Driver Software" manually and direct it to the "ClockworkMod" directory, Windows says it cannot find driver software for the device. If I right click on the "android_winusb.inf" file and choose Install, Windows says the "file doesn't support this method of installation".

adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated

The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.

Thank you!!
it works for me
i installed Motorola device manager and this application
reversegear said:
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Click to expand...
Click to collapse
that's right .. i didn't do that too and it works

I've tried this and when I try to install it, it says "The INF file you selected does not support this method of installation." What do I do?

Didnt work for my moto g
sir, i am really new at this backup thing.
i just want to backup my injustice save game, so that i can restore it to previous point if something goes wrong.
i downloaded latest version on universaladbdriver but still my laptop didnt recognised my MOTO G.
i want to use HELIUM/CARBON for backup and i cant proceed till this problem is removed
please help me, i am new to xda as well.
THANKS
my os is win7 32 bit

hey
same problem i cant install adb or motorola drivers in my pc windows 7 64bit. the links with drives dont work for me..any solution? i want to unlock my bootloaderrrrrrrrrrrr :silly::silly::silly: (when i start to install the adb drivers stuck )
https://www.youtube.com/watch?v=RDA8PpPSFuk here i found solution for me i hope u help guyz(turn the music off )

Gronnd said:
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
Click to expand...
Click to collapse
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..

nuri-d said:
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
Click to expand...
Click to collapse
To solve this when u are in ADB go in device manager, find ur phone with yellow exclamation mark ( !), right click, insta driver-> manual-> android single sooner ADB interface! It will work like a charm!
Sent from my XT1032 using XDA Free mobile app

I had a similar problem on W7 x64, no driver available for my phone (Moto G LTE, XT1039) even with the Universal ADB driver from CWM and the two lines of the first post added in the INF file.
But, you can notice that all Motorola phones in the android_winusb.inf file refer to the same driver : MotCompositeInterface.
So I went to the Device Manager, found my phone, chose to Update the driver, Find a driver from my computer, Choose from List (sorry if the names are not accurate, my Windows version isn't in English).
Then, you can select ClockworkMod, scroll down to Mot Composite ADB Interface and choose it as your driver.
It worked for me (both in adb and fastboot mode), I was able to unlock my bootloader and flash a recovery using it.
Hope this helps !

Hi, I tried all the solutions in this post unsuccessfully, but I found one here: stackoverflow.com/questions/22217792/android-moto-g-mobile-doesnt-show-in-the-devices-list-of-eclipse
that is the simplest and the only one that worked for me.
Download 'Adb Driver Installer' from here adbdriver.com/downloads/
after this connect your Moto G and start the AdbDriverInstaller.exe it will list your device and then press install.
Click to expand...
Click to collapse

Windows 10 & ADB/Fastboot

Anyone here having issues on Windows 10 with ADB/Fastboot recognition?
I'm using the Android SDK Toolkit from the Google website, and I have both ADB and Fastboot installed. ADB recognizes the device, and started a shell on the device, everything is ok.
I reboot the device into fastboot mode, plug it into the same USB port where ADB was working, and nothing happens. It says "connect the usb cable". Frustrating as I'm looking to unlock the bootloader.
Tried rebooting from both MHP/PHP/Stock usb modes, which all opened an adb shell successfully, but fastboot mode is not recognized at all on the same usb port.
SOLVED see lower posts.

when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.

rodcpierce said:
when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.
Click to expand...
Click to collapse
List of devices attached
84BXXXXXXXXXX66 device
Looks like what I'm used to, as I said, adb shell works fine, I can change directory to system or whatever. Just doesn't recognize the device at all in fastboot mode.

hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.

rodcpierce said:
hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.
Click to expand...
Click to collapse
It's telling me to plug in the cord on the bootloader screen. "connect usb cable", I connect it. It still says "connect usb cable". However, in my device manager, I have an Android device that does not have a driver (Code 28).

go ahead and try and run your commands in ADB while on the bootloader screen.

rodcpierce said:
go ahead and try and run your commands in ADB while on the bootloader screen.
Click to expand...
Click to collapse
neither adb or fastboot commands work in bootloader mode on the same USB that ADB worked when phone was on.
The device is recognized in device manager (when in fastboot mode) but has no driver. Is it not the same usb driver responsible for ADB when device is on???

one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rodcpierce said:
one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
Click to expand...
Click to collapse
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
When the phone is on, it appears as a ADB Interface under Universal Serial Bus devices. When the phone is in bootloader mode it appears as Android Bootloader under Android Phone (the new driver). ADB works when the phone is on, but ADB does not work in bootloader mode. Only fastboot works in bootloader mode.

Magnetox said:
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
Click to expand...
Click to collapse
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.

rodcpierce said:
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.
Click to expand...
Click to collapse
No, thank you! Glad the post is here for others now.

Ok. I runned into all of this issues. I finally discovered that after you went into recovery, the device was being installed as a kedacom USB device. So I researched a little and found the solution in the link below.
Short solution:
Right click on "Start Button" and select Device Manager
Find Kedacom, drilldown and right click to update driver
Browser Computer
Let me Pick...
Then Select ADB Driver.
That should fix it.
I hope it helps.
https://www.reddit.com/r/oneplus/comments/59ux5d/cant_root_because_windows_10_keeps_installing/

Galaxy Note 3 not recognized in Odin when in download mode

Hello there, I have been searching for something for hours and just can't figure this out. So I have an old Galaxy Note 3 and want to get Lineageos running on it. Have done this before a few times with other phones, but here from the official guide I have to use Odin.
So what happens is that when the phone ist just regularly on I can see it in Odin, I can also see it when I do adb devices. I have usb debugging on and have set it to trust my computer.
However, as soon as I boot into download mode the phone becomes invisible to the computer, no return to adb, not visible in Odin.
Any ideas what I could be missing? Thanks so much!

Do you see other devices in the device manager?
Show the phone screen in download mode.
What OS on the PC? What version of drivers from Samsung? What variant of Odin?

Thank you for your fast reply! Really appreciate it! Of course I left out some info....
In the windows device manager I see other devices, I also see the note 3 when it is just regularly turned on, just not when in download mode. The note shows up in device manager as SAMSUNG Android ADB Interface and as SAMSUNG Mobile USB Composite Device. Using Odin 3.14, also tried 3.13 at some point.
OS in Windows, can't do Odin in others, can I? Played around with Heimdall on a Linux computer, but that did not go anywhere and can't find much documentation. Did not flash anything, just tried to see if I could get it visible.
Version of drivers from Samsung, how do I check that? I downloaded them from Samsung as in the official instructions.
Now the Download screen might be part of the issue here, I have been searching around with that, it seems that the last thing it says is "UDC start" is not what it is supposed to do... should be attached. Thanks again!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If the phone is in download mode, Windows sees the SAMSUNG Mobile USB CDC Composite Device as a serial bus controller, and Odin sees the COM port.
Install the latest drivers from Samsung (if you have older ones) and the latest adb from Google.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com

Thank you! Just reinstalled the drivers from samsung (already had them, but can't hurt), restarted, but no difference yet.
To clarify, by "installing the latest adb" you mean download the plattform tools, unzip, and then open a command line in the folder? That allows me to run adb commands, like I can do adb devices and will see the phone, just not when it is in download mode.
When in download mode my device manager does show me a Serial USB Device (COM5), however Samsung is not part of the name. It is the device though, as it disappears when unplugged. But since it does not state that it is a samsung device, I am thinking maybe that points to a driver issue in some way?

Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!

bilboBeutlinhh said:
Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!
Click to expand...
Click to collapse
Glad you got it sorted! Cheers

Thanks again! And in case anyone finds / reads this, it seems that just installing the Samsung drivers might not install them all, checking in the device manager when download mode is active and running an update of drivers from there made the difference.