So I'm trying to flash TWRP and it's been stuck on "<waiting for device>" for three hours. I also have the latest USB drivers from Samsung. My model is SM-G530P
Most obvious reason is a poor connection between PC and Android device: the device doesn't get detected.
Install latest ADB / Fastboot drivers
Re-boot Windows PC
Enable USB-Debugging in Android's settings -> Developer options
Re-boot Android device
I did all of that
Look inside here maybe it helps.
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
jogeiscool said:
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
Click to expand...
Click to collapse
Google search for;
"USB drivers for Samsung phones"
That should find a driver install .exe named "USB drivers for Samsung phones". Install those drivers.
If it still doesn't work, try a different computer, install the drivers and Odin on that PC then see if the device will connect.
Sent from my SM-S767VL using Tapatalk
Related
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Mani-saini said:
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Click to expand...
Click to collapse
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Yeah first make sure you see it in the Device Manager on Windows.
galarpo said:
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Click to expand...
Click to collapse
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
how to
Mani-saini said:
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
Click to expand...
Click to collapse
1- Hold SHIFT and restart you computer, always holding SHIFT or run this "shutdown /r /o"
2- You should be now on "Advanced Startup options", select "Troubleshoot" --->"Advanced Options"--->"Startup settings"--->"restart"
3- Next select option 7
4- plug your phone to computer in fastboot mode and install flashtool drivers, remenber to say yes on the windows appearing during installation, after everything is installed, restart your computer and problem solved.
I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
livinginavacuum said:
I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
Click to expand...
Click to collapse
What command are you typing?
cam30era said:
What command are you typing?
Click to expand...
Click to collapse
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
livinginavacuum said:
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
Click to expand...
Click to collapse
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
cam30era said:
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
Click to expand...
Click to collapse
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
You might try rebooting your PC.
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
AjunNg said:
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
Click to expand...
Click to collapse
I tried upgrading the driver to the android_winusb.inf path (from the same link as you provided).
Where can I download the Nexus Root Toolkit?
And wouldn't this still give me the same driver as from this link: http://developer.android.com/sdk/win-usb.html
livinginavacuum said:
Where can I download the Nexus Root Toolkit?
Click to expand...
Click to collapse
Anyone?
AjunNg said:
Have you enabled USB debugging?
.
Click to expand...
Click to collapse
Don't need USB debugging enabled to use ADB when in recovery.
livinginavacuum said:
Anyone?
Click to expand...
Click to collapse
http://bfy.tw/EcS
I recently acquired an SGP312 from ebay and the seller upgraded it to 5.0.2 without anyone asking for it (it was supposed to be NIB now who knows).
I have not unlocked the bootloader but I did confirm it is locked and can be unlocked.
I'm trying to connect it to my PC so I can get it rooted but I'm running into issues with the device being recognized.
I installed the Android SDK USB drivers & copied over android_winusb.inf and fastboot appears to be working fine. Windowns (7) Device Manager, Flashtool, and the Sony flash tool (Emma) all see the tab.
However, none of the other connection modes appear to work.
Flash mode will initially connect with Flashtool but the the device disconnects:
31/037/2015 23:37:03 - INFO - Device connected in flash mode
31/038/2015 23:38:04 - INFO - Device disconnected
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Device Manager shows an Other Devices with SGP312. I tried doing the Update Driver Software option with the drivers from the Sony developer site or the Android SDK drivers but no go.
I then boot up normally and connect either with or without ADB turned on and get the same Device Manager and driver results and PC Companion won't see the phone, either.
kadiir said:
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Download this package of drivers and install properly (Tick Flashmode, Fastboot, Common Drivers Lagan, Xperia Tablet Z drivers).
Sorry, I forgot to mention I ran the flash tool driver utility in the flashtool\drivers directory and chose the first 2 options and the XTZ-specific option but I'll give that a shot and report back.
While I did see a driver I missed I have little change in results other than MTP in non-USB debugging mode attempted to install a driver and failed:
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device
The system cannot find the file specified.
That reminds me that when I try to manually install the driver while in usb debugging mode it has the same message but with USB Composite Device where it says MTP USB Device.
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
kadiir said:
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
Click to expand...
Click to collapse
Seems to be this is an issue, because flashtool driver packages installed fine for me on WinXP/7/8.
Also pc-companion usually installs everything that is necessary for its fuctional, so must be OS problem.
Yep, that was it. Man, I should've checked that first. Sorry for the waste of time.
Quick question - do you know which ADB Interface I install from the SDK drivers? Is it ADB Interface or ADB Composite Interface? Or do I do 2 passes and install both?
Never mind - did some googling and got my answer. Thanks!
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?