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.
Related
Guys I'm at my wits end. I'm about to give up. I'm trying to get adb working on the nook here on my work computer. I can't for the life of me get it to work. I had no problem on my laptop, but then again I think I caught it before windows installed anything.
I've been using "usbdeview" to uninstall rogue drivers, trying to reel in the problem. However every time I go into device manager, it try's to install "Android ADB interface" which I think means its assigning the wrong driver to it. It should be "Android Composite ADB Interface", no? I know thats what it is on my laptop.
Anybody have any last ditch efforts? I should note that adb works perfectly fine on my Aria on this same machine. I love ADB, hate the setup though.
*****EDIT: Working on different usb port*********
You aren't alone, m8.
I used to have no problem with ADB over USB. But after re-formatting my laptop, I just couldn't get it to work, no matter what I did. I gave up
I'd tried wireless ADB, everybody said it's so easy, me? Couldn't ever get it to work. Gave it also.
At least, for now, I wouldn't think I need it.
I'm now convinced its not driver related. There is something holding my computer back from talking to it. But I'm 99% the right drivers are installed. Mounting disks works fine and it identifies like my android phone does, ADB just won't talk to it.
Try unchecking and rechecking Debugging mode...
Tried that many times. Just for fun I ran the easy adb executable on another machine here, THEN plugged in my nook to it. ADB worked perfect. I'm frustrated, but I really want to figure this thing out. (btw, it identifies with the exact same drivers on both machines)
EDIT: Don't know why or how, but for some reason switching usb ports (which I swear I've done before) worked!!!!!!! It now recognizes and can push/pull/install over adb (usb).
WWW.Ubuntu.com
Enough said.
Love me some Ubuntu, but CMD prompt > Terminal every time.
If you don't mind, can you provide the link to where you downloaded the driver?
Thanks
I used the "combo" pack which installed the drivers and a stripped version of ADB to C: (redundant since I already had ADB installed).
http://forum.xda-developers.com/showthread.php?t=910008
Thanks audio,
I'll give it another try.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
Make sure you're Nook is identifying like this when its plugged in via device manager. If you're unsure how to get here; WINDOWS KEY + R, type without quotes "devmgmt.msc", hit ENTER.
{
"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"
}
Note: You're drive letter's under 'Portable Devices' may vary from mine, that's fine. Just make sure they are there.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
I got all those except the Disk drive list above.
I'll give a try and see what happens.
We may need to uninstall some old drivers before we can get it to install the right ones. You on gtalk or msn? I'll help you troubleshoot it the best I can.
Works like charm.
LOL , without this thread, I would (actually I did) abandon installing ADB over USB.
Thanks audio for providing the correct link.
Gotta love this forum.
Hi guys,
I have literally tried everything I could find here. I have tried the Universal drivers, the PDAnet drivers, and the Google drivers, and I have used an installer as well as manually installed the drivers. For the universal and Google drivers, I can get the phone to be recognized by Windows 7 as a Nexus 4, and Windows says the drivers are configured properly. However, the phone doesn't mount and ADB/fastboot still don't connect (and yes, the phone is in USB debugging mode).
After every failed driver I uninstalled the device, removed the Google drivers from USBdeview, and reinstalled the next set of drivers, to no avail. The computer has been restarted many times, no luck. I have tried all three USB ports on my laptop, and I have tried multiple cords, one of which I know for sure works.
Any suggestions would be appreciated. Thank you.
EDIT: If you want, I can add a screenshot of my USBDeview entries to see if there are any conflicting drivers/interfaces. My old phone was a Samsung Galaxy S, but I removed as many of those drivers as I could find.
Silly question, but when attempting fastboot, you did reboot into the bootloader? If you use twrp, they have an adb push setting in the advanced tab(?), see if that's recognized at all?
Sent from my Nexus 4 using Tapatalk 4 Beta
I couldn't use adb or fastboot at all. No adb when the phone is on, no fastboot in the boot loader. I don't have a custom recovery because I can't flash one without fastboot.
Sent from my Nexus 4 using xda app-developers app
I'm also on 64-bit Windows 7, I forgot to mention that. Just tried the Universal Naked Drivers, to no avail.
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
EddyOS said:
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
Click to expand...
Click to collapse
Thanks for the reply. I've been trying to use Minimal ADB and Fastboot so far, since I really don't want to download the SDK. However, I've also tried to use the newest versions of Wug's Nexus Root Toolkit and mskip's toolkit, both of which do not work.
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
EddyOS said:
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
Click to expand...
Click to collapse
The window never pops up on the phone. ADB list of devices comes up blank. I'll try the SDK later.
Using the SDK and the newest ADB did not help, still the same problem. I'm out of ideas.
EDIT: Attached are two screenshots of the USBDeview program after I've uninstalled all the Google and Android drivers. Is there anything there that looks like it needs to be uninstalled?
{
"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"
}
Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
{
"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"
}
blueren said:
Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
Click to expand...
Click to collapse
Just format it and install Ubuntu!!!
lol, just jocking. if adb is working you don't need it to recognize it. You can just use adb push/adb pull, but anyway.. did u try to enable debugging?
It means something has derped with the mtp driver
Open up device manager
You will see your nexus 4 with a yellow exclamation mark next to it
Right click and update driver
Manually choose
Then you will have to scroll through the list and find the mtp device (I can't remember of the top of my head exactly which headers it is under)
Sent from my Nexus 4 using xda app-developers app
Connect your Nexus 4 in USB debuggin mode and uninstall your current driver in device manager checking the 'delete the driver software' option.
Download Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1379875
Reboot Windows 8 into advance mode and select to disable driver signature: PC Settings -> Updates and recovery -> Recovery -> Advance startup -> select F7 option at the selection menu when you see it
Reconnect Nexus 4 and install it with UND driver.
Thanks all! I just uninstalled the current drivers and reconnected the device. Windows picked up on the right drivers. All ok!
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"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 already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:
If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"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"
}
Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.
I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.
Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.